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 Intel 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 Ethertap network tap (EXPERIMENTAL)
7224 If you say Y here (and have said Y to "Kernel/User network link
7225 driver", above) and create a character special file /dev/tap0 with
7226 major number 36 and minor number 16 using mknod ("man mknod"), you
7227 will be able to have a user space program read and write raw
7228 Ethernet frames from/to that special file. tap0 can be configured
7229 with ifconfig and route like any other Ethernet device but it is not
7230 connected to any physical LAN; everything written by the user to
7231 /dev/tap0 is treated by the kernel as if it had come in from a LAN
7232 to the device tap0; everything the kernel wants to send out over the
7233 device tap0 can instead be read by the user from /dev/tap0: the user
7234 mode program replaces the LAN that would be attached to an ordinary
7235 Ethernet device. Please read the file
7236 Documentation/networking/ethertap.txt for more information.
7238 This driver is also available as a module ( = code which can be
7239 inserted in and removed from the running kernel whenever you want).
7240 The module will be called ethertap.o. If you want to compile it as a
7241 module, say M here and read Documentation/modules.txt.
7243 If you don't know what to use this for, you don't need it.
7245 Sealevel Systems 4021 support
7246 CONFIG_SEALEVEL_4021
7247 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
7249 This driver can only be compiled as a module ( = code which can be
7250 inserted in and removed from the running kernel whenever you want).
7251 If you want to do that, say M here. The module will be called
7254 SyncLink HDLC/SYNCPPP support
7255 CONFIG_SYNCLINK_SYNCPPP
7256 Enables HDLC/SYNCPPP support for the SyncLink WAN driver.
7257 Normally the SyncLink WAN driver works with the main PPP
7258 driver (ppp.c) and pppd program. HDLC/SYNCPPP support allows use
7259 of the Cisco HDLC/PPP driver (syncppp.c).
7260 The SyncLink WAN driver (in character devices) must also be enabled.
7262 Frame Relay (DLCI) support
7264 This is support for the frame relay protocol; frame relay is a fast
7265 low-cost way to connect to a remote Internet access provider or to
7266 form a private wide area network. The one physical line from your
7267 box to the local "switch" (i.e. the entry point to the frame relay
7268 network, usually at the phone company) can carry several logical
7269 point-to-point connections to other computers connected to the frame
7270 relay network. For a general explanation of the protocol, check out
7271 http://www.frforum.com/ on the WWW. To use frame relay, you need
7272 supporting hardware (called FRAD) and certain programs from the
7273 net-tools package as explained in
7274 Documentation/networking/framerelay.txt.
7276 This driver is also available as a module ( = code which can be
7277 inserted in and removed from the running kernel whenever you want).
7278 The module will be called dlci.o. If you want to compile it as a
7279 module, say M here and read Documentation/modules.txt.
7283 This is the maximal number of logical point-to-point frame relay
7284 connections (the identifiers of which are called DCLIs) that
7285 the driver can handle. The default is probably fine.
7289 You can specify here how many logical point-to-point frame relay
7290 connections (the identifiers of which are called DCLIs) should be
7291 handled by each of your hardware frame relay access devices. Go with
7294 Sangoma S502A FRAD support
7296 Say Y here if you need a driver for the Sangoma S502A, S502E, and
7297 S508 Frame Relay Access Devices. These are multi-protocol cards, but
7298 only frame relay is supported by the driver at this time. Please
7299 read Documentation/framerelay.txt.
7301 This driver is also available as a module ( = code which can be
7302 inserted in and removed from the running kernel whenever you want).
7303 The module will be called sdla.o. If you want to compile it as a
7304 module, say M here and read Documentation/modules.txt.
7306 Acorn Econet/AUN protocols (EXPERIMENTAL)
7308 Econet is a fairly old and slow networking protocol mainly used by
7309 Acorn computers to access file and print servers. It uses native
7310 Econet network cards. AUN is an implementation of the higher level
7311 parts of Econet that runs over ordinary Ethernet connections, on
7312 top of the UDP packet protocol, which in turn runs on top of the
7313 Internet protocol IP.
7315 If you say Y here, you can choose with the next two options whether
7316 to send Econet/AUN traffic over a UDP Ethernet connection or over
7317 a native Econet network card.
7319 This driver is also available as a module ( = code which can be
7320 inserted in and removed from the running kernel whenever you want).
7321 The module will be called econet.o. If you want to compile it as a
7322 module, say M here and read Documentation/modules.txt.
7325 CONFIG_ECONET_AUNUDP
7326 Say Y here if you want to send Econet/AUN traffic over a UDP
7327 connection (UDP is a packet based protocol that runs on top of the
7328 Internet protocol IP) using an ordinary Ethernet network card.
7331 CONFIG_ECONET_NATIVE
7332 Say Y here if you have a native Econet network card installed in
7337 Wide Area Networks (WANs), such as X.25, frame relay and leased
7338 lines, are used to interconnect Local Area Networks (LANs) over vast
7339 distances with data transfer rates significantly higher than those
7340 achievable with commonly used asynchronous modem connections.
7341 Usually, a quite expensive external device called a `WAN router' is
7342 needed to connect to a WAN.
7344 As an alternative, WAN routing can be built into the Linux kernel.
7345 With relatively inexpensive WAN interface cards available on the
7346 market, a perfectly usable router can be built for less than half
7347 the price of an external router. If you have one of those cards and
7348 wish to use your Linux box as a WAN router, say Y here and also to
7349 the WAN driver for your card, below. You will then need the
7350 wan-tools package which is available from ftp://ftp.sangoma.com .
7351 Read Documentation/networking/wan-router.txt for more information.
7353 The WAN routing support is also available as a module called
7354 wanrouter.o ( = code which can be inserted in and removed from the
7355 running kernel whenever you want). If you want to compile it as a
7356 module, say M here and read Documentation/modules.txt.
7360 Fast switching (read help!)
7361 CONFIG_NET_FASTROUTE
7362 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
7363 Card) data transfers on the local network, which is fast.
7365 IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
7366 filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
7368 However, it will work with all options in the "IP: advanced router"
7369 section (except for "IP: use TOS value as routing key" and
7370 "IP: use FWMARK value as routing key").
7372 At the moment, few devices support fast switching (tulip is one of
7373 them, a modified 8390 driver can be found at
7374 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7378 Forwarding between high speed interfaces
7379 CONFIG_NET_HW_FLOWCONTROL
7380 This option enables NIC (Network Interface Card) hardware throttling
7381 during periods of extremal congestion. At the moment only a couple
7382 of device drivers support it (really only one -- tulip, a modified
7383 8390 driver can be found at
7384 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7386 Really, this option is applicable to any machine attached to a fast
7387 enough network, and even a 10 Mb NIC is able to kill a not very slow
7388 box, such as a 120MHz Pentium.
7390 However, do not say Y here if you did not experience any serious
7393 QoS and/or fair queueing
7395 When the kernel has several packets to send out over a network
7396 device, it has to decide which ones to send first, which ones to
7397 delay, and which ones to drop. This is the job of the packet
7398 scheduler, and several different algorithms for how to do this
7399 "fairly" have been proposed.
7401 If you say N here, you will get the standard packet scheduler, which
7402 is a FIFO (first come, first served). If you say Y here, you will be
7403 able to choose from among several alternative algorithms which can
7404 then be attached to different network devices. This is useful for
7405 example if some of your network devices are real time devices that
7406 need a certain minimum data flow rate, or if you need to limit the
7407 maximum data flow rate for traffic which matches specified criteria.
7408 This code is considered to be experimental.
7410 To administer these schedulers, you'll need the user-level utilities
7411 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/ .
7412 That package also contains some documentation; for more, check out
7413 http://snafu.freedom.org/linux2.2/iproute-notes.html .
7415 This Quality of Service (QoS) support will enable you to use
7416 Differentiated Services (diffserv) and Resource Reservation Protocol
7417 (RSVP) on your Linux router if you also say Y to "QoS support",
7418 "Packet classifier API" and to some classifiers below. Documentation
7419 and software is at http://icawww1.epfl.ch/linux-diffserv/ .
7421 If you say Y here and to "/proc file system" below, you will be able
7422 to read status information about packet schedulers from the file
7425 The available schedulers are listed in the following questions; you
7426 can say Y to as many as you like. If unsure, say N now.
7428 CBQ packet scheduler
7430 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
7431 scheduling algorithm for some of your network devices. This
7432 algorithm classifies the waiting packets into a tree-like hierarchy
7433 of classes; the leaves of this tree are in turn scheduled by
7434 separate algorithms (called "disciplines" in this context).
7436 See the top of net/sched/sch_cbq.c for references about the CBQ
7439 CBQ is a commonly used scheduler, so if you're unsure, you should
7440 say Y here. Then say Y to all the queueing algorithms below that you
7441 want to use as CBQ disciplines. Then say Y to "Packet classifier
7442 API" and say Y to all the classifiers you want to use; a classifier
7443 is a routine that allows you to sort your outgoing traffic into
7444 classes based on a certain criterion.
7446 This code is also available as a module called sch_cbq.o ( = code
7447 which can be inserted in and removed from the running kernel
7448 whenever you want). If you want to compile it as a module, say M
7449 here and read Documentation/modules.txt.
7451 CSZ packet scheduler
7453 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
7454 scheduling algorithm for some of your network devices. At the
7455 moment, this is the only algorithm that can guarantee service for
7456 real-time applications (see the top of net/sched/sch_csz.c for
7457 details and references about the algorithm).
7459 Note: this scheduler is currently broken.
7461 This code is also available as a module called sch_csz.o ( = code
7462 which can be inserted in and removed from the running kernel
7463 whenever you want). If you want to compile it as a module, say M
7464 here and read Documentation/modules.txt.
7466 #ATM pseudo-scheduler
7472 The simplest PRIO pseudo scheduler
7474 Say Y here if you want to use an n-band priority queue packet
7475 "scheduler" for some of your network devices or as a leaf discipline
7476 for the CBQ scheduling algorithm. If unsure, say Y.
7478 This code is also available as a module called sch_prio.o ( = code
7479 which can be inserted in and removed from the running kernel
7480 whenever you want). If you want to compile it as a module, say M
7481 here and read Documentation/modules.txt.
7485 Say Y here if you want to use the Random Early Detection (RED)
7486 packet scheduling algorithm for some of your network devices (see
7487 the top of net/sched/sch_red.c for details and references about the
7490 This code is also available as a module called sch_red.o ( = code
7491 which can be inserted in and removed from the running kernel
7492 whenever you want). If you want to compile it as a module, say M
7493 here and read Documentation/modules.txt.
7497 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
7498 packet scheduling algorithm for some of your network devices or as a
7499 leaf discipline for the CBQ scheduling algorithm (see the top of
7500 net/sched/sch_sfq.c for details and references about the SFQ
7503 This code is also available as a module called sch_sfq.o ( = code
7504 which can be inserted in and removed from the running kernel
7505 whenever you want). If you want to compile it as a module, say M
7506 here and read Documentation/modules.txt.
7510 Say Y here if you want to use the True Link Equalizer (TLE) packet
7511 scheduling algorithm for some of your network devices or as a leaf
7512 discipline for the CBQ scheduling algorithm. This queueing
7513 discipline allows the combination of several physical devices into
7514 one virtual device. (see the top of net/sched/sch_teql.c for
7517 This code is also available as a module called sch_teql.o ( = code
7518 which can be inserted in and removed from the running kernel
7519 whenever you want). If you want to compile it as a module, say M
7520 here and read Documentation/modules.txt.
7524 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
7525 packet scheduling algorithm for some of your network devices or as a
7526 leaf discipline for the CBQ scheduling algorithm (see the top of
7527 net/sched/sch_tbf.c for a description of the TBF algorithm).
7529 This code is also available as a module called sch_tbf.o ( = code
7530 which can be inserted in and removed from the running kernel
7531 whenever you want). If you want to compile it as a module, say M
7532 here and read Documentation/modules.txt.
7535 #+tristate ' GRED queue' CONFIG_NET_SCH_GRED
7536 #+tristate ' Diffserv field marker' CONFIG_NET_SCH_DSMARK
7537 #+tristate ' Ingress Qdisc' CONFIG_NET_SCH_INGRESS
7541 Say Y here if you want to include Quality Of Service scheduling
7542 features, which means that you will be able to request certain
7543 rate-of-flow limits for your network devices.
7545 This Quality of Service (QoS) support will enable you to use
7546 Differentiated Services (diffserv) and Resource Reservation Protocol
7547 (RSVP) on your Linux router if you also say Y to "Packet classifier
7548 API" and to some classifiers below. Documentation and software is at
7549 http://icawww1.epfl.ch/linux-diffserv/ .
7551 Note that the answer to this question won't directly affect the
7552 kernel: saying N will just cause this configure script to skip all
7553 the questions about QoS support.
7556 CONFIG_NET_ESTIMATOR
7557 In order for Quality of Service scheduling to work, the current
7558 rate-of-flow for a network device has to be estimated; if you say Y
7559 here, the kernel will do just that.
7561 Packet classifier API
7563 The CBQ scheduling algorithm requires that network packets which are
7564 scheduled to be sent out over a network device be classified
7565 according to some criterion. If you say Y here, you will get a
7566 choice of several different packet classifiers with the following
7569 This will enable you to use Differentiated Services (diffserv) and
7570 Resource Reservation Protocol (RSVP) on your Linux router.
7571 Documentation and software is at
7572 http://icawww1.epfl.ch/linux-diffserv/ .
7575 #tristate ' TC index classifier' CONFIG_NET_CLS_TCINDEX
7577 Routing tables based classifier
7578 CONFIG_NET_CLS_ROUTE4
7579 If you say Y here, you will be able to classify outgoing packets
7580 according to the route table entry they matched. If unsure, say Y.
7582 This code is also available as a module called cls_route.o ( = code
7583 which can be inserted in and removed from the running kernel
7584 whenever you want). If you want to compile it as a module, say M
7585 here and read Documentation/modules.txt.
7587 Firewall based classifier
7589 If you say Y here, you will be able to classify outgoing packets
7590 according to firewall criteria you specified.
7592 This code is also available as a module called cls_fw.o ( = code
7593 which can be inserted in and removed from the running kernel
7594 whenever you want). If you want to compile it as a module, say M
7595 here and read Documentation/modules.txt.
7599 If you say Y here, you will be able to classify outgoing packets
7600 according to their destination address. If unsure, say Y.
7602 This code is also available as a module called cls_u32.o ( = code
7603 which can be inserted in and removed from the running kernel
7604 whenever you want). If you want to compile it as a module, say M
7605 here and read Documentation/modules.txt
7607 Special RSVP classifier
7609 The Resource Reservation Protocol (RSVP) permits end systems to
7610 request a minimum and maximum data flow rate for a connection; this
7611 is important for real time data such as streaming sound or video.
7613 Say Y here if you want to be able to classify outgoing packets based
7614 on their RSVP requests.
7616 This code is also available as a module called cls_rsvp.o ( = code
7617 which can be inserted in and removed from the running kernel
7618 whenever you want). If you want to compile it as a module, say M
7619 here and read Documentation/modules.txt
7621 Special RSVP classifier for IPv6
7622 CONFIG_NET_CLS_RSVP6
7623 The Resource Reservation Protocol (RSVP) permits end systems to
7624 request a minimum and maximum data flow rate for a connection; this
7625 is important for real time data such as streaming sound or video.
7627 Say Y here if you want to be able to classify outgoing packets based
7628 on their RSVP requests and you are using the new Internet Protocol
7629 IPv6 as opposed to the older and more common IPv4.
7631 This code is also available as a module called cls_rsvp6.o ( = code
7632 which can be inserted in and removed from the running kernel
7633 whenever you want). If you want to compile it as a module, say M
7634 here and read Documentation/modules.txt
7637 # Traffic policing (needed for in/egress)
7638 # CONFIG_NET_CLS_POLICE
7640 ### Some expert please fill these in
7643 Network code profiler
7645 If you say Y here and to "/proc file system support" below, some
7646 obscure and undocumented information about the network code's
7647 performance will be written to /proc/net/profile. If you don't know
7648 what it is about, you don't need it: say N.
7650 Wan interfaces support
7652 Wide Area Networks (WANs), such as X.25, frame relay and leased
7653 lines, are used to interconnect Local Area Networks (LANs) over vast
7654 distances with data transfer rates significantly higher than those
7655 achievable with commonly used asynchronous modem connections.
7656 Usually, a quite expensive external device called a `WAN router' is
7657 needed to connect to a WAN.
7659 As an alternative, a relatively inexpensive WAN interface card can
7660 allow your Linux box to directly connect to a WAN. If you have one
7661 of those cards and wish to use it under Linux, say Y here and also
7662 to the WAN driver for your card, below.
7666 Comtrol Hostess SV-11 support
7668 This is a network card for low speed synchronous serial links, at
7669 up to 256Kbps. It supports both PPP and Cisco HDLC.
7671 At this point, the driver can only be compiled as a module.
7673 COSA/SRP sync serial boards support
7675 This is a driver for COSA and SRP synchronous serial boards. These
7676 boards allow to connect synchronous serial devices (for example
7677 base-band modems, or any other device with the X.21, V.24, V.35 or
7678 V.36 interface) to your Linux box. The cards can work as the
7679 character device, synchronous PPP network device, or the Cisco HDLC
7682 To actually use the COSA or SRP board, you will need user-space
7683 utilities for downloading the firmware to the cards and to set them
7684 up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
7685 information about the cards (including the pointer to the user-space
7686 utilities). You can also read the comment at the top of the
7687 drivers/net/cosa.c for details about the cards and the driver
7690 The driver will be compiled as a module ( = code which can be
7691 inserted in and removed from the running kernel whenever you want).
7692 The module will be called cosa.o. For general information about
7693 modules read Documentation/modules.txt.
7695 Lan Media sync serial boards support
7697 This is a driver for the following Lan Media family of serial boards.
7699 LMC 1000 board allows you to connect synchronous serial devices (for
7700 example base-band modems, or any other device with the X.21, V.24,
7701 V.35 or V.36 interface) to your Linux box.
7703 LMC 1200 with on board DSU board allows you to connect your Linux
7704 box dirrectly to a T1 or E1 circuit.
7706 LMC 5200 board provides a HSSI interface capable of runnig up to
7707 52 mbits per second.
7709 LMC 5245 board connects directly to a T3 circuit saving the
7710 additional external hardware.
7712 To change setting such as syncPPP vs cisco HDLC or clock source you
7713 will need lmcctl. It it available at ftp.lanmedia.com.
7715 This code is also available as a module called lmc.o ( = code
7716 which can be inserted in and removed from the running kernel
7717 whenever you want). If you want to compile it as a module, say M
7718 here and read Documentation/modules.txt.
7720 Fibre Channel driver support
7722 Fibre Channel is a high speed serial protocol mainly used to connect
7723 large storage devices to the computer; it is compatible with and
7724 intended to replace SCSI.
7726 If you intend to use Fibre Channel, you need to have a Fibre channel
7727 adaptor card in your computer; say Y here and to the driver for your
7728 adaptor below. You also should have said Y to "SCSI support" and
7729 "SCSI generic support".
7731 Interphase 5526 Tachyon chipset based adaptor support
7733 Say Y here if you have a Fibre Channel adaptor of this kind.
7735 The driver is also available as a module ( = code which can be
7736 inserted in and removed from the running kernel whenever you want).
7737 The module will be called iph5526.o. For general information about
7738 modules read Documentation/modules.txt.
7740 Red Creek Hardware VPN (EXPERIMENTAL)
7742 This is a driver for hardware which provides a Virtual Private
7743 Network (VPN). Say Y if you have it.
7745 This code is also available as a module called rcpci.o ( = code
7746 which can be inserted in and removed from the running kernel
7747 whenever you want). If you want to compile it as a module, say M
7748 here and read Documentation/modules.txt.
7752 This is a driver for ISA SBNI12-xx cards which are low cost
7753 alternatives to leased line modems. Say Y if you want to insert
7754 the driver into the kernel or say M to compile it as a module (the
7755 module will be called sbni.o).
7757 You can find more information and last versions of drivers and
7758 utilities at http://www.granch.ru . If you have any question you
7759 can send email to sbni@granch.ru.
7764 CONFIG_WAN_ROUTER_DRIVERS
7765 If you have a WAN interface card and you want your Linux box to act
7766 as a WAN router, thereby connecting you Local Area Network to the
7767 outside world over the WAN connection, say Y here and then to the
7768 driver for your card below. In addition, you need to say Y to "Wan
7771 You will need the wan-tools package which is available from
7772 ftp://ftp.sangoma.com . Read Documentation/networking/wan-router.txt
7773 for more information.
7775 Note that the answer to this question won't directly affect the
7776 kernel: saying N will just cause this configure script to skip all
7777 the questions about WAN router drivers. If unsure, say N.
7779 Sangoma WANPIPE(tm) multiprotocol cards
7780 CONFIG_VENDOR_SANGOMA
7781 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com ) is
7782 a family of intelligent multiprotocol WAN adapters with data
7783 transfer rates up to T1 (1.544 Mbps). They are also known as
7784 Synchronous Data Link Adapters (SDLA) and designated S502E(A), S503
7785 or S508. These cards support the X.25, Frame Relay, and PPP
7786 protocols. If you have one or more of these cards, say Y to this
7787 option; you may then also want to read the file
7788 Documentation/networking/wanpipe.txt. The next questions will ask
7789 you about the protocols you want the driver to support.
7791 The driver will be compiled as a module ( = code which can be
7792 inserted in and removed from the running kernel whenever you want).
7793 The module will be called wanpipe.o. For general information about
7794 modules read Documentation/modules.txt.
7796 Maximum number of cards
7797 CONFIG_WANPIPE_CARDS
7798 Enter number of WANPIPE adapters installed in your machine. The
7799 driver can support up to 8 cards. You may enter more than you
7800 actually have if you plan to add more cards in the future without
7801 re-compiling the driver, but remember that in this case you'll waste
7802 some kernel memory (about 1K per card).
7804 WANPIPE Cisco HDLC support
7805 CONFIG_WANPIPE_CHDLC
7806 Say Y to this option if you are planning to connect a WANPIPE card
7807 to a connection which uses the synchronous Cisco HDLC (High-level
7808 Data Link Control) protocol. This protocol is often used on
7809 high-speed leased lines like T1/E1.
7811 WANPIPE X.25 support
7813 Say Y to this option if you are planning to connect a WANPIPE card
7814 to an X.25 network. You should then also have said Y to "CCITT X.25
7815 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
7816 X.25 support will not be included in the driver (saves about 16 KB
7819 WANPIPE Frame Relay support
7821 Say Y to this option if you are planning to connect a WANPIPE card
7822 to a frame relay network. You should then also have said Y to "Frame
7823 Relay (DLCI) support", above. If you say N, the frame relay
7824 support will not be included in the driver (saves about 16 KB of
7829 Say Y to this option if you are planning to connect a WANPIPE card
7830 to a leased line using Point-to-Point protocol (PPP). You should
7831 then also have said Y to "PPP (point-to-point) support", above. If
7832 you say N, the PPP support will not be included in the driver (saves
7833 about 16 KB of kernel memory).
7835 MultiGate/COMX support
7837 Say Y if you want to use any board from the MultiGate (COMX) family.
7838 These boards are synchronous serial adapters for the PC,
7839 manufactured by ITConsult-Pro Co, Hungary.
7841 Read linux/Documentation/networking/comx.txt for help on configuring
7842 and using COMX interfaces. Further info on these cards can be found
7843 at http://www.itc.hu or <info@itc.hu>.
7845 If you want to compile this as a module, say M and read
7846 Documentation/modules.txt. The module will be called comx.o.
7848 COMX/CMX/HiCOMX board support
7850 Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the
7851 MultiGate family. Say Y if you have one of these.
7853 You will need additional firmware to use these cards, which are
7854 downloadable from ftp://ftp.itc.hu/.
7856 If you want to compile this as a module, say M and read
7857 Documentation/modules.txt. The module will be called comx-hw-comx.o.
7859 LoCOMX board support
7860 CONFIG_COMX_HW_LOCOMX
7861 Hardware driver for the 'LoCOMX' board from the MultiGate family.
7862 Say Y if you have a board like this.
7864 If you want to compile this as a module, say M and read
7865 Documentation/modules.txt. The module will be called
7868 MixCOM board support
7869 CONFIG_COMX_HW_MIXCOM
7870 Hardware driver for the 'MixCOM' board from the MultiGate family.
7871 Say Y if you have a board like this.
7873 If you want to use the watchdog device on this card, you should
7874 select it in the Watchdog Cards section of the Character Devices
7875 configuration. The ISDN interface of this card is Teles 16.3
7876 compatible, you should enable it in the ISDN configuration menu. The
7877 driver for the flash ROM of this card is available separately on
7880 If you want to compile this as a module, say M and read
7881 Documentation/modules.txt. The module will be called
7884 MultiGate Cisco-HDLC and synchronous PPP protocol support
7885 CONFIG_COMX_PROTO_PPP
7886 Cisco-HDLC and synchronous PPP protocol driver for all MultiGate
7887 boards. Say Y if you want to use either protocol on your MultiGate
7890 If you want to compile this as a module, say M and read
7891 Documentation/modules.txt. The module will be called
7894 MultiGate LAPB protocol support
7895 CONFIG_COMX_PROTO_LAPB
7896 LAPB protocol driver for all MultiGate boards. Say Y if you
7897 want to use this protocol on your MultiGate boards.
7899 If you want to compile this as a module, say M and read
7900 Documentation/modules.txt. The module will be called
7903 MultiGate Frame Relay protocol support
7904 CONFIG_COMX_PROTO_FR
7905 Frame Relay protocol driver for all MultiGate boards. Say Y if you
7906 want to use this protocol on your MultiGate boards.
7908 If you want to compile this as a module, say M and read
7909 Documentation/modules.txt. The module will be called
7912 Cyclom 2X(tm) multiprotocol cards (EXPERIMENTAL)
7913 CONFIG_CYCLADES_SYNC
7914 Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
7915 http://www.cyclades.com.br) is an intelligent multiprotocol WAN
7916 adapter with data transfer rates up to 512 Kbps. These cards support
7917 the X.25 and SNA related protocols. If you have one or more of these
7918 cards, say Y to this option. The next questions will ask you about
7919 the protocols you want the driver to support (for now only X.25 is
7922 While no documentation is available at this time please grab the
7923 wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
7924 (with minor changes to make it compile with the current wanrouter
7925 include files; efforts are being made to use the original package
7926 available at ftp://ftp.sangoma.com ).
7928 Feel free to contact me or the cycsyn-devel mailing list at
7929 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
7930 additional details, I hope to have documentation available as soon
7931 as possible. (Cyclades Brazil is writing the Documentation).
7933 The driver will be compiled as a module ( = code which can be
7934 inserted in and removed from the running kernel whenever you want).
7935 The module will be called cyclomx.o. For general information about
7936 modules read Documentation/modules.txt.
7938 Cyclom 2X X.25 support
7940 Say Y to this option if you are planning to connect a Cyclom 2X card
7943 If you say N, the X.25 support will not be included in the driver
7944 (saves about 11 KB of kernel memory).
7946 Ethernet (10 or 100Mbit)
7948 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
7949 type of Local Area Network (LAN) in universities and companies.
7951 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
7952 coaxial cable, linking computers in a chain), 10BASE-T or twisted
7953 pair (10 Mbps over twisted pair cable, linking computers to central
7954 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
7955 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
7956 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
7957 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
7958 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
7959 Ethernet (1 Gbps over optical fiber or short copper links).
7961 If your Linux machine will be connected to an Ethernet and you have
7962 an Ethernet network interface card (NIC) installed in your computer,
7963 say Y here and read the Ethernet-HOWTO, available from
7964 http://www.linuxdoc.org/docs.html#howto . You will then also have
7965 to say Y to the driver for your particular NIC.
7967 Note that the answer to this question won't directly affect the
7968 kernel: saying N will just cause this configure script to skip all
7969 the questions about Ethernet network cards. If unsure, say N.
7971 Western Digital/SMC cards
7972 CONFIG_NET_VENDOR_SMC
7973 If you have a network (Ethernet) card belonging to this class, say Y
7974 and read the Ethernet-HOWTO, available from
7975 http://www.linuxdoc.org/docs.html#howto .
7977 Note that the answer to this question doesn't directly affect the
7978 kernel: saying N will just cause this configure script to skip all
7979 the questions about Western Digital cards. If you say Y, you will be
7980 asked for your specific card in the following questions.
7984 If you have a network (Ethernet) card of this type, say Y and read
7985 the Ethernet-HOWTO, available from
7986 http://www.linuxdoc.org/docs.html#howto .
7988 This driver is also available as a module ( = code which can be
7989 inserted in and removed from the running kernel whenever you want).
7990 The module will be called wd.o. If you want to compile it as a
7991 module, say M here and read Documentation/modules.txt as well as
7992 Documentation/networking/net-modules.txt.
7994 SMC Ultra MCA support
7996 If you have a network (Ethernet) card of this type and are running
7997 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
7998 available from http://www.linuxdoc.org/docs.html#howto .
8000 This driver is also available as a module ( = code which can be
8001 inserted in and removed from the running kernel whenever you want).
8002 The module will be called smc-mca.o. If you want to compile it as a
8003 module, say M here and read Documentation/modules.txt as well as
8004 Documentation/networking/net-modules.txt.
8008 If you have a network (Ethernet) card of this type, say Y and read
8009 the Ethernet-HOWTO, available from
8010 http://www.linuxdoc.org/docs.html#howto .
8012 Important: There have been many reports that, with some motherboards
8013 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
8014 such as some BusLogic models) causes corruption problems with many
8015 operating systems. The Linux smc-ultra driver has a work-around for
8016 this but keep it in mind if you have such a SCSI card and have
8019 This driver is also available as a module ( = code which can be
8020 inserted in and removed from the running kernel whenever you want).
8021 The module will be called smc-ultra.o. If you want to compile it as
8022 a module, say M here and read Documentation/modules.txt as well as
8023 Documentation/networking/net-modules.txt.
8025 SMC Ultra32 EISA support
8027 If you have a network (Ethernet) card of this type, say Y and read
8028 the Ethernet-HOWTO, available from
8029 http://www.linuxdoc.org/docs.html#howto .
8031 This driver is also available as a module ( = code which can be
8032 inserted in and removed from the running kernel whenever you want).
8033 The module will be called smc-ultra32.o. If you want to compile it
8034 as a module, say M here and read Documentation/modules.txt as well
8035 as Documentation/networking/net-modules.txt.
8039 This is support for the SMC9xxx based Ethernet cards. Choose this
8040 option if you have a DELL laptop with the docking station, or
8041 another SMC9192/9194 based chipset. Say Y if you want it compiled
8042 into the kernel, and read the file
8043 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
8044 from http://www.linuxdoc.org/docs.html#howto .
8046 This driver is also available as a module ( = code which can be
8047 inserted in and removed from the running kernel whenever you
8048 want). The module will be called smc9194.o. If you want to compile
8049 it as a module, say M here and read Documentation/modules.txt as
8050 well as Documentation/networking/net-modules.txt.
8054 This driver is for NE2000 compatible PCI cards. It will not work
8055 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
8056 support" below). If you have a PCI NE2000 network (Ethernet) card,
8057 say Y and read the Ethernet-HOWTO, available from
8058 http://www.linuxdoc.org/docs.html#howto .
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 ne2k-pci.o. If you want to compile it as a
8063 module, say M here and read Documentation/modules.txt as well as
8064 Documentation/networking/net-modules.txt.
8066 Racal-Interlan (Micom) NI cards
8067 CONFIG_NET_VENDOR_RACAL
8068 If you have a network (Ethernet) card belonging to this class, such
8069 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
8070 available from http://www.linuxdoc.org/docs.html#howto .
8072 Note that the answer to this question doesn't directly affect the
8073 kernel: saying N will just cause this configure script to skip all
8074 the questions about NI cards. If you say Y, you will be asked for
8075 your specific card in the following questions.
8077 NI5010 support (EXPERIMENTAL)
8079 If you have a network (Ethernet) card of this type, say Y and read
8080 the Ethernet-HOWTO, available from
8081 http://www.linuxdoc.org/docs.html#howto . Note that this is still
8084 This driver is also available as a module ( = code which can be
8085 inserted in and removed from the running kernel whenever you want).
8086 The module will be called ni5010.o. If you want to compile it as a
8087 module, say M here and read Documentation/modules.txt as well as
8088 Documentation/networking/net-modules.txt.
8092 If you have a network (Ethernet) card of this type, say Y and read
8093 the Ethernet-HOWTO, available from
8094 http://www.linuxdoc.org/docs.html#howto .
8096 This driver is also available as a module ( = code which can be
8097 inserted in and removed from the running kernel whenever you want).
8098 The module will be called ni52.o. If you want to compile it as a
8099 module, say M here and read Documentation/modules.txt as well as
8100 Documentation/networking/net-modules.txt.
8104 If you have a network (Ethernet) card of this type, say Y and read
8105 the Ethernet-HOWTO, available from
8106 http://www.linuxdoc.org/docs.html#howto .
8108 This driver is also available as a module ( = code which can be
8109 inserted in and removed from the running kernel whenever you want).
8110 The module will be called ni65.o. If you want to compile it as a
8111 module, say M here and read Documentation/modules.txt as well as
8112 Documentation/networking/net-modules.txt.
8114 RealTek 8129 (not 8019/8029!) support (EXPERIMENTAL)
8116 This is a driver for the Fast Ethernet PCI network cards based on
8117 the RTL8129 chip. If you have one of those, say Y and
8118 read the Ethernet-HOWTO, available from
8119 http://www.linuxdoc.org/docs.html#howto .
8121 If you want to compile this driver as a module ( = code which can be
8122 inserted in and removed from the running kernel whenever you want),
8123 say M here and read Documentation/modules.txt. This is recommended.
8124 The module will be called rtl8129.o.
8126 RealTek RTL-8139 PCI Fast Ethernet Adapter support
8128 This is a driver for the Fast Ethernet PCI network cards based on
8129 the RTL8139 chips. If you have one of those, say Y and read
8130 Documentation/networking/8139too.txt as well as the Ethernet-HOWTO,
8131 available from http://www.linuxdoc.org/docs.html#howto .
8133 If you want to compile this driver as a module ( = code which can be
8134 inserted in and removed from the running kernel whenever you want),
8135 say M here and read Documentation/modules.txt. This is recommended.
8136 The module will be called 8139too.o.
8138 SiS 900 PCI Fast Ethernet Adapter support
8140 This is a driver for the Fast Ethernet PCI network cards based on
8141 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
8142 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
8143 read the Ethernet-HOWTO, available at
8144 http://www.linuxdoc.org/docs.html#howto . Please read
8145 Documentation/networking/sis900.txt and comments at the beginning of
8146 drivers/net/sis900.c for more information.
8148 This driver also supports AMD 79C901 HomePNA so that you can use
8149 your phone line as a network cable.
8151 If you want to compile this driver as a module ( = code which can be
8152 inserted in and removed from the running kernel whenever you want),
8153 say M here and read Documentation/modules.txt. This is recommended.
8154 The module will be called sis900.o.
8156 Packet Engines Yellowfin Gigabit-NIC support
8158 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
8159 adapter. This adapter is used by the Beowulf Linux cluster project.
8160 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
8161 more information about this driver in particular and Beowulf in
8164 If you want to compile this driver as a module ( = code which can be
8165 inserted in and removed from the running kernel whenever you want),
8166 say M here and read Documentation/modules.txt. This is recommended.
8167 The module will be called yellowfin.o.
8169 General Instruments Surfboard 1000
8171 This is a driver for the General Instrument (also known as
8172 NextLevel) SURFboard 1000 internal
8173 cable modem. This is an ISA card which is used by a number of cable
8174 TV companies to provide cable modem access. It's a one-way
8175 downstream-only cable modem, meaning that your upstream net link is
8176 provided by your regular phone modem.
8178 At present this driver only compiles as a module, so say M here if
8179 you have this card. The module will be called sb1000.o. Then read
8180 Documentation/networking/README.sb1000 for information on how to use
8181 this module, as it needs special ppp scripts for establishing a
8182 connection. Further documentation and the necessary scripts can be
8185 http://www.jacksonville.net/~fventuri/
8186 http://home.adelphia.net/~siglercm/sb1000.html
8187 http://linuxpower.cx/~cable/
8189 If you don't have this card, of course say N.
8191 Adaptec Starfire support (EXPERIMENTAL)
8192 CONFIG_ADAPTEC_STARFIRE
8193 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
8194 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
8195 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
8198 If you want to compile this driver as a module ( = code which can be
8199 inserted in and removed from the running kernel whenever you want),
8200 say M here and read Documentation/modules.txt. This is recommended.
8201 The module will be called starfile.o.
8203 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
8205 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
8206 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
8207 adapter. The driver allows for using the Jumbo Frame option (9000
8208 bytes/frame) however it requires that your switches can handle this
8209 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
8212 If you want to compile this driver as a module ( = code which can be
8213 inserted in and removed from the running kernel whenever you want),
8214 say M here and read Documentation/modules.txt. This is recommended.
8215 The module will be called acenic.o.
8217 Omit support for older Tigon I based AceNICs
8218 CONFIG_ACENIC_OMIT_TIGON_I
8219 Say Y here if you only have Tigon II based AceNICs and want to leave
8220 out support for the older Tigon I based cards which are no longer
8221 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
8222 version)). This will reduce the size of the driver object by
8223 app. 100KB. If you are not sure whether your card is a Tigon I or a
8224 Tigon II, say N here.
8226 The safe and default value for this is N.
8228 SysKonnect SK-98xx support
8230 Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server
8231 Adapter. The following adapters are supported by this driver:
8232 - SK-9841 (single link 1000Base-LX)
8233 - SK-9842 (dual link 1000Base-LX)
8234 - SK-9843 (single link 1000Base-SX)
8235 - SK-9844 (dual link 1000Base-SX)
8236 - SK-9821 (single link 1000Base-T)
8237 - SK-9822 (dual link 1000Base-T)
8238 The dual link adapters support a link-failover feature.
8239 Read Documentation/networking/sk98lin.txt for information about
8240 optional driver parameters.
8241 Questions concerning this driver may be addressed to:
8244 If you want to compile this driver as a module ( = code which can be
8245 inserted in and removed from the running kernel whenever you want),
8246 say M here and read Documentation/modules.txt. This is recommended.
8247 The module will be called sk98lin.o.
8249 MyriCOM Gigabit Ethernet support
8251 This driver supports MyriCOM Sbus gigabit ethernet cards.
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 myri_sbus.o.
8258 AMD LANCE and PCnet (AT1500 and NE2100) support
8260 If you have a network (Ethernet) card of this type, say Y and read
8261 the Ethernet-HOWTO, available from
8262 http://www.linuxdoc.org/docs.html#howto . Some LinkSys cards are
8265 If you want to compile this driver as a module ( = code which can be
8266 inserted in and removed from the running kernel whenever you want),
8267 say M here and read Documentation/modules.txt. This is recommended.
8268 The module will be called lance.o.
8272 If you have a network (Ethernet) card of this type, say Y and read
8273 the Ethernet-HOWTO, available from
8274 http://www.linuxdoc.org/docs.html#howto .
8277 CONFIG_NET_VENDOR_3COM
8278 If you have a network (Ethernet) card belonging to this class, say Y
8279 and read the Ethernet-HOWTO, available from
8280 http://www.linuxdoc.org/docs.html#howto .
8282 Note that the answer to this question doesn't directly affect the
8283 kernel: saying N will just cause this configure script to skip all
8284 the questions about 3COM cards. If you say Y, you will be asked for
8285 your specific card in the following questions.
8289 If you have a network (Ethernet) card of this type, say Y and read
8290 the Ethernet-HOWTO, available from
8291 http://www.linuxdoc.org/docs.html#howto . Also, consider buying a
8292 new card, since the 3c501 is slow, broken, and obsolete: you will
8293 have problems. Some people suggest to ping ("man ping") a nearby
8294 machine every minute ("man cron") when using this card.
8296 This driver is also available as a module ( = code which can be
8297 inserted in and removed from the running kernel whenever you want).
8298 The module will be called 3c501.o. If you want to compile it as a
8299 module, say M here and read Documentation/modules.txt as well as
8300 Documentation/networking/net-modules.txt.
8304 If you have a network (Ethernet) card of this type, say Y and read
8305 the Ethernet-HOWTO, available from
8306 http://www.linuxdoc.org/docs.html#howto .
8308 This driver is also available as a module ( = code which can be
8309 inserted in and removed from the running kernel whenever you want).
8310 The module will be called 3c503.o. If you want to compile it as a
8311 module, say M here and read Documentation/modules.txt as well as
8312 Documentation/networking/net-modules.txt.
8316 Information about this network (Ethernet) card can be found in
8317 Documentation/networking/3c505.txt. If you have a card of this type,
8318 say Y and read the Ethernet-HOWTO, available from
8319 http://www.linuxdoc.org/docs.html#howto .
8321 If you want to compile this as a module ( = code which can be
8322 inserted in and removed from the running kernel whenever you want),
8323 say M here and read Documentation/modules.txt as well as
8324 Documentation/networking/net-modules.txt. The module will be called
8327 3c507 support (EXPERIMENTAL)
8329 If you have a network (Ethernet) card of this type, say Y and read
8330 the Ethernet-HOWTO, available from
8331 http://www.linuxdoc.org/docs.html#howto .
8333 This driver is also available as a module ( = code which can be
8334 inserted in and removed from the running kernel whenever you want).
8335 The module will be called 3c507.o. If you want to compile it as a
8336 module, say M here and read Documentation/modules.txt as well as
8337 Documentation/networking/net-modules.txt.
8341 If you have a network (Ethernet) card of this type, say Y and read
8342 the Ethernet-HOWTO, available from
8343 http://www.linuxdoc.org/docs.html#howto .
8345 This driver is also available as a module ( = code which can be
8346 inserted in and removed from the running kernel whenever you want).
8347 The module will be called 3c523.o. If you want to compile it as a
8348 module, say M here and read Documentation/modules.txt as well as
8349 Documentation/networking/net-modules.txt.
8353 If you have a network (Ethernet) card of this type, say Y and read
8354 the Ethernet-HOWTO, available from
8355 http://www.linuxdoc.org/docs.html#howto .
8357 This driver is also available as a module ( = code which can be
8358 inserted in and removed from the running kernel whenever you want).
8359 The module will be called 3c527.o. If you want to compile it as a
8360 module, say M here and read Documentation/modules.txt as well as
8361 Documentation/networking/net-modules.txt.
8365 If you have a network (Ethernet) card belonging to the 3Com
8366 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
8367 from http://www.linuxdoc.org/docs.html#howto .
8369 If your card is not working you may need to use the DOS
8370 setup disk to disable Plug & Play mode, and to select the default
8373 If you want to compile this as a module ( = code which can be
8374 inserted in and removed from the running kernel whenever you want),
8375 say M here and read Documentation/modules.txt as well as
8376 Documentation/networking/net-modules.txt. The module will be called
8379 3c515 ISA Fast EtherLink
8381 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
8382 network card, say Y and read the Ethernet-HOWTO, available from
8383 http://www.linuxdoc.org/docs.html#howto .
8385 If you want to compile this as a module ( = code which can be
8386 inserted in and removed from the running kernel whenever you want),
8387 say M here and read Documentation/modules.txt as well as
8388 Documentation/networking/net-modules.txt. The module will be called
8391 3c59x/3c90x/3c575_Cardbus series "Vortex/Boomerang/Cyclone" support
8393 This option enables driver support for a large number of 10mbps and
8394 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
8396 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
8397 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
8398 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
8399 "Tornado" (3c905) PCI
8400 "Hurricane" (3c555/3cSOHO) PCI
8402 If you have such a card, say Y and read the Ethernet-HOWTO, available
8403 from http://www.linuxdoc.org/docs.html#howto . More specific
8404 information is in Documentation/networking/vortex.txt and in the
8405 comments at the beginning of drivers/net/3c59x.c.
8407 If you want to compile this as a module ( = code which can be
8408 inserted in and removed from the running kernel whenever you want),
8409 say M here and read Documentation/modules.txt as well as
8410 Documentation/networking/net-modules.txt.
8414 If your network (Ethernet) card hasn't been mentioned yet and its
8415 bus system (that's the way the cards talks to the other components
8416 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
8417 Make sure you know the name of your card. Read the Ethernet-HOWTO,
8418 available from http://www.linuxdoc.org/docs.html#howto .
8422 Note that the answer to this question doesn't directly affect the
8423 kernel: saying N will just cause this configure script to skip all
8424 the remaining ISA network card questions. If you say Y, you will be
8425 asked for your specific card in the following questions.
8427 Generic ARCnet support
8429 If you have a network card of this type, say Y and check out the
8430 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
8432 You need both this driver, and the driver for the particular ARCnet
8433 chipset of your card. If you don't know, then it's probably a
8434 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
8437 You might also want to have a look at the Ethernet-HOWTO, available
8438 from http://www.linuxdoc.org/docs.html#howto (even though ARCnet
8439 is not really Ethernet).
8441 This driver is also available as a module ( = code which can be
8442 inserted in and removed from the running kernel whenever you want).
8443 The module will be called arcnet.o. If you want to compile it as a
8444 module, say M here and read Documentation/modules.txt as well as
8445 Documentation/networking/net-modules.txt.
8447 Enable arc0e (ARCnet "ether-encap" packet format)
8449 This allows you to use "Ethernet encapsulation" with your ARCnet
8450 card via the virtual arc0e device. You only need arc0e if you want
8451 to talk to nonstandard ARCnet software, specifically,
8452 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
8453 communicate with industry-standard RFC1201 implementations, like the
8454 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
8455 is included automatically as the arc0 device. Please read the
8456 ARCnet documentation in Documentation/networking/arcnet.txt for more
8457 information about using arc0e and arc0s.
8459 Enable old ARCNet packet format (RFC 1051)
8461 This allows you to use RFC1051 with your ARCnet card via the virtual
8462 arc0s device. You only need arc0s if you want to talk to ARCnet
8463 software complying with the "old" standard, specifically, the DOS
8464 arcnet.com packet driver, Amigas running AmiTCP, and some variants
8465 of NetBSD. You do not need to say Y here to communicate with
8466 industry-standard RFC1201 implementations, like the arcether.com
8467 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
8468 automatically as the arc0 device. Please read the ARCnet
8469 documentation in Documentation/networking/arcnet.txt for more
8470 information about using arc0e and arc0s.
8472 ARCnet COM90xx (normal) chipset driver
8473 CONFIG_ARCNET_COM90xx
8474 This is the chipset driver for the standard COM90xx cards. If you
8475 have always used the old ARCnet driver without knowing what type of
8476 card you had, this is probably the one for you.
8478 This driver is also available as a module ( = code which can be
8479 inserted in and removed from the running kernel whenever you want).
8480 The module will be called com90xx.o. If you want to compile it as a
8481 module, say M here and read Documentation/modules.txt as well as
8482 Documentation/networking/net-modules.txt.
8484 ARCnet COM90xx (IO mapped) chipset driver
8485 CONFIG_ARCNET_COM90xxIO
8486 This is the chipset driver for the COM90xx cards, using them in
8487 IO-mapped mode instead of memory-mapped mode. This is slower than
8488 the normal driver. Only use it if your card doesn't support shared
8491 This driver is also available as a module ( = code which can be
8492 inserted in and removed from the running kernel whenever you want).
8493 The module will be called com90io.o. If you want to compile it as a
8494 module, say M here and read Documentation/modules.txt as well as
8495 Documentation/networking/net-modules.txt.
8497 ARCnet COM90xx (RIM I) chipset driver
8499 This is yet another chipset driver for the COM90xx cards, but this
8500 time only using memory-mapped mode, and no IO ports at all. This
8501 driver is completely untested, so if you have one of these cards,
8502 please mail dwmw2@infradead.org, especially if it works!
8504 This driver is also available as a module ( = code which can be
8505 inserted in and removed from the running kernel whenever you
8506 want). The module will be called arc-rimi.o. If you want to compile
8507 it as a module, say M here and read Documentation/modules.txt as
8508 well as Documentation/networking/net-modules.txt.
8510 ARCnet COM20020 chipset driver
8511 CONFIG_ARCNET_COM20020
8512 This is the driver for the new COM20020 chipset. It supports such
8513 things as promiscuous mode, so packet sniffing is possible, and
8514 extra diagnostic information.
8516 This driver is also available as a module ( = code which can be
8517 inserted in and removed from the running kernel whenever you want).
8518 The module will be called com20020.o. If you want to compile it as a
8519 module, say M here and read Documentation/modules.txt as well as
8520 Documentation/networking/net-modules.txt.
8522 Cabletron E21xx support
8524 If you have a network (Ethernet) card of this type, say Y and read
8525 the Ethernet-HOWTO, available from
8526 http://www.linuxdoc.org/docs.html#howto .
8528 This driver is also available as a module ( = code which can be
8529 inserted in and removed from the running kernel whenever you want).
8530 The module will be called e2100.o. If you want to compile it as a
8531 module, say M here and read Documentation/modules.txt as well as
8532 Documentation/networking/net-modules.txt.
8536 Support for CS89x0 chipset based Ethernet cards. If you have a
8537 network (Ethernet) card of this type, say Y and read the
8538 Ethernet-HOWTO, available from
8539 http://www.linuxdoc.org/docs.html#howto as well as
8540 Documentation/networking/cs89x0.txt.
8542 If you want to compile this as a module ( = code which can be
8543 inserted in and removed from the running kernel whenever you want),
8544 say M here and read Documentation/modules.txt as well as
8545 Documentation/networking/net-modules.txt. The module will be called
8550 If you have a network (Ethernet) card of this type, say Y and read
8551 the Ethernet-HOWTO, available from
8552 http://www.linuxdoc.org/docs.html#howto as well as
8553 drivers/net/depca.c.
8555 If you want to compile this as a module ( = code which can be
8556 inserted in and removed from the running kernel whenever you want),
8557 say M here and read Documentation/modules.txt as well as
8558 Documentation/networking/net-modules.txt. The module will be called
8561 EtherWorks 3 support
8563 This driver supports the DE203, DE204 and DE205 network (Ethernet)
8564 cards. If this is for you, say Y and read
8565 Documentation/networking/ewrk3.txt in the kernel source as well as
8566 the Ethernet-HOWTO, available from
8567 http://www.linuxdoc.org/docs.html#howto .
8569 If you want to compile this as a module ( = code which can be
8570 inserted in and removed from the running kernel whenever you want),
8571 say M here and read Documentation/modules.txt as well as
8572 Documentation/networking/net-modules.txt. The module will be called
8577 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
8578 is for you, read the Ethernet-HOWTO, available from
8579 http://www.linuxdoc.org/docs.html#howto .
8581 If you want to compile this as a module ( = code which can be
8582 inserted in and removed from the running kernel whenever you want),
8583 say M here and read Documentation/modules.txt as well as
8584 Documentation/networking/net-modules.txt. The module will be called
8589 If you have a network (Ethernet) card of this type, say Y and read
8590 the Ethernet-HOWTO, available from
8591 http://www.linuxdoc.org/docs.html#howto .
8593 This driver is also available as a module ( = code which can be
8594 inserted in and removed from the running kernel whenever you want).
8595 If you want to compile it as a module, say M here and read
8596 Documentation/modules.txt as well as
8597 Documentation/networking/net-modules.txt. The module will be called
8600 FMV-181/182/183/184 support
8602 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
8603 say Y and read the Ethernet-HOWTO, available from
8604 http://www.linuxdoc.org/docs.html#howto .
8606 If you use an FMV-183 or FMV-184 and it is not working, you may need
8607 to disable Plug & Play mode of the card.
8609 This driver is also available as a module ( = code which can be
8610 inserted in and removed from the running kernel whenever you want).
8611 The module will be called fmv18x.o. If you want to compile it as a
8612 module, say M here and read Documentation/modules.txt as well as
8613 Documentation/networking/net-modules.txt.
8615 EtherExpress PRO support
8617 If you have a network (Ethernet) card of this type, say Y. This
8618 driver supports intel i82595{FX,TX} based boards. Note however
8619 that the EtherExpress PRO/100 Ethernet card has its own separate
8620 driver. Please read the Ethernet-HOWTO, available from
8621 http://www.linuxdoc.org/docs.html#howto .
8623 This driver is also available as a module ( = code which can be
8624 inserted in and removed from the running kernel whenever you want).
8625 The module will be called eepro.o. If you want to compile it as a
8626 module, say M here and read Documentation/modules.txt as well as
8627 Documentation/networking/net-modules.txt.
8629 EtherExpress support
8631 If you have an EtherExpress16 network (Ethernet) card, say Y and
8632 read the Ethernet-HOWTO, available from
8633 http://www.linuxdoc.org/docs.html#howto . Note that the Intel
8634 EtherExpress16 card used to be regarded as a very poor choice
8635 because the driver was very unreliable. We now have a new driver
8636 that should do better.
8638 If you want to compile this driver as a module ( = code which can be
8639 inserted in and removed from the running kernel whenever you want),
8640 say M here and read Documentation/modules.txt as well as
8641 Documentation/networking/net-modules.txt. The module will be called
8644 HP PCLAN+ (27247B and 27252A) support
8646 If you have a network (Ethernet) card of this type, say Y and read
8647 the Ethernet-HOWTO, available from
8648 http://www.linuxdoc.org/docs.html#howto .
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 hp-plus.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 HP PCLAN (27245 and other 27xxx series) support
8658 If you have a network (Ethernet) card of this type, say Y and read
8659 the Ethernet-HOWTO, available from
8660 http://www.linuxdoc.org/docs.html#howto .
8662 This driver is also available as a module ( = code which can be
8663 inserted in and removed from the running kernel whenever you want).
8664 The module will be called hp.o. If you want to compile it as a
8665 module, say M here and read Documentation/modules.txt as well as
8666 Documentation/networking/net-modules.txt.
8668 HP 10/100VG PCLAN (ISA, EISA, PCI) support
8670 If you have a network (Ethernet) card of this type, say Y and read
8671 the Ethernet-HOWTO, available from
8672 http://www.linuxdoc.org/docs.html#howto .
8674 If you want to compile this as a module ( = code which can be
8675 inserted in and removed from the running kernel whenever you want),
8676 say M here and read Documentation/modules.txt as well as
8677 Documentation/networking/net-modules.txt. The module will be called
8680 NE2000/NE1000 support
8682 If you have a network (Ethernet) card of this type, say Y and read
8683 the Ethernet-HOWTO, available from
8684 http://www.linuxdoc.org/docs.html#howto . Many Ethernet cards
8685 without a specific driver are compatible with NE2000.
8687 If you have a PCI NE2000 card however, say N here and Y to "PCI
8688 NE2000 support", above. If you have a NE2000 card and are running on
8689 an MCA system (a bus system used on some IBM PS/2 computers and
8690 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
8693 This driver is also available as a module ( = code which can be
8694 inserted in and removed from the running kernel whenever you want).
8695 The module will be called ne.o. If you want to compile it as a
8696 module, say M here and read Documentation/modules.txt as well as
8697 Documentation/networking/net-modules.txt.
8699 National Semiconductor DP83810 series PCI Ethernet support
8701 This driver is for the National Semiconductor DP83810 series,
8702 including the 83815 chip.
8703 More specific information and updates are available from
8704 http://www.scyld.com/network/natsemi.html
8708 If you have a network (Ethernet) card of this type, say Y and read
8709 the Ethernet-HOWTO, available from
8710 http://www.linuxdoc.org/docs.html#howto .
8712 NE/2 (ne2000 MCA version) support
8714 If you have a network (Ethernet) card of this type, say Y and read
8715 the Ethernet-HOWTO, available from
8716 http://www.linuxdoc.org/docs.html#howto .
8718 This driver is also available as a module ( = code which can be
8719 inserted in and removed from the running kernel whenever you want).
8720 The module will be called ne2.o. If you want to compile it as a
8721 module, say M here and read Documentation/modules.txt as well as
8722 Documentation/networking/net-modules.txt.
8726 These are Micro Channel ethernet adapters. You need to say Y to "MCA
8727 support" in order to use this driver. Supported cards are the SKnet
8728 Junior MC2 and the SKnet MC2(+). The driver automatically
8729 distinguishes between the two cards. Note that using multiple boards
8730 of different type hasn't been tested with this driver. Say Y if you
8731 have one of these ethernet adapters.
8733 This driver is also available as a module ( = code which can be
8734 inserted in and removed from the running kernel whenever you want).
8735 The module is called sk_mca.o. If you want to compile it as a
8736 module, say M here and read Documentation/modules.txt as well as
8737 Documentation/networking/net-modules.txt.
8739 IBM LAN Adapter/A support
8741 This is a Micro Channel ethernet adapter. You need to set CONFIG_MCA
8742 to use this driver. It is both available as an in-kernel driver and
8743 as a module ( = code which can be inserted in and removed from the
8744 running kernel whenever you want). If you want to compile it as a module,
8745 say M here and read Documentation/modules.txt as well as
8746 Documentation/networking/net-modules.txt. If you plan to use more than
8747 one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
8748 available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. The only
8749 currently supported card is the IBM LAN Adapter/A for Ethernet. It will
8750 both support 16K and 32K memory windows, however a 32K window gives
8751 a better security against packet losses. Usage of multiple boards with
8752 this driver should be possible, but has not been tested up to now due
8753 to lack of hardware.
8755 EISA, VLB, PCI and on board controllers
8757 This is another class of network cards which attach directly to the
8758 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
8759 available from http://www.linuxdoc.org/docs.html#howto .
8761 Note that the answer to this question doesn't directly affect the
8762 kernel: saying N will just cause this configure script to skip all
8763 the questions about this class of network cards. If you say Y, you
8764 will be asked for your specific card in the following questions. If
8765 you are unsure, say Y.
8767 AMD PCnet32 (VLB and PCI) support
8769 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
8770 answer Y here and read the Ethernet-HOWTO, available from
8771 http://www.linuxdoc.org/docs.html#howto .
8773 This driver is also available as a module ( = code which can be
8774 inserted in and removed from the running kernel whenever you want).
8775 The module will be called pcnet32.o. If you want to compile it as a
8776 module, say M here and read Documentation/modules.txt as well as
8777 Documentation/networking/net-modules.txt.
8779 Ansel Communications EISA 3200 support
8781 If you have a network (Ethernet) card of this type, say Y and read
8782 the Ethernet-HOWTO, available from
8783 http://www.linuxdoc.org/docs.html#howto .
8785 This driver is also available as a module ( = code which can be
8786 inserted in and removed from the running kernel whenever you want).
8787 The module will be called ac3200.o. If you want to compile it as a
8788 module, say M here and read Documentation/modules.txt as well as
8789 Documentation/networking/net-modules.txt.
8791 Mylex EISA LNE390A/LNE390B support (EXPERIMENTAL)
8793 If you have a network (Ethernet) card of this type, say Y and read
8794 the Ethernet-HOWTO, available from
8795 http://www.linuxdoc.org/docs.html#howto .
8797 This driver is also available as a module ( = code which can be
8798 inserted in and removed from the running kernel whenever you want).
8799 The module will be called lne390.o. If you want to compile it as a
8800 module, say M here and read Documentation/modules.txt as well as
8801 Documentation/networking/net-modules.txt.
8803 Novell/Eagle/Microdyne NE3210 EISA support
8805 If you have a network (Ethernet) card of this type, say Y and read
8806 the Ethernet-HOWTO, available from
8807 http://www.linuxdoc.org/docs.html#howto . Note that this driver
8808 will NOT WORK for NE3200 cards as they are completely different.
8810 This driver is also available as a module ( = code which can be
8811 inserted in and removed from the running kernel whenever you want).
8812 The module will be called ne3210.o. If you want to compile it as a
8813 module, say M here and read Documentation/modules.txt as well as
8814 Documentation/networking/net-modules.txt.
8816 Apricot Xen-II on board Ethernet
8818 If you have a network (Ethernet) controller of this type, say Y and
8819 read the Ethernet-HOWTO, available from
8820 http://www.linuxdoc.org/docs.html#howto .
8822 If you want to compile this as a module ( = code which can be
8823 inserted in and removed from the running kernel whenever you want),
8824 say M here and read Documentation/modules.txt as well as
8825 Documentation/networking/net-modules.txt. The module will be called
8828 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
8830 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
8831 These include the DE425, DE434, DE435, DE450 and DE500 models. If
8832 you have a network card of this type, say Y and read the
8833 Ethernet-HOWTO, available from
8834 http://www.linuxdoc.org/docs.html#howto . More specific
8835 information is contained in Documentation/networking/de4x5.txt.
8837 This driver is also available as a module ( = code which can be
8838 inserted in and removed from the running kernel whenever you want).
8839 The module will be called de4x5.o. If you want to compile it as a
8840 module, say M here and read Documentation/modules.txt as well as
8841 Documentation/networking/net-modules.txt.
8843 DECchip Tulip (dc21x4x) PCI support
8845 This driver is developed for the SMC EtherPower series Ethernet
8846 cards and also works with cards based on the DECchip
8847 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
8848 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
8849 (smc9332dst), you can also try the driver for "Generic DECchip"
8850 cards, above. However, most people with a network card of this type
8851 will say Y here.) Do read the Ethernet-HOWTO, available from
8852 http://www.linuxdoc.org/docs.html#howto . More specific
8853 information is contained in Documentation/networking/tulip.txt.
8855 This driver is also available as a module ( = code which can be
8856 inserted in and removed from the running kernel whenever you want).
8857 The module will be called tulip.o. If you want to compile it as a
8858 module, say M here and read Documentation/modules.txt as well as
8859 Documentation/networking/net-modules.txt.
8861 Digi Intl. RightSwitch support
8863 This is support for the Digi International RightSwitch series of
8864 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
8865 models. If you have a network card of this type, say Y and read the
8866 Ethernet-HOWTO, available from
8867 http://www.linuxdoc.org/docs.html#howto . More specific
8868 information is contained in Documentation/networking/dgrs.txt.
8870 This driver is also available as a module ( = code which can be
8871 inserted in and removed from the running kernel whenever you want).
8872 The module will be called dgrs.o. If you want to compile it as a
8873 module, say M here and read Documentation/modules.txt as well as
8874 Documentation/networking/net-modules.txt.
8876 EtherExpress PRO/100 support
8878 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
8879 card, say Y and read the Ethernet-HOWTO, available from
8880 http://www.linuxdoc.org/docs.html#howto .
8882 This driver is also available as a module ( = code which can be
8883 inserted in and removed from the running kernel whenever you want).
8884 The module will be called eepro100.o. If you want to compile it as a
8885 module, say M here and read Documentation/modules.txt as well as
8886 Documentation/networking/net-modules.txt.
8888 Enable Power Management (EXPERIMENTAL)
8890 Many Intel EtherExpress PRO/100 PCI network cards are capable
8891 of providing power management capabilities. To make use of these
8892 capabilities, say Y.
8894 WARNING: This option is intended for kernel developers and testers.
8895 It is still very experimental, with some people reporting complete
8898 It is recommended to say N here.
8900 ICL EtherTeam 16i/32 support (EXPERIMENTAL)
8902 If you have a network (Ethernet) card of this type, say Y and read
8903 the Ethernet-HOWTO, available from
8904 http://www.linuxdoc.org/docs.html#howto .
8906 This driver is also available as a module ( = code which can be
8907 inserted in and removed from the running kernel whenever you want).
8908 The module will be called eth16i.o. If you want to compile it as a
8909 module, say M here and read Documentation/modules.txt as well as
8910 Documentation/networking/net-modules.txt.
8912 TI ThunderLAN support (EXPERIMENTAL)
8914 If you have a PCI Ethernet network card based on the ThunderLAN chip
8915 which is supported by this driver, say Y and read the
8916 Ethernet-HOWTO, available from
8917 http://www.linuxdoc.org/docs.html#howto .
8919 Devices currently supported by this driver are Compaq Netelligent,
8920 Compaq NetFlex and Olicom cards. Please read the file
8921 Documentation/networking/tlan.txt for more details.
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 tlan.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 Please email feedback to torben.mathiasen@compaq.com.
8933 If you have a VIA "rhine" based network card (Rhine-I (3043) or
8934 Rhine-2 (VT86c100A)), say Y here.
8936 This driver is also available as a module ( = code which can be
8937 inserted in and removed from the running kernel whenever you want).
8938 The module will be called via-rhine.o. If you want to compile it as
8939 a module, say M here and read Documentation/modules.txt as well as
8940 Documentation/networking/net-modules.txt.
8942 PCI DM9102(A)/DM9132/DM9801 support
8944 This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
8945 Davicom ( http://www.davicom.com.tw ). If you have such a network
8946 (Ethernet) card, say Y. Some information is contained in the file
8947 Documentation/networking/dmfe.txt.
8949 This driver is also available as a module ( = code which can be
8950 inserted in and removed from the running kernel whenever you want).
8951 The module will be called dmfe.o. If you want to compile it as a
8952 module, say M here and read Documentation/modules.txt as well as
8953 Documentation/networking/net-modules.txt.
8955 Racal-Interlan EISA ES3210 support (EXPERIMENTAL)
8957 If you have a network (Ethernet) card of this type, say Y and read
8958 the Ethernet-HOWTO, available from
8959 http://www.linuxdoc.org/docs.html#howto .
8961 This driver is also available as a module ( = code which can be
8962 inserted in and removed from the running kernel whenever you want).
8963 The module will be called es3210.o. If you want to compile it as a
8964 module, say M here and read Documentation/modules.txt as well as
8965 Documentation/networking/net-modules.txt.
8967 SMC EtherPower II (EXPERIMENTAL)
8969 If you have an SMC EtherPower II 9432 PCI Ethernet network card
8970 which is based on the SMC83c170, say Y and read the Ethernet-HOWTO,
8971 available from http://www.linuxdoc.org/docs.html#howto .
8973 This driver is also available as a module ( = code which can be
8974 inserted in and removed from the running kernel whenever you want).
8975 The module will be called epic100.o. If you want to compile it as a
8976 module, say M here and read Documentation/modules.txt as well as
8977 Documentation/networking/net-modules.txt.
8979 SGI Seeq ethernet controller support
8981 Say Y here if you have an Seeq based Ethernet network card. This is
8982 used in many Silicon Graphics machines.
8984 Zenith Z-Note support (EXPERIMENTAL)
8986 The Zenith Z-Note notebook computer has a built-in network
8987 (Ethernet) card, and this is the Linux driver for it. Note that the
8988 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
8989 by this driver. Read the Ethernet-HOWTO, available from
8990 http://www.linuxdoc.org/docs.html#howto .
8992 Pocket and portable adapters
8994 Cute little network (Ethernet) devices which attach to the parallel
8995 port ("pocket adapters"), commonly used with laptops. If you have
8996 one of those, say Y and read the Ethernet-HOWTO, available from
8997 http://www.linuxdoc.org/docs.html#howto .
8999 If you want to plug a network (or some other) card into the PCMCIA
9000 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
9001 credit card size extension cards used by all modern laptops), you
9002 need the pcmcia-cs package (location contained in the file
9003 Documentation/Changes) and you can say N here.
9005 Laptop users should read the Linux Laptop home page at
9006 http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
9008 Note that the answer to this question doesn't directly affect the
9009 kernel: saying N will just cause this configure script to skip all
9010 the questions about this class of network devices. If you say Y, you
9011 will be asked for your specific device in the following questions.
9013 AT-LAN-TEC/RealTek pocket adapter support
9015 This is a network (Ethernet) device which attaches to your parallel
9016 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
9017 available from http://www.linuxdoc.org/docs.html#howto , if you
9018 want to use this. If you intend to use this driver, you should have
9019 said N to the "Parallel printer support", because the two drivers
9020 don't like each other.
9022 If you want to compile this driver as a module however ( = code
9023 which can be inserted in and removed from the running kernel
9024 whenever you want), say M here and read Documentation/modules.txt.
9025 The module will be called atp.o.
9027 D-Link DE600 pocket adapter support
9029 This is a network (Ethernet) device which attaches to your parallel
9030 port. Read Documentation/networking/DLINK.txt as well as the
9031 Ethernet-HOWTO, available from
9032 http://www.linuxdoc.org/docs.html#howto , if you want to use
9033 this. It is possible to have several devices share a single parallel
9034 port and it is safe to compile the corresponding drivers into the
9037 If you want to compile this driver as a module however ( = code
9038 which can be inserted in and removed from the running kernel
9039 whenever you want), say M here and read Documentation/modules.txt.
9040 The module will be called de600.o.
9042 D-Link DE620 pocket adapter support
9044 This is a network (Ethernet) device which attaches to your parallel
9045 port. Read Documentation/networking/DLINK.txt as well as the
9046 Ethernet-HOWTO, available from
9047 http://www.linuxdoc.org/docs.html#howto , if you want to use
9048 this. It is possible to have several devices share a single parallel
9049 port and it is safe to compile the corresponding drivers into the
9052 If you want to compile this driver as a module however ( = code
9053 which can be inserted in and removed from the running kernel
9054 whenever you want), say M here and read Documentation/modules.txt.
9055 The module will be called de620.o.
9057 Token Ring driver support
9059 Token Ring is IBM's way of communication on a local network; the
9060 rest of the world uses Ethernet. To participate on a Token Ring
9061 network, you need a special Token ring network card. If you are
9062 connected to such a Token Ring network and want to use your Token
9063 Ring card under Linux, say Y here and to the driver for your
9064 particular card below and read the Token-Ring mini-HOWTO, available
9065 from http://www.linuxdoc.org/docs.html#howto . Most people can
9068 IBM Tropic chipset based adapter support
9070 This is support for all IBM Token Ring cards that don't use DMA. If
9071 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
9072 available from http://www.linuxdoc.org/docs.html#howto .
9074 Warning: this driver will almost definitely fail if more than one
9075 active Token Ring card is present.
9077 This driver is also available as a module ( = code which can be
9078 inserted in and removed from the running kernel whenever you want).
9079 The module will be called ibmtr.o. If you want to compile it as a
9080 module, say M here and read Documentation/modules.txt.
9082 IBM Olympic chipset PCI adapter support
9084 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
9085 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
9086 Wake On Lan, and PCI 100/16/4 adapters.
9088 If you have such an adapter, say Y and read the Token-Ring
9089 mini-HOWTO, available from
9090 http://www.linuxdoc.org/docs.html#howto .
9092 This driver is also available as a module ( = code which can be
9093 inserted in and removed from the running kernel whenever you want).
9094 The module will will be called olympic.o. If you want to compile it
9095 as a module, say M here and read Documentation/modules.txt.
9097 Also read the file Documentation/networking/olympic.txt or check the
9098 Linux Token Ring Project site for the latest information at
9099 http://www.linuxtr.net .
9101 IBM Lanstreamer chipset PCI adapter support
9103 This is support for IBM Lanstreamer PCI Token Ring Cards.
9105 If you have such an adapter, say Y and read the Token-Ring
9106 mini-HOWTO available via FTP (user:anonymous) from
9107 ftp://metalab.unc/edu/pub/Linux/docs/HOWTO.
9109 This driver is also available as a modules ( = code which can be
9110 inserted in and removed from the running kernel whenever you want).
9111 The modules will be called lanstreamer.o. If you want to compile it
9112 as a module, say M here and read Documentation/modules.txt.
9114 Generic TMS380 Token Ring ISA/PCI/MCA/EISA adapter support
9116 This driver provides generic support for token ring adapters
9117 based on the Texas Instruments TMS380 series chipsets. This
9118 includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect
9119 TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591),
9120 Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and several
9121 Madge adapters. If you say Y here, you will be asked to select
9122 which cards to support below. If you're using modules, each
9123 class of card will be supported by a separate module.
9125 If you have such an adapter and would like to use it, say Y and
9126 read the Token-Ring mini-HOWTO, available from
9127 http://www.linuxdoc.org/docs.html#howto .
9129 Also read the file Documentation/networking/tms380tr.txt or
9130 check http://www.auk.cx/tms380tr/ .
9132 This driver is also available as a module ( = code which can be
9133 inserted in and removed from the running kernel whenever you want).
9134 The module will will be called tms380tr.o. If you want to compile it
9135 as a module, say M here and read Documentation/modules.txt.
9137 Generic TMS380 PCI support
9139 This tms380 module supports generic TMS380-based PCI cards.
9141 These cards are known to work:
9142 - Compaq 4/16 TR PCI
9143 - SysKonnect TR4/16 PCI (SK-4590/SK-4591)
9144 - Thomas-Conrad TC4048 PCI 4/16
9145 - 3Com Token Link Velocity
9147 This driver is available as a module ( = code which can be
9148 inserted in and removed from the running kernel whenever you want).
9149 The module will will be called tmspci.o. If you want to compile it
9150 as a module, say M here and read Documentation/modules.txt.
9152 Madge Smart 16/4 PCI Mk2 support
9154 This tms380 module supports the Madge Smart 16/4 PCI Mk2
9157 This driver is available as a module ( = code which can be
9158 inserted in and removed from the running kernel whenever you want).
9159 The module will will be called abyss.o. If you want to compile it
9160 as a module, say M here and read Documentation/modules.txt.
9162 Madge Smart 16/4 Ringode MicroChannel
9164 This tms380 module supports the Madge Smart 16/4 MC16 and MC32
9165 MicroChannel adapters.
9167 This driver is available as a module ( = code which can be
9168 inserted in and removed from the running kernel whenever you want).
9169 The module will will be called madgemc.o. If you want to compile it
9170 as a module, say M here and read Documentation/modules.txt.
9172 SMC ISA TokenRing adapter support
9174 This is support for the ISA and MCA SMC Token Ring cards,
9175 specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A
9178 If you have such an adapter and would like to use it, say Y or M and
9179 read the Token-Ring mini-HOWTO, available from
9180 http://www.linuxdoc.org/docs.html#howto and the file
9181 Documentation/networking/smctr.txt.
9183 This driver is also available as a module ( = code which can be
9184 inserted in and removed from the running kernel whenever you want).
9185 The module will will be called smctr.o. If you want to compile it
9186 as a module, say M here and read Documentation/modules.txt.
9188 Sun Happy Meal 10/100baseT support
9190 This driver supports the "hme" interface present on most Ultra
9191 systems and as an option on older Sbus systems. This driver supports
9192 both PCI and Sbus devices. This driver also supports the "qfe" quad
9193 100baseT device available in both PCI and Sbus configurations.
9195 This support is also available as a module called sunhme.o ( = code
9196 which can be inserted in and removed from the running kernel
9197 whenever you want). If you want to compile it as a module, say M
9198 here and read Documentation/modules.txt.
9202 This driver supports the "le" interface present on all 32-bit Sparc
9203 systems, on some older Ultra systems and as an Sbus option.
9205 This support is also available as a module called sunlance.o ( =
9206 code which can be inserted in and removed from the running kernel
9207 whenever you want). If you want to compile it as a module, say M
9208 here and read Documentation/modules.txt.
9210 Sun BigMAC 10/100baseT support (EXPERIMENTAL)
9212 This driver supports the "be" interface available as an Sbus option.
9213 This is Sun's older 100baseT ethernet device.
9215 This support is also available as a module called sunbmac.o ( = code
9216 which can be inserted in and removed from the running kernel
9217 whenever you want). If you want to compile it as a module, say M
9218 here and read Documentation/modules.txt.
9220 Sun QuadEthernet support
9222 This driver supports the "qe" 10baseT ethernet device, available as
9223 an Sbus option. Note that this is not the same as Quad FastEthernet
9224 "qfe" which is supported by the Happy Meal driver instead.
9226 This support is also available as a module called sunqe.o ( = code
9227 which can be inserted in and removed from the running kernel
9228 whenever you want). If you want to compile it as a module, say M
9229 here and read Documentation/modules.txt.
9231 Traffic Shaper (EXPERIMENTAL)
9233 The traffic shaper is a virtual network device that allows you to
9234 limit the rate of outgoing data flow over some other network device.
9235 The traffic that you want to slow down can then be routed through
9236 these virtual devices. See Documentation/networking/shaper.txt for
9239 An alternative to this traffic shaper is the experimental
9240 Class-Based Queueing (CBQ) scheduling support which you get if you
9241 say Y to "QoS and/or fair queueing" above.
9243 To set up and configure shaper devices, you need the shapecfg
9244 program, available from ftp://shadow.cabi.net/pub/Linux in the
9247 This driver is also available as a module ( = code which can be
9248 inserted in and removed from the running kernel whenever you want).
9249 The module will be called shaper.o. If you want to compile it as a
9250 module, say M here and read Documentation/modules.txt. If unsure,
9255 Fiber Distributed Data Interface is a high speed local area network
9256 design; essentially a replacement for high speed Ethernet. FDDI can
9257 run over copper or fiber. If you are connected to such a network and
9258 want a driver for the FDDI card in your computer, say Y here (and
9259 then also Y to the driver for your FDDI card, below). Most people
9262 Digital DEFEA and DEFPA adapter support
9264 This is support for the DIGITAL series of EISA (DEFEA) and PCI
9265 (DEFPA) controllers which can connect you to a local FDDI network.
9267 SysKonnect FDDI PCI support
9269 Say Y here if you have a SysKonnect FDDI PCI adapter.
9270 The following adapters are supported by this driver:
9271 - SK-5521 (SK-NET FDDI-UP)
9272 - SK-5522 (SK-NET FDDI-UP DAS)
9273 - SK-5541 (SK-NET FDDI-FP)
9274 - SK-5543 (SK-NET FDDI-LP)
9275 - SK-5544 (SK-NET FDDI-LP DAS)
9276 - SK-5821 (SK-NET FDDI-UP64)
9277 - SK-5822 (SK-NET FDDI-UP64 DAS)
9278 - SK-5841 (SK-NET FDDI-FP64)
9279 - SK-5843 (SK-NET FDDI-LP64)
9280 - SK-5844 (SK-NET FDDI-LP64 DAS)
9281 - Netelligent 100 FDDI DAS Fibre SC
9282 - Netelligent 100 FDDI SAS Fibre SC
9283 - Netelligent 100 FDDI DAS UTP
9284 - Netelligent 100 FDDI SAS UTP
9285 - Netelligent 100 FDDI SAS Fibre MIC
9287 Read Documentation/networking/skfp.txt for information about
9290 Questions concerning this driver can be addressed to:
9293 If you want to compile this driver as a module ( = code which can be
9294 inserted in and removed from the running kernel whenever you want),
9295 say M here and read Documentation/modules.txt. This is recommended.
9296 The module will be called skfp.o.
9298 HIgh Performance Parallel Interface support (EXPERIMENTAL)
9300 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
9301 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
9302 can run over copper (25m) or fiber (300m on multi-mode or 10km on
9303 single-mode). HIPPI networks are commonly used for clusters and to
9304 connect to super computers. If you are connected to a HIPPI network
9305 and have a HIPPI network card in your computer that you want to use
9306 under Linux, say Y here (you must also remember to enable the driver
9307 for your HIPPI card below). Most people will say N here.
9309 Essential RoadRunner HIPPI PCI adapter support
9311 Say Y here if this is your PCI HIPPI network card.
9313 This driver is also available as a module ( = code which can be
9314 inserted in and removed from the running kernel whenever you want).
9315 The module will be called rrunner.o. If you want to compile it as
9316 a module, say M here and read Documentation/modules.txt. If unsure,
9319 Use large TX/RX rings
9320 CONFIG_ROADRUNNER_LARGE_RINGS
9321 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
9322 of additional memory to allow for fastest operation, both for
9323 transmitting and receiving. This memory cannot be used by any other
9324 kernel code or by user space programs. Say Y here only if you have
9329 If you have an Acorn system with one of these (AKA25) network cards,
9330 you should say Y to this option if you wish to use it with Linux.
9332 Acorn/ANT Ether3 card
9334 If you have an Acorn system with one of these network cards, you
9335 should say Y to this option if you wish to use it with Linux.
9339 If you have an Acorn system with one of these network cards, you
9340 should say Y to this option if you wish to use it with Linux.
9342 EBSA-110 Ethernet interface
9343 CONFIG_ARM_AM79C961A
9344 If you wish to compile a kernel for the EBSA-110, then you should
9345 always answer Y to this.
9347 Support CDROM drives that are not SCSI or IDE/ATAPI
9348 CONFIG_CD_NO_IDESCSI
9349 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
9350 here, otherwise N. Read the CDROM-HOWTO, available from
9351 http://www.linuxdoc.org/docs.html#howto .
9353 Note that the answer to this question doesn't directly affect the
9354 kernel: saying N will just cause this configure script to skip all
9355 the questions about these CDROM drives. If you are unsure what you
9356 have, say Y and find out whether you have one of the following
9359 For each of these drivers, a file Documentation/cdrom/<driver_name>
9360 exists. Especially in cases where you do not know exactly which kind
9361 of drive you have you should read there. Most of these drivers use a
9362 file drivers/cdrom/<driver_name>.h where you can define your
9363 interface parameters and switch some internal goodies.
9365 All these CDROM drivers are also usable as a module ( = code which
9366 can be inserted in and removed from the running kernel whenever you
9367 want). If you want to compile them as module, say M instead of Y and
9368 read Documentation/modules.txt.
9370 If you want to use any of these CDROM drivers, you also have to
9371 answer Y or M to "ISO 9660 CDROM file system support" below (this
9372 answer will get "defaulted" for you if you enable any of the Linux
9375 Sony CDU31A/CDU33A CDROM support
9377 These CDROM drives have a spring-pop-out caddyless drawer, and a
9378 rectangular green LED centered beneath it. NOTE: these CDROM drives
9379 will not be auto detected by the kernel at boot time; you have to
9380 provide the interface address as an option to the kernel at boot
9381 time as described in Documentation/cdrom/cdu31a or fill in your
9382 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
9383 see the documentation of your boot loader (lilo or loadlin) about
9384 how to pass options to the kernel.
9386 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9387 file system support" below, because that's the file system used on
9390 This driver is also available as a module ( = code which can be
9391 inserted in and removed from the running kernel whenever you want).
9392 The module will be called cdu31a.o. If you want to compile it as a
9393 module, say M here and read Documentation/modules.txt.
9395 Standard Mitsumi [no XA/Multisession] CDROM support
9397 This is the older of the two drivers for the older Mitsumi models
9398 LU-005, FX-001 and FX-001D. This is not the right driver for the
9399 FX-001DE and the triple or quad speed models (all these are
9400 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
9402 With the old LU-005 model, the whole drive chassis slides out for cd
9403 insertion. The FX-xxx models use a motorized tray type mechanism.
9404 Note that this driver does not support XA or MultiSession CDs
9405 (PhotoCDs). There is a new driver (next question) which can do
9406 this. If you want that one, say N here.
9408 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9409 file system support" below, because that's the file system used on
9412 This driver is also available as a module ( = code which can be
9413 inserted in and removed from the running kernel whenever you want).
9414 The module will be called mcd.o. If you want to compile it as a
9415 module, say M here and read Documentation/modules.txt.
9417 IRQ channel for Mitsumi CD-ROM
9419 This allows you to specify the default value of the IRQ used by the
9420 driver. This setting can be overridden by passing the "mcd="
9421 parameter to the kernel at boot time (or at module load time if you
9422 said M to "Standard Mitsumi CDROM support").
9424 I/O base address for Mitsumi CD-ROM
9426 This allows you to specify the default value of the I/O base address
9427 used by the driver. This setting can be overridden by passing the
9428 "mcd=" parameter to the kernel at boot time (or at module load time
9429 if you said M to "Standard Mitsumi CDROM support").
9431 Mitsumi [XA/MultiSession] support
9433 Use this driver if you want to be able to read XA or MultiSession
9434 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
9435 FX-001 or FX-001D CDROM drive. In addition, this driver uses much
9436 less kernel memory than the old one, if that is a concern. This
9437 driver is able to support more than one drive, but each drive needs
9438 a separate interface card. Please read the file
9439 Documentation/cdrom/mcdx.
9441 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9442 file system support" below, because that's the file system used on
9445 This driver is also available as a module ( = code which can be
9446 inserted in and removed from the running kernel whenever you want).
9447 The module will be called mcdx.o. If you want to compile it as a
9448 module, say M here and read Documentation/modules.txt.
9450 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
9452 This driver supports most of the drives which use the Panasonic or
9453 Sound Blaster interface. Please read the file
9454 Documentation/cdrom/sbpcd.
9456 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
9457 (sometimes labeled "Creative"), the Creative Labs CD200, the
9458 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
9459 model), the TEAC CD-55A fall under this category. Some other
9460 "electrically compatible" drives (Vertos, Genoa, some Funai models)
9461 are currently not supported; for the Sanyo H94A drive currently a
9462 separate driver (asked later) is responsible. Most drives have a
9463 uniquely shaped faceplate, with a caddyless motorized drawer, but
9464 without external brand markings. The older CR-52x drives have a
9465 caddy and manual loading/eject, but still no external markings. The
9466 driver is able to do an extended auto-probing for interface
9467 addresses and drive types; this can help to find facts in cases you
9468 are not sure, but can consume some time during the boot process if
9469 none of the supported drives gets found. Once your drive got found,
9470 you should enter the reported parameters into drivers/cdrom/sbpcd.h
9471 and set "DISTRIBUTION 0" there.
9473 This driver can support up to four CDROM controller cards, and each
9474 card can support up to four CDROM drives; if you say Y here, you
9475 will be asked how many controller cards you have. If compiled as a
9476 module, only one controller card (but with up to four drives) is
9479 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9480 file system support" below, because that's the file system used on
9483 This driver is also available as a module ( = code which can be
9484 inserted in and removed from the running kernel whenever you want).
9485 The module will be called sbpcd.o. If you want to compile it as a
9486 module, say M here and read Documentation/modules.txt.
9488 Matsushita/Panasonic, ... second CDROM controller support
9490 Say Y here only if you have two CDROM controller cards of this type
9491 (usually only if you have more than four drives). You should enter
9492 the parameters for the second, third and fourth interface card into
9493 include/linux/sbpcd.h before compiling the new kernel. Read
9494 the file Documentation/cdrom/sbpcd.
9496 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
9498 This is your driver if you have an Aztech CDA268-01A, Orchid
9499 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
9500 CR540 CDROM drive. This driver -- just like all these CDROM drivers
9501 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
9502 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
9504 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9505 file system support" below, because that's the file system used on
9508 This driver is also available as a module ( = code which can be
9509 inserted in and removed from the running kernel whenever you want).
9510 The module will be called aztcd.o. If you want to compile it as a
9511 module, say M here and read Documentation/modules.txt.
9513 Sony CDU535 CDROM support
9515 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
9516 drives. Please read the file Documentation/cdrom/sonycd535.
9518 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9519 file system support" below, because that's the file system used on
9522 This driver is also available as a module ( = code which can be
9523 inserted in and removed from the running kernel whenever you want).
9524 The module will be called sonycd535.o. If you want to compile it as
9525 a module, say M here and read Documentation/modules.txt.
9527 Goldstar R420 CDROM support
9529 If this is your CDROM drive, say Y here. As described in the file
9530 Documentation/cdrom/gscd, you might have to change a setting
9531 in the file drivers/cdrom/gscd.h before compiling the
9532 kernel. Please read the file Documentation/cdrom/gscd.
9534 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9535 file system support" below, because that's the file system used on
9538 This driver is also available as a module ( = code which can be
9539 inserted in and removed from the running kernel whenever you want).
9540 The module will be called gscd.o. If you want to compile it as a
9541 module, say M here and read Documentation/modules.txt.
9543 Philips/LMS CM206 CDROM support
9545 If you have a Philips/LMS CDROM drive cm206 in combination with a
9546 cm260 host adapter card, say Y here. Please also read the file
9547 Documentation/cdrom/cm206.
9549 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9550 file system support" below, because that's the file system used on
9553 This driver is also available as a module ( = code which can be
9554 inserted in and removed from the running kernel whenever you want).
9555 The module will be called cm206.o. If you want to compile it as a
9556 module, say M here and read Documentation/modules.txt.
9558 Optics Storage DOLPHIN 8000AT CDROM support
9560 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
9561 compatible interface. It also works with the Lasermate CR328A. If
9562 you have one of those, say Y. This driver does not work for the
9563 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
9564 one. Please read the file Documentation/cdrom/optcd.
9566 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9567 file system support" below, because that's the file system used on
9570 This driver is also available as a module ( = code which can be
9571 inserted in and removed from the running kernel whenever you want).
9572 The module will be called optcd.o. If you want to compile it as a
9573 module, say M here and read Documentation/modules.txt.
9575 Sanyo CDR-H94A CDROM support
9577 If this is your CDROM drive, say Y here and read the file
9578 Documentation/cdrom/sjcd. You should then also say Y or M to
9579 "ISO 9660 CDROM file system support" below, because that's the
9580 file system used on CDROMs.
9582 This driver is also available as a module ( = code which can be
9583 inserted in and removed from the running kernel whenever you want).
9584 The module will be called sjcd.o. If you want to compile it as a
9585 module, say M here and read Documentation/modules.txt.
9587 ISP16/MAD16/Mozart soft configurable cdrom interface support
9589 These are sound cards with built-in cdrom interfaces using the OPTi
9590 82C928 or 82C929 chips. Say Y here to have them detected and
9591 possibly configured at boot time. In addition, You'll have to say Y
9592 to a driver for the particular cdrom drive you have attached to the
9593 card. Read Documentation/cdrom/isp16 for details.
9595 This driver is also available as a module ( = code which can be
9596 inserted in and removed from the running kernel whenever you want).
9597 The module will be called isp16.o. If you want to compile it as a
9598 module, say M here and read Documentation/modules.txt.
9602 If you say Y here, you will be able to set per user limits for disk
9603 usage (also called disk quotas). Currently, it works only for the
9604 ext2 file system. You need additional software in order to use quota
9605 support; for details, read the Quota mini-HOWTO, available from
9606 http://www.linuxdoc.org/docs.html#howto . Probably the quota
9607 support is only useful for multi user systems. If unsure, say N.
9609 Memory Technology Device (MTD) support
9611 Memory Technology Devices are flash, RAM and similar chips, often
9612 used for solid state filesystems on embedded devices. This option
9613 will provide the generic support for MTD drivers to register
9614 themselves with the kernel and for potential users of MTD devices
9615 to enumerate the devices which are present and obtain a handle on
9616 them. It will also allow you to select individual drivers for
9617 particular hardware and users of MTD device. If unsure, say N.
9619 M-Systems Disk-On-Chip 1000 support
9621 This provides an MTD device driver for the M-Systems DiskOnChip
9622 1000 devices, which are obsolete so you probably want to say 'N'.
9624 M-Systems Disk-On-Chip 2000 support
9626 This provides an MTD device driver for the M-Systems DiskOnChip
9627 2000 devices. If you use this, you probably also want the NFTL
9628 'NAND Flash Translation Layer' below, which is used to emulate
9629 a block device by using a kind of filesystem on the flash chips.
9631 M-Systems Disk-On-Chip Millennium support
9633 This provides an MTD device driver for the M-Systems DiskOnChip
9634 Millennium devices. If you use this, you probably also want the
9635 NFTL 'NAND Flash Translation Layer' below, which is used to emulate
9636 a block device by using a kind of filesystem on the flash chips.
9638 Use extra onboard system memory as MTD device
9640 If your CPU cannot cache all of the physical memory in your machine,
9641 you can still use it for storage or swap by using this driver to
9642 present it to the system as a Memory Technology Device.
9644 Ramix PMC551 PCI Mezzanine ram card support
9646 This provides an MTD device driver for the Ramix PMC551 RAM card.
9647 If you have one, you probably want to enable this.
9649 PMC551 256M DRAM Bugfix.
9650 CONFIG_MTD_PMC551_BUGFIX
9651 Some PMC551 boards hacve invalid column and row mux values. This
9652 option will fix them, but will break other memory configurations.
9654 Debugging RAM test driver
9656 This enables a test MTD device driver which uses vmalloc() to
9657 provide storage. You probably want to say 'N' unless you're
9658 testing stuff, or unless you want to use it in place of a ramdisk
9659 when I've eventually got round to making the CONFIG_BLK_DEV option
9660 and you've turned it off.
9662 Common Flash Interface (CFI) support
9664 Intel's Common Flash Interface specification provides a universal
9665 method for probing the capabilities of flash devices. If you wish
9666 to support any device which uses CFI-compliant devices, you need
9667 to enable this option.
9669 CFI support for Intel/Sharp Extended Command Set chips
9670 CONFIG_MTD_CFI_INTELEXT
9671 The Common Flash Interface defines a number of different command
9672 sets which a CFI-compliant chip may claim to implement. This code
9673 provides support for one of those command sets, used on Intel
9674 Strataflash and other parts.
9676 Flash chip mapping in physical memory
9678 This provides a 'mapping' driver which allows the CFI probe and
9679 command set driver code to communicate with flash chips which
9680 are mapped physically into the CPU's memory. You will need to
9681 configure the physical address and size of the flash chips on
9682 your particular board.
9684 Physical start location of flash chip mapping
9685 CONFIG_MTD_PHYSMAP_START
9686 This is the physical memory location at which the flash chips
9687 are mapped on your particular target board. Refer to the
9688 memory map which should hopefully be in the documentation for
9691 Physical length of flash chip mapping
9692 CONFIG_MTD_PHYSMAP_LEN
9693 This is the total length of the mapping of the flash chips on
9694 your particular board. If there is space, or aliases, in the
9695 physical memory map between the chips, this could be larger
9696 than the total amount of flash present. Refer to the memory
9697 map which should hopefully be in the documentation for your
9700 Flash chip mapping on Mixcom piggyback card
9702 This supports the paging arrangement for access to flash chips
9703 on the Mixcom piggyback card, allowing the flash chip drivers
9704 to get on with their job of driving the flash chips without
9705 having to know about the paging. If you have one of these boards,
9706 you probably want to enable this mapping driver.
9708 Flash chip mapping on Nora
9710 If you had to ask, you don't have one. Say 'N'.
9712 Flash chip mapping on Octagon 5066 SBC
9714 This provides a 'mapping' driver which supports the way in which
9715 the flash chips are connected in the Octagon-5066 Single Board
9716 Computer. You will also need to complete and enable the driver
9717 for JEDEC flash chips.
9719 Flash chip mapping on RPXlite PPC board
9721 The RPXLite PowerPC board has CFI-compliant chips mapped in
9722 a strange sparse mapping. This 'mapping' driver supports that
9723 arrangement, allowing the CFI probe and command set driver code
9724 to communicate with the chips on the RPXLite board.
9726 Flash chip mapping on Tempustech VMAX SBC301
9728 This provides a 'mapping' driver which supports the way in which
9729 the flash chips are connected in the Tempustech VMAX SBC301 Single
9730 Board Computer. You will also need to complete and enable the driver
9731 for JEDEC flash chips.
9733 Direct chardevice access to MTD devices
9735 This provides a character device for each MTD device present in
9736 the system, allowing the user to read and write directly to the
9737 memory chips, and also use ioctl() to obtain information about
9738 the device, or to erase parts of it.
9740 Pseudo-blockdevice access to MTD devices
9742 Although flash chips have an erase size too large to useful as
9743 block devices, it is possible to use MTD devices which are based
9744 on RAM chips in this manner. This blockdevice user of MTD devices
9745 performs that function. At the moment, it is also required for
9746 the Journalling Flash File System to obtain a handle on the MTD
9747 device when it's mounted - although the JFFS doesn't actually use
9748 any of the functions of the mtdblock device.
9750 Later, it may be extended to perform read/erase/modify/write cycles
9751 on flash chips to emulate a smaller block size. Needless to say,
9752 this is very unsafe, but could be useful for filesystems which are
9753 almost never written to.
9755 FTL (Flash Translation Layer) support
9757 This provides support for the original Flash Translation Layer which
9758 is part of the PCMCIA specification. It uses a kind of pseudo-
9759 filesystem on a flash device to emulate a block device with 512-byte
9760 sectors, on top of which you put a 'normal' filesystem. You may find
9761 that the algorithms used in this code are patented unless you live
9762 in the Free World where software patents aren't legal - in the USA
9763 you are only permitted to use this on PCMCIA hardware, although
9764 under the terms of the GPL you're obviously permitted to copy,
9765 modify and distribute the code as you wish. Just not use it.
9767 NFTL (NAND Flash Translation Layer) support
9769 This provides support for the NAND Flash Translation Layer which is
9770 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
9771 filesystem on a flash device to emulate a block device with 512-byte
9772 sectors, on top of which you put a 'normal' filesystem. You may find
9773 that the algorithms used in this code are patented unless you live
9774 in the Free World where software patents aren't legal - in the USA
9775 you are only permitted to use this on DiskOnChip hardware, although
9776 under the terms of the GPL you're obviously permitted to copy,
9777 modify and distribute the code as you wish. Just not use it.
9779 Write support for NFTL (EXPERIMENTAL)
9781 If you're lucky, this will actually work. Don't whinge if it doesn't.
9782 Contact dwmw2@infradead.org if you want to help to make it more
9787 Universal Serial Bus (USB) is a specification for a serial bus
9788 subsystem which offers higher speeds and more features than the
9789 traditional PC serial port. The bus supplies power to peripherals
9790 and allows for hot swapping. Up to 127 USB peripherals can be
9791 connected to a single USB port in a tree structure. The USB port is
9792 the root of the tree, the peripherals are the leaves and the inner
9793 nodes are special USB devices called hubs. Many newer PC's have USB
9794 ports and newer peripherals such as scanners, keyboards, mice,
9795 modems, and printers support the USB protocol and can be connected
9796 to the PC via those ports.
9798 Say Y here if your computer has a USB port and you want to use USB
9799 devices. You then need to say Y to at least one of "UHCI support" or
9800 "OHCI support" below (the type of interface that the USB hardware in
9801 your computer provides to the operating system) and then choose from
9802 among the drivers for USB peripherals. You may want to check out the
9803 information provided in Documentation/usb/ and especially the links
9804 given in Documentation/usb/usb-help.txt.
9806 This code is also available as a module ( = code which can be
9807 inserted in and removed from the running kernel whenever you want).
9808 The module will be called usbcore.o. If you want to compile it as a
9809 module, say M here and read Documentation/modules.txt.
9811 USB verbose debug messages
9813 Say Y here if you want the USB core & hub drivers to produce a bunch
9814 of debug messages to the system log. Select this if you are having a
9815 problem with USB support and want to see more of what is going on.
9817 UHCI (intel PIIX4, VIA, ...) support?
9819 The Universal Host Controller Interface is a standard by Intel for
9820 accessing the USB hardware in the PC (which is also called the USB
9821 host controller). If your USB host controller conforms to this
9822 standard, you may want to say Y, but see below. All recent boards
9823 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
9824 i810, i820) conform to this standard. Also all VIA PCI chipsets
9825 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
9828 Currently there exist two drivers for UHCI host controllers: this
9829 one and the so-called JE driver, which you can get from
9830 "UHCI alternate (JE) support", below. You need only one.
9832 This code is also available as a module ( = code which can be
9833 inserted in and removed from the running kernel whenever you want).
9834 The module will be called usb-uhci.o. If you want to compile it as a
9835 module, say M here and read Documentation/modules.txt.
9837 UHCI (intel PIIX4, VIA, ...) alternate (JE) support?
9839 The Universal Host Controller Interface is a standard by Intel for
9840 accessing the USB hardware in the PC (which is also called the USB
9841 host controller). If your USB host controller conforms to this
9842 standard, you may want to say Y, but see below. All recent boards
9843 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
9844 i810, i820) conform to this standard. Also all VIA PCI chipsets
9845 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
9846 133). If unsure, say Y.
9848 Currently there exist two drivers for UHCI host controllers: this
9849 so-called JE driver, and the one you get from "UHCI support", above.
9852 This code is also available as a module ( = code which can be
9853 inserted in and removed from the running kernel whenever you want).
9854 The module will be called uhci.o. If you want to compile it as a
9855 module, say M here and read Documentation/modules.txt.
9857 UHCI unlink optimizations (EXPERIMENTAL)
9858 CONFIG_USB_UHCI_ALT_UNLINK_OPTIMIZE
9859 This option currently does nothing. You may say Y or N.
9861 OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support
9863 The Open Host Controller Interface is a standard by
9864 Compaq/Microsoft/National for accessing the USB PC hardware (also
9865 called USB host controller). If your USB host controller conforms to
9866 this standard, say Y. The USB host controllers on most non-Intel
9867 architectures and on several x86 compatibles with non-Intel chipsets
9868 -- like SiS (aktual 610, 610 and so on) or ALi (ALi IV, ALi V,
9869 Aladdin Pro..) -- conform to this standard.
9871 You may want to read the file Documentation/usb/ohci.txt.
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-ohci.o. If you want to compile it
9876 as a module, say M here and read Documentation/modules.txt.
9878 USB Human Interface Device (HID) support
9880 Say Y here if you want to connect keyboards, mice, joysticks,
9881 graphic tablets, or any other HID based devices to your
9882 computer via USB. More information is available:
9883 Documentation/usb/input.txt.
9887 This code is also available as a module ( = code which can be
9888 inserted in and removed from the running kernel whenever you want).
9889 The module will be called hid.o. If you want to compile it as a
9890 module, say M here and read Documentation/modules.txt.
9892 USB HIDBP Keyboard support
9894 Say Y here if you don't want to use the generic HID driver for your
9895 USB keyboard and prefer to use the keyboard in its limited Boot
9896 Protocol mode. This driver is much smaller than the HID one.
9898 This code is also available as a module ( = code which can be
9899 inserted in and removed from the running kernel whenever you want).
9900 The module will be called usbkbd.o. If you want to compile it as a
9901 module, say M here and read Documentation/modules.txt.
9905 USB HIDBP Mouse support
9907 Say Y here if you don't want to use the generic HID driver for your
9908 USB mouse and prefer to use the mouse in its limited Boot Protocol
9909 mode. This driver is much smaller than the HID one.
9911 This code is also available as a module ( = code which can be
9912 inserted in and removed from the running kernel whenever you want).
9913 The module will be called usbmouse.o. If you want to compile it as
9914 a module, say M here and read Documentation/modules.txt.
9918 Wacom Intuos/Graphire tablet support
9920 Say Y here if you want to use the USB version of the Wacom Intuos
9921 or Graphire tablet. Make sure to say Y to "Mouse support"
9922 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
9923 (CONFIG_INPUT_EVDEV) as well.
9925 This driver is also available as a module ( = code which can be
9926 inserted in and removed from the running kernel whenever you want).
9927 The module will be called wacom.o. If you want to compile it as a
9928 module, say M here and read Documentation/modules.txt.
9930 Logitech WingMan Force joystick support
9932 Say Y here if you want to use the Logitech WingMan Force with Linux
9933 on the USB port. No force-feedback support yet, but other than that
9934 it should work like a normal joystick.
9936 This driver is also available as a module ( = code which can be
9937 inserted in and removed from the running kernel whenever you want).
9938 The module will be called wmforce.o. If you want to compile it as a
9939 module, say M here and read Documentation/modules.txt.
9942 CONFIG_INPUT_KEYBDEV
9943 Say Y here if you want your USB HID keyboard to be able to serve as
9946 This driver is also available as a module ( = code which can be
9947 inserted in and removed from the running kernel whenever you want).
9948 The module will be called keybdev.o. If you want to compile it as a
9949 module, say M here and read Documentation/modules.txt.
9952 CONFIG_INPUT_MOUSEDEV
9953 Say Y here if you want your USB HID mouse to be accessible as
9954 char devices 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice
9955 as an emulated PS/2 mouse. That way, all user space programs will
9956 be able to use your mouse.
9960 This driver is also available as a module ( = code which can be
9961 inserted in and removed from the running kernel whenever you want).
9962 The module will be called mousedev.o. If you want to compile it as
9963 a module, say M here and read Documentation/modules.txt.
9965 Horizontal screen resolution
9966 CONFIG_INPUT_MOUSEDEV_SCREEN_X
9967 If you're using a digitizer, or a graphic tablet, and want to use
9968 it as a mouse then the mousedev driver needs to know the X window
9969 screen resolution you are using to correctly scale the data. If
9970 you're not using a digitizer, this value is ignored.
9972 Vertical screen resolution
9973 CONFIG_INPUT_MOUSEDEV_SCREEN_Y
9974 If you're using a digitizer, or a graphic tablet, and want to use
9975 it as a mouse then the mousedev driver needs to know the X window
9976 screen resolution you are using to correctly scale the data. If
9977 you're not using a digitizer, this value is ignored.
9981 Say Y here if you want your USB HID joystick or gamepad to be
9982 accessible as char device 13:0+ - /dev/input/jsX device.
9984 This driver is also available as a module ( = code which can be
9985 inserted in and removed from the running kernel whenever you want).
9986 The module will be called joydev.o. If you want to compile it as a
9987 module, say M here and read Documentation/modules.txt.
9989 Event interface support
9991 Say Y here if you want your USB HID device events be accessible
9992 under char device 13:64+ - /dev/inputX in a generic way.
9993 This is the future ...
9997 Say Y here if you want to connect a USB scanner to your computer's
9998 USB port. Please read Documentation/usb/scanner.txt and
9999 Documentation/usb/scanner-hp-sane.txt for more information.
10001 This code 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 scanner.o. If you want to compile it as
10004 a module, say M here and read Documentation/modules.txt.
10008 Say Y here if you want to connect UAB audio equipment such as
10009 speakers to your computer's USB port.
10011 This code is also available as a module ( = code which can be
10012 inserted in and removed from the running kernel whenever you want).
10013 The module will be called audio.o. If you want to compile it as a
10014 module, say M here and read Documentation/modules.txt.
10016 USB Modem (CDC ACM) support
10018 This driver supports USB modems and ISDN adapters which support the
10019 Communication Device Class Abstract Control Model interface.
10020 Please read Documentation/usb/acm.txt for details.
10022 This code is also available as a module ( = code which can be
10023 inserted in and removed from the running kernel whenever you want).
10024 The module will be called acm.o. If you want to compile it as a
10025 module, say M here and read Documentation/modules.txt.
10027 USB Serial converter support
10029 Say Y here if you have a USB device that provides normal serial
10030 ports, and you want to connect it to your USB bus. Supported devices
10031 are the Tech WhiteHEAT multi-port USB to serial converter, and the
10032 FTDI or Keyspan single port USB to serial converter Handspring
10033 Visor. In addition to saying Y here, you need to say Y to the driver
10034 for your specific hardware below. Some other devices may also be
10035 used if you say Y to "USB Generic Serial Driver", below.
10037 Please read Documentation/usb/usb-serial.txt for more information.
10039 This code is also available as a module ( = code which can be
10040 inserted in and removed from the running kernel whenever you want).
10041 The module will be called usbserial.o. If you want to compile it
10042 as a module, say M here and read Documentation/modules.txt.
10044 USB Generic Serial Driver
10045 CONFIG_USB_SERIAL_GENERIC
10046 Say Y here if you want to use the generic USB serial driver. Please
10047 read Documentation/usb/usb-serial.txt for more information on using
10048 this driver. It is recommended that the "USB Serial converter
10049 support" be compiled as a module for this driver to be used
10052 USB ConnectTech WhiteHEAT Serial Driver
10053 CONFIG_USB_SERIAL_WHITEHEAT
10054 Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
10055 USB to serial converter device.
10057 This code is also available as a module ( = code which can be
10058 inserted in and removed from the running kernel whenever you want).
10059 The module will be called whiteheat.o. If you want to compile it as a
10060 module, say M here and read Documentation/modules.txt.
10062 USB Handspring Visor Driver
10063 CONFIG_USB_SERIAL_VISOR
10064 Say Y here if you want to connect to your HandSpring Visor through
10065 its USB docking station. See http://usbvisor.sourceforge.net for
10066 more information on using this driver.
10068 This code is also available as a module ( = code which can be
10069 inserted in and removed from the running kernel whenever you want).
10070 The module will be called visor.o. If you want to compile it as a
10071 module, say M here and read Documentation/modules.txt.
10073 USB FTDI Single Port Serial Driver
10074 CONFIG_USB_SERIAL_FTDI_SIO
10075 Say Y here if you want to use a FTDI SIO single port USB to serial
10076 converter device. The implementation I have is called the USC-1000.
10078 See http://reality.sgi.com/bryder_wellington/ftdi_sio for more
10079 information on this driver and the device.
10081 This code is also available as a module ( = code which can be
10082 inserted in and removed from the running kernel whenever you want).
10083 The module will be called ftdi_sio.o. If you want to compile it as a
10084 module, say M here and read Documentation/modules.txt.
10086 USB Keyspan PDA Single Port Serial Driver
10087 CONFIG_USB_SERIAL_KEYSPAN_PDA
10088 Say Y here if you want to use a Keyspan PDA single port USB to
10089 serial converter device. This driver makes use of firmware
10090 developed from scratch by Brian Warner.
10092 This code is also available as a module ( = code which can be
10093 inserted in and removed from the running kernel whenever you want).
10094 The module will be called keyspan_pda.o. If you want to compile it
10095 as a module, say M here and read Documentation/modules.txt.
10097 USB Keyspan USA-xxx Serial Driver
10098 CONFIG_USB_SERIAL_KEYSPAN
10099 Say Y here if you want to use Keyspan USB to serial converter
10100 devices. This driver makes use of Keyspan's official firmware
10101 and was developed with their support. You must also include
10102 firmware to support your particular device(s).
10104 See http://www.linuxcare.com.au/hugh/keyspan.html for
10107 This code is also available as a module ( = code which can be
10108 inserted in and removed from the running kernel whenever you want).
10109 The module will be called keyspan.o. If you want to compile it as a
10110 module, say M here and read Documentation/modules.txt.
10112 USB Keyspan USA-28 Firmware
10113 CONFIG_USB_SERIAL_KEYSPAN_USA28
10114 Say Y here to include firmware for the USA-28 converter.
10116 USB Keyspan USA-28X Firmware
10117 CONFIG_USB_SERIAL_KEYSPAN_USA28X
10118 Say Y here to include firmware for the USA-28X converter.
10120 USB Keyspan USA-19 Firmware
10121 CONFIG_USB_SERIAL_KEYSPAN_USA19
10122 Say Y here to include firmware for the USA-19 converter.
10124 USB Keyspan USA-18X Firmware
10125 CONFIG_USB_SERIAL_KEYSPAN_USA18X
10126 Say Y here to include firmware for the USA-18X converter.
10128 USB Keyspan USA-19W Firmware
10129 CONFIG_USB_SERIAL_KEYSPAN_USA19W
10130 Say Y here to include firmware for the USA-19W converter.
10132 USB ZyXEL omni.net LCD Plus Driver
10133 CONFIG_USB_SERIAL_OMNINET
10134 Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA.
10136 This code is also available as a module ( = code which can be
10137 inserted in and removed from the running kernel whenever you want).
10138 The module will be called omninet.o. If you want to compile it as a
10139 module, say M here and read Documentation/modules.txt.
10141 USB Digi International AccelePort USB Serial Driver
10142 CONFIG_USB_SERIAL_DIGI_ACCELEPORT
10143 Say Y here if you want to use Digi AccelePort USB 2 or 4 devices,
10144 2 port (plus parallel port) and 4 port USB serial converters. The
10145 parallel port on the USB 2 appears as a third serial port on Linux.
10146 The Digi Acceleport USB 8 is not yet supported by this driver.
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 digi_acceleport.o. If you want to compile
10151 it as a module, say M here and read Documentation/modules.txt.
10153 USB Serial Converter verbose debug
10154 CONFIG_USB_SERIAL_DEBUG
10155 Say Y here if you want verbose debug messages from the USB Serial
10158 USB Printer support
10160 Say Y here if you want to connect a USB printer to your computer's
10163 This code is also available as a module ( = code which can be
10164 inserted in and removed from the running kernel whenever you want).
10165 The module will be called printer.o. If you want to compile it as a
10166 module, say M here and read Documentation/modules.txt.
10168 USB IBM (Xirlink) C-It Camera support
10170 Say Y here if you want to connect a IBM "C-It" camera, also known as
10171 "Xirlink PC Camera" to your computer's USB port. For more
10172 information, read Documentation/usb/ibmcam.txt.
10174 This driver uses the Video For Linux API. You must enable
10175 (Y or M in config) Video For Linux (under Character Devices)
10176 to use this driver. Information on this API and pointers to
10177 "v4l" programs may be found on the WWW at
10178 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10180 This code is also available as a module ( = code which can be
10181 inserted in and removed from the running kernel whenever you want).
10182 The module will be called ibmcam.o. If you want to compile it as a
10183 module, say M here and read Documentation/modules.txt. This camera
10184 has several configuration options which can be specified when you
10185 load the module. Read Documentation/usb/ibmcam.txt to learn more.
10187 USB OV511 Camera support
10189 Say Y here if you want to connect this type of camera to your
10190 computer's USB port. See Documentation/usb/ov511.txt for more
10191 information and for a list of supported cameras.
10193 This driver uses the Video For Linux API. You must say Y or M to
10194 "Video For Linux" (under Character Devices) to use this driver.
10195 Information on this API and pointers to "v4l" programs may be found
10196 on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10198 This code is also available as a module ( = code which can be
10199 inserted in and removed from the running kernel whenever you want).
10200 The module will be called ov511.o. If you want to compile it as a
10201 module, say M here and read Documentation/modules.txt.
10203 USB ADMtek Pegasus-based ethernet device support
10205 Say Y if you want to use your USB ethernet device. Supported
10206 cards until now are:
10207 ADMtek AN986 (eval. board)
10210 Corega FEter USB-TX
10211 MELCO/BUFFALO LUA-TX
10212 D-Link DSB-650TX, DSB-650TX-PNA, DSB-650, DU-E10, DU-E100
10213 Linksys USB100TX, USB10TX
10214 LANEED Ethernet LD-USB/TX
10216 SOHOware NUB Ethernet
10217 If you have devices with vendor IDs other than noted above
10218 you should add them in the driver code and send a message
10219 to me (petkan@dce.bg) for update.
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 pegasus.o. If you want to compile it as a
10224 module, say M here and read Documentation/modules.txt.
10226 USB Kodak DC-2xx Camera support
10228 Say Y here if you want to connect this type of still camera to
10229 your computer's USB port. See Documentation/usb/dc2xx.txt for more
10230 information; some non-Kodak cameras may also work with this
10231 driver, given application support (such as www.gPhoto.org).
10233 This code is also available as a module ( = code which can be
10234 inserted in and removed from the running kernel whenever you want).
10235 The module will be called dc2xx.o. If you want to compile it as a
10236 module, say M here and read Documentation/modules.txt.
10238 USB Mustek MDC800 Digital Camera Support
10240 Say Y here if you want to connect this type of still camera to
10241 your computer's USB port. This driver can be used with gphoto 0.4.3
10242 and higher (look at http://www.gphoto.org ).
10243 To use it create a device node with "mknod /dev/mustek c 180 32" and
10244 configure it in your software.
10246 This code is also available as a module ( = code which can be
10247 inserted in and removed from the running kernel whenever you want).
10248 The module will be called mdc800.o. If you want to compile it as a
10249 module, say M here and read Documentation/modules.txt.
10251 USB Mass Storage support
10253 Say Y here if you want to connect USB mass storage devices to your
10254 computer's USB port.
10256 This code is also available as a module ( = code which can be
10257 inserted in and removed from the running kernel whenever you want).
10258 The module will be called usb-storage.o. If you want to compile it
10259 as a module, say M here and read Documentation/modules.txt.
10261 USB Mass Storage verbose debug
10262 CONFIG_USB_STORAGE_DEBUG
10263 Say Y here in order to have the USB Mass Storage code generate
10264 verbose debugging messages.
10266 USS720 parport driver
10268 This driver is for USB parallel port adapters that use the Lucent
10269 Technologies USS-720 chip. These cables are plugged into your USB
10270 port and provide USB compatibility to peripherals designed with
10271 parallel port interfaces.
10273 The chip has two modes: automatic mode and manual mode. In automatic
10274 mode, it looks to the computer like a standard USB printer. Only
10275 printers may be connected to the USS-720 in this mode. The generic
10276 USB printer driver ("USB Printer support", above) may be used in
10277 that mode, and you can say N here if you want to use the chip only
10280 Manual mode is not limited to printers, any parallel port
10281 device should work. This driver utilizes manual mode.
10282 Note however that some operations are three orders of magnitude
10283 slower than on a PCI/ISA Parallel Port, so timing critical
10284 applications might not work.
10286 Say Y here if you own an USS-720 USB->Parport cable and intend to
10287 connect anything other than a printer to it.
10289 This code is also available as a module ( = code which can be
10290 inserted in and removed from the running kernel whenever you want).
10291 The module will be called uss720.o. If you want to compile it as a
10292 module, say M here and read Documentation/modules.txt.
10294 USB device file system
10295 CONFIG_USB_DEVICEFS
10296 If you say Y here (and to "/proc file system support" below), you
10297 will get a file /proc/usb/devices which lists the devices currently
10298 connected to your USB busses, a file /proc/usb/drivers which lists
10299 the USB kernel client drivers currently loaded, and for every
10300 connected device a file named "/proc/usb/xxx/yyy", where xxx is the
10301 bus number and yyy the device number; the latter files can be used
10302 by user space programs to talk directly to the device. These files
10303 are "virtual", meaning they are generated on the fly and not stored
10306 For the format of the /proc/usb/ files, please read
10307 Documentation/usb/proc_usb_info.txt.
10309 Please note that this code is completely unrelated to devfs, the
10310 "/dev file system support".
10312 Most users want to say Y here.
10314 USB Bandwidth allocation
10315 CONFIG_USB_BANDWIDTH
10316 If you say Y here, the USB subsystem enforces USB bandwidth
10317 allocation and will prevent some device opens from succeeding
10318 if they would cause USB bandwidth usage to go above 90% of
10321 If you say N here, these conditions will cause warning messages
10322 about USB bandwidth usage to be logged and some devices or
10323 drivers may not work correctly.
10327 A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
10328 brought to you by the DAB-Team (http://dab.in.tum.de). This driver
10329 can be taken as an example for URB-based bulk, control, and
10330 isochronous transactions. URB's are explained in
10331 Documentation/usb/URB.txt.
10333 This code is also available as a module ( = code which can be
10334 inserted in and removed from the running kernel whenever you want).
10335 The module will be called dabusb.o. If you want to compile it as a
10336 module, say M here and read Documentation/modules.txt.
10340 A driver for the Prolific PL-2302 USB-to-USB network device. This
10341 'USB cable' connects two hosts via a point-to-point network with
10342 bandwidth of 5 Mbit/s. Configure this driver after connecting the
10343 USB cable via ifconfig plusb0 10.0.0.1 pointopoint 10.0.0.2 (and
10344 vice versa on the other host).
10346 This code is also available as a module ( = code which can be
10347 inserted in and removed from the running kernel whenever you want).
10348 The module will be called plusb.o. If you want to compile it as a
10349 module, say M here and read Documentation/modules.txt.
10351 USB Diamond Rio500 support
10353 Say Y here if you want to connect a USB Rio500 mp3 player to your
10354 computer's USB port. Please read Documentation/usb/rio.txt
10355 for more information.
10357 This code is also available as a module ( = code which can be
10358 inserted in and removed from the running kernel whenever you want).
10359 The module will be called rio500.o. If you want to compile it as
10360 a module, say M here and read Documentation/modules.txt.
10362 D-Link DSB-R100 FM radio support
10364 Say Y here if you want to connect this type of radio to your
10365 computer's USB port. Note that the audio is not digital, and
10366 you must connect the line out connector to a sound card or a
10369 This driver uses the Video For Linux API. You must enable
10370 (Y or M in config) Video For Linux (under Character Devices)
10371 to use this driver. Information on this API and pointers to
10372 "v4l" programs may be found on the WWW at
10373 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10375 This code is also available as a module ( = code which can be
10376 inserted in and removed from the running kernel whenever you want).
10377 The module will be called dsbr100.o. If you want to compile it as a
10378 module, say M here and read Documentation/modules.txt.
10380 Microtek USB scanner support
10381 CONFIG_USB_MICROTEK
10382 Say Y here if you want support for the Microtek X6USB and possibly
10383 some other scanners by that vendor. The scanner will appear as a
10384 scsi generic device to the rest of the system.
10385 A patched version of SANE is necessary to use the
10386 scanner. It's available at
10387 http://fachschaft.cup.uni-muenchen.de/~neukum/scanner.html
10388 This driver can be compiled as a module.
10390 USB Bluetooth support
10391 CONFIG_USB_BLUETOOTH
10392 Say Y here if you want to connect a USB Bluetooth device to your
10393 computer's USB port. You will need the Bluetooth stack (available
10394 at http://developer.axis.com/software/index.shtml) to fully use
10397 This code is also available as a module ( = code which can be
10398 inserted in and removed from the running kernel whenever you want).
10399 The module will be called bluetooth.o. If you want to compile it as
10400 a module, say M here and read Documentation/modules.txt.
10404 Minix is a simple operating system used in many classes about OS's.
10405 The minix file system (method to organize files on a hard disk
10406 partition or a floppy disk) was the original file system for Linux,
10407 but has been superseded by the second extended file system ext2fs.
10408 You don't want to use the minix file system on your hard disk
10409 because of certain built-in restrictions, but it is sometimes found
10410 on older Linux floppy disks. This option will enlarge your kernel by
10411 about 28 KB. If unsure, say N.
10413 If you want to compile this as a module ( = code which can be
10414 inserted in and removed from the running kernel whenever you want),
10415 say M here and read Documentation/modules.txt. The module will be
10416 called minix.o. Note that the file system of your root partition
10417 (the one containing the directory /) cannot be compiled as a module.
10419 Second extended fs support
10421 This is the de facto standard Linux file system (method to organize
10422 files on a storage device) for hard disks.
10424 You want to say Y here, unless you intend to use Linux exclusively
10425 from inside a DOS partition using the UMSDOS file system. The
10426 advantage of the latter is that you can get away without
10427 repartitioning your hard drive (which often implies backing
10428 everything up and restoring afterwards); the disadvantage is that
10429 Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
10430 slower than ext2fs. Even if you want to run Linux in this fashion,
10431 it might be a good idea to have ext2fs around: it enables you to
10432 read more floppy disks and facilitates the transition to a *real*
10433 Linux partition later. Another (rare) case which doesn't require
10434 ext2fs is a diskless Linux box which mounts all files over the
10435 network using NFS (in this case it's sufficient to say Y to "NFS
10436 file system support" below). Saying Y here will enlarge your kernel
10439 The Ext2fs-Undeletion mini-HOWTO, available from
10440 http://www.linuxdoc.org/docs.html#howto , gives information about
10441 how to retrieve deleted files on ext2fs file systems.
10443 To change the behavior of ext2 file systems, you can use the tune2fs
10444 utility ("man tune2fs"). To modify attributes of files and
10445 directories on ext2 file systems, use chattr ("man chattr").
10447 Ext2fs partitions can be read from within DOS using the ext2tool
10448 command line tool package (available via FTP (user: anonymous) from
10449 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2 ) and from
10450 within Windows NT using the ext2nt command line tool package from
10451 ftp://metalab.unc.edu/pub/Linux/utils/dos . Explore2fs is a
10452 graphical explorer for ext2fs partitions which runs on Windows 95
10453 and Windows NT and includes experimental write support; it is
10455 http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm .
10457 If you want to compile this file system as a module ( = code which
10458 can be inserted in and removed from the running kernel whenever you
10459 want), say M here and read Documentation/modules.txt. The module
10460 will be called ext2.o. Be aware however that the file system of your
10461 root partition (the one containing the directory /) cannot be
10462 compiled as a module, and so this could be dangerous. Most everyone
10463 wants to say Y here.
10465 BFS file system support (EXPERIMENTAL)
10467 Boot File System (BFS) is a file system used under SCO UnixWare to
10468 allow the bootloader access to the kernel image and other important
10469 files during the boot process. It is usually mounted under /stand
10470 and corresponds to the slice marked as "STAND" in the UnixWare
10471 partition. You should say Y if you want to read or write
10472 the files on your /stand slice from within Linux. You then also
10473 need to say Y to "UnixWare slices support", below. More information
10474 about the BFS file system is contained in the file
10475 Documentation/filesystems/bfs.txt.
10477 If you don't know what this is about, say N.
10479 If you want to compile this as a module ( = code which can be
10480 inserted in and removed from the running kernel whenever you want),
10481 say M here and read Documentation/modules.txt. The module will be
10482 called bfs.o. Note that the file system of your root partition (the
10483 one containing the directory /) cannot be compiled as a module.
10485 Compressed ROM file system support
10487 Saying Y here includes support for CramFs (Compressed ROM File
10488 System). Cramfs is designed to be a simple, small, and compressed
10489 file system for ROM based embedded systems. CramFs is read-only,
10490 limited to 256MB file systems (with 16MB files), and doesn't support
10491 16/32 bits uid/gid, hard links and timestamps.
10493 See Documentation/filesystems/cramfs.txt and fs/cramfs/README
10494 for further information.
10496 If you want to compile this as a module ( = code which can be
10497 inserted in and removed from the running kernel whenever you want),
10498 say M here and read Documentation/modules.txt. The module will be
10499 called cramfs.o. Note that the root file system (the one containing
10500 the directory /) cannot be compiled as a module.
10504 Simple RAM-based file system support
10506 Ramfs is a file system which keeps all files in RAM. It allows
10507 read and write access.
10509 In contrast to RAM disks, which get allocated a fixed amount of RAM,
10510 ramfs grows and shrinks to accommodate the files it contains.
10512 Before you can use this RAM-based file system, it has to be mounted,
10513 meaning it has to be given a location in the directory hierarchy. If
10514 you want to use the location /ramfiles for example, you would have
10515 to create that directory first and then mount the file system by
10516 saying "mount -t ramfs ramfs /ramfiles" or the equivalent line in
10517 /etc/fstab. Everything is "virtual" in the sense that no files will
10518 be created on your hard drive; if you reboot, everything in
10519 /ramfiles will be lost.
10521 If you want to compile this as a module ( = code which can be
10522 inserted in and removed from the running kernel whenever you want),
10523 say M here and read Documentation/modules.txt. The module will be
10526 ISO 9660 CDROM file system support
10528 This is the standard file system used on CDROMs. It was previously
10529 known as "High Sierra File System" and is called "hsfs" on other
10530 Unix systems. The so-called Rock-Ridge extensions which allow for
10531 long Unix filenames and symbolic links are also supported by this
10532 driver. If you have a CDROM drive and want to do more with it than
10533 just listen to audio CDs and watch its LEDs, say Y (and read
10534 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
10535 from http://www.linuxdoc.org/docs.html#howto ), thereby enlarging
10536 your kernel by about 27 KB; otherwise say N.
10538 If you want to compile this as a module ( = code which can be
10539 inserted in and removed from the running kernel whenever you want),
10540 say M here and read Documentation/modules.txt. The module will be
10543 Microsoft Joliet CDROM extensions
10545 Joliet is a Microsoft extension for the ISO 9660 CDROM file system
10546 which allows for long filenames in unicode format (unicode is the
10547 new 16 bit character code, successor to ASCII, which encodes the
10548 characters of almost all languages of the world; see
10549 http://www.unicode.org for more information). Say Y here if you want
10550 to be able to read Joliet CDROMs under Linux.
10552 UDF File System support (read only)
10554 This is the new file system used on some CDROMs and DVDs. Say Y if
10555 you intend to mount DVD discs or CDRW's written in packet mode, or
10556 if written to by other UDF utilities, such as DirectCD. This UDF
10557 file system support is read-only. If you want to write to UDF
10558 file systems on some media, you need to say Y to "UDF read-write
10559 support" below in addition. Please read
10560 Documentation/filesystems/udf.txt.
10562 This file system support is also available as a module ( = code
10563 which can be inserted in and removed from the running kernel
10564 whenever you want). The module is called udf.o. If you want to
10565 compile it as a module, say M here and read
10566 Documentation/modules.txt.
10570 UDF write support (DANGEROUS)
10572 Say Y if you want to test write support for UDF file systems.
10573 Due to lack of support for writing to CDR/CDRW's, this option
10574 is only supported for hard discs, DVD-RAM, and loopback files.
10578 If you want to use one of the FAT-based file systems (the MS-DOS,
10579 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
10580 ordinary DOS partition) file systems), then you must say Y or M here
10581 to include FAT support. You will then be able to mount partitions or
10582 diskettes with FAT-based file systems and transparently access the
10583 files on them, i.e. MSDOS files will look and behave just like all
10586 This FAT support is not a file system in itself, it only provides
10587 the foundation for the other file systems. You will have to say Y or
10588 M to at least one of "MSDOS fs support" or "VFAT fs support" in
10589 order to make use of it.
10591 Another way to read and write MSDOS floppies and hard drive
10592 partitions from within Linux (but not transparently) is with the
10593 mtools ("man mtools") program suite. You don't need to say Y here in
10596 If you need to move large files on floppies between a DOS and a
10597 Linux box, say Y here, mount the floppy under Linux with an MSDOS
10598 file system and use GNU tar's M option. GNU tar is a program
10599 available for Unix and DOS ("man tar" or "info tar").
10601 It is now also becoming possible to read and write compressed FAT
10602 file systems; read Documentation/filesystems/fat_cvf.txt for
10605 The FAT support will enlarge your kernel by about 37 KB. If unsure,
10608 If you want to compile this as a module however ( = code which can
10609 be inserted in and removed from the running kernel whenever you
10610 want), say M here and read Documentation/modules.txt. The module
10611 will be called fat.o. Note that if you compile the FAT support as a
10612 module, you cannot compile any of the FAT-based file systems into
10613 the kernel -- they will have to be modules as well. The file system
10614 of your root partition (the one containing the directory /) cannot
10615 be a module, so don't say M here if you intend to use UMSDOS as your
10620 This allows you to mount MSDOS partitions of your hard drive (unless
10621 they are compressed; to access compressed MSDOS partitions under
10622 Linux, you can either use the DOS emulator DOSEMU, described in the
10623 DOSEMU-HOWTO, available from
10624 http://www.linuxdoc.org/docs.html#howto , or try dmsdosfs in
10625 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs . If you
10626 intend to use dosemu with a non-compressed MSDOS partition, say Y
10627 here) and MSDOS floppies. This means that file access becomes
10628 transparent, i.e. the MSDOS files look and behave just like all
10631 If you want to use UMSDOS, the Unix-like file system on top of a
10632 DOS file system, which allows you to run Linux from within a DOS
10633 partition without repartitioning, you'll have to say Y or M here.
10635 If you have Windows 95 or Windows NT installed on your MSDOS
10636 partitions, you should use the VFAT file system (say Y to "VFAT fs
10637 support" below), or you will not be able to see the long filenames
10638 generated by Windows 95 / Windows NT.
10640 This option will enlarge your kernel by about 7 KB. If unsure,
10641 answer Y. This will only work if you said Y to "DOS FAT fs support"
10642 as well. If you want to compile this as a module however ( = code
10643 which can be inserted in and removed from the running kernel
10644 whenever you want), say M here and read Documentation/modules.txt.
10645 The module will be called msdos.o.
10647 VFAT (Windows-95) fs support
10649 This option provides support for normal Windows file systems with
10650 long filenames. That includes non-compressed FAT-based file systems
10651 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
10652 programs from the mtools package.
10654 You cannot use the VFAT file system for your Linux root partition
10655 (the one containing the directory /); use UMSDOS instead if you
10656 want to run Linux from within a DOS partition (i.e. say Y to
10657 "UMSDOS: Unix like fs on top of std MSDOS fs", below).
10659 The VFAT support enlarges your kernel by about 10 KB and it only
10660 works if you said Y to the "DOS FAT fs support" above. Please read
10661 the file Documentation/filesystems/vfat.txt for details. If unsure,
10664 If you want to compile this as a module ( = code which can be
10665 inserted in and removed from the running kernel whenever you want),
10666 say M here and read Documentation/modules.txt. The module will be
10669 UMSDOS: Unix-like file system on top of standard MSDOS fs
10671 Say Y here if you want to run Linux from within an existing DOS
10672 partition of your hard drive. The advantage of this is that you can
10673 get away without repartitioning your hard drive (which often implies
10674 backing everything up and restoring afterwards) and hence you're
10675 able to quickly try out Linux or show it to your friends; the
10676 disadvantage is that Linux becomes susceptible to DOS viruses and
10677 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
10678 is to write files with long unix filenames to MSDOS floppies; it
10679 also allows Unix-style soft-links and owner/permissions of files on
10680 MSDOS floppies. You will need a program called umssync in order to
10681 make use of UMSDOS; read Documentation/filesystems/umsdos.txt.
10683 To get utilities for initializing/checking UMSDOS file system, or
10684 latest patches and/or information, visit the UMSDOS home page at
10685 http://www.voyager.hr/~mnalis/umsdos/ .
10687 This option enlarges your kernel by about 28 KB and it only works if
10688 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
10689 above. If you want to compile this as a module ( = code which can be
10690 inserted in and removed from the running kernel whenever you want),
10691 say M here and read Documentation/modules.txt. The module will be
10692 called umsdos.o. Note that the file system of your root partition
10693 (the one containing the directory /) cannot be a module, so saying M
10694 could be dangerous. If unsure, say N.
10696 /proc file system support
10698 This is a virtual file system providing information about the status
10699 of the system. "Virtual" means that it doesn't take up any space on
10700 your hard disk: the files are created on the fly by the kernel when
10701 you try to access them. Also, you cannot read the files with older
10702 version of the program less: you need to use more or cat.
10704 It's totally cool; for example, "cat /proc/interrupts" gives
10705 information about what the different IRQs are used for at the moment
10706 (there is a small number of Interrupt ReQuest lines in your computer
10707 that are used by the attached devices to gain the CPU's attention --
10708 often a source of trouble if two devices are mistakenly configured
10709 to use the same IRQ). The program procinfo to display some
10710 information about your system gathered from the /proc file system.
10712 Before you can use the /proc file system, it has to be mounted,
10713 meaning it has to be given a location in the directory hierarchy.
10714 That location should be /proc. A command such as "mount -t proc proc
10715 /proc" or the equivalent line in /etc/fstab does the job.
10717 The /proc file system is explained in the file
10718 Documentation/filesystems/proc.txt and on the proc(5) manpage ("man
10721 This option will enlarge your kernel by about 67 KB. Several
10722 programs depend on this, so everyone should say Y here.
10724 /dev file system support (EXPERIMENTAL)
10726 This is support for devfs, a virtual file system (like /proc) which
10727 provides the file system interface to device drivers, normally found
10728 in /dev. Devfs does not depend on major and minor number
10729 allocations. Device drivers register entries in /dev which then
10730 appear automatically, which means that the system administrator does
10731 not have to create character and block special device files in the
10732 /dev directory using the mknod command (or MAKEDEV script) anymore.
10734 This is work in progress. If you want to use this, you *must* read
10735 the material in Documentation/filesystems/devfs/, especially the
10740 Enable automatic mounting at boot
10742 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
10743 this to 'Y' will make the kernel automatically mount devfs onto /dev
10744 when the system is booted, before the init thread is started.
10745 You can override this with the "devfs=nomount" boot option.
10751 If you say Y here, then the /dev file system code will generate
10752 debugging messages. See the file
10753 Documentation/filesystems/devfs/boot-options for more details.
10757 NFS file system support
10759 If you are connected to some other (usually local) Unix computer
10760 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
10761 on that computer (the NFS server) using the Network File Sharing
10762 protocol, say Y. "Mounting files" means that the client can access
10763 the files with usual UNIX commands as if they were sitting on the
10764 client's hard disk. For this to work, the server must run the
10765 programs nfsd and mountd (but does not need to have NFS file system
10766 support enabled in its kernel). NFS is explained in the Network
10767 Administrator's Guide, available from
10768 http://www.linuxdoc.org/docs.html#guide , on its man page: "man
10769 nfs", and in the NFS-HOWTO.
10771 A superior but less widely used alternative to NFS is provided by
10772 the Coda file system; see "Coda file system support" below.
10774 If you say Y here, you should have said Y to TCP/IP networking also.
10775 This option would enlarge your kernel by about 27 KB.
10777 This file system is also available as a module ( = code which can be
10778 inserted in and removed from the running kernel whenever you want).
10779 The module is called nfs.o. If you want to compile it as a module,
10780 say M here and read Documentation/modules.txt.
10782 If you are configuring a diskless machine which will mount its root
10783 file system over NFS at boot time, say Y here and to "IP: kernel
10784 level autoconfiguration" above and to "Root file system on NFS"
10785 below. You cannot compile this driver as a module in this case.
10786 There are two packages designed for booting diskless machines over
10787 the net: netboot and etherboot, both available via FTP from
10788 ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
10790 If you don't know what all this is about, say N.
10792 Provide NFSv3 client support (EXPERIMENTAL)
10794 Say Y here if you want your NFS client to be able to speak the newer
10795 version 3 of the NFS protocol.
10799 Root file system on NFS
10801 If you want your Linux box to mount its whole root file system (the
10802 one containing the directory /) from some other computer over the
10803 net via NFS (presumably because your box doesn't have a hard disk),
10804 say Y. Read Documentation/nfsroot.txt for details. It is likely that
10805 in this case, you also want to say Y to "IP: kernel level
10806 autoconfiguration" so that your box can discover its network address
10809 Most people say N here.
10813 If you want your Linux box to act as an NFS *server*, so that other
10814 computers on your local network which support NFS can access certain
10815 directories on your box transparently, you have two options: you can
10816 use the self-contained user space program nfsd, in which case you
10817 should say N here, or you can say Y and use the kernel based NFS
10818 server. The advantage of the kernel based solution is that it is
10821 In either case, you will need support software; the respective
10822 locations are given in the file Documentation/Changes in the NFS
10825 If you say Y here, you will get support for version 2 of the NFS
10826 protocol (NFSv2). If you also want NFSv3, say Y to the next question
10829 Please read the NFS-HOWTO, available from
10830 http://www.linuxdoc.org/docs.html#howto .
10832 The NFS server is also available as a module ( = code which can be
10833 inserted in and removed from the running kernel whenever you want).
10834 The module is called nfsd.o. If you want to compile it as a module,
10835 say M here and read Documentation/modules.txt. If unsure, say N.
10837 Provide NFSv3 server support
10839 If you would like to include the NFSv3 server as well as the NFSv2
10840 server, say Y here. If unsure, say Y.
10842 Provide NFS over TCP server support DEVELOPER ONLY
10844 If you are a developer and want to work on fixing problems with
10845 NFS server over TCP support, say Y here. If unsure, say N.
10847 Some problems can be found by looking for FIXME in net/sunrpc/svcsock.c
10849 OS/2 HPFS file system support
10851 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
10852 is the file system used for organizing files on OS/2 hard disk
10853 partitions. Say Y if you want to be able to read files from and
10854 write files to an OS/2 HPFS partition on your hard drive. OS/2
10855 floppies however are in regular MSDOS format, so you don't need this
10856 option in order to be able to read them. Read
10857 Documentation/filesystems/hpfs.txt.
10859 This file system is also available as a module ( = code which can be
10860 inserted in and removed from the running kernel whenever you want).
10861 The module is called hpfs.o. If you want to compile it as a module,
10862 say M here and read Documentation/modules.txt. If unsure, say N.
10864 NTFS support (read only)
10866 NTFS is the file system of Microsoft Windows NT. Say Y if you want
10867 to get read access to files on NTFS partitions of your hard drive.
10868 The Linux NTFS driver supports most of the mount options of the VFAT
10869 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
10870 give you read-only access to NTFS partitions.
10872 This code is also available as a module ( = code which can be
10873 inserted in and removed from the running kernel whenever you want).
10874 The module will be called ntfs.o. If you want to compile it as a
10875 module, say M here and read Documentation/modules.txt.
10877 NTFS write support (DANGEROUS)
10879 If you say Y here, you will (maybe) be able to write to NTFS file
10880 systems as well as read from them. The read-write support in
10881 NTFS is far from being complete and is not well tested. If you
10882 say Y here, back up your NTFS volume first since it may get
10883 damaged. Also, make sure to run chkdsk from within Microsoft
10884 Windows NT after having performed any writes to a NTFS partition
10885 from Linux to detect any problems as early as possible.
10886 Please note that write support is limited to Windows NT4 and
10891 System V and Coherent file system support (read only)
10893 SCO, Xenix and Coherent are commercial Unix systems for Intel
10894 machines. Saying Y here would allow you to read from their floppies
10895 and hard disk partitions. If you also want to write to these media,
10896 say Y to "SYSV file system write support" below.
10898 If you have floppies or hard disk partitions like that, it is likely
10899 that they contain binaries from those other Unix systems; in order
10900 to run these binaries, you will want to install iBCS2 (Intel Binary
10901 Compatibility Standard is a kernel module which lets you run SCO,
10902 Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
10903 and is often needed to run commercial software that's only available
10904 for those systems. It's available via FTP (user: anonymous) from
10905 ftp://tsx-11.mit.edu/pub/linux/BETA ).
10907 If you only intend to mount files from some other Unix over the
10908 network using NFS, you don't need the System V file system support
10909 (but you need NFS file system support obviously).
10911 Note that this option is generally not needed for floppies, since a
10912 good portable way to transport files and directories between unixes
10913 (and even other operating systems) is given by the tar program ("man
10914 tar" or preferably "info tar"). Note also that this option has
10915 nothing whatsoever to do with the option "System V IPC". Read about
10916 the System V file system in Documentation/filesystems/sysv-fs.txt.
10917 Saying Y here will enlarge your kernel by about 27 KB.
10919 If you want to compile this as a module ( = code which can be
10920 inserted in and removed from the running kernel whenever you want),
10921 say M here and read Documentation/modules.txt. The module will be
10924 If you haven't heard about all of this before, it's safe to say N.
10926 SYSV file system write support (DANGEROUS)
10927 CONFIG_SYSV_FS_WRITE
10928 If you say Y here, you will be able to write to hard drive
10929 partitions and floppy disks which carry a SYSV file system used the
10930 commercial Unixes SCO, Xenix and Coherent.
10932 This support is experimental and you may destroy your data. If
10935 Amiga FFS file system support
10937 The Fast File System (FFS) is the common file system used on hard
10938 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
10939 if you want to be able to read and write files from and to an Amiga
10940 FFS partition on your hard drive. Amiga floppies however cannot be
10941 read with this driver due to an incompatibility of the floppy
10942 controller used in an Amiga and the standard floppy controller in
10943 PCs and workstations. Read Documentation/filesystems/affs.txt and
10946 With this driver you can also mount disk files used by Bernd
10947 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/ ).
10948 If you want to do this, you will also need to say Y or M to "Loop
10949 device support", above.
10951 This file system is also available as a module ( = code which can be
10952 inserted in and removed from the running kernel whenever you want).
10953 The module is called affs.o. If you want to compile it as a module,
10954 say M here and read Documentation/modules.txt. If unsure, say N.
10956 Apple Macintosh file system support (EXPERIMENTAL)
10958 If you say Y here, you will be able to mount Macintosh-formatted
10959 floppy disks and hard drive partitions with full read-write access.
10960 Please read fs/hfs/HFS.txt to learn about the available mount
10963 This file system support is also available as a module ( = code
10964 which can be inserted in and removed from the running kernel
10965 whenever you want). The module is called hfs.o. If you want to
10966 compile it as a module, say M here and read
10967 Documentation/modules.txt.
10969 ROM file system support
10971 This is a very small read-only file system mainly intended for
10972 initial ram disks of installation disks, but it could be used for
10973 other read-only media as well. Read
10974 Documentation/filesystems/romfs.txt for details.
10976 This file system support is also available as a module ( = code
10977 which can be inserted in and removed from the running kernel
10978 whenever you want). The module is called romfs.o. If you want to
10979 compile it as a module, say M here and read
10980 Documentation/modules.txt. Note that the file system of your root
10981 partition (the one containing the directory /) cannot be a module.
10983 If you don't know whether you need it, then you don't need it:
10986 QNX4 file system support (read only) (EXPERIMENTAL)
10988 This is the file system used by the operating system QNX 4. Say Y if
10989 you intend to mount QNX hard disks or floppies. Unless you say Y to
10990 "QNX4FS read-write support" below, you will only be able to read
10991 these file systems.
10993 This file system support is also available as a module ( = code
10994 which can be inserted in and removed from the running kernel
10995 whenever you want). The module is called qnx4.o. If you want to
10996 compile it as a module, say M here and read
10997 Documentation/modules.txt.
10999 If you don't know whether you need it, then you don't need it:
11002 QNX4FS write support (DANGEROUS)
11004 Say Y if you want to test write support for QNX4 file systems.
11006 Kernel automounter support
11008 The automounter is a tool to automatically mount remote file systems
11009 on demand. This implementation is partially kernel-based to reduce
11010 overhead in the already-mounted case; this is unlike the BSD
11011 automounter (amd), which is a pure user space daemon.
11013 To use the automounter you need the user-space tools from the autofs
11014 package; you can find the location in Documentation/Changes. You
11015 also want to answer Y to "NFS file system support", below.
11017 If you want to use the newer version of the automounter with more
11018 features, say N here and say Y to "Kernel automounter v4 support",
11021 If you want to compile this as a module ( = code which can be
11022 inserted in and removed from the running kernel whenever you want),
11023 say M here and read Documentation/modules.txt. The module will be
11026 If you are not a part of a fairly large, distributed network, you
11027 probably do not need an automounter, and can say N here.
11029 Kernel automounter v4 support
11031 The automounter is a tool to automatically mount remote file systems
11032 on demand. This implementation is partially kernel-based to reduce
11033 overhead in the already-mounted case; this is unlike the BSD
11034 automounter (amd), which is a pure user space daemon.
11036 To use the automounter you need the user-space tools from
11037 ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4 ; you also
11038 want to answer Y to "NFS file system support", below.
11040 If you want to compile this as a module ( = code which can be
11041 inserted in and removed from the running kernel whenever you want),
11042 say M here and read Documentation/modules.txt. The module will be
11043 called autofs4.o. You will need to add "alias autofs autofs4" to
11044 your modules configuration file.
11046 If you are not a part of a fairly large, distributed network or
11047 don't have a laptop which needs to dynamically reconfigure to the
11048 local network, you probably do not need an automounter, and can say
11051 EFS file system support (read-only) (EXPERIMENTAL)
11053 EFS is an older file system used for non-ISO9660 CDROMs and hard
11054 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
11055 uses the XFS file system for hard disk partitions however).
11057 This implementation only offers read-only access. If you don't know
11058 what all this is about, it's safe to say N. For more information
11059 about EFS see its home page at http://aeschi.ch.eu.org/efs/ .
11061 If you want to compile the EFS file system support as a module ( =
11062 code which can be inserted in and removed from the running kernel
11063 whenever you want), say M here and read Documentation/modules.txt.
11064 The module will be called efs.o.
11066 Journalling Flash File System (JFFS) support (EXPERIMENTAL)
11068 JFFS is a new file system designed for use on flash memory devices
11069 rather than on block devices. It was developed on the 2.0 kernel
11070 by Axis Communications AB for use on their Linux-based products,
11071 and released under GPL, then 'borrowed' and ported to work with
11072 the 2.4 kernel and the new Memory Technology Device system.
11074 The 2.4 port is experimental and not yet supported by Axis. Basically,
11075 the good bits are probably theirs, and if it's broken in 2.4 it's
11076 probably our fault. See http://www.developer.axis.com/software/jffs/
11077 for more information about JFFS.
11079 Any potential patches or queries should be sent to Axis' mailing
11080 list for JFFS: <jffs-dev@axis.com>
11082 UFS file system support (read-only)
11084 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
11085 OpenBSD and NeXTstep) use a file system called UFS. Some System V
11086 Unixes can create and mount hard disk partitions and diskettes using
11087 this file system as well. Saying Y here will allow you to read from
11088 these partitions; if you also want to write to them, say Y to the
11089 experimental "UFS file system write support", below. Please read the
11090 file Documentation/filesystems/ufs.txt for more information.
11092 If you only intend to mount files from some other Unix over the
11093 network using NFS, you don't need the UFS file system support (but
11094 you need NFS file system support obviously).
11096 Note that this option is generally not needed for floppies, since a
11097 good portable way to transport files and directories between unixes
11098 (and even other operating systems) is given by the tar program ("man
11099 tar" or preferably "info tar").
11101 When accessing NeXTstep files, you may need to convert them from the
11102 NeXT character set to the Latin1 character set; use the program
11103 recode ("info recode") for this purpose.
11105 If you want to compile the UFS file system support as a module ( =
11106 code which can be inserted in and removed from the running kernel
11107 whenever you want), say M here and read Documentation/modules.txt.
11108 The module will be called ufs.o.
11110 If you haven't heard about all of this before, it's safe to say N.
11112 UFS file system write support (DANGEROUS)
11113 CONFIG_UFS_FS_WRITE
11114 Say Y here if you want to try writing to UFS partitions. This is
11115 experimental, so you should back up your UFS partitions beforehand.
11117 Advanced partition selection
11118 CONFIG_PARTITION_ADVANCED
11119 Say Y here if you would like to use hard disks under Linux which
11120 were partitioned under an operating system running on a different
11121 architecture than your Linux system.
11123 Note that the answer to this question won't directly affect the
11124 kernel: saying N will just cause this configure script to skip all
11125 the questions about foreign partitioning schemes.
11129 Alpha OSF partition support
11130 CONFIG_OSF_PARTITION
11131 Say Y here if you would like to use hard disks under Linux which
11132 were partitioned on an Alpha machine.
11134 Macintosh partition map support
11135 CONFIG_MAC_PARTITION
11136 Say Y here if you would like to use hard disks under Linux which
11137 were partitioned on a Macintosh.
11139 PC BIOS (MSDOS partition tables) support
11140 CONFIG_MSDOS_PARTITION
11141 Say Y here if you would like to use hard disks under Linux which
11142 were partitioned on an x86 PC (not necessarily by DOS).
11144 BSD disklabel (FreeBSD partition tables) support
11145 CONFIG_BSD_DISKLABEL
11146 FreeBSD uses its own hard disk partition scheme on your PC. It
11147 requires only one entry in the primary partition table of your disk
11148 and manages it similarly to DOS extended partitions, putting in its
11149 first sector a new partition table in BSD disklabel format. Saying Y
11150 here allows you to read these disklabels and further mount FreeBSD
11151 partitions from within Linux if you have also said Y to "UFS
11152 file system support", above. If you don't know what all this is
11155 Sun partition tables support
11156 CONFIG_SUN_PARTITION
11157 Like most systems, SunOS uses its own hard disk partition table
11158 format, incompatible with all others. Saying Y here allows you to
11159 read these partition tables and further mount SunOS partitions from
11160 within Linux if you have also said Y to "UFS file system support",
11161 above. This is mainly used to carry data from a SPARC under SunOS to
11162 your Linux box via a removable medium like magneto-optical or ZIP
11163 drives; note however that a good portable way to transport files and
11164 directories between unixes (and even other operating systems) is
11165 given by the tar program ("man tar" or preferably "info tar"). If
11166 you don't know what all this is about, say N.
11168 Solaris (x86) partition table support
11169 CONFIG_SOLARIS_X86_PARTITION
11170 Like most systems, Solaris x86 uses its own hard disk partition
11171 table format, incompatible with all others. Saying Y here allows you
11172 to read these partition tables and further mount Solaris x86
11173 partitions from within Linux if you have also said Y to "UFS
11174 file system support", above.
11176 SGI partition support
11177 CONFIG_SGI_PARTITION
11178 Say Y here if you would like to be able to read the hard disk
11179 partition table format used by SGI machines.
11181 ADFS file system support (EXPERIMENTAL)
11183 The Acorn Disc Filing System is the standard file system of the
11184 RiscOS operating system which runs on Acorn's ARM-based Risc PC
11185 systems and the Acorn Archimedes range of machines. If you say Y
11186 here, Linux will be able to read from ADFS partitions on hard drives
11187 and from ADFS-formatted floppy discs. If you also want to be able to
11188 write to those devices, say Y to "ADFS write support" below.
11190 The ADFS partition should be the first partition (i.e.,
11191 /dev/[hs]d?1) on each of your drives. Please read the file
11192 Documentation/filesystems/adfs.txt for further details.
11194 This code is also available as a module called adfs.o ( = code which
11195 can be inserted in and removed from the running kernel whenever you
11196 want). If you want to compile it as a module, say M here and read
11197 Documentation/modules.txt.
11201 ADFS write support (DANGEROUS)
11203 If you say Y here, you will be able to write to ADFS partitions on
11204 hard drives and ADFS-formatted floppy disks. This is experimental
11205 codes, so if you're unsure, say N.
11207 /dev/pts file system for Unix98 PTYs
11209 You should say Y here if you said Y to "Unix98 PTY support" above.
11210 You'll then get a virtual file system which can be mounted on
11211 /dev/pts with "mount -t devpts". This, together with the pseudo
11212 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
11213 support as described in The Open Group's Unix98 standard: in order
11214 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
11215 of the pseudo terminal is then made available to the process and the
11216 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
11217 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
11219 The GNU C library glibc 2.1 contains the requisite support for this
11220 mode of operation; you also need client programs that use the Unix98
11221 API. Please read Documentation/Changes for more information about
11222 the Unix98 pty devices.
11224 Note that the experimental "/dev file system support"
11225 (CONFIG_DEVFS_FS) is a more general facility.
11227 UnixWare slices support (EXPERIMENTAL)
11228 CONFIG_UNIXWARE_DISKLABEL
11229 Like some systems, UnixWare uses its own slice table inside a
11230 partition (VTOC - Virtual Table of Contents). Its format is
11231 incompatible with all other OSes. Saying Y here allows you to read
11232 VTOC and further mount UnixWare partitions read-only from within
11233 Linux if you have also said Y to "UFS file system support" or
11234 "System V and Coherent file system support", above.
11236 This is mainly used to carry data from a UnixWare box to your
11237 Linux box via a removable medium like magneto-optical, ZIP or
11238 removable IDE drives. Note, however, that a good portable way to
11239 transport files and directories between unixes (and even other
11240 operating systems) is given by the tar program ("man tar" or
11241 preferably "info tar").
11243 If you don't know what all this is about, say N.
11245 SMB file system support (to mount Windows shares etc.)
11247 SMB (Server Message Block) is the protocol Windows for Workgroups
11248 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
11249 files and printers over local networks. Saying Y here allows you to
11250 mount their file systems (often called "shares" in this context) and
11251 access them just like any other Unix directory. Currently, this
11252 works only if the Windows machines use TCP/IP as the underlying
11253 transport protocol, and not NetBEUI. For details, read
11254 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available
11255 from http://www.linuxdoc.org/docs.html#howto .
11257 Note: if you just want your box to act as an SMB *server* and make
11258 files and printing services available to Windows clients (which need
11259 to have a TCP/IP stack), you don't need to say Y here; you can use
11260 the program samba (available via FTP (user: anonymous) in
11261 ftp://metalab.unc.edu/pub/Linux/system/network/samba ) for that.
11263 General information about how to connect Linux, Windows machines and
11264 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11266 If you want to compile the SMB support as a module ( = code which
11267 can be inserted in and removed from the running kernel whenever you
11268 want), say M here and read Documentation/modules.txt. The module
11269 will be called smbfs.o. Most people say N, however.
11271 nls support setting
11272 CONFIG_SMB_NLS_REMOTE
11273 This setting allows you to specify a default value for which
11274 codepage the server uses. If this field is left blank no
11275 translations will be done by default. The local codepage/charset
11276 default to CONFIG_NLS_DEFAULT.
11278 The nls settings can be changed at mount time, if your smbmount
11279 supports that, using the codepage and iocharset parameters.
11281 Currently no smbmount distributed with samba supports this, it is
11282 assumed future versions will. In the meantime you can get an
11283 unofficial patch for samba 2.0.7 from:
11284 http://www.hojdpunkten.ac.se/054/samba/index.html
11286 Coda file system support (advanced network fs)
11288 Coda is an advanced network file system, similar to NFS in that it
11289 enables you to mount file systems of a remote server and access them
11290 with regular Unix commands as if they were sitting on your hard
11291 disk. Coda has several advantages over NFS: support for disconnected
11292 operation (e.g. for laptops), read/write server replication,
11293 security model for authentication and encryption, persistent client
11294 caches and write back caching.
11296 If you say Y here, your Linux box will be able to act as a Coda
11297 *client*. You will need user level code as well, both for the client
11298 and server. Servers are currently user level, i.e. they need no
11299 kernel support. Please read Documentation/filesystems/coda.txt and
11300 check out the Coda home page http://www.coda.cs.cmu.edu .
11302 If you want to compile the coda client support as a module ( = code
11303 which can be inserted in and removed from the running kernel
11304 whenever you want), say M here and read Documentation/modules.txt.
11305 The module will be called coda.o.
11307 NCP file system support (to mount NetWare volumes)
11309 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
11310 used by Novell NetWare clients to talk to file servers. It is to IPX
11311 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
11312 mount NetWare file server volumes and to access them just like any
11313 other Unix directory. For details, please read the file
11314 Documentation/filesystems/ncpfs.txt in the kernel source and the
11315 IPX-HOWTO from http://www.linuxdoc.org/docs.html#howto .
11317 You do not have to say Y here if you want your Linux box to act as a
11318 file *server* for Novell NetWare clients.
11320 General information about how to connect Linux, Windows machines and
11321 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11323 If you want to compile this as a module ( = code which can be
11324 inserted in and removed from the running kernel whenever you want),
11325 say M here and read Documentation/modules.txt. The module will be
11326 called ncpfs.o. Say N unless you are connected to a Novell network.
11329 CONFIG_NCPFS_PACKET_SIGNING
11330 NCP allows packets to be signed for stronger security. If you want
11331 security, say Y. Normal users can leave it off. To be able to use
11332 packet signing you must use ncpfs > 2.0.12.
11334 Proprietary file locking
11335 CONFIG_NCPFS_IOCTL_LOCKING
11336 Allows locking of records on remote volumes. Say N unless you have
11337 special applications which are able to utilize this locking scheme.
11339 Clear remove/delete inhibit when needed
11340 CONFIG_NCPFS_STRONG
11341 Allows manipulation of files flagged as Delete or Rename Inhibit. To
11342 use this feature you must mount volumes with the ncpmount parameter
11343 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
11344 volumes with -f 444.
11346 Use NFS namespace when available
11347 CONFIG_NCPFS_NFS_NS
11348 Allows you to utilize NFS namespace on NetWare servers. It brings
11349 you case sensitive filenames. Say Y. You can disable it at
11350 mount-time with the `-N nfs' parameter of ncpmount.
11352 Use OS2/LONG namespace when available
11353 CONFIG_NCPFS_OS2_NS
11354 Allows you to utilize OS2/LONG namespace on NetWare servers.
11355 Filenames in this namespace are limited to 255 characters, they are
11356 case insensitive, and case in names is preserved. Say Y. You can
11357 disable it at mount time with the -N os2 parameter of ncpmount.
11359 Lowercase DOS filenames on LONG namespace volume
11360 CONFIG_NCPFS_SMALLDOS
11361 If you say Y here, every filename on a NetWare server volume using
11362 the OS2/LONG namespace and created under DOS or on a volume using
11363 DOS namespace will be converted to lowercase characters.
11364 Saying N here will give you these filenames in uppercase.
11366 This is only a cosmetic option since the OS2/LONG namespace is case
11367 insensitive. The only major reason for this option is backward
11368 compatibility when moving from DOS to OS2/LONG namespace support.
11369 Long filenames (created by Win95) will not be affected.
11371 This option does not solve the problem that filenames appear
11372 differently under Linux and under Windows, since Windows does an
11373 additional conversions on the client side. You can achieve similar
11374 effects by saying Y to "Allow using of Native Language Support"
11377 Allow mounting of volume subdirectories
11378 CONFIG_NCPFS_MOUNT_SUBDIR
11379 Allows you to mount not only whole servers or whole volumes, but
11380 also subdirectories from a volume. It can be used to reexport data
11381 and so on. There is no reason to say N, so Y is recommended unless
11382 you count every byte.
11384 To utilize this feature you must use ncpfs-2.0.12 or newer.
11386 NDS authentication support
11387 CONFIG_NCPFS_NDS_DOMAINS
11388 This allows storing NDS private keys in kernel space where they
11389 can be used to authenticate another server as interserver NDS
11390 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
11391 this feature. Say Y if you are using NDS connections to NetWare
11392 servers. Do not say Y if security is primary for you because root
11393 can read your session key (from /proc/kcore).
11395 Allow using of Native Language Support
11397 Allows you to use codepages and I/O charsets for file name
11398 translation between the server file system and input/output. This
11399 may be useful, if you want to access the server with other operating
11400 systems, e.g. Windows 95. See also NLS for more Information.
11402 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
11404 Symbolic links and mode permission bits
11405 CONFIG_NCPFS_EXTRAS
11406 This enables the use of symbolic links and an execute permission
11407 bit on NCPFS. The file server need not have long name space or NFS
11408 name space loaded for these to work.
11410 To use the new attributes, it is recommended to use the flags
11411 '-f 600 -d 755' on the ncpmount command line.
11413 nls default codepage
11415 The default NLS used when mounting filesystem. Currently, the valid
11417 big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
11418 cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
11419 cp949, cp950, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3,
11420 iso8859-4, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9,
11421 iso8859-14, iso8859-15, koi8-r, sjis
11422 If you specify a wrong value, it will use the built-in NLS; compatible
11425 If unsure, specify it as "iso8859-1".
11428 CONFIG_NLS_CODEPAGE_437
11429 The Microsoft FAT file system family can deal with filenames in
11430 native language character sets. These character sets are stored
11431 in so-called DOS codepages. You need to include the appropriate
11432 codepage if you want to be able to read/write these filenames on
11433 DOS/Windows partitions correctly. This does apply to the filenames
11434 only, not to the file contents. You can include several codepages;
11435 say Y here if you want to include the DOS codepage that is used in
11436 the United States and parts of Canada. This is recommended.
11439 CONFIG_NLS_CODEPAGE_737
11440 The Microsoft FAT file system family can deal with filenames in
11441 native language character sets. These character sets are stored
11442 in so-called DOS codepages. You need to include the appropriate
11443 codepage if you want to be able to read/write these filenames on
11444 DOS/Windows partitions correctly. This does apply to the filenames
11445 only, not to the file contents. You can include several codepages;
11446 say Y here if you want to include the DOS codepage that is used for
11447 Greek. If unsure, say N.
11450 CONFIG_NLS_CODEPAGE_775
11451 The Microsoft FAT file system family can deal with filenames in
11452 native language character sets. These character sets are stored
11453 in so-called DOS codepages. You need to include the appropriate
11454 codepage if you want to be able to read/write these filenames on
11455 DOS/Windows partitions correctly. This does apply to the filenames
11456 only, not to the file contents. You can include several codepages;
11457 say Y here if you want to include the DOS codepage that is used
11458 for the Baltic Rim Languages. If unsure, say N.
11461 CONFIG_NLS_CODEPAGE_850
11462 The Microsoft FAT file system family can deal with filenames in
11463 native language character sets. These character sets are stored in
11464 so-called DOS codepages. You need to include the appropriate
11465 codepage if you want to be able to read/write these filenames on
11466 DOS/Windows partitions correctly. This does apply to the filenames
11467 only, not to the file contents. You can include several codepages;
11468 say Y here if you want to include the DOS codepage that is used for
11469 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
11470 more countries here]. It has some characters useful to many European
11471 languages that are not part of the US codepage 437.
11476 CONFIG_NLS_CODEPAGE_852
11477 The Microsoft FAT file system family can deal with filenames in
11478 native language character sets. These character sets are stored in
11479 so-called DOS codepages. You need to include the appropriate
11480 codepage if you want to be able to read/write these filenames on
11481 DOS/Windows partitions correctly. This does apply to the filenames
11482 only, not to the file contents. You can include several codepages;
11483 say Y here if you want to include the Latin 2 codepage used by DOS
11484 for much of Central and Eastern Europe. It has all the required
11485 characters for these languages: Albanian, Croatian, Czech, English,
11486 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
11487 transcription), Slovak, Slovenian, and Sorbian.
11490 CONFIG_NLS_CODEPAGE_855
11491 The Microsoft FAT file system family can deal with filenames in
11492 native language character sets. These character sets are stored in
11493 so-called DOS codepages. You need to include the appropriate
11494 codepage if you want to be able to read/write these filenames on
11495 DOS/Windows partitions correctly. This does apply to the filenames
11496 only, not to the file contents. You can include several codepages;
11497 say Y here if you want to include the DOS codepage for Cyrillic.
11500 CONFIG_NLS_CODEPAGE_857
11501 The Microsoft FAT file system family can deal with filenames in
11502 native language character sets. These character sets are stored in
11503 so-called DOS codepages. You need to include the appropriate
11504 codepage if you want to be able to read/write these filenames on
11505 DOS/Windows partitions correctly. This does apply to the filenames
11506 only, not to the file contents. You can include several codepages;
11507 say Y here if you want to include the DOS codepage for Turkish.
11510 CONFIG_NLS_CODEPAGE_860
11511 The Microsoft FAT file system family can deal with filenames in
11512 native language character sets. These character sets are stored in
11513 so-called DOS codepages. You need to include the appropriate
11514 codepage if you want to be able to read/write these filenames on
11515 DOS/Windows partitions correctly. This does apply to the filenames
11516 only, not to the file contents. You can include several codepages;
11517 say Y here if you want to include the DOS codepage for Portuguese.
11520 CONFIG_NLS_CODEPAGE_861
11521 The Microsoft FAT file system family can deal with filenames in
11522 native language character sets. These character sets are stored in
11523 so-called DOS codepages. You need to include the appropriate
11524 codepage if you want to be able to read/write these filenames on
11525 DOS/Windows partitions correctly. This does apply to the filenames
11526 only, not to the file contents. You can include several codepages;
11527 say Y here if you want to include the DOS codepage for Icelandic.
11530 CONFIG_NLS_CODEPAGE_862
11531 The Microsoft FAT file system family can deal with filenames in
11532 native language character sets. These character sets are stored in
11533 so-called DOS codepages. You need to include the appropriate
11534 codepage if you want to be able to read/write these filenames on
11535 DOS/Windows partitions correctly. This does apply to the filenames
11536 only, not to the file contents. You can include several codepages;
11537 say Y here if you want to include the DOS codepage for Hebrew.
11540 CONFIG_NLS_CODEPAGE_863
11541 The Microsoft FAT file system family can deal with filenames in
11542 native language character sets. These character sets are stored in
11543 so-called DOS codepages. You need to include the appropriate
11544 codepage if you want to be able to read/write these filenames on
11545 DOS/Windows partitions correctly. This does apply to the filenames
11546 only, not to the file contents. You can include several codepages;
11547 say Y here if you want to include the DOS codepage for Canadian
11551 CONFIG_NLS_CODEPAGE_864
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 Arabic.
11561 CONFIG_NLS_CODEPAGE_865
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 the Nordic
11569 European countries.
11572 CONFIG_NLS_CODEPAGE_866
11573 The Microsoft FAT file system family can deal with filenames in
11574 native language character sets. These character sets are stored in
11575 so-called DOS codepages. You need to include the appropriate
11576 codepage if you want to be able to read/write these filenames on
11577 DOS/Windows partitions correctly. This does apply to the filenames
11578 only, not to the file contents. You can include several codepages;
11579 say Y here if you want to include the DOS codepage for
11583 CONFIG_NLS_CODEPAGE_869
11584 The Microsoft FAT file system family can deal with filenames in
11585 native language character sets. These character sets are stored in
11586 so-called DOS codepages. You need to include the appropriate
11587 codepage if you want to be able to read/write these filenames on
11588 DOS/Windows partitions correctly. This does apply to the filenames
11589 only, not to the file contents. You can include several codepages;
11590 say Y here if you want to include the DOS codepage for Greek.
11593 CONFIG_NLS_CODEPAGE_874
11594 The Microsoft FAT file system family can deal with filenames in
11595 native language character sets. These character sets are stored in
11596 so-called DOS codepages. You need to include the appropriate
11597 codepage if you want to be able to read/write these filenames on
11598 DOS/Windows partitions correctly. This does apply to the filenames
11599 only, not to the file contents. You can include several codepages;
11600 say Y here if you want to include the DOS codepage for Thai.
11603 CONFIG_NLS_CODEPAGE_932
11604 The Microsoft fat filesystem family can deal with filenames in
11605 native language character sets. These character sets are stored in
11606 so-called DOS codepages. You need to include the appropriate
11607 codepage if you want to be able to read/write these filenames on
11608 DOS/Windows partitions correctly. This does apply to the filenames
11609 only, not to the file contents. You can include several codepages;
11610 say Y here if you want to include the DOS codepage for Shift-JIS
11611 or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
11612 NLS Default value during kernel configuration , instead of 'cp932'
11615 CONFIG_NLS_CODEPAGE_936
11616 The Microsoft fat filesystem family can deal with filenames in
11617 native language character sets. These character sets are stored in
11618 so-called DOS codepages. You need to include the appropriate
11619 codepage if you want to be able to read/write these filenames on
11620 DOS/Windows partitions correctly. This does apply to the filenames
11621 only, not to the file contents. You can include several codepages;
11622 say Y here if you want to include the DOS codepage for Simplified
11626 CONFIG_NLS_CODEPAGE_949
11627 The Microsoft fat filesystem family can deal with filenames in
11628 native language character sets. These character sets are stored in
11629 so-called DOS codepages. You need to include the appropriate
11630 codepage if you want to be able to read/write these filenames on
11631 DOS/Windows partitions correctly. This does apply to the filenames
11632 only, not to the file contents. You can include several codepages;
11633 say Y here if you want to include the DOS codepage for UHC.
11636 CONFIG_NLS_CODEPAGE_950
11637 The Microsoft fat filesystem family can deal with filenames in
11638 native language character sets. These character sets are stored in
11639 so-called DOS codepages. You need to include the appropriate
11640 codepage if you want to be able to read/write these filenames on
11641 DOS/Windows partitions correctly. This does apply to the filenames
11642 only, not to the file contents. You can include several codepages;
11643 say Y here if you want to include the DOS codepage for Traditional
11647 CONFIG_NLS_ISO8859_1
11648 If you want to display filenames with native language characters
11649 from the Microsoft FAT file system family or from JOLIET CDROMs
11650 correctly on the screen, you need to include the appropriate
11651 input/output character sets. Say Y here for the Latin 1 character
11652 set, which covers most West European languages such as Albanian,
11653 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
11654 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
11655 and Swedish. It is also the default for the US. If unsure, say Y.
11658 CONFIG_NLS_ISO8859_2
11659 If you want to display filenames with native language characters
11660 from the Microsoft FAT file system family or from JOLIET CDROMs
11661 correctly on the screen, you need to include the appropriate
11662 input/output character sets. Say Y here for the Latin 2 character
11663 set, which works for most Latin-written Slavic and Central European
11664 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
11668 CONFIG_NLS_ISO8859_3
11669 If you want to display filenames with native language characters
11670 from the Microsoft FAT file system family or from JOLIET CDROMs
11671 correctly on the screen, you need to include the appropriate
11672 input/output character sets. Say Y here for the Latin 3 character
11673 set, which is popular with authors of Esperanto, Galician, Maltese,
11677 CONFIG_NLS_ISO8859_4
11678 If you want to display filenames with native language characters
11679 from the Microsoft FAT file system family or from JOLIET CDROMs
11680 correctly on the screen, you need to include the appropriate
11681 input/output character sets. Say Y here for the Latin 4 character
11682 set which introduces letters for Estonian, Latvian, and
11683 Lithuanian. It is an incomplete predecessor of Latin 6.
11686 CONFIG_NLS_ISO8859_5
11687 If you want to display filenames with native language characters
11688 from the Microsoft FAT file system family or from JOLIET CDROMs
11689 correctly on the screen, you need to include the appropriate
11690 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
11691 character set with which you can type Bulgarian, Byelorussian,
11692 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
11693 KOI8-R is preferred in Russia.
11696 CONFIG_NLS_ISO8859_6
11697 If you want to display filenames with native language characters
11698 from the Microsoft FAT file system family or from JOLIET CDROMs
11699 correctly on the screen, you need to include the appropriate
11700 input/output character sets. Say Y here for ISO8859-6, the Arabic
11704 CONFIG_NLS_ISO8859_7
11705 If you want to display filenames with native language characters
11706 from the Microsoft FAT file system family or from JOLIET CDROMs
11707 correctly on the screen, you need to include the appropriate
11708 input/output character sets. Say Y here for ISO8859-7, the Modern
11709 Greek character set.
11712 CONFIG_NLS_ISO8859_8
11713 If you want to display filenames with native language characters
11714 from the Microsoft FAT file system family or from JOLIET CDROMs
11715 correctly on the screen, you need to include the appropriate
11716 input/output character sets. Say Y here for ISO8859-8, the Hebrew
11720 CONFIG_NLS_ISO8859_9
11721 If you want to display filenames with native language characters
11722 from the Microsoft FAT file system family or from JOLIET CDROMs
11723 correctly on the screen, you need to include the appropriate
11724 input/output character sets. Say Y here for the Latin 5 character
11725 set, and it replaces the rarely needed Icelandic letters in Latin 1
11726 with the Turkish ones. Useful in Turkey.
11729 CONFIG_NLS_ISO8859_10
11730 If you want to display filenames with native language characters
11731 from the Microsoft FAT file system family or from JOLIET CDROMs
11732 correctly on the screen, you need to include the appropriate
11733 input/output character sets. Say Y here for the Latin 6 character
11734 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
11735 letters that were missing in Latin 4 to cover the entire Nordic
11738 NLS ISO 8859-14 (Latin 8; Celtic)
11739 CONFIG_NLS_ISO8859_14
11740 If you want to display filenames with native language characters
11741 from the Microsoft FAT file system family or from JOLIET CDROMs
11742 correctly on the screen, you need to include the appropriate
11743 input/output character sets. Say Y here for the Latin 8 character
11744 set, which adds the last accented vowels for Welsh (aka Cymraeg)
11745 (and Manx Gaelic) hat were missing in Latin 1.
11746 http://linux.speech.cymru.org/ has further information.
11749 CONFIG_NLS_ISO8859_15
11750 If you want to display filenames with native language characters
11751 from the Microsoft FAT file system family or from JOLIET CDROMs
11752 correctly on the screen, you need to include the appropriate
11753 input/output character sets. Say Y here for the Latin 9 character
11754 set, which covers most West European languages such as Albanian,
11755 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
11756 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
11757 Portuguese, Spanish, and Swedish. Latin 9 is an update to
11758 Latin 1 (ISO 8859-1) that removes a handful of rarely used
11759 characters and instead adds support for Estonian, corrects the
11760 support for French and Finnish, and adds the new Euro character. If
11765 If you want to display filenames with native language characters
11766 from the Microsoft FAT file system family or from JOLIET CDROMs
11767 correctly on the screen, you need to include the appropriate
11768 input/output character sets. Say Y here for the preferred Russian
11773 If you say Y here, you will get support for terminal devices with
11774 display and keyboard devices. These are called "virtual" because you
11775 can run several virtual terminals (also called virtual consoles) on
11776 one physical terminal. This is rather useful, for example one
11777 virtual terminal can collect system messages and warnings, another
11778 one can be used for a text-mode user session, and a third could run
11779 an X session, all in parallel. Switching between virtual terminals
11780 is done with certain key combinations, usually Alt-<function key>.
11782 The setterm command ("man setterm") can be used to change the
11783 properties (such as colors or beeping) of a virtual terminal. The
11784 man page console_codes(4) ("man console_codes") contains the special
11785 character sequences that can be used to change those properties
11786 directly. The fonts used on virtual terminals can be changed with
11787 the setfont ("man setfont") command and the key bindings are defined
11788 with the loadkeys ("man loadkeys") command.
11790 You need at least one virtual terminal device in order to make use
11791 of your keyboard and monitor. Therefore, only people configuring an
11792 embedded system would want to say N here in order to save some
11793 memory; the only way to log into such a system is then via a serial
11794 or network connection.
11796 If unsure, say Y, or else you won't be able to do much with your new
11797 shiny Linux system :-)
11799 Support for console on virtual terminal
11801 The system console is the device which receives all kernel messages
11802 and warnings and which allows logins in single user mode. If you
11803 answer Y here, a virtual terminal (the device used to interact with
11804 a physical terminal) can be used as system console. This is the most
11805 common mode of operations, so you should say Y here unless you want
11806 the kernel messages be output only to a serial port (in which case
11807 you should say Y to "Console on serial port", below).
11809 If you do say Y here, by default the currently visible virtual
11810 terminal (/dev/tty0) will be used as system console. You can change
11811 that with a kernel command line option such as "console=tty3" which
11812 would use the third virtual terminal as system console. (Try "man
11813 bootparam" or see the documentation of your boot loader (lilo or
11814 loadlin) about how to pass options to the kernel at boot time.)
11818 Support for PowerMac keyboard
11819 CONFIG_MAC_KEYBOARD
11820 This option allows you to use an ADB keyboard attached to your
11821 machine. Note that this disables any other (ie. PS/2) keyboard
11822 support, even if your machine is physically capable of using both at
11825 If you use an ADB keyboard (4 pin connector), say Y here.
11826 If you use a PS/2 keyboard (6 pin connector), say N here.
11828 Standard/generic serial support
11830 This selects whether you want to include the driver for the standard
11831 serial ports. The standard answer is Y. People who might say N here
11832 are those that are setting up dedicated Ethernet WWW/FTP servers, or
11833 users that have one of the various bus mice instead of a serial
11834 mouse and don't intend to use their machine's standard serial port
11835 for anything. (Note that the Cyclades and Stallion multi serial port
11836 drivers do not need this driver built in for them to work.)
11838 If you want to compile this driver as a module, say M here and read
11839 Documentation/modules.txt. The module will be called serial.o.
11840 [WARNING: Do not compile this driver as a module if you are using
11841 non-standard serial ports, since the configuration information will
11842 be lost when the driver is unloaded. This limitation may be lifted
11845 BTW1: If you have a mouseman serial mouse which is not recognized by
11846 the X window system, try running gpm first.
11848 BTW2: If you intend to use a software modem (also called Winmodem)
11849 under Linux, forget it. These modems are crippled and require
11850 proprietary drivers which are only available under Windows.
11852 Most people will say Y or M here, so that they can use serial mice,
11853 modems and similar devices connecting to the standard serial ports.
11855 Support for console on serial port
11856 CONFIG_SERIAL_CONSOLE
11857 If you say Y here, it will be possible to use a serial port as the
11858 system console (the system console is the device which receives all
11859 kernel messages and warnings and which allows logins in single user
11860 mode). This could be useful if some terminal or printer is connected
11861 to that serial port.
11863 Even if you say Y here, the currently visible virtual console
11864 (/dev/tty0) will still be used as the system console by default, but
11865 you can alter that using a kernel command line option such as
11866 "console=ttyS1". (Try "man bootparam" or see the documentation of
11867 your boot loader (lilo or loadlin) about how to pass options to the
11868 kernel at boot time.)
11870 If you don't have a VGA card installed and you say Y here, the
11871 kernel will automatically use the first serial line, /dev/ttyS0, as
11876 Support for PowerMac serial ports
11878 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
11879 here. If you also have regular serial ports and enable the driver
11880 for them, you can't currently use the serial console feature.
11882 Comtrol Rocketport support
11884 This is a driver for the Comtrol Rocketport cards which provide
11885 multiple serial ports. You would need something like this to connect
11886 more than two modems to your Linux box, for instance in order to
11887 become a dial-in server.
11889 If you want to compile this driver as a module, say M here and read
11890 Documentation/modules.txt. The module will be called rocket.o.
11892 Digiboard Intelligent async support
11894 This is a driver for Digi International's Xx, Xeve, and Xem series
11895 of cards which provide multiple serial ports. You would need
11896 something like this to connect more than two modems to your Linux
11897 box, for instance in order to become a dial-in server. This driver
11898 supports the original PC (ISA) boards as well as PCI, and EISA. If
11899 you have a card like this, say Y here and read the file
11900 Documentation/digiepca.txt.
11902 NOTE: There is another, separate driver for the Digiboard PC boards:
11903 "Digiboard PC/Xx Support" below. You should (and can) only select
11904 one of the two drivers.
11906 If you want to compile this driver as a module, say M here and read
11907 Documentation/modules.txt. The module will be called epca.o.
11909 Digiboard PC/Xx Support
11911 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
11912 that give you many serial ports. You would need something like this
11913 to connect more than two modems to your Linux box, for instance in
11914 order to become a dial-in server. If you have a card like that, say
11915 Y here and read the file Documentation/digiboard.txt.
11917 If you want to compile this driver as a module, say M here and read
11918 Documentation/modules.txt. The module will be called pcxx.o.
11920 SDL RISCom/8 card support
11922 This is a driver for the SDL Communications RISCom/8 multiport card,
11923 which gives you many serial ports. You would need something like
11924 this to connect more than two modems to your Linux box, for instance
11925 in order to become a dial-in server. If you have a card like that,
11926 say Y here and read the file Documentation/riscom8.txt.
11928 Also it's possible to say M here and compile this driver as kernel
11929 loadable module; the module will be called riscom8.o.
11931 Computone IntelliPort Plus serial support
11933 This driver supports the entire family of Intelliport II/Plus
11934 controllers with the exception of the MicroChannel controllers and
11935 products previous to the Intelliport II. These are multiport cards,
11936 which give you many serial ports. You would need something like
11937 this to connect more than two modems to your Linux box, for
11938 instance in order to become a dial-in server. If you have a
11939 card like that, say Y here and read Documentation/computone.txt.
11941 If you want to compile this as a module ( = code which can be
11942 inserted in and removed from the running kernel whenever you want),
11943 say M here and read Documentation/modules.txt. You will get two
11944 modules called ip2.o and ip2main.o.
11946 Specialix IO8+ card support
11948 This is a driver for the Specialix IO8+ multiport card (both the
11949 ISA and the PCI version) which gives you many serial ports. You
11950 would need something like this to connect more than two modems to
11951 your Linux box, for instance in order to become a dial-in server.
11953 If you have a card like that, say Y here and read the file
11954 Documentation/specialix.txt. Also it's possible to say M here and
11955 compile this driver as kernel loadable module which will be called
11958 Specialix DTR/RTS pin is RTS
11959 CONFIG_SPECIALIX_RTSCTS
11960 The Specialix card can only support either RTS or DTR. If you say N
11961 here, the driver will use the pin as "DTR" when the tty is in
11962 software handshake mode. If you say Y here or hardware handshake is
11963 on, it will always be RTS. Read the file Documentation/specialix.txt
11964 for more information.
11966 Cyclades async mux support
11968 This is a driver for a card that gives you many serial ports. You
11969 would need something like this to connect more than two modems to
11970 your Linux box, for instance in order to become a dial-in server.
11971 For information about the Cyclades-Z card, read
11972 drivers/char/README.cycladesZ.
11974 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
11977 If you want to compile this as a module ( = code which can be
11978 inserted in and removed from the running kernel whenever you want),
11979 say M here and read Documentation/modules.txt. The module will be
11982 If you haven't heard about it, it's safe to say N.
11984 Cyclades-Z interrupt mode operation (EXPERIMENTAL)
11986 The Cyclades-Z family of multiport cards allows 2 (two) driver op
11987 modes: polling and interrupt. In polling mode, the driver will check
11988 the status of the Cyclades-Z ports every certain amount of time
11989 (which is called polling cycle and is configurable). In interrupt
11990 mode, it will use an interrupt line (IRQ) in order to check the
11991 status of the Cyclades-Z ports. The default op mode is polling. If
11994 Stallion multiport serial support
11996 Stallion cards give you many serial ports. You would need something
11997 like this to connect more than two modems to your Linux box, for
11998 instance in order to become a dial-in server. If you say Y here, you
11999 will be asked for your specific card model in the next questions.
12000 Make sure to read drivers/char/README.stallion in this case. If you
12001 have never heard about all this, it's safe to say N.
12003 Stallion EasyIO or EC8/32 support
12005 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
12006 card, then this is for you; say Y. Make sure to read
12007 Documentation/stallion.txt.
12009 If you want to compile this as a module ( = code which can be
12010 inserted in and removed from the running kernel whenever you want),
12011 say M here and read Documentation/modules.txt. The module will be
12014 Stallion EC8/64, ONboard, Brumby support
12016 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
12017 serial multiport card, say Y here. Make sure to read
12018 Documentation/stallion.txt.
12020 To compile it as a module ( = code which can be inserted in and
12021 removed from the running kernel whenever you want), say M here and
12022 read Documentation/modules.txt. The module will be called
12025 Microgate SyncLink adapter support
12027 Provides support for the SyncLink ISA and PCI
12028 multiprotocol serial adapters. These adapters
12029 support asynchronous and HDLC bit synchronous
12030 communication up to 10Mbps (PCI adapter).
12032 This driver can only be built as a module ( = code which can be
12033 inserted in and removed from the running kernel whenever you want).
12034 The module will be called synclink.o. If you want to do that, say M
12037 Synchronous HDLC line discipline support
12039 Allows synchronous HDLC communications with tty device drivers that
12040 support synchronous HDLC such as the Microgate SyncLink adapter.
12042 This driver can only be built as a module ( = code which can be
12043 inserted in and removed from the running kernel whenever you want).
12044 The module will be called n_hdlc.o. If you want to do that, say M
12047 Specialix SX (and SI) card support
12049 This is a driver for the SX and SI multiport serial cards.
12050 Please read the file Documentation/sx.txt for details.
12052 This driver can only be built as a module ( = code which can be
12053 inserted in and removed from the running kernel whenever you want).
12054 The module will be called sx.o. If you want to do that, say M here.
12056 Hayes ESP serial port support
12058 This is a driver which supports Hayes ESP serial ports. Both single
12059 port cards and multiport cards are supported. Make sure to read
12060 Documentation/hayes-esp.txt.
12062 To compile this driver as a module ( = code which can be inserted in
12063 and removed from the running kernel whenever you want), say M here
12064 and read Documentation/modules.txt. The module will be called esp.o.
12067 Moxa Intellio support
12068 CONFIG_MOXA_INTELLIO
12069 Say Y here if you have a Moxa Intellio multiport serial card.
12071 This driver can also be built as a module ( = code which can be
12072 inserted in and removed from the running kernel whenever you want).
12073 The module will be called moxa.o. If you want to do that, say M
12076 Moxa SmartIO support
12077 CONFIG_MOXA_SMARTIO
12078 Say Y here if you have a Moxa SmartIO multiport serial card.
12080 This driver can also be built as a module ( = code which can be
12081 inserted in and removed from the running kernel whenever you want).
12082 The module will be called mxser.o. If you want to do that, say M
12085 Multi-Tech multiport card support (EXPERIMENTAL)
12087 This is a driver for the Multi-Tech cards which provide several
12088 serial ports. The driver is experimental and can currently only be
12089 built as a module ( = code which can be inserted in and removed from
12090 the running kernel whenever you want). Please read
12091 Documentation/modules.txt. The module will be called isicom.o
12095 A pseudo terminal (PTY) is a software device consisting of two
12096 halves: a master and a slave. The slave device behaves identical to
12097 a physical terminal; the master device is used by a process to
12098 read data from and write data to the slave, thereby emulating a
12099 terminal. Typical programs for the master side are telnet servers
12102 Linux has traditionally used the BSD-like names /dev/ptyxx for
12103 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
12104 has a number of problems. The GNU C library glibc 2.1 and later,
12105 however, supports the Unix98 naming standard: in order to acquire a
12106 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
12107 terminal is then made available to the process and the pseudo
12108 terminal slave can be accessed as /dev/pts/<number>. What was
12109 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
12111 The entries in /dev/pts/ are created on the fly by a virtual
12112 file system; therefore, if you say Y here you should say Y to
12113 "/dev/pts file system for Unix98 PTYs" as well.
12115 If you want to say Y here, you need to have the C library glibc 2.1
12116 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
12117 Read the instructions in Documentation/Changes pertaining to pseudo
12118 terminals. It's safe to say N.
12120 Maximum number of Unix98 PTYs in use (0-2048)
12121 CONFIG_UNIX98_PTY_COUNT
12122 The maximum number of Unix98 PTYs that can be used at any one time.
12123 The default is 256, and should be enough for desktop systems. Server
12124 machines which support incoming telnet/rlogin/ssh connections and/or
12125 serve several X terminals may want to increase this: every incoming
12126 connection and every xterm uses up one PTY.
12128 When not in use, each additional set of 256 PTYs occupy
12129 approximately 8 KB of kernel memory on 32-bit architectures.
12131 Parallel printer support
12133 If you intend to attach a printer to the parallel port of your Linux
12134 box (as opposed to using a serial printer; if the connector at the
12135 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
12136 read the Printing-HOWTO, available from
12137 http://www.linuxdoc.org/docs.html#howto .
12139 It is possible to share one parallel port among several devices
12140 (e.g. printer and ZIP drive) and it is safe to compile the
12141 corresponding drivers into the kernel. If you want to compile this
12142 driver as a module however ( = code which can be inserted in and
12143 removed from the running kernel whenever you want), say M here and
12144 read Documentation/modules.txt and Documentation/parport.txt. The
12145 module will be called lp.o.
12147 If you have several parallel ports, you can specify which ports to
12148 use with the "lp" kernel command line option. (Try "man bootparam"
12149 or see the documentation of your boot loader (lilo or loadlin) about
12150 how to pass options to the kernel at boot time.) The syntax of the
12151 "lp" command line option can be found in drivers/char/lp.c.
12153 If you have more than 3 printers, you need to increase the LP_NO
12156 Support for console on line printer
12158 If you want kernel messages to be printed out as they occur, you
12159 can have a console on the printer. This option adds support for
12160 doing that; to actually get it to happen you need to pass the
12161 option "console=lp0" to the kernel at boot time.
12163 Note that kernel messages can get lost if the printer is out of
12164 paper (or off, or unplugged, or too busy..), but this behaviour
12165 can be changed. See drivers/char/lp.c (do this at your own risk).
12169 Support for user-space parallel port device drivers
12171 Saying Y to this adds support for /dev/parport device nodes. This
12172 is needed for programs that want portable access to the parallel
12173 port, for instance deviceid (which displays Plug-and-Play device
12176 This is the parallel port equivalent of SCSI generic support (sg).
12177 It is safe to say N to this -- it is not needed for normal printing
12178 or parallel port CD-ROM/disk support.
12180 This support is also available as a module. If you want to compile
12181 it as a module, say M here and read Documentation/modules.txt. The
12182 module will be called ppdev.o.
12188 I2C (pronounce: I-square-C) is a slow serial bus protocol used in
12189 many micro controller applications and developed by Philips. SMBus,
12190 or System Management Bus is a subset of the I2C protocol. More
12191 information is contained in the directory Documentation/i2c/,
12192 especially in the file called "summary" there.
12194 Both I2C and SMBus are supported here. You will need this for
12195 hardware sensors support, and also for Video for Linux support.
12196 Specifically, if you want to use a BT848 based frame grabber/overlay
12197 boards under Linux, say Y here and also to "I2C bit-banging
12198 interfaces", below.
12200 If you want I2C support, you should say Y here and also to the
12201 specific driver for your bus adapter(s) below. If you say Y to
12202 "/proc file system" below, you will then get a /proc interface which
12203 is documented in Documentation/i2c/proc-interface.
12205 This I2C support is also available as a module. If you want to
12206 compile it as a module, say M here and read
12207 Documentation/modules.txt. The module will be called i2c-core.o.
12209 I2C bit-banging interfaces
12211 This allows you to use a range of I2C adapters called bit-banging
12212 adapters. Say Y if you own an I2C adapter belonging to this class
12213 and then say Y to the specific driver for you adapter below.
12215 This support is also available as a module. If you want to compile
12216 it as a module, say M here and read Documentation/modules.txt. The
12217 module will be called i2c-algo-bit.o.
12219 Philips style parallel port adapter
12220 CONFIG_I2C_PHILIPSPAR
12221 This supports parallel-port I2C adapters made by Philips. Say Y if
12222 you own such an adapter.
12224 This driver is also available as a module. If you want to compile
12225 it as a module, say M here and read Documentation/modules.txt. The
12226 module will be called i2c-philips-par.o.
12228 Note that if you want support for different parallel port devices,
12229 life will be much easier if you compile them all as modules.
12233 This supports parallel-port I2C adapters called ELV. Say Y if you
12234 own such an adapter.
12236 This driver is also available as a module. If you want to compile
12237 it as a module, say M here and read Documentation/modules.txt. The
12238 module will be called i2c-elv.o.
12240 Velleman K9000 adapter
12241 CONFIG_I2C_VELLEMAN
12242 This supports the Velleman K9000 parallel-port I2C adapter. Say Y if
12243 you own such an adapter.
12245 This driver is also available as a module. If you want to compile
12246 it as a module, say M here and read Documentation/modules.txt. The
12247 module will be called i2c-velleman.o.
12249 I2C PCF 8584 interfaces
12251 This allows you to use a range of I2C adapters called PCF adapters.
12252 Say Y if you own an I2C adapter belonging to this class and then say
12253 Y to the specific driver for you adapter below.
12255 This support is also available as a module. If you want to compile
12256 it as a module, say M here and read Documentation/modules.txt. The
12257 module will be called i2c-algo-pcf.o.
12261 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own such
12264 This driver is also available as a module. If you want to compile
12265 it as a module, say M here and read Documentation/modules.txt. The
12266 module will be called i2c-elektor.o.
12268 I2C device interface
12270 Say Y here to use i2c-* device files, usually found in the /dev
12271 directory on your system. They make it possible to have user-space
12272 programs use the I2C bus. Information on how to do this is contained
12273 in the file Documentation/i2c/dev-interface.
12275 This code is also available as a module. If you want to compile
12276 it as a module, say M here and read Documentation/modules.txt. The
12277 module will be called i2c-dev.o.
12281 Say Y here if your machine has a bus mouse as opposed to a serial
12282 mouse. Most people have a regular serial MouseSystem or
12283 Microsoft mouse (made by Logitech) that plugs into a COM port
12284 (rectangular with 9 or 25 pins). These people say N here. If you
12285 have something else, read the Busmouse-HOWTO, available from
12286 http://www.linuxdoc.org/docs.html#howto , and say Y here.
12288 If you have a laptop, you either have to check the documentation or
12289 experiment a bit to find out whether the trackball is a serial mouse
12290 or not; it's best to say Y here for you.
12292 This is the generic bus mouse driver code. If you have a bus mouse,
12293 you will have to say Y here and also to the specific driver for your
12296 This code is also available as a module ( = code which can be
12297 inserted in and removed from the running kernel whenever you want).
12298 The module will be called busmouse.o. If you want to compile it as a
12299 module, say M here and read Documentation/modules.txt.
12301 Mouse Support (not serial and bus mice)
12303 This is for machines with a mouse which is neither a serial nor a
12304 bus mouse. Examples are PS/2 mice (such as the track balls on some
12305 laptops) and some digitizer pads. Most people have a regular serial
12306 MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
12307 COM port (rectangular with 9 or 25 pins). These people say N here.
12308 If you have something else, read the Busmouse-HOWTO, available from
12309 http://www.linuxdoc.org/docs.html#howto . This HOWTO contains
12310 information about all non-serial mice, not just bus mice.
12312 If you have a laptop, you either have to check the documentation or
12313 experiment a bit to find out whether the trackball is a serial mouse
12314 or not; it's best to say Y here for you.
12316 Note that the answer to this question won't directly affect the
12317 kernel: saying N will just cause this configure script to skip all
12318 the questions about non-serial mice. If unsure, say Y.
12320 Logitech busmouse support
12321 CONFIG_LOGIBUSMOUSE
12322 Logitech mouse connected to a proprietary interface card. It's
12323 generally a round connector with 9 pins. Note that the newer mice
12324 made by Logitech don't use the Logitech protocol anymore; for those,
12325 you don't need this option. You want to read the Busmouse-HOWTO ,
12326 available from http://www.linuxdoc.org/docs.html#howto .
12328 If you want to compile this as a module ( = code which can be
12329 inserted in and removed from the running kernel whenever you want),
12330 say M here and read Documentation/modules.txt. The module will be
12331 called busmouse.o. If you are unsure, say N and read the HOWTO
12332 nevertheless: it will tell you what you have.
12334 PS/2 mouse (aka "auxiliary device") support
12336 The PS/2 mouse connects to a special mouse port that looks much like
12337 the keyboard port (small circular connector with 6 pins). This way,
12338 the mouse does not use any serial ports. This port can also be used
12339 for other input devices like light pens, tablets, keypads. Compaq,
12340 AST and IBM all use this as their mouse port on currently shipping
12341 machines. The trackballs of some laptops are PS/2 mice also. In
12342 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
12344 Although PS/2 mice are not technically bus mice, they are explained
12345 in detail in the Busmouse-HOWTO, available from
12346 http://www.linuxdoc.org/docs.html#howto .
12348 When using a PS/2 mouse, you can get problems if you want to use the
12349 mouse both on the Linux console and under X. Using the "-R" option
12350 of the Linux mouse managing program gpm (available from
12351 ftp://metalab.unc.edu/pub/Linux/system/mouse ) solves this
12352 problem, or you can get the "mconv2" utility from the same location.
12354 C&T 82C710 mouse port support (as on TI Travelmate)
12355 CONFIG_82C710_MOUSE
12356 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
12357 you are unsure, try first to say N here and come back if the mouse
12358 doesn't work. Read the Busmouse-HOWTO, available from
12359 http://www.linuxdoc.org/docs.html#howto .
12361 PC110 digitizer pad support
12363 This drives the digitizer pad on the IBM PC110 palmtop. It can turn
12364 the digitizer pad into a PS/2 mouse emulation with tap gestures or
12365 into an absolute pad.
12367 If you want to compile this as a module ( = code which can be
12368 inserted in and removed from the running kernel whenever you want),
12369 say M here and read Documentation/modules.txt. The module will be
12372 Microsoft busmouse support
12374 These animals (also called Inport mice) are connected to an
12375 expansion board using a round connector with 9 pins. If this is what
12376 you have, say Y and read the Busmouse-HOWTO, available from
12377 http://www.linuxdoc.org/docs.html#howto .
12379 If you are unsure, say N and read the HOWTO nevertheless: it will
12380 tell you what you have. Also be aware that several vendors talk
12381 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
12382 count the pins on the connector.
12384 If you want to compile this as a module ( = code which can be
12385 inserted in and removed from the running kernel whenever you want),
12386 say M here and read Documentation/modules.txt. The module will be
12387 called msbusmouse.o.
12389 Apple Desktop Bus mouse support
12391 Say Y here if you have this type of bus mouse (4 pin connector) as
12392 is common on Macintoshes. You may want to read the Busmouse-HOWTO,
12393 available from http://www.linuxdoc.org/docs.html#howto .
12395 If you want to compile this as a module ( = code which can be
12396 inserted in and removed from the running kernel whenever you want),
12397 say M here and read Documentation/modules.txt. The module will be
12400 ATIXL busmouse support
12401 CONFIG_ATIXL_BUSMOUSE
12402 This is a rare type of busmouse that is connected to the back of an
12403 ATI video card. Say Y if you have one of those. Note however that
12404 most mice by ATI are actually Microsoft busmice; you should say Y to
12405 "Microsoft busmouse support" above if you have one of those. Read
12406 the Busmouse-HOWTO, available from
12407 http://www.linuxdoc.org/docs.html#howto .
12409 If you want to compile this as a module ( = code which can be
12410 inserted in and removed from the running kernel whenever you want),
12411 say M here and read Documentation/modules.txt. The module will be
12412 called atixlmouse.o.
12414 If you are unsure, say N and read the HOWTO nevertheless: it will
12415 tell you what you have.
12417 QIC-02 tape support
12419 If you have a non-SCSI tape drive like that, say Y. Or, if you want
12420 to compile this driver as a module ( = code which can be inserted in
12421 and removed from the running kernel whenever you want), say M here
12422 and read Documentation/modules.txt. The module will be called
12425 Do you want runtime configuration for QIC-02
12426 CONFIG_QIC02_DYNCONF
12427 You can either configure this driver once and for all by editing a
12428 header file (include/linux/tpqic02.h), in which case you should
12429 say N, or you can fetch a program via anonymous FTP which is able
12430 to configure this driver during runtime. The program to do this is
12431 called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
12434 If you want to use the qic02conf program, say Y.
12436 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
12438 If you have a tape drive that is connected to your floppy
12439 controller, say Y here.
12441 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
12442 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
12443 controller of their own. These drives (and their companion
12444 controllers) are also supported if you say Y here.
12446 If you have a special controller (such as the CMS FC-10, FC-20,
12447 Mountain Mach-II, or any controller that is based on the Intel 82078
12448 FDC like the high speed controllers by Seagate and Exabyte and
12449 Iomega's "Ditto Dash") you must configure it by selecting the
12450 appropriate entries from the "Floppy tape controllers" sub-menu
12451 below and possibly modify the default values for the IRQ and DMA
12452 channel and the IO base in ftape's configuration menu.
12454 If you want to use your floppy tape drive on a PCI-bus based system,
12455 please read the file drivers/char/ftape/README.PCI.
12457 The ftape kernel driver is also available as a runtime loadable
12458 module ( = code which can be inserted in and removed from the
12459 running kernel whenever you want). If you want to compile it as a
12460 module, say M here and read Documentation/modules.txt. The module
12461 will be called ftape.o.
12463 Note that the Ftape-HOWTO is out of date (sorry) and documents the
12464 older version 2.08 of this software but still contains useful
12465 information. There is a web page with more recent documentation at
12466 http://www.math1.rwth-aachen.de/~heine/ftape/ . This page
12467 always contains the latest release of the ftape driver and useful
12468 information (backup software, ftape related patches and
12469 documentation, FAQ). Note that the file system interface has changed
12470 quite a bit compared to previous versions of ftape. Please read
12471 Documentation/ftape.txt.
12473 The file system interface for ftape
12475 Normally, you want to say Y or M. DON'T say N here or you
12476 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
12478 The ftape module itself no longer contains the routines necessary
12479 to interface with the kernel VFS layer (i.e. to actually write data
12480 to and read data from the tape drive). Instead the file system
12481 interface (i.e. the hardware independent part of the driver) has
12482 been moved to a separate module.
12484 If you say M zftape will be compiled as a runtime loadable
12485 module ( = code which can be inserted in and removed from the
12486 running kernel whenever you want). In this case you should read
12487 Documentation/modules.txt. The module will be called zftape.o.
12489 Regardless of whether you say Y or M here, an additional runtime
12490 loadable module called `zft-compressor.o' which contains code to
12491 support user transparent on-the-fly compression based on Ross
12492 William's lzrw3 algorithm will be produced. If you have enabled the
12493 kernel module loader (i.e. have said Y to "Kernel module loader
12494 support", above) then `zft-compressor.o' will be loaded
12495 automatically by zftape when needed.
12497 Despite its name, zftape does NOT use compression by default. The
12498 file Documentation/ftape.txt contains a short description of the
12499 most important changes in the file system interface compared to
12500 previous versions of ftape. The ftape home page
12501 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
12502 further information.
12504 IMPORTANT NOTE: zftape can read archives created by previous
12505 versions of ftape and provide file mark support (i.e. fast skipping
12506 between tape archives) but previous version of ftape will lack file
12507 mark support when reading archives produced by zftape.
12509 Default block size for zftape
12510 CONFIG_ZFT_DFLT_BLK_SZ
12511 If unsure leave this at its default value, i.e. 10240. Note that
12512 you specify only the default block size here. The block size can be
12513 changed at run time using the MTSETBLK tape operation with the
12514 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
12515 shell command line).
12517 The probably most striking difference between zftape and previous
12518 versions of ftape is the fact that all data must be written or read
12519 in multiples of a fixed block size. The block size defaults to
12520 10240 which is what GNU tar uses. The values for the block size
12521 should be either 1 or multiples of 1024 up to a maximum value of
12522 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
12523 compression will be disabled.
12525 Reasonable values are `10240' (GNU tar's default block size),
12526 `5120' (afio's default block size), `32768' (default block size some
12527 backup programs assume for SCSI tape drives) or `1' (no restriction
12528 on block size, but disables builtin compression).
12530 Number of DMA buffers
12531 CONFIG_FT_NR_BUFFERS
12532 Please leave this at `3' unless you REALLY know what you are doing.
12533 It is not necessary to change this value. Values below 3 make the
12534 proper use of ftape impossible, values greater than 3 are a waste of
12535 memory. You can change the amount of DMA memory used by ftape at
12536 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
12537 wastes 32 KB of memory. Please note that this memory cannot be
12540 Procfs entry for ftape
12542 Optional. Saying Y will result in creation of a directory
12543 `/proc/ftape' under the /proc file system. The files can be viewed
12544 with your favorite pager (i.e. use "more /proc/ftape/history" or
12545 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
12546 file will contain some status information about the inserted
12547 cartridge, the kernel driver, your tape drive, the floppy disk
12548 controller and the error history for the most recent use of the
12549 kernel driver. Saying Y will enlarge the size of the ftape driver
12550 by approximately 2 KB.
12552 WARNING: When compiling ftape as a module (i.e. saying M to "Floppy
12553 tape drive") it is dangerous to use ftape's /proc file system
12554 interface. Accessing `/proc/ftape' while the module is unloaded will
12555 result in a kernel Oops. This cannot be fixed from inside ftape.
12557 Controlling the amount of debugging output of ftape
12558 CONFIG_FT_NORMAL_DEBUG
12559 This option controls the amount of debugging output the ftape driver
12560 is ABLE to produce; it does not increase or diminish the debugging
12561 level itself. If unsure, leave this at its default setting,
12562 i.e. choose "Normal".
12564 Ftape can print lots of debugging messages to the system console
12565 resp. kernel log files. Reducing the amount of possible debugging
12566 output reduces the size of the kernel module by some KB, so it might
12567 be a good idea to use "None" for emergency boot floppies.
12569 If you want to save memory then the following strategy is
12570 recommended: leave this option at its default setting "Normal" until
12571 you know that the driver works as expected, afterwards reconfigure
12572 the kernel, this time specifying "Reduced" or "None" and recompile
12573 and install the kernel as usual. Note that choosing "Excessive"
12574 debugging output does not increase the amount of debugging output
12575 printed to the console but only makes it possible to produce
12576 "Excessive" debugging output.
12578 Please read Documentation/ftape.txt for a short description
12579 how to control the amount of debugging output.
12581 The floppy drive controller for ftape
12583 Only change this setting if you have a special controller. If you
12584 didn't plug any add-on card into your computer system but just
12585 plugged the floppy tape cable into the already existing floppy drive
12586 controller then you don't want to change the default setting,
12587 i.e. choose "Standard".
12589 Choose "MACH-2" if you have a Mountain Mach-2 controller.
12590 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
12592 Choose "Alt/82078" if you have another controller that is located at
12593 an IO base address different from the standard floppy drive
12594 controller's base address of `0x3f0', or uses an IRQ (interrupt)
12595 channel different from `6', or a DMA channel different from
12596 `2'. This is necessary for any controller card that is based on
12597 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
12598 speed" controllers.
12600 If you choose something other than "Standard" then please make
12601 sure that the settings for the IO base address and the IRQ and DMA
12602 channel in the configuration menus below are correct. Use the manual
12603 of your tape drive to determine the correct settings!
12605 If you are already successfully using your tape drive with another
12606 operating system then you definitely should use the same settings
12607 for the IO base, the IRQ and DMA channel that have proven to work
12608 with that other OS.
12610 Note that this menu lets you specify only the default setting for
12611 the hardware setup. The hardware configuration can be changed at
12612 boot time (when ftape is compiled into the kernel, i.e. if you
12613 have said Y to "Floppy tape drive") or module load time (i.e. if you
12614 have said M to "Floppy tape drive").
12616 Please read also the file Documentation/ftape.txt which
12617 contains a short description of the parameters that can be set at
12618 boot or load time. If you want to use your floppy tape drive on a
12619 PCI-bus based system, please read the file
12620 drivers/char/ftape/README.PCI.
12622 IO base of the floppy disk controller used with Ftape
12624 You don't need to specify a value if the following default
12625 settings for the base IO address are correct:
12626 <<< MACH-2 : 0x1E0 >>>
12627 <<< FC-10/FC-20: 0x180 >>>
12628 <<< Secondary : 0x370 >>>
12629 Secondary refers to a secondary FDC controller like the "high speed"
12630 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12631 Please make sure that the setting for the IO base address
12632 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12633 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12634 successfully using the tape drive with another operating system then
12635 you definitely should use the same settings for the IO base that has
12636 proven to work with that other OS.
12638 Note that this menu lets you specify only the default setting for
12639 the IO base. The hardware configuration can be changed at boot time
12640 (when ftape is compiled into the kernel, i.e. if you specified Y to
12641 "Floppy tape drive") or module load time (i.e. if you have said M to
12642 "Floppy tape drive").
12644 Please read also the file Documentation/ftape.txt which contains a
12645 short description of the parameters that can be set at boot or load
12648 IRQ channel for the floppy disk controller used with Ftape
12650 You don't need to specify a value if the following default
12651 settings for the interrupt channel are correct:
12653 <<< FC-10/FC-20: 9 >>>
12654 <<< Secondary : 6 >>>
12655 Secondary refers to secondary a FDC controller like the "high speed"
12656 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12657 Please make sure that the setting for the IO base address
12658 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12659 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12660 successfully using the tape drive with another operating system then
12661 you definitely should use the same settings for the IO base that has
12662 proven to work with that other OS.
12664 Note that this menu lets you specify only the default setting for
12665 the IRQ channel. The hardware configuration can be changed at boot
12666 time (when ftape is compiled into the kernel, i.e. if you said Y to
12667 "Floppy tape drive") or module load time (i.e. if you said M to
12668 "Floppy tape drive").
12670 Please read also the file Documentation/ftape.txt which contains a
12671 short description of the parameters that can be set at boot or load
12674 DMA channel for the floppy disk controller used with Ftape
12676 You don't need to specify a value if the following default
12677 settings for the DMA channel are correct:
12679 <<< FC-10/FC-20: 3 >>>
12680 <<< Secondary : 2 >>>
12681 Secondary refers to a secondary FDC controller like the "high speed"
12682 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12683 Please make sure that the setting for the IO base address
12684 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12685 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12686 successfully using the tape drive with another operating system then
12687 you definitely should use the same settings for the IO base that has
12688 proven to work with that other OS.
12690 Note that this menu lets you specify only the default setting for
12691 the DMA channel. The hardware configuration can be changed at boot
12692 time (when ftape is compiled into the kernel, i.e. if you said Y to
12693 "Floppy tape drive") or module load time (i.e. if you said M to
12694 "Floppy tape drive").
12696 Please read also the file Documentation/ftape.txt which contains a
12697 short description of the parameters that can be set at boot or load
12700 FDC FIFO Threshold before requesting DMA service
12702 Set the FIFO threshold of the FDC. If this is higher the DMA
12703 controller may serve the FDC after a higher latency time. If this is
12704 lower, fewer DMA transfers occur leading to less bus contention.
12705 You may try to tune this if ftape annoys you with "reduced data
12706 rate because of excessive overrun errors" messages. However, this
12707 doesn't seem to have too much effect.
12709 If unsure, don't touch the initial value, i.e. leave it at "8".
12711 FDC maximum data rate
12712 CONFIG_FT_FDC_MAX_RATE
12713 With some motherboard/FDC combinations ftape will not be able to
12714 run your FDC/tape drive combination at the highest available
12715 speed. If this is the case you'll encounter "reduced data rate
12716 because of excessive overrun errors" messages and lots of retries
12717 before ftape finally decides to reduce the data rate.
12719 In this case it might be desirable to tell ftape beforehand that
12720 it need not try to run the tape drive at the highest available
12721 speed. If unsure, leave this disabled, i.e. leave it at 2000
12724 Direct Rendering Manager (XFree86 DRI support)
12726 Kernel-level support for the Direct Rendering Infrastructure (DRI)
12727 introduced in XFree86 4.0. If you say Y here, you need to select
12728 the module that's right for your graphics card from the list below.
12729 These modules provide support for synchronization, security, and
12730 DMA transfers. Please see http://dri.sourceforge.net for more
12731 details. You should also select and configure AGP
12732 (/dev/agpgart) support.
12734 3dfx Banshee/Voodoo3+
12736 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
12737 graphics card. If M is selected, the module will be called tdfx.o.
12741 Choose this option if you have a 3dlabs GMX 2000 graphics card.
12742 If M is selected, the module will be called gamma.o.
12746 Choose this option if you have an ATI Rage 128 graphics card. If M
12747 is selected, the module will be called r128.o. AGP support for
12748 this card is strongly suggested (unless you have a PCI version).
12752 Choose this option if you have an Intel I810 graphics card. If M is
12753 selected, the module will be called i810.o. AGP support is required
12754 for this driver to work.
12758 Choose this option if you have a Matrox g200 or g400 graphics card. If M
12759 is selected, the module will be called mga.o. AGP support is required
12760 for this driver to work.
12762 MTRR control and configuration
12764 On Intel P6 family processors (Pentium Pro, Pentium II and later)
12765 the Memory Type Range Registers (MTRRs) may be used to control
12766 processor access to memory ranges. This is most useful if you have
12767 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
12768 allows bus write transfers to be combined into a larger transfer
12769 before bursting over the PCI/AGP bus. This can increase performance
12770 of image write operations 2.5 times or more. Saying Y here creates a
12771 /proc/mtrr file which may be used to manipulate your processor's
12772 MTRRs. Typically the X server should use this.
12774 This code has a reasonably generic interface so that similar
12775 control registers on other processors can be easily supported
12778 The Cyrix 6x86, 6x86MX and M II processors have Address Range
12779 Registers (ARRs) which provide a similar functionality to MTRRs. For
12780 these, the ARRs are used to emulate the MTRRs.
12781 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
12782 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
12783 write-combining. All of these processors are supported by this code
12784 and it makes sense to say Y here if you have one of them.
12786 Saying Y here also fixes a problem with buggy SMP BIOSes which only
12787 set the MTRRs for the boot CPU and not for the secondary CPUs. This
12788 can lead to all sorts of problems, so it's good to say Y here.
12790 You can safely say Y even if your machine doesn't have MTRRs, you'll
12791 just add about 9 KB to your kernel.
12793 See Documentation/mtrr.txt for more information.
12795 Main CPU frequency, only for DEC alpha machine
12796 CONFIG_FT_ALPHA_CLOCK
12797 On some DEC Alpha machines the CPU clock frequency cannot be
12798 determined automatically, so you need to specify it here ONLY if
12799 running a DEC Alpha, otherwise this setting has no effect.
12801 Double Talk PC internal speech card support
12803 This driver is for the DoubleTalk PC, a speech synthesizer
12804 manufactured by RC Systems (http://www.rcsys.com/ ). It is also
12805 called the `internal DoubleTalk'. If you want to compile this as a
12806 module ( = code which can be inserted in and removed from the
12807 running kernel whenever you want), say M here and read
12808 Documentation/modules.txt. The module will be called dtlk.o.
12810 Siemens R3964 serial protocol support
12812 This driver allows synchronous communication with devices using the
12813 Siemens R3964 packet protocol. Unless you are dealing with special
12814 hardware like PLCs, you are unlikely to need this.
12816 To compile this driver as a module ( = code which can be inserted in
12817 and removed from the running kernel whenever you want), say M here
12818 and read Documentation/modules.txt. The module will be called
12823 Applicom intelligent fieldbus card support
12825 This driver provides the kernel-side support for the intelligent
12826 fieldbus cards made by Applicom International. More information
12827 about these cards can be found on the WWW at the address
12828 http://www.applicom-int.com/ , or by email from David Woodhouse
12829 <dwmw2@infradead.org>.
12831 To compile this driver as a module ( = code which can be inserted in
12832 and removed from the running kernel whenever you want), say M here
12833 and read Documentation/modules.txt. The module will be called
12838 Intel Random Number Generator support
12840 This driver provides kernel-side support for the Random Number
12841 Generator hardware found on Intel i8xx-based motherboards.
12843 Both a character driver, used to read() entropy data, and a timer
12844 function which automatically adds entropy directly into the
12845 kernel pool, are exported by this driver.
12847 To compile this driver as a module ( = code which can be inserted in
12848 and removed from the running kernel whenever you want), say M here
12849 and read Documentation/modules.txt. The module will be called
12854 Power Management support
12856 "Power Management" means that parts of your computer are shut
12857 off or put into a power conserving "sleep" mode if they are not
12858 being used. There are two competing standards for doing this: APM
12859 and ACPI. If you want to use either one, say Y here and then also to
12860 the requisite support below.
12862 Power Management is most important for battery powered laptop
12863 computers; if you have a laptop, check out the Linux Laptop home
12865 http://www.cs.utexas.edu/users/kharker/linux-laptop/ and the Battery
12866 Powered Linux mini-HOWTO, available from
12867 http://www.linuxdoc.org/docs.html#howto .
12869 Note that, even if you say N here, Linux on the x86 architecture
12870 will issue the hlt instruction if nothing is to be done, thereby
12871 sending the processor to sleep and saving power.
12875 The Advanced Configuration and Power Interface is a standard
12876 designed to allow the operating system more control over power
12877 management issues, such as suspending a computer in a low power
12878 consumption state after a certain time of inaction. It aims to be
12879 an improved version of APM (see below). ACPI has to be
12880 supported by the motherboard. You can read more about the standard
12881 at http://www.teleport.com/~acpi/ .
12883 If your computer supports ACPI and you want to use it, say Y here.
12884 You will then need supporting software; for location and more
12885 information, please read Documentation/pm.txt and the Battery
12886 Powered Linux mini-HOWTO, available from
12887 http://www.linuxdoc.org/docs.html#howto .
12889 If you say Y here and also to "Advanced Power Management" (APM)
12890 below, then ACPI has precedence in the sense that, if your hardware
12891 supports ACPI, it will be used and APM won't.
12893 ACPI interpreter (EXPERIMENTAL)
12894 CONFIG_ACPI_INTERPRETER
12895 If you say Y here, an ACPI interpreter will be included in your
12896 kernel, eventually making the full range of ACPI features
12897 available on systems that support ACPI. Note, this option will
12898 enlarge your kernel by about 120K.
12900 The interpreter is currently experimental so only say Y if
12901 you know what you are doing.
12903 Enter S1 for sleep (EXPERIMENTAL)
12904 CONFIG_ACPI_S1_SLEEP
12905 If you say Y here, ACPI compliant devices can enter level 1 of ACPI
12906 saving power levels. Basically, this will let them enter sleep mode.
12908 Advanced Power Management BIOS support
12910 APM is a BIOS specification for saving power using several different
12911 techniques. This is mostly useful for battery powered laptops with
12912 APM compliant BIOSes. If you say Y here, the system time will be
12913 reset after a RESUME operation, the /proc/apm device will provide
12914 battery status information, and user-space programs will receive
12915 notification of APM "events" (e.g. battery status change).
12917 If you select "Y" here, you can disable actual use of the APM
12918 BIOS by passing the "apm=off" option to the kernel at boot time.
12920 Note that the APM support is almost completely disabled for
12921 machines with more than one CPU.
12923 In order to use APM, you will need supporting software. For location
12924 and more information, read Documentation/pm.txt and the Battery
12925 Powered Linux mini-HOWTO, available from
12926 http://www.linuxdoc.org/docs.html#howto .
12928 This driver does not spin down disk drives (see the hdparm(8)
12929 manpage ("man 8 hdparm") for that), and it doesn't turn off
12930 VESA-compliant "green" monitors.
12932 This driver does not support the TI 4000M TravelMate and the ACER
12933 486/DX4/75 because they don't have compliant BIOSes. Many "green"
12934 desktop machines also don't have compliant BIOSes, and this driver
12935 may cause those machines to panic during the boot phase.
12937 Generally, if you don't have a battery in your machine, there isn't
12938 much point in using this driver and you should say N. If you get
12939 random kernel OOPSes or reboots that don't seem to be related to
12940 anything, try disabling/enabling this option (or disabling/enabling
12943 Some other things you should try when experiencing seemingly random,
12946 1) make sure that you have enough swap space and that it is
12948 2) pass the "no-hlt" option to the kernel
12949 3) switch on floating point emulation in the kernel and pass
12950 the "no387" option to the kernel
12951 4) pass the "floppy=nodma" option to the kernel
12952 5) pass the "mem=4M" option to the kernel (thereby disabling
12953 all but the first 4 MB of RAM)
12954 6) make sure that the CPU is not over clocked.
12955 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
12956 8) disable the cache from your BIOS settings
12957 9) install a fan for the video card or exchange video RAM
12958 10) install a better fan for the CPU
12959 11) exchange RAM chips
12960 12) exchange the motherboard.
12962 To compile this driver as a module ( = code which can be inserted in
12963 and removed from the running kernel whenever you want), say M here
12964 and read Documentation/modules.txt. The module will be called
12967 Ignore USER SUSPEND
12968 CONFIG_APM_IGNORE_USER_SUSPEND
12969 This option will ignore USER SUSPEND requests. On machines with a
12970 compliant APM BIOS, you want to say N. However, on the NEC Versa M
12971 series notebooks, it is necessary to say Y because of a BIOS bug.
12973 Enable APM at boot time
12974 CONFIG_APM_DO_ENABLE
12975 Enable APM features at boot time. From page 36 of the APM BIOS
12976 specification: "When disabled, the APM BIOS does not automatically
12977 power manage devices, enter the Standby State, enter the Suspend
12978 State, or take power saving steps in response to CPU Idle calls."
12979 This driver will make CPU Idle calls when Linux is idle (unless this
12980 feature is turned off -- see "Do CPU IDLE calls", below). This
12981 should always save battery power, but more complicated APM features
12982 will be dependent on your BIOS implementation. You may need to turn
12983 this option off if your computer hangs at boot time when using APM
12984 support, or if it beeps continuously instead of suspending. Turn
12985 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
12986 T400CDT. This is off by default since most machines do fine without
12990 CONFIG_APM_CPU_IDLE
12991 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
12992 On some machines, this can activate improved power savings, such as
12993 a slowed CPU clock rate, when the machine is idle. These idle calls
12994 are made after the idle loop has run for some length of time (e.g.,
12995 333 mS). On some machines, this will cause a hang at boot time or
12996 whenever the CPU becomes idle. (On machines with more than one CPU,
12997 this option does nothing.)
12999 Enable console blanking using APM
13000 CONFIG_APM_DISPLAY_BLANK
13001 Enable console blanking using the APM. Some laptops can use this to
13002 turn off the LCD backlight when the screen blanker of the Linux
13003 virtual console blanks the screen. Note that this is only used by
13004 the virtual console screen blanker, and won't turn off the backlight
13005 when using the X Window system. This also doesn't have anything to
13006 do with your VESA-compliant power-saving monitor. Further, this
13007 option doesn't work for all laptops -- it might not turn off your
13008 backlight at all, or it might print a lot of errors to the console,
13009 especially if you are using gpm.
13011 RTC stores time in GMT
13012 CONFIG_APM_RTC_IS_GMT
13013 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
13014 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
13017 It is in fact recommended to store GMT in your RTC, because then you
13018 don't have to worry about daylight savings time changes. The only
13019 reason not to use GMT in your RTC is if you also run a broken OS
13020 that doesn't understand GMT.
13022 Allow interrupts during APM BIOS calls
13023 CONFIG_APM_ALLOW_INTS
13024 Normally we disable external interrupts while we are making calls to
13025 the APM BIOS as a measure to lessen the effects of a badly behaving
13026 BIOS implementation. The BIOS should reenable interrupts if it
13027 needs to. Unfortunately, some BIOSes do not -- especially those in
13028 many of the newer IBM Thinkpads. If you experience hangs when you
13029 suspend, try setting this to Y. Otherwise, say N.
13031 Use real mode APM BIOS call to power off
13032 CONFIG_APM_REAL_MODE_POWER_OFF
13033 Use real mode APM BIOS calls to switch off the computer. This is
13034 a work-around for a number of buggy BIOSes. Switch this option on if
13035 your computer crashes instead of powering off properly.
13037 Watchdog Timer Support
13039 If you say Y here (and to one of the following options) and create a
13040 character special file /dev/watchdog with major number 10 and minor
13041 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
13042 subsequently opening the file and then failing to write to it for
13043 longer than 1 minute will result in rebooting the machine. This
13044 could be useful for a networked machine that needs to come back
13045 online as fast as possible after a lock-up. There's both a watchdog
13046 implementation entirely in software (which can sometimes fail to
13047 reboot the machine) and a driver for hardware watchdog boards, which
13048 are more robust and can also keep track of the temperature inside
13049 your computer. For details, read Documentation/watchdog.txt in the
13052 The watchdog is usually used together with the watchdog daemon
13053 which is available via FTP (user: anonymous) from
13054 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/ . This daemon can also
13055 monitor NFS connections and can reboot the machine when the process
13060 Disable watchdog shutdown on close
13061 CONFIG_WATCHDOG_NOWAYOUT
13062 The default watchdog behaviour (which you get if you say N here) is
13063 to stop the timer if the process managing it closes the file
13064 /dev/watchdog. It's always remotely possible that this process might
13065 get killed. If you say Y here, the watchdog cannot be stopped once
13066 it has been started.
13070 If you have a WDT500P or WDT501P watchdog board, say Y here,
13071 otherwise N. It is not possible to probe for this board, which means
13072 that you have to inform the kernel about the IO port and IRQ using
13073 the "wdt=" kernel option (try "man bootparam" or see the
13074 documentation of your boot loader (lilo or loadlin) about how to
13075 pass options to the kernel at boot time).
13077 If you want to compile this as a module ( = code which can be
13078 inserted in and removed from the running kernel whenever you want),
13079 say M here and read Documentation/modules.txt. The module will be
13082 WDT PCI Watchdog timer
13084 If you have a PCI WDT500/501 watchdog board, say Y here,
13085 otherwise N. It is not possible to probe for this board, which means
13086 that you have to inform the kernel about the IO port and IRQ using
13087 the "wdt=" kernel option (try "man bootparam" or see the
13088 documentation of your boot loader (lilo or loadlin) about how to
13089 pass options to the kernel at boot time).
13091 If you want to compile this as a module ( = code which can be
13092 inserted in and removed from the running kernel whenever you want),
13093 say M here and read Documentation/modules.txt. The module will be
13098 Saying Y here and creating a character special file /dev/temperature
13099 with major number 10 and minor number 131 ("man mknod") will give
13100 you a thermometer inside your computer: reading from
13101 /dev/temperature yields one byte, the temperature in degrees
13102 Fahrenheit. This works only if you have a WDT501P watchdog board
13107 Enable the Fan Tachometer on the WDT501. Only do this if you have a
13108 fan tachometer actually set up.
13111 CONFIG_SOFT_WATCHDOG
13112 A software monitoring watchdog. This will fail to reboot your system
13113 from some situations that the hardware watchdog will recover
13114 from. Equally it's a lot cheaper to install.
13116 This driver is also available as a module ( = code which can be
13117 inserted in and removed from the running kernel whenever you want).
13118 If you want to compile it as a module, say M here and read
13119 Documentation/modules.txt. The module will be called softdog.o.
13121 Berkshire Products PC Watchdog
13123 This is the driver for the Berkshire Products PC Watchdog card.
13124 This card simply watches your kernel to make sure it doesn't freeze,
13125 and if it does, it reboots your computer after a certain amount of
13126 time. This driver is like the WDT501 driver but for different
13127 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
13128 watchdog cards can be ordered from http://www.berkprod.com .
13130 This driver is also available as a module ( = code which can be
13131 inserted in and removed from the running kernel whenever you want).
13132 The module is called pcwd.o. If you want to compile it as a module,
13133 say M here and read Documentation/modules.txt.
13135 Most people will say N.
13137 Acquire SBC Watchdog Timer
13139 This is the driver for the hardware watchdog on the PSC-6x86 Single
13140 Board Computer produced by Acquire Inc (and others). This watchdog
13141 simply watches your kernel to make sure it doesn't freeze, and if
13142 it does, it reboots your computer after a certain amount of time.
13144 This driver is like the WDT501 driver but for different hardware.
13145 This driver is also available as a module ( = code which can be
13146 inserted in and removed from the running kernel whenever you want).
13147 The module is called pscwdt.o. If you want to compile it as a
13148 module, say M here and read Documentation/modules.txt. Most people
13153 This is a driver for the Mixcom hardware watchdog cards. This
13154 watchdog simply watches your kernel to make sure it doesn't freeze,
13155 and if it does, it reboots your computer after a certain amount of
13158 This driver is also available as a module ( = code which can be
13159 inserted in and removed from the running kernel whenever you want).
13160 The module is called mixcomwd.o. If you want to compile it as a
13161 module, say M here and read Documentation/modules.txt. Most people
13164 /dev/cpu/microcode - Intel P6 CPU microcode support
13166 If you say Y here and also to "/dev file system support" in the
13167 'File systems' section, you will be able to update the microcode on
13168 Intel processors in the P6 family, e.g. Pentium Pro, Pentium II,
13169 Pentium III, Xeon etc. You will obviously need the actual microcode
13170 binary data itself which is not shipped with the Linux kernel.
13172 For latest news and information on obtaining all the required
13173 ingredients for this driver, check:
13174 http://www.urbanmyth.org/microcode/
13176 This driver is also available as a module ( = code which can be
13177 inserted in and removed from the running kernel whenever you want).
13178 The module will be called microcode.o. If you want to compile it as
13179 a module, say M here and read Documentation/modules.txt.
13181 /dev/cpu/*/msr - Model-specific register support
13183 This device gives privileged processes access to the x86
13184 Model-Specific Registers (MSRs). It is a character device with
13185 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
13186 MSR accesses are directed to a specific CPU on multi-processor
13189 /dev/cpu/*/cpuid - CPU information support
13191 This device gives processes access to the x86 CPUID instruction to
13192 be executed on a specific processor. It is a character device
13193 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
13196 Enhanced Real Time Clock Support
13198 If you say Y here and create a character special file /dev/rtc with
13199 major number 10 and minor number 135 using mknod ("man mknod"), you
13200 will get access to the real time clock (or hardware clock) built
13201 into your computer.
13203 Every PC has such a clock built in. It can be used to generate
13204 signals from as low as 1Hz up to 8192Hz, and can also be used
13205 as a 24 hour alarm. It reports status information via the file
13206 /proc/driver/rtc and its behaviour is set by various ioctls on
13209 If you run Linux on a multiprocessor machine and said Y to
13210 "Symmetric Multi Processing" above, you should say Y here to read
13211 and set the RTC in an SMP compatible fashion.
13213 If you think you have a use for such a device (such as periodic data
13214 sampling), then say Y here, and read Documentation/rtc.txt for
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 is called rtc.o. If you want to compile it as a module,
13220 say M here and read Documentation/modules.txt.
13223 #EFI Real Time Clock Services
13226 Tadpole ANA H8 Support
13228 The Hitachi H8/337 is a microcontroller used to deal with the power
13229 and thermal environment. If you say Y here, you will be able to
13230 communicate with it via a character special device.
13236 If you say Y here and create a character special file /dev/nvram
13237 with major number 10 and minor number 144 using mknod ("man mknod"),
13238 you get read and write access to the 50 bytes of non-volatile memory
13239 in the real time clock (RTC), which is contained in every PC and
13242 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
13243 on Ataris. /dev/nvram may be used to view settings there, or to
13244 change them (with some utility). It could also be used to frequently
13245 save a few bits of very important data that may not be lost over
13246 power-off and for which writing to disk is too insecure. Note
13247 however that most NVRAM space in a PC belongs to the BIOS and you
13248 should NEVER idly tamper with it. See Ralf Brown's interrupt list
13249 for a guide to the use of CMOS bytes by your BIOS.
13251 On Atari machines, /dev/nvram is always configured and does not need
13254 This driver is also available as a module ( = code which can be
13255 inserted in and removed from the running kernel whenever you want).
13256 The module will be called nvram.o. If you want to compile it as a
13257 module, say M here and read Documentation/modules.txt.
13261 If you have a joystick, 6dof controller, gamepad, steering wheel,
13262 weapon control system or something like that you can say Y here to
13263 enable generic support for these controllers. You will also need to
13264 say Y or M to at least one of the hardware specific drivers. This
13265 will make the controllers available as /dev/input/jsX devices.
13266 Please read the file Documentation/joystick.txt which contains more
13267 information and the location of the joystick package that you'll
13272 Say Y here if you have an ISA, ISAPnP or PCI standard gameport.
13273 For more information on how to use the driver please read
13274 Documentation/joystick.txt
13276 This driver is also available as a module ( = code which can be
13277 inserted in and removed from the running kernel whenever you want).
13278 The module will be called ns558.o. If you want to compile
13279 it as a module, say M here and read Documentation/modules.txt.
13281 PDPI Lightning 4 gamecard
13282 CONFIG_INPUT_LIGHTNING
13283 Say Y here if you have a PDPI Lightning 4 gamecard. For more
13284 information on how to use the driver please read
13285 Documentation/joystick.txt
13287 This driver is also available as a module ( = code which can be
13288 inserted in and removed from the running kernel whenever you want).
13289 The module will be called lightning.o. If you want to compile
13290 it as a module, say M here and read Documentation/modules.txt.
13292 Aureal Vortex and Trident 4DWave gameports
13293 CONFIG_INPUT_PCIGAME
13294 Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
13295 card. For more information on how to use the driver please read
13296 Documentation/joystick.txt
13298 This driver is also available as a module ( = code which can be
13299 inserted in and removed from the running kernel whenever you want).
13300 The module will be called pcigame.o. If you want to compile
13301 it as a module, say M here and read Documentation/modules.txt.
13303 Classic PC analog joysticks and gamepads
13304 CONFIG_INPUT_ANALOG
13305 Say Y here if you have a controller that connects to the PC
13306 gameport. This supports many different types, including joysticks
13307 with throttle control, with rudders, or with extensions like
13308 additional hats and buttons compatible with CH Flightstick Pro,
13309 ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg
13310 joysticks. For more information on how to use the driver please read
13311 Documentation/joystick.txt
13313 This driver is also available as a module ( = code which can be
13314 inserted in and removed from the running kernel whenever you want).
13315 The module will be called analog.o. If you want to compile
13316 it as a module, say M here and read Documentation/modules.txt.
13318 Assasin 3D and MadCatz Panther devices
13320 Say Y here if you have an FPGaming or MadCatz controller using the
13321 A3D protocol over the PC gameport. For more information on how to
13322 use the driver please read Documentation/joystick.txt
13324 This driver is also available as a module ( = code which can be
13325 inserted in and removed from the running kernel whenever you want).
13326 The module will be called a3d.o. If you want to compile
13327 it as a module, say M here and read Documentation/modules.txt.
13329 Logitech ADI digital joysticks and gamepads
13331 Say Y here if you have a Logitech controller using the ADI
13332 protocol over the PC gameport. For more information on how to use
13333 the driver please read Documentation/joystick.txt
13335 This driver is also available as a module ( = code which can be
13336 inserted in and removed from the running kernel whenever you want).
13337 The module will be called adi.o. If you want to compile
13338 it as a module, say M here and read Documentation/modules.txt.
13340 Creative Labs Blaster Cobra gamepad
13342 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
13343 For more information on how to use the driver please read
13344 Documentation/joystick.txt
13346 This driver is also available as a module ( = code which can be
13347 inserted in and removed from the running kernel whenever you want).
13348 The module will be called cobra.o. If you want to compile
13349 it as a module, say M here and read Documentation/modules.txt.
13351 Genius Flight2000 Digital joysticks and gamepads
13353 Say Y here if you have a Genius Flight2000 or MaxFighter
13354 digitally communicating joystick or gamepad. For more information
13355 on how to use the driver please read Documentation/joystick.txt
13357 This driver is also available as a module ( = code which can be
13358 inserted in and removed from the running kernel whenever you want).
13359 The module will be called gf2k.o. If you want to compile
13360 it as a module, say M here and read Documentation/modules.txt.
13362 Gravis GrIP joysticks and gamepads
13364 Say Y here if you have a Gravis controller using the GrIP protocol
13365 over the PC gameport. For more information on how to use the driver
13366 please read Documentation/joystick.txt
13368 This driver is also available as a module ( = code which can be
13369 inserted in and removed from the running kernel whenever you want).
13370 The module will be called grip.o. If you want to compile
13371 it as a module, say M here and read Documentation/modules.txt.
13373 InterAct digital joysticks and gamepads
13374 CONFIG_INPUT_INTERACT
13375 Say Y hereif you have an InterAct gameport or joystick
13376 communicating digitally over the gameport. For more information on
13377 how to use the driver please read Documentation/joystick.txt
13379 This driver is also available as a module ( = code which can be
13380 inserted in and removed from the running kernel whenever you want).
13381 The module will be called interact.o. If you want to compile
13382 it as a module, say M here and read Documentation/modules.txt.
13384 ThrustMaster DirectConnect joysticks and gamepads
13386 Say Y here if you have a ThrustMaster controller using the
13387 DirectConnect (BSP) protocol over the PC gameport. For more
13388 information on how to use the driver please read
13389 Documentation/joystick.txt
13391 This driver is also available as a module ( = code which can be
13392 inserted in and removed from the running kernel whenever you want).
13393 The module will be called tmdc.o. If you want to compile
13394 it as a module, say M here and read Documentation/modules.txt.
13396 Microsoft SideWinder digital joysticks and gamepads
13397 CONFIG_INPUT_SIDEWINDER
13398 Say Y here if you have a Microsoft controller using the Digital
13399 Overdrive protocol over PC gameport. For more information on how to
13400 use the driver please read Documentation/joystick.txt
13402 This driver is also available as a module ( = code which can be
13403 inserted in and removed from the running kernel whenever you want).
13404 The module will be called sidewinder.o. If you want to compile
13405 it as a module, say M here and read Documentation/modules.txt.
13407 Serial port input line discipline
13408 CONFIG_INPUT_SERPORT
13409 Say Y hereif you plan to use a joystick that communicates over the
13410 serial (COM) port. For more information on how to use the driver
13411 please read Documentation/joystick.txt
13413 This driver is also available as a module ( = code which can be
13414 inserted in and removed from the running kernel whenever you want).
13415 The module will be called serport.o. If you want to compile
13416 it as a module, say M here and read Documentation/modules.txt.
13418 Logitech WingMan Warrior joystick
13419 CONFIG_INPUT_WARRIOR
13420 Say Y here if you have a Logitech WingMan Warrior joystick
13421 connected to your computer's serial port. For more information on
13422 how to use the driver please read Documentation/joystick.txt
13424 This driver is also available as a module ( = code which can be
13425 inserted in and removed from the running kernel whenever you want).
13426 The module will be called warrior.o. If you want to compile
13427 it as a module, say M here and read Documentation/modules.txt.
13429 LogiCad3d Magellan/SpaceMouse 6dof controller
13430 CONFIG_INPUT_MAGELLAN
13431 Say Y here if you have a Magellan or Space Mouse 6DOF controller
13432 connected to your computer's serial port. For more information on
13433 how to use the driver please read Documentation/joystick.txt
13435 This driver is also available as a module ( = code which can be
13436 inserted in and removed from the running kernel whenever you want).
13437 The module will be called magellan.o. If you want to compile
13438 it as a module, say M here and read Documentation/modules.txt.
13440 SpaceTec SpaceOrb/Avenger 6dof controller
13441 CONFIG_INPUT_SPACEORB
13442 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
13443 controller connected to your computer's serial port. For more
13444 information on how to use the driver please read
13445 Documentation/joystick.txt
13447 This driver is also available as a module ( = code which can be
13448 inserted in and removed from the running kernel whenever you want).
13449 The module will be called spaceorb.o. If you want to compile
13450 it as a module, say M here and read Documentation/modules.txt.
13452 SpaceTec SpaceBall 4000 FLX 6dof controller
13453 CONFIG_INPUT_SPACEBALL
13454 Say Y here if you have a SpaceTec SpaceBall 4000 FLX controller
13455 connected to your computer's serial port. For more information on
13456 how to use the driver please read Documentation/joystick.txt
13458 I-Force joysticks/wheels
13459 CONFIG_INPUT_IFORCE_232
13460 Say Y here if you have an I-Force joystick or steering wheel
13461 connected to your serial (COM) port. For more information on
13462 how to use the driver please read Documentation/joystick.txt
13464 This driver is also available as a module ( = code which can be
13465 inserted in and removed from the running kernel whenever you want).
13466 The module will be called iforce.o. If you want to compile
13467 it as a module, say M here and read Documentation/modules.txt.
13469 I-Force joysticks/wheels
13470 CONFIG_INPUT_IFORCE_USB
13471 Say Y here if you have an I-Force joystick or steering wheel
13472 connected to your USB port. For more information on how to use the
13473 driver please read Documentation/joystick.txt
13475 This driver is also available as a module ( = code which can be
13476 inserted in and removed from the running kernel whenever you want).
13477 The module will be called iforce.o. If you want to compile
13478 it as a module, say M here and read Documentation/modules.txt.
13480 Multisystem, Sega Genesis, Saturn joysticks and gamepads
13482 Say Y here if you have a Sega Master System gamepad, Sega Genesis
13483 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
13484 Commodore, Amstrad CPC joystick connected to your parallel port.
13485 For more information on how to use the driver please read
13486 Documentation/joystick.txt and Documentation/joystick-parport.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 db9.o. If you want to compile
13491 it as a module, say M here and read Documentation/modules.txt.
13493 Multisystem, NES, SNES, N64, PSX joysticks and gamepads
13494 CONFIG_INPUT_GAMECON
13495 Say Y here if you have a Nintendo Entertainment System gamepad,
13496 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
13497 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
13498 Commodore, Amstrad CPC joystick connected to your parallel port.
13499 For more information on how to use the driver please read
13500 Documentation/joystick.txt and Documentation/joystick-parport.txt
13502 This driver is also available as a module ( = code which can be
13503 inserted in and removed from the running kernel whenever you want).
13504 The module will be called gamecon.o. If you want to compile
13505 it as a module, say M here and read Documentation/modules.txt.
13507 Multisystem joysticks via TurboGraFX device
13508 CONFIG_INPUT_TURBOGRAFX
13509 Say Y here if you have the TurboGraFX interface by Steffen
13510 Schwenke, and want to use it with Multiststem -- Atari, Amiga,
13511 Commodore, Amstrad CPC joystick. For more information on how to use
13512 the driver please read Documentation/joystick.txt and
13513 Documentation/joystick-parport.txt
13515 This driver is also available as a module ( = code which can be
13516 inserted in and removed from the running kernel whenever you want).
13517 The module will be called turbografx.o. If you want to compile
13518 it as a module, say M here and read Documentation/modules.txt.
13521 CONFIG_INPUT_AMIJOY
13522 Say Y here if you have an Amiga with a digital joystick connected
13523 to it. For more information on how to use the driver please read
13524 Documentation/joystick.txt
13526 This driver is also available as a module ( = code which can be
13527 inserted in and removed from the running kernel whenever you want).
13528 The module will be called joy-amiga.o. If you want to compile
13529 it as a module, say M here and read Documentation/modules.txt.
13531 Atomwide Serial Support
13532 CONFIG_ATOMWIDE_SERIAL
13533 If you have an Atomwide Serial card for an Acorn system, say Y to
13534 this option. The driver can handle 1, 2, or 3 port cards.
13537 The Serial Port Dual Serial Port
13538 CONFIG_DUALSP_SERIAL
13539 If you have the Serial Port's dual serial card for an Acorn system,
13540 say Y to this option. If unsure, say N
13544 If you say Y here and create a character device node /dev/nwbutton
13545 with major and minor numbers 10 and 158 ("man mknod"), then every
13546 time the orange button is pressed a number of times, the number of
13547 times the button was pressed will be written to that device.
13549 This is most useful for applications, as yet unwritten, which
13550 perform actions based on how many times the button is pressed in a
13553 Do not hold the button down for too long, as the driver does not
13554 alter the behaviour of the hardware reset circuitry attached to the
13555 button; it will still execute a hard reset if the button is held
13556 down for longer than approximately five seconds.
13558 This driver is also available as a module ( = code which can be
13559 inserted in and removed from the running kernel whenever you want).
13560 If you want to compile it as a module, say M here and read
13561 Documentation/modules.txt. The module will be called nwbutton.o.
13563 Most people will answer Y to this question and "Reboot Using Button"
13564 below to be able to initiate a system shutdown from the button.
13566 Reboot Using Button
13567 CONFIG_NWBUTTON_REBOOT
13568 If you say Y here, then you will be able to initiate a system
13569 shutdown and reboot by pressing the orange button a number of times.
13570 The number of presses to initiate the shutdown is two by default,
13571 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
13572 in nwbutton.h and recompiling the driver or, if you compile the
13573 driver as a module, you can specify the number of presses at load
13574 time with "insmod button reboot_count=<something>".
13578 If you have a sound card in your computer, i.e. if it can say more
13579 than an occasional beep, say Y. Be sure to have all the information
13580 about your sound card and its configuration down (I/O port,
13581 interrupt and DMA channel), because you will be asked for it.
13583 You want to read the Sound-HOWTO, available from
13584 http://www.linuxdoc.org/docs.html#howto . General information
13585 about the modular sound system is contained in the files
13586 Documentation/sound/Introduction. The file
13587 Documentation/sound/README.OSS contains some slightly outdated but
13588 still useful information as well.
13590 If you have a PnP sound card and you want to configure it at boot
13591 time using the ISA PnP tools (read
13592 http://www.roestock.demon.co.uk/isapnptools/ ), then you need to
13593 compile the sound card support as a module ( = code which can be
13594 inserted in and removed from the running kernel whenever you want)
13595 and load that module after the PnP configuration is finished. To do
13596 this, say M here and read Documentation/modules.txt as well as
13597 Documentation/sound/README.modules; the module will be called
13600 I'm told that even without a sound card, you can make your computer
13601 say more than an occasional beep, by programming the PC speaker.
13602 Kernel patches and supporting utilities to do that are in the pcsp
13603 package, available at ftp://ftp.infradead.org/pub/pcsp/ .
13607 OSS is the Open Sound System suite of sound card drivers. They make
13608 sound programming easier since they provide a common API. Say Y or M
13609 here (the module will be called sound.o) if you haven't found a
13610 driver for your sound card above, then pick your driver from the
13613 Persistent DMA buffers
13615 Linux can often have problems allocating DMA buffers for ISA sound
13616 cards on machines with more than 16MB of RAM. This is because ISA
13617 DMA buffers must exist below the 16MB boundary and it is quite
13618 possible that a large enough free block in this region cannot be
13619 found after the machine has been running for a while. If you say Y
13620 here the DMA buffers (64Kb) will be allocated at boot time and kept
13621 until the shutdown. This option is only useful if you said Y to
13622 "OSS sound modules", above. If you said M to "OSS sound modules"
13623 then you can get the persistent DMA buffer functionality by passing
13624 the command-line argument "dmabuf=1" to the sound.o module.
13626 Say Y unless you have 16MB or less RAM or a PCI sound card.
13628 Support for Aztech Sound Galaxy (non-PnP) cards
13629 CONFIG_SOUND_SGALAXY
13630 This module initializes the older non Plug and Play sound galaxy
13631 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
13632 Galaxy Washington 16.
13634 If you compile the driver into the kernel, you have to add
13635 "sgalaxy=<io>,<irq>,<dma>,<dma2>,<sgbase>" to the kernel command
13638 Support for AD1816(A) based cards (EXPERIMENTAL)
13639 CONFIG_SOUND_AD1816
13640 Say M here if you have a sound card based on the Analog Devices
13643 If you compile the driver into the kernel, you have to add
13644 "ad1816=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
13646 Yamaha OPL3-SA1 audio controller
13647 CONFIG_SOUND_OPL3SA1
13648 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
13649 usually built into motherboards. Read Documentation/sound/OPL3-SA
13652 If you compile the driver into the kernel, you have to add
13653 "opl3sa=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
13656 ProAudioSpectrum 16 support
13658 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
13659 16 or Logitech SoundMan 16 sound card. Answer N if you have some
13660 other card made by Media Vision or Logitech since those are not
13661 PAS16 compatible. Please read Documentation/sound/PAS16.
13663 If you compile the driver into the kernel, you have to add
13664 "pas2=<io>,<irq>,<dma>,<dma2>,<sbio>,<sbirq>,<sbdma>,<sbdma2>
13665 to the kernel command line.
13667 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
13669 Answer Y if you have an original Sound Blaster card made by Creative
13670 Labs or a 100% hardware compatible clone (like the Thunderboard or
13671 SM Games). For an unknown card you may answer Y if the card claims
13672 to be Sound Blaster-compatible.
13674 Please read the file Documentation/sound/Soundblaster.
13676 You should also say Y here for cards based on the Avance Logic
13677 ALS-007 and ALS-1X0 chips (read Documentation/sound/ALS) and for cards
13678 based on ESS chips (read Documentation/sound/ESS1868 and
13679 Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
13680 Y here and also to "AWE32 synth" below and read
13681 Documentation/sound/INSTALL.awe. If you have an IBM Mwave card, say
13682 Y here and read Documentation/sound/mwave.
13684 If you compile the driver into the kernel and don't want to use
13685 isapnp, you have to add "sb=<io>,<irq>,<dma>,<dma2>" to the kernel
13688 You can say M here to compile this driver as a module; the module is
13691 #Loopback MIDI device support
13692 #CONFIG_SOUND_VMIDI
13694 ### somebody please fill this in.
13697 Gravis Ultrasound support
13699 Say Y here for any type of Gravis Ultrasound card, including
13700 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
13701 more information on configuring this card with modules.
13703 If you compile the driver into the kernel, you have to add
13704 "gus=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
13706 MPU-401 support (NOT for SB16)
13707 CONFIG_SOUND_MPU401
13708 Be careful with this question. The MPU401 interface is supported by
13709 all sound cards. However, some natively supported cards have their
13710 own driver for MPU401. Enabling this MPU401 option with these cards
13711 will cause a conflict. Also, enabling MPU401 on a system that
13712 doesn't really have a MPU401 could cause some trouble. If your card
13713 was in the list of supported cards, look at the card specific
13714 instructions in the drivers/sound/Readme.cards file. It's safe to
13715 answer Y if you have a true MPU401 MIDI interface card.
13717 If you compile the driver into the kernel, you have to add
13718 "mpu401=<io>,<irq>" to the kernel command line.
13721 CONFIG_SOUND_UART6850
13722 This option enables support for MIDI interfaces based on the 6850
13723 UART chip. This interface is rarely found on sound cards. It's safe
13724 to answer N to this question.
13726 If you compile the driver into the kernel, you have to add
13727 "uart6850=<io>,<irq>" to the kernel command line.
13729 PSS (AD1848, ADSP-2115, ESC614) support
13731 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
13732 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
13733 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
13734 how to compile it into the kernel or as a module see the file
13735 Documentation/sound/PSS.
13737 If you compile the driver into the kernel, you have to add
13738 "pss=<io>,<mssio>,<mssirq>,<mssdma>,<mpuio>,<mpuirq>" to the kernel
13741 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
13743 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
13744 cards if they have master volume, bass, treble, and you can't
13745 control it under Linux. If you answer N for Beethoven ADSP-16, you
13746 can't control master volume, bass, treble and synth volume.
13748 If you said M to "PSS support" above, you may enable or disable this
13749 PSS mixer with the module parameter pss_mixer. For more information
13750 see the file Documentation/sound/PSS.
13752 Have DSPxxx.LD firmware file
13753 CONFIG_PSS_HAVE_BOOT
13754 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
13755 to include this file. Without this file the synth device (OPL) may
13758 Full pathname of DSPxxx.LD firmware file
13759 CONFIG_PSS_BOOT_FILE
13760 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
13763 Microsoft Sound System support
13765 Again think carefully before answering Y to this question. It's safe
13766 to answer Y if you have the original Windows Sound System card made
13767 by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
13768 in case your card is NOT among these:
13770 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
13771 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
13772 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
13773 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
13774 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
13775 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
13776 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
13777 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
13778 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
13779 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
13780 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
13781 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
13782 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
13784 For cards having native support in VoxWare, consult the card
13785 specific instructions in drivers/sound/Readme.cards. Some drivers
13786 have their own MSS support and saying Y to this option will cause a
13789 If you compile the driver into the kernel, you have to add
13790 "ad1848=<io>,<irq>,<dma>,<dma2>[,<type>]" to the kernel command
13793 SGI Visual Workstation on-board audio
13795 Say Y or M if you have an SGI Visual Workstation and you want to
13796 be able to use its on-board audio. Read Documentation/sound/visws
13797 for more info on this driver's capabilities.
13799 Ensoniq Soundscape support
13800 CONFIG_SOUND_SSCAPE
13801 Answer Y if you have a sound card based on the Ensoniq SoundScape
13802 chipset. Such cards are being manufactured at least by Ensoniq, Spea
13803 and Reveal (Reveal makes also other cards).
13805 If you compile the driver into the kernel, you have to add
13806 "sscape=<io>,<irq>,<dma>,<mpuio>,<mpuirq>" to the kernel command
13809 MediaTriX AudioTriX Pro support
13811 Answer Y if you have the AudioTriX Pro sound card manufactured
13814 Have TRXPRO.HEX firmware file
13815 CONFIG_TRIX_HAVE_BOOT
13816 The MediaTrix AudioTrix Pro has an on-board microcontroller which
13817 needs to be initialized by downloading the code from the file
13818 TRXPRO.HEX in the DOS driver directory. If you don't have the
13819 TRXPRO.HEX file handy you may skip this step. However, the SB and
13820 MPU-401 modes of AudioTrix Pro will not work without this file!
13822 Full pathname of TRXPRO.HEX firmware file
13823 CONFIG_TRIX_BOOT_FILE
13824 Enter the full pathname of your TRXPRO.HEX file, starting from /.
13826 Support for OPTi MAD16 and/or Mozart based cards
13828 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
13829 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931,
13830 please read drivers/sound/README.C931. These chips are currently
13831 quite common so it's possible that many no-name cards have one of
13832 them. In addition the MAD16 chip is used in some cards made by known
13833 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
13834 and Diamond (latest ones). Note however that the Tropez sound cards
13835 have their own driver; if you have one of those, say N here and Y or
13836 M to "Full support for Turtle Beach WaveFront", below.
13838 If you compile the driver into the kernel, you have to add
13839 "mad16=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the
13840 kernel command line.
13842 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
13843 more information on setting these cards up as modules.
13845 Full support for Turtle Beach WaveFront synth/sound cards
13846 CONFIG_SOUND_WAVEFRONT
13847 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
13848 and read the files Documentation/sound/Wavefront and
13849 Documentation/sound/Tropez+.
13851 Support MIDI in older MAD16 based cards (requires SB)
13852 CONFIG_MAD16_OLDCARD
13853 Answer Y (or M) if you have an older card based on the C928 or
13854 Mozart chipset and you want to have MIDI support. If you enable this
13855 option you also need to enable support for Sound Blaster.
13857 Support for Crystal CS4232 based (PnP) cards
13858 CONFIG_SOUND_CS4232
13859 Say Y here if you have a card based on the Crystal CS4232 chip set,
13860 which uses its own Plug and Play protocol.
13862 If you compile the driver into the kernel, you have to add
13863 "cs4232=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
13866 See Documentation/sound/CS4232 for more information on configuring
13869 Support for Yamaha OPL3-SA2, SA3, and SAx based PnP cards
13870 CONFIG_SOUND_OPL3SA2
13871 Say Y or M if you have a card based on one of these Yamaha
13872 sound chipsets. Read Documentation/sound/OPL3-SA2 for more
13873 information on configuring these cards.
13875 If you compile the driver into the kernel, you have to add
13876 "opl3sa2=<io>,<irq>,<dma>,<dma2>,<mssio>,<mpuio>" to the kernel
13879 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
13881 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
13884 If you compile the driver into the kernel, you have to add
13885 "maui=<io>,<irq>" to the kernel command line.
13887 Have OSWF.MOT firmware file
13888 CONFIG_MAUI_HAVE_BOOT
13889 Turtle Beach Maui and Tropez sound cards have a microcontroller
13890 which needs to be initialized prior to use. OSWF.MOT is a file
13891 distributed with the card's DOS/Windows drivers. Answer Y if you
13894 Full pathname of OSWF.MOT firmware file
13895 CONFIG_MAUI_BOOT_FILE
13896 Enter the full pathname of your OSWF.MOT file, starting from /.
13898 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
13899 CONFIG_SOUND_MSNDCLAS
13900 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
13901 Monterey (not for the Pinnacle or Fiji).
13903 See Documentation/sound/MultiSound for important information about
13906 Full pathname of MSNDINIT.BIN firmware file
13907 CONFIG_MSNDCLAS_INIT_FILE
13908 The MultiSound cards have two firmware files which are required for
13909 operation, and are not currently included. These files can be
13910 obtained from Turtle Beach. See Documentation/sound/MultiSound for
13911 information on how to obtain this.
13913 Full pathname of MSNDPERM.BIN firmware file
13914 CONFIG_MSNDCLAS_PERM_FILE
13915 The MultiSound cards have two firmware files which are required for
13916 operation, and are not currently included. These files can be
13917 obtained from Turtle Beach. See Documentation/sound/MultiSound for
13918 information on how to obtain this.
13920 Support for Turtle Beach MultiSound Pinnacle, Fiji
13921 CONFIG_SOUND_MSNDPIN
13922 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
13923 See Documentation/sound/MultiSound for important information about
13926 Full pathname of PNDSPINI.BIN firmware file
13927 CONFIG_MSNDPIN_INIT_FILE
13928 The MultiSound cards have two firmware files which are required for
13929 operation, and are not currently included. These files can be
13930 obtained from Turtle Beach. See Documentation/sound/MultiSound for
13931 information on how to obtain this.
13933 Full pathname of PNDSPERM.BIN firmware file
13934 CONFIG_MSNDPIN_PERM_FILE
13935 The MultiSound cards have two firmware files which are required for
13936 operation, and are not currently included. These files can be
13937 obtained from Turtle Beach. See Documentation/sound/MultiSound for
13938 information on how to obtain this.
13940 MSND Pinnacle have S/PDIF I/O
13941 CONFIG_MSNDPIN_DIGITAL
13942 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
13943 answer Y here; otherwise, say N. If you have this, you will be able
13944 to play and record from the S/PDIF port (digital signal). See
13945 Documentation/sound/MultiSound for information on how to make use of
13948 MSND Pinnacle non-PnP Mode
13949 CONFIG_MSNDPIN_NONPNP
13950 The Pinnacle and Fiji card resources can be configured either with
13951 PnP, or through a configuration port. Say Y here if your card is NOT
13952 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
13953 use of the IDE and joystick peripherals on the card as well; these
13954 do not show up when the card is in PnP mode. Specifying zero for any
13955 resource of a device will disable the device. If you are running the
13956 card in PnP mode, you must say N here and use isapnptools to
13957 configure the card's resources.
13959 MSND Pinnacle config port
13961 This is the port which the Pinnacle and Fiji uses to configure the
13962 card's resources when not in PnP mode. If your card is in PnP mode,
13963 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
13966 MSND buffer size (kB)
13967 CONFIG_MSND_FIFOSIZE
13968 Configures the size of each audio buffer, in kilobytes, for
13969 recording and playing in the MultiSound drivers (both the Classic
13970 and Pinnacle). Larger values reduce the chance of data overruns at
13971 the expense of overall latency. If unsure, use the default.
13973 FM synthesizer (YM3812/OPL-3) support
13974 CONFIG_SOUND_YM3812
13975 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
13976 Answering Y is usually a safe and recommended choice, however some
13977 cards may have software (TSR) FM emulation. Enabling FM support with
13978 these cards may cause trouble (I don't currently know of any such
13980 Please read the file Documentation/sound/OPL3 if your card has an
13983 If you compile the driver into the kernel, you have to add
13984 "opl3=<io>" to the kernel command line.
13988 ACI mixer (miroPCM12/PCM20)
13989 CONFIG_SOUND_ACI_MIXER
13990 ACI (Audio Command Interface) is a protocol used to communicate with
13991 the microcontroller on some sound cards produced by miro, e.g. the
13992 miroSOUND PCM12 and PCM20. The main function of the ACI is to
13993 control the mixer and to get a product identification.
13995 This Voxware ACI driver currently only supports the ACI functions on
13996 the miroSOUND PCM12 and PCM20 cards. On the PCM20, ACI also controls
13997 the radio tuner. This is supported in the video4linux
13998 radio-miropcm20 driver.
14001 CONFIG_SOUND_AWE32_SYNTH
14002 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
14003 similar sound card. See Documentation/sound/README.awe,
14004 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
14005 available from http://www.linuxdoc.org/docs.html#howto for more
14008 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
14009 CONFIG_SOUND_AEDSP16
14010 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
14011 driver supports Audio Excel DSP 16 but not the III nor PnP versions
14014 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
14015 a Microsoft Sound System card, so you should have said Y to either
14016 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
14017 or "Microsoft Sound System support", above, and you need to answer
14018 the "MSS emulation" and "SBPro emulation" questions below
14019 accordingly. You should say Y to one and only one of these two
14022 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
14023 drivers/sound/lowlevel/aedsp16.c as well as
14024 Documentation/sound/AudioExcelDSP16 to get more information about
14025 this driver and its configuration.
14027 Audio Excel DSP 16 (SBPro emulation)
14028 CONFIG_AEDSP16_SBPRO
14029 Answer Y if you want your audio card to emulate Sound Blaster Pro.
14030 You should then say Y to "100% Sound Blaster compatibles
14031 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
14034 If you compile the driver into the kernel, you have to add
14035 "aedsp16=<io>,<irq>,<dma>,<mssio>,<mpuio>,<mouirq>" to the kernel
14038 Audio Excel DSP 16 (MSS emulation)
14040 Answer Y if you want your audio card to emulate Microsoft Sound
14041 System. You should then say Y to "Microsoft Sound System support"
14042 and say N to "Audio Excel DSP 16 (SBPro emulation)".
14044 SC-6600 based audio cards (new Audio Excel DSP 16)
14046 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
14047 16 cards. Find in the manual the FCC ID of your audio card and
14048 answer Y if you have an SC6600 DSP.
14050 SC-6600 Joystick Interface
14052 Say Y here in order to use the joystick interface of the Audio Excel
14055 SC-6600 CDROM Interface
14056 CONFIG_SC6600_CDROM
14057 This is used to activate the the CDROM interface of the Audio Excel
14058 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
14061 Audio Excel DSP 16 (MPU401 emulation)
14062 CONFIG_AEDSP16_MPU401
14063 Answer Y if you want your audio card to emulate the MPU-401 midi
14064 interface. You should then also say Y to "MPU-401 support".
14066 Note that the I/O base for MPU-401 support of aedsp16 is the same
14067 you have selected for "MPU-401 support". If you are using this
14068 driver as a module you have to specify the MPU I/O base address with
14069 the parameter 'mpu_base=0xNNN'.
14071 Creative EMU10K1 based PCI sound cards
14072 CONFIG_SOUND_EMU10K1
14073 Say Y or M if you have a PCI sound card using the EMU10K1
14074 chipset, such as the Creative SBLive!, SB PCI512 or Emu-APS.
14076 Crystal SoundFusion (CS4280/461x)
14077 CONFIG_SOUND_FUSION
14078 This module drives the Crystal SoundFusion devices (CS4280/46xx series)
14079 when wired as native sound drivers with AC97 codecs. If this driver
14080 does not work try the CS4232 driver.
14082 Ensoniq ES1370 based PCI sound cards
14083 CONFIG_SOUND_ES1370
14084 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14085 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
14086 out if your sound card uses an ES1370 without removing your
14087 computer's cover, use lspci -n and look for the PCI ID
14088 1274:5000. Since Ensoniq was bought by Creative Labs,
14089 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
14090 This driver differs slightly from OSS/Free, so PLEASE READ
14091 Documentation/sound/es1370.
14093 Ensoniq ES1371 based PCI sound cards
14094 CONFIG_SOUND_ES1371
14095 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14096 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
14097 your sound card uses an ES1371 without removing your computer's
14098 cover, use lspci -n and look for the PCI ID 1274:1371. Since
14099 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
14100 models are either ES1370 or ES1371 based. This driver differs
14101 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
14103 ESS Solo1 based PCI sound cards (eg. SC1938)
14104 CONFIG_SOUND_ESSSOLO1
14105 Say Y or M if you have a PCI sound card utilizing the ESS Technology
14106 Solo1 chip. To find out if your sound card uses a
14107 Solo1 chip without removing your computer's cover, use
14108 lspci -n and look for the PCI ID 125D:1969. This driver
14109 differs slightly from OSS/Free, so PLEASE READ
14110 Documentation/sound/solo1.
14112 S3 SonicVibes based PCI sound cards
14113 CONFIG_SOUND_SONICVIBES
14114 Say Y or M if you have a PCI sound card utilizing the S3
14115 SonicVibes chipset. To find out if your sound card uses a
14116 SonicVibes chip without removing your computer's cover, use
14117 lspci -n and look for the PCI ID 5333:CA00. This driver
14118 differs slightly from OSS/Free, so PLEASE READ
14119 Documentation/sound/sonicvibes.
14121 Trident 4DWave DX/NX, SiS 7018 or ALi 5451 PCI Audio Core
14122 CONFIG_SOUND_TRIDENT
14123 Say Y or M if you have a PCI sound card utilizing the Trident
14124 4DWave-DX/NX chipset or your mother board chipset has SiS 7018
14125 or ALi 5451 built-in. The SiS 7018 PCI Audio Core is embedded
14126 in SiS960 Super South Bridge and SiS540/630 Single Chipset.
14127 The ALi 5451 PCI Audio Core is embedded in ALi M1535, M1535D,
14128 M1535+ or M1535D+ South Bridge.
14130 Use lspci -n to find out if your sound card or chipset uses
14131 Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands
14132 for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018. PCI ID
14133 10B9:5451 stands for ALi5451.
14135 This driver differs slightly from OSS/Free, so PLEASE READ the
14136 comments at the top of driver/sound/trident.c
14138 Rockwell WaveArtist
14139 CONFIG_SOUND_WAVEARTIST
14140 Say Y here to include support for the Rockwell WaveArtist sound
14141 system. This driver is mainly for the NetWinder.
14143 VIA 82Cxxx Audio Codec
14144 CONFIG_SOUND_VIA82CXXX
14145 Say Y here to include support for the audio codec found on VIA
14146 82Cxxx-based chips. Typically these are built into a motherboard. DO
14147 NOT select Sound Blaster or Adlib with this driver, unless you have
14148 a Sound Blaster or Adlib card in addition to your VIA audio chip.
14150 NeoMagic 256AV/256ZX sound chipsets
14152 Say M here to include audio support for the NeoMagic 256AV/256ZX
14153 chipsets. These are the audio chipsets found in the Sony
14154 Z505S/SX/DX, some Sony F-series, and the Dell Latitude CPi and CPt
14155 laptops. It includes support for an AC97-compatible mixer and an
14156 apparently proprietary sound engine.
14158 See Documentation/sound/NM256 for further information.
14160 ESS Maestro sound chipsets
14161 CONFIG_SOUND_MAESTRO
14162 Say Y or M if you have a sound system driven by ESS's Maestro line
14163 of PCI sound chips. These include the Maestro 1, Maestro 2, and
14164 Maestro 2E. See Documentation/sound/Maestro for more details.
14166 Are you using a crosscompiler
14167 CONFIG_CROSSCOMPILE
14168 Say Y here if you are compiling the kernel on a different
14169 architecture than the one it is intended to run on.
14171 Kernel support for Linux/MIPS 32-bit binary compatibility
14172 CONFIG_MIPS32_COMPAT
14173 Select this option if you want Linux/MIPS 32-bit binary
14174 compatibility. Since all software available for Linux/MIPS is
14175 currently 32-bit you should say Y here.
14177 Build fp exception handler module
14178 CONFIG_MIPS_FPE_MODULE
14179 Build the floating point exception handler module. This option is
14180 only useful for people working on the floating point exception
14181 handler. If you don't, say N.
14183 Remote GDB kernel debugging
14184 CONFIG_REMOTE_DEBUG
14185 If you say Y here, it will be possible to remotely debug the MIPS
14186 kernel using gdb. This enlarges your kernel image disk size by
14187 several megabytes and requires a machine with more than 16 MB,
14188 better 32 MB RAM to avoid excessive linking time. This is only
14189 useful for kernel hackers. If unsure, say N.
14191 Magic System Request Key support
14193 If you say Y here, you will have some control over the system even
14194 if the system crashes for example during kernel debugging (e.g., you
14195 will be able to flush the buffer cache to disk, reboot the system
14196 immediately or dump some status information). This is accomplished
14197 by pressing various keys while holding SysRq (Alt+PrintScreen). It
14198 also works on a serial console (on PC hardware at least), if you
14199 send a BREAK and then within 5 seconds a command keypress. The
14200 keys are documented in Documentation/sysrq.txt. Don't say Y unless
14201 you really know what this hack does.
14205 ISDN ("Integrated Services Digital Networks", called RNIS in France)
14206 is a special type of fully digital telephone service; it's mostly
14207 used to connect to your Internet service provider (with SLIP or
14208 PPP). The main advantage is that the speed is higher than ordinary
14209 modem/telephone connections, and that you can have voice
14210 conversations while downloading stuff. It only works if your
14211 computer is equipped with an ISDN card and both you and your service
14212 provider purchased an ISDN line from the phone company. For details,
14213 read http://alumni.caltech.edu/~dank/isdn/ on the WWW.
14215 This driver allows you to use an ISDN-card for networking
14216 connections and as dialin/out device. The isdn-tty's have a built in
14217 AT-compatible modem emulator. Network devices support autodial,
14218 channel-bundling, callback and caller-authentication without having
14219 a daemon running. A reduced T.70 protocol is supported with tty's
14220 suitable for German BTX. On D-Channel, the protocols EDSS1
14221 (Euro-ISDN) and 1TR6 (German style) are supported. See
14222 Documentation/isdn/README for more information.
14224 If you want to compile the ISDN code as a module ( = code which can
14225 be inserted in and removed from the running kernel whenever you
14226 want), say M here and read Documentation/modules.txt. The module
14227 will be called isdn.o. If unsure, say N.
14229 Support synchronous PPP
14231 Over digital connections such as ISDN, there is no need to
14232 synchronize sender and recipient's clocks with start and stop bits
14233 as is done over analog telephone lines. Instead, one can use
14234 "synchronous PPP". Saying Y here will include this protocol. This
14235 protocol is used by Cisco and Sun for example. So you want to say Y
14236 here if the other end of your ISDN connection supports it. You will
14237 need a special version of pppd (called ipppd) for using this
14238 feature. See Documentation/isdn/README.syncppp and
14239 Documentation/isdn/syncPPP.FAQ for more information.
14241 Support generic MP (RFC 1717)
14243 With synchronous PPP enabled, it is possible to increase throughput
14244 by bundling several ISDN-connections, using this protocol. See
14245 Documentation/isdn/README.syncppp for more information.
14247 Use VJ-compression with synchronous PPP
14249 This enables Van Jacobson header compression for synchronous PPP.
14250 Say Y if the other end of the connection supports it.
14252 Support audio via ISDN
14254 If you say Y here, the modem-emulator will support a subset of the
14255 EIA Class 8 Voice commands. Using a getty with voice-support
14256 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
14257 with the ISDN utility package for example), you will be able to use
14258 your Linux box as an ISDN-answering machine. Of course, this must be
14259 supported by the lowlevel driver also. Currently, the HiSax driver
14260 is the only voice-supporting driver. See
14261 Documentation/isdn/README.audio for more information.
14263 X.25 PLP on top of ISDN
14265 This feature provides the X.25 protocol over ISDN connections.
14266 See Documentation/isdn/README.x25 for more information
14267 if you are thinking about using this.
14269 ISDN diversion services support
14270 CONFIG_ISDN_DIVERSION
14271 This option allows you to use some supplementary diversion
14272 services in conjunction with the HiSax driver on an EURO/DSS1
14275 Supported options are CD (call deflection), CFU (Call forward
14276 unconditional), CFB (Call forward when busy) and CFNR (call forward
14277 not reachable). Additionally the actual CFU, CFB and CFNR state may
14280 The use of CFU, CFB, CFNR and interrogation may be limited to some
14281 countries. The keypad protocol is still not implemented. CD should
14282 work in all countries if the service has been subscribed to.
14284 Please read the file Documentation/isdn/README.diversion.
14286 ICN 2B and 4B support
14287 CONFIG_ISDN_DRV_ICN
14288 This enables support for two kinds of ISDN-cards made by a German
14289 company called ICN. 2B is the standard version for a single ISDN
14290 line with two B-channels, 4B supports two ISDN lines. For running
14291 this card, additional firmware is necessary, which has to be
14292 downloaded into the card using a utility which is distributed
14293 separately. See Documentation/isdn/README and README.icn for more
14296 If you want to compile this as a module ( = code which can be
14297 inserted in and removed from the running kernel whenever you want),
14298 say M here and read Documentation/modules.txt. The module will be
14302 CONFIG_ISDN_DRV_LOOP
14303 This driver provides a virtual ISDN card. Its primary purpose is
14304 testing of linklevel features or configuration without getting
14305 charged by your service-provider for lots of phone calls.
14306 You need will need the loopctrl utility from the latest isdn4k-utils
14307 package to set up this driver.
14309 HiSax SiemensChipSet driver support
14310 CONFIG_ISDN_DRV_HISAX
14311 This is a driver supporting the Siemens chipset on various
14312 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
14313 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
14316 HiSax is just the name of this driver, not the name of any hardware.
14318 If you have a card with such a chipset, you should say Y here and
14319 also to the configuration option of the driver for your particular
14322 If you want to compile this as a module ( = code which can be
14323 inserted in and removed from the running kernel whenever you want),
14324 say M here and read Documentation/modules.txt. The module will be
14325 called hisax.o. See Documentation/isdn/README.HiSax for more
14326 information on using this driver.
14328 HiSax Support for EURO/DSS1
14330 Say Y or N according to the D-channel protocol which your local
14331 telephone service company provides.
14333 The call control protocol E-DSS1 is used in most European countries.
14334 If unsure, say yes.
14336 Support for german charge info
14338 If you want that the HiSax hardware driver sends messages to the
14339 upper level of the isdn code on each AOCD (Advice Of Charge, During
14340 the call -- transmission of the fee information during a call) and
14341 on each AOCE (Advice Of Charge, at the End of the call --
14342 transmission of fee information at the end of the call), say Y here.
14343 This works only in Germany.
14345 Disable sending complete
14346 CONFIG_HISAX_NO_SENDCOMPLETE
14347 If you have trouble with some ugly exchanges or you live in
14348 Australia select this option.
14350 Disable sending low layer compatibility
14351 CONFIG_HISAX_NO_LLC
14352 If you have trouble with some ugly exchanges try to select this
14355 Disable keypad protocol option
14356 CONFIG_HISAX_NO_KEYPAD
14357 If you like to send special dial strings including * or # without
14358 using the keypad protocol, select this option.
14360 HiSax Support for German 1TR6
14362 Say Y or N according to the D-channel protocol which your local
14363 telephone service company provides.
14365 1TR6 is an old call control protocol which was used in Germany
14366 before E-DSS1 was established. Nowadays, all new lines in Germany
14369 HiSax Support for US NI1
14371 Enable this if you like to use ISDN in US on a NI1 basic rate interface.
14375 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
14376 and many compatibles.
14378 See Documentation/isdn/README.HiSax on how to configure it using the
14379 different cards, a different D-channel protocol, or non-standard
14380 IRQ/port/shmem settings.
14382 Teles 16.3 or PNP or PCMCIA
14384 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
14385 Teles/Creatix PnP and the Teles PCMCIA.
14387 See Documentation/isdn/README.HiSax on how to configure it using the
14388 different cards, a different D-channel protocol, or non-standard
14392 CONFIG_HISAX_TELESPCI
14393 This enables HiSax support for the Teles PCI.
14394 See Documentation/isdn/README.HiSax on how to configure it.
14398 This enables HiSax support for the Teles/Creatix parallel port
14399 S0BOX. See Documentation/isdn/README.HiSax on how to configure it.
14402 CONFIG_HISAX_AVM_A1
14403 This enables HiSax support for the AVM A1 (aka "Fritz").
14405 See Documentation/isdn/README.HiSax on how to configure it using the
14406 different cards, a different D-channel protocol, or non-standard
14409 AVM PnP/PCI (Fritz!PNP/PCI)
14410 CONFIG_HISAX_FRITZPCI
14411 This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI".
14412 See Documentation/isdn/README.HiSax on how to configure it.
14414 AVM A1 PCMCIA (Fritz)
14415 CONFIG_HISAX_AVM_A1_PCMCIA
14416 This enables HiSax support for the AVM A1 "Fritz!PCMCIA").
14417 See Documentation/isdn/README.HiSax on how to configure it.
14421 This enables HiSax support for the Elsa Mircolink ISA cards, for the
14422 Elsa Quickstep series cards and Elsa PCMCIA.
14424 See Documentation/isdn/README.HiSax on how to configure it using the
14425 different cards, a different D-channel protocol, or non-standard
14428 ITK ix1-micro Revision 2
14429 CONFIG_HISAX_IX1MICROR2
14430 This enables HiSax support for the ITK ix1-micro Revision 2 card.
14432 See Documentation/isdn/README.HiSax on how to configure it using the
14433 different cards, a different D-channel protocol, or non-standard
14436 Eicon.Diehl Diva cards
14437 CONFIG_HISAX_DIEHLDIVA
14438 This enables HiSax support for the Eicon.Diehl Diva none PRO
14439 versions passive ISDN cards.
14441 See Documentation/isdn/README.HiSax on how to configure it using the
14442 different cards, a different D-channel protocol, or non-standard
14446 CONFIG_HISAX_ASUSCOM
14447 This enables HiSax support for the AsusCom and their OEM versions
14448 passive ISDN ISA cards.
14450 See Documentation/isdn/README.HiSax on how to configure it using the
14451 different cards, a different D-channel protocol, or non-standard
14455 CONFIG_HISAX_TELEINT
14456 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
14458 See Documentation/isdn/README.HiSax on how to configure it using the
14459 different cards, a different D-channel protocol, or non-standard
14464 This enables HiSax support for the HFC-S 2BDS0 based cards, like
14467 See Documentation/isdn/README.HiSax on how to configure it using the
14468 different cards, a different D-channel protocol, or non-standard
14472 CONFIG_HISAX_SEDLBAUER
14473 This enables HiSax support for the Sedlbauer passive ISDN cards.
14475 See Documentation/isdn/README.HiSax on how to configure it using the
14476 different cards, a different D-channel protocol, or non-standard
14479 USR Sportster internal TA
14480 CONFIG_HISAX_SPORTSTER
14481 This enables HiSax support for the USR Sportster internal TA card.
14483 See Documentation/isdn/README.HiSax on how to configure it using a
14484 different D-channel protocol, or non-standard IRQ/port settings.
14488 This enables HiSax support for the ITH MIC card.
14490 See Documentation/isdn/README.HiSax on how to configure it using a
14491 different D-channel protocol, or non-standard IRQ/port settings.
14494 CONFIG_HISAX_NETJET
14495 This enables HiSax support for the NetJet from Traverse
14498 See Documentation/isdn/README.HiSax on how to configure it using a
14499 different D-channel protocol, or non-standard IRQ/port settings.
14502 CONFIG_HISAX_NETJET_U
14503 This enables HiSax support for the Netspider U interface ISDN card from
14504 Traverse Technologies.
14505 See Documentation/isdn/README.HiSax on how to configure it using a
14506 different D-channel protocol, or non-standard IRQ/port settings.
14510 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
14512 See Documentation/isdn/README.HiSax on how to configure it using a
14513 different D-channel protocol, or non-standard IRQ/port settings.
14515 Siemens I-Surf card
14517 This enables HiSax support for the Siemens I-Talk/I-Surf card with
14519 See Documentation/isdn/README.HiSax on how to configure it using a
14520 different D-channel protocol, or non-standard IRQ/port settings.
14523 CONFIG_HISAX_HSTSAPHIR
14524 This enables HiSax support for the HST Saphir card.
14526 See Documentation/isdn/README.HiSax on how to configure it using a
14527 different D-channel protocol, or non-standard IRQ/port settings.
14530 CONFIG_HISAX_BKM_A4T
14531 This enables HiSax support for the Telekom A4T card.
14533 See Documentation/isdn/README.HiSax on how to configure it using a
14534 different D-channel protocol, or non-standard IRQ/port settings.
14537 CONFIG_HISAX_SCT_QUADRO
14538 This enables HiSax support for the Scitel Quadro card.
14540 See Documentation/isdn/README.HiSax on how to configure it using a
14541 different D-channel protocol, or non-standard IRQ/port settings.
14545 This enables HiSax support for the Gazel cards.
14547 See Documentation/isdn/README.HiSax on how to configure it using a
14548 different D-channel protocol, or non-standard IRQ/port settings.
14551 CONFIG_HISAX_HFC_PCI
14552 This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
14554 For more informations see under Documentation/isdn/README.hfc-pci.
14556 Winbond W6692 based cards
14558 This enables HiSax support for Winbond W6692 based PCI ISDN cards.
14560 See Documentation/isdn/README.HiSax on how to configure it using a
14561 different D-channel protocol, or non-standard IRQ/port settings.
14563 HFC-S+, HFC-SP, HFC-PCMCIA cards (EXPERIMENTAL)
14564 CONFIG_HISAX_HFC_SX
14565 This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA
14566 cards. This code is not finished yet.
14568 Am7930 (EXPERIMENTAL)
14569 CONFIG_HISAX_AMD7930
14570 This enables HiSax support for the AMD7930 chips on some SPARCs.
14571 This code is not finished yet.
14574 CONFIG_ISDN_DRV_PCBIT
14575 This enables support for the PCBIT ISDN-card. This card is
14576 manufactured in Portugal by Octal. For running this card, additional
14577 firmware is necessary, which has to be downloaded into the card
14578 using a utility which is distributed separately. See
14579 Documentation/isdn/README and Documentation/isdn/README.pcbit for
14582 If you want to compile this as a module ( = code which can be
14583 inserted in and removed from the running kernel whenever you want),
14584 say M here and read Documentation/modules.txt. The module will be
14587 Spellcaster support (EXPERIMENTAL)
14589 This enables support for the Spellcaster BRI ISDN boards. This
14590 driver currently builds only in a modularized version ( = code which
14591 can be inserted in and removed from the running kernel whenever you
14592 want, details in Documentation/modules.txt); the module will be
14593 called sc.o. See Documentation/isdn/README.sc and
14594 http://www.spellcast.com for more information.
14596 Eicon active card support
14597 CONFIG_ISDN_DRV_EICON
14598 Say Y here if you have an Eicon active ISDN card. In order to use
14599 this card, additional firmware is necessary, which has to be loaded
14600 into the card using the eiconctrl utility which is part of the
14601 latest isdn4k-utils package. Please read the file
14602 Documentation/isdn/README.eicon for more information.
14604 Eicon Diva Server card support
14605 CONFIG_ISDN_DRV_EICON_PCI
14606 Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN card.
14607 Please read Documentation/isdn/README.eicon for more information.
14609 Eicon old-type card support
14610 CONFIG_ISDN_DRV_EICON_ISA
14611 Say Y here if you have an old-type Eicon active ISDN card. In order
14612 to use this card, additional firmware is necessary, which has to be
14613 loaded into the card using the eiconctrl utility which is part of
14614 the latest isdn4k-utils package. Please read the file
14615 Documentation/isdn/README.eicon for more information.
14617 Eicon driver type standalone
14618 CONFIG_ISDN_DRV_EICON_STANDALONE
14619 Enable this option if you want the eicon driver as standalone
14620 version with no interface to the ISDN4Linux isdn module. If you
14621 say Y here, the eicon module only supports the Diva Server PCI
14622 cards and will provide its own IDI interface. You should say N
14625 Support AT-Fax Class 1 and 2 commands
14626 CONFIG_ISDN_TTY_FAX
14627 If you say Y here, the modem-emulator will support a subset of the
14628 Fax Class 1 and 2 commands. Using a getty with fax-support
14629 (mgetty+sendfax, hylafax), you will be able to use your Linux box as
14630 an ISDN-fax-machine. This must be supported by the lowlevel driver
14631 also. See Documentation/isdn/README.fax for more information.
14635 This provides the CAPI (Common ISDN Application Programming
14636 Interface, a standard making it easy for programs to access ISDN
14637 hardware, see http://www.capi.org/ . This is needed for AVM's set of
14638 active ISDN controllers like B1, T1, M1.
14640 This code is also available as a module ( = code which can be
14641 inserted in and removed from the running kernel whenever you want).
14642 The modules will be called capi.o and kernelcapi.o. If you want to
14643 compile it as a module, say M here and read
14644 Documentation/modules.txt.
14647 CONFIG_ISDN_DRV_AVMB1_B1ISA
14648 Enable support for the ISA version of the AVM B1 card.
14651 CONFIG_ISDN_DRV_AVMB1_B1PCI
14652 Enable support for the PCI version of the AVM B1 card.
14654 AVM B1 PCI V4 support
14655 CONFIG_ISDN_DRV_AVMB1_B1PCIV4
14656 Enable support for the V4 version of AVM B1 PCI card.
14658 AVM T1/T1-B ISA support
14659 CONFIG_ISDN_DRV_AVMB1_T1ISA
14660 Enable support for the AVM T1 T1B card.
14661 Note: This is a PRI card and handle 30 B-channels.
14663 AVM B1/M1/M2 PCMCIA support
14664 CONFIG_ISDN_DRV_AVMB1_B1PCMCIA
14665 Enable support for the PCMCIA version of the AVM B1 card.
14667 AVM T1/T1-B PCI support
14668 CONFIG_ISDN_DRV_AVMB1_T1PCI
14669 Enable support for the AVM T1 T1B card.
14670 Note: This is a PRI card and handle 30 B-channels.
14673 CONFIG_ISDN_DRV_AVMB1_C4
14674 Enable support for the AVM C4 PCI card.
14675 This card handle 4 BRI ISDN lines (8 channels).
14677 Verbose reason code reporting (kernel size +=7K)
14678 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
14679 If you say Y here, the AVM B1 driver will give verbose reasons for
14680 disconnecting. This will increase the size of the kernel by 7 KB. If
14683 IBM Active 2000 support (EXPERIMENTAL)
14684 CONFIG_ISDN_DRV_ACT2000
14685 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
14686 this card, additional firmware is necessary, which has to be loaded
14687 into the card using a utility which is part of the latest
14688 isdn4k-utils package. Please read the file
14689 Documentation/isdn/README.act2000 for more information.
14691 Hypercope HYSDN cards (Champ, Ergo, Metro) support (module)
14693 Say Y here if you have one of Hypercope's active PCI ISDN cards
14694 Champ, Ergo and Metro. You will then get a module called hysdn.o.
14695 Please read the file Documentation/isdn/README.hysdn for more
14698 HYSDN CAPI 2.0 support
14700 Say Y here if you like to use Hypercope's CAPI 2.0 interface
14702 Support for Sun4 architecture
14704 Say Y here if, and only if, your machine is a Sun4. Note that
14705 a kernel compiled with this option will run only on Sun4.
14706 (And the current version will probably work only on sun4/330.)
14708 SPARC ESP SCSI support
14710 This is the driver for the Sun ESP SCSI host adapter. The ESP
14711 chipset is present in most SPARC SBUS-based computers.
14713 This support is also available as a module called esp.o ( = code
14714 which can be inserted in and removed from the running kernel
14715 whenever you want). If you want to compile it as a module, say M
14716 here and read Documentation/modules.txt.
14718 PTI Qlogic, ISP Driver
14719 CONFIG_SCSI_QLOGICPTI
14720 This driver supports SBUS SCSI controllers from PTI or QLogic. These
14721 controllers are known under Solaris as qpti and in the openprom as
14722 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
14723 driven by a different driver.
14725 This support is also available as a module called qlogicpti.o ( =
14726 code which can be inserted in and removed from the running kernel
14727 whenever you want). If you want to compile it as a module, say M
14728 here and read Documentation/modules.txt.
14730 SPARC /dev/openprom compatibility driver (EXPERIMENTAL)
14731 CONFIG_SUN_OPENPROMIO
14732 This driver provides user programs with an interface to the SPARC
14733 PROM device tree. The driver implements a SunOS-compatible
14734 interface and a NetBSD-compatible interface.
14736 If you want to compile this as a module ( = code which can be
14737 inserted in and removed from the running kernel whenever you want),
14738 say M and read Documentation/modules.txt. If unsure, say Y.
14740 Openprom tree appears in /proc/openprom
14741 CONFIG_SUN_OPENPROMFS
14742 If you say Y, the OpenPROM device tree will be available as a
14743 virtual file system, which you can mount to /proc/openprom by "mount
14744 -t openpromfs none /proc/openprom".
14746 If you want to compile the /proc/openprom support as a module ( =
14747 code which can be inserted in and removed from the running kernel
14748 whenever you want), say M here and read Documentation/modules.txt.
14749 The module will be called openpromfs.o. If unsure, say M.
14751 Kernel support for Linux/Sparc 32bit binary compatibility
14752 CONFIG_SPARC32_COMPAT
14753 This allows you to run 32-bit binaries on your Ultra.
14754 Everybody wants this; say Y.
14756 Kernel support for 32-bit ELF binaries
14757 CONFIG_BINFMT_ELF32
14758 This allows you to run 32-bit Linux/ELF binaries on your Ultra.
14759 Everybody wants this; say Y.
14761 Kernel support for 32-bit (ie. SunOS) a.out binaries
14762 CONFIG_BINFMT_AOUT32
14763 This allows you to run 32-bit a.out format binaries on your Ultra.
14764 If you want to run SunOS binaries (see SunOS binary emulation below)
14765 or other a.out binaries, say Y. If unsure, say N.
14767 SunOS binary emulation
14769 This allows you to run most SunOS binaries. If you want to do this,
14770 say Y here and place appropriate files in /usr/gnemul/sunos. See
14771 http://www.ultralinux.org/faq.html for more information. If you want
14772 to run SunOS binaries on an Ultra you must also say Y to "Kernel
14773 support for 32-bit a.out binaries" above.
14775 Mostek real time clock support
14776 CONFIG_SUN_MOSTEK_RTC
14777 The Mostek RTC chip is used on all known Sun computers except
14778 some JavaStations. For a JavaStation you need to say Y both here
14779 and to "Enhanced Real Time Clock Support".
14781 Say Y here unless you are building a special purpose kernel.
14783 OBP Flash Device support
14785 The OpenBoot PROM on Ultra systems is flashable. If you want to be
14786 able to upgrade the OBP firmware, say Y here.
14788 JavaStation OS Flash SIMM
14790 If you say Y here, you will be able to boot from your JavaStation's
14793 Siemens SAB82532 serial support
14795 This driver supports the serial ports on newer (PCI) Ultra systems.
14796 Say Y if you want to be able to use your serial ports.
14798 Aurora Multiboard 1600se (EXPERIMENTAL)
14800 The Aurora Multiboard is a multi-port high-speed serial controller.
14801 If you have one of these, say Y.
14803 Audio support (EXPERIMENTAL)
14805 This driver provides support for the build-in sound devices on most
14806 Sun machines. If you want to be able to use this, select this option
14807 and one or more of the lowlevel drivers below. See
14808 http://www.dementia.org/~shadow/sparcaudio.html for more
14811 AMD7930 Lowlevel Driver
14812 CONFIG_SPARCAUDIO_AMD7930
14813 This driver supports the AMD 7930 chip found on sun4c, 4/6xx, and
14814 SparcClassic systems.
14816 CS4231 Lowlevel Driver
14817 CONFIG_SPARCAUDIO_CS4231
14818 This driver supports the Crystal Semiconductor CS4231 chip found on
14819 the SS4, SS5, and Ultras.
14821 DBRI Lowlevel Driver
14822 CONFIG_SPARCAUDIO_DBRI
14823 This driver supports the DBRI audio interface found on the SS10,
14824 SS20, Sparcbook 3, and Voyager systems.
14826 Dummy lowlevel Driver
14827 CONFIG_SPARCAUDIO_DUMMY
14828 This is a pseudo-driver used for debugging and testing the
14829 sparcaudio subsystem. Say N unless you want to work on this
14832 Sparc hardware (EXPERIMENTAL)
14833 CONFIG_PARPORT_SUNBPP
14834 This driver provides support for the bidirectional parallel port
14835 found on many Sun machines. Note that many of the newer Ultras
14836 actually have pc style hardware instead.
14839 # m68k-specific kernel options
14840 # Documented by Chris Lawrence <quango@themall.net> et al.
14844 This option enables support for the Amiga series of computers. If
14845 you plan to use this kernel on an Amiga, say Y here and browse the
14846 material available in Documentation/m68k; otherwise say N.
14850 This option enables support for the 68000-based Atari series of
14851 computers (including the TT, Falcon and Medusa). If you plan to use
14852 this kernel on an Atari, say Y here and browse the material
14853 available in Documentation/m68k; otherwise say N.
14857 This option enables support for the Hades Atari clone. If you plan
14858 to use this kernel on a Hades, say Y here; otherwise say N.
14862 This option enables support for the Apple Macintosh series of
14863 computers (yes, there is experimental support now, at least for part
14866 Say N unless you're willing to code the remaining necessary support.
14871 This option enables support for the HP9000/300 series of
14872 workstations. Support for these machines is still very experimental.
14873 If you plan to try to use the kernel on such a machine say Y here.
14874 Everybody else says N.
14878 This option enables support for the Sun 3x series of workstations.
14879 Be warned that this support is very experimental. You will also want
14880 to say Y to 68020 support and N to the other processors below.
14882 If you don't want to compile a kernel for a Sun 3x, say N.
14886 If you anticipate running this kernel on a computer with a MC68020
14887 processor, say Y. Otherwise, say N. Note that the 68020 requires a
14888 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
14889 Sun 3, which provides its own version.
14893 If you anticipate running this kernel on a computer with a MC68030
14894 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
14895 work, as it does not include an MMU (Memory Management Unit).
14899 If you anticipate running this kernel on a computer with a MC68LC040
14900 or MC68040 processor, say Y. Otherwise, say N. Note that an
14901 MC68EC040 will not work, as it does not include an MMU (Memory
14906 If you anticipate running this kernel on a computer with a MC68060
14907 processor, say Y. Otherwise, say N.
14909 Math emulation support (EXPERIMENTAL)
14911 At some point in the future, this will cause floating-point math
14912 instructions to be emulated by the kernel on machines that lack a
14913 floating-point math coprocessor. Thrill-seekers and chronically
14914 sleep-deprived psychotic hacker types can say Y now, everyone else
14915 should probably wait a while.
14917 Math emulation only kernel
14918 CONFIG_M68KFPU_EMU_ONLY
14919 This option prevents any floating-point instructions from being
14920 compiled into the kernel, thereby the kernel doesn't save any
14921 floating point context anymore during task switches, so this
14922 kernel will only be usable on machines without a floating-point
14923 math coprocessor. This makes the kernel a bit faster as no tests
14924 needs to be executed whether a floating-point instruction in the
14925 kernel should be executed or not.
14927 Math emulation extra precision
14928 CONFIG_M68KFPU_EMU_EXTRAPREC
14929 The fpu uses normally a few bit more during calculations for
14930 correct rounding, the emulator can (often) do the same but this
14931 extra calculation can cost quite some time, so you can disable
14932 it here. The emulator will then "only" calculate with a 64 bit
14933 mantissa and round slightly incorrect, what is more then enough
14936 Advanced configuration options
14938 This gives you access to some advanced options for the CPU. The
14939 defaults should be fine for most users, but these options may make
14940 it possible for you to improve performance somewhat if you know what
14943 Note that the answer to this question won't directly affect the
14944 kernel: saying N will just cause this configure script to skip all
14945 the questions about these options.
14947 Most users should say N to this question.
14949 Use read-modify-write instructions
14951 This allows to use certain instructions that work with indivisible
14952 read-modify-write bus cycles. While this is faster than the
14953 workaround of disabling interrupts, it can conflict with DMA
14954 ( = direct memory access) on many Amiga systems, and it is also said
14955 to destabilize other machines. It is very likely that this will
14956 cause serious problems on any Amiga or Atari Medusa if set. The only
14957 configuration where it should work are 68030-based Ataris, where it
14958 apparently improves performance. But you've been warned! Unless you
14959 really know what you are doing, say N. Try Y only if you're quite
14962 Amiga AutoConfig Identification
14964 This enables support for automatic identification of Amiga expansion
14965 cards that obey the AutoConfig(tm) specification.
14966 Say Y if you want your expansion cards to be identified on bootup;
14967 it will enlarge your kernel by about 10 KB. The identification
14968 information is then also available through /proc/zorro (say Y to
14969 "/proc file system support"!). Read Documentation/zorro.txt for more
14972 Note that even if you say N here, you can still use your expansion
14973 cards. If in doubt, say Y.
14975 Amiga 1200/600 PCMCIA support (EXPERIMENTAL)
14976 CONFIG_AMIGA_PCMCIA
14977 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
14978 600. If you intend to use pcmcia cards say Y; otherwise say N.
14980 Amiga Zorro II ramdisk support
14982 This enables support for using Chip RAM and Zorro II RAM as a
14983 ramdisk or as a swap partition. Say Y if you want to include this
14984 driver in the kernel. This driver is also available as a module
14985 ( = code which can be inserted in and removed from the running
14986 kernel whenever you want). The module is called z2ram.o. If you want
14987 to compile it as a module, say M here and read
14988 Documentation/modules.txt.
14990 Atari ST-RAM swap support
14992 This enables support for using (parts of) ST-RAM as swap space,
14993 instead of as normal system memory. This can first enhance system
14994 performance if you have lots of alternate RAM (compared to the size
14995 of ST-RAM), because executable code always will reside in faster
14996 memory. ST-RAM will remain as ultra-fast swap space. On the other
14997 hand, it allows much improved dynamic allocations of ST-RAM buffers
14998 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
14999 sound). The probability that such allocations at module load time
15000 fail is drastically reduced.
15004 This enables support for the Atari ACSI interface. The driver
15005 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
15006 be switched to that mode. Due to the ACSI command format, only disks
15007 up to 1 GB are supported. Special support for certain ACSI to SCSI
15008 adapters, which could relax that, isn't included yet. The ACSI
15009 driver is also the basis for certain other drivers for devices
15010 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
15011 Ethernet, and PAMsNet Ethernet. If you want to use one of these
15012 devices, you need ACSI support, too.
15014 This driver is also available as a module ( = code which can be
15015 inserted in and removed from the running kernel whenever you want).
15016 The module will be called acsi.o.
15018 Probe all LUNs on each ACSI device
15019 CONFIG_ACSI_MULTI_LUN
15020 If you have a ACSI device that supports more than one LUN (Logical
15021 Unit Number), e.g. a CD jukebox, you should say Y here so that all
15022 will be found by the ACSI driver. An ACSI device with multiple LUNs
15023 acts logically like multiple ACSI devices. The vast majority of ACSI
15024 devices have only one LUN, and so most people can say N here and
15025 should in fact do so, because it is safer.
15027 Atari SLM laser printer support
15029 If you have an Atari SLM laser printer, say Y to include support for
15030 it in the kernel. Otherwise, say N. This driver is also available as
15031 a module ( = code which can be inserted in and removed from the
15032 running kernel whenever you want). The module will be called
15033 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
15034 problems due to that fact!
15036 A3000 WD33C93A support
15038 If you have an Amiga 3000 and have SCSI devices connected to the
15039 built-in SCSI controller, say Y. Otherwise, say N. This driver is
15040 also available as a module ( = code which can be inserted in and
15041 removed from the running kernel whenever you want). The module is
15042 called wd33c93.o. If you want to compile it as a module, say M here
15043 and read Documentation/modules.txt.
15045 A2091 WD33C93A support
15047 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
15048 say N. This driver is also available as a module ( = code which can
15049 be inserted in and removed from the running kernel whenever you
15050 want). The module is called wd33c93.o. If you want to compile it as
15051 a module, say M here and read Documentation/modules.txt.
15053 GVP Series II WD33C93A support
15055 If you have a Great Valley Products Series II SCSI controller,
15056 answer Y. Also say Y if you have a later model of GVP SCSI
15057 controller (such as the GVP A4008 or a Combo board). Otherwise,
15058 answer N. This driver does NOT work for the T-Rex series of
15059 accelerators from TekMagic and GVP-M.
15061 This driver is also available as a module ( = code which can be
15062 inserted in and removed from the running kernel whenever you
15063 want). The module will be called gvp11.o. If you want to compile it
15064 as a module, say M here and read Documentation/modules.txt.
15066 Cyberstorm SCSI support
15067 CONFIG_CYBERSTORM_SCSI
15068 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
15069 accelerator board and the optional Cyberstorm SCSI controller,
15070 answer Y. Otherwise, say N.
15072 Cyberstorm II SCSI support
15073 CONFIG_CYBERSTORMII_SCSI
15074 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
15075 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
15078 Blizzard 2060 SCSI support (EXPERIMENTAL)
15079 CONFIG_BLZ2060_SCSI
15080 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
15081 and want to use the onboard SCSI controller, say Y. Otherwise,
15084 Blizzard 1230IV/1260 SCSI support
15085 CONFIG_BLZ1230_SCSI
15086 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
15087 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
15090 Blizzard PowerUP 603e+ SCSI support
15091 CONFIG_BLZ603EPLUS_SCSI
15092 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
15093 accelerator, say Y. Otherwise, say N.
15095 Fastlane SCSI support
15096 CONFIG_FASTLANE_SCSI
15097 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
15098 one in the near future, say Y to this question. Otherwise, say N.
15100 Atari native SCSI support
15102 If you have an Atari with built-in NCR5380 SCSI controller (TT,
15103 Falcon, ...) say Y to get it supported. Of course also, if you have
15104 a compatible SCSI controller (e.g. for Medusa). This driver is also
15105 available as a module ( = code which can be inserted in and removed
15106 from the running kernel whenever you want). The module is called
15107 atari_scsi.o. If you want to compile it as a module, say M here and
15108 read Documentation/modules.txt. This driver supports both styles of
15109 NCR integration into the system: the TT style (separate DMA), and
15110 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
15111 other schemes, like in the Hades (without DMA).
15113 Long delays for Toshiba CD-ROMs
15114 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
15115 This option increases the delay after a SCSI arbitration to
15116 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
15117 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
15118 would impact performance a bit, so say N.
15120 Hades SCSI DMA emulator
15122 This option enables code which emulates the TT SCSI DMA chip on the
15123 Hades. This increases the SCSI transfer rates at least ten times
15124 compared to PIO transfers.
15128 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
15131 This driver is also available as a module ( = code which can be
15132 inserted in and removed from the running kernel whenever you
15133 want). The module is called ariadne.o. If you want to compile it as
15134 a module, say M here and read Documentation/modules.txt.
15138 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
15141 This driver is also available as a module ( = code which can be
15142 inserted in and removed from the running kernel whenever you
15143 want). The module is called ariadne2.o. If you want to compile it as
15144 a module, say M here and read Documentation/modules.txt.
15148 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
15151 This driver is also available as a module ( = code which can be
15152 inserted in and removed from the running kernel whenever you
15153 want). The module is called a2065.o. If you want to compile it as a
15154 module, say M here and read Documentation/modules.txt.
15158 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
15160 This driver is also available as a module ( = code which can be
15161 inserted in and removed from the running kernel whenever you
15162 want). The module is called hydra.o. If you want to compile it as a
15163 module, say M here and read Documentation/modules.txt.
15165 Pcmcia NE2000 compatible support
15167 If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
15170 This driver is also available as a module ( = code which can be
15171 inserted in and removed from the running kernel whenever you
15172 want). The module is called apne.o. If you want to compile it as a
15173 module, say M here and read Documentation/modules.txt.
15175 Atari Lance support
15177 Say Y to include support for several Atari Ethernet adapters based
15178 on the AMD Lance chipset: RieblCard (with or without battery), or
15179 PAMCard VME (also the version by Rhotron, with different addresses).
15182 CONFIG_ATARI_BIONET
15183 Say Y to include support for BioData's BioNet-100 Ethernet adapter
15184 for the ACSI port. The driver works (has to work...) with a polled
15185 I/O scheme, so it's rather slow :-(
15188 CONFIG_ATARI_PAMSNET
15189 Say Y to include support for the PAMsNet Ethernet adapter for the
15190 ACSI port ("ACSI node"). The driver works (has to work...) with a
15191 polled I/O scheme, so it's rather slow :-(
15193 Amiga mouse support
15195 If you want to be able to use an Amiga mouse in Linux, say Y.
15197 This driver is also available as a module ( = code which can be
15198 inserted in and removed from the running kernel whenever you want).
15199 The module is called amigamouse.o. If you want to compile it as a
15200 module, say M here and read Documentation/modules.txt.
15202 Atari mouse support
15204 If you want to be able to use an Atari mouse in Linux, say Y.
15206 This driver is also available as a module ( = code which can be
15207 inserted in and removed from the running kernel whenever you want).
15208 The module is called atarimouse.o. If you want to compile it as a
15209 module, say M here and read Documentation/modules.txt.
15211 Atari MFP serial support
15212 CONFIG_ATARI_MFPSER
15213 If you like to use the MFP serial ports ("Modem1", "Serial1") under
15214 Linux, say Y. The driver equally supports all kinds of MFP serial
15215 ports and automatically detects whether Serial1 is available.
15217 This driver is also available as a module ( = code which can be
15218 inserted in and removed from the running kernel whenever you want).
15219 If you want to compile it as a module, say M here and read
15220 Documentation/modules.txt.
15222 Note for Falcon users: You also have an MFP port, it's just not
15223 wired to the outside... But you could use the port under Linux.
15225 Atari SCC serial support
15227 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
15228 LAN) and like to use them under Linux, say Y. All built-in SCC's are
15229 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
15230 two connectors for channel A (Serial2 and LAN), they are visible as
15231 two separate devices.
15233 This driver is also available as a module ( = code which can be
15234 inserted in and removed from the running kernel whenever you want).
15235 If you want to compile it as a module, say M here and read
15236 Documentation/modules.txt.
15238 Atari SCC serial DMA support
15239 CONFIG_ATARI_SCC_DMA
15240 This enables DMA support for receiving data on channel A of the SCC.
15241 If you have a TT you may say Y here and read
15242 drivers/char/atari_SCC.README. All other users should say N here,
15243 because only the TT has SCC-DMA, even if your machine keeps claiming
15246 Atari MIDI serial support
15248 If you want to use your Atari's MIDI port in Linux, say Y.
15250 This driver is also available as a module ( = code which can be
15251 inserted in and removed from the running kernel whenever you
15252 want). If you want to compile it as a module, say M here and read
15253 Documentation/modules.txt.
15255 Atari DSP56k Digital Signal Processor support (EXPERIMENTAL)
15256 CONFIG_ATARI_DSP56K
15257 If you want to be able to use the DSP56001 in Falcons, say Y. This
15258 driver is still experimental, and if you don't know what it is, or
15259 if you don't have this processor, just say N.
15261 This driver is also available as a module ( = code which can be
15262 inserted in and removed from the running kernel whenever you want).
15263 If you want to compile it as a module, say M here and read
15264 Documentation/modules.txt.
15266 Amiga builtin serial support
15267 CONFIG_AMIGA_BUILTIN_SERIAL
15268 If you want to use your Amiga's built-in serial port in Linux,
15271 This driver is also available as a module ( = code which can be
15272 inserted in and removed from the running kernel whenever you
15273 want). If you want to compile it as a module, say M here and read
15274 Documentation/modules.txt.
15276 GVP IO-Extender support
15278 If you want to use a GVP IO-Extender serial card in Linux, say Y.
15281 Multiface Card III serial support
15282 CONFIG_MULTIFACE_III_TTY
15283 If you want to use a Multiface III card's serial port in Linux,
15286 This driver is also available as a module ( = code which can be
15287 inserted in and removed from the running kernel whenever you want).
15288 If you want to compile it as a module, say M here and read
15289 Documentation/modules.txt.
15291 Atari DMA sound support
15292 CONFIG_DMASOUND_ATARI
15293 If you want to use the internal audio of your Atari in Linux, answer
15294 Y to this question. This will provide a Sun-like /dev/audio,
15295 compatible with the Linux/i386 sound system. Otherwise, say N.
15297 This driver is also available as a module ( = code which can be
15298 inserted in and removed from the running kernel whenever you
15299 want). If you want to compile it as a module, say M here and read
15300 Documentation/modules.txt.
15302 PowerMac DMA sound support
15303 CONFIG_DMASOUND_AWACS
15304 If you want to use the internal audio of your PowerMac in Linux,
15305 answer Y to this question. This will provide a Sun-like /dev/audio,
15306 compatible with the Linux/i386 sound system. Otherwise, say N.
15308 This driver is also available as a module ( = code which can be
15309 inserted in and removed from the running kernel whenever you
15310 want). If you want to compile it as a module, say M here and read
15311 Documentation/modules.txt.
15313 Amiga DMA sound support
15314 CONFIG_DMASOUND_PAULA
15315 If you want to use the internal audio of your Amiga in Linux, answer
15316 Y to this question. This will provide a Sun-like /dev/audio,
15317 compatible with the Linux/i386 sound system. Otherwise, say N.
15319 This driver is also available as a module ( = code which can be
15320 inserted in and removed from the running kernel whenever you
15321 want). If you want to compile it as a module, say M here and read
15322 Documentation/modules.txt.
15325 CONFIG_DMASOUND_Q40
15326 If you want to use the internal audio of your Q40 in Linux, answer
15327 Y to this question. This will provide a Sun-like /dev/audio,
15328 compatible with the Linux/i386 sound system. Otherwise, say N.
15330 This driver is also available as a module ( = code which can be
15331 inserted in and removed from the running kernel whenever you
15332 want). If you want to compile it as a module, say M here and read
15333 Documentation/modules.txt.
15335 HP DCA serial support
15337 If you want to use the internal "DCA" serial ports on an HP300
15338 machine, say Y here.
15340 HP on-board LANCE support
15342 If you want to use the builtin "LANCE" Ethernet controller on an
15343 HP300 machine, say Y here.
15347 Say Y here to enable support for the "DIO" expansion bus used in
15348 HP300 machines. If you are using such a system you almost certainly
15353 There are four types of PowerPC chips supported. The more common
15354 types (601, 603, 604, 740, 750), the Motorola embedded versions
15355 (821, 823, 850, 855, 860), the IBM embedded versions (403 and
15356 405) and the high end 64 bit Power processors (Power 3, Power 4).
15357 Unless you are building a kernel for one of the embedded
15358 processor systems, or a 64 bit IBM RS/6000, choose 6xx. Note that
15359 the kernel runs in 32-bit mode even on 64-bit chips.
15363 Linux currently supports several different kinds of PowerPC-based
15364 machines: Apple Power Macintoshes and clones (such as the Motorola
15365 Starmax series), PReP (PowerPC Reference Platform) machines such as
15366 the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
15367 embedded MBX boards from Motorola. Currently, a single kernel binary
15368 only supports one type or the other. However, there is very early
15369 work on support for CHRP, PReP and PowerMac's from a single binary.
15371 Power management support for PowerBooks
15373 This provides support for putting a PowerBook to sleep; it also
15374 enables media bay support. Power management works on the
15375 PB2400/3400/3500, Wallstreet, Lombard, and Bronze PowerBook G3. You
15376 must get the power management daemon, pmud, to make it work and you
15377 must have the /dev/pmu device (see the pmud README).
15379 Get pmud from ftp://linuxcare.com.au/pub/ppclinux/pmud/
15381 If you have a PowerBook, you should say Y.
15383 You may also want to compile the dma sound driver as a module and
15384 have it autoloaded. The act of removing the module shuts down the
15385 sound hardware for more power savings.
15387 Support for Open Firmware device tree in /proc
15388 CONFIG_PROC_DEVICETREE
15389 This option adds a device-tree directory under /proc which contains
15390 an image of the device tree that the kernel copies from Open
15391 Firmware. If unsure, say Y here.
15393 MESH (Power Mac internal SCSI) support
15395 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
15396 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
15397 other Power Macintoshes do). Say Y to include support for this SCSI
15398 adaptor. This driver is also available as a module called mesh.o
15399 ( = code which can be inserted in and removed from the running
15400 kernel whenever you want). If you want to compile it as a module,
15401 say M here and read Documentation/modules.txt.
15403 Maximum synchronous transfer rate
15404 CONFIG_SCSI_MESH_SYNC_RATE
15405 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
15406 drives a bus which is entirely internal to the machine (such as the
15407 7500, 7600, 8500, etc.), the MESH is capable of synchronous
15408 operation at up to 10 MB/s. On machines where the SCSI bus
15409 controlled by the MESH can have external devices connected, it is
15410 usually rated at 5 MB/s. 5 is a safe value here unless you know the
15411 MESH SCSI bus is internal only; in that case you can say 10. Say 0
15412 to disable synchronous operation.
15414 53C94 (Power Mac external SCSI) support
15415 CONFIG_SCSI_MAC53C94
15416 On Power Macintoshes (and clones) with two SCSI buses, the external
15417 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
15418 machines which only have one SCSI bus, such as the 7200, also use
15419 the 53C94. Say Y to include support for the 53C94.
15421 This driver is also available as a module called mac53c94.o ( = code
15422 which can be inserted in and removed from the running kernel
15423 whenever you want). If you want to compile it as a module, say M
15424 here and read Documentation/modules.txt.
15426 MACE (Power Mac Ethernet) support
15428 Power Macintoshes and clones with Ethernet built-in on the
15429 motherboard will usually use a MACE (Medium Access Control for
15430 Ethernet) interface. Say Y to include support for the MACE chip.
15432 This driver is also available as a module called mace.o ( = code
15433 which can be inserted in and removed from the running kernel
15434 whenever you want). If you want to compile it as a module, say M
15435 here and read Documentation/modules.txt.
15437 BMAC (G3 ethernet) support
15439 Say Y for support of BMAC Ethernet interfaces. These are used on G3
15442 This driver is also available as a module called bmac.o ( = code
15443 which can be inserted in and removed from the running kernel
15444 whenever you want). If you want to compile it as a module, say M
15445 here and read Documentation/modules.txt.
15447 GMAC (G4/iBook ethernet) support
15449 Say Y for support of GMAC Ethernet interfaces. These are used on G4
15450 and iBook computers.
15452 This driver is also available as a module called gmac.o ( = code
15453 which can be inserted in and removed from the running kernel
15454 whenever you want). If you want to compile it as a module, say M
15455 here and read Documentation/modules.txt.
15457 Symbios 53c885 (Synergy ethernet) support
15459 This is and Ethernet driver for the dual-function NCR 53C885
15460 SCSI/Ethernet controller.
15462 This driver is also available as a module called ncr885e.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 National DP83902AV (Oak ethernet) support
15469 Say Y if your machine has this type of Ethernet network card.
15471 This driver is also available as a module called oaknet.o ( = code
15472 which can be inserted in and removed from the running kernel
15473 whenever you want). If you want to compile it as a module, say M
15474 here and read Documentation/modules.txt.
15478 Support for audio/video capture and overlay devices and FM radio
15479 cards. The exact capabilities of each device vary. User tools for
15480 this are available from
15481 ftp://ftp.uk.linux.org/pub/linux/video4linux .
15483 If you are interested in writing a driver for such an audio/video
15484 device or user software interacting with such a driver, please read
15485 the file Documentation/video4linux/API.html.
15487 This driver is also available as a module called videodev.o ( = code
15488 which can be inserted in and removed from the running kernel
15489 whenever you want). If you want to compile it as a module, say M
15490 here and read Documentation/modules.txt.
15492 Video For Linux /proc file system information
15493 CONFIG_VIDEO_PROC_FS
15494 If you say Y here, you are able to access video device information
15497 To use this option, you have to check, that the "/proc file system
15498 support" (CONFIG_PROC_FS) is enabled too.
15500 AIMSlab RadioTrack (aka RadioReveal) support
15501 CONFIG_RADIO_RTRACK
15502 Choose Y here if you have one of these FM radio cards, and then fill
15503 in the port address below.
15505 Note that newer AIMSlab RadioTrack cards have a different chipset
15506 and are not supported by this driver. For these cards, use the
15507 RadioTrack II driver below.
15509 If you have a GemTeks combined (PnP) sound- and radio card you must
15510 use this driver as a module and setup the card with isapnptools. You
15511 must also pass the module a suitable io parameter, 0x248 has been
15512 reported to be used by these cards.
15514 In order to control your radio card, you will need to use programs
15515 that are compatible with the Video for Linux API. Information on
15516 this API and pointers to "v4l" programs may be found on the WWW at
15517 http://roadrunner.swansea.uk.linux.org/v4l.shtml . More information
15518 is contained in the file Documentation/video4linux/radiotrack.txt.
15520 If you want to compile this driver as a module ( = code which can be
15521 inserted in and removed from the running kernel whenever you want),
15522 say M here and read Documentation/modules.txt. The module will be
15523 called radio-aimslab.o.
15525 RadioTrack i/o port
15526 CONFIG_RADIO_RTRACK_PORT
15527 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
15528 haven't changed the jumper setting on the card.
15530 AIMSlab RadioTrack II support
15531 CONFIG_RADIO_RTRACK2
15532 Choose Y here if you have this FM radio card, and then fill in the
15533 port address below.
15535 In order to control your radio card, you will need to use programs
15536 that are compatible with the Video for Linux API. Information on
15537 this API and pointers to "v4l" programs may be found on the WWW at
15538 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15540 If you want to compile this driver as a module ( = code which can be
15541 inserted in and removed from the running kernel whenever you want),
15542 say M here and read Documentation/modules.txt. The module will be
15543 called radio-rtrack2.o.
15545 RadioTrack II i/o port
15546 CONFIG_RADIO_RTRACK2_PORT
15547 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
15548 haven't changed the jumper setting on the card.
15550 Aztech/Packard Bell Radio
15551 CONFIG_RADIO_AZTECH
15552 Choose Y here if you have one of these FM radio cards, and then fill
15553 in the port address below.
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 .
15560 If you want to compile this driver as a module ( = code which can be
15561 inserted in and removed from the running kernel whenever you want),
15562 say M here and read Documentation/modules.txt. The module will be
15563 called radio-aztech.o.
15565 Aztech/Packard Bell radio card i/o port
15566 CONFIG_RADIO_AZTECH_PORT
15567 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
15568 haven't changed the setting of jumper JP3 on the card. Removing the
15569 jumper sets the card to 0x358.
15571 ADS Cadet AM/FM Radio Tuner Card
15573 Choose Y here if you have one of these AM/FM radio cards, and then
15574 fill in the 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 Further documentation on this driver can be found on the WWW at
15582 http://linux.blackhawke.net/cadet.html .
15584 If you want to compile this driver as a module ( = code which can be
15585 inserted in and removed from the running kernel whenever you want),
15586 say M here and read Documentation/modules.txt. The module will be
15587 called radio-cadet.o.
15590 CONFIG_RADIO_SF16FMI
15591 Choose Y here if you have one of these FM radio cards, and then fill
15592 in the port address below.
15594 In order to control your radio card, you will need to use programs
15595 that are compatible with the Video for Linux API. Information on
15596 this API and pointers to "v4l" programs may be found on the WWW at
15597 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15599 If you want to compile this driver as a module ( = code which can be
15600 inserted in and removed from the running kernel whenever you want),
15601 say M here and read Documentation/modules.txt. The module will be
15602 called radio-sf16fmi.o
15604 SF16FMI I/O port (0x284 or 0x384)
15605 CONFIG_RADIO_SF16FMI_PORT
15606 Enter the I/O port of your SF16FMI radio card.
15609 CONFIG_RADIO_TYPHOON
15610 Choose Y here if you have one of these FM radio cards, and then fill
15611 in the port address and the frequency used for muting below.
15613 In order to control your radio card, you will need to use programs
15614 that are compatible with the Video for Linux API. Information on
15615 this API and pointers to "v4l" programs may be found on the WWW at
15616 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15618 If you want to compile this driver as a module ( = code which can be
15619 inserted in and removed from the running kernel whenever you want),
15620 say M here and read Documentation/modules.txt. The module will be
15621 called radio-typhoon.o
15623 Support for /proc/radio-typhoon
15624 CONFIG_RADIO_TYPHOON_PROC_FS
15625 Say Y here if you want the typhoon radio card driver to write
15626 status information (frequency, volume, muted, mute frequency,
15627 base address) to /proc/radio-typhoon. The file can be viewed with
15628 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
15629 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
15631 Typhoon I/O port (0x316 or 0x336)
15632 CONFIG_RADIO_TYPHOON_PORT
15633 Enter the I/O port of your Typhoon or EcoRadio radio card.
15635 Typhoon frequency set when muting the device (kHz)
15636 CONFIG_RADIO_TYPHOON_MUTEFREQ
15637 Enter the frequency used for muting the radio. The device is never
15638 completely silent. If the volume is just turned down, you can still
15639 hear silent voices and music. For that reason, the frequency of the
15640 radio device is set to the frequency you can enter here whenever
15641 the device is muted. There should be no local radio station at that
15645 CONFIG_RADIO_ZOLTRIX
15646 Choose Y here if you have one of these FM radio cards, and then fill
15647 in the port address below.
15649 In order to control your radio card, you will need to use programs
15650 that are compatible with the Video for Linux API. Information on
15651 this API and pointers to "v4l" programs may be found on the WWW at
15652 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15654 If you want to compile this driver as a module ( = code which can be
15655 inserted in and removed from the running kernel whenever you want),
15656 say M here and read Documentation/modules.txt. The module will be
15657 called radio-zoltrix.o
15659 ZOLTRIX I/O port (0x20c or 0x30c)
15660 CONFIG_RADIO_ZOLTRIX_PORT
15661 Enter the I/O port of your Zoltrix radio card.
15663 IIC on parallel port
15665 I2C is a simple serial bus system used in many micro controller
15666 applications. Saying Y here will allow you to use your parallel port
15667 as an I2C interface.
15669 If you want to compile this driver as a module ( = code which can be
15670 inserted in and removed from the running kernel whenever you want),
15671 say M here and read Documentation/modules.txt. The module will be
15672 called i2c-parport.o.
15675 CONFIG_RADIO_MIROPCM20
15676 Choose Y here if you have this FM radio card. You also need to say Y
15677 to "ACI mixer (miroPCM12/PCM20)" (in "additional low level sound
15678 drivers") for this to work.
15680 In order to control your radio card, you will need to use programs
15681 that are compatible with the Video for Linux API. Information on
15682 this API and pointers to "v4l" programs may be found on the WWW at
15683 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15685 If you want to compile this driver as a module ( = code which can be
15686 inserted in and removed from the running kernel whenever you want),
15687 say M here and read Documentation/modules.txt. The module will be
15688 called radio-miropcm20.o
15691 CONFIG_RADIO_GEMTEK
15692 Choose Y here if you have this FM radio card, and then fill in the
15693 port address below.
15695 In order to control your radio card, you will need to use programs
15696 that are compatible with the Video for Linux API. Information on
15697 this API and pointers to "v4l" programs may be found on the WWW at
15698 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15700 If you want to compile this driver as a module ( = code which can be
15701 inserted in and removed from the running kernel whenever you want),
15702 say M here and read Documentation/modules.txt. The module will be
15703 called radio-gemtek.o.
15706 CONFIG_RADIO_GEMTEK_PORT
15707 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
15708 0x34c, if you haven't changed the jumper setting on the card. On
15709 Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the i/o
15712 PlanB Video-In for PowerMacs
15714 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
15715 input hardware. If you want to experiment with this, say Y.
15716 Otherwise, or if you don't understand a word, say N.
15717 See http://www.cpu.lu/~mlan/planb.html for more info.
15719 Saying M will compile this driver as a module (planb.o).
15721 TerraTec ActiveRadio
15722 CONFIG_RADIO_TERRATEC
15723 Choose Y here if you have this FM radio card, and then fill in the
15724 port address below. (TODO)
15726 Note: This driver is in its early stages. Right now volume and
15727 frequency control and muting works at least for me, but
15728 unfortunately i have not found anybody who wants to use this card
15729 with Linux. So if it is this what YOU are trying to do right now,
15730 PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
15732 In order to control your radio card, you will need to use programs
15733 that are compatible with the Video for Linux API. Information on
15734 this API and pointers to "v4l" programs may be found on the WWW at
15735 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15737 If you want to compile this driver as a module ( = code which can be
15738 inserted in and removed from the running kernel whenever you want),
15739 say M here and read Documentation/modules.txt. The module will be
15740 called radio-terratec.o.
15742 Terratec i/o port (normally 0x590)
15743 CONFIG_RADIO_TERRATEC_PORT
15744 Fill in the i/o port of your TerraTec FM radio card. If unsure, go
15748 # Zoran ZR36057/36060 support
15749 # CONFIG_VIDEO_ZORAN
15751 # Include support for Iomega Buz
15754 Trust FM radio card
15756 This is a driver for the Trust FM radio cards. Say Y if you have
15757 such a card and want to use it under Linux.
15759 This driver is also available as a module called radio-trust.o ( =
15760 code which can be inserted in and removed from the running kernel
15761 whenever you want). If you want to compile it as a module, say M
15762 here and read Documentation/modules.txt.
15764 Trust i/o port (usually 0x350 or 0x358)
15765 CONFIG_RADIO_TRUST_PORT
15766 Enter the i/o port of your Trust FM radio card. If unsure, try the
15767 values "0x350" or "0x358".
15769 BT848 Video For Linux
15771 Support for BT848 based frame grabber/overlay boards. This includes
15772 the Miro, Hauppauge and STB boards. Please read the material in
15773 Documentation/video4linux/bttv for more information.
15775 If you say Y or M here, you need to say Y or M to "I2C support" and
15776 "I2C bit-banging interfaces" in the character device section.
15778 This driver is available as a module called bttv.o ( = code
15779 which can be inserted in and removed from the running kernel
15780 whenever you want). If you want to compile it as a module, say M
15781 here and read Documentation/modules.txt.
15783 ZR36120/36125 Video for Linux
15784 CONFIG_VIDEO_ZR36120
15785 Support for ZR36120/ZR36125 based frame grabber/overlay boards.
15786 This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV,
15787 and Buster boards. Please read the material in
15788 Documentation/video4linux/zr36120.txt for more information.
15790 This driver is also available as a module called zr36120.o ( = code
15791 which can be inserted in and removed from the running kernel
15792 whenever you want). If you want to compile it as a module, say M
15793 here and read Documentation/modules.txt.
15795 SAA5249 Teletext processor
15796 CONFIG_VIDEO_SAA5249
15797 Support for I2C bus based teletext using the SAA5249 chip. At the
15798 moment this is only useful on some European WinTV cards.
15800 This driver is also available as a module called saa5249.o ( = code
15801 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 Quickcam BW Video For Linux
15806 CONFIG_VIDEO_BWQCAM
15807 Say Y have if you the black and white version of the QuickCam
15808 camera. See the next option for the color version.
15810 This driver is also available as a module called bw-qcam.o ( = code
15811 which can be inserted in and removed from the running kernel
15812 whenever you want). If you want to compile it as a module, say M
15813 here and read Documentation/modules.txt.
15815 Colour QuickCam Video For Linux
15817 This is the video4linux driver for the colour version of the
15818 Connectix Quickcam. If you have one of these cameras, say Y here,
15819 otherwise say N. This driver does not work with the original
15820 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
15821 as a module (c-qcam.o). Read Documentation/video4linux/CQcam.txt for
15824 CPiA Video For Linux
15826 This is the video4linux driver for cameras based on Vision's CPiA
15827 (Colour Processor Interface ASIC), such as the Creative Labs Video
15828 Blaster Webcam II. If you have one of these cameras, say Y here
15829 and select parallel port and/or USB lowlevel support below,
15830 otherwise say N. This will not work with the Creative Webcam III.
15832 Please read Documentation/video4linux/README.cpia for more
15835 This driver is also available as a module (cpia.o).
15837 CPiA Parallel Port Lowlevel Support
15838 CONFIG_VIDEO_CPIA_PP
15839 This is the lowlevel parallel port support for cameras based on
15840 Vision's CPiA (Colour Processor Interface ASIC), such as the
15841 Creative Webcam II. If you have the parallel port version of one
15842 of these cameras, say Y here, otherwise say N. It is also available
15843 as a module (cpia_pp.o).
15845 CPiA USB Lowlevel Support
15846 CONFIG_VIDEO_CPIA_USB
15847 This is the lowlevel USB support for cameras based on Vision's CPiA
15848 (Colour Processor Interface ASIC), such as the Creative Webcam II.
15849 If you have the USB version of one of these cameras, say Y here,
15850 otherwise say N. This will not work with the Creative Webcam III.
15851 It is also available as a module (cpia_usb.o).
15853 Mediavision Pro Movie Studio Video For Linux
15855 Say Y if you have such a thing. This driver is also available as a
15856 module called pms.o ( = code which can be inserted in and removed
15857 from the running kernel whenever you want). If you want to compile
15858 it as a module, say M here and read Documentation/modules.txt.
15860 SAB3036 tuner support
15862 Say Y here to include support for Philips SAB3036 compatible tuners.
15863 If in doubt, say N.
15865 Compaq SMART2 support
15867 This is the driver for Compaq Smart Array controllers.
15868 Everyone using these boards should say Y here.
15869 See the file Documentation/cpqarray.txt for the current list of
15870 boards supported by this driver, and for further information
15871 on the use of this driver.
15878 This selects what ARM system you wish to build the kernel for. It
15879 also selects to some extent the CPU type. If you are unsure what
15880 to set this option to, please consult any information supplied with
15883 Include support for the CATS
15885 Say Y here if you intend to run this kernel on the CATS.
15887 Saying N will reduce the size of the Footbridge kernel.
15889 Include support for the EBSA285
15890 CONFIG_ARCH_EBSA285
15891 Say Y here if you intend to run this kernel on the EBSA285 card
15892 in host ("central function") mode.
15894 Saying N will reduce the size of the Footbridge kernel.
15896 Include support for the LinkUp Systems L7200 SDB
15898 Say Y here if you intend to run this kernel on a LinkUp Systems
15899 L7200 Software Development Board which uses an ARM720T processor.
15900 Information on this board can be obtained at:
15902 http://www.linkupsys.com/
15904 If you have any questions or comments about the Linux kernel port
15905 to this board, send e-mail to sjhill@cotw.com
15907 Include support for the NetWinder
15908 CONFIG_ARCH_NETWINDER
15909 Say Y here if you intend to run this kernel on the Rebel.COM
15910 NetWinder. Information about this machine can be found at:
15912 http://www.netwinder.org/
15914 Saying N will reduce the size of the Footbridge kernel.
15916 Include support for the Compaq Personal Server
15917 CONFIG_ARCH_PERSONAL_SERVER
15918 Say Y here if you intend to run this kernel on the Compaq
15921 Saying N will reduce the size of the Footbridge kernel.
15923 The Compaq Personal Server is not available for purchase.
15924 There are no product plans beyond the current research
15925 prototypes at this time. Information is available at:
15927 http://crl.research.compaq.com/projects/personalserver
15929 If you have any questions or comments about the Compaq Personal
15930 Server, send e-mail to skiff@crl.dec.com
15932 Include support for Assabet
15933 CONFIG_SA1100_ASSABET
15934 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
15935 Microprocessor Development Board (also known as the Assabet).
15937 Include support for Neponset
15938 CONFIG_ASSABET_NEPONSET
15939 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
15940 Microprocessor Development Board (Assabet) with the SA-1111
15941 Development Board (Nepon).
15943 Include support for the Compaq iPAQ H3600 (Bitsy)
15944 CONFIG_SA1100_BITSY
15945 Say Y here if you intend to run this kernel on the Compaq iPAQ
15946 H3600 handheld computer. Information about this machine and the
15947 Linux port to this machine can be found at:
15949 http://www.handhelds.org/Compaq/index.html#iPAQ_H3600
15950 http://www.compaq.com/products/handhelds/pocketpc/
15952 Include support for Brutus
15953 CONFIG_SA1100_BRUTUS
15954 Say Y here if you are using the Intel(R) StrongARM(R) SA-1100
15955 Microprocessor Development Board (also known as the Brutus).
15957 Include support for LART
15959 Say Y here if you are using the Linux Advanced Radio Terminal
15960 (also known as the LART). See http://www.lart.tudelft.nl/ for
15961 information on the LART.
15963 Include support for ThinClient
15964 CONFIG_SA1100_THINCLIENT
15965 Say Y here if you are using an Applied Data Systems Intel(R)
15966 StrongARM(R) SA-1100 based Thin Client SBC. See
15967 http://www.flatpanels.com/ for information on this system.
15969 Include support for GraphicsClient
15970 CONFIG_SA1100_GRAPHICSCLIENT
15971 Say Y here if you are using an Applied Data Systems Intel(R)
15972 StrongARM(R) SA-1100 based Graphics Client SBC. See
15973 http://www.flatpanels.com/ for information on this system.
15975 Include support for Victor
15976 CONFIG_SA1100_VICTOR
15977 Say Y here if you are using a Visu Aide Intel(R) StrongARM(R)
15978 SA-1100 based Victor Digital Talking Book Reader. See
15979 http://www.visuaide.com/pagevictor.en.html for information on
15984 Say Y to include the NWFPE floating point emulator in the kernel.
15985 This is necessary to run most binaries. Linux does not currently
15986 support floating point hardware so you need to say Y here even if
15987 your machine has an FPA or floating point co-processor podule.
15989 It is also possible to say M to build the emulator as a module
15990 (nwfpe.o) or indeed to leave it out altogether. However, unless you
15991 know what you are doing this can easily render your machine
15992 unbootable. Saying Y is the safe option.
15994 You may say N here if you are going to load the Acorn FPEmulator
15995 early in the bootup.
15997 DS1620 Thermometer support
15999 Say Y here to include support for the thermal management hardware
16000 found in the NetWinder. This driver allows the user to control the
16001 temperature set points and to read the current temperature.
16003 It is also possible to say M here to build it as a module (ds1620.o)
16004 It is recommended to be used on a NetWinder, but it is not a
16007 Verbose kernel error messages
16008 CONFIG_DEBUG_ERRORS
16009 This option controls verbose debugging information which can be
16010 printed when the kernel detects an internal error. This debugging
16011 information is useful to kernel hackers when tracking down problems,
16012 but mostly meaningless to other people. It's safe to say Y unless
16013 you are concerned with the code size or don't want to see these
16016 Compile kernel with frame pointer
16017 CONFIG_FRAME_POINTER
16018 If you say Y here, the resulting kernel will be slightly larger and
16019 slower, but it will give useful debugging information. If you don't
16020 debug the kernel, you can say N.
16022 User fault debugging
16024 When a user program crashes due to an exception, the kernel can
16025 print a brief message explaining what the problem was. This is
16026 sometimes helpful for debugging but serves no purpose on a
16027 production system. Most people should say N here.
16029 Include gdb debugging information in kernel binary
16031 Say Y here to include source-level debugging information in the
16032 `vmlinux' binary image. This is handy if you want to use gdb or
16033 addr2line to debug the kernel. It has no impact on the in-memory
16034 footprint of the running kernel but it can increase the amount of
16035 time and disk space needed for compilation of the kernel. If in
16038 Kernel low-level debugging functions
16040 Say Y here to include definitions of printascii, printchar, printhex
16041 in the kernel. This is helpful if you are debugging code that
16042 executes before the console is initialized.
16044 Kernel low-level debugging messages via footbridge serial port
16045 CONFIG_DEBUG_DC21285_PORT
16046 Say Y here if you want the low-level print routines to direct their
16047 output to the serial port in the DC21285 (Footbridge).
16049 Split initialisation functions into discardable section
16050 CONFIG_TEXT_SECTIONS
16051 If you say Y here, kernel code that is only used during
16052 initialisation is collected into a special area of the kernel so
16053 that it can be discarded and the memory reclaimed when
16054 initialisation is complete. In addition, if the kernel you wish to
16055 build is able to run on multiple architectures, it allows the unused
16056 code to be discarded. Some versions of binutils, however, have a bug
16057 that causes the kernel to crash during startup when this option is
16058 enabled. Say Y unless you experience problems that you suspect may
16061 Disable pgtable cache (EXPERIMENTAL)
16062 CONFIG_NO_PGT_CACHE
16063 Normally the kernel maintains a `quicklist' of preallocated
16064 pagetable structures in order to increase performance. On machines
16065 with very few pages this may however be a loss. Say Y here to
16066 disable the pgtable cache.
16068 RISC OS personality
16070 Say Y here to include the kernel code necessary if you want to run
16071 Acorn RISC OS/Arthur binaries under Linux. This code is still very
16072 experimental; if this sounds frightening, say N and sleep in peace.
16073 You can also say M here to compile this support as a module (which
16074 will be called arthur.o).
16076 Initial kernel command line
16078 On some architectures (EBSA110 and CATS), there is currently no way
16079 for the boot loader to pass arguments to the kernel. For these
16080 architectures, you should supply some command-line options at build
16081 time by entering them here. As a minimum, you should specify the
16082 memory size and the root device (e.g., mem=64M root=/dev/nfs)
16084 Hardware alignment trap (EXPERIMENTAL)
16085 CONFIG_ALIGNMENT_TRAP
16086 ARM processors can not fetch/store information which is not
16087 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
16088 address divisible by 4. On 32-bit ARM processors, these non-aligned
16089 fetch/store instructions will be emulated in software if you say
16090 here, which has a severe performance impact. This is necessary for
16091 correct operation of some network protocols. With an IP-only
16092 configuration it is safe to say N, otherwise say Y.
16094 21285 serial port support
16095 CONFIG_SERIAL_21285
16096 If you have a machine based on a 21285 (Footbridge) StrongARM/PCI
16097 bridge you can enable its onboard serial port by enabling this
16098 option. The device has major ID 4, minor 64.
16100 Console on 21285 serial port
16101 CONFIG_SERIAL_21285_CONSOLE
16102 If you have enabled the serial port on the 21285 footbridge you can
16103 make it the console by answering Y to this option.
16105 L7200 serial port support
16106 CONFIG_SERIAL_L7200
16107 If you have a LinkUp Systems L7200 board you can enable its two
16108 onboard serial ports by enabling this option. The device numbers
16109 are major ID 4 with minor 64 and 65 respectively.
16111 Console on L7200 serial port
16112 CONFIG_SERIAL_L7200_CONSOLE
16113 If you have enabled the serial ports on the L7200 development board
16114 you can make the first serial port the console by answering Y to
16118 CONFIG_HOST_FOOTBRIDGE
16119 The 21285 Footbridge chip can operate in either `host mode' or
16120 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
16121 is the configuration master, otherwise say N. This must not be
16122 set to Y if the card is used in 'add-in' mode.
16124 MFM hard disk support
16126 Support the MFM hard drives on the Acorn Archimedes both
16127 on-board the A4x0 motherboards and via the Acorn MFM podules.
16128 Drives up to 64MB are supported. If you haven't got one of these
16129 machines or drives just say N.
16131 Old Archimedes floppy (1772) support
16132 CONFIG_BLK_DEV_FD1772
16133 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
16134 R140 and R260) series of computers; it supports only 720K floppies
16135 at the moment. If you don't have one of these machines just answer
16138 Autodetect hard drive geometry
16139 CONFIG_BLK_DEV_MFM_AUTODETECT
16140 If you answer Y, the MFM code will attempt to automatically detect
16141 the cylinders/heads/sectors count on your hard drive. WARNING: This
16142 sometimes doesn't work and it also does some dodgy stuff which
16143 potentially might damage your drive.
16145 NetWinder /dev/flash support
16147 If you say Y here and create a character device /dev/flash with
16148 major 10 and minor 160 you can manipulate the flash ROM containing
16149 the NetWinder firmware. Be careful as accidentally overwriting the
16150 flash contents can render your computer unbootable. On no account
16151 allow random users access to this device. :-)
16153 This driver is also available as a module ( = code which can be
16154 inserted in and removed from the running kernel whenever you want).
16155 The module will be called nwflash.o. If you want to compile it as a
16156 module, say M here and read Documentation/modules.txt.
16158 If you're not sure, say N.
16160 Footbridge internal watchdog
16161 CONFIG_21285_WATCHDOG
16162 The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
16163 here if you wish to use this. Alternatively say M to compile the
16164 driver as a module, which will be called wdt285.o.
16166 This driver does not work on all machines. In particular, early CATS
16167 boards have hardware problems that will cause the machine to simply
16168 lock up if the watchdog fires.
16170 "If in doubt, leave it out" - say N.
16172 NetWinder WB977 watchdog
16173 CONFIG_977_WATCHDOG
16174 Say Y here to include support for the WB977 watchdog included in
16175 NetWinder machines. Alternatively say M to compile the driver as
16176 a module, which will be called wdt977.o.
16178 Not sure? It's safe to say N.
16180 IrDA subsystem support
16182 Say Y here if you want to build support for the IrDA (TM) protocols.
16183 The Infrared Data Associations (tm) specifies standards for wireless
16184 infrared communication and is supported by most laptops and PDA's.
16186 To use Linux support for the IrDA (tm) protocols, you will also need
16187 some user-space utilities like the irmanager and probably irattach
16188 as well. For more information, see the file
16189 Documentation/networking/irda.txt. You also want to read the
16190 IR-HOWTO, available at http://www.linuxdoc.org/docs.html#howto .
16192 This support is also available as a module called irda.o. If you
16193 want to compile it as a module, say M here and read
16194 Documentation/modules.txt.
16196 IrDA Cache last LSAP
16197 CONFIG_IRDA_CACHE_LAST_LSAP
16198 Say Y here if you want IrLMP to cache the last LSAP used. This makes
16199 sense since most frames will be sent/received on the same
16200 connection. Enabling this option will save a hash-lookup per frame.
16205 CONFIG_IRDA_FAST_RR
16206 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
16207 when acting as a primary station. This will make IrLAP send out a RR
16208 frame immediately when receiving a frame if its own transmit queue
16209 is currently empty. This will give a lot of speed improvement when
16210 receiving much data since the secondary station will not have to
16211 wait the max. turn around time before it is allowed to transmit the
16212 next time. If the transmit queue of the secondary is also empty the
16213 primary will back off waiting longer for sending out the RR frame
16214 until the timeout reaches the normal value. Enabling this option
16215 will make the IR-diode burn more power and thus reduce your battery
16222 Say Y here if you want the IrDA subsystem to write debug information
16223 to your syslog. You can change the debug level in
16224 /proc/sys/net/irda/debug
16226 If unsure, say Y (since it makes it easier to find the bugs).
16228 IrLAP Compression support
16229 CONFIG_IRDA_COMPRESSION
16230 Compression is _not_ part of the IrDA(tm) protocol specification,
16231 but it's working great! Linux is the first to try out compression
16232 support at the IrLAP layer. This means that you will only benefit
16233 from compression if you are running a Linux <-> Linux configuration.
16235 If you say Y here, you also need to say Y or M to a compression
16238 IrLAP Deflate Compression Protocol (EXPERIMENTAL)
16239 CONFIG_IRDA_DEFLATE
16240 Say Y here if you want to build support for the Deflate compression
16241 protocol. The deflate compression (GZIP) is exactly
16242 the same as the one used by the PPP protocol.
16244 If you want to compile this compression support as a module, say M
16245 here and read Documentation/modules.txt. The module will be called
16250 Say Y here if you want to build support for the IrLAN protocol. If
16251 you want to compile it as a module (irlan.o), say M here and read
16252 Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
16253 possible to put up a wireless LAN using infrared beams.
16255 The IrLAN protocol can be used to talk with infrared access points
16256 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
16257 to another Linux machine running the IrLAN protocol for ad-hoc
16262 Say Y here if you want to build support for the IrCOMM protocol. If
16263 you want to compile it as a module (you will get ircomm.o and
16264 ircomm-tty.o), say M here and read Documentation/modules.txt. IrCOMM
16265 implements serial port emulation, and makes it possible to use all
16266 existing applications that understands TTY's with an infrared link.
16267 Thus you should be able to use application like PPP, minicom and
16268 others. Enabling this option will create two modules called ircomm
16271 IrTTY IrDA Device Driver
16273 Say Y here if you want to build support for the IrTTY line
16274 discipline. If you want to compile it as a module (irtty.o), say M
16275 here and read Documentation/modules.txt. IrTTY makes it possible to
16276 use Linux's own serial driver for all IrDA ports that are 16550
16277 compatible. Most IrDA chips are 16550 compatible so you should
16278 probably say Y to this option. Using IrTTY will however limit the
16279 speed of the connection to 115200 bps (IrDA SIR mode)
16283 IrPORT IrDA Device Driver
16285 Say Y here if you want to build support for the IrPORT IrDA device
16286 driver. If you want to compile it as a module (irport.o), say M here
16287 and read Documentation/modules.txt. IrPORT can be used instead of
16288 IrTTY and sometimes this can be better. One example is if your IrDA
16289 port does not have echo-canceling, which will work OK with IrPORT
16290 since this driver is working in half-duplex mode only. You don't
16291 need to use irattach with IrPORT, but you just insert it the same
16292 way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice that
16293 IrPORT is a SIR device driver which means that speed is limited to
16298 Winbond W83977AF IrDA Device Driver
16300 Say Y here if you want to build IrDA support for the Winbond
16301 W83977AF super-io chipset. This driver should be used for the IrDA
16302 chipset in the Corel NetWinder. The driver supports SIR, MIR and FIR
16305 If you want to compile it as a module, say M here and read
16306 Documentation/modules.txt. The module will be called w83977af_ir.o.
16308 NSC PC87108 IrDA Device Driver
16310 Say Y here if you want to build support for the NSC PC87108 and
16311 PC87338 IrDA chipsets. This driver supports SIR,
16312 MIR and FIR (4Mbps) speeds.
16314 If you want to compile it as a module, say M here and read
16315 Documentation/modules.txt. The module will be called nsc-ircc.o.
16317 Toshiba Type-O IR Port Device Driver
16319 Say Y here if you want to build support for the Toshiba Type-O IR
16320 chipset. This chipset is used by the Toshiba Libretto 100CT, and
16321 many more laptops. If you want to compile it as a module, say M here
16322 and read Documentation/modules.txt. The module will be called
16325 SMC IrCC (Experimental)
16326 CONFIG_SMC_IRCC_FIR
16327 Say Y here if you want to build support for the SMC Infrared
16328 Communications Controller. It is used in the Fujitsu Lifebook 635t
16329 and Sony PCG-505TX. If you want to compile it as a module, say M
16330 here and read Documentation/modules.txt. The module will be called
16333 Serial dongle support
16335 Say Y here if you have an infrared device that connects to your
16336 computer's serial port. These devices are called dongles. Then say Y
16337 or M to the driver for your particular dongle below.
16339 Note that the answer to this question won't directly affect the
16340 kernel: saying N will just cause this configure script to skip all
16341 the questions about serial dongles.
16343 ESI JetEye PC Dongle
16345 Say Y here if you want to build support for the Extended Systems
16346 JetEye PC dongle. If you want to compile it as a module, say M here
16347 and read Documentation/modules.txt. The ESI dongle attaches to the
16348 normal 9-pin serial port connector, and can currently only be used
16349 by IrTTY. To activate support for ESI dongles you will have to
16350 start irattach like this: "irattach -d esi".
16352 ACTiSYS IR-220L and IR220L+ dongle
16353 CONFIG_ACTISYS_DONGLE
16354 Say Y here if you want to build support for the ACTiSYS
16355 IR-220L and IR220L+ dongles. If you want to compile it as a module,
16356 say M here and read Documentation/modules.txt. The ACTiSYS dongles
16357 attaches to the normal 9-pin serial port connector, and can
16358 currently only be used by IrTTY. To activate support for ACTiSYS
16359 dongles you will have to start irattach like this:
16360 "irattach -d actisys" or "irattach -d actisys+".
16362 Tekram IrMate 210B dongle
16363 CONFIG_TEKRAM_DONGLE
16364 Say Y here if you want to build support for the Tekram IrMate 210B
16365 dongle. If you want to compile it as a module, say M here
16366 and read Documentation/modules.txt. The Tekram dongle attaches to
16367 the normal 9-pin serial port connector, and can currently only be
16368 used by IrTTY. To activate support for Tekram dongles you will have
16369 to start irattach like this: "irattach -d tekram".
16371 Greenwich GIrBIL dongle
16372 CONFIG_GIRBIL_DONGLE
16373 Say Y here if you want to build support for the Greenwich GIrBIL
16374 dongle. If you want to compile it as a module, say M here and read
16375 Documentation/modules.txt. The Greenwich dongle attaches to the
16376 normal 9-pin serial port connector, and can currently only be used
16377 by IrTTY. To activate support for Greenwich dongles you will have to
16378 insert "irattach -d girbil" in the /etc/irda/drivers script.
16380 Parallax Litelink dongle
16381 CONFIG_LITELINK_DONGLE
16382 Say Y here if you want to build support for the Parallax Litelink
16383 dongle. If you want to compile it as a module, say M here and read
16384 Documentation/modules.txt. The Parallax dongle attaches to the
16385 normal 9-pin serial port connector, and can currently only be used
16386 by IrTTY. To activate support for Parallax dongles you will have to
16387 start irattach like this "irattach -d litelink".
16390 CONFIG_OLD_BELKIN_DONGLE
16391 Say Y here if you want to build support for the Adaptec Airport 1000
16392 and 2000 dongles. If you want to compile it as a module, say M here
16393 and read Documentation/modules.txt. The module will be called
16394 old_belkin.o. Some information is contained in the comments at the
16395 top of drivers/net/irda/old_belkin.c.
16397 VME (Motorola and BVM) support
16399 Say Y here if you want to build a kernel for a 680x0 based VME
16400 board. Boards currently supported include Motorola boards MVME162,
16401 MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
16402 boards from BVM Ltd are also supported.
16404 MVME162, 166 and 167 support
16406 Say Y to include support for Motorola VME boards. This will build a
16407 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
16408 MVME177 boards. If you select this option you will have to select
16409 the appropriate drivers for SCSI, Ethernet and serial ports later
16412 BVME4000 and BVME6000 support
16414 Say Y to include support for VME boards from BVM Ltd. This will
16415 build a kernel which can run on BVME4000 and BVME6000 boards. If
16416 you select this option you will have to select the appropriate
16417 drivers for SCSI, Ethernet and serial ports later on.
16419 Use write-through caching for 68060 supervisor accesses
16420 CONFIG_060_WRITETHROUGH
16421 The 68060 generally uses copyback caching of recently accessed data.
16422 Copyback caching means that memory writes will be held in an on-chip
16423 cache and only written back to memory some time later. Saying Y
16424 here will force supervisor (kernel) accesses to use writethrough
16425 caching. Writethrough caching means that data is written to memory
16426 straight away, so that cache and memory data always agree.
16427 Writethrough caching is less efficient, but is needed for some
16428 drivers on 68060 based systems where the 68060 bus snooping signal
16429 is hardwired on. The 53c710 SCSI driver is known to suffer from
16432 NCR53C710 SCSI driver for MVME16x
16433 CONFIG_MVME16x_SCSI
16434 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
16435 SCSI controller chip. Almost everyone using one of these boards
16436 will want to say Y to this question.
16438 NCR53C710 SCSI driver for BVME6000
16439 CONFIG_BVME6000_SCSI
16440 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
16441 SCSI controller chip. Almost everyone using one of these boards
16442 will want to say Y to this question.
16444 MVME16x Ethernet support
16446 This is the driver for the Ethernet interface on the Motorola
16447 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
16448 driver for this chip in your kernel. If you want to compile it as
16449 a module, say M here and read Documentation/modules.txt.
16451 BVME6000 Ethernet support
16452 CONFIG_BVME6000_NET
16453 This is the driver for the Ethernet interface on BVME4000 and
16454 BVME6000 VME boards. Say Y here to include the driver for this chip
16455 in your kernel. If you want to compile it as a module, say M here
16456 and read Documentation/modules.txt.
16458 CD2401 support for MVME166/7 serial ports
16460 This is the driver for the serial ports on the Motorola MVME166,
16461 167, and 172 boards. Everyone using one of these boards should say
16464 SCC support for MVME162 serial ports
16466 This is the driver for the serial ports on the Motorola MVME162 and
16467 172 boards. Everyone using one of these boards should say Y here.
16469 SCC support for BVME6000 serial ports
16470 CONFIG_BVME6000_SCC
16471 This is the driver for the serial ports on the BVME4000 and BVME6000
16472 boards from BVM Ltd. Everyone using one of these boards should say
16475 7-Segment Display support
16477 This is the driver for the 7-segment display and LED present on
16478 Sun Microsystems CompactPCI models CP1400 and CP1500.
16480 This driver is also available as a module ( = code which can be
16481 inserted in and removed from the running kernel whenever you want).
16482 The module will be called display7seg.o. If you want to compile it
16483 as a module, say M here and read Documentation/modules.txt.
16485 If you do not have a CompactPCI model CP1400 or CP1500, or
16486 another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
16487 you should say N to this option.
16490 # A couple of things I keep forgetting:
16491 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
16492 # Intel, IRQ, ISDN, Linux, MSDOS, NetWare, NetWinder,
16493 # NFS, PCI, SCSI, SPARC
16494 # two words: file system, hard drive, hard disk, home page,
16495 # user space, web site
16496 # other: it's safe to save; daemon; use --, not - or ---;
16497 # use KB for 1024 bytes, not kB or K.
16500 # This is used by Emacs' spell checker ispell.el:
16502 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
16503 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
16504 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
16505 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
16506 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
16507 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
16508 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
16509 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
16510 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
16511 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
16512 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
16513 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
16514 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
16515 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
16516 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
16517 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
16518 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
16519 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
16520 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
16521 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
16522 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
16523 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
16524 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
16525 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
16526 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
16527 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
16528 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
16529 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
16530 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
16531 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
16532 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
16533 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
16534 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
16535 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
16536 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
16537 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
16538 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
16539 # LocalWords: carleton DECstation SUNFD JENSEN Noname XXXM SLiRP LILO's amifb
16540 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
16541 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
16542 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
16543 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
16544 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
16545 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
16546 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
16547 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
16548 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
16549 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
16550 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
16551 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
16552 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
16553 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
16554 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
16555 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
16556 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
16557 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles XXXX LVM lvm
16559 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
16560 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
16561 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
16562 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
16563 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
16564 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
16565 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
16566 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
16567 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
16568 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
16569 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
16570 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
16571 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
16572 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
16573 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
16574 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
16575 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
16576 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
16577 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
16578 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
16579 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
16580 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
16581 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
16582 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
16583 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
16584 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
16585 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
16586 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
16587 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
16588 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
16589 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
16590 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
16591 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
16592 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
16593 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
16594 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
16595 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
16596 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
16597 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
16598 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
16599 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
16600 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
16601 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
16602 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
16603 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
16604 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
16605 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
16606 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
16607 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
16608 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
16609 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
16610 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
16611 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
16612 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
16613 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
16614 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
16615 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
16616 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
16617 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
16618 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
16619 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
16620 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
16621 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
16622 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
16623 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
16624 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
16625 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
16626 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
16627 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
16628 # LocalWords: adm Nodename hostname uname Kernelname bootp nmi DI OV StegFS
16629 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
16630 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
16631 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
16632 # LocalWords: Sitor Amtor Pactor GTOR hayes TX TMOUT JFdocs BIGMEM DAC IRQ's
16633 # LocalWords: IDEPCI IDEDMA PDC pdc TRM trm raidtools luthien nuclecu BAGET VR
16634 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
16635 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
16636 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
16637 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
16638 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
16639 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
16640 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
16641 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
16642 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
16643 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
16644 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
16645 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
16646 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
16647 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
16648 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
16649 # LocalWords: charset Inuit Greenlandic Sami Lappish koi Alexey Kuznetsov's sa
16650 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
16651 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
16652 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
16653 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
16654 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
16655 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
16656 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
16657 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
16658 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
16659 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
16660 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
16661 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
16662 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
16663 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
16664 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
16665 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
16666 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
16667 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
16668 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
16669 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
16670 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
16671 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
16672 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
16673 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
16674 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
16675 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
16676 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
16677 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
16678 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
16679 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SNA PAE
16680 # LocalWords: SysKonnect tms sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
16681 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
16682 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
16683 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
16684 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
16685 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
16686 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
16687 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
16688 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
16689 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
16690 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
16691 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
16692 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
16693 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
16694 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
16695 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
16696 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
16697 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
16698 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
16699 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
16700 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
16701 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
16702 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
16703 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
16704 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
16705 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
16706 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
16707 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
16708 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
16709 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
16710 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
16711 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
16712 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
16713 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
16714 # LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
16715 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
16716 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
16717 # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
16718 # LocalWords: IrLPT UIRCC Tecra Strebel jstrebel suse Eichwalder ke INI INIA
16719 # LocalWords: FCP qlogicfc sym isapnp DTLK DoubleTalk rcsys dtlk DMAP SGIVW ar
16720 # LocalWords: dmabuf EcoRadio MUTEFREQ GIrBIL girbil tepkom vol mha diplom PQS
16721 # LocalWords: bmac Microgate SyncLink synclink hdlc excl ioaddr Tane tanep TCQ
16722 # LocalWords: PDS SMALLDOS charsets bigfoot kernelfr mcs cls fw rsvp SKnet sk
16723 # LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd
16724 # LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu
16725 # LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable
16726 # LocalWords: FPEmulator ds vmlinux initialisation discardable pgtable PGT mdw
16727 # LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect
16728 # LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY
16729 # LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC
16730 # LocalWords: mainboard's Digital's alim FastTrak aec PIIXn piix Gayle Eyetech
16731 # LocalWords: Catweasel IDEDOUBLER Powerbook Centris ICSIDE RapIDE OSM HDM IOP
16732 # LocalWords: HDM's OSM's lan FibreChannel ECP autoprobe itg lbl ipmasq cjb IC
16733 # LocalWords: bieringer Caulfield's dreamtime decnet SIOCFIGCONF SIOCGIFCONF
16734 # LocalWords: rtnetlink Endnode Aironet Arlan Telxon ylenurme arlan ACB aeschi
16735 # LocalWords: Sealevel sealevel Cyclom br wanconfig tarball conectiva cycsyn
16736 # LocalWords: devel bazar cyclomx NetGear GA IBMOL Lanstreamer uhci eu efs CYZ
16737 # LocalWords: olympic linuxtr usbcore acm EZUSB downloader EFS XFS INTR op IIC
16738 # LocalWords: heine soundcore JavaStations JavaStation GemTeks TerraTec TODO
16739 # LocalWords: ActiveRadio Standalone terratec Rolf Offermanns rolf offermanns
16740 # LocalWords: Zoran ZR Buz LML CPQ DA cpqarray PPDEV deviceid vlp ppdev atyfb
16741 # LocalWords: AcceleRAID eXtremeRAID NETFILTER Netfilter masqueraded netfilter
16742 # LocalWords: kernelnotes Cardbus PCMCIA's CardBus clgenfb Permedia YAM MMAP
16743 # LocalWords: mmapped ATM atm PVCs SVCs InARP ATMARP neighbour neighbours MPOA
16744 # LocalWords: VCs ENI FPGA Tonga MMF MF UTP printks ZeitNet ZN ZATM uPD SAR PN
16745 # LocalWords: approx NICStAR NICs ForeRunnerLE Madge Collage ATMizer Dxxxx VCI
16746 # LocalWords: ServeRAID IPS ips ipslinux gzip BSDCOMP LZW RAYCS Interphase app
16747 # LocalWords: Tachyon IPHASE Surfboard NextLevel SURFboard jacksonville Tigon
16748 # LocalWords: fventuri adelphia siglercm linuxpower AceNICs Starfire starfire
16749 # LocalWords: ISOC CPiA cpia uss ACPI UDF DirectCD udf CDRW's OSF Manx acpi DM
16750 # LocalWords: Unixware cymru Computone IntelliPort Intelliport computone SI sx
16751 # LocalWords: adbmouse DRI DRM dlabs GMX PLCs Applicom fieldbus applicom int
16752 # LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU
16753 # LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator SBNI tw
16754 # LocalWords: LOGIBUSMOUSE Granch granch sbni Raylink NOHIGHMEM Athlon SIM sim
16755 # LocalWords: hpl Tourrilhes DuraLAN starfile Davicom davicom dmfe auk tms tr
16756 # LocalWords: TokenExpress Belkin Peracom eTek DVDs infradead Cxxx Adlib AV ZX
16757 # LocalWords: NeoMagic CPi CPt Celeron decapsulation Undeletion BFS bfs nVidia
16758 # LocalWords: OnStream Irongate Riva phonedev QuickNet LineJack PhoneJack IXJ
16759 # LocalWords: Quicknet PhoneJACK LineJACK ixj pnpdump Quicknet's Joandi SSID
16760 # LocalWords: aironet quickconfig adhoc btw bap NONCS cardservices Xircom lin
16761 # LocalWords: Netwave AirSurfer netwave HomePNA failover MVP iMacs ALi aktual
16762 # LocalWords: Aladin HIDBP usbkbd KEYBDEV MOUSEDEV JOYDEV EVDEV UAB WhiteHEAT
16763 # LocalWords: Handspring ov DABUSB URB URB's dabusb CRAMFS NFSv ELV IOAPIC WIP
16764 # LocalWords: NLMv SMBus ALGOBIT algo PHILIPSPAR philips elv Velleman velleman
16765 # LocalWords: ALGOPCF Elektor elektor CHARDEV dfx TDFX tdfx Extensa dof gravis
16766 # LocalWords: assasin logitech Overdrive thrustmaster DWave Aureal magellan db
16767 # LocalWords: SpaceTec SpaceOrb SpaceBall spaceorb FLX spaceball turbografx zr
16768 # LocalWords: amiga ESS's WaveWatcher Maxi belkin RW's ata glx GART MPV Baget
16769 # LocalWords: OpenGL Xserver agpgart HOTPLUG CyberPro Integraphics Netwinder
16770 # LocalWords: aty FONTWIDTH eni zatm nicstar ForeRunner OC DECstations DEC's
16771 # LocalWords: PHYsical SUNI reinsertion ChipSAR KVC PHY ClassID iphase iadbg
16772 # LocalWords: DEVS FireWire PCILynx pcilynx LOCALRAM miro's DV RAWIO GRED Mk
16773 # LocalWords: Diffserv DSMARK Ingress Qdisc TCINDEX TMSPCI tmspci Ringode JE
16774 # LocalWords: MADGEMC madgemc TokenRing SMCTR TokenCard smctr Wacom Graphire
16775 # LocalWords: WMFORCE mousedev ConnectTech HandSpring Xirlink IBMCAM ibmcam SN
16776 # LocalWords: DEVICEFS yyy Cymraeg Dwave SIMM JSFLASH JavaStation's multilink
16777 # LocalWords: nsc ircc DDB Vrc CMN TB PROMs Vino rivafb DDC Matroxes MGA TVO
16778 # LocalWords: MAVEN fbdev crtc maven matroxset NTSC PCA SBA AAL SKFP DAS SAS
16779 # LocalWords: skfp Intuos ADMtek's pegasus PLUSB plusb pointopoint mp rio Xeon
16780 # LocalWords: DEVFS devfs dd bs EDSS german TELESPCI FRITZPCI HFC HFCS BDS HST
16781 # LocalWords: ISURF ISAR Saphir HSTSAPHIR Telekom BKM Scitel Quadro SCT Gazel
16782 # LocalWords: SP PRI Hypercope HYSDN Hypercope's hysdn IbssJoinNetTimeout FTDI
16783 # LocalWords: ARCNet Keyspan PDA ADMtek sgalaxy sgbase opl mpuio mpuirq sbio
16784 # LocalWords: sbirq sbdma gus uart mssio mssirq mssdma sscape maui mouirq iph
16785 # LocalWords: CHDLC UPS's usbmouse wacom wmforce keybdev joydev fibre Trunking
16786 # LocalWords: Etherchannel IOC Moxa Intellio moxa SmartIO mxser Mixcom EFI ir
16787 # LocalWords: MIXCOMWD mixcomwd SENDCOMPLETE GMAC iBook gmac OAKNET oaknet PCG
16788 # LocalWords: diffserv irlan irtty toshoboe IrCC Lifebook idex AUTODMA FIP Cxx
16789 # LocalWords: Yenta Databook TCIC FMVJ fmvj NMCLAN LiveWire nmclan XIRC xirc
16790 # LocalWords: loadkeys setfont shm SuperIO soc SOCAL socal FCAL fc fcal COMX
16791 # LocalWords: MultiGate ITConsult comx CMX HiCOMX downloadable hw LoCOMX PROTO
16792 # LocalWords: locomx MixCOM mixcom proto MyriCOM MYRI Sbus myri sbus IBMLS hme
16793 # LocalWords: lanstreamer baseT HAPPYMEAL qfe sunhme SUNLANCE sunlance BigMAC
16794 # LocalWords: SUNBMAC sunbmac QuadEthernet SUNQE qe FastEthernet sunqe DSB PTI
16795 # LocalWords: DSBR dsbr procinfo QLOGICPTI qpti ptisp QLGC qlogicpti se LBA NF
16796 # LocalWords: OPENPROMFS OpenPROM openpromfs OBP OpenBoot flashable Multiboard
16797 # LocalWords: SPARCAUDIO SparcClassic Ultras DBRI Sparcbook sparcaudio SUNBPP
16798 # LocalWords: UltraDMA WDC CRC CONNTRACK IPTABLES iptables nfmark interface's
16799 # LocalWords: tdfxfb TNTx HGA hgafb VERBOSEDEBUG SunTrunking SunSoft XIRTULIP
16800 # LocalWords: ethercards PNIC Macronix MXIC ASIX xircom Mustek MDC gphoto mdc
16801 # LocalWords: CramFs Cramfs uid cramfs AVM's kernelcapi PCIV cdrdao Cdparanoia
16802 # LocalWords: DMX Domex dmx wellington ftdi sio Accton Billington Corega FEter
16803 # LocalWords: MELCO LUA PNA Linksys SNC chkdsk AWACS Webcam RAMFS Ramfs ramfs
16804 # LocalWords: ramfiles MAKEDEV pty WDTPCI APA apa