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 This driver provides support for the built-in IDE controller on most
1092 of the recent Apple Power Macintoshes and PowerBooks.
1095 PowerMac IDE DMA support
1096 CONFIG_BLK_DEV_IDEDMA_PMAC
1097 This option allows the driver for the built-in IDE controller on
1098 Power Macintoshes and PowerBooks to use DMA (direct memory access)
1099 to transfer data to and from memory. Saying Y is safe and improves
1103 CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO
1104 This option allows the driver for the built-in IDE controller on
1105 Power Macintoshes and PowerBooks to use DMA automatically, without
1106 it having to be explicitly enabled. This option is provided because
1107 of concerns about a couple of cases where using DMA on buggy PC
1108 hardware may have caused damage. Saying Y should be safe on all
1111 Macintosh Quadra/Powerbook IDE interface support
1112 CONFIG_BLK_DEV_MAC_IDE
1113 This is the IDE driver for the builtin IDE interface on some m68k
1114 Macintosh models. It supports both the `Quadra style' (used in
1115 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
1116 (used in the Powerbook 150 and 190 models) IDE interface.
1118 Say Y if you have such an Macintosh model and want to use IDE
1119 devices (hard disks, CD-ROM drives, etc.) that are connected to the
1120 builtin IDE interface.
1122 ICS IDE interface support
1123 CONFIG_BLK_DEV_IDE_ICSIDE
1124 On Acorn systems, say Y here if you wish to use the ICS IDE
1125 interface card. This is not required for ICS partition support.
1126 If you are unsure, say N to this.
1129 CONFIG_BLK_DEV_IDEDMA_ICS
1130 Say Y here if you want to add DMA (Direct Memory Access) support to
1133 Use ICS DMA by default
1134 CONFIG_IDEDMA_ICS_AUTO
1135 Prior to kernel version 2.1.112, Linux used to automatically use
1136 DMA for IDE drives and chipsets which support it. Due to concerns
1137 about a couple of cases where buggy hardware may have caused damage,
1138 the default is now to NOT use DMA automatically. To revert to the
1139 previous behaviour, say Y to this question.
1141 If you suspect your hardware is at all flakey, say N here.
1142 Do NOT email the IDE kernel people regarding this issue!
1144 XT hard disk support
1146 Very old 8 bit hard disk controllers used in the IBM XT computer
1147 will be supported if you say Y here.
1149 If you want to compile the driver as a module ( = code which can be
1150 inserted in and removed from the running kernel whenever you want),
1151 say M here and read Documentation/modules.txt. The module will be
1154 It's pretty unlikely that you have one of these: say N.
1156 PS/2 ESDI hard disk support
1158 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
1161 If you want to compile the driver as a module ( = code which can be
1162 inserted in and removed from the running kernel whenever you want),
1163 say M here and read Documentation/modules.txt. The module will be
1166 Mylex DAC960/DAC1100 PCI RAID Controller support
1167 CONFIG_BLK_DEV_DAC960
1168 This driver adds support for the Mylex DAC960, AcceleRAID, and
1169 eXtremeRAID PCI RAID controllers. See the file
1170 Documentation/README.DAC960 for further information about this
1173 If you want to compile the driver as a module ( = code which can be
1174 inserted in and removed from the running kernel whenever you want),
1175 say M here and read Documentation/modules.txt. The module will be
1178 Parallel port IDE device support
1180 There are many external CD-ROM and disk devices that connect through
1181 your computer's parallel port. Most of them are actually IDE devices
1182 using a parallel port IDE adapter. This option enables the PARIDE
1183 subsystem which contains drivers for many of these external drives.
1184 Read Documentation/paride.txt for more information.
1186 If you have said Y to the "Parallel-port support" configuration
1187 option, you may share a single port between your printer and other
1188 parallel port devices. Answer Y to build PARIDE support into your
1189 kernel, or M if you would like to build it as a loadable module. If
1190 your parallel port support is in a loadable module, you must build
1191 PARIDE as a module. If you built PARIDE support into your kernel,
1192 you may still build the individual protocol modules and high-level
1193 drivers as loadable modules. If you build this support as a module,
1194 it will be called paride.o.
1196 To use the PARIDE support, you must say Y or M here and also to at
1197 least one high-level driver (e.g. "Parallel port IDE disks",
1198 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
1199 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
1200 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
1203 Parallel port IDE disks
1205 This option enables the high-level driver for IDE-type disk devices
1206 connected through a parallel port. If you chose to build PARIDE
1207 support into your kernel, you may answer Y here to build in the
1208 parallel port IDE driver, otherwise you should answer M to build
1209 it as a loadable module. The module will be called pd.o. You
1210 must also have at least one parallel port protocol driver in your
1211 system. Among the devices supported by this driver are the SyQuest
1212 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
1213 hard drives from MicroSolutions.
1215 Parallel port ATAPI CD-ROMs
1217 This option enables the high-level driver for ATAPI CD-ROM devices
1218 connected through a parallel port. If you chose to build PARIDE
1219 support into your kernel, you may answer Y here to build in the
1220 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
1221 build it as a loadable module. The module will be called pcd.o. You
1222 must also have at least one parallel port protocol driver in your
1223 system. Among the devices supported by this driver are the
1224 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
1225 you have such a CD-ROM drive, you should also say Y or M to "ISO
1226 9660 CDROM file system support" below, because that's the file
1227 system used on CDROMs.
1229 Parallel port ATAPI disks
1231 This option enables the high-level driver for ATAPI disk devices
1232 connected through a parallel port. If you chose to build PARIDE
1233 support into your kernel, you may answer Y here to build in the
1234 parallel port ATAPI disk driver, otherwise you should answer M
1235 to build it as a loadable module. The module will be called pf.o.
1236 You must also have at least one parallel port protocol driver in
1237 your system. Among the devices supported by this driver are the
1238 MicroSolutions backpack PD/CD drive and the Imation Superdisk
1241 Parallel port ATAPI tapes
1243 This option enables the high-level driver for ATAPI tape devices
1244 connected through a parallel port. If you chose to build PARIDE
1245 support into your kernel, you may answer Y here to build in the
1246 parallel port ATAPI disk driver, otherwise you should answer M
1247 to build it as a loadable module. The module will be called pt.o.
1248 You must also have at least one parallel port protocol driver in
1249 your system. Among the devices supported by this driver is the
1250 parallel port version of the HP 5GB drive.
1252 Parallel port generic ATAPI devices
1254 This option enables a special high-level driver for generic ATAPI
1255 devices connected through a parallel port. The driver allows user
1256 programs, such as cdrecord, to send ATAPI commands directly to a
1259 If you chose to build PARIDE support into your kernel, you may
1260 answer Y here to build in the parallel port generic ATAPI driver,
1261 otherwise you should answer M to build it as a loadable module. The
1262 module will be called pg.o.
1264 You must also have at least one parallel port protocol driver in
1267 This driver implements an API loosely related to the generic SCSI
1268 driver. See include/linux/pg.h for details.
1270 You can obtain the most recent version of cdrecord from
1271 ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
1272 later fully support this driver.
1274 ATEN EH-100 protocol
1276 This option enables support for the ATEN EH-100 parallel port IDE
1277 protocol. This protocol is used in some inexpensive low performance
1278 parallel port kits made in Hong Kong. If you chose to build PARIDE
1279 support into your kernel, you may answer Y here to build in the
1280 protocol driver, otherwise you should answer M to build it as a
1281 loadable module. The module will be called aten.o. You must also
1282 have a high-level driver for the type of device that you want to
1285 MicroSolutions backpack protocol
1287 This option enables support for the MicroSolutions backpack parallel
1288 port IDE protocol. If you chose to build PARIDE support into your
1289 kernel, you may answer Y here to build in the protocol driver,
1290 otherwise you should answer M to build it as a loadable module. The
1291 module will be called bpck.o. You must also have a high-level driver
1292 for the type of device that you want to support.
1294 DataStor Commuter protocol
1296 This option enables support for the Commuter parallel port IDE
1297 protocol from DataStor. If you chose to build PARIDE support
1298 into your kernel, you may answer Y here to build in the protocol
1299 driver, otherwise you should answer M to build it as a loadable
1300 module. The module will be called comm.o. You must also have
1301 a high-level driver for the type of device that you want to support.
1303 DataStor EP-2000 protocol
1305 This option enables support for the EP-2000 parallel port IDE
1306 protocol from DataStor. If you chose to build PARIDE support
1307 into your kernel, you may answer Y here to build in the protocol
1308 driver, otherwise you should answer M to build it as a loadable
1309 module. The module will be called dstr.o. You must also have
1310 a high-level driver for the type of device that you want to support.
1312 Shuttle EPAT/EPEZ protocol
1314 This option enables support for the EPAT parallel port IDE protocol.
1315 EPAT is a parallel port IDE adapter manufactured by Shuttle
1316 Technology and widely used in devices from major vendors such as
1317 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
1318 PARIDE support into your kernel, you may answer Y here to build in
1319 the protocol driver, otherwise you should answer M to build it as a
1320 loadable module. The module will be called epat.o. You must also
1321 have a high-level driver for the type of device that you want to
1324 Shuttle EPIA protocol
1326 This option enables support for the (obsolete) EPIA parallel port
1327 IDE protocol from Shuttle Technology. This adapter can still be
1328 found in some no-name kits. If you chose to build PARIDE support
1329 into your kernel, you may answer Y here to build in the protocol
1330 driver, otherwise you should answer M to build it as a loadable
1331 module. The module will be called epia.o. You must also have a
1332 high-level driver for the type of device that you want to support.
1334 FIT TD-2000 protocol
1336 This option enables support for the TD-2000 parallel port IDE
1337 protocol from Fidelity International Technology. This is a simple
1338 (low speed) adapter that is used in some portable hard drives. If
1339 you chose to build PARIDE support into your kernel, you may answer Y
1340 here to build in the protocol driver, otherwise you should answer M
1341 to build it as a loadable module. The module will be called ktti.o.
1342 You must also have a high-level driver for the type of device that
1343 you want to support.
1345 FIT TD-3000 protocol
1347 This option enables support for the TD-3000 parallel port IDE
1348 protocol from Fidelity International Technology. This protocol is
1349 used in newer models of their portable disk, CD-ROM and PD/CD
1350 devices. If you chose to build PARIDE support into your kernel, you
1351 may answer Y here to build in the protocol driver, otherwise you
1352 should answer M to build it as a loadable module. The module will be
1353 called fit3.o. You must also have a high-level driver for the type
1354 of device that you want to support.
1356 Freecom IQ ASIC-2 protocol
1358 This option enables support for version 2 of the Freecom IQ parallel
1359 port IDE adapter. This adapter is used by the Maxell Superdisk
1360 drive. If you chose to build PARIDE support into your kernel, you
1361 may answer Y here to build in the protocol driver, otherwise you
1362 should answer M to build it as a loadable module. The module will be
1363 called friq.o. You must also have a high-level driver for the type
1364 of device that you want to support.
1366 FreeCom power protocol
1368 This option enables support for the Freecom power parallel port IDE
1369 protocol. If you chose to build PARIDE support into your kernel, you
1370 may answer Y here to build in the protocol driver, otherwise you
1371 should answer M to build it as a loadable module. The module will be
1372 called frpw.o. You must also have a high-level driver for the type
1373 of device that you want to support.
1375 KingByte KBIC-951A/971A protocols
1377 This option enables support for the KBIC-951A and KBIC-971A parallel
1378 port IDE protocols from KingByte Information Corp. KingByte's
1379 adapters appear in many no-name portable disk and CD-ROM products,
1380 especially in Europe. If you chose to build PARIDE support into your
1381 kernel, you may answer Y here to build in the protocol driver,
1382 otherwise you should answer M to build it as a loadable module. The
1383 module will be called kbic.o. You must also have a high-level driver
1384 for the type of device that you want to support.
1388 This option enables support for the "PHd" parallel port IDE protocol
1389 from KT Technology. This is a simple (low speed) adapter that is
1390 used in some 2.5" portable hard drives. If you chose to build PARIDE
1391 support into your kernel, you may answer Y here to build in the
1392 protocol driver, otherwise you should answer M to build it as a
1393 loadable module. The module will be called ktti.o. You must also
1394 have a high-level driver for the type of device that you want to
1397 OnSpec 90c20 protocol
1399 This option enables support for the (obsolete) 90c20 parallel port
1400 IDE protocol from OnSpec (often marketed under the ValuStore brand
1401 name). If you chose to build PARIDE support into your kernel, you
1402 may answer Y here to build in the protocol driver, otherwise you
1403 should answer M to build it as a loadable module. The module will
1404 be called on20.o. You must also have a high-level driver for the
1405 type of device that you want to support.
1407 OnSpec 90c26 protocol
1409 This option enables support for the 90c26 parallel port IDE protocol
1410 from OnSpec Electronics (often marketed under the ValuStore brand
1411 name). If you chose to build PARIDE support into your kernel, you
1412 may answer Y here to build in the protocol driver, otherwise you
1413 should answer M to build it as a loadable module. The module will be
1414 called on26.o. You must also have a high-level driver for the type
1415 of device that you want to support.
1417 Logical Volume Manager (LVM) support
1419 This driver lets you combine several hard disks, hard disk
1420 partitions, multiple devices or even loop devices (for evaluation
1421 purposes) into a volume group. Imagine a volume group as a kind of
1422 virtual disk. Logical volumes, which can be thought of as virtual
1423 partitions, can be created in the volume group. You can resize
1424 volume groups and logical volumes after creation time, corresponding
1425 to new capacity needs. Logical volumes are accessed as block
1426 devices named /dev/VolumeGroupName/LogicalVolumeName.
1428 For details see Documentation/LVM-HOWTO. You will need supporting
1429 user space software; location is in Documentation/Changes.
1431 If you want to compile this support as a module ( = code which can
1432 be inserted in and removed from the running kernel whenever you
1433 want), say M here and read Documentation/modules.txt. The module
1434 will be called lvm-mod.o.
1436 Logical Volume Manager /proc file system information
1438 If you say Y here, you are able to access overall Logical Volume
1439 Manager, Volume Group, Logical and Physical Volume information in
1442 To use this option, you have to check, that the "/proc file system
1443 support" (CONFIG_PROC_FS) is enabled too.
1445 Multiple devices driver support
1447 This driver lets you combine several hard disk partitions into one
1448 logical block device. This can be used to simply append one
1449 partition to another one or to combine several redundant hard disks
1450 into a RAID1/4/5 device so as to provide protection against hard
1451 disk failures. This is called "Software RAID" since the combining of
1452 the partitions is done by the kernel. "Hardware RAID" means that the
1453 combining is done by a dedicated controller; if you have such a
1454 controller, you do not need to say Y here.
1456 More information about Software RAID on Linux is contained in the
1457 Software-RAID mini-HOWTO, available from
1458 http://www.linuxdoc.org/docs.html#howto . There you will also
1459 learn where to get the supporting user space utilities raidtools.
1463 Linear (append) mode
1465 If you say Y here, then your multiple devices driver will be able to
1466 use the so-called linear mode, i.e. it will combine the hard disk
1467 partitions by simply appending one to the other.
1469 If you want to compile this as a module ( = code which can be
1470 inserted in and removed from the running kernel whenever you want),
1471 say M here and read Documentation/modules.txt. The module will be
1476 RAID-0 (striping) mode
1478 If you say Y here, then your multiple devices driver will be able to
1479 use the so-called raid0 mode, i.e. it will combine the hard disk
1480 partitions into one logical device in such a fashion as to fill them
1481 up evenly, one chunk here and one chunk there. This will increase
1482 the throughput rate if the partitions reside on distinct disks.
1484 Information about Software RAID on Linux is contained in the
1485 Software-RAID mini-HOWTO, available from
1486 http://www.linuxdoc.org/docs.html#howto . There you will also
1487 learn where to get the supporting user space utilities raidtools.
1489 If you want to compile this as a module ( = code which can be
1490 inserted in and removed from the running kernel whenever you want),
1491 say M here and read Documentation/modules.txt. The module will be
1496 RAID-1/RAID-5 code (DANGEROUS)
1497 CONFIG_RAID15_DANGEROUS
1498 This new RAID1/RAID5 code has been freshly merged, and has not seen
1499 enough testing yet. While there are no known bugs in it, it might
1500 destroy your filesystems, eat your data and start World War III.
1501 You have been warned.
1505 RAID-1 (mirroring) mode
1507 A RAID-1 set consists of several disk drives which are exact copies
1508 of each other. In the event of a mirror failure, the RAID driver
1509 will continue to use the operational mirrors in the set, providing
1510 an error free MD (multiple device) to the higher levels of the
1511 kernel. In a set with N drives, the available space is the capacity
1512 of a single drive, and the set protects against a failure of (N - 1)
1515 Information about Software RAID on Linux is contained in the
1516 Software-RAID mini-HOWTO, available from
1517 http://www.linuxdoc.org/docs.html#howto . There you will also
1518 learn where to get the supporting user space utilities raidtools.
1520 If you want to use such a RAID-1 set, say Y. This code is also
1521 available as a module called raid1.o ( = code which can be inserted
1522 in and removed from the running kernel whenever you want). If you
1523 want to compile it as a module, say M here and read
1524 Documentation/modules.txt.
1530 A RAID-5 set of N drives with a capacity of C MB per drive provides
1531 the capacity of C * (N - 1) MB, and protects against a failure
1532 of a single drive. For a given sector (row) number, (N - 1) drives
1533 contain data sectors, and one drive contains the parity protection.
1534 For a RAID-4 set, the parity blocks are present on a single drive,
1535 while a RAID-5 set distributes the parity across the drives in one
1536 of the available parity distribution methods.
1538 Information about Software RAID on Linux is contained in the
1539 Software-RAID mini-HOWTO, available from
1540 http://www.linuxdoc.org/docs.html#howto . There you will also
1541 learn where to get the supporting user space utilities raidtools.
1543 If you want to use such a RAID-4/RAID-5 set, say Y. This code is
1544 also available as a module called raid5.o ( = code which can be
1545 inserted in and removed from the running kernel whenever you want).
1546 If you want to compile it as a module, say M here and read
1547 Documentation/modules.txt.
1553 To boot with an initial raid volume (any type) you can select
1554 autodetect, or answer Y here and appropriate options to the kernel
1556 For lilo and loadlin options see the file Documentation/md.txt.
1558 RAID AutoDetect support
1559 CONFIG_AUTODETECT_RAID
1560 An alternative to "Raid Boot support" is autodetect support.
1561 With this selected, any partitons of type 0xFD will be considered for
1562 inclusion in a RAID array. Information in the RAID-superblock on
1563 the partition will determine how it is included.
1565 Support for Acer PICA 1 chipset
1567 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
1568 kernel that runs on these, say Y here. For details about Linux on
1569 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1570 http://oss.sgi.com/mips .
1572 Support for Algorithmics P4032 (EXPERIMENTAL)
1574 This is an evaluation board of the British company Algorithmics. The
1575 board uses the R4300 and a R5230 CPUs. For more information about
1576 this board see http://www.algor.co.uk .
1578 Support for BAGET MIPS series
1580 This enables support for the Baget, a Russian embedded system. For
1581 more details about the Baget see the Linux/MIPS FAQ on
1582 http://oss.sgi.com/mips .
1584 Support for Cobalt Microserver
1585 CONFIG_COBALT_MICRO_SERVER
1586 This enables support for the Cobalt Microserver. For more information
1587 see the Linux/MIPS FAQ on http://oss.sgi.com/mips .
1591 This adds support for the Cobalt Microserver 2800. A kernel with this
1592 option selected will only work on the 2800.
1594 Support for DECstations
1596 This enables support for DEC's MIPS based workstations. For details
1597 see the Linux/MIPS FAQ on http://oss.sgi.com/mips and the
1598 DECstation porting pages on http://decstation.unix-ag.org .
1600 If you have one of the following DECstation Models you definitely
1601 want to choose R4xx0 for the CPU Type:
1608 otherwise choose R3000.
1610 Support for NEC DDB Vrc-5074
1612 This enables support for the VR5000-based NEC DDB Vrc-5074
1615 Support for Mips Magnum 4000
1616 CONFIG_MIPS_MAGNUM_4000
1617 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1618 kernel that runs on these, say Y here. For details about Linux on
1619 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1620 http://oss.sgi.com/mips.
1622 Support for Olivetti M700
1623 CONFIG_OLIVETTI_M700
1624 This is a machine with a R4000 100 MHz CPU. To compile a Linux
1625 kernel that runs on these, say Y here. For details about Linux on
1626 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
1627 http://oss.sgi.com/mips.
1629 Support for SGI IP22
1631 This are the SGI Indy, Challenge S and Indigo2, as well as certain
1632 OEM variants like the Tandem CMN B006S. To compile a Linux kernel
1633 that runs on these, say Y here.
1635 Support for SGI IP27
1636 This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
1637 workstations. To compile a Linux kernel that runs on these, say Y
1641 CONFIG_SGI_SN0_N_MODE
1642 The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
1643 configured in either N-Modes which allows for more nodes or M-Mode
1644 which allows for more more memory. Your system is most probably
1645 running in M-Mode, so you should say N here.
1647 MIPS JAZZ onboard SONIC Ethernet support
1648 CONFIG_MIPS_JAZZ_SONIC
1649 This is the driver for the onboard card of of MIPS Magnum 4000,
1650 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
1652 MIPS JAZZ FAS216 SCSI support
1654 This is the driver for the onboard SCSI host adapter of MIPS Magnum
1655 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
1658 PCMCIA SCSI adapter support
1660 Say Y here if you intend to attach a PCMCIA or CardBus card to your
1661 computer which acts as a SCSI host adapter. These are credit card
1662 size devices often used with laptops.
1664 Note that the answer to this question won't directly affect the
1665 kernel: saying N will just cause this configure script to skip all
1666 the questions PCMCIA SCSI host adapters.
1668 Adaptec AHA152X PCMCIA support
1669 CONFIG_PCMCIA_AHA152X
1670 Say Y here if you intend to attach this type of PCMCIA SCSI host
1671 adapter to your computer.
1673 This driver is also available as a module called aha152x_cs.o ( =
1674 code which can be inserted in and removed from the running kernel
1675 whenever you want). If you want to compile it as a module, say M
1676 here and read Documentation/modules.txt.
1678 Qlogic PCMCIA support
1679 CONFIG_PCMCIA_QLOGIC
1680 Say Y here if you intend to attach this type of PCMCIA SCSI host
1681 adapter to your computer.
1683 This driver is also available as a module called qlogic_cs.o ( =
1684 code which can be inserted in and removed from the running kernel
1685 whenever you want). If you want to compile it as a module, say M
1686 here and read Documentation/modules.txt.
1688 Future Domain PCMCIA support
1689 CONFIG_PCMCIA_FDOMAIN
1690 Say Y here if you intend to attach this type of PCMCIA SCSI host
1691 adapter to your computer.
1693 This driver is also available as a module called fdomain_cs.o ( =
1694 code which can be inserted in and removed from the running kernel
1695 whenever you want). If you want to compile it as a module, say M
1696 here and read Documentation/modules.txt.
1698 Adaptec APA1480 CardBus support
1699 CONFIG_PCMCIA_APA1480
1700 Say Y here if you intend to attach this type of CardBus SCSI host
1701 adapter to your computer.
1703 This driver is also available as a module called apa1480_cb.o ( =
1704 code which can be inserted in and removed from the running kernel
1705 whenever you want). If you want to compile it as a module, say M
1706 here and read Documentation/modules.txt.
1710 Please make sure to pick the right CPU type. Linux/MIPS is not
1711 designed to be generic, i.e. Kernels compiled for R3000 CPUs will
1712 *not* work on R4000 Machines and vice versa.
1713 However, since most the supported Machines have an R4000 (or
1714 similar) CPU, R4xx0 might be a safe bet.
1715 If the resulting Kernel does not work try to recompile with R3000.
1717 Support for large 64-bit configurations
1718 CONFIG_MIPS_INSANE_LARGE
1719 MIPS R10000 does support a 44 bit / 16TB address space as opposed to
1720 previous 64-bit processors which only supported 40 bit / 1TB. If you
1721 need processes of more than 1TB virtual address space, say Y here.
1722 This will result in additional memory usage, so it is not
1723 recommended for normal users.
1725 Generate little endian code
1726 CONFIG_CPU_LITTLE_ENDIAN
1727 Some MIPS machines can be configured for either little or big endian
1728 byte order. These modes require different kernels. Say Y if your
1729 machine is little endian, N if it's a big endian machine.
1733 Unless you really know what you are doing, you should say Y here.
1734 The reason is that some programs need kernel networking support even
1735 when running on a stand-alone machine that isn't connected to any
1736 other computer. If you are upgrading from an older kernel, you
1737 should consider updating your networking tools too because changes
1738 in the kernel and the tools often go hand in hand. The tools are
1739 contained in the package net-tools, the location and version number
1740 of which are given in Documentation/Changes.
1742 For a general introduction to Linux networking, it is highly
1743 recommended to read the NET-3-HOWTO, available from
1744 http://www.linuxdoc.org/docs.html#howto .
1748 The Linux Socket Filter is derived from the Berkeley Packet Filter.
1749 If you say Y here, user-space programs can attach a filter to any
1750 socket and thereby tell the kernel that it should allow or disallow
1751 certain types of data to get through the socket. Linux Socket
1752 Filtering works on all socket types except TCP for now. See the text
1753 file Documentation/networking/filter.txt for more information.
1756 Network packet filtering
1758 Netfilter is a framework for filtering and mangling network packets
1759 that pass through your Linux box.
1761 The most common use of packet filtering is to run your Linux box as
1762 a firewall protecting a local network from the Internet. The type of
1763 firewall provided by this kernel support is called a "packet
1764 filter", which means that it can reject individual network packets
1765 based on type, source, destination etc. The other kind of firewall,
1766 a "proxy-based" one, is more secure but more intrusive and more
1767 bothersome to set up; it inspects the network traffic much more
1768 closely, modifies it and has knowledge about the higher level
1769 protocols, which a packet filter lacks. Moreover, proxy-based
1770 firewalls often require changes to the programs running on the local
1771 clients. Proxy-based firewalls don't need support by the kernel, but
1772 they are often combined with a packet filter, which only works if
1775 You should also say Y here if you intend to use your Linux box as
1776 the gateway to the Internet for a local network of machines without
1777 globally valid IP addresses. This is called "masquerading": if one
1778 of the computers on your local network wants to send something to
1779 the outside, your box can "masquerade" as that computer, i.e. it
1780 forwards the traffic to the intended outside destination, but
1781 modifies the packets to make it look like they came from the
1782 firewall box itself. It works both ways: if the outside host
1783 replies, the Linux box will silently forward the traffic to the
1784 correct local computer. This way, the computers on your local net
1785 are completely invisible to the outside world, even though they can
1786 reach the outside and can receive replies. It is even possible to
1787 run globally visible servers from within a masqueraded local network
1788 using a mechanism called portforwarding. Masquerading is also often
1789 called NAT (Network Address Translation).
1791 Another use of Netfilter is in transparent proxying: if a machine on
1792 the local network tries to connect to an outside host, your Linux
1793 box can transparently forward the traffic to a local server,
1794 typically a caching proxy server.
1796 Various modules exist for netfilter which replace the previous
1797 masquerading (ipmasqadm), packet filtering (ipchains), transparent
1798 proxying, and portforwarding mechanisms. Please see
1799 Documentation/Changes under "iptables" for the location of these
1802 Make sure to say N to "Fast switching" below if you intend to say Y
1803 here, as Fast switching currently bypasses netfilter.
1805 Chances are that you should say Y here if you compile a kernel which
1806 will run as a router and N for regular hosts. If unsure, say N.
1808 Network packet filtering debugging
1809 CONFIG_NETFILTER_DEBUG
1810 You can say Y here if you want to get additional messages useful in
1811 debugging the netfilter code.
1813 IP: connection tracking (required for masq/NAT)
1814 CONFIG_IP_NF_CONNTRACK
1815 Connection tracking keeps a record of what packets have passed
1816 through your machine, in order to figure out how they are related
1819 This is required to do Masquerading or other kinds of Network
1820 Address Translation (except for Fast NAT). It can also be used to
1821 enhance packet filtering (see `Connection state match support'
1824 If you want to compile it as a module, say M here and read
1825 Documentation/modules.txt. If unsure, say `N'.
1827 FTP protocol support
1829 Tracking FTP connections is problematic: special helpers are
1830 required for tracking them, and doing masquerading and other forms
1831 of Network Address Translation on them.
1833 If you want to compile it as a module, say M here and read
1834 Documentation/modules.txt. If unsure, say `Y'.
1836 IP: user space queueing via NETLINK (EXPERIMENTAL)
1838 Netfilter has the ability to queue packets to user space: the
1839 netlink device can be used to access them using this driver.
1841 If you want to compile it as a module, say M here and read
1842 Documentation/modules.txt. If unsure, say `N'.
1844 IP: ip tables support (required for filtering/masq/NAT)
1845 CONFIG_IP_NF_IPTABLES
1846 iptables is a general, extensible packet identification framework.
1847 The packet filtering and full NAT (masquerading, port forwarding,
1848 etc) subsystems now use this: say `Y' or `M' here if you want to use
1851 If you want to compile it as a module, say M here and read
1852 Documentation/modules.txt. If unsure, say `N'.
1855 CONFIG_IP_NF_MATCH_LIMIT
1856 limit matching allows you to control the rate at which a rule can be
1857 matched: mainly useful in combination with the LOG target ("LOG
1858 target support", below) and to avoid some Denial of Service attacks.
1860 If you want to compile it as a module, say M here and read
1861 Documentation/modules.txt. If unsure, say `N'.
1863 MAC address match support
1864 CONFIG_IP_NF_MATCH_MAC
1865 mac matching allows you to match packets based on the source
1866 ethernet address of the packet.
1868 If you want to compile it as a module, say M here and read
1869 Documentation/modules.txt. If unsure, say `N'.
1871 netfilter mark match support
1872 CONFIG_IP_NF_MATCH_MARK
1873 Netfilter mark matching allows you to match packets based on the
1874 `nfmark' value in the packet. This can be set by the MARK target
1877 If you want to compile it as a module, say M here and read
1878 Documentation/modules.txt. If unsure, say `N'.
1880 Multiple port match support
1881 CONFIG_IP_NF_MATCH_MULTIPORT
1882 Multiport matching allows you to match TCP or UDP packets based on
1883 a series of source or destination ports: normally a rule can only
1884 match a single range of ports.
1886 If you want to compile it as a module, say M here and read
1887 Documentation/modules.txt. If unsure, say `N'.
1890 CONFIG_IP_NF_MATCH_TOS
1891 TOS matching allows you to match packets based on the Type Of
1892 Service fields of the IP packet.
1894 If you want to compile it as a module, say M here and read
1895 Documentation/modules.txt. If unsure, say `N'.
1897 Connection state match support
1898 CONFIG_IP_NF_MATCH_STATE
1899 Connection state matching allows you to match packets based on their
1900 relationship to a tracked connection (ie. previous packets). This
1901 is a powerful tool for packet classification.
1903 If you want to compile it as a module, say M here and read
1904 Documentation/modules.txt. If unsure, say `N'.
1906 Unclean match support (EXPERIMENTAL)
1907 CONFIG_IP_NF_MATCH_UNCLEAN
1908 Unclean packet matching matches any strange or invalid packets, by
1909 looking at a series of fields in the IP, TCP, UDP and ICMP headers.
1911 If you want to compile it as a module, say M here and read
1912 Documentation/modules.txt. If unsure, say `N'.
1914 Owner match support (EXPERIMENTAL)
1915 CONFIG_IP_NF_MATCH_OWNER
1916 Packet owner matching allows you to match locally-generated packets
1917 based on who created them: the user, group, process or session.
1919 If you want to compile it as a module, say M here and read
1920 Documentation/modules.txt. If unsure, say `N'.
1924 Packet filtering defines a table `filter', which has a series of
1925 rules for simple packet filtering at local input, forwarding and
1926 local output. See the man page for iptables(8).
1928 If you want to compile it as a module, say M here and read
1929 Documentation/modules.txt. If unsure, say `N'.
1931 REJECT target support
1932 CONFIG_IP_NF_TARGET_REJECT
1933 The REJECT target allows a filtering rule to specify that an ICMP
1934 error should be issued in response to an incoming packet, rather
1935 than silently being dropped.
1937 If you want to compile it as a module, say M here and read
1938 Documentation/modules.txt. If unsure, say `N'.
1940 MIRROR target support (EXPERIMENTAL)
1941 CONFIG_IP_NF_TARGET_MIRROR
1942 The MIRROR target allows a filtering rule to specify that an
1943 incoming packet should be bounced back to the sender.
1945 If you want to compile it as a module, say M here and read
1946 Documentation/modules.txt. If unsure, say `N'.
1950 The Full NAT option allows masquerading, port forwarding and other
1951 forms of full Network Address Port Translation. It is controlled by
1952 the `nat' table in iptables: see the man page for iptables(8).
1954 If you want to compile it as a module, say M here and read
1955 Documentation/modules.txt. If unsure, say `N'.
1957 MASQUERADE target support
1958 CONFIG_IP_NF_TARGET_MASQUERADE
1959 Masquerading is a special case of NAT: all outgoing connections are
1960 changed to seem to come from a particular interface's address, and
1961 if the interface goes down, those connections are lost. This is
1962 only useful for dialup accounts with dynamic IP address (ie. your IP
1963 address will be different on next dialup).
1965 If you want to compile it as a module, say M here and read
1966 Documentation/modules.txt. If unsure, say `N'.
1968 REDIRECT target support
1969 CONFIG_IP_NF_TARGET_REDIRECT
1970 REDIRECT is a special case of NAT: all incoming connections are
1971 mapped onto the incoming interface's address, causing the packets to
1972 come to the local machine instead of passing through. This is
1973 useful for transparent proxies.
1975 If you want to compile it as a module, say M here and read
1976 Documentation/modules.txt. If unsure, say `N'.
1980 This option adds a `mangle' table to iptables: see the man page for
1981 iptables(8). This table is used for various packet alterations
1982 which can effect how the packet is routed.
1984 If you want to compile it as a module, say M here and read
1985 Documentation/modules.txt. If unsure, say `N'.
1988 CONFIG_IP_NF_TARGET_TOS
1989 This option adds a `TOS' target, which allows you to create rules in
1990 the `mangle' table which alter the Type Of Service field of an IP
1991 packet prior to routing.
1993 If you want to compile it as a module, say M here and read
1994 Documentation/modules.txt. If unsure, say `N'.
1997 CONFIG_IP_NF_TARGET_MARK
1998 This option adds a `MARK' target, which allows you to create rules
1999 in the `mangle' table which alter the netfilter mark (nfmark) field
2000 associated with the packet packet prior to routing. This can change
2001 the routing method (see `IP: use netfilter MARK value as routing
2002 key') and can also be used by other subsystems to change their
2005 If you want to compile it as a module, say M here and read
2006 Documentation/modules.txt. If unsure, say `N'.
2009 CONFIG_IP_NF_TARGET_LOG
2010 This option adds a `LOG' target, which allows you to create rules in
2011 any iptables table which records the packet header to the syslog.
2013 If you want to compile it as a module, say M here and read
2014 Documentation/modules.txt. If unsure, say `N'.
2016 ipchains (2.2-style) support
2017 CONFIG_IP_NF_COMPAT_IPCHAINS
2018 This option places ipchains (with masquerading and redirection
2019 support) back into the kernel, using the new netfilter
2020 infrastructure. It is not recommended for new installations (see
2021 `Packet filtering'). With this enabled, you should be able to use
2022 the ipchains tool exactly as in 2.2 kernels.
2024 If you want to compile it as a module, say M here and read
2025 Documentation/modules.txt. If unsure, say `N'.
2027 ipfwadm (2.0-style) support
2028 CONFIG_IP_NF_COMPAT_IPFWADM
2029 This option places ipfwadm (with masquerading and redirection
2030 support) back into the kernel, using the new netfilter
2031 infrastructure. It is not recommended for new installations (see
2032 `Packet filtering'). With this enabled, you should be able to use
2033 the ipfwadm tool exactly as in 2.0 kernels.
2035 If you want to compile it as a module, say M here and read
2036 Documentation/modules.txt. If unsure, say `N'.
2038 SYN flood protection
2040 Normal TCP/IP networking is open to an attack known as "SYN
2041 flooding". This denial-of-service attack prevents legitimate remote
2042 users from being able to connect to your computer during an ongoing
2043 attack and requires very little work from the attacker, who can
2044 operate from anywhere on the Internet.
2046 SYN cookies provide protection against this type of attack. If you
2047 say Y here, the TCP/IP stack will use a cryptographic challenge
2048 protocol known as "SYN cookies" to enable legitimate users to
2049 continue to connect, even when your machine is under attack. There
2050 is no need for the legitimate users to change their TCP/IP software;
2051 SYN cookies work transparently to them. For technical information
2052 about SYN cookies, check out
2053 ftp://koobera.math.uic.edu/syncookies.html .
2055 If you are SYN flooded, the source address reported by the kernel is
2056 likely to have been forged by the attacker; it is only reported as
2057 an aid in tracing the packets to their actual source and should not
2058 be taken as absolute truth.
2060 SYN cookies may prevent correct error reporting on clients when the
2061 server is really overloaded. If this happens frequently better turn
2064 If you say Y here, note that SYN cookies aren't enabled by default;
2065 you can enable them by saying Y to "/proc file system support" and
2066 "Sysctl support" below and executing the command
2068 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
2070 at boot time after the /proc file system has been mounted.
2075 CONFIG_ALPHA_GENERIC
2076 This is the system type of your hardware. A "generic" kernel will
2077 run on any supported Alpha system. However, if you configure a
2078 kernel for your specific system, it will be faster and smaller.
2080 To find out what type of Alpha system you have, you may want to
2081 check out the Linux/Alpha FAQ, accessible on the WWW from
2082 http://www.alphalinux.org . In summary:
2084 Alcor/Alpha-XLT AS 600
2085 Alpha-XL XL-233, XL-266
2086 AlphaBook1 Alpha laptop
2087 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
2088 Cabriolet AlphaPC64, AlphaPCI64
2090 EB164 EB164 21164 evaluation board
2091 EB64+ EB64+ 21064 evaluation board
2092 EB66 EB66 21066 evaluation board
2093 EB66+ EB66+ 21066 evaluation board
2094 Jensen DECpc 150, DEC 2000 model 300,
2097 Miata Personal Workstation 433a, 433au, 500a,
2098 500au, 600a, or 600au
2100 Noname AXPpci33, UDB (Multia)
2101 Noritake AS 1000A, AS 600A, AS 800
2103 Rawhide AS 1200, AS 4000, AS 4100
2104 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
2106 Sable AS 2000, AS 2100
2109 Wildfire AlphaServer GS 40/80/160/320
2111 If you don't know what to do, choose "generic".
2113 EV5 CPU daughtercard
2115 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
2119 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
2121 Using SRM as bootloader
2123 There are two different types of booting firmware on Alphas: SRM,
2124 which is command line driven, and ARC, which uses menus and arrow
2125 keys. Details about the Linux/Alpha booting process are contained in
2126 the Linux/Alpha FAQ, accessible on the WWW from
2127 http://www.alphalinux.org .
2129 The usual way to load Linux on an Alpha machine is to use MILO
2130 (a bootloader that lets you pass command line parameters to the
2131 kernel just like lilo does for the x86 architecture) which can be
2132 loaded either from ARC or can be installed directly as a permanent
2133 firmware replacement from floppy (which requires changing a certain
2134 jumper on the motherboard). If you want to do either of these, say N
2135 here. If MILO doesn't work on your system (true for Jensen
2136 motherboards), you can bypass it altogether and boot Linux directly
2137 from an SRM console; say Y here in order to do that. Note that you
2138 won't be able to boot from an IDE disk using SRM.
2142 Legacy kernel start address
2143 CONFIG_ALPHA_LEGACY_START_ADDRESS
2144 The 2.4 kernel changed the kernel start address from 0x310000
2145 to 0x810000 to make room for the Wildfire's larger SRM console.
2147 If you're using aboot 0.7 or later, the bootloader will examine
2148 the ELF headers to determine where to transfer control. Unfortunately,
2149 most older bootloaders -- APB, or MILO -- hardcoded the kernel
2150 start address rather than examining the ELF headers, and the result
2153 Say Y if you have a broken bootloader. Say N if you do not, or
2154 if you wish to run on Wildfire.
2156 Non-standard serial port support
2157 CONFIG_SERIAL_NONSTANDARD
2158 Say Y here if you have any non-standard serial boards -- boards
2159 which aren't supported using the standard "dumb" serial driver.
2160 This includes intelligent serial boards such as Cyclades,
2161 Digiboards, etc. These are usually used for systems that need many
2162 serial ports because they serve many terminals or dial-in
2165 Note that the answer to this question won't directly affect the
2166 kernel: saying N will just cause this configure script to skip all
2167 the questions about non-standard serial boards.
2169 Most people can say N here.
2171 Extended dumb serial driver options
2172 CONFIG_SERIAL_EXTENDED
2173 If you wish to use any non-standard features of the standard "dumb"
2174 driver, say Y here. This includes HUB6 support, shared serial
2175 interrupts, special multiport support, support for more than the
2176 four COM 1/2/3/4 boards, etc.
2178 Note that the answer to this question won't directly affect the
2179 kernel: saying N will just cause this configure script to skip all
2180 the questions about serial driver options. If unsure, say N.
2182 Support more than 4 serial ports
2183 CONFIG_SERIAL_MANY_PORTS
2184 Say Y here if you have dumb serial boards other than the four
2185 standard COM 1/2/3/4 ports. This may happen if you have an AST
2186 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
2187 from http://www.linuxdoc.org/docs.html#howto ), or other custom
2188 serial port hardware which acts similar to standard serial port
2189 hardware. If you only use the standard COM 1/2/3/4 ports, you can
2190 say N here to save some memory. You can also say Y if you have an
2191 "intelligent" multiport card such as Cyclades, Digiboards, etc.
2193 Support for sharing serial interrupts
2194 CONFIG_SERIAL_SHARE_IRQ
2195 Some serial boards have hardware support which allows multiple dumb
2196 serial ports on the same board to share a single IRQ. To enable
2197 support for this in the serial driver, say Y here.
2199 Auto detect IRQ on standard ports (unsafe)
2200 CONFIG_SERIAL_DETECT_IRQ
2201 Say Y here if you want the kernel to try to guess which IRQ
2202 to use for your serial port.
2204 This is considered unsafe; it is far better to configure the IRQ in
2205 a boot script using the setserial command.
2209 Support special multiport boards
2210 CONFIG_SERIAL_MULTIPORT
2211 Some multiport serial ports have special ports which are used to
2212 signal when there are any serial ports on the board which need
2213 servicing. Say Y here to enable the serial driver to take advantage
2214 of those special I/O ports.
2216 SGI PROM Console Support
2217 CONFIG_SGI_PROM_CONSOLE
2218 Say Y here if you want to use the PROMs for console I/O.
2220 SGI Zilog85C30 serial support
2222 If you want to use your SGI's built-in serial ports under Linux,
2225 SGI Newport Graphics support (EXPERIMENTAL)
2226 CONFIG_SGI_NEWPORT_GFX
2227 If you have an SGI machine and you want to compile the graphics
2228 drivers, say Y here. This will include the code for the
2229 /dev/graphics and /dev/gfx drivers into the kernel for supporting
2230 virtualized access to your graphics hardware.
2232 SGI Newport Console support
2233 CONFIG_SGI_NEWPORT_CONSOLE
2234 Say Y here if you want the console on the Newport aka XL graphics
2235 card of your Indy. Most people say Y here.
2237 SGI DS1286 RTC support
2239 If you say Y here and create a character special file /dev/rtc with
2240 major number 10 and minor number 135 using mknod ("man mknod"), you
2241 will get access to the real time clock built into your computer.
2242 Every SGI has such a clock built in. It reports status information
2243 via the file /proc/rtc and its behaviour is set by various ioctls on
2246 Support the Bell Technologies HUB6 card
2248 Say Y here to enable support in the dumb serial driver to support
2251 PCMCIA serial device support
2252 CONFIG_PCMCIA_SERIAL_CS
2253 Say Y here to enable support for 16-bit PCMCIA serial devices,
2254 including serial port cards, modems, and the modem functions of
2255 multi-function ethernet/modem cards. (PCMCIA- or PC-cards are
2256 credit-card size devices often used with laptops.)
2258 This driver is also available as a module ( = code which can be
2259 inserted in and removed from the running kernel whenever you want).
2260 The module will be called serial_cs.o. If you want to compile it as
2261 a module, say M here and read Documentation/modules.txt. If unsure,
2264 CardBus serial device support
2265 CONFIG_PCMCIA_SERIAL_CB
2266 Say Y here to enable support for CardBus serial devices, including
2267 serial port cards, modems, and the modem functions of multi-function
2268 ethernet/modem devices. (CardBus cards are the newer and better
2269 version of PCMCIA- or PC-cards: credit card size devices often
2272 This driver is also available as a module ( = code which can be
2273 inserted in and removed from the running kernel whenever you want).
2274 The module will be called serial_cb.o. If you want to compile it as
2275 a module, say M here and read Documentation/modules.txt. If unsure,
2278 /dev/agpgart (AGP Support) (EXPERIMENTAL)
2280 AGP (Accelerated Graphics Port) is a bus system mainly used to
2281 connect graphics cards to the rest of the system.
2283 If you have an AGP system and you say Y here, it will be possible to
2284 use the AGP features of your 3D rendering video card. This code acts
2285 as a sort of "AGP driver" for the motherboard's chipset. The glx
2286 module will then be able to program the GART (graphics aperture
2287 relocation table) registers with appropriate values to transfer
2288 commands to the card.
2290 If you need more texture memory than you can get with the AGP GART
2291 (theoretically up to 256 MB, but in practice usually 64 or 128 MB
2292 due to kernel allocation issues), you could use PCI accesses
2293 and have up to a couple gigs of texture space.
2295 Note that this is the only means to have XFree4/GLX use
2296 write-combining with MTRR support on the AGP bus. Without it, OpenGL
2297 direct rendering will be a lot slower but still faster than PIO.
2299 For the moment, you should probably say N, unless you want to test
2300 the GLX component for XFree86 3.3.6, which can be downloaded from
2301 http://utah-glx.sourceforge.net/ , or need to use the 810 Xserver in
2304 This driver is available as a module. If you want to compile it as a
2305 module, say M here and read Documentation/modules.txt. The module
2306 will be called agpgart.o.
2308 Intel 440LX/BX/GX support
2310 This option gives you AGP support for the GLX component of the
2311 XFree86 4.x on Intel 440LX/BX/GX chipsets.
2313 For the moment, you should probably say N, unless you want to test
2314 the GLX component for XFree86 3.3.6, which can be downloaded from
2315 http://utah-glx.sourceforge.net/ .
2317 Intel I810/I810 DC100/I810e support
2319 This option gives you AGP support for the Xserver for the Intel
2320 810 chipset boards. This is required to do any useful video
2325 This option gives you AGP support for the GLX component of the
2326 XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
2328 For the moment, you should probably say N, unless you want to test
2329 the GLX component for XFree86 3.3.6, which can be downloaded from
2330 http://utah-glx.sourceforge.net/ .
2332 AMD Irongate support
2334 This option gives you AGP support for the GLX component of the
2335 XFree86 4.x on AMD Irongate chipset.
2337 For the moment, you should probably say N, unless you want to test
2338 the GLX component for XFree86 3.3.6, which can be downloaded from
2339 http://utah-glx.sourceforge.net/ .
2343 This option gives you AGP support for the GLX component of the "soon
2344 to be released" XFree86 4.x on Silicon Integrated Systems [SiS]
2347 Note that 5591/5592 AGP chipsets are NOT supported.
2349 For the moment, you should probably say N, unless you want to test
2350 the GLX component for XFree86 3.3.6, which can be downloaded from
2351 http://utah-glx.sourceforge.net/ .
2355 This option gives you AGP support for the GLX component of the
2356 XFree86 4.x on the ALi M1541 chipset.
2358 This chipset can do AGP 1x and 2x, but note that there is an
2359 acknowledged incompatibility with Matrox G200 cards. Due to
2360 timing issues, this chipset cannot do AGP 2x with the G200.
2361 This is a hardware limitation. AGP 1x seems to be fine, though.
2363 For the moment, you should probably say N, unless you want to test
2364 the GLX component for XFree86 3.3.6, which can be downloaded from
2365 http://utah-glx.sourceforge.net/ .
2369 Find out whether you have a PCI motherboard. PCI is the name of a
2370 bus system, i.e. the way the CPU talks to the other stuff inside
2371 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
2372 VESA. If you have PCI, say Y, otherwise N.
2374 The PCI-HOWTO, available from
2375 http://www.linuxdoc.org/docs.html#howto , contains valuable
2376 information about which PCI hardware does work under Linux and which
2380 CONFIG_PCI_INTEGRATOR
2381 Find out whether you have a PCI motherboard. PCI is the name of a
2382 bus system, i.e. the way the CPU talks to the other stuff inside
2383 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
2384 VESA. If you have PCI, say Y, otherwise N.
2386 The PCI-HOWTO, available from
2387 http://www.linuxdoc.org/docs.html#howto , contains valuable
2388 information about which PCI hardware does work under Linux and which
2393 Find out whether you have a PCI motherboard. PCI is the name of a
2394 bus system, i.e. the way the CPU talks to the other stuff inside
2395 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
2396 VESA. If you have PCI, say Y, otherwise N.
2398 The PCI-HOWTO, available from
2399 http://www.linuxdoc.org/docs.html#howto , contains valuable
2400 information about which PCI hardware does work under Linux and which
2405 On PCI systems, the BIOS can be used to detect the PCI devices and
2406 determine their configuration. However, some old PCI motherboards
2407 have BIOS bugs and may crash if this is done. Also, some embedded
2408 PCI-based systems don't have any BIOS at all. Linux can also try to
2409 detect the PCI hardware directly without using the BIOS.
2411 With this option, you can specify how Linux should detect the PCI
2412 devices. If you choose "BIOS", the BIOS will be used, if you choose
2413 "Direct", the BIOS won't be used, and if you choose "Any", the
2414 kernel will try the direct access method and falls back to the BIOS
2415 if that doesn't work. If unsure, go with the default, which is
2418 PCI device name database
2420 By default, the kernel contains a database of all known PCI device
2421 names to make the information in /proc/pci, /proc/ioports and
2422 similar files comprehensible to the user. This database increases
2423 size of the kernel image by about 80KB, but it gets freed after the
2424 system boots up, so it doesn't take up kernel memory. Anyway, if you
2425 are building an installation floppy or kernel for an embedded system
2426 where kernel image size really matters, you can disable this feature
2427 and you'll get device ID numbers instead of names.
2429 When in doubt, say Y.
2433 MicroChannel Architecture is found in some IBM PS/2 machines and
2434 laptops. It is a bus system similar to PCI or ISA. See
2435 Documentation/mca.txt (and especially the web page given there)
2436 before attempting to build an MCA bus kernel.
2438 SGI Visual Workstation support
2440 The SGI Visual Workstation series is an IA32-based workstation
2441 based on SGI systems chips with some legacy PC hardware attached.
2442 Say Y here to create a kernel to run on the SGI 320 or 540.
2443 A kernel compiled for the Visual Workstation will not run on other
2444 PC boards and vice versa.
2445 See Documentation/sgi-visws.txt for more.
2447 SGI Visual Workstation framebuffer support
2449 SGI Visual Workstation support for framebuffer graphics.
2453 The Intelligent Input/Output (I2O) architecture allows hardware
2454 drivers to be split into two parts: an operating system specific
2455 module called the OSM and an hardware specific module called the
2456 HDM. The OSM can talk to a whole range of HDM's, and ideally the
2457 HDM's are not OS dependent. This allows for the same HDM driver to
2458 be used under different operating systems if the relevant OSM is in
2459 place. In order for this to work, you need to have an I2O interface
2460 adapter card in your computer. This card contains a special I/O
2461 processor (IOP), thus allowing high speeds since the CPU does not
2462 have to deal with I/O.
2464 If you say Y here, you will get a choice of interface adapter
2465 drivers and OSM's with the following questions.
2467 This support is also available as a module ( = code which can be
2468 inserted in and removed from the running kernel whenever you want).
2469 If you want to compile it as a module, say M here and read
2470 Documentation/modules.txt. You will get modules called i2o_core.o
2477 Say Y for support of PCI bus I2O interface adapters. Currently this
2478 is the only variety supported, so you should say Y.
2480 This support is also available as a module called i2o_pci.o ( = code
2481 which can be inserted in and removed from the running kernel
2482 whenever you want). If you want to compile it as a module, say M
2483 here and read Documentation/modules.txt.
2487 Include support for the I2O Block OSM. The Block OSM presents disk
2488 and other structured block devices to the operating system.
2490 This support is also available as a module called i2o_block.o ( =
2491 code which can be inserted in and removed from the running kernel
2492 whenever you want). If you want to compile it as a module, say M
2493 here and read Documentation/modules.txt.
2497 Include support for the LAN OSM. You will also need to include
2498 support for token ring or FDDI if you wish to use token ring or FDDI
2499 I2O cards with this driver.
2501 This support is also available as a module called i2o_lan.o ( = code
2502 which can be inserted in and removed from the running kernel
2503 whenever you want). If you want to compile it as a module, say M
2504 here and read Documentation/modules.txt.
2508 Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
2509 I2O controller. You can use both the SCSI and Block OSM together if
2512 This support is also available as a module called i2o_scsi.o ( =
2513 code which can be inserted in and removed from the running kernel
2514 whenever you want). If you want to compile it as a module, say M
2515 here and read Documentation/modules.txt.
2519 If you say Y here and to "/proc file system support", you will be
2520 able to read I2O related information from the virtual directory
2523 This support is also available as a module called i2o_proc.o ( =
2524 code which can be inserted in and removed from the running kernel
2525 whenever you want). If you want to compile it as a module, say M
2526 here and read Documentation/modules.txt.
2528 Plug and Play support
2530 Plug and Play (PnP) is a standard for peripherals which allows those
2531 peripherals to be configured by software, e.g. assign IRQ's or other
2532 parameters. No jumpers on the cards are needed, instead the values
2533 are provided to the cards from the BIOS, from the operating system,
2534 or using a user-space utility.
2536 Say Y here if you would like Linux to configure your Plug and Play
2537 devices. You should then also say Y to "ISA Plug and Play support",
2538 below. Alternatively, you can say N here and configure your PnP
2539 devices using the user space utilities contained in the isapnptools
2542 This support is also available as a module ( = code which can be
2543 inserted in and removed from the running kernel whenever you want).
2544 If you want to compile it as a module, say M here and read
2545 Documentation/modules.txt.
2547 ISA Plug and Play support
2549 Say Y here if you would like support for ISA Plug and Play devices.
2550 Some information is in Documentation/isapnp.txt.
2552 This support is also available as a module called isapnp.o ( =
2553 code which can be inserted in and removed from the running kernel
2554 whenever you want). If you want to compile it as a module, say M
2555 here and read Documentation/modules.txt.
2559 Support for hot-pluggable devices
2561 Say Y here if you want to plug devices into your computer while
2562 the system is running, and be able to use them quickly. In many
2563 cases, the devices can likewise be unplugged at any time too.
2565 One well known example of this is PCMCIA- or PC-cards, credit-card
2566 size devices such as network cards, modems or hard drives which are
2567 plugged into slots found on all modern laptop computers.
2569 Another example, used on modern desktops as well as laptops, is USB.
2570 Enable HOTPLUG with USB and KMOD, and your kernel will automatically
2571 call out to a user mode "policy agent" to load modules and set up
2572 software needed to use USB devices you plug in. Get agent software
2573 (at http://www.linux-usb.org/policy.html) and install it.
2575 PCMCIA/Cardbus support
2577 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
2578 computer. These are credit-card size devices such as network cards,
2579 modems or hard drives often used with laptops computers. There are
2580 actually two varieties of these cards: the older 16 bit PCMCIA cards
2581 and the newer 32 bit CardBus cards. If you want to use CardBus
2582 cards, you need to say Y here and also to "CardBus support" below.
2584 To use your PC-cards, you will need supporting software from David
2585 Hinds' pcmcia-cs package (see the file Documentation/Changes for
2586 location). Please also read the PCMCIA-HOWTO, available from
2587 http://www.linuxdoc.org/docs.html#howto
2589 This driver is also available as a module ( = code which can be
2590 inserted in and removed from the running kernel whenever you want).
2591 When compiled this way, there will be modules called pcmcia_core.o
2592 and ds.o. If you want to compile it as a module, say M here and
2593 read Documentation/modules.txt.
2597 CardBus is a bus mastering architecture for PC-cards, which allows
2598 for 32 bit PC-cards (the original PCMCIA standard specifies only
2599 a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
2601 To use your PC-cards, you will need supporting software from David
2602 Hinds' pcmcia-cs package (see the file Documentation/Changes for
2607 i82365/Yenta compatible bridge support
2609 Say Y here to include support for PCMCIA and CardBus host bridges
2610 that are register compatible with the Intel i82365 and/or the Yenta
2611 specification: this includes virtually all modern PCMCIA bridges.
2612 "Bridge" is the name used for the hardware inside your computer that
2613 PCMCIA cards are plugged into. If unsure, say Y.
2615 Databook TCIC host bridge support
2617 Say Y here to include support for the Databook TCIC family of PCMCIA
2618 host bridges. These are only found on a handful of old systems.
2619 "Bridge" is the name used for the hardware inside your computer that
2620 PCMCIA cards are plugged into. If unsure, say N.
2624 Inter Process Communication is a suite of library functions and
2625 system calls which let processes (running programs) synchronize and
2626 exchange information. It is generally considered to be a good thing,
2627 and some programs won't run unless you say Y here. In particular, if
2628 you want to run the DOS emulator dosemu under Linux (read the
2629 DOSEMU-HOWTO, available from
2630 http://www.linuxdoc.org/docs.html#howto ), you'll need to say Y
2633 You can find documentation about IPC with "info ipc" and also in
2634 section 6.4 of the Linux Programmer's Guide, available from
2635 http://www.linuxdoc.org/docs.html#guide .
2637 Shared memory is now implemented using a new (minimal) virtual file
2638 system. To mount it automatically at system startup just add the
2639 following line to your /etc/fstab:
2641 none /dev/shm shm defaults 0 0
2643 Saying Y here enlarges your kernel by about 18 KB. Just say Y.
2645 BSD Process Accounting
2646 CONFIG_BSD_PROCESS_ACCT
2647 If you say Y here, a user level program will be able to instruct the
2648 kernel (via a special system call) to write process accounting
2649 information to a file: whenever a process exits, information about
2650 that process will be appended to the file by the kernel. The
2651 information includes things such as creation time, owning user,
2652 command name, memory usage, controlling terminal etc. (the complete
2653 list is in the struct acct in include/linux/acct.h). It is up to the
2654 user level program to do useful things with this information. This
2655 is generally a good idea, so say Y.
2659 The sysctl interface provides a means of dynamically changing
2660 certain kernel parameters and variables on the fly without requiring
2661 a recompile of the kernel or reboot of the system. The primary
2662 interface consists of a system call, but if you say Y to "/proc
2663 file system support", a tree of modifiable sysctl entries will be
2664 generated beneath the /proc/sys directory. They are explained in the
2665 files in Documentation/sysctl/. Note that enabling this option will
2666 enlarge the kernel by at least 8 KB.
2668 As it is generally a good thing, you should say Y here unless
2669 building a kernel for install/rescue disks or your system is very
2672 Kernel core (/proc/kcore) format
2674 If you enabled support for /proc file system then the file
2675 /proc/kcore will contain the kernel core image. This can be used
2678 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
2680 You have two choices here: ELF and A.OUT. Selecting ELF will make
2681 /proc/kcore appear in ELF core format as defined by the Executable
2682 and Linking Format specification. Selecting A.OUT will choose the
2683 old "a.out" format which may be necessary for some old versions
2684 of binutils or on some architectures.
2686 This is especially useful if you have compiled the kernel with the
2687 "-g" option to preserve debugging information. It is mainly used
2688 for examining kernel data structures on the live kernel so if you
2689 don't understand what this means or are not a kernel hacker, just
2690 leave it at its default value ELF.
2692 Kernel support for ELF binaries
2694 ELF (Executable and Linkable Format) is a format for libraries and
2695 executables used across different architectures and operating
2696 systems. Saying Y here will enable your kernel to run ELF binaries
2697 and enlarge it by about 13 KB. ELF support under Linux has now all
2698 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
2699 because it is portable (this does *not* mean that you will be able
2700 to run executables from different architectures or operating systems
2701 however) and makes building run-time libraries very easy. Many new
2702 executables are distributed solely in ELF format. You definitely
2705 Information about ELF is contained in the ELF HOWTO available from
2706 http://www.linuxdoc.org/docs.html#howto .
2708 If you find that after upgrading from Linux kernel 1.2 and saying Y
2709 here, you still can't run any ELF binaries (they just crash), then
2710 you'll have to install the newest ELF runtime libraries, including
2711 ld.so (check the file Documentation/Changes for location and latest
2714 If you want to compile this as a module ( = code which can be
2715 inserted in and removed from the running kernel whenever you want),
2716 say M here and read Documentation/modules.txt. The module will be
2717 called binfmt_elf.o. Saying M or N here is dangerous because some
2718 crucial programs on your system might be in ELF format.
2720 Kernel support for A.OUT binaries
2722 A.out (Assembler.OUTput) is a set of formats for libraries and
2723 executables used in the earliest versions of UNIX. Linux used the
2724 a.out formats QMAGIC and ZMAGIC until they were replaced with the
2727 As more and more programs are converted to ELF, the use for a.out
2728 will gradually diminish. If you disable this option it will reduce
2729 your kernel by one page. This is not much and by itself does not
2730 warrant removing support. However its removal is a good idea if you
2731 wish to ensure that absolutely none of your programs will use this
2732 older executable format. If you don't know what to answer at this
2733 point then answer Y. If someone told you "You need a kernel with
2734 QMAGIC support" then you'll have to say Y here. You may answer M to
2735 compile a.out support as a module and later load the module when you
2736 want to use a program or library in a.out format. The module will be
2737 called binfmt_aout.o. Saying M or N here is dangerous though,
2738 because some crucial programs on your system might still be in A.OUT
2741 Kernel support for Linux/Intel ELF binaries
2743 Say Y here if you want to be able to execute Linux/Intel ELF
2744 binaries just like native Alpha binaries on your Alpha machine. For
2745 this to work, you need to have the emulator /usr/bin/em86 in place.
2747 You can get the same functionality by saying N here and saying Y to
2748 "Kernel support for MISC binaries".
2750 You may answer M to compile the emulation support as a module and
2751 later load the module when you want to use a Linux/Intel binary. The
2752 module will be called binfmt_em86.o. If unsure, say Y.
2754 Kernel support for MISC binaries
2756 If you say Y here, it will be possible to plug wrapper-driven binary
2757 formats into the kernel. You will like this especially when you use
2758 programs that need an interpreter to run like Java, Python or
2759 Emacs-Lisp. It's also useful if you often run DOS executables under
2760 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
2761 http://www.linuxdoc.org/docs.html#howto ). Once you have
2762 registered such a binary class with the kernel, you can start one of
2763 those programs simply by typing in its name at a shell prompt; Linux
2764 will automatically feed it to the correct interpreter.
2766 You can do other nice things, too. Read the file
2767 Documentation/binfmt_misc.txt to learn how to use this feature, and
2768 Documentation/java.txt for information about how to include Java
2771 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
2772 use this part of the kernel.
2774 You may say M here for module support and later load the module when
2775 you have use for it; the module is called binfmt_misc.o. If you
2776 don't know what to answer at this point, say Y.
2778 Solaris binary emulation (EXPERIMENTAL)
2780 This is experimental code which will enable you to run (many)
2781 Solaris binaries on your SPARC Linux machine.
2783 This code is also available as a module ( = code which can be
2784 inserted in and removed from the running kernel whenever you want).
2785 The module will be called solaris.o. If you want to compile it as a
2786 module, say M here and read Documentation/modules.txt.
2790 This is the processor type of your CPU. This information is used for
2791 optimizing purposes. In order to compile a kernel that can run on
2792 all x86 CPU types (albeit not optimally fast), you can specify
2795 The kernel will not necessarily run on earlier architectures than
2796 the one you have chosen, e.g. a Pentium optimized kernel will run on
2797 a PPro, but not necessarily on a i486.
2799 Here are the settings recommended for greatest speed:
2800 - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
2801 486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels will
2802 run on a 386 class machine.
2803 - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
2804 SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
2805 - "586" for generic Pentium CPUs, possibly lacking the TSC
2806 (time stamp counter) register.
2807 - "Pentium-Classic" for the Intel Pentium.
2808 - "Pentium-MMX" for the Intel Pentium MMX.
2809 - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
2810 - "Pentium-III" for the Intel Pentium III.
2811 - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
2812 - "Athlon" for the AMD Athlon (K7).
2813 - "Crusoe" for the Transmeta Crusoe series.
2814 - "Winchip-C6" for original IDT Winchip.
2815 - "Winchip-2" for IDT Winchip 2.
2816 - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
2818 If you don't know what to do, choose "386".
2822 Saying Y here will allow you to use Linux in text mode through a
2823 display that complies with the generic VGA standard. Virtually
2824 everyone wants that.
2826 The program SVGATextMode can be used to utilize SVGA video cards to
2827 their full potential in text mode. Download it from
2828 ftp://metalab.unc.edu/pub/Linux/utils/console .
2832 Video mode selection support
2834 This enables support for text mode selection on kernel startup. If
2835 you want to take advantage of some high-resolution text mode your
2836 card's BIOS offers, but the traditional Linux utilities like
2837 SVGATextMode don't, you can say Y here and set the mode using the
2838 "vga=" option from your boot loader (lilo or loadlin) or set
2839 "vga=ask" which brings up a video mode menu on kernel startup. (Try
2840 "man bootparam" or see the documentation of your boot loader about
2841 how to pass options to the kernel.)
2843 Read the file Documentation/svga.txt for more information about the
2844 Video mode selection support. If unsure, say N.
2846 Support for frame buffer devices (EXPERIMENTAL)
2848 The frame buffer device provides an abstraction for the graphics
2849 hardware. It represents the frame buffer of some video hardware and
2850 allows application software to access the graphics hardware through
2851 a well-defined interface, so the software doesn't need to know
2852 anything about the low-level (hardware register) stuff.
2854 Frame buffer devices work identically across the different
2855 architectures supported by Linux and make the implementation of
2856 application programs easier and more portable; at this point, an X
2857 server exists which uses the frame buffer device exclusively.
2858 On several non-X86 architectures, the frame buffer device is the
2859 only way to use the graphics hardware.
2861 The device is accessed through special device nodes, usually located
2862 in the /dev directory, i.e. /dev/fb*.
2864 You need an utility program called fbset to make full use of frame
2865 buffer devices. Please read Documentation/fb/framebuffer.txt and the
2866 Framebuffer-HOWTO at
2867 http://www.tahallah.demon.co.uk/programming/prog.html for more
2870 Say Y here and to the driver for your graphics board below if you
2871 are compiling a kernel for a non-x86 architecture.
2873 If you are compiling for the x86 architecture, you can say Y if you
2874 want to play with it, but it is not essential. Please note that
2875 running graphical applications that directly touch the hardware
2876 (e.g. an accelerated X server) and that are not frame buffer
2877 device-aware may cause unexpected results. If unsure, say N.
2881 This is the frame buffer device driver for the Acorn VIDC graphics
2882 hardware found in Acorn RISC PCs and other ARM-based machines. If
2885 Amiga native chipset support
2887 This is the frame buffer device driver for the builtin graphics
2888 chipset found in Amigas.
2890 The driver is also available as a module ( = code which can be
2891 inserted and removed from the running kernel whenever you want). The
2892 module will be called amifb.o. If you want to compile it as a
2893 module, say M here and read Documentation/modules.txt.
2895 Amiga OCS chipset support
2897 This enables support for the original Agnus and Denise video chips,
2898 found in the Amiga 1000 and most A500's and A2000's. If you intend
2899 to run Linux on any of these systems, say Y; otherwise say N.
2901 Amiga ECS chipset support
2903 This enables support for the Enhanced Chip Set, found in later
2904 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
2905 you intend to run Linux on any of these systems, say Y; otherwise
2908 Amiga AGA chipset support
2910 This enables support for the Advanced Graphics Architecture (also
2911 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
2912 and CD32. If you intend to run Linux on any of these systems, say Y;
2915 Amiga CyberVision support
2917 This enables support for the Cybervision 64 graphics card from
2918 Phase5. Please note that its use is not all that intuitive (i.e. if
2919 you have any questions, be sure to ask!). Say N unless you have a
2920 Cybervision 64 or plan to get one before you next recompile the
2921 kernel. Please note that this driver DOES NOT support the
2922 Cybervision 64 3D card, as they use incompatible video chips.
2924 CyberPro 20x0 support
2926 This enables support for the Integraphics CyberPro 20x0 and 5000
2927 VGA chips used in the Rebel.com Netwinder and other machines.
2928 Say Y if you have a NetWinder or a graphics card containing this
2929 device, otherwise say N.
2931 Amiga CyberVision3D support (EXPERIMENTAL)
2933 This enables support for the Cybervision 64/3D graphics card from
2934 Phase5. Please note that its use is not all that intuitive (i.e. if
2935 you have any questions, be sure to ask!). Say N unless you have a
2936 Cybervision 64/3D or plan to get one before you next recompile the
2937 kernel. Please note that this driver DOES NOT support the older
2938 Cybervision 64 card, as they use incompatible video chips.
2940 Amiga RetinaZ3 support (EXPERIMENTAL)
2942 This enables support for the Retina Z3 graphics card. Say N unless
2943 you have a Retina Z3 or plan to get one before you next recompile
2946 Cirrus Logic generic driver (EXPERIMENTAL)
2948 This enables support for Cirrus Logic GD542x/543x based boards on
2949 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
2951 If you have a PCI-based system, this enables support for these
2952 chips: GD-543x, GD-544x, GD-5480.
2954 Please read the file Documentation/fb/clgenfb.txt.
2956 Say N unless you have such a graphics board or plan to get one
2957 before you next recompile the kernel.
2959 Permedia2 support (EXPERIMENTAL)
2961 Say Y here if this is your graphics board.
2965 Say Y here if you want to run Linux on an MC680x0-based Apollo
2966 Domain workstation such as the DN3500.
2968 Apollo 3c505 support
2969 CONFIG_APOLLO_ELPLUS
2970 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
2971 If you don't have one made for Apollos, you can use one from a PC,
2972 except that your Apollo won't be able to boot from it (because the
2973 code in the ROM will be for a PC).
2975 Atari native chipset support
2977 This is the frame buffer device driver for the builtin graphics
2978 chipset found in Ataris.
2980 Open Firmware frame buffer device support
2982 Say Y if you want support with Open Firmware for your graphics
2985 S3 Trio frame buffer device support
2987 If you have a S3 Trio say Y. Say N for S3 Virge.
2989 3Dfx Banshee/Voodoo3 display support (EXPERIMENTAL)
2991 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
2992 chips. Say Y if you have such a graphics board.
2994 The driver is also available as a module ( = code which can be
2995 inserted and removed from the running kernel whenever you want). The
2996 module will be called tdfxfb.o. If you want to compile it as a
2997 module, say M here and read Documentation/modules.txt.
2999 nVidia Riva support (EXPERIMENTAL)
3001 This driver supports graphics boards with the nVidia Riva (aka TNTx)
3003 Say Y if you have such a graphics board.
3005 The driver is also available as a module ( = code which can be
3006 inserted and removed from the running kernel whenever you want). The
3007 module will be called rivafb.o. If you want to compile it as a
3008 module, say M here and read Documentation/modules.txt.
3010 ATI Mach64 display support (EXPERIMENTAL)
3012 This driver supports graphics boards with the ATI Mach64 chips.
3013 Say Y if you have such a graphics board.
3015 The driver is also available as a module ( = code which can be
3016 inserted and removed from the running kernel whenever you want). The
3017 module will be called atyfb.o. If you want to compile it as a
3018 module, say M here and read Documentation/modules.txt.
3020 ATI Rage128 display support (EXPERIMENTAL)
3022 This driver supports graphics boards with the ATI Rage128 chips.
3023 Say Y if you have such a graphics board and read
3024 Documentation/fb/aty128fb.txt.
3026 The driver is also available as a module ( = code which can be
3027 inserted and removed from the running kernel whenever you want). The
3028 module will be called aty128fb.o. If you want to compile it as a
3029 module, say M here and read Documentation/modules.txt.
3031 PowerMac "control" frame buffer device support
3033 This driver supports a frame buffer for the graphics adapter in the
3034 Power Macintosh 7300 and others.
3036 PowerMac "platinum" frame buffer device support
3038 This driver supports a frame buffer for the "platinum" graphics
3039 adapter in some Power Macintoshes.
3041 PowerMac "valkyrie" frame buffer device support
3043 This driver supports a frame buffer for the "valkyrie" graphics
3044 adapter in some Power Macintoshes.
3046 Chips 65550 display support
3048 This is the frame buffer device driver for the Chips & Technologies
3049 65550 graphics chip in PowerBooks.
3051 TGA frame buffer support
3053 This is the frame buffer device driver for generic TGA graphic
3054 cards. Say Y if you have one of those.
3056 VESA VGA graphics console
3058 This is the frame buffer device driver for generic VESA 2.0
3059 compliant graphic cards. The older VESA 1.2 cards are not supported.
3060 You will get a boot time penguin logo at no additional cost. Please
3061 read Documentation/fb/vesafb.txt. If unsure, say Y.
3063 VGA 16-color planar support
3064 CONFIG_FBCON_VGA_PLANES
3065 This low level frame buffer console driver enable the kernel to use
3066 the 16-color planar modes of the old VGA cards where the bits of
3067 each pixel are separated into 4 planes.
3069 Only answer Y here if you have a (very old) VGA card that isn't VESA
3072 VGA 16-color graphics console
3074 This is the frame buffer device driver for VGA 16 color graphic
3075 cards. Say Y if you have such a card.
3077 This code is also available as a module. If you want to compile it
3078 as a module ( = code which can be inserted in and removed from the
3079 running kernel whenever you want), say M here and read
3080 Documentation/modules.txt. The module will be called vga16fb.o.
3082 Select other compiled-in fonts
3084 Say Y here if you would like to use fonts other than the default
3085 your frame buffer console usually use.
3087 Note that the answer to this question won't directly affect the
3088 kernel: saying N will just cause this configure script to skip all
3089 the questions about foreign fonts.
3091 If unsure, say N (the default choices are safe).
3095 This is the "high resolution" font for the VGA frame buffer (the one
3096 provided by the VGA text console 80x25 mode.
3100 Support only 8 pixels wide fonts
3101 CONFIG_FBCON_FONTWIDTH8_ONLY
3102 Answer Y here will make the kernel provide only the 8x8 fonts (these
3103 are the less readable).
3107 Sparc console 8x16 font
3109 This is the high resolution console font for Sun machines. Say Y.
3111 Sparc console 12x22 font (not supported by all drivers)
3112 CONFIG_FONT_SUN12x22
3113 This is the high resolution console font for Sun machines with very
3114 big letters (like the letters used in the SPARC PROM). If the
3115 standard font is unreadable for you, say Y, otherwise say N.
3119 This is the "high resolution" font for the VGA frame buffer (the one
3120 provided by the text console 80x50 (and higher) modes).
3122 Note that this is a poor quality font. The VGA 8x16 font is quite a
3125 Given the resolution provided by the frame buffer device, answer N
3128 Backward compatibility mode for Xpmac
3129 CONFIG_FB_COMPAT_XPMAC
3130 If you use the Xpmac X server (common with mklinux), you'll need to
3131 say Y here to use X. You should consider changing to XFree86 which
3132 includes a server that supports the frame buffer device directly
3135 HGA monochrome support (EXPERIMENTAL)
3137 Say Y here if you have a Hercules mono graphics card.
3139 This driver is also available as a module ( = code which can be
3140 inserted and removed from the running kernel whenever you want).
3141 The module will be called hgafb.o. If you want to compile it as
3142 a module, say M here and read Documentation/modules.txt.
3144 As this card technology is 15 years old, most people will answer N
3147 Matrox unified accelerated driver (EXPERIMENTAL)
3149 Say Y here if you have a Matrox Millennium, Matrox Millennium II,
3150 Matrox Mystique, Matrox Mystique 220, Matrox Productiva G100, Matrox
3151 Mystique G200, Matrox Millennium G200, Matrox Marvel G200 video or
3152 Matrox G400 card in your box. At this time, support for the G100,
3153 Mystique G200 and Marvel G200 is untested.
3155 This driver is also available as a module ( = code which can be
3156 inserted and removed from the running kernel whenever you want).
3157 The module will be called matroxfb.o. If you want to compile it as
3158 a module, say M here and read Documentation/modules.txt.
3160 You can pass several parameters to the driver at boot time or at
3161 module load time. The parameters look like "video=matrox:XXX", where
3162 the meaning of XXX can be found at the end of the main source file
3163 (drivers/video/matroxfb.c). Please see the file
3164 Documentation/fb/matroxfb.txt.
3166 Matrox Millennium support
3167 CONFIG_FB_MATROX_MILLENIUM
3168 Say Y here if you have a Matrox Millennium or Matrox Millennium II
3169 video card. If you select "Advanced lowlevel driver options" below,
3170 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
3171 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
3172 also use font widths different from 8.
3174 Matrox Mystique support
3175 CONFIG_FB_MATROX_MYSTIQUE
3176 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
3177 video card. If you select "Advanced lowlevel driver options" below,
3178 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
3179 packed pixel and 32 bpp packed pixel. You can also use font widths
3182 Matrox G100/G200/G400 support
3183 CONFIG_FB_MATROX_G100
3184 Say Y here if you have a Matrox Productiva G100, Matrox Mystique
3185 G200, Matrox Marvel G200 or Matrox Millennium G200 video card. If
3186 you select "Advanced lowlevel driver options", you should check 8
3187 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed pixel and 32
3188 bpp packed pixel. You can also use font widths different from 8.
3190 If you need support for G400 secondary head, you must first say Y to
3191 "I2C support" and "I2C bit-banging support" in the character devices
3192 section, and then to "Matrox I2C support" and "G400 second head
3193 support" here in the framebuffer section.
3196 CONFIG_FB_MATROX_I2C
3197 This drivers creates I2C buses which are needed for accessing the
3198 DDC (I2C) bus present on all Matroxes, an I2C bus which
3199 interconnects Matrox optional devices, like MGA-TVO on G200 and
3200 G400, and the secondary head DDC bus, present on G400 only.
3202 You can say Y or M here if you want to experiment with monitor
3203 detection code. You must say Y or M here if you want to use either
3204 second head of G400 or MGA-TVO on G200 or G400.
3206 If you compile it as module, it will create a module named
3209 Matrox G400 second head support
3210 CONFIG_FB_MATROX_MAVEN
3211 Say Y or M here if you want to use a secondary head (meaning two
3212 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
3213 head is not compatible with accelerated XFree 3.3.x SVGA servers -
3214 secondary head output is blanked while you are in X. With XFree
3215 3.9.17 preview you can use both heads if you use SVGA over fbdev or
3216 the fbdev driver on first head and the fbdev driver on second head.
3218 If you compile it as module, two modules are created,
3219 matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
3220 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
3221 also load i2c-matroxfb to get it to run.
3223 The driver starts in monitor mode and you must use the matroxset
3224 tool (available at ftp://platan.vc.cvut.cz/pub/linux/matrox-latest)
3225 to switch it to PAL or NTSC or to swap primary and secondary head
3226 outputs. Secondary head driver also always start in 640x480
3227 resolution, you must use fbset to change it.
3229 Also do not forget that second head supports only 16 and 32 bpp
3230 packed pixels, so it is a good idea to compile them into the kernel
3231 too. You can use only some font widths, as the driver uses generic
3232 painting procedures (the secondary head does not use acceleration
3235 There is no need for enabling 'Matrox multihead support' if you have
3236 only one Matrox card in the box.
3238 Matrox unified driver multihead support
3239 CONFIG_FB_MATROX_MULTIHEAD
3240 Say Y here if you have more than one (supported) Matrox device in
3241 your computer and you want to use all of them for different monitors
3242 ("multihead"). If you have only one device, you should say N because
3243 the driver compiled with Y is larger and a bit slower, especially on
3246 If you said M to "Matrox unified accelerated driver" and N here, you
3247 will still be able to use several Matrox devices simultaneously:
3248 insert several instances of the module matroxfb.o into the kernel
3249 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
3250 for the different Matrox devices. This method is slightly faster but
3251 uses 40 KB of kernel memory per Matrox card.
3253 MDA text console (dual-headed)
3255 Say Y here if you have an old MDA or monochrome Hercules graphics
3256 adapter in your system acting as a second head ( = video card). You
3257 will then be able to use two monitors with your Linux system. Do not
3258 say Y here if your MDA card is the primary card in your system; the
3259 normal VGA driver will handle it.
3261 This driver is also available as a module ( = code which can be
3262 inserted and removed from the running kernel whenever you want).
3263 The module will be called mdacon.o. If you want to compile it as
3264 a module, say M here and read Documentation/modules.txt.
3268 SBUS and UPA frame buffers
3270 Say Y if you want support for SBUS or UPA based frame buffer device.
3272 Creator/Creator3D support
3274 This is the frame buffer device driver for the Creator and Creator3D
3277 CGsix (GX,TurboGX) support
3279 This is the frame buffer device driver for the CGsix (GX, TurboGX)
3284 This is the frame buffer device driver for the BWtwo frame buffer.
3288 This is the frame buffer device driver for the CGthree frame buffer.
3290 TCX (SS4/SS5 only) support
3292 This is the frame buffer device driver for the TCX 24/8bit frame
3295 Virtual Frame Buffer support (ONLY FOR TESTING!)
3297 This is a `virtual' frame buffer device. It operates on a chunk of
3298 unswapable kernel memory instead of on the memory of a graphics
3299 board. This means you cannot see any output sent to this frame
3300 buffer device, while it does consume precious memory. The main use
3301 of this frame buffer device is testing and debugging the frame
3302 buffer subsystem. Do NOT enable it for normal systems! To protect
3303 the innocent, it has to be enabled explicitly at boot time using the
3304 kernel option `video=vfb:'.
3306 This driver is also available as a module ( = code which can be
3307 inserted and removed from the running kernel whenever you want). The
3308 module will be called vfb.o. If you want to compile it as a module,
3309 say M here and read Documentation/modules.txt.
3314 This is a framebuffer device for the SA-1100 LCD Controller.
3315 See http://www.linux-fbdev.org/ for information on framebuffer
3318 If you plan to use the LCD display with your SA-1100 system, say
3321 Advanced low level driver options
3322 CONFIG_FBCON_ADVANCED
3323 The frame buffer console uses character drawing routines that are
3324 tailored to the specific organization of pixels in the memory of
3325 your graphics hardware. These are called the low level frame buffer
3326 console drivers. Note that they are used for text console output
3327 only; they are NOT needed for graphical applications.
3329 If you say N here, the needed low level drivers are automatically
3330 enabled, depending on what frame buffer devices you selected above.
3331 This is recommended for most users.
3333 If you say Y here, you have more fine-grained control over which low
3334 level drivers are enabled. You can e.g. leave out low level drivers
3335 for color depths you do not intend to use for text consoles.
3337 Low level frame buffer console drivers can be modules ( = code which
3338 can be inserted and removed from the running kernel whenever you
3339 want). The modules will be called fbcon-*.o. If you want to compile
3340 (some of) them as modules, read Documentation/modules.txt.
3346 This is the low level frame buffer console driver for monochrome
3347 (2 colors) packed pixels.
3349 2 bpp packed pixels support
3351 This is the low level frame buffer console driver for 2 bits per
3352 pixel (4 colors) packed pixels.
3354 4 bpp packed pixels support
3356 This is the low level frame buffer console driver for 4 bits per
3357 pixel (16 colors) packed pixels.
3359 8 bpp packed pixels support
3361 This is the low level frame buffer console driver for 8 bits per
3362 pixel (256 colors) packed pixels.
3364 16 bpp packed pixels support
3366 This is the low level frame buffer console driver for 15 or 16 bits
3367 per pixel (32K or 64K colors, also known as `hicolor') packed
3370 24 bpp packed pixels support
3372 This is the low level frame buffer console driver for 24 bits per
3373 pixel (16M colors, also known as `truecolor') packed pixels. It is
3374 NOT for `sparse' 32 bits per pixel mode.
3376 32 bpp packed pixels support
3378 This is the low level frame buffer console driver for 32 bits per
3379 pixel (16M colors, also known as `truecolor') sparse packed pixels.
3381 Amiga bitplanes support
3383 This is the low level frame buffer console driver for 1 to 8
3384 bitplanes (2 to 256 colors) on Amiga.
3386 Amiga interleaved bitplanes support
3388 This is the low level frame buffer console driver for 1 to 8
3389 interleaved bitplanes (2 to 256 colors) on Amiga.
3391 Atari interleaved bitplanes (2 planes) support
3392 CONFIG_FBCON_IPLAN2P2
3393 This is the low level frame buffer console driver for 2 interleaved
3394 bitplanes (4 colors) on Atari.
3396 Atari interleaved bitplanes (4 planes) support
3397 CONFIG_FBCON_IPLAN2P4
3398 This is the low level frame buffer console driver for 4 interleaved
3399 bitplanes (16 colors) on Atari.
3401 Atari interleaved bitplanes (8 planes) support
3402 CONFIG_FBCON_IPLAN2P8
3403 This is the low level frame buffer console driver for 8 interleaved
3404 bitplanes (256 colors) on Atari.
3406 Mac variable bpp packed pixels support
3408 This is the low level frame buffer console driver for 1/2/4/8/16/32
3409 bits per pixel packed pixels on Mac. It supports variable font
3410 widths for low resolution screens.
3412 HGA monochrome support (EXPERIMENTAL)
3414 This is the low level frame buffer console driver for Hercules mono
3417 VGA characters/attributes support
3419 This is the low level frame buffer console driver for VGA text mode;
3420 it is used by frame buffer device drivers that support VGA text
3423 Parallel-port support
3425 If you want to use devices connected to your machine's parallel port
3426 (the connector at the computer with 25 holes), e.g. printer, ZIP
3427 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
3428 create a mini network by connecting the parallel ports of two local
3429 machines) etc., then you need to say Y here; please read
3430 Documentation/parport.txt and drivers/parport/BUGS-parport.
3432 For extensive information about drivers for many devices attaching
3433 to the parallel port see http://www.torque.net/linux-pp.html on the
3436 It is possible to share a single parallel port among several devices
3437 and it is safe to compile all the corresponding drivers into the
3438 kernel. If you want to compile parallel port support as a module ( =
3439 code which can be inserted in and removed from the running kernel
3440 whenever you want), say M here and read Documentation/modules.txt.
3441 The module will be called parport.o. If you have more than one
3442 parallel port and want to specify which port and IRQ to be used by
3443 this driver at module load time, take a look at
3444 Documentation/networking/parport.txt.
3450 You should say Y here if you have a PC-style parallel port. All IBM
3451 PC compatible computers and some Alphas have PC-style parallel
3454 This code is also available as a module. If you want to compile it
3455 as a module ( = code which can be inserted in and removed from the
3456 running kernel whenever you want), say M here and read
3457 Documentation/modules.txt. The module will be called parport_pc.o.
3461 Use FIFO/DMA if available
3462 CONFIG_PARPORT_PC_FIFO
3463 Many parallel port chipsets provide hardware that can speed up
3464 printing. Say Y here if you want to take advantage of that.
3466 As well as actually having a FIFO, or DMA capability, the kernel
3467 will need to know which IRQ the parallel port has. By default,
3468 parallel port interrupts will not be used, and so neither will the
3469 FIFO. See Documentation/parport.txt to find out how to specify
3470 which IRQ/DMA to use.
3472 SuperIO chipset support (EXPERIMENTAL)
3473 CONFIG_PARPORT_PC_SUPERIO
3474 Saying Y here enables some probes for Super-IO chipsets in order to
3475 find out things like base addresses, IRQ lines and DMA channels. It
3478 Support for PCMCIA management for PC-style ports
3479 CONFIG_PARPORT_PC_PCMCIA
3480 Say Y here if you need PCMCIA support for your PC-style parallel
3481 ports. If unsure, say N.
3483 Support foreign hardware
3484 CONFIG_PARPORT_OTHER
3485 Say Y here if you want to be able to load driver modules to support
3486 other non-standard types of parallel ports. This causes a
3487 performance loss, so most people say N.
3489 Support IEEE1284 status readback
3490 CONFIG_PRINTER_READBACK
3491 If you have a device on your parallel port that support this
3492 protocol, this option will allow the device to report its status. It
3495 IEEE1284 transfer modes
3497 If you have a printer that supports status readback or device ID, or
3498 want to use a device that uses enhanced parallel port transfer modes
3499 such as EPP and ECP, say Y here to enable advanced IEEE 1284
3500 transfer modes. Also say Y if you want device ID information to
3501 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
3503 Enable loadable module support
3505 Kernel modules are small pieces of compiled code which can be
3506 inserted in or removed from the running kernel, using the programs
3507 insmod and rmmod. This is described in the file
3508 Documentation/modules.txt, including the fact that you have to say
3509 "make modules" in order to compile the modules that you chose during
3510 kernel configuration. Modules can be device drivers, file systems,
3511 binary executable formats, and so on. If you think that you may want
3512 to make use of modules with this kernel in the future, then say Y
3513 here. If unsure, say Y.
3515 Set version information on all symbols for modules
3517 Usually, modules have to be recompiled whenever you switch to a new
3518 kernel. Saying Y here makes it possible, and safe, to use the
3519 same modules even after compiling a new kernel; this requires the
3520 program modprobe. All the software needed for module support is in
3521 the modutils package (check the file Documentation/Changes for
3522 location and latest version). NOTE: if you say Y here but don't
3523 have the program genksyms (which is also contained in the above
3524 mentioned modutils package), then the building of your kernel will
3525 fail. If you are going to use modules that are generated from
3526 non-kernel sources, you would benefit from this option. Otherwise
3527 it's not that important. So, N ought to be a safe bet.
3529 Kernel module loader support
3531 Normally when you have selected some drivers and/or file systems to
3532 be created as loadable modules, you also have the responsibility to
3533 load the corresponding modules (using the programs insmod or
3534 modprobe) before you can use them. If you say Y here however, the
3535 kernel will be able to load modules for itself: when a part of the
3536 kernel needs a module, it runs modprobe with the appropriate
3537 arguments, thereby loading the module if it is available. (This is a
3538 replacement for kerneld.) Say Y here and read about configuring it
3539 in Documentation/kmod.txt.
3541 ARP daemon support (EXPERIMENTAL)
3543 Normally, the kernel maintains an internal cache which maps IP
3544 addresses to hardware addresses on the local network, so that
3545 Ethernet/Token Ring/ etc. frames are sent to the proper address on
3546 the physical networking layer. For small networks having a few
3547 hundred directly connected hosts or less, keeping this address
3548 resolution (ARP) cache inside the kernel works well. However,
3549 maintaining an internal ARP cache does not work well for very large
3550 switched networks, and will use a lot of kernel memory if TCP/IP
3551 connections are made to many machines on the network.
3553 If you say Y here, the kernel's internal ARP cache will never grow
3554 to more than 256 entries (the oldest entries are expired in a LIFO
3555 manner) and communication will be attempted with the user space ARP
3556 daemon arpd. Arpd then answers the address resolution request either
3557 from its own cache or by asking the net.
3559 This code is experimental and also obsolete. If you want to use it,
3560 you need to find a version of the daemon arpd on the net somewhere,
3561 and you should also say Y to "Kernel/User network link driver",
3562 below. If unsure, say N.
3566 These are the protocols used on the Internet and on most local
3567 Ethernets. It is highly recommended to say Y here (this will enlarge
3568 your kernel by about 144 KB), since some programs (e.g. the X window
3569 system) use TCP/IP even if your machine is not connected to any
3570 other computer. You will get the so-called loopback device which
3571 allows you to ping yourself (great fun, that!).
3573 For an excellent introduction to Linux networking, please read the
3574 NET-3-HOWTO, available from
3575 http://www.linuxdoc.org/docs.html#howto .
3577 This option is also necessary if you want to use the full power of
3578 term (term is a program which gives you almost full Internet
3579 connectivity if you have a regular dial up shell account on some
3580 Internet connected Unix computer; for more information, read
3581 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
3583 If you say Y here and also to "/proc file system support" and
3584 "Sysctl support" below, you can change various aspects of the
3585 behavior of the TCP/IP code by writing to the (virtual) files in
3586 /proc/sys/net/ipv4/*; the options are explained in the file
3587 Documentation/Networking/ip-sysctl.txt.
3589 Short answer: say Y.
3593 This is code for addressing several networked computers at once,
3594 enlarging your kernel by about 2 KB. You need multicasting if you
3595 intend to participate in the MBONE, a high bandwidth network on top
3596 of the Internet which carries audio and video broadcasts. More
3597 information about the MBONE is on the WWW at
3598 http://www-itg.lbl.gov/mbone/ . Information about the multicast
3599 capabilities of the various network cards is contained in
3600 Documentation/networking/multicast.txt. For most people, it's safe
3604 CONFIG_IP_ADVANCED_ROUTER
3605 If you intend to run your Linux box mostly as a router, i.e. as a
3606 computer that forwards and redistributes network packets, say Y; you
3607 will then be presented with several options that allow more precise
3608 control about the routing process.
3610 The answer to this question won't directly affect the kernel:
3611 answering N will just cause this configure script to skip all the
3612 questions about advanced routing.
3614 Note that your box can only act as a router if you enable IP
3615 forwarding in your kernel; you can do that by saying Y to "/proc
3616 file system support" and "Sysctl support" below and executing the
3619 echo "1" > /proc/sys/net/ipv4/ip_forward
3621 at boot time after the /proc file system has been mounted.
3623 If you turn on IP forwarding, you will also get the rp_filter, which
3624 automatically rejects incoming packets if the routing table entry
3625 for their source address doesn't match the network interface they're
3626 arriving on. This has security advantages because it prevents the
3627 so-called IP spoofing, however it can pose problems if you use
3628 asymmetric routing (packets from you to a host take a different path
3629 than packets from that host to you) or if you operate a non-routing
3630 host which has several IP addresses on different interfaces. To turn
3633 echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
3635 echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
3637 If unsure, say N here.
3640 CONFIG_IP_MULTIPLE_TABLES
3641 Normally, a router decides what to do with a received packet based
3642 solely on the packet's final destination address. If you say Y here,
3643 the Linux router will also be able to take the packet's source
3644 address into account. Furthermore, if you also say Y to "IP: use TOS
3645 value as routing key" below, the TOS (Type-Of-Service) field of the
3646 packet can be used for routing decisions as well. In addition, if
3647 you say Y here and to "IP: fast network address translation" below,
3648 the router will also be able to modify source and destination
3649 addresses of forwarded packets.
3651 If you are interested in this, please see the preliminary
3652 documentation at http://www.compendium.com.ar/policy-routing.txt and
3653 ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex . You
3654 will need supporting software from ftp://ftp.inr.ac.ru/ip-routing/
3658 IP: equal cost multipath
3659 CONFIG_IP_ROUTE_MULTIPATH
3660 Normally, the routing tables specify a single action to be taken in
3661 a deterministic manner for a given packet. If you say Y here
3662 however, it becomes possible to attach several actions to a packet
3663 pattern, in effect specifying several alternative paths to travel
3664 for those packets. The router considers all these paths to be of
3665 equal "cost" and chooses one of them in a non-deterministic fashion
3666 if a matching packet arrives.
3668 IP: use TOS value as routing key
3670 The header of every IP packet carries a TOS (Type Of Service) value
3671 with which the packet requests a certain treatment, e.g. low latency
3672 (for interactive traffic), high throughput, or high reliability. If
3673 you say Y here, you will be able to specify different routes for
3674 packets with different TOS values.
3676 IP: use netfilter MARK value as routing key
3677 CONFIG_IP_ROUTE_FWMARK
3678 If you say Y here, you will be able to specify different routes for
3679 packets with different mark values (see iptables(8), MARK target).
3681 IP: verbose route monitoring
3682 CONFIG_IP_ROUTE_VERBOSE
3683 If you say Y here, which is recommended, then the kernel will print
3684 verbose messages regarding the routing, for example warnings about
3685 received packets which look strange and could be evidence of an
3686 attack or a misconfigured system somewhere. The information is
3687 handled by the klogd daemon which is responsible for kernel messages
3690 IP: large routing tables
3691 CONFIG_IP_ROUTE_LARGE_TABLES
3692 If you have routing zones that grow to more than about 64 entries,
3693 you may want to say Y here to speed up the routing process.
3695 IP: fast network address translation
3697 If you say Y here, your router will be able to modify source and
3698 destination addresses of packets that pass through it, in a manner
3699 you specify. General information about Network Address Translation
3700 can be gotten from the document
3701 http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html
3703 IP: kernel level autoconfiguration
3705 This enables automatic configuration of IP addresses of devices and
3706 of the routing table during kernel boot, based on either information
3707 supplied on the kernel command line or by BOOTP or RARP protocols.
3708 You need to say Y only for diskless machines requiring network
3709 access to boot (in which case you want to say Y to "Root file system
3710 on NFS" as well), because all other machines configure the network
3711 in their startup scripts.
3715 If you want your Linux box to mount its whole root file system (the
3716 one containing the directory /) from some other computer over the
3717 net via NFS and you want the IP address of your computer to be
3718 discovered automatically at boot time using the BOOTP protocol (a
3719 special protocol designed for doing this job), say Y here. In case
3720 the boot ROM of your network card was designed for booting Linux and
3721 does BOOTP itself, providing all necessary information on the kernel
3722 command line, you can say N here. If unsure, say Y. Note that if you
3723 want to use BOOTP, a BOOTP server must be operating on your network.
3724 Read Documentation/nfsroot.txt for details.
3728 If you want your Linux box to mount its whole root file system (the
3729 one containing the directory /) from some other computer over the
3730 net via NFS and you want the IP address of your computer to be
3731 discovered automatically at boot time using the RARP protocol (an
3732 older protocol which is being obsoleted by BOOTP and DHCP), say Y
3733 here. Note that if you want to use RARP, a RARP server must be
3734 operating on your network. Read Documentation/nfsroot.txt for
3739 Tunneling means encapsulating data of one protocol type within
3740 another protocol and sending it over a channel that understands the
3741 encapsulating protocol. This particular tunneling driver implements
3742 encapsulation of IP within IP, which sounds kind of pointless, but
3743 can be useful if you want to make your (or some other) machine
3744 appear on a different network than it physically is, or to use
3745 mobile-IP facilities (allowing laptops to seamlessly move between
3746 networks without changing their IP addresses; check out
3747 http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html ).
3749 Saying Y to this option will produce two modules ( = code which can
3750 be inserted in and removed from the running kernel whenever you
3751 want). Most people won't need this and can say N.
3753 IP: GRE tunnels over IP
3755 Tunneling means encapsulating data of one protocol type within
3756 another protocol and sending it over a channel that understands the
3757 encapsulating protocol. This particular tunneling driver implements
3758 GRE (Generic Routing Encapsulation) and at this time allows
3759 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
3760 This driver is useful if the other endpoint is a Cisco router: Cisco
3761 likes GRE much better than the other Linux tunneling driver ("IP:
3762 tunneling" above). In addition, GRE allows multicast redistribution
3765 IP: broadcast GRE over IP
3766 CONFIG_NET_IPGRE_BROADCAST
3767 One application of GRE/IP is to construct a broadcast WAN (Wide Area
3768 Network), which looks like a normal Ethernet LAN (Local Area
3769 Network), but can be distributed all over the Internet. If you want
3770 to do that, say Y here and to "IP: multicast routing" below.
3772 IP: multicast routing
3774 This is used if you want your machine to act as a router for IP
3775 packets that have several destination addresses. It is needed on the
3776 MBONE, a high bandwidth network on top of the Internet which carries
3777 audio and video broadcasts. In order to do that, you would most
3778 likely run the program mrouted. Information about the multicast
3779 capabilities of the various network cards is contained in
3780 Documentation/networking/multicast.txt. If you haven't heard about
3781 it, you don't need it.
3783 IP: PIM-SM version 1 support
3785 Kernel side support for Sparse Mode PIM (Protocol Independent
3786 Multicast) version 1. This multicast routing protocol is used widely
3787 because Cisco supports it. You need special software to use it
3788 (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
3789 information about PIM.
3791 Say Y if you want to use PIM-SM v1. Note that you can say N here if
3792 you just want to use Dense Mode PIM.
3794 IP: PIM-SM version 2 support
3796 Kernel side support for Sparse Mode PIM version 2. In order to use
3797 this, you need an experimental routing daemon supporting it (pimd or
3798 gated-5). This routing protocol is not used widely, so say N unless
3799 you want to play with it.
3801 PC/TCP compatibility mode
3803 If you have been having difficulties telnetting to your Linux
3804 machine from a DOS system that uses (broken) PC/TCP networking
3805 software (all versions up to OnNet 2.0) over your local Ethernet try
3806 saying Y here. Everyone else says N.
3808 People having problems with NCSA telnet should see the file
3809 Documentation/networking/ncsa-telnet.
3811 Path MTU Discovery (normally enabled)
3812 CONFIG_PATH_MTU_DISCOVERY
3813 MTU (maximal transfer unit) is the size of the chunks we send out
3814 over the net. "Path MTU Discovery" means that, instead of always
3815 sending very small chunks, we start out sending big ones and if we
3816 then discover that some host along the way likes its chunks smaller,
3817 we adjust to a smaller size. This is good, so most people say Y
3820 However, some DOS software (versions of DOS NCSA telnet and Trumpet
3821 Winsock in PPP mode) is broken and won't be able to connect to your
3822 Linux machine correctly in all cases (especially through a terminal
3823 server) unless you say N here. See
3824 Documentation/networking/ncsa-telnet for the location of fixed NCSA
3825 telnet clients. If in doubt, say Y.
3827 Disable NAGLE algorithm (normally enabled)
3828 CONFIG_TCP_NAGLE_OFF
3829 The NAGLE algorithm works by requiring an acknowledgment before
3830 sending small IP frames (packets). This keeps tiny telnet and
3831 rlogin packets from congesting Wide Area Networks. Most people
3832 strongly recommend to say N here, thereby leaving NAGLE
3833 enabled. Those programs that would benefit from disabling this
3834 facility can do it on a per connection basis themselves.
3836 IP: Allow large windows (not recommended if <16 MB of memory)
3838 On high speed, long distance networks the performance limit on
3839 networking becomes the amount of data the sending machine can buffer
3840 until the other end confirms its reception. (At 45 Mbit/second there
3841 are a lot of bits between New York and London ...). If you say Y
3842 here, bigger buffers can be used which allows larger amounts of data
3843 to be "in flight" at any given time. It also means a user process
3844 can require a lot more memory for network buffers and thus this
3845 option is best used only on machines with 16 MB of memory or higher.
3846 Unless you are using long links with end to end speeds of over 2
3847 Mbit a second or satellite links this option will make no difference
3852 If you say Y here, you will include support for Unix domain sockets;
3853 sockets are the standard Unix mechanism for establishing and
3854 accessing network connections. Many commonly used programs such as
3855 the X Window system and syslog use these sockets even if your
3856 machine is not connected to any network. Unless you are working on
3857 an embedded system or something similar, you therefore definitely
3860 However, the socket support is also available as a module ( = code
3861 which can be inserted in and removed from the running kernel
3862 whenever you want). If you want to compile it as a module, say M
3863 here and read Documentation/modules.txt. The module will be called
3864 unix.o. If you try building this as a module and you have said Y to
3865 "Kernel module loader support" above, be sure to add 'alias net-pf-1
3866 unix' to your /etc/modules.conf file. Note that several important
3867 services won't work correctly if you say M here and then neglect to
3870 Say Y unless you know what you are doing.
3872 The IPv6 protocol (EXPERIMENTAL)
3874 This is experimental support for the next version of the Internet
3875 Protocol: IP version 6 (also called IPng "IP next generation").
3876 Features of this new protocol include: expanded address space,
3877 authentication and privacy, and seamless interoperability with the
3878 current version of IP (IP version 4). For general information about
3879 IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html ;
3880 for specific information about IPv6 under Linux read the HOWTO at
3881 http://www.bieringer.de/linux/IPv6/ and the file net/ipv6/README in
3884 If you want to use IPv6, please upgrade to the newest net-tools as
3885 given in Documentation/Changes. You will still be able to do regular
3886 IPv4 networking as well.
3888 This protocol support is also available as a module ( = code which
3889 can be inserted in and removed from the running kernel whenever you
3890 want). The module will be called ipv6.o. If you want to compile it
3891 as a module, say M here and read Documentation/modules.txt.
3893 It is safe to say N here for now.
3895 IPv6: enable EUI-64 token format
3897 6bone, the network of computers using the IPv6 protocol, is moving
3898 to a new aggregatable address format and a new link local address
3899 assignment (EUI-64). Say Y if your site has upgraded already, or
3900 has started to upgrade.
3902 IPv6: disable provider based addresses
3904 Linux tries to operate correctly when your site has moved to EUI-64
3905 only partially. Unfortunately, the two address formats (old:
3906 "provider based" and new: "aggregatable") are incompatible. Say Y if
3907 your site finished the upgrade to EUI-64, and/or you encountered
3908 some problems caused by the presence of two link-local addresses on
3911 IPv6: routing messages via old netlink
3913 You can say Y here to receive routing messages from the IPv6 code
3914 through the old netlink interface. However, a better option is to
3915 say Y to "Kernel/User network link driver" and to "Routing
3918 Kernel httpd acceleration (EXPERIMENTAL)
3920 The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
3921 server built into the kernel. It is limited since it can only serve
3922 files from the file system and cannot deal with executable content
3923 such as CGI scripts. Serving files is sped up if you use kHTTPd.
3924 If kHTTPd is not able to fulfill a request, it can transparently
3925 pass it through to a user space web server such as apache.
3927 Saying "M" here builds the kHTTPd module; this is NOT enough to have
3928 a working kHTTPd. For safety reasons, the module has to be activated
3929 by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
3932 Before using this, read the README in net/khttpd !
3934 The kHTTPd is experimental. Be careful when using it on a production
3935 machine. Also note that kHTTPd doesn't support virtual servers yet.
3939 This is support for the Novell networking protocol, IPX, commonly
3940 used for local networks of Windows machines. You need it if you want
3941 to access Novell NetWare file or print servers using the Linux
3942 Novell client ncpfs (available from
3943 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ ) or from within
3944 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
3945 http://www.linuxdoc.org/docs.html#howto ). In order to do the
3946 former, you'll also have to say Y to "NCP file system support",
3949 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
3950 is similar to TCP. There is also experimental support for SPX in
3951 Linux (see "SPX networking", below).
3953 To turn your Linux box into a fully featured NetWare file server and
3954 IPX router, say Y here and fetch either lwared from
3955 ftp://metalab.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
3956 from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs . For more information,
3957 read the IPX-HOWTO available from
3958 http://www.linuxdoc.org/docs.html#howto .
3960 General information about how to connect Linux, Windows machines and
3961 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
3963 The IPX driver would enlarge your kernel by about 16 KB. This driver
3964 is also available as a module ( = code which can be inserted in and
3965 removed from the running kernel whenever you want). The module will
3966 be called ipx.o. If you want to compile it as a module, say M here
3967 and read Documentation/modules.txt. Unless you want to integrate
3968 your Linux box with a local Novell network, say N.
3970 IPX: Full internal IPX network
3972 Every IPX network has an address that identifies it. Sometimes it is
3973 useful to give an IPX "network" address to your Linux box as well
3974 (for example if your box is acting as a file server for different
3975 IPX networks: it will then be accessible from everywhere using the
3976 same address). The way this is done is to create a virtual internal
3977 "network" inside your box and to assign an IPX address to this
3978 network. Say Y here if you want to do this; read the IPX-HOWTO at
3979 http://www.linuxdoc.org/docs.html#howto for details.
3981 The full internal IPX network enables you to allocate sockets on
3982 different virtual nodes of the internal network. This is done by
3983 evaluating the field sipx_node of the socket address given to the
3984 bind call. So applications should always initialize the node field
3985 to 0 when binding a socket on the primary network. In this case the
3986 socket is assigned the default node that has been given to the
3987 kernel when the internal network was created. By enabling the full
3988 internal IPX network the cross-forwarding of packets targeted at
3989 'special' sockets to sockets listening on the primary network is
3990 disabled. This might break existing applications, especially RIP/SAP
3991 daemons. A RIP/SAP daemon that works well with the full internal net
3992 can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs .
3994 If you don't know what you are doing, say N.
3996 IPX: SPX networking (EXPERIMENTAL)
3998 The Sequenced Packet eXchange protocol is a transport layer protocol
3999 built on top of IPX. It is used in Novell NetWare systems for
4000 client-server applications and is similar to TCP (which runs on top
4003 Note that Novell NetWare file sharing does not use SPX; it uses a
4004 protocol called NCP, for which separate Linux support is available
4005 ("NCP file system support" below for the client side, and the user
4006 space programs lwared or mars_nwe for the server side).
4008 Say Y here if you have use for SPX; read the IPX-HOWTO at
4009 http://www.linuxdoc.org/docs.html#howto for details.
4011 This driver is also available as a module ( = code which can be
4012 inserted in and removed from the running kernel whenever you want).
4013 The module will be called af_spx.o. If you want to compile it as a
4014 module, say M here and read Documentation/modules.txt.
4016 DECnet networking (EXPERIMENTAL)
4018 The DECnet networking protocol was used in many products made by
4019 Digital (now Compaq). It provides reliable stream and sequenced
4020 packet communications over which run a variety of services similar
4021 to those which run over TCP/IP.
4023 To find some tools to use with the kernel layer support, please
4024 look at Patrick Caulfield's web site:
4025 http://linux.dreamtime.org/decnet/
4027 More detailed documentation is available in the
4028 Documentation/networking/decnet.txt file.
4030 Be sure to say Y to "/proc file system support" and "Sysctl support"
4031 below when using DECnet, since you will need sysctl support to aid
4032 in configuration at run time.
4034 The DECnet code is also available as a module ( = code which can be
4035 inserted in and removed from the running kernel whenever you want).
4036 The module is called decnet.o.
4038 DECnet SIOCFIGCONF support
4039 CONFIG_DECNET_SIOCGIFCONF
4040 This option should only be turned on if you are really sure that
4041 you know what you are doing. It can break other applications which
4042 use this system call and the proper way to get the information
4043 provided by this call is to use rtnetlink.
4047 DECnet Router Support (EXPERIMENTAL)
4048 CONFIG_DECNET_ROUTER
4049 Add support for turning your DECnet Endnode into a level 1 or 2
4050 router. This is an unfinished option for developers only. If you do
4051 say Y here, then make sure that you also say Y to "Kernel/User
4052 network link driver", "Routing messages" and "Network packet
4053 filtering". The first two are required to allow configuration via
4054 rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
4055 from ftp://ftp.inr.ac.ru). The "Network packet filtering" option
4056 will be required for the forthcoming routing daemon to work.
4058 See Documentation/networking/decnet.txt for more information.
4060 DECnet: use FWMARK value as routing key
4061 CONFIG_DECNET_ROUTE_FWMARK
4062 If you say Y here, you will be able to specify different routes for
4063 packets with different FWMARK ("firewalling mark") values
4064 (see ipchains(8), "-m" argument).
4066 Appletalk interfaces support
4068 AppleTalk is the way Apple computers speak to each other on a
4069 network. If your Linux box is connected to such a network and you
4070 want to join the conversation, say Y.
4072 AppleTalk protocol support
4074 AppleTalk is the way Apple computers speak to each other on a
4075 network. If your Linux box is connected to such a network and you
4076 want to join the conversation, say Y. You will need to use the
4077 netatalk package so that your Linux box can act as a print and file
4078 server for Macs as well as access AppleTalk printers. Check out
4079 http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
4080 for details. EtherTalk is the name used for AppleTalk over Ethernet
4081 and the cheaper and slower LocalTalk is AppleTalk over a proprietary
4082 Apple network using serial links. EtherTalk and LocalTalk are fully
4085 General information about how to connect Linux, Windows machines and
4086 Macs is on the WWW at http://www.eats.com/linux_mac_win.html . The
4087 NET-3-HOWTO, available from
4088 http://www.linuxdoc.org/docs.html#howto , contains valuable
4089 information as well.
4091 This driver is also available as a module ( = code which can be
4092 inserted in and removed from the running kernel whenever you want).
4093 The module is called appletalk.o. If you want to compile it as a
4094 module, say M here and read Documentation/modules.txt. I hear that
4095 the GNU boycott of Apple is over, so even politically correct people
4096 are allowed to say Y here.
4098 AppleTalk-IP driver support
4100 This allows IP networking for users who only have AppleTalk
4101 networking available. This feature is experimental. With this
4102 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
4103 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
4104 you want your Linux box to act as an Internet gateway for a zoo of
4105 AppleTalk connected Macs). Please see the file
4106 Documentation/networking/ipddp.txt for more information.
4108 If you say Y here, the AppleTalk-IP support will be compiled into
4109 the kernel. In this case, you can either use encapsulation or
4110 decapsulation, but not both. With the following two questions, you
4111 decide which one you want.
4113 If you say M here, the AppleTalk-IP support will be compiled as a
4114 module ( = code which can be inserted in and removed from the
4115 running kernel whenever you want, read Documentation/modules.txt).
4116 The module is called ipddp.o. In this case, you will be able to use
4117 both encapsulation and decapsulation simultaneously, by loading two
4118 copies of the module and specifying different values for the module
4121 IP to AppleTalk-IP Encapsulation support
4123 If you say Y here, the AppleTalk-IP code will be able to encapsulate
4124 IP packets inside AppleTalk frames; this is useful if your Linux box
4125 is stuck on an AppleTalk network (which hopefully contains a
4126 decapsulator somewhere). Please see
4127 Documentation/networking/ipddp.txt for more information. If you said
4128 Y to "AppleTalk-IP driver support" above and you say Y here, then
4129 you cannot say Y to "AppleTalk-IP to IP Decapsulation support",
4132 AppleTalk-IP to IP Decapsulation support
4134 If you say Y here, the AppleTalk-IP code will be able to decapsulate
4135 AppleTalk-IP frames to IP packets; this is useful if you want your
4136 Linux box to act as an Internet gateway for an AppleTalk network.
4137 Please see Documentation/networking/ipddp.txt for more information.
4138 If you said Y to "AppleTalk-IP driver support" above and you say Y
4139 here, then you cannot say Y to "IP to AppleTalk-IP Encapsulation
4142 Apple/Farallon LocalTalk PC card support
4144 This allows you to use the AppleTalk PC card to connect to LocalTalk
4145 networks. The card is also known as the Farallon PhoneNet PC card.
4146 If you are in doubt, this card is the one with the 65C02 chip on it.
4147 You also need version 1.3.3 or later of the netatalk package.
4148 This driver is experimental, which means that it may not work.
4149 See the file Documentation/networking/ltpc.txt.
4151 COPS LocalTalk PC card support
4153 This allows you to use COPS AppleTalk cards to connect to LocalTalk
4154 networks. You also need version 1.3.3 or later of the netatalk
4155 package. This driver is experimental, which means that it may not
4156 work. This driver will only work if you choose "AppleTalk DDP"
4157 networking support, above.
4158 Please read the file Documentation/networking/cops.txt.
4160 Dayna firmware support
4162 Support COPS compatible cards with Dayna style firmware (Dayna
4163 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
4164 III, Farallon PhoneNET PC II).
4166 Tangent firmware support
4168 Support COPS compatible cards with Tangent style firmware (Tangent
4169 ATB_II, Novell NL-1000, Daystar Digital LT-200.
4171 Amateur Radio support
4173 If you want to connect your Linux box to an amateur radio, answer Y
4174 here. You want to read http://www.tapr.org/tapr/html/pkthome.html
4175 and the HAM-HOWTO and the AX25-HOWTO, both available from
4176 http://www.linuxdoc.org/docs.html#howto .
4178 Note that the answer to this question won't directly affect the
4179 kernel: saying N will just cause this configure script to skip all
4180 the questions about amateur radio.
4182 Amateur Radio AX.25 Level 2
4184 This is the protocol used for computer communication over amateur
4185 radio. It is either used by itself for point-to-point links, or to
4186 carry other protocols such as tcp/ip. To use it, you need a device
4187 that connects your Linux box to your amateur radio. You can either
4188 use a low speed TNC (a Terminal Node Controller acts as a kind of
4189 modem connecting your computer's serial port to your radio's
4190 microphone input and speaker output) supporting the KISS protocol or
4191 one of the various SCC cards that are supported by the generic Z8530
4192 or the DMA SCC driver. Another option are the Baycom modem serial
4193 and parallel port hacks or the sound card modem (supported by their
4194 own drivers). If you say Y here, you also have to say Y to one of
4197 Information about where to get supporting software for Linux amateur
4198 radio as well as information about how to configure an AX.25 port is
4199 contained in the AX25-HOWTO, available from
4200 http://www.linuxdoc.org/docs.html#howto . You might also want to
4201 check out the file Documentation/networking/ax25.txt in the kernel
4202 source. More information about digital amateur radio in general is
4203 on the WWW at http://www.tapr.org/tapr/html/pkthome.html .
4205 This driver is also available as a module ( = code which can be
4206 inserted in and removed from the running kernel whenever you want).
4207 The module will be called ax25.o. If you want to compile it as a
4208 module, say M here and read Documentation/modules.txt.
4210 AX.25 DAMA Slave support
4211 CONFIG_AX25_DAMA_SLAVE
4212 DAMA is a mechanism to prevent collisions when doing AX.25
4213 networking. A DAMA server (called "master") accepts incoming traffic
4214 from clients (called "slaves") and redistributes it to other slaves.
4215 If you say Y here, your Linux box will act as a DAMA slave; this is
4216 transparent in that you don't have to do any special DAMA
4217 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
4220 AX.25 DAMA Master support
4221 CONFIG_AX25_DAMA_MASTER
4222 DAMA is a mechanism to prevent collisions when doing AX.25
4223 networking. A DAMA server (called "master") accepts incoming traffic
4224 from clients (called "slaves") and redistributes it to other
4225 slaves. If you say Y here, your Linux box will act as a DAMA server.
4228 Amateur Radio NET/ROM
4230 NET/ROM is a network layer protocol on top of AX.25 useful for
4233 A comprehensive listing of all the software for Linux amateur radio
4234 users as well as information about how to configure an AX.25 port is
4235 contained in the AX25-HOWTO, available from
4236 http://www.linuxdoc.org/docs.html#howto . You also might want to
4237 check out the file Documentation/networking/ax25.txt. More
4238 information about digital amateur radio in general is on the WWW at
4239 http://www.tapr.org/tapr/html/pkthome.html .
4241 This driver is also available as a module ( = code which can be
4242 inserted in and removed from the running kernel whenever you want).
4243 The module will be called netrom.o. If you want to compile it as a
4244 module, say M here and read Documentation/modules.txt.
4246 Amateur Radio X.25 PLP (Rose)
4248 The Packet Layer Protocol (PLP) is a way to route packets over X.25
4249 connections in general and amateur radio AX.25 connections in
4250 particular, essentially an alternative to NET/ROM.
4252 A comprehensive listing of all the software for Linux amateur radio
4253 users as well as information about how to configure an AX.25 port is
4254 contained in the AX25-HOWTO, available from
4255 http://www.linuxdoc.org/docs.html#howto . You also might want to
4256 check out the file Documentation/networking/ax25.txt. More
4257 information about digital amateur radio in general is on the WWW at
4258 http://www.tapr.org/tapr/html/pkthome.html .
4260 This driver is also available as a module ( = code which can be
4261 inserted in and removed from the running kernel whenever you want).
4262 The module will be called rose.o. If you want to compile it as a
4263 module, say M here and read Documentation/modules.txt.
4265 Serial port KISS driver for AX.25
4267 KISS is a protocol used for the exchange of data between a computer
4268 and a Terminal Node Controller (a small embedded system commonly
4269 used for networking over AX.25 amateur radio connections; it
4270 connects the computer's serial port with the radio's microphone
4271 input and speaker output).
4273 Although KISS is less advanced than the 6pack protocol, it has
4274 the advantage that it is already supported by most modern TNCs
4275 without the need for a firmware upgrade.
4277 If you want to compile this driver as a module ( = code which can be
4278 inserted in and removed from the running kernel whenever you want),
4279 say M here and read Documentation/modules.txt. The module will be
4282 Serial port 6PACK driver for AX.25
4284 6pack is a transmission protocol for the data exchange between your
4285 PC and your TNC (the Terminal Node Controller acts as a kind of
4286 modem connecting your computer's serial port to your radio's
4287 microphone input and speaker output). This protocol can be used as
4288 an alternative to KISS for networking over AX.25 amateur radio
4289 connections, but it has some extended functionality.
4291 Note that this driver is still experimental and might cause
4292 problems. For details about the features and the usage of the
4293 driver, read Documentation/networking/6pack.txt.
4295 If you want to compile this driver as a module ( = code which can be
4296 inserted in and removed from the running kernel whenever you want),
4297 say M here and read Documentation/modules.txt. The module will be
4302 AX.25 is the protocol used for computer communication over amateur
4303 radio. If you say Y here, you will be able to send and receive AX.25
4304 traffic over Ethernet (also called "BPQ AX.25"), which could be
4305 useful if some other computer on your local network has a direct
4306 amateur radio connection.
4308 High-speed (DMA) SCC driver for AX.25
4310 This is a driver for high-speed SCC boards, i.e. those supporting
4311 DMA on one port. You usually use those boards to connect your
4312 computer to an amateur radio modem (such as the WA4DSY 56kbps
4313 modem), in order to send and receive AX.25 packet radio network
4316 Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
4317 PackeTwin, and S5SCC/DMA boards. They are detected automatically.
4318 If you have one of these cards, say Y here and read the AX25-HOWTO,
4319 available from http://www.linuxdoc.org/docs.html#howto .
4321 This driver can operate multiple boards simultaneously. If you
4322 compile it as a module (by saying M instead of Y), it will be called
4323 dmascc.o. If you don't pass any parameter to the driver, all
4324 possible I/O addresses are probed. This could irritate other devices
4325 that are currently not in use. You may specify the list of addresses
4326 to be probed by "dmascc=addr1,addr2,..." (when compiled into the
4327 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
4328 network interfaces will be called dmascc0 and dmascc1 for the board
4329 detected first, dmascc2 and dmascc3 for the second one, and so on.
4331 Before you configure each interface with ifconfig, you MUST set
4332 certain parameters, such as channel access timing, clock mode, and
4333 DMA channel. This is accomplished with a small utility program,
4334 dmascc_cfg, available at
4335 http://www.nt.tuwien.ac.at/~kkudielk/Linux/ . Please be sure to get
4336 at least version 1.27 of dmascc_cfg, as older versions will not
4337 work with the current driver.
4339 Z8530 SCC driver for AX.25
4341 These cards are used to connect your Linux box to an amateur radio
4342 in order to communicate with other computers. If you want to use
4343 this, read Documentation/networking/z8530drv.txt and the AX25-HOWTO,
4344 available from http://www.linuxdoc.org/docs.html#howto . Also
4345 make sure to say Y to "Amateur Radio AX.25 Level 2" support.
4347 If you want to compile this as a module ( = code which can be
4348 inserted in and removed from the running kernel whenever you want),
4349 say M here and read Documentation/modules.txt. The module will be
4352 additional delay for PA0HZP OptoSCC compatible boards
4354 Say Y here if you experience problems with the SCC driver not
4355 working properly; please read Documentation/networking/z8530drv.txt
4356 for details. If unsure, say N.
4358 #support for TRX that feedback the tx signal to rx
4361 ### Don't know what's going on here.
4365 YAM driver for AX.25
4367 The YAM is a modem for packet radio which connects to the serial
4368 port and includes some of the functions of a Terminal Node
4369 Controller. If you have one of those, say Y here.
4371 If you want to compile this 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.
4375 BAYCOM picpar and par96 driver for AX.25
4377 This is a driver for Baycom style simple amateur radio modems that
4378 connect to a parallel interface. The driver supports the picpar and
4379 par96 designs. To configure the driver, use the sethdlc utility
4380 available in the standard ax25 utilities package. For information on
4381 the modems, see http://www.baycom.de and the file
4382 Documentation/networking/baycom.txt.
4384 If you want to compile this driver as a module ( = code which can be
4385 inserted in and removed from the running kernel whenever you want),
4386 say M here and read Documentation/modules.txt. This is recommended.
4387 The module will be called baycom_par.o.
4389 BAYCOM EPP driver for AX.25
4391 This is a driver for Baycom style simple amateur radio modems that
4392 connect to a parallel interface. The driver supports the EPP
4393 designs. To configure the driver, use the sethdlc utility available
4394 in the standard ax25 utilities package. For information on the
4395 modems, see http://www.baycom.de and the file
4396 Documentation/networking/baycom.txt.
4398 If you want to compile this driver as a module ( = code which can be
4399 inserted in and removed from the running kernel whenever you want),
4400 say M here and read Documentation/modules.txt. This is recommended.
4401 The module will be called baycom_par.o.
4403 BAYCOM ser12 full duplex driver for AX.25
4404 CONFIG_BAYCOM_SER_FDX
4405 This is one of two drivers for Baycom style simple amateur radio
4406 modems that connect to a serial interface. The driver supports the
4407 ser12 design in full duplex mode. In addition, it allows the
4408 baudrate to be set between 300 and 4800 baud (however not all modems
4409 support all baudrates). This is the preferred driver. The next
4410 driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
4411 driver and still provided in case this driver does not work with
4412 your serial interface chip. To configure the driver, use the sethdlc
4413 utility available in the standard ax25 utilities package. For
4414 information on the modems, see http://www.baycom.de and
4415 Documentation/networking/baycom.txt.
4417 If you want to compile this driver as a module ( = code which can be
4418 inserted in and removed from the running kernel whenever you want),
4419 say M here and read Documentation/modules.txt. This is recommended.
4420 The module will be called baycom_ser_fdx.o.
4422 BAYCOM ser12 half duplex driver for AX.25
4423 CONFIG_BAYCOM_SER_HDX
4424 This is one of two drivers for Baycom style simple amateur radio
4425 modems that connect to a serial interface. The driver supports the
4426 ser12 design in full duplex mode. This is the old driver. It is
4427 still provided in case your serial interface chip does not work with
4428 the full duplex driver. This driver is depreciated. To configure the
4429 driver, use the sethdlc utility available in the standard ax25
4430 utilities package. For information on the modems, see
4431 http://www.baycom.de and Documentation/networking/baycom.txt.
4433 If you want to compile this driver as a module ( = code which can be
4434 inserted in and removed from the running kernel whenever you want),
4435 say M here and read Documentation/modules.txt. This is recommended.
4436 The module will be called baycom_ser_hdx.o.
4438 Sound card modem driver for AX.25
4440 This experimental driver allows a standard Sound Blaster or
4441 WindowsSoundSystem compatible sound card to be used as a packet
4442 radio modem (NOT as a telephone modem!), to send digital traffic
4445 To configure the driver, use the sethdlc, smdiag and smmixer
4446 utilities available in the standard ax25 utilities package. For
4447 information on how to key the transmitter, see
4448 http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html and
4449 Documentation/networking/soundmodem.txt.
4451 If you want to compile this driver as a module ( = code which can be
4452 inserted in and removed from the running kernel whenever you want),
4453 say M here and read Documentation/modules.txt. This is recommended.
4454 The module will be called soundmodem.o.
4456 Sound card modem support for Sound Blaster and compatible cards
4457 CONFIG_SOUNDMODEM_SBC
4458 This option enables the soundmodem driver to use Sound Blaster and
4459 compatible cards. If you have a dual mode card (i.e. a WSS cards
4460 with a Sound Blaster emulation) you should say N here and Y to
4461 "Sound card modem support for WSS and Crystal cards", below, because
4462 this usually results in better performance. This option also
4463 supports SB16/32/64 in full duplex mode.
4465 Sound card modem support for WSS and Crystal cards
4466 CONFIG_SOUNDMODEM_WSS
4467 This option enables the soundmodem driver to use WindowsSoundSystem
4468 compatible cards. These cards feature a codec chip from either
4469 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
4470 Semiconductors (such as CS4248, CS423x). This option also supports
4471 the WSS full duplex operation which currently works with Crystal
4472 CS423x chips. If you don't need full duplex operation, do not enable
4473 it to save performance.
4475 Sound card modem support for 1200 baud AFSK modulation
4476 CONFIG_SOUNDMODEM_AFSK1200
4477 This option enables the soundmodem driver 1200 baud AFSK modem,
4478 compatible to popular modems using TCM3105 or AM7911. The
4479 demodulator requires about 12% of the CPU power of a Pentium 75 CPU
4482 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
4483 CONFIG_SOUNDMODEM_AFSK2400_7
4484 This option enables the soundmodem driver 2400 baud AFSK modem,
4485 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
4486 crystal. Note that the availability of this driver does _not_ imply
4487 that I recommend building such links. It is only here since users
4488 especially in eastern Europe have asked me to do so. In fact this
4489 modulation scheme has many disadvantages, mainly its incompatibility
4490 with many transceiver designs and the fact that the TCM3105 (if
4491 used) is operated widely outside its specifications.
4493 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
4494 CONFIG_SOUNDMODEM_AFSK2400_8
4495 This option enables the soundmodem driver 2400 baud AFSK modem,
4496 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
4497 Note that the availability of this driver does _not_ imply that I
4498 recommend building such links. It is only here since users
4499 especially in eastern Europe have asked me to do so. In fact this
4500 modulation scheme has many disadvantages, mainly its incompatibility
4501 with many transceiver designs and the fact that the TCM3105 (if
4502 used) is operated widely outside its specifications.
4504 Sound card modem support for 2666 baud AFSK modulation
4505 CONFIG_SOUNDMODEM_AFSK2666
4506 This option enables the soundmodem driver 2666 baud AFSK modem.
4507 This modem is experimental, and not compatible to anything
4510 Sound card modem support for 4800 baud 8PSK modulation
4511 CONFIG_SOUNDMODEM_PSK4800
4512 This option enables the soundmodem driver 4800 baud 8PSK modem.
4513 This modem is experimental, and not compatible to anything
4516 Sound card modem support for 4800 baud HAPN-1 modulation
4517 CONFIG_SOUNDMODEM_HAPN4800
4518 This option enables the soundmodem driver 4800 baud HAPN-1
4519 compatible modem. This modulation seems to be widely used 'down
4520 under' and in the Netherlands. Here, nobody uses it, so I could not
4521 test if it works. It is compatible to itself, however :-)
4523 Sound card modem support for 9600 baud FSK G3RUH modulation
4524 CONFIG_SOUNDMODEM_FSK9600
4525 This option enables the soundmodem driver 9600 baud FSK modem,
4526 compatible to the G3RUH standard. The demodulator requires about 4%
4527 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
4528 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
4529 can only use one protocol at a time, depending on what the other end
4532 CCITT X.25 Packet Layer (EXPERIMENTAL)
4534 X.25 is a set of standardized network protocols, similar in scope to
4535 frame relay; the one physical line from your box to the X.25 network
4536 entry point can carry several logical point-to-point connections
4537 (called "virtual circuits") to other computers connected to the X.25
4538 network. Governments, banks, and other organizations tend to use it
4539 to connect to each other or to form Wide Area Networks (WANs). Many
4540 countries have public X.25 networks. X.25 consists of two
4541 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
4542 if you want that) and the lower level data link layer protocol LAPB
4543 (say Y to "LAPB Data Link Driver" below if you want that).
4545 You can read more about X.25 at http://www.sangoma.com/x25.htm and
4546 http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm .
4547 Information about X.25 for Linux is contained in the files
4548 Documentation/networking/x25.txt and
4549 Documentation/networking/x25-iface.txt.
4551 One connects to an X.25 network either with a dedicated network card
4552 using the X.21 protocol (not yet supported by Linux) or one can do
4553 X.25 over a standard telephone line using an ordinary modem (say Y
4554 to "X.25 async driver" below) or over Ethernet using an ordinary
4555 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
4556 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
4557 and "LAPB over Ethernet driver" below).
4559 If you want to compile this driver as a module ( = code which can be
4560 inserted in and removed from the running kernel whenever you want),
4561 say M here and read Documentation/modules.txt. The module will be
4562 called x25.o. If unsure, say N.
4564 LAPB Data Link Driver (EXPERIMENTAL)
4566 Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
4567 the lower) part of the X.25 protocol. It offers a reliable
4568 connection service to exchange data frames with one other host, and
4569 it is used to transport higher level protocols (mostly X.25 Packet
4570 Layer, the higher part of X.25, but others are possible as well).
4571 Usually, LAPB is used with specialized X.21 network cards, but Linux
4572 currently supports LAPB only over Ethernet connections. If you want
4573 to use LAPB connections over Ethernet, say Y here and to "LAPB over
4574 Ethernet driver" below. Read
4575 Documentation/networking/lapb-module.txt for technical details.
4577 If you want to compile this driver as a module though ( = code which
4578 can be inserted in and removed from the running kernel whenever you
4579 want), say M here and read Documentation/modules.txt. The module
4580 will be called lapb.o. If unsure, say N.
4582 802.2 LLC (EXPERIMENTAL)
4584 This is a Logical Link Layer protocol used for X.25 connections over
4585 Ethernet, using ordinary Ethernet cards.
4587 802.1d Ethernet Bridging
4589 If you say Y here, then your Linux box will be able to act as an
4590 Ethernet bridge, which means that the different Ethernet segments it
4591 is connected to will appear as one Ethernet to the participants.
4592 Several such bridges can work together to create even larger
4593 networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
4594 As this is a standard, Linux bridges will cooperate properly with
4595 other third party bridge products.
4597 In order to use the ethernet bridge, you'll need the bridge
4598 configuration tools; see Documentation/networking/bridge.txt for
4599 location. Please read the Bridge mini-HOWTO for more information.
4601 Note that if your box acts as a bridge, it probably contains several
4602 Ethernet devices, but the kernel is not able to recognize more than
4603 one at boot time without help; for details read the Ethernet-HOWTO,
4604 available from in http://www.linuxdoc.org/docs.html#howto .
4606 If you want to compile this code as a module ( = code which can be
4607 inserted in and removed from the running kernel whenever you want),
4608 say M here and read Documentation/modules.txt. The module will be
4615 The Packet protocol is used by applications which communicate
4616 directly with network devices without an intermediate network
4617 protocol implemented in the kernel, e.g. tcpdump. If you want them
4620 This driver is also available as a module called af_packet.o ( =
4621 code which can be inserted in and removed from the running kernel
4622 whenever you want). If you want to compile it as a module, say M
4623 here and read Documentation/modules.txt; if you use modprobe or
4624 kmod, you may also want to add "alias net-pf-17 af_packet" to
4629 Packet socket: mmapped IO
4631 If you say Y here, the Packet protocol driver will use an IO
4632 mechanism that results in faster communication.
4636 Kernel/User network link driver
4638 This driver allows for two-way communication between the kernel and
4639 user processes. It does so by creating a new socket family, PF_NETLINK.
4640 Over this socket, the kernel can send and receive datagrams carrying
4641 information. It is documented on many systems in netlink(7), a HOWTO is
4642 provided as well, for example on
4643 http://snafu.freedom.org/linux2.2/docs/netlink-HOWTO.html
4645 So far, the kernel uses this feature to publish some network related
4646 information if you say Y to "Routing messages", below. You also need
4647 to say Y here if you want to use arpd, a daemon that helps keep the
4648 internal ARP cache (a mapping between IP addresses and hardware
4649 addresses on the local network) small. The ethertap device, which
4650 lets user space programs read and write raw Ethernet frames, also
4651 needs the network link driver.
4657 If you say Y here, userspace programs can receive some network
4658 related routing information over the netlink. 'rtmon', supplied
4659 with the iproute2 package (ftp://ftp.inr.ac.ru), can read and
4660 interpret this data. Information sent to the kernel over this link
4663 Netlink device emulation
4665 This option will be removed soon. Any programs that want to use
4666 character special nodes like /dev/tap0 or /dev/route (all with major
4667 number 36) need this option, and need to be rewritten soon to use
4668 the real netlink socket.
4669 This is a backward compatibility option, choose Y for now.
4671 Asynchronous Transfer Mode (ATM)
4673 ATM is a high-speed networking technology for Local Area Networks
4674 and Wide Area Networks. It uses a fixed packet size and is
4675 connection oriented, allowing for the negotiation of minimum
4676 bandwidth requirements.
4678 In order to participate in an ATM network, your Linux box needs an
4679 ATM networking card. If you have that, say Y here and to the driver
4680 of your ATM card below.
4682 Note that you need a set of user-space programs to actually make use
4683 of ATM. See the file Documentation/networking/atm.txt for further
4686 Classical IP over ATM
4688 Classical IP over ATM for PVCs and SVCs, supporting InARP and
4689 ATMARP. If you want to communication with other IP hosts on your ATM
4690 network, you will typically either say Y here or to "LAN Emulation
4693 Do NOT send ICMP if no neighbour
4694 CONFIG_ATM_CLIP_NO_ICMP
4695 Normally, an "ICMP host unreachable" message is sent if a neighbour
4696 cannot be reached because there is no VC to it in the kernel's
4697 ATMARP table. This may cause problems when ATMARP table entries are
4698 briefly removed during revalidation. If you say Y here, packets to
4699 such neighbours are silently discarded instead.
4701 LAN Emulation (LANE) support
4703 LAN Emulation emulates services of existing LANs across an ATM
4704 network. Besides operating as a normal ATM end station client, Linux
4705 LANE client can also act as an proxy client bridging packets between
4706 ELAN and Ethernet segments. You need LANE if you want to try MPOA.
4708 Multi-Protocol Over ATM (MPOA) support
4710 Multi-Protocol Over ATM allows ATM edge devices such as routers,
4711 bridges and ATM attached hosts establish direct ATM VCs across
4712 subnetwork boundaries. These shortcut connections bypass routers
4713 enhancing overall network performance.
4717 ATM over TCP driver. Useful mainly for development and for
4718 experiments. If unsure, say N.
4720 Efficient Networks ENI155P
4722 Driver for the Efficient Networks ENI155p series and SMC ATM
4723 Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
4724 2MB on-board RAM (Efficient calls them "C" and "S", respectively),
4725 and the FPGA and the ASIC Tonga versions of the board are supported.
4726 The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
4729 This driver is also available as a module. If you want to compile
4730 it as a module, say M here and read Documentation/modules.txt. The
4731 module will be called eni.o.
4733 Enable extended debugging
4734 CONFIG_ATM_ENI_DEBUG
4735 Extended debugging records various events and displays that list
4736 when an inconsistency is detected. This mechanism is faster than
4737 generally using printks, but still has some impact on performance.
4738 Note that extended debugging may create certain race conditions
4739 itself. Enable this ONLY if you suspect problems with the driver.
4741 Fine-tune burst settings
4742 CONFIG_ATM_ENI_TUNE_BURST
4743 In order to obtain good throughput, the ENI NIC can transfer
4744 multiple words of data per PCI bus access cycle. Such a multi-word
4745 transfer is called a burst.
4747 The default settings for the burst sizes are suitable for most PCI
4748 chipsets. However, in some cases, large bursts may overrun buffers
4749 in the PCI chipset and cause data corruption. In such cases, large
4750 bursts must be disabled and only (slower) small bursts can be used.
4751 The burst sizes can be set independently in the send (TX) and
4752 receive (RX) direction.
4754 Note that enabling many different burst sizes in the same direction
4755 may increase the cost of setting up a transfer such that the
4756 resulting throughput is lower than when using only the largest
4757 available burst size.
4759 Also, sometimes larger bursts lead to lower throughput, e.g. on an
4760 Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
4761 when going from 8W to 16W bursts.
4763 Enable 16W TX bursts (discouraged)
4764 CONFIG_ATM_ENI_BURST_TX_16W
4765 Burst sixteen words at once in the send direction. This may work
4766 with recent PCI chipsets, but is known to fail with older chipsets.
4768 Enable 8W TX bursts (recommended)
4769 CONFIG_ATM_ENI_BURST_TX_8W
4770 Burst eight words at once in the send direction. This is the default
4773 Enable 4W TX bursts (optional)
4774 CONFIG_ATM_ENI_BURST_TX_4W
4775 Burst four words at once in the send direction. You may want to try
4776 this if you have disabled 8W bursts. Enabling 4W if 8W is also set
4777 may or may not improve throughput.
4779 Enable 2W TX bursts (optional)
4780 CONFIG_ATM_ENI_BURST_TX_2W
4781 Burst two words at once in the send direction. You may want to try
4782 this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
4783 are also set may or may not improve throughput.
4785 Enable 16W RX bursts (discouraged)
4786 CONFIG_ATM_ENI_BURST_RX_16W
4787 Burst sixteen words at once in the receive direction. This may work
4788 with recent PCI chipsets, but is known to fail with older chipsets.
4790 Enable 8W RX bursts (discouraged)
4791 CONFIG_ATM_ENI_BURST_RX_8W
4792 Burst eight words at once in the receive direction. This may work
4793 with recent PCI chipsets, but is known to fail with older chipsets,
4794 such as the Intel Neptune series.
4796 Enable 4W RX bursts (recommended)
4797 CONFIG_ATM_ENI_BURST_RX_4W
4798 Burst four words at once in the receive direction. This is the
4799 default setting. Enabling 4W if 8W is also set may or may not
4802 Enable 2W RX bursts (optional)
4803 CONFIG_ATM_ENI_BURST_RX_2W
4804 Burst two words at once in the receive direction. You may want to
4805 try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
4806 8W are also set may or may not improve throughput.
4808 ZeitNet ZN1221/ZN1225
4810 Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
4813 This driver is also available as a module. If you want to compile
4814 it as a module, say M here and read Documentation/modules.txt. The
4815 module will be called zatm.o.
4817 Enable extended debugging
4818 CONFIG_ATM_ZATM_DEBUG
4819 Extended debugging records various events and displays that list
4820 when an inconsistency is detected. This mechanism is faster than
4821 generally using printks, but still has some impact on performance.
4822 Note that extended debugging may create certain race conditions
4823 itself. Enable this ONLY if you suspect problems with the driver.
4825 Enable usec resolution timestamps
4826 CONFIG_ATM_ZATM_EXACT_TS
4827 The uPD98401 SAR chip supports a high-resolution timer (approx. 30
4828 MHz) that is used for very accurate reception timestamps. Because
4829 that timer overflows after 140 seconds, and also to avoid timer
4830 drift, time measurements need to be periodically synchronized with
4831 the normal system time. Enabling this feature will add some general
4832 overhead for timer synchronization and also per-packet overhead for
4835 IDT 77201/11 (NICStAR) (ForeRunnerLE)
4837 The NICStAR chipset family is used in a large number of ATM NICs for
4838 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
4839 series. Say Y if you have one of those.
4841 This driver is also available as a module. If you want to compile
4842 it as a module, say M here and read Documentation/modules.txt. The
4843 module will be called nicstar.o.
4845 ForeRunner LE155 PHYsical layer
4846 CONFIG_ATM_NICSTAR_USE_SUNI
4847 Support for the S-UNI and compatible PHYsical layer chips. These are
4848 found in most 155Mbps NICStAR based ATM cards, namely in the
4849 ForeRunner LE155 cards. This driver provides detection of cable
4850 removal and reinsertion and provides some statistics. This driver
4851 doesn't have removal capability when compiled as a module, so if you
4852 need that capability don't include S-UNI support (it's not needed to
4853 make the card work).
4855 ForeRunner LE25 PHYsical layer
4856 CONFIG_ATM_NICSTAR_USE_IDT77105
4857 Support for the PHYsical layer chip in ForeRunner LE25 cards. In
4858 addition to cable removal/reinsertion detection, this driver allows
4859 you to control the loopback mode of the chip via a dedicated IOCTL.
4860 This driver is required for proper handling of temporary carrier
4861 loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
4863 Madge Ambassador (Collage PCI 155 Server)
4864 CONFIG_ATM_AMBASSADOR
4865 This is a driver for ATMizer based ATM card produced by Madge
4866 Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
4867 here if you have one of these cards.
4869 Enable debugging messages
4870 CONFIG_ATM_AMBASSADOR_DEBUG
4871 Somewhat useful debugging messages are available. The choice of
4872 messages is controlled by a bitmap. This may be specified as a
4873 module argument (kernel command line argument as well?), changed
4874 dynamically using an ioctl (not yet) or changed by sending the
4875 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
4876 drivers/atm/ambassador.h for the meanings of the bits in the mask.
4878 When active, these messages can have a significant impact on the
4879 speed of the driver, and the size of your syslog files! When
4880 inactive, they will have only a modest impact on performance.
4882 Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
4884 This is a driver for the Horizon chipset ATM adapter cards once
4885 produced by Madge Networks Ltd. Say Y (or M to compile as a module
4886 named horizon.o) here if you have one of these cards.
4888 Enable debugging messages
4889 CONFIG_ATM_HORIZON_DEBUG
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 (not yet) or changed by sending the
4894 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
4895 drivers/atm/horizon.h 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 Interphase ATM PCI x575/x525/x531
4903 This is a driver for the Interphase (i)ChipSAR adapter cards
4904 which include a variety of variants in term of the size of the
4905 control memory (128K-1KVC, 512K-4KVC), the size of the packet
4906 memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
4907 UTP155, UTP25, DS3 and E3). Go to:
4908 www.iphase.com/products/ClassSheet.cfm?ClassID=ATM
4909 for more info about the cards. Say Y (or M to compile as a module
4910 named iphase.o) here if you have one of these cards.
4912 See the file Documentation/networking/iphase.txt for further
4915 Enable debugging messages
4917 Somewhat useful debugging messages are available. The choice of
4918 messages is controlled by a bitmap. This may be specified as a
4919 module argument (kernel command line argument as well?), changed
4920 dynamically using an ioctl (Get the debug utility, iadbg, from
4921 ftp.iphase.com/pub/atm/pci). See the file drivers/atm/iphase.h
4922 for the meanings of the bits in the mask.
4924 When active, these messages can have a significant impact on the
4925 speed of the driver, and the size of your syslog files! When
4926 inactive, they will have only a modest impact on performance.
4928 Linux telephony support
4930 Say Y here if you have a telephony card, which for example allows
4931 you to use a regular phone for voice-over-IP applications.
4933 Note: this has nothing to do with modems. You do not need to say Y
4934 here in order to be able to use a modem under Linux.
4936 This support is also available as a module. If you want to compile
4937 it as a module, say M here and read Documentation/modules.txt. The
4938 module will be called phonedev.o.
4940 Compaq Smart Array support
4941 CONFIG_BLK_CPQ_CISS_DA
4942 This is the driver for Compaq Smart Array controllers.
4943 Everyone using these boards should say Y here.
4944 See "linux/Documentation/cciss.txt" for the current list of
4945 boards supported by this driver, and for further information
4946 on the use of this driver.
4948 QuickNet Internet LineJack/PhoneJack support
4950 Say M if you have a telephony card manufactured by Quicknet
4951 Technologies, Inc. These include the Internet PhoneJACK and
4952 Internet LineJACK Telephony Cards. You will get a module called
4955 For the ISA versions of these products, you can configure the
4956 cards using the isapnp tools (pnpdump/isapnp) or you can use the
4957 isapnp support. Please read Documentation/telephony/ixj.txt.
4959 For more information on these cards, see Quicknet's web site at:
4960 http://www.quicknet.net/ .
4962 If you do not have any Quicknet telephony cards, you can safely
4965 FORE Systems 200E-series
4966 CONFIG_ATM_FORE200E_MAYBE
4967 This is a driver for the FORE Systems 200E-series ATM adapter
4968 cards. It simultaneously supports PCA-200E and SBA-200E models
4969 on PCI and SBUS hosts. Say Y (or M to compile as a module
4970 named fore_200e.o) here if you have one of these ATM adapters.
4972 Note that the driver will actually be compiled only if you
4973 additionally enable the support for PCA-200E and/or SBA-200E
4976 See the file Documentation/networking/fore200e.txt for further
4979 Enable PCA-200E card support on PCI-based hosts
4980 CONFIG_ATM_FORE200E_PCA
4981 Say Y here if you want your PCA-200E cards to be probed.
4983 Use default PCA-200E firmware
4984 CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
4985 Use the default PCA-200E firmware data shipped with the driver.
4987 Normal users do not have to deal with the firmware stuff, so
4988 they should say Y here.
4990 Pathname of user-supplied binary firmware
4991 CONFIG_ATM_FORE200E_PCA_FW
4992 This defines the pathname of an alternative PCA-200E binary
4993 firmware image supplied by the user. This pathname may be
4994 absolute or relative to the drivers/atm directory.
4996 The driver comes with an adequate firmware image, so normal users do
4997 not have to supply an alternative one. They just say Y to "Use
4998 default PCA-200E firmware" instead.
5000 Enable SBA-200E card support on SBUS-based hosts
5001 CONFIG_ATM_FORE200E_SBA
5002 Say Y here if you want your SBA-200E cards to be probed.
5004 Use default SBA-200E firmware
5005 CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
5006 Use the default SBA-200E firmware data shipped with the driver.
5008 Normal users do not have to deal with the firmware stuff, so
5009 they should say Y here.
5011 Pathname of user-supplied binary firmware
5012 CONFIG_ATM_FORE200E_SBA_FW
5013 This defines the pathname of an alternative SBA-200E binary
5014 firmware image supplied by the user. This pathname may be
5015 absolute or relative to the drivers/atm directory.
5017 The driver comes with an adequate firmware image, so normal users do
5018 not have to supply an alternative one. They just say Y to "Use
5019 default SBA-200E firmware", above.
5021 Maximum number of tx retries
5022 CONFIG_ATM_FORE200E_TX_RETRY
5023 Specifies the number of times the driver attempts to transmit
5024 a message before giving up, if the transmit queue of the ATM card
5025 is transiently saturated.
5027 Saturation of the transmit queue may occur only under extreme
5028 conditions, e.g. when a fast host continuously submits very small
5029 frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
5031 Note that under common conditions, it is unlikely that you encounter
5032 a saturation of the transmit queue, so the retry mechanism never
5035 Debugging level (0-3)
5036 CONFIG_ATM_FORE200E_DEBUG
5037 Specifies the level of debugging messages issued by the driver.
5038 The verbosity of the driver increases with the value of this
5041 When active, these messages can have a significant impact on
5042 the performances of the driver, and the size of your syslog files!
5043 Keep the debugging level to 0 during normal operations.
5047 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
5048 any other SCSI device under Linux, say Y and make sure that you know
5049 the name of your SCSI host adapter (the card inside your computer
5050 that "speaks" the SCSI protocol, also called SCSI controller),
5051 because you will be asked for it.
5053 You also need to say Y here if you want support for the parallel
5054 port version of the 100 MB IOMEGA ZIP drive.
5056 Please read the SCSI-HOWTO, available from
5057 http://www.linuxdoc.org/docs.html#howto . The
5058 SCSI-Programming-HOWTO contains information about how to add or
5059 remove an SCSI device from a running Linux machine without
5062 This driver is also available as a module ( = code which can be
5063 inserted in and removed from the running kernel whenever you want).
5064 The module will be called scsi_mod.o. If you want to compile it as a
5065 module, say M here and read Documentation/modules.txt and
5066 Documentation/scsi.txt. However, do not compile this as a module if
5067 your root file system (the one containing the directory /) is
5068 located on a SCSI device.
5072 If you want to use a SCSI hard disk or the SCSI or parallel port
5073 version of the IOMEGA ZIP drive under Linux, say Y and read the
5074 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
5075 http://www.linuxdoc.org/docs.html#howto . This is NOT for SCSI
5078 This driver is also available as a module ( = code which can be
5079 inserted in and removed from the running kernel whenever you want).
5080 The module will be called sd_mod.o. If you want to compile it as a
5081 module, say M here and read Documentation/modules.txt and
5082 Documentation/scsi.txt. Do not compile this driver as a module if
5083 your root file system (the one containing the directory /) is
5084 located on a SCSI disk. In this case, do not compile the driver for
5085 your SCSI host adapter (below) as a module either.
5088 CONFIG_SD_EXTRA_DEVS
5089 This controls the amount of additional space allocated in tables for
5090 drivers that are loaded as modules after the kernel is booted. In
5091 the event that the SCSI core itself was loaded as a module, this
5092 value is the number of additional disks that can be loaded after the
5093 first host driver is loaded.
5095 Admittedly this isn't pretty, but there are tons of race conditions
5096 involved with resizing the internal arrays on the fly. Someday this
5097 flag will go away, and everything will work automatically.
5099 If you don't understand what's going on, go with the default.
5103 If you want to use a SCSI tape drive under Linux, say Y and read the
5104 SCSI-HOWTO, available from
5105 http://www.linuxdoc.org/docs.html#howto , and
5106 drivers/scsi/README.st in the kernel source. This is NOT for SCSI
5109 This driver is also available as a module ( = code which can be
5110 inserted in and removed from the running kernel whenever you want).
5111 The module will be called st.o. If you want to compile it as a
5112 module, say M here and read Documentation/modules.txt and
5113 Documentation/scsi.txt .
5117 If you want to use a SCSI CDROM under Linux, say Y and read the
5118 SCSI-HOWTO and the CDROM-HOWTO at
5119 http://www.linuxdoc.org/docs.html#howto . Also make sure to say Y
5120 or M to "ISO 9660 CDROM file system support" later.
5122 This driver is also available as a module ( = code which can be
5123 inserted in and removed from the running kernel whenever you want).
5124 The module will be called sr_mod.o. If you want to compile it as a
5125 module, say M here and read Documentation/modules.txt and
5126 Documentation/scsi.txt .
5129 CONFIG_SR_EXTRA_DEVS
5130 This controls the amount of additional space allocated in tables for
5131 drivers that are loaded as modules after the kernel is booted. In
5132 the event that the SCSI core itself was loaded as a module, this
5133 value is the number of additional CDROMs that can be loaded after
5134 the first host driver is loaded.
5136 Admittedly this isn't pretty, but there are tons of race conditions
5137 involved with resizing the internal arrays on the fly. Someday this
5138 flag will go away, and everything will work automatically.
5140 If you don't understand what's going on, go with the default.
5142 Enable vendor-specific extensions (for SCSI CDROM)
5143 CONFIG_BLK_DEV_SR_VENDOR
5144 This enables the usage of vendor specific SCSI commands. This is
5145 required to support multisession CDs with old NEC/TOSHIBA cdrom
5146 drives (and HP Writers). If you have such a drive and get the first
5147 session only, try saying Y here; everybody else says N.
5149 SCSI generic support
5151 If you want to use SCSI scanners, synthesizers or CD-writers or just
5152 about anything having "SCSI" in its name other than hard disks,
5153 CDROMs or tapes, say Y here. These won't be supported by the kernel
5154 directly, so you need some additional software which knows how to
5155 talk to these devices using the SCSI protocol:
5157 For scanners, look at SANE (http://www.mostang.com/sane). For CD
5158 writer software look at cdrecord
5159 (http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html)
5160 and for burning a "disk at once": cdrdao
5161 (http://www.ping.de/sites/daneb/cdrdao.html). Cdparanoia is a high
5162 quality digital reader of audio CDs (http://www.xiph.org/paranoia).
5163 For other devices, it's possible that you'll have to write the
5164 driver software yourself. Please read the file
5165 Documentation/scsi-generic.txt for more information.
5167 If you want to compile this as a module ( = code which can be
5168 inserted in and removed from the running kernel whenever you want),
5169 say M here and read Documentation/modules.txt and
5170 Documentation/scsi.txt. The module will be called sg.o. If unsure,
5173 Debug new queueing code for SCSI
5174 CONFIG_SCSI_DEBUG_QUEUES
5175 This option turns on a lot of additional consistency checking for
5176 the new queueing code. This will adversely affect performance, but
5177 it is likely that bugs will be caught sooner if this is turned on.
5178 This will typically cause the kernel to panic if an error is
5179 detected, but it would have probably crashed if the panic weren't
5180 there. Comments/questions/problems to linux-scsi mailing list
5181 please. See http://www.andante.org/scsi_queue.html for more
5182 up-to-date information.
5184 Probe all LUNs on each SCSI device
5185 CONFIG_SCSI_MULTI_LUN
5186 If you have a SCSI device that supports more than one LUN (Logical
5187 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
5188 can say Y here to force the SCSI driver to probe for multiple LUNs.
5189 A SCSI device with multiple LUNs acts logically like multiple SCSI
5190 devices. The vast majority of SCSI devices have only one LUN, and
5191 so most people can say N here and should in fact do so, because it
5194 Verbose SCSI error reporting (kernel size +=12K)
5195 CONFIG_SCSI_CONSTANTS
5196 The error messages regarding your SCSI hardware will be easier to
5197 understand if you say Y here; it will enlarge your kernel by about
5198 12 KB. If in doubt, say Y.
5200 SCSI logging facility
5202 This turns on a logging facility that can be used to debug a number
5203 of SCSI related problems.
5205 If you say Y here, no logging output will appear by default, but you
5206 can enable logging by saying Y to "/proc file system support" and
5207 "Sysctl support" below and executing the command
5209 echo "scsi log token [level]" > /proc/scsi/scsi
5211 at boot time after the /proc file system has been mounted.
5213 There are a number of things that can be used for 'token' (you can
5214 find them in the source: drivers/scsi/scsi.c), and this allows you
5215 to select the types of information you want, and the level allows
5216 you to select the level of verbosity.
5218 If you say N here, it may be harder to track down some types of SCSI
5219 problems. If you say Y here your kernel will be somewhat larger, but
5220 there should be no noticeable performance impact as long as you have
5223 AdvanSys SCSI support
5224 CONFIG_SCSI_ADVANSYS
5225 This is a driver for all SCSI host adapters manufactured by
5226 AdvanSys. It is documented in the kernel source in
5227 drivers/scsi/advansys.c.
5229 This driver is also available as a module ( = code which can be
5230 inserted in and removed from the running kernel whenever you want).
5231 If you want to compile it as a module, say M here and read
5232 Documentation/modules.txt. The module will be called advansys.o.
5234 Adaptec AHA152X/2825 support
5236 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
5237 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
5238 must be manually specified in this case.
5240 It is explained in section 3.3 of the SCSI-HOWTO, available from
5241 http://www.linuxdoc.org/docs.html#howto . You might also want to
5242 read the file drivers/scsi/README.aha152x.
5244 This driver is also available as a module ( = code which can be
5245 inserted in and removed from the running kernel whenever you want).
5246 The module will be called aha152x.o. If you want to compile it as a
5247 module, say M here and read Documentation/modules.txt.
5249 Adaptec AHA1542 support
5251 This is support for a SCSI host adapter. It is explained in section
5252 3.4 of the SCSI-HOWTO, available from
5253 http://www.linuxdoc.org/docs.html#howto . Note that Trantor was
5254 purchased by Adaptec, and some former Trantor products are being
5255 sold under the Adaptec name. If it doesn't work out of the box, you
5256 may have to change some settings in drivers/scsi/aha1542.h.
5258 If you want to compile this as a module ( = code which can be
5259 inserted in and removed from the running kernel whenever you want),
5260 say M here and read Documentation/modules.txt. The module will be
5263 Adaptec AHA1740 support
5265 This is support for a SCSI host adapter. It is explained in section
5266 3.5 of the SCSI-HOWTO, available from
5267 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5268 of the box, you may have to change some settings in
5269 drivers/scsi/aha1740.h.
5271 This driver is also available as a module ( = code which can be
5272 inserted in and removed from the running kernel whenever you want).
5273 The module will be called aha1740.o. If you want to compile it as a
5274 module, say M here and read Documentation/modules.txt.
5276 Adaptec AIC7xxx chipset SCSI controller support
5278 This is support for the various aic7xxx based Adaptec SCSI
5279 controllers. These include the 274x EISA cards; 284x VLB cards;
5280 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
5281 motherboard based SCSI controllers from Adaptec. It does not support
5282 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
5283 support them. It does not support the 2920 cards from Adaptec that
5284 use the Future Domain SCSI controller chip. For those cards, you
5285 need the "Future Domain 16xx SCSI support" driver.
5287 In general, if the controller is based on an Adaptec SCSI controller
5288 chip from the aic777x series or the aic78xx series, this driver
5289 should work. The only exception is the 7810 which is specifically
5290 not supported (that's the RAID controller chip on the AAA-13x
5293 Note that the AHA2920 SCSI host adapter is *not* supported by this
5294 driver; choose "Future Domain 16xx SCSI support" instead if you have
5297 Information on the configuration options for this controller can be
5298 found by checking the help file for each of the available
5299 configuration options. You should read drivers/scsi/README.aic7xxx
5300 at a minimum before contacting the maintainer with any questions.
5301 The SCSI-HOWTO, available from
5302 http://www.linuxdoc.org/docs.html#howto , can also be of great
5305 If you want to compile this driver as a module ( = code which can be
5306 inserted in and removed from the running kernel whenever you want),
5307 say M here and read Documentation/modules.txt. The module will be
5310 Enable or Disable Tagged Command Queueing by default
5311 CONFIG_AIC7XXX_TCQ_ON_BY_DEFAULT
5312 This option causes the aic7xxx driver to attempt to use Tagged
5313 Command Queueing (TCQ) on all devices that claim to support it.
5315 TCQ is a feature of SCSI-2 which improves performance: the host
5316 adapter can send several SCSI commands to a device's queue even if
5317 previous commands haven't finished yet. Because the device is
5318 intelligent, it can optimize its operations (like head positioning)
5319 based on its own request queue. Not all devices implement this
5322 If you say Y here, you can still turn off TCQ on troublesome devices
5323 with the use of the tag_info boot parameter. See the file
5324 drivers/scsi/README.aic7xxx for more information on that and other
5325 aic7xxx setup commands. If this option is turned off, you may still
5326 enable TCQ on known good devices by use of the tag_info boot
5329 If you are unsure about your devices then it is safest to say N
5332 However, TCQ can increase performance on some hard drives by as much
5333 as 50% or more, so it is recommended that if you say N here, you
5334 should at least read the README.aic7xxx file so you will know how to
5335 enable this option manually should your drives prove to be safe in
5338 Conversely, certain drives are known to lock up or cause bus resets
5339 when TCQ is enabled on them. If you have a Western Digital
5340 Enterprise SCSI drive for instance, then don't even bother to enable
5341 TCQ on it as the drive will become unreliable, and it will actually
5344 Default number of TCQ commands per device
5345 CONFIG_AIC7XXX_CMDS_PER_DEVICE
5346 Specify the number of commands you would like to allocate per SCSI
5347 device when Tagged Command Queueing (TCQ) is enabled on that device.
5349 Reasonable figures are in the range of 8 to 24 commands per device,
5350 but depending on hardware could be increased or decreased from that
5351 figure. If the number is too high for any particular device, the
5352 driver will automatically compensate usually after only 10 minutes
5353 of uptime. It will not hinder performance if some of your devices
5354 eventually have their command depth reduced, but is a waste of
5355 memory if all of your devices end up reducing this number down to a
5356 more reasonable figure.
5358 NOTE: Certain very broken drives are known to lock up when given
5359 more commands than they like to deal with. Quantum Fireball drives
5360 are the most common in this category. For the Quantum Fireball
5361 drives it is suggested to use no more than 8 commands per device.
5365 Collect statistics to report in /proc
5366 CONFIG_AIC7XXX_PROC_STATS
5367 This option tells the driver to keep track of how many commands have
5368 been sent to each particular device and report that information to
5369 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
5370 the aic7xxx controller you want the information on. This adds a
5371 small amount of overhead to each and every SCSI command the aic7xxx
5372 driver handles, so if you aren't really interested in this
5373 information, it is best to leave it disabled. This will only work if
5374 you also say Y to "/proc file system support", below.
5378 Delay in seconds after SCSI bus reset
5379 CONFIG_AIC7XXX_RESET_DELAY
5380 This sets how long the driver will wait after resetting the SCSI bus
5381 before attempting to communicate with the devices on the SCSI bus
5382 again. This delay will be used during the reset phase at bootup time
5383 as well as after any reset that might occur during normal operation.
5384 Reasonable numbers range anywhere from 5 to 15 seconds depending on
5385 your devices. DAT tape drives are notorious for needing more time
5386 after a bus reset to be ready for the next command, but most hard
5387 drives and CD-ROM devices are ready in only a few seconds. This
5388 option has a maximum upper limit of 20 seconds to avoid bad
5389 interactions between the aic7xxx driver and the rest of the Linux
5390 kernel. The default value has been reduced to 5 seconds. If this
5391 doesn't work with your hardware, try increasing this value.
5393 IBM ServeRAID Support
5395 This is support for the IBM ServeRAID hardware RAID controllers.
5396 See http://www.developer.ibm.com/welcome/netfinity/serveraid.html
5397 for more information. If this driver does not work correctly
5398 without modification please contact the author by email at
5399 ipslinux@us.ibm.com.
5401 You can build this driver as a module ( = code which can be
5402 inserted in and removed from the running kernel whenever you want),
5403 but only a single instance may be loaded. If you want to compile it
5404 as a module, say M here and read Documentation/modules.txt. The
5405 module will be called ips.o.
5407 BusLogic SCSI support
5408 CONFIG_SCSI_BUSLOGIC
5409 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
5410 Adapters. Consult the SCSI-HOWTO, available from
5411 http://www.linuxdoc.org/docs.html#howto , and the files
5412 README.BusLogic and README.FlashPoint in drivers/scsi for more
5413 information. If this driver does not work correctly without
5414 modification, please contact the author, Leonard N. Zubkoff, by
5415 email to lnz@dandelion.com.
5417 You can also build this driver as a module ( = code which can be
5418 inserted in and removed from the running kernel whenever you want),
5419 but only a single instance may be loaded. If you want to compile it
5420 as a module, say M here and read Documentation/modules.txt. The
5421 module will be called BusLogic.o.
5423 Omit BusLogic SCSI FlashPoint support
5424 CONFIG_SCSI_OMIT_FLASHPOINT
5425 This option allows you to omit the FlashPoint support from the
5426 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
5427 substantial, so users of MultiMaster Host Adapters may wish to omit
5430 DMX3191D SCSI support
5431 CONFIG_SCSI_DMX3191D
5432 This is support for Domex DMX3191D SCSI Host Adapters.
5434 This driver is also available as a module ( = code which can be
5435 inserted in and removed from the running kernel whenever you want).
5436 The module will be called dmx3191d.o. If you want to compile it as a
5437 module, say M here and read Documentation/modules.txt.
5439 DTC3180/3280 SCSI support
5441 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
5442 the SCSI-HOWTO, available from
5443 http://www.linuxdoc.org/docs.html#howto , and the file
5444 drivers/scsi/README.dtc3x80.
5446 This driver is also available as a module ( = code which can be
5447 inserted in and removed from the running kernel whenever you want).
5448 The module will be called dtc.o. If you want to compile it as a
5449 module, say M here and read Documentation/modules.txt.
5451 EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
5452 CONFIG_SCSI_EATA_DMA
5453 This is support for the EATA-DMA protocol compliant SCSI Host
5454 Adapters like the SmartCache III/IV, SmartRAID controller families
5455 and the DPT PM2011B and PM2012B controllers.
5457 Note that this driver is obsolete; if you have one of the above SCSI
5458 Host Adapters, you should normally say N here and Y to "EATA
5459 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
5460 from http://www.linuxdoc.org/docs.html#howto .
5462 This driver is also available as a module ( = code which can be
5463 inserted in and removed from the running kernel whenever you want).
5464 The module will be called eata_dma.o. If you want to compile it as a
5465 module, say M here and read Documentation/modules.txt.
5467 EATA-PIO (old DPT PM2001, PM2012A) support
5468 CONFIG_SCSI_EATA_PIO
5469 This driver supports all EATA-PIO protocol compliant SCSI Host
5470 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
5471 host adapters could also use this driver but are discouraged from
5472 doing so, since this driver only supports hard disks and lacks
5473 numerous features. You might want to have a look at the SCSI-HOWTO,
5474 available from http://www.linuxdoc.org/docs.html#howto .
5476 If you want to compile this as a module ( = code which can be
5477 inserted in and removed from the running kernel whenever you want),
5478 say M here and read Documentation/modules.txt. The module will be
5481 UltraStor 14F/34F support
5483 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
5484 The source at drivers/scsi/u14-34f.c contains some information about
5485 this hardware. If the driver doesn't work out of the box, you may
5486 have to change some settings in drivers/scsi/u14-34f.c. Read the
5487 SCSI-HOWTO, available from
5488 http://www.linuxdoc.org/docs.html#howto . Note that there is also
5489 another driver for the same hardware: "UltraStor SCSI support",
5490 below. You should say Y to both only if you want 24F support as
5493 This driver is also available as a module ( = code which can be
5494 inserted in and removed from the running kernel whenever you want).
5495 The module will be called u14-34f.o. If you want to compile it as a
5496 module, say M here and read Documentation/modules.txt.
5498 enable elevator sorting
5499 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
5500 This option enables elevator sorting for all probed SCSI disks and
5501 CDROMs. It definitely reduces the average seek distance when doing
5502 random seeks, but this does not necessarily result in a noticeable
5503 performance improvement: your mileage may vary...
5505 The safe answer is N.
5507 maximum number of queued commands
5508 CONFIG_SCSI_U14_34F_MAX_TAGS
5509 This specifies how many SCSI commands can be maximally queued for
5510 each probed SCSI device. You should reduce the default value of 8
5511 only if you have disks with buggy or limited tagged command support.
5512 Minimum is 2 and maximum is 14. This value is also the window size
5513 used by the elevator sorting option above. The effective value used
5514 by the driver for each probed SCSI device is reported at boot time.
5516 Future Domain 16xx SCSI/AHA-2920A support
5517 CONFIG_SCSI_FUTURE_DOMAIN
5518 This is support for Future Domain's 16-bit SCSI host adapters
5519 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
5520 other adapters based on the Future Domain chipsets (Quantum
5521 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
5522 It is explained in section 3.7 of the SCSI-HOWTO, available from
5523 http://www.linuxdoc.org/docs.html#howto .
5525 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
5526 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
5527 controller support"). This Future Domain driver works with the older
5528 Adaptec AHA-2920A boards with a Future Domain chip on them.
5530 This driver is also available as a module ( = code which can be
5531 inserted in and removed from the running kernel whenever you want).
5532 The module will be called fdomain.o. If you want to compile it as a
5533 module, say M here and read Documentation/modules.txt.
5535 Future Domain MCS-600/700 SCSI support
5537 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
5538 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
5539 is identical to the MCS 700 and hence also supported by this driver.
5540 This driver also supports the Reply SB16/SCSI card (the SCSI part).
5541 It supports multiple adapters in the same system.
5543 This driver is also available as a module ( = code which can be
5544 inserted in and removed from the running kernel whenever you want).
5545 The module will be called fd_mcs.o. If you want to compile it as a
5546 module, say M here and read Documentation/modules.txt.
5548 Generic NCR5380/53c400 SCSI support
5549 CONFIG_SCSI_GENERIC_NCR5380
5550 This is the generic NCR family of SCSI controllers, not to be
5551 confused with the NCR 53c7 or 8xx controllers. It is explained in
5552 section 3.8 of the SCSI-HOWTO, available from
5553 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5554 of the box, you may have to change some settings in
5555 drivers/scsi/g_NCR5380.h.
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 g_NCR5380.o. If you want to compile it as
5560 a module, say M here and read Documentation/modules.txt.
5562 Enable NCR53c400 extensions
5563 CONFIG_SCSI_GENERIC_NCR53C400
5564 This enables certain optimizations for the NCR53c400 SCSI cards. You
5565 might as well try it out. Note that this driver will only probe for
5566 the Trantor T130B in its default configuration; you might have to
5567 pass a command line option to the kernel at boot time if it doesn't
5568 detect your card. See the file drivers/scsi/README.g_NCR5380 for
5571 NCR5380/53c400 mapping method (use Port for T130B)
5572 CONFIG_SCSI_G_NCR5380_PORT
5573 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
5574 port or memory mapped. You should know what you have. The most
5575 common card, Trantor T130B, uses port mapped mode.
5577 NCR53c7,8xx SCSI support
5578 CONFIG_SCSI_NCR53C7xx
5579 This is a driver for the 53c7 and 8xx NCR family of SCSI
5580 controllers, not to be confused with the NCR 5380 controllers. It is
5581 explained in section 3.8 of the SCSI-HOWTO, available from
5582 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5583 of the box, you may have to change some settings in
5584 drivers/scsi/53c7,8xx.h. Please read drivers/scsi/README.ncr53c7xx
5585 for the available boot time command line options.
5587 Note: there is another driver for the 53c8xx family of controllers
5588 ("NCR53C8XX SCSI support" below). If you want to use them both, you
5589 need to say M to both and build them as modules, but only one may be
5590 active at a time. If you have a 53c8xx board, it's better to use the
5593 This driver is also available as a module ( = code which can be
5594 inserted in and removed from the running kernel whenever you want).
5595 The module will be called 53c7,8xx.o. If you want to compile it as a
5596 module, say M here and read Documentation/modules.txt.
5598 always negotiate synchronous transfers
5599 CONFIG_SCSI_NCR53C7xx_sync
5600 In general, this is good; however, it is a bit dangerous since there
5601 are some broken SCSI devices out there. Take your chances. Safe bet
5604 allow FAST-SCSI [10MHz]
5605 CONFIG_SCSI_NCR53C7xx_FAST
5606 This will enable 10MHz FAST-SCSI transfers with your host
5607 adapter. Some systems have problems with that speed, so it's safest
5611 CONFIG_SCSI_NCR53C7xx_DISCONNECT
5612 This enables the disconnect/reconnect feature of the NCR SCSI
5613 controller. When you say Y here, a slow SCSI device will not lock
5614 the SCSI bus while processing a request, allowing simultaneous use
5615 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
5616 providing much better performance when using slow and fast SCSI
5617 devices at the same time. Some devices, however, do not operate
5618 properly with this option enabled, and will cause your SCSI system
5619 to hang, which might cause a system crash. The safe answer
5620 therefore is to say N.
5622 NCR53C8XX SCSI support
5623 CONFIG_SCSI_NCR53C8XX
5624 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
5625 of PCI-SCSI controllers. This driver supports parity checking,
5626 tagged command queuing and fast synchronous data transfers up to 80
5627 MB/s with wide FAST-40 LVD devices and controllers.
5629 Recent versions of the 53C8XX chips are better supported by the
5630 option "SYM53C8XX SCSI support", below.
5632 Note: there is yet another driver for the 53c8xx family of
5633 controllers ("NCR53c7,8xx SCSI support" above). If you want to use
5634 them both, you need to say M to both and build them as modules, but
5635 only one may be active at a time. If you have a 53c8xx board, you
5636 probably do not want to use the "NCR53c7,8xx SCSI support".
5638 Please read drivers/scsi/README.ncr53c8xx for more information.
5640 SYM53C8XX SCSI support
5641 CONFIG_SCSI_SYM53C8XX
5642 This driver supports all the features of recent 53C8XX chips (used
5643 in PCI SCSI controllers), notably the hardware phase mismatch
5644 feature of the SYM53C896.
5646 Older versions of the 53C8XX chips are not supported by this
5647 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
5648 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
5649 driver ("NCR53C8XX SCSI support" above) or configure both the
5650 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
5653 When both drivers are linked into the kernel, the SYM53C8XX driver
5654 is called first at initialization and you can use the 'excl=ioaddr'
5655 driver boot option to exclude attachment of adapters by the
5656 SYM53C8XX driver. For example, entering
5657 'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
5658 adapters at io address 0xb400 and 0xc000 from being attached by the
5659 SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
5660 The 'excl' option is also supported by the NCR53C8XX driver.
5662 Please read drivers/scsi/README.ncr53c8xx for more information.
5664 synchronous data transfers frequency
5665 CONFIG_SCSI_NCR53C8XX_SYNC
5666 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
5667 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers are
5668 respectively the maximum data transfer rates in mega-transfers per
5669 second for each class. For example, a FAST-20 Wide 16 device is able
5670 to transfer data at 20 million 16 bit packets per second for a total
5673 You may specify 0 if you want to only use asynchronous data
5674 transfers. This is the safest and slowest option. Otherwise, specify
5675 a value between 5 and 80, depending on the capability of your SCSI
5676 controller. The higher the number, the faster the data transfer.
5677 Note that 80 should normally be ok since the driver decreases the
5678 value automatically according to the controller's capabilities.
5680 Your answer to this question is ignored for controllers with NVRAM,
5681 since the driver will get this information from the user set-up. It
5682 also can be overridden using a boot setup option, as follows
5683 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
5684 for FAST-20 synchronous data transfer (20 mega-transfers per
5687 The normal answer therefore is not to go with the default but to
5688 select the maximum value 80 allowing the driver to use the maximum
5689 value supported by each controller. If this causes problems with
5690 your SCSI devices, you should come back and decrease the value.
5692 There is no safe option other than using good cabling, right
5693 terminations and SCSI conformant devices.
5696 CONFIG_SCSI_NCR53C8XX_IOMAPPED
5697 If you say Y here, the driver will use normal IO, as opposed to
5698 memory mapped IO. Memory mapped IO has less latency than normal IO
5699 and works for most Intel-based hardware. Under Linux/Alpha only
5700 normal IO is currently supported by the driver and so, this option
5701 has no effect on those systems.
5703 The normal answer therefore is N; try Y only if you encounter SCSI
5706 not allow targets to disconnect
5707 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
5708 This option is only provided for safety if you suspect some SCSI
5709 device of yours to not support properly the target-disconnect
5710 feature. In that case, you would say Y here. In general however, to
5711 not allow targets to disconnect is not reasonable if there is more
5712 than 1 device on a SCSI bus. The normal answer therefore is N.
5714 default tagged command queue depth
5715 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
5716 "Tagged command queuing" is a feature of SCSI-2 which improves
5717 performance: the host adapter can send several SCSI commands to a
5718 device's queue even if previous commands haven't finished yet.
5719 Because the device is intelligent, it can optimize its operations
5720 (like head positioning) based on its own request queue. Some SCSI
5721 devices don't implement this properly; if you want to disable this
5722 feature, enter 0 or 1 here (it doesn't matter which).
5724 The default value is 8 and should be supported by most hard disks.
5725 This value can be overridden from the boot command line using the
5726 'tags' option as follows (example):
5727 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
5728 4, set queue depth to 16 for target 2 and target 3 on controller 0
5729 and set queue depth to 10 for target 0 / lun 2 on controller 1.
5731 The normal answer therefore is to go with the default 8 and to use
5732 a boot command line option for devices that need to use a different
5733 command queue depth.
5735 There is no safe option other than using good SCSI devices.
5737 maximum number of queued commands
5738 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
5739 This option allows you to specify the maximum number of commands
5740 that can be queued to any device, when tagged command queuing is
5741 possible. The default value is 32. Minimum is 2, maximum is 64.
5742 Modern hard disks are able to support 64 tags and even more, but
5743 do not seem to be faster when more than 32 tags are being used.
5745 So, the normal answer here is to go with the default value 32 unless
5746 you are using very large hard disks with large cache (>= 1 MB) that
5747 are able to take advantage of more than 32 tagged commands.
5749 There is no safe option and the default answer is recommended.
5751 assume boards are SYMBIOS compatible (EXPERIMENTAL)
5752 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
5753 This option allows you to enable some features depending on GPIO
5754 wiring. These General Purpose Input/Output pins can be used for
5755 vendor specific features or implementation of the standard SYMBIOS
5756 features. Genuine SYMBIOS controllers use GPIO0 in output for
5757 controller LED and GPIO3 bit as a flag indicating
5758 singled-ended/differential interface. The Tekram DC-390U/F boards
5759 uses a different GPIO wiring.
5761 Your answer to this question is ignored if all your controllers have
5762 NVRAM, since the driver is able to detect the board type from the
5765 If all the controllers in your system are genuine SYMBIOS boards or
5766 use BIOS and drivers from SYMBIOS, you would want to say Y here,
5767 otherwise N. N is the safe answer.
5769 enable profiling statistics gathering
5770 CONFIG_SCSI_NCR53C8XX_PROFILE
5771 This option allows you to enable profiling information gathering.
5772 These statistics are not very accurate due to the low frequency
5773 of the kernel clock (100 Hz on i386) and have performance impact
5774 on systems that use very fast devices.
5776 The normal answer therefore is N.
5778 include support for the NCR PQS/PDS SCSI card
5779 CONFIG_SCSI_NCR53C8XX_PQS_PDS
5780 Say Y here if you have a special SCSI adapter produced by NCR
5781 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
5782 this if you do not have one of these adapters. However, since this
5783 device is detected as a specific PCI device, this option is quite
5786 The common answer here is N, but answering Y is safe.
5790 This is support for the IBM SCSI adapter found in many of the PS/2
5791 series computers. These machines have an MCA bus, so you need to
5792 answer Y to "MCA support" as well and read Documentation/mca.txt.
5794 If the adapter isn't found during boot (a common problem for models
5795 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
5796 option, where <pun> is the id of the SCSI subsystem (usually 7, but
5797 if that doesn't work check your reference diskette). Owners of model
5798 95 with a LED-matrix-display can in addition activate some activity
5799 info like under OS/2, but more informative, by setting
5800 'ibmmcascsi=display' as an additional kernel parameter. Try "man
5801 bootparam" or see the documentation of your boot loader about how to
5802 pass options to the kernel.
5804 If you want to compile this driver as a module ( = code which can be
5805 inserted in and removed from the running kernel whenever you want),
5806 say M here and read Documentation/modules.txt. The module will be
5810 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
5811 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
5812 are assigned to the drive letters, starting with the lowest SCSI-id
5813 (physical number -- pun) to be drive C:, as seen from DOS and
5814 similar operating systems. When looking into papers describing the
5815 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
5816 The SCSI-standard follows a hardware-hierarchy which says that id 7
5817 has the highest priority and id 0 the lowest. Therefore, the host
5818 adapters are still today everywhere placed as SCSI-id 7 by default.
5819 In the SCSI-standard, the drive letters express the priority of the
5820 disk. C: should be the hard disk, or a partition on it, with the
5821 highest priority. This must therefore be the disk with the highest
5822 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
5823 original definition of the SCSI-standard as also industrial- and
5824 process-control-machines, like VME-CPUs running under realtime-OSs
5825 (e.g. LynxOS, OS9) do.
5827 If you like to run Linux on your MCA-machine with the same
5828 assignment of hard disks as seen from e.g. DOS or OS/2 on your
5829 machine, which is in addition conformant to the SCSI-standard, you
5830 must say Y here. This is also necessary for MCA-Linux users who want
5831 to keep downward compatibility to older releases of the
5832 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
5835 If you like to have the lowest SCSI-id assigned as drive C:, as
5836 modern SCSI-BIOSes do, which does not conform to the standard, but
5837 is widespread and common in the PC-world of today, you must say N
5838 here. If unsure, say Y.
5840 Reset SCSI-devices at boot time
5841 CONFIG_IBMMCA_SCSI_DEV_RESET
5842 By default, SCSI-devices are reset when the machine is powered on.
5843 However, some devices exist, like special-control-devices,
5844 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
5845 not reset when switched on. If you say Y here, each device connected
5846 to your SCSI-bus will be issued a reset-command after it has been
5847 probed, while the kernel is booting. This may cause problems with
5848 more modern devices, like hard disks, which do not appreciate these
5849 reset commands, and can cause your system to hang. So say Y only if
5850 you know that one of your older devices needs it; N is the safe
5853 NCR 53C9x MCA support
5854 CONFIG_SCSI_MCA_53C9X
5855 Some Microchannel machines, notably the NCR 35xx line, use a SCSI
5856 controller based on the NCR 53C94. This driver will allow use of
5857 the controller on the 3550, and very possibly others.
5859 If you want to compile this as a module (= code which can be
5860 inserted and removed from the running kernel whenever you want), say
5861 M here and read Documentation/modules.txt. The module will be called
5864 Always IN2000 SCSI support
5866 This is support for an ISA bus SCSI host adapter. You'll find more
5867 information in drivers/scsi/in2000.readme. If it doesn't work out of
5868 the box, you may have to change the jumpers for IRQ or address
5871 If you want to compile this as a module ( = code which can be
5872 inserted in and removed from the running kernel whenever you want),
5873 say M here and read Documentation/modules.txt. The module will be
5876 Initio 91XXU(W) SCSI support
5878 This is support for the Initio 91XXU(W) SCSI host adapter. Please
5879 read the SCSI-HOWTO, available from
5880 http://www.linuxdoc.org/docs.html#howto .
5882 If you want to compile this as a module ( = code which can be
5883 inserted in and removed from the running kernel whenever you want),
5884 say M here and read Documentation/modules.txt. The module will be
5889 This is support for a SCSI host adapter. It is explained in section
5890 3.10 of the SCSI-HOWTO, available from
5891 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
5892 of the box, you may have to change some settings in
5893 drivers/scsi/pas16.h.
5895 This driver is also available as a module ( = code which can be
5896 inserted in and removed from the running kernel whenever you want).
5897 The module will be called pas16.o. If you want to compile it as a
5898 module, say M here and read Documentation/modules.txt.
5900 Initio INI-A100U2W SCSI support
5902 This is support for the Initio INI-A100U2W SCSI host adapter. Please
5903 read the SCSI-HOWTO, available from
5904 http://www.linuxdoc.org/docs.html#howto .
5906 If you want to compile this as a module ( = code which can be
5907 inserted in and removed from the running kernel whenever you want),
5908 say M here and read Documentation/modules.txt. The module will be
5913 This is support for the PCI2000I EIDE interface card which acts as a
5914 SCSI host adapter. Please read the SCSI-HOWTO, available from
5915 http://www.linuxdoc.org/docs.html#howto .
5917 This driver is also available as a module called pci2000.o ( = code
5918 which can be inserted in and removed from the running kernel
5919 whenever you want). If you want to compile it as a module, say M
5920 here and read Documentation/modules.txt.
5923 CONFIG_SCSI_PCI2220I
5924 This is support for the PCI2220i EIDE interface card which acts as a
5925 SCSI host adapter. Please read the SCSI-HOWTO, available from
5926 http://www.linuxdoc.org/docs.html#howto .
5928 This driver is also available as a module called pci2220i.o ( = code
5929 which can be inserted in and removed from the running kernel
5930 whenever you want). If you want to compile it as a module, say M
5931 here and read Documentation/modules.txt.
5935 This is support for the PSI240i EIDE interface card which acts as a
5936 SCSI host adapter. Please read the SCSI-HOWTO, available from
5937 http://www.linuxdoc.org/docs.html#howto .
5939 This driver is also available as a module called psi240i.o ( = code
5940 which can be inserted in and removed from the running kernel
5941 whenever you want). If you want to compile it as a module, say M
5942 here and read Documentation/modules.txt.
5944 Qlogic FAS SCSI support
5945 CONFIG_SCSI_QLOGIC_FAS
5946 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
5947 FastSCSI! cards as well as any other card based on the FASXX chip
5948 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
5950 This driver does NOT support the PCI versions of these cards. The
5951 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
5952 SCSI support"), below.
5954 Information about this driver is contained in
5955 drivers/scsi/README.qlogicfas. You should also read the SCSI-HOWTO,
5956 available from http://www.linuxdoc.org/docs.html#howto .
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 qlogicfas.o. If you want to compile it as
5961 a module, say M here and read Documentation/modules.txt.
5963 Qlogic ISP SCSI support (EXPERIMENTAL)
5964 CONFIG_SCSI_QLOGIC_ISP
5965 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
5966 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
5967 card is supported by the "AM53/79C974 PCI SCSI" driver).
5969 If you say Y here, make sure to choose "BIOS" at the question "PCI
5972 Please read the file drivers/scsi/README.qlogicisp. You should also
5973 read the SCSI-HOWTO, available from
5974 http://www.linuxdoc.org/docs.html#howto .
5976 This driver is also available as a module ( = code which can be
5977 inserted in and removed from the running kernel whenever you want).
5978 The module will be called qlogicisp.o. If you want to compile it as
5979 a module, say M here and read Documentation/modules.txt.
5981 Qlogic ISP FC SCSI support
5982 CONFIG_SCSI_QLOGIC_FC
5983 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
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 qlogicfc.o. If you want to compile it as
5988 a module, say M here and read Documentation/modules.txt.
5990 Qlogic QLA 1280 SCSI support
5991 CONFIG_SCSI_QLOGIC_1280
5992 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
5994 This driver is also available as a module ( = code which can be
5995 inserted in and removed from the running kernel whenever you want).
5996 The module will be called qla1280.o. If you want to compile it as
5997 a module, say M here and read Documentation/modules.txt.
5999 Seagate ST-02 and Future Domain TMC-8xx SCSI support
6001 These are 8-bit SCSI controllers; the ST-01 is also supported by
6002 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
6003 available from http://www.linuxdoc.org/docs.html#howto . If it
6004 doesn't work out of the box, you may have to change some settings in
6005 drivers/scsi/seagate.h.
6007 This driver is also available as a module ( = code which can be
6008 inserted in and removed from the running kernel whenever you want).
6009 The module will be called seagate.o. If you want to compile it as a
6010 module, say M here and read Documentation/modules.txt.
6012 Trantor T128/T128F/T228 SCSI support
6014 This is support for a SCSI host adapter. It is explained in section
6015 3.11 of the SCSI-HOWTO, available from
6016 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
6017 of the box, you may have to change some settings in
6018 drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
6019 some former Trantor products are being sold under the Adaptec name.
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 t128.o. If you want to compile it as a
6024 module, say M here and read Documentation/modules.txt.
6026 UltraStor SCSI support
6027 CONFIG_SCSI_ULTRASTOR
6028 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
6029 adapter family. This driver is explained in section 3.12 of the
6030 SCSI-HOWTO, available from
6031 http://www.linuxdoc.org/docs.html#howto . If it doesn't work out
6032 of the box, you may have to change some settings in
6033 drivers/scsi/ultrastor.h.
6035 Note that there is also another driver for the same hardware:
6036 "UltraStor 14F/34F support", above.
6038 If you want to compile this as a module ( = code which can be
6039 inserted in and removed from the running kernel whenever you want),
6040 say M here and read Documentation/modules.txt. The module will be
6043 7000FASST SCSI support
6044 CONFIG_SCSI_7000FASST
6045 This driver supports the Western Digital 7000 SCSI host adapter
6046 family. Some information is in the source: drivers/scsi/wd7000.c.
6048 This driver is also available as a module ( = code which can be
6049 inserted in and removed from the running kernel whenever you
6050 want). The module will be called wd7000.o. If you want to compile it
6051 as a module, say M here and read Documentation/modules.txt.
6055 This driver supports the ACARD 870U/W SCSI host adapter.
6057 This driver is also available as a module ( = code which can be
6058 inserted in and removed from the running kernel whenever you want).
6059 The module will be called atp870u.o. If you want to compile it as a
6060 module, say M here and read Documentation/modules.txt.
6062 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
6064 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
6065 ISA and all EISA i/o addresses are probed looking for the "EATA"
6066 signature. If you chose "BIOS" at the question "PCI access mode",
6067 the addresses of all the PCI SCSI controllers reported by the PCI
6068 subsystem are probed as well.
6070 You want to read the start of drivers/scsi/eata.c and the
6071 SCSI-HOWTO, available from
6072 http://www.linuxdoc.org/docs.html#howto .
6074 Note that there is also another driver for the same hardware
6075 available: "EATA-DMA support". You should say Y to only one of them.
6077 If you want to compile this as a module ( = code which can be
6078 inserted in and removed from the running kernel whenever you want),
6079 say M here and read Documentation/modules.txt. The module will be
6082 enable tagged command queuing
6083 CONFIG_SCSI_EATA_TAGGED_QUEUE
6084 This is a feature of SCSI-2 which improves performance: the host
6085 adapter can send several SCSI commands to a device's queue even if
6086 previous commands haven't finished yet. Most EATA adapters negotiate
6087 this feature automatically with the device, even if your answer is
6088 N. The safe answer is N.
6090 enable elevator sorting
6091 CONFIG_SCSI_EATA_LINKED_COMMANDS
6092 This option enables elevator sorting for all probed SCSI disks and
6093 CDROMs. It definitely reduces the average seek distance when doing
6094 random seeks, but this does not necessarily result in a noticeable
6095 performance improvement: your mileage may vary...
6096 The safe answer is N.
6098 maximum number of queued commands
6099 CONFIG_SCSI_EATA_MAX_TAGS
6100 This specifies how many SCSI commands can be maximally queued for
6101 each probed SCSI device. You should reduce the default value of 16
6102 only if you have disks with buggy or limited tagged command support.
6103 Minimum is 2 and maximum is 62. This value is also the window size
6104 used by the elevator sorting option above. The effective value used
6105 by the driver for each probed SCSI device is reported at boot time.
6107 NCR53c406a SCSI support
6108 CONFIG_SCSI_NCR53C406A
6109 This is support for the NCR53c406a SCSI host adapter. For user
6110 configurable parameters, check out drivers/scsi/NCR53c406.c in the
6111 kernel source. Also read the SCSI-HOWTO, available from
6112 http://www.linuxdoc.org/docs.html#howto .
6114 If you want to compile this driver as a module ( = code which can be
6115 inserted in and removed from the running kernel whenever you want),
6116 say M here and read Documentation/modules.txt. The module will be
6119 Symbios Logic sym53c416 support
6120 CONFIG_SCSI_SYM53C416
6121 This is support for the sym53c416 SCSI host adapter, the SCSI
6122 adapter that comes with some HP scanners. This driver requires that
6123 the sym53c416 is configured first using some sort of pnp
6124 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
6125 are using isapnp then you need to compile this driver as a module
6126 and then load it using insmod after isapnp has run. The parameters
6127 of the configured card(s) should be passed to the driver. The format
6130 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
6132 There is support for up to four adapters. If you want to compile
6133 this driver as a module ( = code which can be inserted in and
6134 removed from the running kernel whenever you want), say M here and
6135 read Documentation/modules.txt. The module will be called
6138 Simple 53c710 SCSI support (Compaq, NCR machines)
6140 This is a simple driver for NCR53c710 based SCSI host adapters.
6142 More complex drivers for this chip are available ("NCR53c7,8xx SCSI
6143 support", above), but they require that the scsi chip be able to do
6144 DMA block moves between memory and on-chip registers, which can
6145 cause problems under certain conditions. This driver is designed to
6146 avoid these problems and is intended to work with any Intel machines
6147 using 53c710 chips, including various Compaq and NCR machines.
6149 Please read the comments at the top of the file
6150 drivers/scsi/sim710.c for more information.
6152 If you want to compile this driver as a module ( = code which can be
6153 inserted in and removed from the running kernel whenever you want),
6154 say M here and read Documentation/modules.txt. The module will be
6157 Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
6159 This driver supports PCI SCSI host adapters based on the Am53C974A
6160 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
6161 PCscsi/PCnet (Am53/79C974) solutions.
6163 Documentation can be found in drivers/scsi/README.tmscsim.
6165 Note that this driver does NOT support Tekram DC390W/U/F, which are
6166 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
6167 Also note that there is another generic Am53C974 driver,
6168 "AM53/79C974 PCI SCSI support" below. You can pick either one.
6170 If you want to compile this driver as a module ( = code which can be
6171 inserted in and removed from the running kernel whenever you want),
6172 say M here and read Documentation/modules.txt. The module will be
6175 Omit support for other Am53/79C974 based SCSI adapters
6176 CONFIG_SCSI_DC390T_NOGENSUPP
6177 If you say N here, the DC390(T) SCSI driver relies on the DC390
6178 EEPROM to get initial values for its settings, such as speed,
6179 termination, etc. If it can't find this EEPROM, it will use defaults
6180 or the user supplied boot/module parameters. For details on driver
6181 configuration see drivers/scsi/README.tmscsim.
6183 If you say Y here and if no EEPROM is found, the driver gives up and
6184 thus only supports Tekram DC390(T) adapters. This can be useful if
6185 you have a DC390(T) and another Am53C974 based adapter, which, for
6186 some reason, you want to drive with the other AM53C974 driver.
6190 AM53/79C974 PCI SCSI support
6191 CONFIG_SCSI_AM53C974
6192 This is support for the AM53/79C974 SCSI host adapters. Please read
6193 drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
6194 available from http://www.linuxdoc.org/docs.html#howto , is for
6197 Note that there is another driver for AM53C974 based adapters:
6198 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
6199 can pick either one.
6201 If you want to compile this driver as a module ( = code which can be
6202 inserted in and removed from the running kernel whenever you want),
6203 say M here and read Documentation/modules.txt. The module will be
6206 AMI MegaRAID support
6207 CONFIG_SCSI_MEGARAID
6208 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490
6209 and 467 SCSI host adapters.
6211 If you want to compile this driver as a module ( = code which can be
6212 inserted in and removed from the running kernel whenever you want),
6213 say M here and read Documentation/modules.txt. The module will be
6216 GDT SCSI Disk Array Controller support
6218 This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
6219 manufactured by ICP vortex. It is documented in the kernel source in
6220 drivers/scsi/gdth.c and drivers/scsi/gdth.h.
6222 This driver is also available as a module ( = code which can be
6223 inserted in and removed from the running kernel whenever you want).
6224 If you want to compile it as a module, say M here and read
6225 Documentation/modules.txt.
6227 IOMEGA parallel port (ppa - older drives)
6229 This driver supports older versions of IOMEGA's parallel port ZIP
6230 drive (a 100 MB removable media device).
6232 Note that you can say N here if you have the SCSI version of the ZIP
6233 drive: it will be supported automatically if you said Y to the
6234 generic "SCSI disk support", above.
6236 If you have the ZIP Plus drive or a more recent parallel port ZIP
6237 drive (if the supplied cable with the drive is labeled "AutoDetect")
6238 then you should say N here and Y to "IOMEGA parallel port (imm -
6239 newer drives)", below.
6241 For more information about this driver and how to use it you should
6242 read the file drivers/scsi/README.ppa. You should also read the
6243 SCSI-HOWTO, which is available from
6244 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
6245 you will still be able to use the parallel port for other tasks,
6246 such as a printer; it is safe to compile both drivers into the
6249 This driver is also available as a module which can be inserted in
6250 and removed from the running kernel whenever you want. To compile
6251 this driver as a module, say M here and read
6252 Documentation/modules.txt. The module will be called ppa.o.
6254 IOMEGA parallel port (imm - newer drives)
6256 This driver supports newer versions of IOMEGA's parallel port ZIP
6257 drive (a 100 MB removable media device).
6259 Note that you can say N here if you have the SCSI version of the ZIP
6260 drive: it will be supported automatically if you said Y to the
6261 generic "SCSI disk support", above.
6263 If you have the ZIP Plus drive or a more recent parallel port ZIP
6264 drive (if the supplied cable with the drive is labeled "AutoDetect")
6265 then you should say Y here; if you have an older ZIP drive, say N
6266 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
6268 For more information about this driver and how to use it you should
6269 read the file drivers/scsi/README.ppa. You should also read the
6270 SCSI-HOWTO, which is available from
6271 http://www.linuxdoc.org/docs.html#howto . If you use this driver,
6272 you will still be able to use the parallel port for other tasks,
6273 such as a printer; it is safe to compile both drivers into the
6276 This driver is also available as a module which can be inserted in
6277 and removed from the running kernel whenever you want. To compile
6278 this driver as a module, say M here and read
6279 Documentation/modules.txt. The module will be called imm.o.
6281 Force the Iomega ZIP drivers to use EPP-16
6282 CONFIG_SCSI_IZIP_EPP16
6283 EPP (Enhanced Parallel Port) is a standard for parallel ports which
6284 allows them to act as expansion buses that can handle up to 64
6287 Some parallel port chipsets are slower than their motherboard, and
6288 so we have to control the state of the chipset's FIFO queue every
6289 now and then to avoid data loss. This will be done if you say Y
6292 Generally, saying Y is the safe option and slows things down a bit.
6294 Assume slow parallel port control register
6295 CONFIG_SCSI_IZIP_SLOW_CTR
6296 Some parallel ports are known to have excessive delays between
6297 changing the parallel port control register and good data being
6298 available on the parallel port data/status register. This option
6299 forces a small delay (1.0 usec to be exact) after changing the
6300 control register to let things settle out. Enabling this option may
6301 result in a big drop in performance but some very old parallel ports
6302 (found in 386 vintage machines) will not work properly.
6304 Generally, saying N is fine.
6306 Parallel port SCSI device support
6308 There are many external CD-ROM and disk devices that connect through
6309 your computer's parallel port. Lots of them are actually SCSI
6310 devices using a parallel port SCSI adapter. This option enables the
6311 ppSCSI subsystem which contains drivers for many of these external
6312 drives. You may also want to look at CONFIG_PARIDE (Parallel port
6313 IDE device support).
6315 If you built ppSCSI support into your kernel, you may still build
6316 the individual protocol modules and high-level drivers as loadable
6317 modules. If you build this support as a module, it will be called
6320 To use the ppSCSI support, you must say Y or M here and also to at
6321 least one protocol driver (e.g. "Shuttle EPST adapter", "Iomega VPI0
6322 adapter", "Shining ScarSCI adapter" etc.).
6324 Adaptec APA-348 adapter
6326 This option enables support for the APA-348 adapter from Adaptec
6327 (also known as Trantor T348). If you build this as a module it will
6330 Adaptec APA-358 adapter
6332 This option enables support for the APA-358 adapter from Adaptec
6333 (also known as Trantor T358). If you build this as a module it will
6338 This option enables support for the Iomega VPI0 adapter found in the
6339 original ZIP-100 drives and the Jaz Traveller. If you build this as
6340 a module it will be called vpi0.o.
6342 OnSpec 90c26 adapter
6343 CONFIG_PPSCSI_ONSCSI
6344 This option enables support for the OnSpec 90c26 in its SCSI adapter
6345 mode. If you build this as a module it will be called onscsi.o.
6347 Shining SparSCI adapter
6348 CONFIG_PPSCSI_SPARCSI
6349 This option enables support for the WBS-11A parallel port SCSI
6350 adapter. This adapter has been marketed by LinkSys as the
6351 "ParaSCSI+" and by Shining Technologies as the "SparCSI". If you
6352 build this as a module it will be called sparcsi.o.
6354 Shuttle EPSA-2 adapter
6356 This option enables support for the Shuttle Technologies EPSA2
6357 parallel port SCSI adapter. EPAS2 is a predecessor to the EPST. If
6358 you build this as a module it will be called epsa2.o.
6360 Shuttle EPST adapter
6362 This option enables support for the Shuttle Technologies EPST
6363 parallel port SCSI adapter. If you build this as a module is will
6366 SCSI Debug host simulator. (EXPERIMENTAL)
6368 This is a host adapter simulator that can be programmed to simulate
6369 a large number of conditions that could occur on a real bus. The
6370 advantage is that many hard to reproduce problems can be tested in a
6371 controlled environment where there is reduced risk of losing
6372 important data. This is primarily of use to people trying to debug
6373 the middle and upper layers of the SCSI subsystem. If unsure, say N.
6375 Fibre Channel support and FC4 SCSI support
6377 Fibre Channel is a high speed serial protocol mainly used to
6378 connect large storage devices to the computer; it is compatible with
6379 and intended to replace SCSI.
6381 This is an experimental support for storage arrays connected to your
6382 computer using optical fibre cables and the "X3.269-199X Fibre
6383 Channel Protocol for SCSI" specification. If you want to use this,
6384 you need to say Y here and to "SCSI support" as well as to the
6385 drivers for the storage array itself and for the interface adapter
6386 such as SOC or SOC+. This subsystem could even serve for IP
6387 networking, with some code extensions.
6393 Serial Optical Channel is an interface card with one or two Fibre
6394 Optic ports, each of which can be connected to a disk array. Note
6395 that if you have older firmware in the card, you'll need the
6396 microcode from the Solaris driver to make it work.
6398 This support is also available as a module called soc.o ( = code
6399 which can be inserted in and removed from the running kernel
6400 whenever you want). If you want to compile it as a module, say M
6401 here and read Documentation/modules.txt.
6403 Sun SOC+ (aka SOCAL)
6405 Serial Optical Channel Plus is an interface card with up to two
6406 Fibre Optic ports. This card supports FC Arbitrated Loop (usually
6407 A5000 or internal FC disks in E[3-6]000 machines through the
6408 Interface Board). You'll probably need the microcode from the
6409 Solaris driver to make it work.
6411 This support is also available as a module called socal.o ( = code
6412 which can be inserted in and removed from the running kernel
6413 whenever you want). If you want to compile it as a module, say M
6414 here and read Documentation/modules.txt.
6416 SparcSTORAGE Array 100 and 200 series
6418 If you never bought a disk array made by Sun, go with N.
6420 This support is also available as a module called pluto.o ( = code
6421 which can be inserted in and removed from the running kernel
6422 whenever you want). If you want to compile it as a module, say M
6423 here and read Documentation/modules.txt.
6425 Sun Enterprise Network Array (A5000 and EX500)
6427 This driver drives FC-AL disks connected through a Fibre Channel
6428 card using the drivers/fc4 layer (currently only SOCAL). The most
6429 common is either A5000 array or internal disks in E[3-6]000
6432 This support is also available as a module called fcal.o ( = code
6433 which can be inserted in and removed from the running kernel
6434 whenever you want). If you want to compile it as a module, say M
6435 here and read Documentation/modules.txt. If unsure, say N.
6438 CONFIG_SCSI_ACORNSCSI_3
6439 This enables support for the Acorn SCSI card (aka30). If you have an
6440 Acorn system with one of these, say Y. If unsure, say N.
6442 Acorn SCSI tagged queue support
6443 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
6444 Say Y here to enable tagged queuing support on the Acorn SCSI card.
6446 This is a feature of SCSI-2 which improves performance: the host
6447 adapter can send several SCSI commands to a device's queue even if
6448 previous commands haven't finished yet. Some SCSI devices don't
6449 implement this properly, so the safe answer is N.
6451 Acorn SCSI Synchronous transfers support
6452 CONFIG_SCSI_ACORNSCSI_SYNC
6453 Say Y here to enable synchronous transfer negotiation with all
6454 targets on the Acorn SCSI card.
6456 In general, this improves performance; however some SCSI devices
6457 don't implement it properly, so the safe answer is N.
6461 This enables support for the Oak SCSI card. If you have an Acorn
6462 system with one of these, say Y. If unsure, say N.
6464 Cumana SCSI I support
6465 CONFIG_SCSI_CUMANA_1
6466 This enables support for the Cumana SCSI I card. If you have an
6467 Acorn system with one of these, say Y. If unsure, say N.
6469 Cumana SCSI II support (EXPERIMENTAL)
6470 CONFIG_SCSI_CUMANA_2
6471 This enables support for the Cumana SCSI II card. If you have an
6472 Acorn system with one of these, say Y. If unsure, say N.
6476 This enables support for the EcoSCSI card -- a small card that sits
6477 in the Econet socket. If you have an Acorn system with one of these,
6478 say Y. If unsure, say N.
6480 EESOX SCSI support (EXPERIMENTAL)
6481 CONFIG_SCSI_EESOXSCSI
6482 This enables support for the EESOX SCSI card. If you have an Acorn
6483 system with one of these, say Y, otherwise say N.
6485 Powertec SCSI support (EXPERIMENTAL)
6486 CONFIG_SCSI_POWERTECSCSI
6487 This enables support for the Powertec SCSI card on Acorn systems. If
6488 you have one of these, say Y. If unsure, say N.
6490 IEEE 1394 (aka FireWire) support
6492 IEEE 1394 describes a high performance serial bus, which is also
6493 known as FireWire(tm) or i.Link(tm) and is used for connecting all
6494 sorts of devices (most notably digital video cameras) to your
6497 If you have FireWire hardware and want to use it, say Y here. This
6498 is the core support only, you will also need to select a driver for
6499 your IEEE 1394 adapter.
6501 If you want to compile this as a module ( = code which can be
6502 inserted in and removed from the running kernel whenever you want),
6503 say M here and read Documentation/modules.txt. The module will be
6506 TI PCILynx IEEE 1394 support
6507 CONFIG_IEEE1394_PCILYNX
6508 Say Y here if you have a IEEE-1394 controller with the Texas
6509 Instruments PCILynx chip. Note: this driver is written for revision
6510 2 of this chip and may not work with revision 0.
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 Use local RAM on PCILynx board
6518 CONFIG_IEEE1394_PCILYNX_LOCALRAM
6519 This option makes the PCILynx driver use local RAM available on some
6520 PCILynx setups for Packet Control Lists. Local RAM is random access
6521 memory which resides on the PCILynx board as opposed to on your
6522 computer's motherboard. Local RAM may speed up command processing
6523 because no PCI transfers are necessary during use of the Packet
6526 Note that there are no known PCILynx systems providing local RAM
6527 except for the evaluation boards by Texas Instruments and that the
6528 PCILynx does not reliably report missing RAM. This means that it is
6529 dangerous to say Y here if you are not absolutely sure that your
6530 board provides 64KB of local RAM.
6534 Support for non-IEEE1394 local ports
6535 CONFIG_IEEE1394_PCILYNX_PORTS
6536 This option enables driver code to access the RAM, ROM and AUX ports
6537 of the PCILynx through character devices in /dev. If you don't know
6538 what this is about then you won't need it.
6542 Adaptec AIC-5800 IEEE 1394 support
6543 CONFIG_IEEE1394_AIC5800
6544 Say Y here if you have a IEEE 1394 controller using the Adaptec
6545 AIC-5800 chip. All Adaptec host adapters (89xx series) use this
6546 chip, as well as miro's DV boards.
6548 If you want to compile this as a module ( = code which can be
6549 inserted in and removed from the running kernel whenever you want),
6550 say M here and read Documentation/modules.txt. The module will be
6553 OHCI (Open Host Controller Interface) support
6554 CONFIG_IEEE1394_OHCI1394
6555 Say Y here if you have a IEEE 1394 controller based on OHCI.
6556 The current driver was only tested with OHCI chipsets made
6557 by Texas Instruments. However, most third-party vendors use
6560 If you want to compile this as a module ( = code which can be
6561 inserted in and removed from the running kernel whenever you want),
6562 say M here and read Documentation/modules.txt. The module will be
6565 Raw IEEE 1394 I/O support
6566 CONFIG_IEEE1394_RAWIO
6567 Say Y here if you want support for the raw device. This is generally
6568 a good idea, so you should say Y here. The raw device enables
6569 direct communication of user programs with the IEEE 1394 bus and
6570 thus with the attached peripherals.
6572 If you want to compile this as a module ( = code which can be
6573 inserted in and removed from the running kernel whenever you want),
6574 say M here and read Documentation/modules.txt. The module will be
6577 Excessive debugging output
6578 CONFIG_IEEE1394_VERBOSEDEBUG
6579 If you say Y here, you will get very verbose debugging logs from the
6580 subsystem which includes a dump of the header of every sent and
6581 received packet. This can amount to a high amount of data collected
6582 in a very short time which is usually also saved to disk by the
6583 system logging daemons.
6585 Say Y if you really want or need the debugging output, everyone else
6588 Network device support?
6590 You can say N here if you don't intend to connect your Linux box to
6591 any other computer at all or if all your connections will be over a
6592 telephone line with a modem either via UUCP (UUCP is a protocol to
6593 forward mail and news between unix hosts over telephone lines; read
6594 the UUCP-HOWTO, available from
6595 http://www.linuxdoc.org/docs.html#howto ) or dialing up a shell
6596 account or a BBS, even using term (term is a program which gives you
6597 almost full Internet connectivity if you have a regular dial up
6598 shell account on some Internet connected Unix computer. Read
6599 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ).
6601 You'll have to say Y if your computer contains a network card that
6602 you want to use under Linux (make sure you know its name because you
6603 will be asked for it and read the Ethernet-HOWTO (especially if you
6604 plan to use more than one network card under Linux)) or if you want
6605 to use SLIP (Serial Line Internet Protocol is the protocol used to
6606 send Internet traffic over telephone lines or null modem cables) or
6607 CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
6608 and newer replacement for SLIP) or PLIP (Parallel Line Internet
6609 Protocol is mainly used to create a mini network by connecting the
6610 parallel ports of two local machines) or AX.25/KISS (protocol for
6611 sending Internet traffic over amateur radio links).
6613 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
6614 Olaf Kirch's excellent and free book "Network Administrator's
6615 Guide", to be found in http://www.linuxdoc.org/docs.html#guide . If
6618 Dummy net driver support
6620 This is essentially a bit-bucket device (i.e. traffic you send to
6621 this device is consigned into oblivion) with a configurable IP
6622 address. It is most commonly used in order to make your currently
6623 inactive SLIP address seem like a real address for local programs.
6624 If you use SLIP or PPP, you might want to say Y here. Since this
6625 thing often comes in handy, the default is Y. It won't enlarge your
6626 kernel either. What a deal. Read about it in the Network
6627 Administrator's Guide, available from
6628 http://www.linuxdoc.org/docs.html#guide .
6630 If you want to compile this as a module ( = code which can be
6631 inserted in and removed from the running kernel whenever you want),
6632 say M here and read Documentation/modules.txt. The module will be
6633 called dummy.o. If you want to use more than one dummy device at a
6634 time, you need to compile this driver as a module. Instead of
6635 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
6637 Bonding driver support
6639 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
6640 Channels together. This is called 'Etherchannel' by Cisco,
6641 'Trunking' by Sun, and 'Bonding' in Linux.
6643 If you have two ethernet connections to some other computer, you can
6644 make them behave like one double speed connection using this driver.
6645 Naturally, this has to be supported at the other end as well, either
6646 with a similar Bonding Linux driver, a Cisco 5500 switch or a
6647 SunTrunking SunSoft driver.
6649 This is similar to the EQL driver, but it merges Ethernet segments
6650 instead of serial lines.
6652 If you want to compile this as a module ( = code which can be
6653 inserted in and removed from the running kernel whenever you want),
6654 say M here and read Documentation/modules.txt. The module will be
6657 SLIP (serial line) support
6659 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
6660 connect to your Internet service provider or to connect to some
6661 other local Unix box or if you want to configure your Linux box as a
6662 Slip/CSlip server for other people to dial in. SLIP (Serial Line
6663 Internet Protocol) is a protocol used to send Internet traffic over
6664 serial connections such as telephone lines or null modem cables;
6665 nowadays, the protocol PPP is more commonly used for this same
6668 Normally, your access provider has to support SLIP in order for you
6669 to be able to use it, but there is now a SLIP emulator called SLiRP
6670 around (available via FTP (user: anonymous) from
6671 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
6672 allows you to use SLIP over a regular dial up shell connection. If
6673 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
6674 NET-3-HOWTO, available from
6675 http://www.linuxdoc.org/docs.html#howto , explains how to
6676 configure SLIP. Note that you don't need this option if you just
6677 want to run term (term is a program which gives you almost full
6678 Internet connectivity if you have a regular dial up shell account on
6679 some Internet connected Unix computer. Read
6680 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html ). SLIP
6681 support will enlarge your kernel by about 4 KB. If unsure, say N.
6683 If you want to compile this as a module ( = code which can be
6684 inserted in and removed from the running kernel whenever you want),
6685 say M here and read Documentation/modules.txt as well as
6686 Documentation/networking/net-modules.txt. The module will be called
6689 CSLIP compressed headers
6690 CONFIG_SLIP_COMPRESSED
6691 This protocol is faster than SLIP because it uses compression on the
6692 TCP/IP headers (not on the data itself), but it has to be supported
6693 on both ends. Ask your access provider if you are not sure and
6694 answer Y, just in case. You will still be able to use plain SLIP. If
6695 you plan to use SLiRP, the SLIP emulator (available from
6696 ftp://metalab.unc.edu/pub/Linux/system/network/serial/ ) which
6697 allows you to use SLIP over a regular dial up shell connection, you
6698 definitely want to say Y here. The NET-3-HOWTO, available from
6699 http://www.linuxdoc.org/docs.html#howto , explains how to configure
6700 CSLIP. This won't enlarge your kernel.
6702 Keepalive and linefill
6704 Adds additional capabilities to the SLIP driver to support the
6705 RELCOM line fill and keepalive monitoring. Ideal on poor quality
6708 Six bit SLIP encapsulation
6709 CONFIG_SLIP_MODE_SLIP6
6710 Just occasionally you may need to run IP over hostile serial
6711 networks that don't pass all control characters or are only seven
6712 bit. Saying Y here adds an extra mode you can use with SLIP:
6713 "slip6". In this mode, SLIP will only send normal ASCII symbols over
6714 the serial device. Naturally, this has to be supported at the other
6715 end of the link as well. It's good enough, for example, to run IP
6716 over the async ports of a Camtec JNT Pad. If unsure, say N.
6718 PPP (point-to-point protocol) support
6720 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
6721 the same purpose: sending Internet traffic over telephone (and other
6722 serial) lines. Ask your access provider if they support it, because
6723 otherwise you can't use it; most internet access providers these
6724 days support PPP rather than SLIP.
6726 To use PPP, you need an additional program called pppd as described
6727 in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
6728 at http://www.linuxdoc.org/docs.html#howto . If you upgrade
6729 from an older kernel, you might need to upgrade pppd as well. The
6730 PPP option enlarges your kernel by about 16 KB.
6732 There are actually two versions of PPP: the traditional PPP for
6733 asynchronous lines, such as regular analog phone lines, and
6734 synchronous PPP which can be used over digital ISDN lines for
6735 example. If you want to use PPP over phone lines or other
6736 asynchronous serial lines, you need to say Y (or M) here and also to
6737 the next option, "PPP support for async serial ports". For PPP over
6738 synchronous lines, you should say Y (or M) here and to "Support
6739 synchronous PPP", below.
6741 This driver is also available as a module ( = code which can be
6742 inserted in and removed from the running kernel whenever you want).
6743 If you said Y to "Version information on all symbols" above, then
6744 you cannot compile the PPP driver into the kernel; you can then only
6745 compile it as a module. The module will be called ppp_generic.o. If
6746 you want to compile it as a module, say M here and read
6747 Documentation/modules.txt as well as
6748 Documentation/networking/net-modules.txt.
6750 PPP multilink support (EXPERIMENTAL)
6751 CONFIG_PPP_MULTILINK
6752 PPP multilink is a protocol (defined in RFC 1990) which allows you
6753 to combine several (logical or physical) lines into one logical PPP
6754 connection, so that you can utilize your full bandwidth.
6756 This has to be supported at the other end as well and you need a
6757 version of the pppd daemon which understands the multilink protocol.
6761 PPP support for async serial ports
6763 Say Y (or M) here if you want to be able to use PPP over standard
6764 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
6765 a modem (not a synchronous or ISDN modem) to contact your ISP, you
6768 This code is also available as a module (code which can be inserted
6769 into and removed from the running kernel). If you want to compile
6770 it as a module, say M here and read Documentation/modules.txt.
6774 PPP support for sync tty ports
6776 Say Y (or M) here if you want to be able to use PPP over synchronous
6777 (HDLC) tty devices, such as the SyncLink adapter. These devices
6778 are often used for high-speed leased lines like T1/E1.
6780 This code is also available as a module (code which can be inserted
6781 into and removed from the running kernel). If you want to compile
6782 it as a module, say M here and read Documentation/modules.txt.
6784 PPP Deflate compression
6786 Support for the Deflate compression method for PPP, which uses the
6787 Deflate algorithm (the same algorithm that gzip uses) to compress
6788 each PPP packet before it is sent over the wire. The machine at the
6789 other end of the PPP link (usually your ISP) has to support the
6790 Deflate compression method as well for this to be useful. Even if
6791 they don't support it, it is safe to say Y here.
6793 This code is also available as a module (code which can be inserted
6794 into and removed from the running kernel). If you want to compile
6795 it as a module, say M here and read Documentation/modules.txt.
6797 PPP BSD-Compress compression
6799 Support for the BSD-Compress compression method for PPP, which uses
6800 the LZW compression method to compress each PPP packet before it is
6801 sent over the wire. The machine at the other end of the PPP link
6802 (usually your ISP) has to support the BSD-Compress compression
6803 method as well for this to be useful. Even if they don't support it,
6804 it is safe to say Y here.
6806 The PPP Deflate compression method ("PPP Deflate compression",
6807 above) is preferable to BSD-Compress, because it compresses better
6810 Note that the BSD compression code will always be compiled as a
6811 module; it is called bsd_comp.o and will show up in the directory
6812 modules once you have said "make modules". If unsure, say N.
6814 PPP over Ethernet (EXPERIMENTAL)
6816 Support for PPP over Ethernet.
6818 This driver requires a specially patched pppd daemon. The patch to
6819 pppd, along with binaries of a patched pppd package can be found at:
6820 http://www.math.uwaterloo.ca/~mostrows
6822 Wireless LAN (non-hamradio)
6824 Support for wireless LANs and everything having to do with radio,
6825 but not with amateur radio or FM broadcasting.
6827 Saying Y here also enables the Wireless Extensions (creates
6828 /proc/net/wireless and enables ifconfig access). The Wireless
6829 Extension is a generic API allowing a driver to expose to the user
6830 space configuration and statistics specific to common Wireless LANs.
6831 The beauty of it is that a single set of tool can support all the
6832 variations of Wireless LANs, regardless of their type (as long as
6833 the driver supports Wireless Extension). Another advantage is that
6834 these parameters may be changed on the fly without restarting the
6835 driver (or Linux). If you wish to use Wireless Extensions with
6836 wireless PCMCIA (PC-) cards, you need to say Y here; you can fetch
6838 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
6840 Some user-level drivers for scarab devices which don't require
6841 special kernel support are available from
6842 ftp://shadow.cabi.net/pub/Linux .
6844 STRIP (Metricom Starmode radio IP)
6846 Say Y if you have a Metricom radio and intend to use Starmode Radio
6847 IP. STRIP is a radio protocol developed for the MosquitoNet project
6848 (on the WWW at http://mosquitonet.stanford.edu/ ) to send Internet
6849 traffic using Metricom radios. Metricom radios are small, battery
6850 powered, 100kbit/sec packet radio transceivers, about the size and
6851 weight of a cellular telephone. (You may also have heard them called
6852 "Metricom modems" but we avoid the term "modem" because it misleads
6853 many people into thinking that you can plug a Metricom modem into a
6854 phone line and use it as a modem.)
6856 You can use STRIP on any Linux machine with a serial port, although
6857 it is obviously most useful for people with laptop computers. If you
6858 think you might get a Metricom radio in the future, there is no harm
6859 in saying Y to STRIP now, except that it makes the kernel a bit
6862 You can also compile this as a module ( = code which can be inserted
6863 in and removed from the running kernel whenever you want), say M
6864 here and read Documentation/modules.txt. The module will be called
6867 AT&T WaveLAN & DEC RoamAbout DS support
6869 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
6870 a Radio LAN (wireless Ethernet-like Local Area Network) using the
6871 radio frequencies 900 MHz and 2.4 GHz.
6873 This driver support the ISA version of the WaveLAN card. A separate
6874 driver for the PCMCIA (PC-card) hardware is available in David
6875 Hinds' pcmcia-cs package (see the file Documentation/Changes for
6878 If you want to use an ISA WaveLAN card under Linux, say Y and read
6879 the Ethernet-HOWTO, available from
6880 http://www.linuxdoc.org/docs.html#howto . Some more specific
6881 information is contained in Documentation/networking/wavelan.txt and
6882 in the source code drivers/net/wavelan.p.h.
6884 You will also need the wireless tools package available from
6885 http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html .
6886 Please read the man pages contained therein.
6888 This driver is also available as a module ( = code which can be
6889 inserted in and removed from the running kernel whenever you want).
6890 The module will be called wavelan.o. If you want to compile it as a
6891 module, say M here and read Documentation/modules.txt as well as
6892 Documentation/networking/net-modules.txt.
6894 Aironet Arlan 655 & IC2200 DS support
6896 Aironet makes Arlan, a class of wireless LAN adapters. These use the
6897 www.Telxon.com chip, which is also used on several similar cards.
6898 This driver is tested on the 655 and IC2200 series cards. Look at
6899 http://www.ylenurme.ee/~elmer/655/ for the latest information.
6901 The driver is built as two modules, arlan and arlan-proc. The latter
6902 is the /proc interface and is not needed most of time.
6904 On some computers the card ends up in non-valid state after some
6905 time. Use a ping-reset script to clear it.
6907 Aironet 4500/4800 series adapters
6909 www.aironet.com (recently bought by Cisco) makes these 802.11 DS
6910 adapters. Driver by Elmer Joandi (elmer@ylenurme.ee).
6912 Say Y here if you have such an adapter, and then say Y below to
6913 the option that applies to your particular type of card (PCI, ISA,
6916 This driver is also available as a module ( = code which can be
6917 inserted in and removed from the running kernel whenever you want).
6918 The module will be called aironet4500_core.o. If you want to
6919 compile it as a module, say M here and read
6920 Documentation/modules.txt as well as
6921 Documentation/networking/net-modules.txt.
6923 quick config parameters:
6924 SSID=tsunami - "The Password"
6925 adhoc=1 there are no Access Points around
6926 master=1 Adhoc master (the one who creates network
6928 slave=1 Adhoc slave (btw, it is still forming own net
6929 sometimes, and has problems with firmware...
6930 change IbssJoinNetTimeout from /proc...)
6931 channel=1..? meaningful in adhoc mode
6933 If you have problems with screwing up card, both_bap_lock=1 is a
6934 conservative value (performance hit 15%).
6936 All other parameters can be set via the proc interface.
6938 Aironet 4500/4800 ISA/PCI/PNP/365 support
6939 CONFIG_AIRONET4500_NONCS
6940 If you have an ISA, PCI or PCMCIA Aironet 4500/4800 wireless LAN
6941 card, say Y here, and then also to the options below that apply
6944 This driver is also available as a module ( = code which can be
6945 inserted in and removed from the running kernel whenever you want).
6946 The module will be called aironet4500_card.o. If you want to
6947 compile it as a module, say M here and read
6948 Documentation/modules.txt
6950 Aironet 4500/4800 PNP support
6951 CONFIG_AIRONET4500_PNP
6952 If you have an ISA Aironet 4500/4800 card which you want to use in
6953 PNP (Plug and Play) mode, say Y here. This is the recommended mode
6954 for ISA cards. Remember however to enable the PNP jumper on the
6955 board if you say Y here.
6957 Aironet 4500/4800 PCI support
6958 CONFIG_AIRONET4500_PCI
6959 If you have an PCI Aironet 4500/4800 card, say Y here.
6961 Aironet 4500/4800 ISA broken support (EXPERIMENTAL)
6962 CONFIG_AIRONET4500_ISA
6963 If you have an ISA Aironet 4500/4800 card which you want to run in
6964 non-PNP mode, say Y here. This is not recommended and does not work
6965 correctly at this point. Say N.
6967 Aironet 4500/4800 I365 broken support (EXPERIMENTAL)
6968 CONFIG_AIRONET4500_I365
6969 If you have a PCMCIA Aironet 4500/4800 card which you want to use
6970 without the standard PCMCIA cardservices provided by the pcmcia-cs
6971 package, say Y here. This is not recommended, so say N.
6973 Aironet 4500/4800 PCMCIA support
6974 CONFIG_AIRONET4500_CS
6975 Say Y here if you have a PCMCIA Aironet 4500/4800 card which you
6976 want to use with the standard PCMCIA cardservices provided by the
6979 This driver is also available as a module ( = code which can be
6980 inserted in and removed from the running kernel whenever you want).
6981 The module will be called aironet4500_cs.o. If you want to
6982 compile it as a module, say M here and read
6983 Documentation/modules.txt.
6985 Aironet 4500/4800 PROC interface
6986 CONFIG_AIRONET4500_PROC
6987 If you say Y here (and to the "/proc file system" below), you will
6988 be able to configure your Aironet card via the
6989 /proc/sys/aironet4500 interface.
6991 Additional info: look in drivers/net/aironet4500_rids.c.
6993 This driver is also available as a module ( = code which can be
6994 inserted in and removed from the running kernel whenever you want).
6995 The module will be called aironet4500_proc.o. If you want to
6996 compile it as a module, say M here and read
6997 Documentation/modules.txt.
6999 NOTE: the proc interface uses a lot of memory, so it is recommended
7000 to compile it as a module and remove the module after
7003 LAPB over Ethernet driver
7005 This is a driver for a pseudo device (typically called /dev/lapb0)
7006 which allows you to open an LAPB point-to-point connection to some
7007 other computer on your Ethernet network. In order to do this, you
7008 need to say Y or M to the driver for your Ethernet card as well as
7009 to "LAPB Data Link Driver".
7011 If you want to compile this driver as a module ( = code which can be
7012 inserted in and removed from the running kernel whenever you want),
7013 say M here and read Documentation/modules.txt. The module will be
7014 called lapbether.o. If unsure, say N.
7018 This is a driver for sending and receiving X.25 frames over regular
7019 asynchronous serial lines such as telephone lines equipped with
7020 ordinary modems. Experts should note that this driver doesn't
7021 currently comply with the asynchronous HDLS framing protocols in
7022 CCITT recommendation X.25.
7024 If you want to compile this driver as a module ( = code which can be
7025 inserted in and removed from the running kernel whenever you want),
7026 say M here and read Documentation/modules.txt. The module will be
7027 called x25_asy.o. If unsure, say N.
7029 PCMCIA network device support
7031 Say Y if you would like to include support for any PCMCIA or CardBus
7032 network adapters, then say Y to the driver for your particular card
7033 below. PCMCIA- or PC-cards are credit-card size devices often used
7034 with laptops computers; CardBus is the newer and faster version of
7037 To use your PC-cards, you will need supporting software from David
7038 Hinds' pcmcia-cs package (see the file Documentation/Changes for
7039 location). You also want to check out the PCMCIA-HOWTO, available
7040 from http://www.linuxdoc.org/docs.html#howto .
7044 3Com 3c589 PCMCIA support
7046 Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA
7047 (PC-card) Ethernet card to your computer.
7049 This driver is also available as a module ( = code which can be
7050 inserted in and removed from the running kernel whenever you want).
7051 The module will be called 3c589_cs.o. If you want to compile it as a
7052 module, say M here and read Documentation/modules.txt. If unsure,
7055 3Com 3c574 PCMCIA support
7057 Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA
7058 (PC-card) Fast Ethernet card to your computer.
7060 This driver is also available as a module ( = code which can be
7061 inserted in and removed from the running kernel whenever you want).
7062 The module will be called 3c574_cs.o. If you want to compile it as a
7063 module, say M here and read Documentation/modules.txt. If unsure,
7066 Fujitsu FMV-J18x PCMCIA support
7067 CONFIG_PCMCIA_FMVJ18X
7068 Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible
7069 PCMCIA (PC-card) Ethernet card to your computer.
7071 This driver is also available as a module ( = code which can be
7072 inserted in and removed from the running kernel whenever you want).
7073 The module will be called fmvj18x_cs.o. If you want to compile it as
7074 a module, say M here and read Documentation/modules.txt. If unsure,
7077 NE2000 compatible PCMCIA support
7079 Say Y here if you intend to attach an NE2000 compatible PCMCIA
7080 (PC-card) Ethernet or Fast Ethernet card to your computer.
7082 This driver is also available as a module ( = code which can be
7083 inserted in and removed from the running kernel whenever you want).
7084 The module will be called pcnet_cs.o. If you want to compile it as a
7085 module, say M here and read Documentation/modules.txt. If unsure,
7088 New Media PCMCIA support
7089 CONFIG_PCMCIA_NMCLAN
7090 Say Y here if you intend to attach a New Media Ethernet or LiveWire
7091 PCMCIA (PC-card) Ethernet card to your computer.
7093 This driver is also available as a module ( = code which can be
7094 inserted in and removed from the running kernel whenever you want).
7095 The module will be called nmclan_cs.o. If you want to compile it as
7096 a module, say M here and read Documentation/modules.txt. If unsure,
7099 SMC 91Cxx PCMCIA support
7100 CONFIG_PCMCIA_SMC91C92
7101 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
7102 (PC-card) Ethernet or Fast Ethernet card to your computer.
7104 This driver is also available as a module ( = code which can be
7105 inserted in and removed from the running kernel whenever you want).
7106 The module will be called smc91c92_cs.o. If you want to compile it
7107 as a module, say M here and read Documentation/modules.txt. If
7110 Xircom 16-bit PCMCIA support
7111 CONFIG_PCMCIA_XIRC2PS
7112 Say Y here if you intend to attach a Xircom 16-bit PCMCIA
7113 (PC-card) Ethernet or Fast Ethernet card to your computer.
7115 This driver is also available as a module ( = code which can be
7116 inserted in and removed from the running kernel whenever you want).
7117 The module will be called xirc2ps_cs.o. If you want to compile it as
7118 a module, say M here and read Documentation/modules.txt. If unsure,
7121 COM20020 ARCnet PCMCIA support
7122 CONFIG_ARCNET_COM20020_CS
7123 Say Y here if you intend to attach this type of ARCnet PCMCIA card
7126 This driver is also available as a module ( = code which can be
7127 inserted in and removed from the running kernel whenever you want).
7128 The module will be called com20020_cs.o. If you want to compile it
7129 as a module, say M here and read Documentation/modules.txt. If
7132 IBM PCMCIA Token Ring adapter support
7134 Say Y here if you intend to attach this type of Token Ring PCMCIA
7135 card to your computer. You then also need to say Y to "Token Ring
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 ibmtr_cs.o. If you want to compile it
7141 as a module, say M here and read Documentation/modules.txt.
7143 Xircom Tulip-like CardBus support
7144 CONFIG_PCMCIA_XIRTULIP
7145 This driver is for the Digital "Tulip" Ethernet CardBus adapters.
7146 It should work with most DEC 21*4*-based chips/ethercards, as well
7147 as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and
7150 This driver is also available as a module ( = code which can be
7151 inserted in and removed from the running kernel whenever you want).
7152 The module will be called xircom_tulip_cb.o. If you want to compile
7153 it as a module, say M here and read Documentation/modules.txt. If
7157 CONFIG_NET_PCMCIA_RADIO
7158 Say Y here if you would like to use a PCMCIA (PC-card) device to
7159 connect to a wireless local area network. Then say Y to the driver
7160 for your particular card below.
7162 To use your PC-cards, you will need supporting software from David
7163 Hinds' pcmcia-cs package (see the file Documentation/Changes for
7164 location). You also want to check out the PCMCIA-HOWTO, available
7165 from http://www.linuxdoc.org/docs.html#howto .
7167 Aviator/Raytheon 2.4MHz wireless support
7169 Say Y here if you intend to attach an Aviator/Raytheon PCMCIA
7170 (PC-card) wireless Ethernet networking card to your computer.
7171 Please read the file Documentation/networking/ray_cs.txt for
7174 This driver is also available as a module ( = code which can be
7175 inserted in and removed from the running kernel whenever you want).
7176 The module will be called ray_cs.o. If you want to compile it as a
7177 module, say M here and read Documentation/modules.txt. If unsure,
7180 Xircom Netwave AirSurfer wireless support
7181 CONFIG_PCMCIA_NETWAVE
7182 Say Y here if you intend to attach this type of PCMCIA (PC-card)
7183 wireless Ethernet networking card to your computer.
7185 This driver is also available as a module ( = code which can be
7186 inserted in and removed from the running kernel whenever you want).
7187 The module will be called netwave_cs.o. If you want to compile it as
7188 a module, say M here and read Documentation/modules.txt. If unsure,
7191 AT&T/Lucent Wavelan wireless support
7192 CONFIG_PCMCIA_WAVELAN
7193 Say Y here if you intend to attach an AT&T/Lucent Wavelan PCMCIA
7194 (PC-card) wireless Ethernet networking card to your computer. This
7195 driver is for the non-IEEE-802.11 Wavelan cards.
7197 This driver is also available as a module ( = code which can be
7198 inserted in and removed from the running kernel whenever you want).
7199 The module will be called wavelan_cs.o. If you want to compile it as
7200 a module, say M here and read Documentation/modules.txt. If unsure,
7203 PLIP (parallel port) support
7205 PLIP (Parallel Line Internet Protocol) is used to create a
7206 reasonably fast mini network consisting of two (or, rarely, more)
7207 local machines. A PLIP link from a Linux box is a popular means to
7208 install a Linux distribution on a machine which doesn't have a CDROM
7209 drive (a minimal system has to be transferred with floppies first).
7210 The kernels on both machines need to have this PLIP option enabled
7213 The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
7214 (the connectors at the computers with 25 holes) are connected with
7215 "null printer" or "Turbo Laplink" cables which can transmit 4 bits
7216 at a time (mode 0) or with special PLIP cables, to be used on
7217 bidirectional parallel ports only, which can transmit 8 bits at a
7218 time (mode 1); you can find the wiring of these cables in
7219 Documentation/networking/PLIP.txt. The cables can be up to 15m long.
7220 Mode 0 works also if one of the machines runs DOS/Windows and has
7221 some PLIP software installed, e.g. the Crynwr PLIP packet driver
7222 (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html ) and
7223 winsock or NCSA's telnet.
7225 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
7226 as the NET-3-HOWTO, both available from
7227 http://www.linuxdoc.org/docs.html#howto . Note that the PLIP
7228 protocol has been changed and this PLIP driver won't work together
7229 with the PLIP support in Linux versions 1.0.x. This option enlarges
7230 your kernel by about 8 KB.
7232 If you want to compile this as a module ( = code which can be
7233 inserted in and removed from the running kernel whenever you want),
7234 say M here and read Documentation/modules.txt as well as
7235 Documentation/networking/net-modules.txt. The module will be called
7236 plip.o. If unsure, say Y or M, in case you buy a laptop later.
7238 EQL (serial line load balancing) support
7240 If you have two serial connections to some other computer (this
7241 usually requires two modems and two telephone lines) and you use
7242 SLIP (the protocol for sending Internet traffic over telephone
7243 lines) or PPP (a better SLIP) on them, you can make them behave like
7244 one double speed connection using this driver. Naturally, this has
7245 to be supported at the other end as well, either with a similar EQL
7246 Linux driver or with a Livingston Portmaster 2e.
7248 Say Y if you want this and read Documentation/networking/eql.txt.
7249 You may also want to read section 6.2 of the NET-3-HOWTO, available
7250 from http://www.linuxdoc.org/docs.html#howto .
7252 This driver is also available as a module ( = code which can be
7253 inserted in and removed from the running kernel whenever you want).
7254 The module will be called eql.o. If you want to compile it as a
7255 module, say M here and read Documentation/modules.txt. If unsure,
7258 Universal TUN/TAP device driver.
7260 TUN/TAP provides packet reception and transmission for user space programs.
7261 It can be viewed as a simple Point-to-Point or Ethernet device, which
7262 instead of receiving packets from a physical media, receives them from
7263 user space program and instead of sending packets via physical media
7264 writes them to the user space program.
7266 When a program opens /dev/net/tun, driver creates and registers
7267 corresponding net device tunX or tapX. After a program closed above
7268 devices, driver will automatically delete tunXX or tapXX device and all
7269 routes corresponding to it.
7271 Please read Documentation/networking/tuntap.txt for more information.
7273 This driver is also available as a module ( = code which can be
7274 inserted in and removed from the running kernel whenever you want).
7275 The module will be called tun.o. If you want to compile it as a
7276 module, say M here and read Documentation/modules.txt.
7278 If you don't know what to use this for, you don't need it.
7280 Ethertap network tap (OBSOLETE)
7282 If you say Y here (and have said Y to "Kernel/User network link
7283 driver", above) and create a character special file /dev/tap0 with
7284 major number 36 and minor number 16 using mknod ("man mknod"), you
7285 will be able to have a user space program read and write raw
7286 Ethernet frames from/to that special file. tap0 can be configured
7287 with ifconfig and route like any other Ethernet device but it is not
7288 connected to any physical LAN; everything written by the user to
7289 /dev/tap0 is treated by the kernel as if it had come in from a LAN
7290 to the device tap0; everything the kernel wants to send out over the
7291 device tap0 can instead be read by the user from /dev/tap0: the user
7292 mode program replaces the LAN that would be attached to an ordinary
7293 Ethernet device. Please read the file
7294 Documentation/networking/ethertap.txt for more information.
7296 This driver is also available as a module ( = code which can be
7297 inserted in and removed from the running kernel whenever you want).
7298 The module will be called ethertap.o. If you want to compile it as a
7299 module, say M here and read Documentation/modules.txt.
7301 If you don't know what to use this for, you don't need it.
7303 Sealevel Systems 4021 support
7304 CONFIG_SEALEVEL_4021
7305 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
7307 This driver can only be compiled as a module ( = code which can be
7308 inserted in and removed from the running kernel whenever you want).
7309 If you want to do that, say M here. The module will be called
7312 SyncLink HDLC/SYNCPPP support
7313 CONFIG_SYNCLINK_SYNCPPP
7314 Enables HDLC/SYNCPPP support for the SyncLink WAN driver.
7315 Normally the SyncLink WAN driver works with the main PPP
7316 driver (ppp.c) and pppd program. HDLC/SYNCPPP support allows use
7317 of the Cisco HDLC/PPP driver (syncppp.c).
7318 The SyncLink WAN driver (in character devices) must also be enabled.
7320 Frame Relay (DLCI) support
7322 This is support for the frame relay protocol; frame relay is a fast
7323 low-cost way to connect to a remote Internet access provider or to
7324 form a private wide area network. The one physical line from your
7325 box to the local "switch" (i.e. the entry point to the frame relay
7326 network, usually at the phone company) can carry several logical
7327 point-to-point connections to other computers connected to the frame
7328 relay network. For a general explanation of the protocol, check out
7329 http://www.frforum.com/ on the WWW. To use frame relay, you need
7330 supporting hardware (called FRAD) and certain programs from the
7331 net-tools package as explained in
7332 Documentation/networking/framerelay.txt.
7334 This driver is also available as a module ( = code which can be
7335 inserted in and removed from the running kernel whenever you want).
7336 The module will be called dlci.o. If you want to compile it as a
7337 module, say M here and read Documentation/modules.txt.
7341 This is the maximal number of logical point-to-point frame relay
7342 connections (the identifiers of which are called DCLIs) that
7343 the driver can handle. The default is probably fine.
7347 You can specify here how many logical point-to-point frame relay
7348 connections (the identifiers of which are called DCLIs) should be
7349 handled by each of your hardware frame relay access devices. Go with
7352 Sangoma S502A FRAD support
7354 Say Y here if you need a driver for the Sangoma S502A, S502E, and
7355 S508 Frame Relay Access Devices. These are multi-protocol cards, but
7356 only frame relay is supported by the driver at this time. Please
7357 read Documentation/framerelay.txt.
7359 This driver is also available as a module ( = code which can be
7360 inserted in and removed from the running kernel whenever you want).
7361 The module will be called sdla.o. If you want to compile it as a
7362 module, say M here and read Documentation/modules.txt.
7364 Acorn Econet/AUN protocols (EXPERIMENTAL)
7366 Econet is a fairly old and slow networking protocol mainly used by
7367 Acorn computers to access file and print servers. It uses native
7368 Econet network cards. AUN is an implementation of the higher level
7369 parts of Econet that runs over ordinary Ethernet connections, on
7370 top of the UDP packet protocol, which in turn runs on top of the
7371 Internet protocol IP.
7373 If you say Y here, you can choose with the next two options whether
7374 to send Econet/AUN traffic over a UDP Ethernet connection or over
7375 a native Econet network card.
7377 This driver is also available as a module ( = code which can be
7378 inserted in and removed from the running kernel whenever you want).
7379 The module will be called econet.o. If you want to compile it as a
7380 module, say M here and read Documentation/modules.txt.
7383 CONFIG_ECONET_AUNUDP
7384 Say Y here if you want to send Econet/AUN traffic over a UDP
7385 connection (UDP is a packet based protocol that runs on top of the
7386 Internet protocol IP) using an ordinary Ethernet network card.
7389 CONFIG_ECONET_NATIVE
7390 Say Y here if you have a native Econet network card installed in
7395 Wide Area Networks (WANs), such as X.25, frame relay and leased
7396 lines, are used to interconnect Local Area Networks (LANs) over vast
7397 distances with data transfer rates significantly higher than those
7398 achievable with commonly used asynchronous modem connections.
7399 Usually, a quite expensive external device called a `WAN router' is
7400 needed to connect to a WAN.
7402 As an alternative, WAN routing can be built into the Linux kernel.
7403 With relatively inexpensive WAN interface cards available on the
7404 market, a perfectly usable router can be built for less than half
7405 the price of an external router. If you have one of those cards and
7406 wish to use your Linux box as a WAN router, say Y here and also to
7407 the WAN driver for your card, below. You will then need the
7408 wan-tools package which is available from ftp://ftp.sangoma.com .
7409 Read Documentation/networking/wan-router.txt for more information.
7411 The WAN routing support is also available as a module called
7412 wanrouter.o ( = code which can be inserted in and removed from the
7413 running kernel whenever you want). If you want to compile it as a
7414 module, say M here and read Documentation/modules.txt.
7418 Fast switching (read help!)
7419 CONFIG_NET_FASTROUTE
7420 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
7421 Card) data transfers on the local network, which is fast.
7423 IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
7424 filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
7426 However, it will work with all options in the "IP: advanced router"
7427 section (except for "IP: use TOS value as routing key" and
7428 "IP: use FWMARK value as routing key").
7430 At the moment, few devices support fast switching (tulip is one of
7431 them, a modified 8390 driver can be found at
7432 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7436 Forwarding between high speed interfaces
7437 CONFIG_NET_HW_FLOWCONTROL
7438 This option enables NIC (Network Interface Card) hardware throttling
7439 during periods of extremal congestion. At the moment only a couple
7440 of device drivers support it (really only one -- tulip, a modified
7441 8390 driver can be found at
7442 ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz ).
7444 Really, this option is applicable to any machine attached to a fast
7445 enough network, and even a 10 Mb NIC is able to kill a not very slow
7446 box, such as a 120MHz Pentium.
7448 However, do not say Y here if you did not experience any serious
7451 QoS and/or fair queueing
7453 When the kernel has several packets to send out over a network
7454 device, it has to decide which ones to send first, which ones to
7455 delay, and which ones to drop. This is the job of the packet
7456 scheduler, and several different algorithms for how to do this
7457 "fairly" have been proposed.
7459 If you say N here, you will get the standard packet scheduler, which
7460 is a FIFO (first come, first served). If you say Y here, you will be
7461 able to choose from among several alternative algorithms which can
7462 then be attached to different network devices. This is useful for
7463 example if some of your network devices are real time devices that
7464 need a certain minimum data flow rate, or if you need to limit the
7465 maximum data flow rate for traffic which matches specified criteria.
7466 This code is considered to be experimental.
7468 To administer these schedulers, you'll need the user-level utilities
7469 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/ .
7470 That package also contains some documentation; for more, check out
7471 http://snafu.freedom.org/linux2.2/iproute-notes.html .
7473 This Quality of Service (QoS) support will enable you to use
7474 Differentiated Services (diffserv) and Resource Reservation Protocol
7475 (RSVP) on your Linux router if you also say Y to "QoS support",
7476 "Packet classifier API" and to some classifiers below. Documentation
7477 and software is at http://icawww1.epfl.ch/linux-diffserv/ .
7479 If you say Y here and to "/proc file system" below, you will be able
7480 to read status information about packet schedulers from the file
7483 The available schedulers are listed in the following questions; you
7484 can say Y to as many as you like. If unsure, say N now.
7486 CBQ packet scheduler
7488 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
7489 scheduling algorithm for some of your network devices. This
7490 algorithm classifies the waiting packets into a tree-like hierarchy
7491 of classes; the leaves of this tree are in turn scheduled by
7492 separate algorithms (called "disciplines" in this context).
7494 See the top of net/sched/sch_cbq.c for references about the CBQ
7497 CBQ is a commonly used scheduler, so if you're unsure, you should
7498 say Y here. Then say Y to all the queueing algorithms below that you
7499 want to use as CBQ disciplines. Then say Y to "Packet classifier
7500 API" and say Y to all the classifiers you want to use; a classifier
7501 is a routine that allows you to sort your outgoing traffic into
7502 classes based on a certain criterion.
7504 This code is also available as a module called sch_cbq.o ( = code
7505 which can be inserted in and removed from the running kernel
7506 whenever you want). If you want to compile it as a module, say M
7507 here and read Documentation/modules.txt.
7509 CSZ packet scheduler
7511 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
7512 scheduling algorithm for some of your network devices. At the
7513 moment, this is the only algorithm that can guarantee service for
7514 real-time applications (see the top of net/sched/sch_csz.c for
7515 details and references about the algorithm).
7517 Note: this scheduler is currently broken.
7519 This code is also available as a module called sch_csz.o ( = code
7520 which can be inserted in and removed from the running kernel
7521 whenever you want). If you want to compile it as a module, say M
7522 here and read Documentation/modules.txt.
7524 #ATM pseudo-scheduler
7530 The simplest PRIO pseudo scheduler
7532 Say Y here if you want to use an n-band priority queue packet
7533 "scheduler" for some of your network devices or as a leaf discipline
7534 for the CBQ scheduling algorithm. If unsure, say Y.
7536 This code is also available as a module called sch_prio.o ( = code
7537 which can be inserted in and removed from the running kernel
7538 whenever you want). If you want to compile it as a module, say M
7539 here and read Documentation/modules.txt.
7543 Say Y here if you want to use the Random Early Detection (RED)
7544 packet scheduling algorithm for some of your network devices (see
7545 the top of net/sched/sch_red.c for details and references about the
7548 This code is also available as a module called sch_red.o ( = code
7549 which can be inserted in and removed from the running kernel
7550 whenever you want). If you want to compile it as a module, say M
7551 here and read Documentation/modules.txt.
7555 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
7556 packet scheduling algorithm for some of your network devices or as a
7557 leaf discipline for the CBQ scheduling algorithm (see the top of
7558 net/sched/sch_sfq.c for details and references about the SFQ
7561 This code is also available as a module called sch_sfq.o ( = code
7562 which can be inserted in and removed from the running kernel
7563 whenever you want). If you want to compile it as a module, say M
7564 here and read Documentation/modules.txt.
7568 Say Y here if you want to use the True Link Equalizer (TLE) packet
7569 scheduling algorithm for some of your network devices or as a leaf
7570 discipline for the CBQ scheduling algorithm. This queueing
7571 discipline allows the combination of several physical devices into
7572 one virtual device. (see the top of net/sched/sch_teql.c for
7575 This code is also available as a module called sch_teql.o ( = code
7576 which can be inserted in and removed from the running kernel
7577 whenever you want). If you want to compile it as a module, say M
7578 here and read Documentation/modules.txt.
7582 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
7583 packet scheduling algorithm for some of your network devices or as a
7584 leaf discipline for the CBQ scheduling algorithm (see the top of
7585 net/sched/sch_tbf.c for a description of the TBF algorithm).
7587 This code is also available as a module called sch_tbf.o ( = code
7588 which can be inserted in and removed from the running kernel
7589 whenever you want). If you want to compile it as a module, say M
7590 here and read Documentation/modules.txt.
7593 #+tristate ' GRED queue' CONFIG_NET_SCH_GRED
7594 #+tristate ' Diffserv field marker' CONFIG_NET_SCH_DSMARK
7595 #+tristate ' Ingress Qdisc' CONFIG_NET_SCH_INGRESS
7599 Say Y here if you want to include Quality Of Service scheduling
7600 features, which means that you will be able to request certain
7601 rate-of-flow limits for your network devices.
7603 This Quality of Service (QoS) support will enable you to use
7604 Differentiated Services (diffserv) and Resource Reservation Protocol
7605 (RSVP) on your Linux router if you also say Y to "Packet classifier
7606 API" and to some classifiers below. Documentation and software is at
7607 http://icawww1.epfl.ch/linux-diffserv/ .
7609 Note that the answer to this question won't directly affect the
7610 kernel: saying N will just cause this configure script to skip all
7611 the questions about QoS support.
7614 CONFIG_NET_ESTIMATOR
7615 In order for Quality of Service scheduling to work, the current
7616 rate-of-flow for a network device has to be estimated; if you say Y
7617 here, the kernel will do just that.
7619 Packet classifier API
7621 The CBQ scheduling algorithm requires that network packets which are
7622 scheduled to be sent out over a network device be classified
7623 according to some criterion. If you say Y here, you will get a
7624 choice of several different packet classifiers with the following
7627 This will enable you to use Differentiated Services (diffserv) and
7628 Resource Reservation Protocol (RSVP) on your Linux router.
7629 Documentation and software is at
7630 http://icawww1.epfl.ch/linux-diffserv/ .
7633 #tristate ' TC index classifier' CONFIG_NET_CLS_TCINDEX
7635 Routing tables based classifier
7636 CONFIG_NET_CLS_ROUTE4
7637 If you say Y here, you will be able to classify outgoing packets
7638 according to the route table entry they matched. If unsure, say Y.
7640 This code is also available as a module called cls_route.o ( = code
7641 which can be inserted in and removed from the running kernel
7642 whenever you want). If you want to compile it as a module, say M
7643 here and read Documentation/modules.txt.
7645 Firewall based classifier
7647 If you say Y here, you will be able to classify outgoing packets
7648 according to firewall criteria you specified.
7650 This code is also available as a module called cls_fw.o ( = code
7651 which can be inserted in and removed from the running kernel
7652 whenever you want). If you want to compile it as a module, say M
7653 here and read Documentation/modules.txt.
7657 If you say Y here, you will be able to classify outgoing packets
7658 according to their destination address. If unsure, say Y.
7660 This code is also available as a module called cls_u32.o ( = code
7661 which can be inserted in and removed from the running kernel
7662 whenever you want). If you want to compile it as a module, say M
7663 here and read Documentation/modules.txt
7665 Special RSVP classifier
7667 The Resource Reservation Protocol (RSVP) permits end systems to
7668 request a minimum and maximum data flow rate for a connection; this
7669 is important for real time data such as streaming sound or video.
7671 Say Y here if you want to be able to classify outgoing packets based
7672 on their RSVP requests.
7674 This code is also available as a module called cls_rsvp.o ( = code
7675 which can be inserted in and removed from the running kernel
7676 whenever you want). If you want to compile it as a module, say M
7677 here and read Documentation/modules.txt
7679 Special RSVP classifier for IPv6
7680 CONFIG_NET_CLS_RSVP6
7681 The Resource Reservation Protocol (RSVP) permits end systems to
7682 request a minimum and maximum data flow rate for a connection; this
7683 is important for real time data such as streaming sound or video.
7685 Say Y here if you want to be able to classify outgoing packets based
7686 on their RSVP requests and you are using the new Internet Protocol
7687 IPv6 as opposed to the older and more common IPv4.
7689 This code is also available as a module called cls_rsvp6.o ( = code
7690 which can be inserted in and removed from the running kernel
7691 whenever you want). If you want to compile it as a module, say M
7692 here and read Documentation/modules.txt
7695 # Traffic policing (needed for in/egress)
7696 # CONFIG_NET_CLS_POLICE
7698 ### Some expert please fill these in
7701 Network code profiler
7703 If you say Y here and to "/proc file system support" below, some
7704 obscure and undocumented information about the network code's
7705 performance will be written to /proc/net/profile. If you don't know
7706 what it is about, you don't need it: say N.
7708 Wan interfaces support
7710 Wide Area Networks (WANs), such as X.25, frame relay and leased
7711 lines, are used to interconnect Local Area Networks (LANs) over vast
7712 distances with data transfer rates significantly higher than those
7713 achievable with commonly used asynchronous modem connections.
7714 Usually, a quite expensive external device called a `WAN router' is
7715 needed to connect to a WAN.
7717 As an alternative, a relatively inexpensive WAN interface card can
7718 allow your Linux box to directly connect to a WAN. If you have one
7719 of those cards and wish to use it under Linux, say Y here and also
7720 to the WAN driver for your card, below.
7724 Comtrol Hostess SV-11 support
7726 This is a network card for low speed synchronous serial links, at
7727 up to 256Kbps. It supports both PPP and Cisco HDLC.
7729 At this point, the driver can only be compiled as a module.
7731 COSA/SRP sync serial boards support
7733 This is a driver for COSA and SRP synchronous serial boards. These
7734 boards allow to connect synchronous serial devices (for example
7735 base-band modems, or any other device with the X.21, V.24, V.35 or
7736 V.36 interface) to your Linux box. The cards can work as the
7737 character device, synchronous PPP network device, or the Cisco HDLC
7740 To actually use the COSA or SRP board, you will need user-space
7741 utilities for downloading the firmware to the cards and to set them
7742 up. Look at the http://www.fi.muni.cz/~kas/cosa/ for more
7743 information about the cards (including the pointer to the user-space
7744 utilities). You can also read the comment at the top of the
7745 drivers/net/cosa.c for details about the cards and the driver
7748 The driver will be compiled as a module ( = code which can be
7749 inserted in and removed from the running kernel whenever you want).
7750 The module will be called cosa.o. For general information about
7751 modules read Documentation/modules.txt.
7753 Lan Media sync serial boards support
7755 This is a driver for the following Lan Media family of serial boards.
7757 LMC 1000 board allows you to connect synchronous serial devices (for
7758 example base-band modems, or any other device with the X.21, V.24,
7759 V.35 or V.36 interface) to your Linux box.
7761 LMC 1200 with on board DSU board allows you to connect your Linux
7762 box dirrectly to a T1 or E1 circuit.
7764 LMC 5200 board provides a HSSI interface capable of runnig up to
7765 52 mbits per second.
7767 LMC 5245 board connects directly to a T3 circuit saving the
7768 additional external hardware.
7770 To change setting such as syncPPP vs cisco HDLC or clock source you
7771 will need lmcctl. It it available at ftp.lanmedia.com.
7773 This code is also available as a module called lmc.o ( = code
7774 which can be inserted in and removed from the running kernel
7775 whenever you want). If you want to compile it as a module, say M
7776 here and read Documentation/modules.txt.
7778 Fibre Channel driver support
7780 Fibre Channel is a high speed serial protocol mainly used to connect
7781 large storage devices to the computer; it is compatible with and
7782 intended to replace SCSI.
7784 If you intend to use Fibre Channel, you need to have a Fibre channel
7785 adaptor card in your computer; say Y here and to the driver for your
7786 adaptor below. You also should have said Y to "SCSI support" and
7787 "SCSI generic support".
7789 Interphase 5526 Tachyon chipset based adaptor support
7791 Say Y here if you have a Fibre Channel adaptor of this kind.
7793 The driver is also available as a module ( = code which can be
7794 inserted in and removed from the running kernel whenever you want).
7795 The module will be called iph5526.o. For general information about
7796 modules read Documentation/modules.txt.
7798 Red Creek Hardware VPN (EXPERIMENTAL)
7800 This is a driver for hardware which provides a Virtual Private
7801 Network (VPN). Say Y if you have it.
7803 This code is also available as a module called rcpci.o ( = code
7804 which can be inserted in and removed from the running kernel
7805 whenever you want). If you want to compile it as a module, say M
7806 here and read Documentation/modules.txt.
7810 This is a driver for ISA SBNI12-xx cards which are low cost
7811 alternatives to leased line modems. Say Y if you want to insert
7812 the driver into the kernel or say M to compile it as a module (the
7813 module will be called sbni.o).
7815 You can find more information and last versions of drivers and
7816 utilities at http://www.granch.ru . If you have any question you
7817 can send email to sbni@granch.ru.
7822 CONFIG_WAN_ROUTER_DRIVERS
7823 If you have a WAN interface card and you want your Linux box to act
7824 as a WAN router, thereby connecting you Local Area Network to the
7825 outside world over the WAN connection, say Y here and then to the
7826 driver for your card below. In addition, you need to say Y to "Wan
7829 You will need the wan-tools package which is available from
7830 ftp://ftp.sangoma.com . Read Documentation/networking/wan-router.txt
7831 for more information.
7833 Note that the answer to this question won't directly affect the
7834 kernel: saying N will just cause this configure script to skip all
7835 the questions about WAN router drivers. If unsure, say N.
7837 Sangoma WANPIPE(tm) multiprotocol cards
7838 CONFIG_VENDOR_SANGOMA
7839 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com ) is
7840 a family of intelligent multiprotocol WAN adapters with data
7841 transfer rates up to T1 (1.544 Mbps). They are also known as
7842 Synchronous Data Link Adapters (SDLA) and designated S502E(A), S503
7843 or S508. These cards support the X.25, Frame Relay, and PPP
7844 protocols. If you have one or more of these cards, say Y to this
7845 option; you may then also want to read the file
7846 Documentation/networking/wanpipe.txt. The next questions will ask
7847 you about the protocols you want the driver to support.
7849 The driver will be compiled as a module ( = code which can be
7850 inserted in and removed from the running kernel whenever you want).
7851 The module will be called wanpipe.o. For general information about
7852 modules read Documentation/modules.txt.
7854 Maximum number of cards
7855 CONFIG_WANPIPE_CARDS
7856 Enter number of WANPIPE adapters installed in your machine. The
7857 driver can support up to 8 cards. You may enter more than you
7858 actually have if you plan to add more cards in the future without
7859 re-compiling the driver, but remember that in this case you'll waste
7860 some kernel memory (about 1K per card).
7862 WANPIPE Cisco HDLC support
7863 CONFIG_WANPIPE_CHDLC
7864 Say Y to this option if you are planning to connect a WANPIPE card
7865 to a connection which uses the synchronous Cisco HDLC (High-level
7866 Data Link Control) protocol. This protocol is often used on
7867 high-speed leased lines like T1/E1.
7869 WANPIPE X.25 support
7871 Say Y to this option if you are planning to connect a WANPIPE card
7872 to an X.25 network. You should then also have said Y to "CCITT X.25
7873 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
7874 X.25 support will not be included in the driver (saves about 16 KB
7877 WANPIPE Frame Relay support
7879 Say Y to this option if you are planning to connect a WANPIPE card
7880 to a frame relay network. You should then also have said Y to "Frame
7881 Relay (DLCI) support", above. If you say N, the frame relay
7882 support will not be included in the driver (saves about 16 KB of
7887 Say Y to this option if you are planning to connect a WANPIPE card
7888 to a leased line using Point-to-Point protocol (PPP). You should
7889 then also have said Y to "PPP (point-to-point) support", above. If
7890 you say N, the PPP support will not be included in the driver (saves
7891 about 16 KB of kernel memory).
7893 MultiGate/COMX support
7895 Say Y if you want to use any board from the MultiGate (COMX) family.
7896 These boards are synchronous serial adapters for the PC,
7897 manufactured by ITConsult-Pro Co, Hungary.
7899 Read linux/Documentation/networking/comx.txt for help on configuring
7900 and using COMX interfaces. Further info on these cards can be found
7901 at http://www.itc.hu or <info@itc.hu>.
7903 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
7906 If you want to compile this as a module, say M and read
7907 Documentation/modules.txt. The module will be called comx.o.
7909 COMX/CMX/HiCOMX board support
7911 Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the
7912 MultiGate family. Say Y if you have one of these.
7914 You will need additional firmware to use these cards, which are
7915 downloadable from ftp://ftp.itc.hu/.
7917 If you want to compile this as a module, say M and read
7918 Documentation/modules.txt. The module will be called comx-hw-comx.o.
7920 LoCOMX board support
7921 CONFIG_COMX_HW_LOCOMX
7922 Hardware driver for the 'LoCOMX' board from the MultiGate family.
7923 Say Y if you have a board like this.
7925 If you want to compile this as a module, say M and read
7926 Documentation/modules.txt. The module will be called
7929 MixCOM board support
7930 CONFIG_COMX_HW_MIXCOM
7931 Hardware driver for the 'MixCOM' board from the MultiGate family.
7932 Say Y if you have a board like this.
7934 If you want to use the watchdog device on this card, you should
7935 select it in the Watchdog Cards section of the Character Devices
7936 configuration. The ISDN interface of this card is Teles 16.3
7937 compatible, you should enable it in the ISDN configuration menu. The
7938 driver for the flash ROM of this card is available separately on
7941 If you want to compile this as a module, say M and read
7942 Documentation/modules.txt. The module will be called
7947 Hardware driver for the TCO timer built into the Intel i810 and i815
7948 chipset family. The TCO (Total Cost of Ownership) timer is a watchdog
7949 timer that will reboot the machine after it's second expiration. The
7950 expiration time can be configured by commandline argument
7951 "i810_margin=<n>" where <n> is the counter initial value. It is
7952 decremented every 0.6 secs, the default is 50 which gives a timeout
7953 of 30 seconds and one minute until reset.
7955 On some motherboards the driver may fail to reset the chipset's
7956 NO_REBOOT flag which prevents the watchdog from rebooting the machine.
7957 If this is the case you will get a kernel message like
7958 "i810tco init: failed to reset NO_REBOOT flag".
7960 If you want to compile this as a module, say M and read
7961 Documentation/modules.txt. The module will be called
7964 MultiGate Cisco-HDLC and synchronous PPP protocol support
7965 CONFIG_COMX_PROTO_PPP
7966 Cisco-HDLC and synchronous PPP protocol driver for all MultiGate
7967 boards. Say Y if you want to use either protocol on your MultiGate
7970 If you want to compile this as a module, say M and read
7971 Documentation/modules.txt. The module will be called
7974 MultiGate LAPB protocol support
7975 CONFIG_COMX_PROTO_LAPB
7976 LAPB protocol driver for all MultiGate boards. Say Y if you
7977 want to use this protocol on your MultiGate boards.
7979 If you want to compile this as a module, say M and read
7980 Documentation/modules.txt. The module will be called
7983 MultiGate Frame Relay protocol support
7984 CONFIG_COMX_PROTO_FR
7985 Frame Relay protocol driver for all MultiGate boards. Say Y if you
7986 want to use this protocol on your MultiGate boards.
7988 If you want to compile this as a module, say M and read
7989 Documentation/modules.txt. The module will be called
7992 Cyclom 2X(tm) multiprotocol cards (EXPERIMENTAL)
7993 CONFIG_CYCLADES_SYNC
7994 Cyclom 2X from Cyclades Corporation (http://www.cyclades.com and
7995 http://www.cyclades.com.br) is an intelligent multiprotocol WAN
7996 adapter with data transfer rates up to 512 Kbps. These cards support
7997 the X.25 and SNA related protocols. If you have one or more of these
7998 cards, say Y to this option. The next questions will ask you about
7999 the protocols you want the driver to support (for now only X.25 is
8002 While no documentation is available at this time please grab the
8003 wanconfig tarball in http://www.conectiva.com.br/~acme/cycsyn-devel
8004 (with minor changes to make it compile with the current wanrouter
8005 include files; efforts are being made to use the original package
8006 available at ftp://ftp.sangoma.com ).
8008 Feel free to contact me or the cycsyn-devel mailing list at
8009 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
8010 additional details, I hope to have documentation available as soon
8011 as possible. (Cyclades Brazil is writing the Documentation).
8013 The driver will be compiled as a module ( = code which can be
8014 inserted in and removed from the running kernel whenever you want).
8015 The module will be called cyclomx.o. For general information about
8016 modules read Documentation/modules.txt.
8018 Cyclom 2X X.25 support
8020 Say Y to this option if you are planning to connect a Cyclom 2X card
8023 If you say N, the X.25 support will not be included in the driver
8024 (saves about 11 KB of kernel memory).
8026 Ethernet (10 or 100Mbit)
8028 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
8029 type of Local Area Network (LAN) in universities and companies.
8031 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
8032 coaxial cable, linking computers in a chain), 10BASE-T or twisted
8033 pair (10 Mbps over twisted pair cable, linking computers to central
8034 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
8035 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
8036 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
8037 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
8038 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
8039 Ethernet (1 Gbps over optical fiber or short copper links).
8041 If your Linux machine will be connected to an Ethernet and you have
8042 an Ethernet network interface card (NIC) installed in your computer,
8043 say Y here and read the Ethernet-HOWTO, available from
8044 http://www.linuxdoc.org/docs.html#howto . You will then also have
8045 to say Y to the driver for your particular NIC.
8047 Note that the answer to this question won't directly affect the
8048 kernel: saying N will just cause this configure script to skip all
8049 the questions about Ethernet network cards. If unsure, say N.
8051 Western Digital/SMC cards
8052 CONFIG_NET_VENDOR_SMC
8053 If you have a network (Ethernet) card belonging to this class, say Y
8054 and read the Ethernet-HOWTO, available from
8055 http://www.linuxdoc.org/docs.html#howto .
8057 Note that the answer to this question doesn't directly affect the
8058 kernel: saying N will just cause this configure script to skip all
8059 the questions about Western Digital cards. If you say Y, you will be
8060 asked for your specific card in the following questions.
8064 If you have a network (Ethernet) card of this type, say Y and read
8065 the Ethernet-HOWTO, available from
8066 http://www.linuxdoc.org/docs.html#howto .
8068 This driver is also available as a module ( = code which can be
8069 inserted in and removed from the running kernel whenever you want).
8070 The module will be called wd.o. If you want to compile it as a
8071 module, say M here and read Documentation/modules.txt as well as
8072 Documentation/networking/net-modules.txt.
8074 SMC Ultra MCA support
8076 If you have a network (Ethernet) card of this type and are running
8077 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
8078 available from http://www.linuxdoc.org/docs.html#howto .
8080 This driver is also available as a module ( = code which can be
8081 inserted in and removed from the running kernel whenever you want).
8082 The module will be called smc-mca.o. If you want to compile it as a
8083 module, say M here and read Documentation/modules.txt as well as
8084 Documentation/networking/net-modules.txt.
8088 If you have a network (Ethernet) card of this type, say Y and read
8089 the Ethernet-HOWTO, available from
8090 http://www.linuxdoc.org/docs.html#howto .
8092 Important: There have been many reports that, with some motherboards
8093 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
8094 such as some BusLogic models) causes corruption problems with many
8095 operating systems. The Linux smc-ultra driver has a work-around for
8096 this but keep it in mind if you have such a SCSI card and have
8099 This driver is also available as a module ( = code which can be
8100 inserted in and removed from the running kernel whenever you want).
8101 The module will be called smc-ultra.o. If you want to compile it as
8102 a module, say M here and read Documentation/modules.txt as well as
8103 Documentation/networking/net-modules.txt.
8105 SMC Ultra32 EISA support
8107 If you have a network (Ethernet) card of this type, say Y and read
8108 the Ethernet-HOWTO, available from
8109 http://www.linuxdoc.org/docs.html#howto .
8111 This driver is also available as a module ( = code which can be
8112 inserted in and removed from the running kernel whenever you want).
8113 The module will be called smc-ultra32.o. If you want to compile it
8114 as a module, say M here and read Documentation/modules.txt as well
8115 as Documentation/networking/net-modules.txt.
8119 This is support for the SMC9xxx based Ethernet cards. Choose this
8120 option if you have a DELL laptop with the docking station, or
8121 another SMC9192/9194 based chipset. Say Y if you want it compiled
8122 into the kernel, and read the file
8123 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
8124 from http://www.linuxdoc.org/docs.html#howto .
8126 This driver is also available as a module ( = code which can be
8127 inserted in and removed from the running kernel whenever you
8128 want). The module will be called smc9194.o. If you want to compile
8129 it as a module, say M here and read Documentation/modules.txt as
8130 well as Documentation/networking/net-modules.txt.
8134 This driver is for NE2000 compatible PCI cards. It will not work
8135 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
8136 support" below). If you have a PCI NE2000 network (Ethernet) card,
8137 say Y and read the Ethernet-HOWTO, available from
8138 http://www.linuxdoc.org/docs.html#howto .
8140 This driver is also available as a module ( = code which can be
8141 inserted in and removed from the running kernel whenever you want).
8142 The module will be called ne2k-pci.o. If you want to compile it as a
8143 module, say M here and read Documentation/modules.txt as well as
8144 Documentation/networking/net-modules.txt.
8146 Racal-Interlan (Micom) NI cards
8147 CONFIG_NET_VENDOR_RACAL
8148 If you have a network (Ethernet) card belonging to this class, such
8149 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
8150 available from http://www.linuxdoc.org/docs.html#howto .
8152 Note that the answer to this question doesn't directly affect the
8153 kernel: saying N will just cause this configure script to skip all
8154 the questions about NI cards. If you say Y, you will be asked for
8155 your specific card in the following questions.
8157 NI5010 support (EXPERIMENTAL)
8159 If you have a network (Ethernet) card of this type, say Y and read
8160 the Ethernet-HOWTO, available from
8161 http://www.linuxdoc.org/docs.html#howto . Note that this is still
8164 This driver is also available as a module ( = code which can be
8165 inserted in and removed from the running kernel whenever you want).
8166 The module will be called ni5010.o. If you want to compile it as a
8167 module, say M here and read Documentation/modules.txt as well as
8168 Documentation/networking/net-modules.txt.
8172 If you have a network (Ethernet) card of this type, say Y and read
8173 the Ethernet-HOWTO, available from
8174 http://www.linuxdoc.org/docs.html#howto .
8176 This driver is also available as a module ( = code which can be
8177 inserted in and removed from the running kernel whenever you want).
8178 The module will be called ni52.o. If you want to compile it as a
8179 module, say M here and read Documentation/modules.txt as well as
8180 Documentation/networking/net-modules.txt.
8184 If you have a network (Ethernet) card of this type, say Y and read
8185 the Ethernet-HOWTO, available from
8186 http://www.linuxdoc.org/docs.html#howto .
8188 This driver is also available as a module ( = code which can be
8189 inserted in and removed from the running kernel whenever you want).
8190 The module will be called ni65.o. If you want to compile it as a
8191 module, say M here and read Documentation/modules.txt as well as
8192 Documentation/networking/net-modules.txt.
8194 RealTek 8129 (not 8019/8029/8139!) support (EXPERIMENTAL)
8196 This is NOT for RTL-8139 cards. Instead, select the 8139too driver
8198 This is a driver for the Fast Ethernet PCI network cards based on
8199 the RTL8129 chip. If you have one of those, say Y and
8200 read the Ethernet-HOWTO, available from
8201 http://www.linuxdoc.org/docs.html#howto .
8203 If you want to compile this driver as a module ( = code which can be
8204 inserted in and removed from the running kernel whenever you want),
8205 say M here and read Documentation/modules.txt. This is recommended.
8206 The module will be called rtl8129.o.
8208 RealTek RTL-8139 PCI Fast Ethernet Adapter support
8210 This is a driver for the Fast Ethernet PCI network cards based on
8211 the RTL8139 chips. If you have one of those, say Y and read
8212 Documentation/networking/8139too.txt as well as the Ethernet-HOWTO,
8213 available from http://www.linuxdoc.org/docs.html#howto .
8215 If you want to compile this driver as a module ( = code which can be
8216 inserted in and removed from the running kernel whenever you want),
8217 say M here and read Documentation/modules.txt. This is recommended.
8218 The module will be called 8139too.o.
8220 SiS 900 PCI Fast Ethernet Adapter support
8222 This is a driver for the Fast Ethernet PCI network cards based on
8223 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
8224 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
8225 read the Ethernet-HOWTO, available at
8226 http://www.linuxdoc.org/docs.html#howto . Please read
8227 Documentation/networking/sis900.txt and comments at the beginning of
8228 drivers/net/sis900.c for more information.
8230 This driver also supports AMD 79C901 HomePNA so that you can use
8231 your phone line as a network cable.
8233 If you want to compile this driver as a module ( = code which can be
8234 inserted in and removed from the running kernel whenever you want),
8235 say M here and read Documentation/modules.txt. This is recommended.
8236 The module will be called sis900.o.
8238 Packet Engines Yellowfin Gigabit-NIC support
8240 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
8241 adapter. This adapter is used by the Beowulf Linux cluster project.
8242 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
8243 more information about this driver in particular and Beowulf in
8246 If you want to compile this driver as a module ( = code which can be
8247 inserted in and removed from the running kernel whenever you want),
8248 say M here and read Documentation/modules.txt. This is recommended.
8249 The module will be called yellowfin.o.
8251 General Instruments Surfboard 1000
8253 This is a driver for the General Instrument (also known as
8254 NextLevel) SURFboard 1000 internal
8255 cable modem. This is an ISA card which is used by a number of cable
8256 TV companies to provide cable modem access. It's a one-way
8257 downstream-only cable modem, meaning that your upstream net link is
8258 provided by your regular phone modem.
8260 At present this driver only compiles as a module, so say M here if
8261 you have this card. The module will be called sb1000.o. Then read
8262 Documentation/networking/README.sb1000 for information on how to use
8263 this module, as it needs special ppp scripts for establishing a
8264 connection. Further documentation and the necessary scripts can be
8267 http://www.jacksonville.net/~fventuri/
8268 http://home.adelphia.net/~siglercm/sb1000.html
8269 http://linuxpower.cx/~cable/
8271 If you don't have this card, of course say N.
8273 Adaptec Starfire support (EXPERIMENTAL)
8274 CONFIG_ADAPTEC_STARFIRE
8275 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
8276 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
8277 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
8280 If you want to compile this driver as a module ( = code which can be
8281 inserted in and removed from the running kernel whenever you want),
8282 say M here and read Documentation/modules.txt. This is recommended.
8283 The module will be called starfile.o.
8285 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
8287 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
8288 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
8289 adapter. The driver allows for using the Jumbo Frame option (9000
8290 bytes/frame) however it requires that your switches can handle this
8291 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
8294 If you want to compile this driver as a module ( = code which can be
8295 inserted in and removed from the running kernel whenever you want),
8296 say M here and read Documentation/modules.txt. This is recommended.
8297 The module will be called acenic.o.
8299 Omit support for older Tigon I based AceNICs
8300 CONFIG_ACENIC_OMIT_TIGON_I
8301 Say Y here if you only have Tigon II based AceNICs and want to leave
8302 out support for the older Tigon I based cards which are no longer
8303 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
8304 version)). This will reduce the size of the driver object by
8305 app. 100KB. If you are not sure whether your card is a Tigon I or a
8306 Tigon II, say N here.
8308 The safe and default value for this is N.
8310 SysKonnect SK-98xx support
8312 Say Y here if you have a SysKonnect SK-98xx Gigabit Ethernet Server
8313 Adapter. The following adapters are supported by this driver:
8314 - SK-9841 (single link 1000Base-LX)
8315 - SK-9842 (dual link 1000Base-LX)
8316 - SK-9843 (single link 1000Base-SX)
8317 - SK-9844 (dual link 1000Base-SX)
8318 - SK-9821 (single link 1000Base-T)
8319 - SK-9822 (dual link 1000Base-T)
8320 - SK-9861 (single link Volition connector)
8321 - SK-9862 (dual link Volition connector)
8322 The driver also supports the following adapters from Allied Telesyn:
8325 The dual link adapters support a link-failover feature.
8326 Read Documentation/networking/sk98lin.txt for information about
8327 optional driver parameters.
8328 Questions concerning this driver may be addressed to:
8331 If you want to compile this driver as a module ( = code which can be
8332 inserted in and removed from the running kernel whenever you want),
8333 say M here and read Documentation/modules.txt. This is recommended.
8334 The module will be called sk98lin.o.
8336 MyriCOM Gigabit Ethernet support
8338 This driver supports MyriCOM Sbus gigabit ethernet cards.
8340 If you want to compile this driver as a module ( = code which can be
8341 inserted in and removed from the running kernel whenever you want),
8342 say M here and read Documentation/modules.txt. This is recommended.
8343 The module will be called myri_sbus.o.
8345 AMD LANCE and PCnet (AT1500 and NE2100) support
8347 If you have a network (Ethernet) card of this type, say Y and read
8348 the Ethernet-HOWTO, available from
8349 http://www.linuxdoc.org/docs.html#howto . Some LinkSys cards are
8352 If you want to compile this driver as a module ( = code which can be
8353 inserted in and removed from the running kernel whenever you want),
8354 say M here and read Documentation/modules.txt. This is recommended.
8355 The module will be called lance.o.
8359 If you have a network (Ethernet) card of this type, say Y and read
8360 the Ethernet-HOWTO, available from
8361 http://www.linuxdoc.org/docs.html#howto .
8364 CONFIG_NET_VENDOR_3COM
8365 If you have a network (Ethernet) card belonging to this class, say Y
8366 and read the Ethernet-HOWTO, available from
8367 http://www.linuxdoc.org/docs.html#howto .
8369 Note that the answer to this question doesn't directly affect the
8370 kernel: saying N will just cause this configure script to skip all
8371 the questions about 3COM cards. If you say Y, you will be asked for
8372 your specific card in the following questions.
8376 If you have a network (Ethernet) card of this type, say Y and read
8377 the Ethernet-HOWTO, available from
8378 http://www.linuxdoc.org/docs.html#howto . Also, consider buying a
8379 new card, since the 3c501 is slow, broken, and obsolete: you will
8380 have problems. Some people suggest to ping ("man ping") a nearby
8381 machine every minute ("man cron") when using this card.
8383 This driver is also available as a module ( = code which can be
8384 inserted in and removed from the running kernel whenever you want).
8385 The module will be called 3c501.o. If you want to compile it as a
8386 module, say M here and read Documentation/modules.txt as well as
8387 Documentation/networking/net-modules.txt.
8391 If you have a network (Ethernet) card of this type, say Y and read
8392 the Ethernet-HOWTO, available from
8393 http://www.linuxdoc.org/docs.html#howto .
8395 This driver is also available as a module ( = code which can be
8396 inserted in and removed from the running kernel whenever you want).
8397 The module will be called 3c503.o. If you want to compile it as a
8398 module, say M here and read Documentation/modules.txt as well as
8399 Documentation/networking/net-modules.txt.
8403 Information about this network (Ethernet) card can be found in
8404 Documentation/networking/3c505.txt. If you have a card of this type,
8405 say Y and read the Ethernet-HOWTO, available from
8406 http://www.linuxdoc.org/docs.html#howto .
8408 If you want to compile this as a module ( = code which can be
8409 inserted in and removed from the running kernel whenever you want),
8410 say M here and read Documentation/modules.txt as well as
8411 Documentation/networking/net-modules.txt. The module will be called
8414 3c507 support (EXPERIMENTAL)
8416 If you have a network (Ethernet) card of this type, say Y and read
8417 the Ethernet-HOWTO, available from
8418 http://www.linuxdoc.org/docs.html#howto .
8420 This driver is also available as a module ( = code which can be
8421 inserted in and removed from the running kernel whenever you want).
8422 The module will be called 3c507.o. If you want to compile it as a
8423 module, say M here and read Documentation/modules.txt as well as
8424 Documentation/networking/net-modules.txt.
8428 If you have a network (Ethernet) card of this type, say Y and read
8429 the Ethernet-HOWTO, available from
8430 http://www.linuxdoc.org/docs.html#howto .
8432 This driver is also available as a module ( = code which can be
8433 inserted in and removed from the running kernel whenever you want).
8434 The module will be called 3c523.o. If you want to compile it as a
8435 module, say M here and read Documentation/modules.txt as well as
8436 Documentation/networking/net-modules.txt.
8440 If you have a network (Ethernet) card of this type, say Y and read
8441 the Ethernet-HOWTO, available from
8442 http://www.linuxdoc.org/docs.html#howto .
8444 This driver is also available as a module ( = code which can be
8445 inserted in and removed from the running kernel whenever you want).
8446 The module will be called 3c527.o. If you want to compile it as a
8447 module, say M here and read Documentation/modules.txt as well as
8448 Documentation/networking/net-modules.txt.
8452 If you have a network (Ethernet) card belonging to the 3Com
8453 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
8454 from http://www.linuxdoc.org/docs.html#howto .
8456 If your card is not working you may need to use the DOS
8457 setup disk to disable Plug & Play mode, and to select the default
8460 If you want to compile this as a module ( = code which can be
8461 inserted in and removed from the running kernel whenever you want),
8462 say M here and read Documentation/modules.txt as well as
8463 Documentation/networking/net-modules.txt. The module will be called
8466 3c515 ISA Fast EtherLink
8468 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
8469 network card, say Y and read the Ethernet-HOWTO, available from
8470 http://www.linuxdoc.org/docs.html#howto .
8472 If you want to compile this as a module ( = code which can be
8473 inserted in and removed from the running kernel whenever you want),
8474 say M here and read Documentation/modules.txt as well as
8475 Documentation/networking/net-modules.txt. The module will be called
8478 3c59x/3c90x/3c575_Cardbus series "Vortex/Boomerang/Cyclone" support
8480 This option enables driver support for a large number of 10mbps and
8481 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
8483 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
8484 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
8485 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
8486 "Tornado" (3c905) PCI
8487 "Hurricane" (3c555/3cSOHO) PCI
8489 If you have such a card, say Y and read the Ethernet-HOWTO, available
8490 from http://www.linuxdoc.org/docs.html#howto . More specific
8491 information is in Documentation/networking/vortex.txt and in the
8492 comments at the beginning of drivers/net/3c59x.c.
8494 If you want to compile this as a module ( = code which can be
8495 inserted in and removed from the running kernel whenever you want),
8496 say M here and read Documentation/modules.txt as well as
8497 Documentation/networking/net-modules.txt.
8501 If your network (Ethernet) card hasn't been mentioned yet and its
8502 bus system (that's the way the cards talks to the other components
8503 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
8504 Make sure you know the name of your card. Read the Ethernet-HOWTO,
8505 available from http://www.linuxdoc.org/docs.html#howto .
8509 Note that the answer to this question doesn't directly affect the
8510 kernel: saying N will just cause this configure script to skip all
8511 the remaining ISA network card questions. If you say Y, you will be
8512 asked for your specific card in the following questions.
8514 Generic ARCnet support
8516 If you have a network card of this type, say Y and check out the
8517 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
8519 You need both this driver, and the driver for the particular ARCnet
8520 chipset of your card. If you don't know, then it's probably a
8521 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
8524 You might also want to have a look at the Ethernet-HOWTO, available
8525 from http://www.linuxdoc.org/docs.html#howto (even though ARCnet
8526 is not really Ethernet).
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 arcnet.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.
8534 Enable arc0e (ARCnet "ether-encap" packet format)
8536 This allows you to use "Ethernet encapsulation" with your ARCnet
8537 card via the virtual arc0e device. You only need arc0e if you want
8538 to talk to nonstandard ARCnet software, specifically,
8539 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
8540 communicate with industry-standard RFC1201 implementations, like the
8541 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
8542 is included automatically as the arc0 device. Please read the
8543 ARCnet documentation in Documentation/networking/arcnet.txt for more
8544 information about using arc0e and arc0s.
8546 Enable old ARCNet packet format (RFC 1051)
8548 This allows you to use RFC1051 with your ARCnet card via the virtual
8549 arc0s device. You only need arc0s if you want to talk to ARCnet
8550 software complying with the "old" standard, specifically, the DOS
8551 arcnet.com packet driver, Amigas running AmiTCP, and some variants
8552 of NetBSD. You do not need to say Y here to communicate with
8553 industry-standard RFC1201 implementations, like the arcether.com
8554 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
8555 automatically as the arc0 device. Please read the ARCnet
8556 documentation in Documentation/networking/arcnet.txt for more
8557 information about using arc0e and arc0s.
8559 ARCnet COM90xx (normal) chipset driver
8560 CONFIG_ARCNET_COM90xx
8561 This is the chipset driver for the standard COM90xx cards. If you
8562 have always used the old ARCnet driver without knowing what type of
8563 card you had, this is probably the one for you.
8565 This driver is also available as a module ( = code which can be
8566 inserted in and removed from the running kernel whenever you want).
8567 The module will be called com90xx.o. If you want to compile it as a
8568 module, say M here and read Documentation/modules.txt as well as
8569 Documentation/networking/net-modules.txt.
8571 ARCnet COM90xx (IO mapped) chipset driver
8572 CONFIG_ARCNET_COM90xxIO
8573 This is the chipset driver for the COM90xx cards, using them in
8574 IO-mapped mode instead of memory-mapped mode. This is slower than
8575 the normal driver. Only use it if your card doesn't support shared
8578 This driver is also available as a module ( = code which can be
8579 inserted in and removed from the running kernel whenever you want).
8580 The module will be called com90io.o. If you want to compile it as a
8581 module, say M here and read Documentation/modules.txt as well as
8582 Documentation/networking/net-modules.txt.
8584 ARCnet COM90xx (RIM I) chipset driver
8586 This is yet another chipset driver for the COM90xx cards, but this
8587 time only using memory-mapped mode, and no IO ports at all. This
8588 driver is completely untested, so if you have one of these cards,
8589 please mail dwmw2@infradead.org, especially if it works!
8591 This driver is also available as a module ( = code which can be
8592 inserted in and removed from the running kernel whenever you
8593 want). The module will be called arc-rimi.o. If you want to compile
8594 it as a module, say M here and read Documentation/modules.txt as
8595 well as Documentation/networking/net-modules.txt.
8597 ARCnet COM20020 chipset driver
8598 CONFIG_ARCNET_COM20020
8599 This is the driver for the new COM20020 chipset. It supports such
8600 things as promiscuous mode, so packet sniffing is possible, and
8601 extra diagnostic information.
8603 This driver is also available as a module ( = code which can be
8604 inserted in and removed from the running kernel whenever you want).
8605 The module will be called com20020.o. If you want to compile it as a
8606 module, say M here and read Documentation/modules.txt as well as
8607 Documentation/networking/net-modules.txt.
8609 Cabletron E21xx support
8611 If you have a network (Ethernet) card of this type, say Y and read
8612 the Ethernet-HOWTO, available from
8613 http://www.linuxdoc.org/docs.html#howto .
8615 This driver is also available as a module ( = code which can be
8616 inserted in and removed from the running kernel whenever you want).
8617 The module will be called e2100.o. If you want to compile it as a
8618 module, say M here and read Documentation/modules.txt as well as
8619 Documentation/networking/net-modules.txt.
8623 Support for CS89x0 chipset based Ethernet cards. If you have a
8624 network (Ethernet) card of this type, say Y and read the
8625 Ethernet-HOWTO, available from
8626 http://www.linuxdoc.org/docs.html#howto as well as
8627 Documentation/networking/cs89x0.txt.
8629 If you want to compile this as a module ( = code which can be
8630 inserted in and removed from the running kernel whenever you want),
8631 say M here and read Documentation/modules.txt as well as
8632 Documentation/networking/net-modules.txt. The module will be called
8637 If you have a network (Ethernet) card of this type, say Y and read
8638 the Ethernet-HOWTO, available from
8639 http://www.linuxdoc.org/docs.html#howto as well as
8640 drivers/net/depca.c.
8642 If you want to compile this as a module ( = code which can be
8643 inserted in and removed from the running kernel whenever you want),
8644 say M here and read Documentation/modules.txt as well as
8645 Documentation/networking/net-modules.txt. The module will be called
8648 EtherWorks 3 support
8650 This driver supports the DE203, DE204 and DE205 network (Ethernet)
8651 cards. If this is for you, say Y and read
8652 Documentation/networking/ewrk3.txt in the kernel source as well as
8653 the Ethernet-HOWTO, available from
8654 http://www.linuxdoc.org/docs.html#howto .
8656 If you want to compile this as a module ( = code which can be
8657 inserted in and removed from the running kernel whenever you want),
8658 say M here and read Documentation/modules.txt as well as
8659 Documentation/networking/net-modules.txt. The module will be called
8664 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
8665 is for you, read the Ethernet-HOWTO, available from
8666 http://www.linuxdoc.org/docs.html#howto .
8668 If you want to compile this as a module ( = code which can be
8669 inserted in and removed from the running kernel whenever you want),
8670 say M here and read Documentation/modules.txt as well as
8671 Documentation/networking/net-modules.txt. The module will be called
8676 If you have a network (Ethernet) card of this type, say Y and read
8677 the Ethernet-HOWTO, available from
8678 http://www.linuxdoc.org/docs.html#howto .
8680 This driver is also available as a module ( = code which can be
8681 inserted in and removed from the running kernel whenever you want).
8682 If you want to compile it as a module, say M here and read
8683 Documentation/modules.txt as well as
8684 Documentation/networking/net-modules.txt. The module will be called
8687 FMV-181/182/183/184 support
8689 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
8690 say Y and read the Ethernet-HOWTO, available from
8691 http://www.linuxdoc.org/docs.html#howto .
8693 If you use an FMV-183 or FMV-184 and it is not working, you may need
8694 to disable Plug & Play mode of the card.
8696 This driver is also available as a module ( = code which can be
8697 inserted in and removed from the running kernel whenever you want).
8698 The module will be called fmv18x.o. If you want to compile it as a
8699 module, say M here and read Documentation/modules.txt as well as
8700 Documentation/networking/net-modules.txt.
8702 EtherExpress PRO support
8704 If you have a network (Ethernet) card of this type, say Y. This
8705 driver supports intel i82595{FX,TX} based boards. Note however
8706 that the EtherExpress PRO/100 Ethernet card has its own separate
8707 driver. Please read the Ethernet-HOWTO, available from
8708 http://www.linuxdoc.org/docs.html#howto .
8710 This driver is also available as a module ( = code which can be
8711 inserted in and removed from the running kernel whenever you want).
8712 The module will be called eepro.o. If you want to compile it as a
8713 module, say M here and read Documentation/modules.txt as well as
8714 Documentation/networking/net-modules.txt.
8716 EtherExpress support
8718 If you have an EtherExpress16 network (Ethernet) card, say Y and
8719 read the Ethernet-HOWTO, available from
8720 http://www.linuxdoc.org/docs.html#howto . Note that the Intel
8721 EtherExpress16 card used to be regarded as a very poor choice
8722 because the driver was very unreliable. We now have a new driver
8723 that should do better.
8725 If you want to compile this driver as a module ( = code which can be
8726 inserted in and removed from the running kernel whenever you want),
8727 say M here and read Documentation/modules.txt as well as
8728 Documentation/networking/net-modules.txt. The module will be called
8731 Packet Engines Hamachi GNIC-II support
8733 If you have a Gigabit Ethernet card of this type, say Y and read
8734 the Ethernet-HOWTO, available from
8735 http://www.linuxdoc.org/docs.html#howto .
8737 If you want to compile this as a module ( = code which can be
8738 inserted in and removed from the running kernel whenever you want),
8739 say M here and read Documentation/modules.txt as well as
8740 Documentation/networking/net-modules.txt. The module will be called
8743 HP PCLAN+ (27247B and 27252A) support
8745 If you have a network (Ethernet) card of this type, say Y and read
8746 the Ethernet-HOWTO, available from
8747 http://www.linuxdoc.org/docs.html#howto .
8749 This driver is also available as a module ( = code which can be
8750 inserted in and removed from the running kernel whenever you want).
8751 The module will be called hp-plus.o. If you want to compile it as a
8752 module, say M here and read Documentation/modules.txt as well as
8753 Documentation/networking/net-modules.txt.
8755 HP PCLAN (27245 and other 27xxx series) support
8757 If you have a network (Ethernet) card of this type, say Y and read
8758 the Ethernet-HOWTO, available from
8759 http://www.linuxdoc.org/docs.html#howto .
8761 This driver is also available as a module ( = code which can be
8762 inserted in and removed from the running kernel whenever you want).
8763 The module will be called hp.o. If you want to compile it as a
8764 module, say M here and read Documentation/modules.txt as well as
8765 Documentation/networking/net-modules.txt.
8767 HP 10/100VG PCLAN (ISA, EISA, PCI) support
8769 If you have a network (Ethernet) card of this type, say Y and read
8770 the Ethernet-HOWTO, available from
8771 http://www.linuxdoc.org/docs.html#howto .
8773 If you want to compile this as a module ( = code which can be
8774 inserted in and removed from the running kernel whenever you want),
8775 say M here and read Documentation/modules.txt as well as
8776 Documentation/networking/net-modules.txt. The module will be called
8779 NE2000/NE1000 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 . Many Ethernet cards
8784 without a specific driver are compatible with NE2000.
8786 If you have a PCI NE2000 card however, say N here and Y to "PCI
8787 NE2000 support", above. If you have a NE2000 card and are running on
8788 an MCA system (a bus system used on some IBM PS/2 computers and
8789 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
8792 This driver is also available as a module ( = code which can be
8793 inserted in and removed from the running kernel whenever you want).
8794 The module will be called ne.o. If you want to compile it as a
8795 module, say M here and read Documentation/modules.txt as well as
8796 Documentation/networking/net-modules.txt.
8798 National Semiconductor DP83810 series PCI Ethernet support
8800 This driver is for the National Semiconductor DP83810 series,
8801 including the 83815 chip.
8802 More specific information and updates are available from
8803 http://www.scyld.com/network/natsemi.html
8807 If you have a network (Ethernet) card of this type, say Y and read
8808 the Ethernet-HOWTO, available from
8809 http://www.linuxdoc.org/docs.html#howto .
8811 NE/2 (ne2000 MCA version) support
8813 If you have a network (Ethernet) card of this type, say Y and read
8814 the Ethernet-HOWTO, available from
8815 http://www.linuxdoc.org/docs.html#howto .
8817 This driver is also available as a module ( = code which can be
8818 inserted in and removed from the running kernel whenever you want).
8819 The module will be called ne2.o. If you want to compile it as a
8820 module, say M here and read Documentation/modules.txt as well as
8821 Documentation/networking/net-modules.txt.
8825 These are Micro Channel ethernet adapters. You need to say Y to "MCA
8826 support" in order to use this driver. Supported cards are the SKnet
8827 Junior MC2 and the SKnet MC2(+). The driver automatically
8828 distinguishes between the two cards. Note that using multiple boards
8829 of different type hasn't been tested with this driver. Say Y if you
8830 have one of these ethernet adapters.
8832 This driver is also available as a module ( = code which can be
8833 inserted in and removed from the running kernel whenever you want).
8834 The module is called sk_mca.o. If you want to compile it as a
8835 module, say M here and read Documentation/modules.txt as well as
8836 Documentation/networking/net-modules.txt.
8838 IBM LAN Adapter/A support
8840 This is a Micro Channel ethernet adapter. You need to set CONFIG_MCA
8841 to use this driver. It is both available as an in-kernel driver and
8842 as a module ( = code which can be inserted in and removed from the
8843 running kernel whenever you want). If you want to compile it as a module,
8844 say M here and read Documentation/modules.txt as well as
8845 Documentation/networking/net-modules.txt. If you plan to use more than
8846 one network card under linux, read the Multiple-Ethernet-mini-HOWTO,
8847 available from sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini. The only
8848 currently supported card is the IBM LAN Adapter/A for Ethernet. It will
8849 both support 16K and 32K memory windows, however a 32K window gives
8850 a better security against packet losses. Usage of multiple boards with
8851 this driver should be possible, but has not been tested up to now due
8852 to lack of hardware.
8854 EISA, VLB, PCI and on board controllers
8856 This is another class of network cards which attach directly to the
8857 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
8858 available from http://www.linuxdoc.org/docs.html#howto .
8860 Note that the answer to this question doesn't directly affect the
8861 kernel: saying N will just cause this configure script to skip all
8862 the questions about this class of network cards. If you say Y, you
8863 will be asked for your specific card in the following questions. If
8864 you are unsure, say Y.
8866 AMD PCnet32 (VLB and PCI) support
8868 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
8869 answer Y here and read the Ethernet-HOWTO, available from
8870 http://www.linuxdoc.org/docs.html#howto .
8872 This driver is also available as a module ( = code which can be
8873 inserted in and removed from the running kernel whenever you want).
8874 The module will be called pcnet32.o. If you want to compile it as a
8875 module, say M here and read Documentation/modules.txt as well as
8876 Documentation/networking/net-modules.txt.
8878 Ansel Communications EISA 3200 support
8880 If you have a network (Ethernet) card of this type, say Y and read
8881 the Ethernet-HOWTO, available from
8882 http://www.linuxdoc.org/docs.html#howto .
8884 This driver is also available as a module ( = code which can be
8885 inserted in and removed from the running kernel whenever you want).
8886 The module will be called ac3200.o. If you want to compile it as a
8887 module, say M here and read Documentation/modules.txt as well as
8888 Documentation/networking/net-modules.txt.
8890 Mylex EISA LNE390A/LNE390B support (EXPERIMENTAL)
8892 If you have a network (Ethernet) card of this type, say Y and read
8893 the Ethernet-HOWTO, available from
8894 http://www.linuxdoc.org/docs.html#howto .
8896 This driver is also available as a module ( = code which can be
8897 inserted in and removed from the running kernel whenever you want).
8898 The module will be called lne390.o. If you want to compile it as a
8899 module, say M here and read Documentation/modules.txt as well as
8900 Documentation/networking/net-modules.txt.
8902 Novell/Eagle/Microdyne NE3210 EISA support
8904 If you have a network (Ethernet) card of this type, say Y and read
8905 the Ethernet-HOWTO, available from
8906 http://www.linuxdoc.org/docs.html#howto . Note that this driver
8907 will NOT WORK for NE3200 cards as they are completely different.
8909 This driver is also available as a module ( = code which can be
8910 inserted in and removed from the running kernel whenever you want).
8911 The module will be called ne3210.o. If you want to compile it as a
8912 module, say M here and read Documentation/modules.txt as well as
8913 Documentation/networking/net-modules.txt.
8915 Apricot Xen-II on board Ethernet
8917 If you have a network (Ethernet) controller of this type, say Y and
8918 read the Ethernet-HOWTO, available from
8919 http://www.linuxdoc.org/docs.html#howto .
8921 If you want to compile this as a module ( = code which can be
8922 inserted in and removed from the running kernel whenever you want),
8923 say M here and read Documentation/modules.txt as well as
8924 Documentation/networking/net-modules.txt. The module will be called
8927 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
8929 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
8930 These include the DE425, DE434, DE435, DE450 and DE500 models. If
8931 you have a network card of this type, say Y and read the
8932 Ethernet-HOWTO, available from
8933 http://www.linuxdoc.org/docs.html#howto . More specific
8934 information is contained in Documentation/networking/de4x5.txt.
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 de4x5.o. If you want to compile it as a
8939 module, say M here and read Documentation/modules.txt as well as
8940 Documentation/networking/net-modules.txt.
8942 DECchip Tulip (dc21x4x) PCI support
8944 This driver is developed for the SMC EtherPower series Ethernet
8945 cards and also works with cards based on the DECchip
8946 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
8947 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
8948 (smc9332dst), you can also try the driver for "Generic DECchip"
8949 cards, above. However, most people with a network card of this type
8950 will say Y here.) Do read the Ethernet-HOWTO, available from
8951 http://www.linuxdoc.org/docs.html#howto . More specific
8952 information is contained in Documentation/networking/tulip.txt.
8954 This driver is also available as a module ( = code which can be
8955 inserted in and removed from the running kernel whenever you want).
8956 The module will be called tulip.o. If you want to compile it as a
8957 module, say M here and read Documentation/modules.txt as well as
8958 Documentation/networking/net-modules.txt.
8960 Digi Intl. RightSwitch support
8962 This is support for the Digi International RightSwitch series of
8963 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
8964 models. If you have a network card of this type, say Y and read the
8965 Ethernet-HOWTO, available from
8966 http://www.linuxdoc.org/docs.html#howto . More specific
8967 information is contained in Documentation/networking/dgrs.txt.
8969 This driver is also available as a module ( = code which can be
8970 inserted in and removed from the running kernel whenever you want).
8971 The module will be called dgrs.o. If you want to compile it as a
8972 module, say M here and read Documentation/modules.txt as well as
8973 Documentation/networking/net-modules.txt.
8975 EtherExpress PRO/100 support
8977 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
8978 card, say Y and read the Ethernet-HOWTO, available from
8979 http://www.linuxdoc.org/docs.html#howto .
8981 This driver is also available as a module ( = code which can be
8982 inserted in and removed from the running kernel whenever you want).
8983 The module will be called eepro100.o. If you want to compile it as a
8984 module, say M here and read Documentation/modules.txt as well as
8985 Documentation/networking/net-modules.txt.
8987 Enable Power Management (EXPERIMENTAL)
8989 Many Intel EtherExpress PRO/100 PCI network cards are capable
8990 of providing power management capabilities. To make use of these
8991 capabilities, say Y.
8993 WARNING: This option is intended for kernel developers and testers.
8994 It is still very experimental, with some people reporting complete
8997 It is recommended to say N here.
8999 ICL EtherTeam 16i/32 support (EXPERIMENTAL)
9001 If you have a network (Ethernet) card of this type, say Y and read
9002 the Ethernet-HOWTO, available from
9003 http://www.linuxdoc.org/docs.html#howto .
9005 This driver is also available as a module ( = code which can be
9006 inserted in and removed from the running kernel whenever you want).
9007 The module will be called eth16i.o. If you want to compile it as a
9008 module, say M here and read Documentation/modules.txt as well as
9009 Documentation/networking/net-modules.txt.
9011 TI ThunderLAN support (EXPERIMENTAL)
9013 If you have a PCI Ethernet network card based on the ThunderLAN chip
9014 which is supported by this driver, say Y and read the
9015 Ethernet-HOWTO, available from
9016 http://www.linuxdoc.org/docs.html#howto .
9018 Devices currently supported by this driver are Compaq Netelligent,
9019 Compaq NetFlex and Olicom cards. Please read the file
9020 Documentation/networking/tlan.txt for more details.
9022 This driver is also available as a module ( = code which can be
9023 inserted in and removed from the running kernel whenever you want).
9024 The module will be called tlan.o. If you want to compile it as a
9025 module, say M here and read Documentation/modules.txt as well as
9026 Documentation/networking/net-modules.txt.
9028 Please email feedback to torben.mathiasen@compaq.com.
9032 If you have a VIA "rhine" based network card (Rhine-I (3043) or
9033 Rhine-2 (VT86c100A)), say Y here.
9035 This driver is also available as a module ( = code which can be
9036 inserted in and removed from the running kernel whenever you want).
9037 The module will be called via-rhine.o. If you want to compile it as
9038 a module, say M here and read Documentation/modules.txt as well as
9039 Documentation/networking/net-modules.txt.
9041 PCI DM9102(A)/DM9132/DM9801 support
9043 This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
9044 Davicom ( http://www.davicom.com.tw ). If you have such a network
9045 (Ethernet) card, say Y. Some information is contained in the file
9046 Documentation/networking/dmfe.txt.
9048 This driver is also available as a module ( = code which can be
9049 inserted in and removed from the running kernel whenever you want).
9050 The module will be called dmfe.o. If you want to compile it as a
9051 module, say M here and read Documentation/modules.txt as well as
9052 Documentation/networking/net-modules.txt.
9054 Racal-Interlan EISA ES3210 support (EXPERIMENTAL)
9056 If you have a network (Ethernet) card of this type, say Y and read
9057 the Ethernet-HOWTO, available from
9058 http://www.linuxdoc.org/docs.html#howto .
9060 This driver is also available as a module ( = code which can be
9061 inserted in and removed from the running kernel whenever you want).
9062 The module will be called es3210.o. If you want to compile it as a
9063 module, say M here and read Documentation/modules.txt as well as
9064 Documentation/networking/net-modules.txt.
9068 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
9069 which is based on the SMC83c17x (EPIC/100).
9070 More specific information and updates are available from
9071 http://www.scyld.com/network/epic100.html
9073 SGI Seeq ethernet controller support
9075 Say Y here if you have an Seeq based Ethernet network card. This is
9076 used in many Silicon Graphics machines.
9078 Sundance "Alta" PCI Ethernet support
9080 This driver is for the Sundance "Alta" chip.
9081 More specific information and updates are available from
9082 http://www.scyld.com/network/sundance.html
9084 Winbond W89c840 PCI Ethernet support
9086 This driver is for the Winbond W89c840 chip. It also works with
9087 the TX9882 chip on the Compex RL100-ATX board.
9088 More specific information and updates are available from
9089 http://www.scyld.com/network/drivers.html
9091 Zenith Z-Note support (EXPERIMENTAL)
9093 The Zenith Z-Note notebook computer has a built-in network
9094 (Ethernet) card, and this is the Linux driver for it. Note that the
9095 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
9096 by this driver. Read the Ethernet-HOWTO, available from
9097 http://www.linuxdoc.org/docs.html#howto .
9099 Pocket and portable adapters
9101 Cute little network (Ethernet) devices which attach to the parallel
9102 port ("pocket adapters"), commonly used with laptops. If you have
9103 one of those, say Y and read the Ethernet-HOWTO, available from
9104 http://www.linuxdoc.org/docs.html#howto .
9106 If you want to plug a network (or some other) card into the PCMCIA
9107 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
9108 credit card size extension cards used by all modern laptops), you
9109 need the pcmcia-cs package (location contained in the file
9110 Documentation/Changes) and you can say N here.
9112 Laptop users should read the Linux Laptop home page at
9113 http://www.cs.utexas.edu/users/kharker/linux-laptop/ .
9115 Note that the answer to this question doesn't directly affect the
9116 kernel: saying N will just cause this configure script to skip all
9117 the questions about this class of network devices. If you say Y, you
9118 will be asked for your specific device in the following questions.
9120 AT-LAN-TEC/RealTek pocket adapter support
9122 This is a network (Ethernet) device which attaches to your parallel
9123 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
9124 available from http://www.linuxdoc.org/docs.html#howto , if you
9125 want to use this. If you intend to use this driver, you should have
9126 said N to the "Parallel printer support", because the two drivers
9127 don't like each other.
9129 If you want to compile this driver as a module however ( = code
9130 which can be inserted in and removed from the running kernel
9131 whenever you want), say M here and read Documentation/modules.txt.
9132 The module will be called atp.o.
9134 D-Link DE600 pocket adapter support
9136 This is a network (Ethernet) device which attaches to your parallel
9137 port. Read Documentation/networking/DLINK.txt as well as the
9138 Ethernet-HOWTO, available from
9139 http://www.linuxdoc.org/docs.html#howto , if you want to use
9140 this. It is possible to have several devices share a single parallel
9141 port and it is safe to compile the corresponding drivers into the
9144 If you want to compile this driver as a module however ( = code
9145 which can be inserted in and removed from the running kernel
9146 whenever you want), say M here and read Documentation/modules.txt.
9147 The module will be called de600.o.
9149 D-Link DE620 pocket adapter support
9151 This is a network (Ethernet) device which attaches to your parallel
9152 port. Read Documentation/networking/DLINK.txt as well as the
9153 Ethernet-HOWTO, available from
9154 http://www.linuxdoc.org/docs.html#howto , if you want to use
9155 this. It is possible to have several devices share a single parallel
9156 port and it is safe to compile the corresponding drivers into the
9159 If you want to compile this driver as a module however ( = code
9160 which can be inserted in and removed from the running kernel
9161 whenever you want), say M here and read Documentation/modules.txt.
9162 The module will be called de620.o.
9164 Token Ring driver support
9166 Token Ring is IBM's way of communication on a local network; the
9167 rest of the world uses Ethernet. To participate on a Token Ring
9168 network, you need a special Token ring network card. If you are
9169 connected to such a Token Ring network and want to use your Token
9170 Ring card under Linux, say Y here and to the driver for your
9171 particular card below and read the Token-Ring mini-HOWTO, available
9172 from http://www.linuxdoc.org/docs.html#howto . Most people can
9175 IBM Tropic chipset based adapter support
9177 This is support for all IBM Token Ring cards that don't use DMA. If
9178 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
9179 available from http://www.linuxdoc.org/docs.html#howto .
9181 Warning: this driver will almost definitely fail if more than one
9182 active Token Ring card is present.
9184 This driver is also available as a module ( = code which can be
9185 inserted in and removed from the running kernel whenever you want).
9186 The module will be called ibmtr.o. If you want to compile it as a
9187 module, say M here and read Documentation/modules.txt.
9189 IBM Olympic chipset PCI adapter support
9191 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
9192 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
9193 Wake On Lan, and PCI 100/16/4 adapters.
9195 If you have such an adapter, say Y and read the Token-Ring
9196 mini-HOWTO, available from
9197 http://www.linuxdoc.org/docs.html#howto .
9199 This driver is also available as a module ( = code which can be
9200 inserted in and removed from the running kernel whenever you want).
9201 The module will will be called olympic.o. If you want to compile it
9202 as a module, say M here and read Documentation/modules.txt.
9204 Also read the file Documentation/networking/olympic.txt or check the
9205 Linux Token Ring Project site for the latest information at
9206 http://www.linuxtr.net .
9208 IBM Lanstreamer chipset PCI adapter support
9210 This is support for IBM Lanstreamer PCI Token Ring Cards.
9212 If you have such an adapter, say Y and read the Token-Ring
9213 mini-HOWTO available via FTP (user:anonymous) from
9214 ftp://metalab.unc/edu/pub/Linux/docs/HOWTO.
9216 This driver is also available as a modules ( = code which can be
9217 inserted in and removed from the running kernel whenever you want).
9218 The modules will be called lanstreamer.o. If you want to compile it
9219 as a module, say M here and read Documentation/modules.txt.
9221 Generic TMS380 Token Ring ISA/PCI/MCA/EISA adapter support
9223 This driver provides generic support for token ring adapters
9224 based on the Texas Instruments TMS380 series chipsets. This
9225 includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect
9226 TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591),
9227 Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and several
9228 Madge adapters. If you say Y here, you will be asked to select
9229 which cards to support below. If you're using modules, each
9230 class of card will be supported by a separate module.
9232 If you have such an adapter and would like to use it, say Y and
9233 read the Token-Ring mini-HOWTO, available from
9234 http://www.linuxdoc.org/docs.html#howto .
9236 Also read the file Documentation/networking/tms380tr.txt or
9237 check http://www.auk.cx/tms380tr/ .
9239 This driver is also available as a module ( = code which can be
9240 inserted in and removed from the running kernel whenever you want).
9241 The module will will be called tms380tr.o. If you want to compile it
9242 as a module, say M here and read Documentation/modules.txt.
9244 Generic TMS380 PCI support
9246 This tms380 module supports generic TMS380-based PCI cards.
9248 These cards are known to work:
9249 - Compaq 4/16 TR PCI
9250 - SysKonnect TR4/16 PCI (SK-4590/SK-4591)
9251 - Thomas-Conrad TC4048 PCI 4/16
9252 - 3Com Token Link Velocity
9254 This driver is available as a module ( = code which can be
9255 inserted in and removed from the running kernel whenever you want).
9256 The module will will be called tmspci.o. If you want to compile it
9257 as a module, say M here and read Documentation/modules.txt.
9259 Madge Smart 16/4 PCI Mk2 support
9261 This tms380 module supports the Madge Smart 16/4 PCI Mk2
9264 This driver is available as a module ( = code which can be
9265 inserted in and removed from the running kernel whenever you want).
9266 The module will will be called abyss.o. If you want to compile it
9267 as a module, say M here and read Documentation/modules.txt.
9269 Madge Smart 16/4 Ringode MicroChannel
9271 This tms380 module supports the Madge Smart 16/4 MC16 and MC32
9272 MicroChannel adapters.
9274 This driver is available as a module ( = code which can be
9275 inserted in and removed from the running kernel whenever you want).
9276 The module will will be called madgemc.o. If you want to compile it
9277 as a module, say M here and read Documentation/modules.txt.
9279 SMC ISA TokenRing adapter support
9281 This is support for the ISA and MCA SMC Token Ring cards,
9282 specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A
9285 If you have such an adapter and would like to use it, say Y or M and
9286 read the Token-Ring mini-HOWTO, available from
9287 http://www.linuxdoc.org/docs.html#howto and the file
9288 Documentation/networking/smctr.txt.
9290 This driver is also available as a module ( = code which can be
9291 inserted in and removed from the running kernel whenever you want).
9292 The module will will be called smctr.o. If you want to compile it
9293 as a module, say M here and read Documentation/modules.txt.
9295 Sun Happy Meal 10/100baseT support
9297 This driver supports the "hme" interface present on most Ultra
9298 systems and as an option on older Sbus systems. This driver supports
9299 both PCI and Sbus devices. This driver also supports the "qfe" quad
9300 100baseT device available in both PCI and Sbus configurations.
9302 This support is also available as a module called sunhme.o ( = code
9303 which can be inserted in and removed from the running kernel
9304 whenever you want). If you want to compile it as a module, say M
9305 here and read Documentation/modules.txt.
9309 This driver supports the "le" interface present on all 32-bit Sparc
9310 systems, on some older Ultra systems and as an Sbus option.
9312 This support is also available as a module called sunlance.o ( =
9313 code which can be inserted in and removed from the running kernel
9314 whenever you want). If you want to compile it as a module, say M
9315 here and read Documentation/modules.txt.
9317 Sun BigMAC 10/100baseT support (EXPERIMENTAL)
9319 This driver supports the "be" interface available as an Sbus option.
9320 This is Sun's older 100baseT ethernet device.
9322 This support is also available as a module called sunbmac.o ( = code
9323 which can be inserted in and removed from the running kernel
9324 whenever you want). If you want to compile it as a module, say M
9325 here and read Documentation/modules.txt.
9327 Sun QuadEthernet support
9329 This driver supports the "qe" 10baseT ethernet device, available as
9330 an Sbus option. Note that this is not the same as Quad FastEthernet
9331 "qfe" which is supported by the Happy Meal driver instead.
9333 This support is also available as a module called sunqe.o ( = code
9334 which can be inserted in and removed from the running kernel
9335 whenever you want). If you want to compile it as a module, say M
9336 here and read Documentation/modules.txt.
9338 Traffic Shaper (EXPERIMENTAL)
9340 The traffic shaper is a virtual network device that allows you to
9341 limit the rate of outgoing data flow over some other network device.
9342 The traffic that you want to slow down can then be routed through
9343 these virtual devices. See Documentation/networking/shaper.txt for
9346 An alternative to this traffic shaper is the experimental
9347 Class-Based Queueing (CBQ) scheduling support which you get if you
9348 say Y to "QoS and/or fair queueing" above.
9350 To set up and configure shaper devices, you need the shapecfg
9351 program, available from ftp://shadow.cabi.net/pub/Linux in the
9354 This driver is also available as a module ( = code which can be
9355 inserted in and removed from the running kernel whenever you want).
9356 The module will be called shaper.o. If you want to compile it as a
9357 module, say M here and read Documentation/modules.txt. If unsure,
9362 Fiber Distributed Data Interface is a high speed local area network
9363 design; essentially a replacement for high speed Ethernet. FDDI can
9364 run over copper or fiber. If you are connected to such a network and
9365 want a driver for the FDDI card in your computer, say Y here (and
9366 then also Y to the driver for your FDDI card, below). Most people
9369 Digital DEFEA and DEFPA adapter support
9371 This is support for the DIGITAL series of EISA (DEFEA) and PCI
9372 (DEFPA) controllers which can connect you to a local FDDI network.
9374 SysKonnect FDDI PCI support
9376 Say Y here if you have a SysKonnect FDDI PCI adapter.
9377 The following adapters are supported by this driver:
9378 - SK-5521 (SK-NET FDDI-UP)
9379 - SK-5522 (SK-NET FDDI-UP DAS)
9380 - SK-5541 (SK-NET FDDI-FP)
9381 - SK-5543 (SK-NET FDDI-LP)
9382 - SK-5544 (SK-NET FDDI-LP DAS)
9383 - SK-5821 (SK-NET FDDI-UP64)
9384 - SK-5822 (SK-NET FDDI-UP64 DAS)
9385 - SK-5841 (SK-NET FDDI-FP64)
9386 - SK-5843 (SK-NET FDDI-LP64)
9387 - SK-5844 (SK-NET FDDI-LP64 DAS)
9388 - Netelligent 100 FDDI DAS Fibre SC
9389 - Netelligent 100 FDDI SAS Fibre SC
9390 - Netelligent 100 FDDI DAS UTP
9391 - Netelligent 100 FDDI SAS UTP
9392 - Netelligent 100 FDDI SAS Fibre MIC
9394 Read Documentation/networking/skfp.txt for information about
9397 Questions concerning this driver can be addressed to:
9400 If you want to compile this driver as a module ( = code which can be
9401 inserted in and removed from the running kernel whenever you want),
9402 say M here and read Documentation/modules.txt. This is recommended.
9403 The module will be called skfp.o.
9405 HIgh Performance Parallel Interface support (EXPERIMENTAL)
9407 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
9408 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
9409 can run over copper (25m) or fiber (300m on multi-mode or 10km on
9410 single-mode). HIPPI networks are commonly used for clusters and to
9411 connect to super computers. If you are connected to a HIPPI network
9412 and have a HIPPI network card in your computer that you want to use
9413 under Linux, say Y here (you must also remember to enable the driver
9414 for your HIPPI card below). Most people will say N here.
9416 Essential RoadRunner HIPPI PCI adapter support
9418 Say Y here if this is your PCI HIPPI network card.
9420 This driver is also available as a module ( = code which can be
9421 inserted in and removed from the running kernel whenever you want).
9422 The module will be called rrunner.o. If you want to compile it as
9423 a module, say M here and read Documentation/modules.txt. If unsure,
9426 Use large TX/RX rings
9427 CONFIG_ROADRUNNER_LARGE_RINGS
9428 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
9429 of additional memory to allow for fastest operation, both for
9430 transmitting and receiving. This memory cannot be used by any other
9431 kernel code or by user space programs. Say Y here only if you have
9436 If you have an Acorn system with one of these (AKA25) network cards,
9437 you should say Y to this option if you wish to use it with Linux.
9439 Acorn/ANT Ether3 card
9441 If you have an Acorn system with one of these network cards, you
9442 should say Y to this option if you wish to use it with Linux.
9446 If you have an Acorn system with one of these network cards, you
9447 should say Y to this option if you wish to use it with Linux.
9449 EBSA-110 Ethernet interface
9450 CONFIG_ARM_AM79C961A
9451 If you wish to compile a kernel for the EBSA-110, then you should
9452 always answer Y to this.
9454 Support CDROM drives that are not SCSI or IDE/ATAPI
9455 CONFIG_CD_NO_IDESCSI
9456 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
9457 here, otherwise N. Read the CDROM-HOWTO, available from
9458 http://www.linuxdoc.org/docs.html#howto .
9460 Note that the answer to this question doesn't directly affect the
9461 kernel: saying N will just cause this configure script to skip all
9462 the questions about these CDROM drives. If you are unsure what you
9463 have, say Y and find out whether you have one of the following
9466 For each of these drivers, a file Documentation/cdrom/<driver_name>
9467 exists. Especially in cases where you do not know exactly which kind
9468 of drive you have you should read there. Most of these drivers use a
9469 file drivers/cdrom/<driver_name>.h where you can define your
9470 interface parameters and switch some internal goodies.
9472 All these CDROM drivers are also usable as a module ( = code which
9473 can be inserted in and removed from the running kernel whenever you
9474 want). If you want to compile them as module, say M instead of Y and
9475 read Documentation/modules.txt.
9477 If you want to use any of these CDROM drivers, you also have to
9478 answer Y or M to "ISO 9660 CDROM file system support" below (this
9479 answer will get "defaulted" for you if you enable any of the Linux
9482 Sony CDU31A/CDU33A CDROM support
9484 These CDROM drives have a spring-pop-out caddyless drawer, and a
9485 rectangular green LED centered beneath it. NOTE: these CDROM drives
9486 will not be auto detected by the kernel at boot time; you have to
9487 provide the interface address as an option to the kernel at boot
9488 time as described in Documentation/cdrom/cdu31a or fill in your
9489 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
9490 see the documentation of your boot loader (lilo or loadlin) about
9491 how to pass options to the kernel.
9493 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9494 file system support" below, because that's the file system used on
9497 This driver is also available as a module ( = code which can be
9498 inserted in and removed from the running kernel whenever you want).
9499 The module will be called cdu31a.o. If you want to compile it as a
9500 module, say M here and read Documentation/modules.txt.
9502 Standard Mitsumi [no XA/Multisession] CDROM support
9504 This is the older of the two drivers for the older Mitsumi models
9505 LU-005, FX-001 and FX-001D. This is not the right driver for the
9506 FX-001DE and the triple or quad speed models (all these are
9507 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
9509 With the old LU-005 model, the whole drive chassis slides out for cd
9510 insertion. The FX-xxx models use a motorized tray type mechanism.
9511 Note that this driver does not support XA or MultiSession CDs
9512 (PhotoCDs). There is a new driver (next question) which can do
9513 this. If you want that one, say N here.
9515 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9516 file system support" below, because that's the file system used on
9519 This driver is also available as a module ( = code which can be
9520 inserted in and removed from the running kernel whenever you want).
9521 The module will be called mcd.o. If you want to compile it as a
9522 module, say M here and read Documentation/modules.txt.
9524 IRQ channel for Mitsumi CD-ROM
9526 This allows you to specify the default value of the IRQ used by the
9527 driver. This setting can be overridden by passing the "mcd="
9528 parameter to the kernel at boot time (or at module load time if you
9529 said M to "Standard Mitsumi CDROM support").
9531 I/O base address for Mitsumi CD-ROM
9533 This allows you to specify the default value of the I/O base address
9534 used by the driver. This setting can be overridden by passing the
9535 "mcd=" parameter to the kernel at boot time (or at module load time
9536 if you said M to "Standard Mitsumi CDROM support").
9538 Mitsumi [XA/MultiSession] support
9540 Use this driver if you want to be able to read XA or MultiSession
9541 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
9542 FX-001 or FX-001D CDROM drive. In addition, this driver uses much
9543 less kernel memory than the old one, if that is a concern. This
9544 driver is able to support more than one drive, but each drive needs
9545 a separate interface card. Please read the file
9546 Documentation/cdrom/mcdx.
9548 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9549 file system support" below, because that's the file system used on
9552 This driver is also available as a module ( = code which can be
9553 inserted in and removed from the running kernel whenever you want).
9554 The module will be called mcdx.o. If you want to compile it as a
9555 module, say M here and read Documentation/modules.txt.
9557 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
9559 This driver supports most of the drives which use the Panasonic or
9560 Sound Blaster interface. Please read the file
9561 Documentation/cdrom/sbpcd.
9563 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
9564 (sometimes labeled "Creative"), the Creative Labs CD200, the
9565 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
9566 model), the TEAC CD-55A fall under this category. Some other
9567 "electrically compatible" drives (Vertos, Genoa, some Funai models)
9568 are currently not supported; for the Sanyo H94A drive currently a
9569 separate driver (asked later) is responsible. Most drives have a
9570 uniquely shaped faceplate, with a caddyless motorized drawer, but
9571 without external brand markings. The older CR-52x drives have a
9572 caddy and manual loading/eject, but still no external markings. The
9573 driver is able to do an extended auto-probing for interface
9574 addresses and drive types; this can help to find facts in cases you
9575 are not sure, but can consume some time during the boot process if
9576 none of the supported drives gets found. Once your drive got found,
9577 you should enter the reported parameters into drivers/cdrom/sbpcd.h
9578 and set "DISTRIBUTION 0" there.
9580 This driver can support up to four CDROM controller cards, and each
9581 card can support up to four CDROM drives; if you say Y here, you
9582 will be asked how many controller cards you have. If compiled as a
9583 module, only one controller card (but with up to four drives) is
9586 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9587 file system support" below, because that's the file system used on
9590 This driver is also available as a module ( = code which can be
9591 inserted in and removed from the running kernel whenever you want).
9592 The module will be called sbpcd.o. If you want to compile it as a
9593 module, say M here and read Documentation/modules.txt.
9595 Matsushita/Panasonic, ... second CDROM controller support
9597 Say Y here only if you have two CDROM controller cards of this type
9598 (usually only if you have more than four drives). You should enter
9599 the parameters for the second, third and fourth interface card into
9600 include/linux/sbpcd.h before compiling the new kernel. Read
9601 the file Documentation/cdrom/sbpcd.
9603 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
9605 This is your driver if you have an Aztech CDA268-01A, Orchid
9606 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
9607 CR540 CDROM drive. This driver -- just like all these CDROM drivers
9608 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
9609 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
9611 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9612 file system support" below, because that's the file system used on
9615 This driver is also available as a module ( = code which can be
9616 inserted in and removed from the running kernel whenever you want).
9617 The module will be called aztcd.o. If you want to compile it as a
9618 module, say M here and read Documentation/modules.txt.
9620 Sony CDU535 CDROM support
9622 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
9623 drives. Please read the file Documentation/cdrom/sonycd535.
9625 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9626 file system support" below, because that's the file system used on
9629 This driver is also available as a module ( = code which can be
9630 inserted in and removed from the running kernel whenever you want).
9631 The module will be called sonycd535.o. If you want to compile it as
9632 a module, say M here and read Documentation/modules.txt.
9634 Goldstar R420 CDROM support
9636 If this is your CDROM drive, say Y here. As described in the file
9637 Documentation/cdrom/gscd, you might have to change a setting
9638 in the file drivers/cdrom/gscd.h before compiling the
9639 kernel. Please read the file Documentation/cdrom/gscd.
9641 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9642 file system support" below, because that's the file system used on
9645 This driver is also available as a module ( = code which can be
9646 inserted in and removed from the running kernel whenever you want).
9647 The module will be called gscd.o. If you want to compile it as a
9648 module, say M here and read Documentation/modules.txt.
9650 Philips/LMS CM206 CDROM support
9652 If you have a Philips/LMS CDROM drive cm206 in combination with a
9653 cm260 host adapter card, say Y here. Please also read the file
9654 Documentation/cdrom/cm206.
9656 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9657 file system support" below, because that's the file system used on
9660 This driver is also available as a module ( = code which can be
9661 inserted in and removed from the running kernel whenever you want).
9662 The module will be called cm206.o. If you want to compile it as a
9663 module, say M here and read Documentation/modules.txt.
9665 Optics Storage DOLPHIN 8000AT CDROM support
9667 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
9668 compatible interface. It also works with the Lasermate CR328A. If
9669 you have one of those, say Y. This driver does not work for the
9670 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
9671 one. Please read the file Documentation/cdrom/optcd.
9673 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
9674 file system support" below, because that's the file system used on
9677 This driver is also available as a module ( = code which can be
9678 inserted in and removed from the running kernel whenever you want).
9679 The module will be called optcd.o. If you want to compile it as a
9680 module, say M here and read Documentation/modules.txt.
9682 Sanyo CDR-H94A CDROM support
9684 If this is your CDROM drive, say Y here and read the file
9685 Documentation/cdrom/sjcd. You should then also say Y or M to
9686 "ISO 9660 CDROM file system support" below, because that's the
9687 file system used on CDROMs.
9689 This driver is also available as a module ( = code which can be
9690 inserted in and removed from the running kernel whenever you want).
9691 The module will be called sjcd.o. If you want to compile it as a
9692 module, say M here and read Documentation/modules.txt.
9694 ISP16/MAD16/Mozart soft configurable cdrom interface support
9696 These are sound cards with built-in cdrom interfaces using the OPTi
9697 82C928 or 82C929 chips. Say Y here to have them detected and
9698 possibly configured at boot time. In addition, You'll have to say Y
9699 to a driver for the particular cdrom drive you have attached to the
9700 card. Read Documentation/cdrom/isp16 for details.
9702 This driver is also available as a module ( = code which can be
9703 inserted in and removed from the running kernel whenever you want).
9704 The module will be called isp16.o. If you want to compile it as a
9705 module, say M here and read Documentation/modules.txt.
9709 If you say Y here, you will be able to set per user limits for disk
9710 usage (also called disk quotas). Currently, it works only for the
9711 ext2 file system. You need additional software in order to use quota
9712 support; for details, read the Quota mini-HOWTO, available from
9713 http://www.linuxdoc.org/docs.html#howto . Probably the quota
9714 support is only useful for multi user systems. If unsure, say N.
9716 Memory Technology Device (MTD) support
9718 Memory Technology Devices are flash, RAM and similar chips, often
9719 used for solid state filesystems on embedded devices. This option
9720 will provide the generic support for MTD drivers to register
9721 themselves with the kernel and for potential users of MTD devices
9722 to enumerate the devices which are present and obtain a handle on
9723 them. It will also allow you to select individual drivers for
9724 particular hardware and users of MTD device. If unsure, say N.
9726 M-Systems Disk-On-Chip 1000 support
9728 This provides an MTD device driver for the M-Systems DiskOnChip
9729 1000 devices, which are obsolete so you probably want to say 'N'.
9731 M-Systems Disk-On-Chip 2000 support
9733 This provides an MTD device driver for the M-Systems DiskOnChip
9734 2000 devices. If you use this, you probably also want the NFTL
9735 'NAND Flash Translation Layer' below, which is used to emulate
9736 a block device by using a kind of filesystem on the flash chips.
9738 M-Systems Disk-On-Chip Millennium support
9740 This provides an MTD device driver for the M-Systems DiskOnChip
9741 Millennium devices. If you use this, you probably also want the
9742 NFTL 'NAND Flash Translation Layer' below, which is used to emulate
9743 a block device by using a kind of filesystem on the flash chips.
9745 Use extra onboard system memory as MTD device
9747 If your CPU cannot cache all of the physical memory in your machine,
9748 you can still use it for storage or swap by using this driver to
9749 present it to the system as a Memory Technology Device.
9751 Ramix PMC551 PCI Mezzanine ram card support
9753 This provides an MTD device driver for the Ramix PMC551 RAM card.
9754 If you have one, you probably want to enable this.
9756 PMC551 256M DRAM Bugfix.
9757 CONFIG_MTD_PMC551_BUGFIX
9758 Some PMC551 boards hacve invalid column and row mux values. This
9759 option will fix them, but will break other memory configurations.
9761 Debugging RAM test driver
9763 This enables a test MTD device driver which uses vmalloc() to
9764 provide storage. You probably want to say 'N' unless you're
9765 testing stuff, or unless you want to use it in place of a ramdisk
9766 when I've eventually got round to making the CONFIG_BLK_DEV option
9767 and you've turned it off.
9769 Common Flash Interface (CFI) support
9771 Intel's Common Flash Interface specification provides a universal
9772 method for probing the capabilities of flash devices. If you wish
9773 to support any device which uses CFI-compliant devices, you need
9774 to enable this option.
9776 CFI support for Intel/Sharp Extended Command Set chips
9777 CONFIG_MTD_CFI_INTELEXT
9778 The Common Flash Interface defines a number of different command
9779 sets which a CFI-compliant chip may claim to implement. This code
9780 provides support for one of those command sets, used on Intel
9781 Strataflash and other parts.
9783 Flash chip mapping in physical memory
9785 This provides a 'mapping' driver which allows the CFI probe and
9786 command set driver code to communicate with flash chips which
9787 are mapped physically into the CPU's memory. You will need to
9788 configure the physical address and size of the flash chips on
9789 your particular board.
9791 Physical start location of flash chip mapping
9792 CONFIG_MTD_PHYSMAP_START
9793 This is the physical memory location at which the flash chips
9794 are mapped on your particular target board. Refer to the
9795 memory map which should hopefully be in the documentation for
9798 Physical length of flash chip mapping
9799 CONFIG_MTD_PHYSMAP_LEN
9800 This is the total length of the mapping of the flash chips on
9801 your particular board. If there is space, or aliases, in the
9802 physical memory map between the chips, this could be larger
9803 than the total amount of flash present. Refer to the memory
9804 map which should hopefully be in the documentation for your
9807 Flash chip mapping on Mixcom piggyback card
9809 This supports the paging arrangement for access to flash chips
9810 on the Mixcom piggyback card, allowing the flash chip drivers
9811 to get on with their job of driving the flash chips without
9812 having to know about the paging. If you have one of these boards,
9813 you probably want to enable this mapping driver.
9815 Flash chip mapping on Nora
9817 If you had to ask, you don't have one. Say 'N'.
9819 Flash chip mapping on Octagon 5066 SBC
9821 This provides a 'mapping' driver which supports the way in which
9822 the flash chips are connected in the Octagon-5066 Single Board
9823 Computer. You will also need to complete and enable the driver
9824 for JEDEC flash chips.
9826 Flash chip mapping on RPXlite PPC board
9828 The RPXLite PowerPC board has CFI-compliant chips mapped in
9829 a strange sparse mapping. This 'mapping' driver supports that
9830 arrangement, allowing the CFI probe and command set driver code
9831 to communicate with the chips on the RPXLite board.
9833 Flash chip mapping on Tempustech VMAX SBC301
9835 This provides a 'mapping' driver which supports the way in which
9836 the flash chips are connected in the Tempustech VMAX SBC301 Single
9837 Board Computer. You will also need to complete and enable the driver
9838 for JEDEC flash chips.
9840 Direct chardevice access to MTD devices
9842 This provides a character device for each MTD device present in
9843 the system, allowing the user to read and write directly to the
9844 memory chips, and also use ioctl() to obtain information about
9845 the device, or to erase parts of it.
9847 Pseudo-blockdevice access to MTD devices
9849 Although flash chips have an erase size too large to useful as
9850 block devices, it is possible to use MTD devices which are based
9851 on RAM chips in this manner. This blockdevice user of MTD devices
9852 performs that function. At the moment, it is also required for
9853 the Journalling Flash File System to obtain a handle on the MTD
9854 device when it's mounted - although the JFFS doesn't actually use
9855 any of the functions of the mtdblock device.
9857 Later, it may be extended to perform read/erase/modify/write cycles
9858 on flash chips to emulate a smaller block size. Needless to say,
9859 this is very unsafe, but could be useful for filesystems which are
9860 almost never written to.
9862 FTL (Flash Translation Layer) support
9864 This provides support for the original Flash Translation Layer which
9865 is part of the PCMCIA specification. It uses a kind of pseudo-
9866 filesystem on a flash device to emulate a block device with 512-byte
9867 sectors, on top of which you put a 'normal' filesystem. You may find
9868 that the algorithms used in this code are patented unless you live
9869 in the Free World where software patents aren't legal - in the USA
9870 you are only permitted to use this on PCMCIA hardware, although
9871 under the terms of the GPL you're obviously permitted to copy,
9872 modify and distribute the code as you wish. Just not use it.
9874 NFTL (NAND Flash Translation Layer) support
9876 This provides support for the NAND Flash Translation Layer which is
9877 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
9878 filesystem on a flash device to emulate a block device with 512-byte
9879 sectors, on top of which you put a 'normal' filesystem. You may find
9880 that the algorithms used in this code are patented unless you live
9881 in the Free World where software patents aren't legal - in the USA
9882 you are only permitted to use this on DiskOnChip hardware, although
9883 under the terms of the GPL you're obviously permitted to copy,
9884 modify and distribute the code as you wish. Just not use it.
9886 Write support for NFTL (EXPERIMENTAL)
9888 If you're lucky, this will actually work. Don't whinge if it doesn't.
9889 Contact dwmw2@infradead.org if you want to help to make it more
9894 Universal Serial Bus (USB) is a specification for a serial bus
9895 subsystem which offers higher speeds and more features than the
9896 traditional PC serial port. The bus supplies power to peripherals
9897 and allows for hot swapping. Up to 127 USB peripherals can be
9898 connected to a single USB port in a tree structure. The USB port is
9899 the root of the tree, the peripherals are the leaves and the inner
9900 nodes are special USB devices called hubs. Many newer PC's have USB
9901 ports and newer peripherals such as scanners, keyboards, mice,
9902 modems, and printers support the USB protocol and can be connected
9903 to the PC via those ports.
9905 Say Y here if your computer has a USB port and you want to use USB
9906 devices. You then need to say Y to at least one of "UHCI support" or
9907 "OHCI support" below (the type of interface that the USB hardware in
9908 your computer provides to the operating system) and then choose from
9909 among the drivers for USB peripherals. You may want to check out the
9910 information provided in Documentation/usb/ and especially the links
9911 given in Documentation/usb/usb-help.txt.
9913 This code is also available as a module ( = code which can be
9914 inserted in and removed from the running kernel whenever you want).
9915 The module will be called usbcore.o. If you want to compile it as a
9916 module, say M here and read Documentation/modules.txt.
9918 USB verbose debug messages
9920 Say Y here if you want the USB core & hub drivers to produce a bunch
9921 of debug messages to the system log. Select this if you are having a
9922 problem with USB support and want to see more of what is going on.
9924 UHCI (intel PIIX4, VIA, ...) support?
9926 The Universal Host Controller Interface is a standard by Intel for
9927 accessing the USB hardware in the PC (which is also called the USB
9928 host controller). If your USB host controller conforms to this
9929 standard, you may want to say Y, but see below. All recent boards
9930 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
9931 i810, i820) conform to this standard. Also all VIA PCI chipsets
9932 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
9935 Currently there exist two drivers for UHCI host controllers: this
9936 one and the so-called JE driver, which you can get from
9937 "UHCI alternate (JE) support", below. You need only one.
9939 This code is also available as a module ( = code which can be
9940 inserted in and removed from the running kernel whenever you want).
9941 The module will be called usb-uhci.o. If you want to compile it as a
9942 module, say M here and read Documentation/modules.txt.
9944 UHCI (intel PIIX4, VIA, ...) alternate (JE) support?
9946 The Universal Host Controller Interface is a standard by Intel for
9947 accessing the USB hardware in the PC (which is also called the USB
9948 host controller). If your USB host controller conforms to this
9949 standard, you may want to say Y, but see below. All recent boards
9950 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
9951 i810, i820) conform to this standard. Also all VIA PCI chipsets
9952 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
9953 133). If unsure, say Y.
9955 Currently there exist two drivers for UHCI host controllers: this
9956 so-called JE driver, and the one you get from "UHCI support", above.
9959 This code is also available as a module ( = code which can be
9960 inserted in and removed from the running kernel whenever you want).
9961 The module will be called uhci.o. If you want to compile it as a
9962 module, say M here and read Documentation/modules.txt.
9964 UHCI unlink optimizations (EXPERIMENTAL)
9965 CONFIG_USB_UHCI_ALT_UNLINK_OPTIMIZE
9966 This option currently does nothing. You may say Y or N.
9968 OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support
9970 The Open Host Controller Interface is a standard by
9971 Compaq/Microsoft/National for accessing the USB PC hardware (also
9972 called USB host controller). If your USB host controller conforms to
9973 this standard, say Y. The USB host controllers on most non-Intel
9974 architectures and on several x86 compatibles with non-Intel chipsets
9975 -- like SiS (aktual 610, 610 and so on) or ALi (ALi IV, ALi V,
9976 Aladdin Pro..) -- conform to this standard.
9978 You may want to read the file Documentation/usb/ohci.txt.
9980 This code is also available as a module ( = code which can be
9981 inserted in and removed from the running kernel whenever you want).
9982 The module will be called usb-ohci.o. If you want to compile it
9983 as a module, say M here and read Documentation/modules.txt.
9985 USB Human Interface Device (HID) support
9987 Say Y here if you want to connect keyboards, mice, joysticks,
9988 graphic tablets, or any other HID based devices to your
9989 computer via USB. More information is available:
9990 Documentation/usb/input.txt.
9994 This code is also available as a module ( = code which can be
9995 inserted in and removed from the running kernel whenever you want).
9996 The module will be called hid.o. If you want to compile it as a
9997 module, say M here and read Documentation/modules.txt.
9999 USB HIDBP Keyboard support
10001 Say Y here if you don't want to use the generic HID driver for your
10002 USB keyboard and prefer to use the keyboard in its limited Boot
10003 Protocol mode. This driver is much smaller than the HID one.
10005 This code is also available as a module ( = code which can be
10006 inserted in and removed from the running kernel whenever you want).
10007 The module will be called usbkbd.o. If you want to compile it as a
10008 module, say M here and read Documentation/modules.txt.
10012 USB HIDBP Mouse support
10014 Say Y here if you don't want to use the generic HID driver for your
10015 USB mouse and prefer to use the mouse in its limited Boot Protocol
10016 mode. This driver is much smaller than the HID one.
10018 This code is also available as a module ( = code which can be
10019 inserted in and removed from the running kernel whenever you want).
10020 The module will be called usbmouse.o. If you want to compile it as
10021 a module, say M here and read Documentation/modules.txt.
10025 Wacom Intuos/Graphire tablet support
10027 Say Y here if you want to use the USB version of the Wacom Intuos
10028 or Graphire tablet. Make sure to say Y to "Mouse support"
10029 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
10030 (CONFIG_INPUT_EVDEV) as well.
10032 This driver is also available as a module ( = code which can be
10033 inserted in and removed from the running kernel whenever you want).
10034 The module will be called wacom.o. If you want to compile it as a
10035 module, say M here and read Documentation/modules.txt.
10037 Logitech WingMan Force joystick support
10039 Say Y here if you want to use the Logitech WingMan Force with Linux
10040 on the USB port. No force-feedback support yet, but other than that
10041 it should work like a normal joystick.
10043 This driver is also available as a module ( = code which can be
10044 inserted in and removed from the running kernel whenever you want).
10045 The module will be called wmforce.o. If you want to compile it as a
10046 module, say M here and read Documentation/modules.txt.
10048 Use input layer for ADB devices
10049 CONFIG_INPUT_ADBHID
10050 Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
10051 such as keyboards, mice, joysticks, or graphic tablets handled by the
10052 input layer. If you say Y here, make sure to say Y to the
10053 corresponding drivers "Keyboard support" (CONFIG_INPUT_KEYBDEV),
10054 "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface support"
10055 (CONFIG_INPUT_EVDEV) as well.
10057 If you say N here, you still have the option of using the old ADB
10058 keyboard and mouse drivers.
10063 CONFIG_INPUT_KEYBDEV
10064 Say Y here if you want your USB HID keyboard (or an ADB keyboard
10065 handled by the input layer) to be able to serve as a system keyboard.
10067 This driver is also available as a module ( = code which can be
10068 inserted in and removed from the running kernel whenever you want).
10069 The module will be called keybdev.o. If you want to compile it as a
10070 module, say M here and read Documentation/modules.txt.
10073 CONFIG_INPUT_MOUSEDEV
10074 Say Y here if you want your USB HID mouse (or ADB mouse handled by
10075 the input layer) to be accessible as char devices 13:32+ -
10076 /dev/input/mouseX and 13:63 - /dev/input/mice as an emulated ImPS/2
10077 mouse. That way, all user space programs will be able to use your
10082 This driver is also available as a module ( = code which can be
10083 inserted in and removed from the running kernel whenever you want).
10084 The module will be called mousedev.o. If you want to compile it as
10085 a module, say M here and read Documentation/modules.txt.
10087 Horizontal screen resolution
10088 CONFIG_INPUT_MOUSEDEV_SCREEN_X
10089 If you're using a digitizer, or a graphic tablet, and want to use
10090 it as a mouse then the mousedev driver needs to know the X window
10091 screen resolution you are using to correctly scale the data. If
10092 you're not using a digitizer, this value is ignored.
10094 Vertical screen resolution
10095 CONFIG_INPUT_MOUSEDEV_SCREEN_Y
10096 If you're using a digitizer, or a graphic tablet, and want to use
10097 it as a mouse then the mousedev driver needs to know the X window
10098 screen resolution you are using to correctly scale the data. If
10099 you're not using a digitizer, this value is ignored.
10102 CONFIG_INPUT_JOYDEV
10103 Say Y here if you want your USB HID joystick or gamepad to be
10104 accessible as char device 13:0+ - /dev/input/jsX device.
10106 This driver is also available as a module ( = code which can be
10107 inserted in and removed from the running kernel whenever you want).
10108 The module will be called joydev.o. If you want to compile it as a
10109 module, say M here and read Documentation/modules.txt.
10111 Event interface support
10113 Say Y here if you want your USB or ADB HID device events be accessible
10114 under char device 13:64+ - /dev/input/eventX in a generic way.
10115 This is the future ...
10117 USB Scanner support
10119 Say Y here if you want to connect a USB scanner to your computer's
10120 USB port. Please read Documentation/usb/scanner.txt and
10121 Documentation/usb/scanner-hp-sane.txt for more information.
10123 This code is also available as a module ( = code which can be
10124 inserted in and removed from the running kernel whenever you want).
10125 The module will be called scanner.o. If you want to compile it as
10126 a module, say M here and read Documentation/modules.txt.
10130 Say Y here if you want to connect UAB audio equipment such as
10131 speakers to your computer's USB port.
10133 This code is also available as a module ( = code which can be
10134 inserted in and removed from the running kernel whenever you want).
10135 The module will be called audio.o. If you want to compile it as a
10136 module, say M here and read Documentation/modules.txt.
10138 USB Modem (CDC ACM) support
10140 This driver supports USB modems and ISDN adapters which support the
10141 Communication Device Class Abstract Control Model interface.
10142 Please read Documentation/usb/acm.txt for details.
10144 This code is also available as a module ( = code which can be
10145 inserted in and removed from the running kernel whenever you want).
10146 The module will be called acm.o. If you want to compile it as a
10147 module, say M here and read Documentation/modules.txt.
10149 USB Serial converter support
10151 Say Y here if you have a USB device that provides normal serial
10152 ports, and you want to connect it to your USB bus. Supported devices
10153 are the Tech WhiteHEAT multi-port USB to serial converter, and the
10154 FTDI or Keyspan single port USB to serial converter Handspring
10155 Visor. In addition to saying Y here, you need to say Y to the driver
10156 for your specific hardware below. Some other devices may also be
10157 used if you say Y to "USB Generic Serial Driver", below.
10159 Please read Documentation/usb/usb-serial.txt for more information.
10161 This code is also available as a module ( = code which can be
10162 inserted in and removed from the running kernel whenever you want).
10163 The module will be called usbserial.o. If you want to compile it
10164 as a module, say M here and read Documentation/modules.txt.
10166 USB Generic Serial Driver
10167 CONFIG_USB_SERIAL_GENERIC
10168 Say Y here if you want to use the generic USB serial driver. Please
10169 read Documentation/usb/usb-serial.txt for more information on using
10170 this driver. It is recommended that the "USB Serial converter
10171 support" be compiled as a module for this driver to be used
10174 USB ConnectTech WhiteHEAT Serial Driver
10175 CONFIG_USB_SERIAL_WHITEHEAT
10176 Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
10177 USB to serial converter device.
10179 This code is also available as a module ( = code which can be
10180 inserted in and removed from the running kernel whenever you want).
10181 The module will be called whiteheat.o. If you want to compile it as a
10182 module, say M here and read Documentation/modules.txt.
10184 USB Handspring Visor Driver
10185 CONFIG_USB_SERIAL_VISOR
10186 Say Y here if you want to connect to your HandSpring Visor through
10187 its USB docking station. See http://usbvisor.sourceforge.net for
10188 more information on using this driver.
10190 This code is also available as a module ( = code which can be
10191 inserted in and removed from the running kernel whenever you want).
10192 The module will be called visor.o. If you want to compile it as a
10193 module, say M here and read Documentation/modules.txt.
10195 USB FTDI Single Port Serial Driver
10196 CONFIG_USB_SERIAL_FTDI_SIO
10197 Say Y here if you want to use a FTDI SIO single port USB to serial
10198 converter device. The implementation I have is called the USC-1000.
10200 See http://reality.sgi.com/bryder_wellington/ftdi_sio for more
10201 information on this driver and the device.
10203 This code is also available as a module ( = code which can be
10204 inserted in and removed from the running kernel whenever you want).
10205 The module will be called ftdi_sio.o. If you want to compile it as a
10206 module, say M here and read Documentation/modules.txt.
10208 USB Keyspan PDA Single Port Serial Driver
10209 CONFIG_USB_SERIAL_KEYSPAN_PDA
10210 Say Y here if you want to use a Keyspan PDA single port USB to
10211 serial converter device. This driver makes use of firmware
10212 developed from scratch by Brian Warner.
10214 This code is also available as a module ( = code which can be
10215 inserted in and removed from the running kernel whenever you want).
10216 The module will be called keyspan_pda.o. If you want to compile it
10217 as a module, say M here and read Documentation/modules.txt.
10219 USB Keyspan USA-xxx Serial Driver
10220 CONFIG_USB_SERIAL_KEYSPAN
10221 Say Y here if you want to use Keyspan USB to serial converter
10222 devices. This driver makes use of Keyspan's official firmware
10223 and was developed with their support. You must also include
10224 firmware to support your particular device(s).
10226 See http://www.linuxcare.com.au/hugh/keyspan.html for
10229 This code is also available as a module ( = code which can be
10230 inserted in and removed from the running kernel whenever you want).
10231 The module will be called keyspan.o. If you want to compile it as a
10232 module, say M here and read Documentation/modules.txt.
10234 USB Keyspan USA-28 Firmware
10235 CONFIG_USB_SERIAL_KEYSPAN_USA28
10236 Say Y here to include firmware for the USA-28 converter.
10238 USB Keyspan USA-28X Firmware
10239 CONFIG_USB_SERIAL_KEYSPAN_USA28X
10240 Say Y here to include firmware for the USA-28X converter.
10242 USB Keyspan USA-19 Firmware
10243 CONFIG_USB_SERIAL_KEYSPAN_USA19
10244 Say Y here to include firmware for the USA-19 converter.
10246 USB Keyspan USA-18X Firmware
10247 CONFIG_USB_SERIAL_KEYSPAN_USA18X
10248 Say Y here to include firmware for the USA-18X converter.
10250 USB Keyspan USA-19W Firmware
10251 CONFIG_USB_SERIAL_KEYSPAN_USA19W
10252 Say Y here to include firmware for the USA-19W converter.
10254 USB ZyXEL omni.net LCD Plus Driver
10255 CONFIG_USB_SERIAL_OMNINET
10256 Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA.
10258 This code is also available as a module ( = code which can be
10259 inserted in and removed from the running kernel whenever you want).
10260 The module will be called omninet.o. If you want to compile it as a
10261 module, say M here and read Documentation/modules.txt.
10263 USB Digi International AccelePort USB Serial Driver
10264 CONFIG_USB_SERIAL_DIGI_ACCELEPORT
10265 Say Y here if you want to use Digi AccelePort USB 2 or 4 devices,
10266 2 port (plus parallel port) and 4 port USB serial converters. The
10267 parallel port on the USB 2 appears as a third serial port on Linux.
10268 The Digi Acceleport USB 8 is not yet supported by this driver.
10270 This code is also available as a module ( = code which can be
10271 inserted in and removed from the running kernel whenever you want).
10272 The module will be called digi_acceleport.o. If you want to compile
10273 it as a module, say M here and read Documentation/modules.txt.
10275 USB Serial Converter verbose debug
10276 CONFIG_USB_SERIAL_DEBUG
10277 Say Y here if you want verbose debug messages from the USB Serial
10280 USB Printer support
10282 Say Y here if you want to connect a USB printer to your computer's
10285 This code is also available as a module ( = code which can be
10286 inserted in and removed from the running kernel whenever you want).
10287 The module will be called printer.o. If you want to compile it as a
10288 module, say M here and read Documentation/modules.txt.
10290 USB IBM (Xirlink) C-It Camera support
10292 Say Y here if you want to connect a IBM "C-It" camera, also known as
10293 "Xirlink PC Camera" to your computer's USB port. For more
10294 information, read Documentation/usb/ibmcam.txt.
10296 This driver uses the Video For Linux API. You must enable
10297 (Y or M in config) Video For Linux (under Character Devices)
10298 to use this driver. Information on this API and pointers to
10299 "v4l" programs may be found on the WWW at
10300 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10302 This code is also available as a module ( = code which can be
10303 inserted in and removed from the running kernel whenever you want).
10304 The module will be called ibmcam.o. If you want to compile it as a
10305 module, say M here and read Documentation/modules.txt. This camera
10306 has several configuration options which can be specified when you
10307 load the module. Read Documentation/usb/ibmcam.txt to learn more.
10309 USB OV511 Camera support
10311 Say Y here if you want to connect this type of camera to your
10312 computer's USB port. See Documentation/usb/ov511.txt for more
10313 information and for a list of supported cameras.
10315 This driver uses the Video For Linux API. You must say Y or M to
10316 "Video For Linux" (under Character Devices) to use this driver.
10317 Information on this API and pointers to "v4l" programs may be found
10318 on the WWW at http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10320 This code is also available as a module ( = code which can be
10321 inserted in and removed from the running kernel whenever you want).
10322 The module will be called ov511.o. If you want to compile it as a
10323 module, say M here and read Documentation/modules.txt.
10325 USB ADMtek Pegasus-based ethernet device support
10327 Say Y if you want to use your USB ethernet device. Supported
10328 cards until now are:
10329 ADMtek AN986 Pegasus (eval. board)
10330 ADMtek ADM8511 Pegasus II (eval. board)
10333 Corega FEter USB-TX
10334 MELCO/BUFFALO LUA-TX
10335 D-Link DSB-650TX, DSB-650TX-PNA, DSB-650, DU-E10, DU-E100
10336 Linksys USB100TX, USB10TX
10337 LANEED Ethernet LD-USB/TX
10339 SOHOware NUB Ethernet
10341 Any Pegasus II based board also are supported.
10342 If you have devices with vendor IDs other than noted above
10343 you should add them in the driver code and send a message
10344 to me (petkan@dce.bg) for update.
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 pegasus.o. If you want to compile it as a
10349 module, say M here and read Documentation/modules.txt.
10351 USB Kodak DC-2xx Camera support
10353 Say Y here if you want to connect this type of still camera to
10354 your computer's USB port. See Documentation/usb/dc2xx.txt for more
10355 information; some non-Kodak cameras may also work with this
10356 driver, given application support (such as www.gPhoto.org).
10358 This code is also available as a module ( = code which can be
10359 inserted in and removed from the running kernel whenever you want).
10360 The module will be called dc2xx.o. If you want to compile it as a
10361 module, say M here and read Documentation/modules.txt.
10363 USB Mustek MDC800 Digital Camera Support
10365 Say Y here if you want to connect this type of still camera to
10366 your computer's USB port. This driver can be used with gphoto 0.4.3
10367 and higher (look at http://www.gphoto.org ).
10368 To use it create a device node with "mknod /dev/mustek c 180 32" and
10369 configure it in your software.
10371 This code is also available as a module ( = code which can be
10372 inserted in and removed from the running kernel whenever you want).
10373 The module will be called mdc800.o. If you want to compile it as a
10374 module, say M here and read Documentation/modules.txt.
10376 USB Mass Storage support
10378 Say Y here if you want to connect USB mass storage devices to your
10379 computer's USB port.
10381 This code is also available as a module ( = code which can be
10382 inserted in and removed from the running kernel whenever you want).
10383 The module will be called usb-storage.o. If you want to compile it
10384 as a module, say M here and read Documentation/modules.txt.
10386 USB Mass Storage verbose debug
10387 CONFIG_USB_STORAGE_DEBUG
10388 Say Y here in order to have the USB Mass Storage code generate
10389 verbose debugging messages.
10391 USS720 parport driver
10393 This driver is for USB parallel port adapters that use the Lucent
10394 Technologies USS-720 chip. These cables are plugged into your USB
10395 port and provide USB compatibility to peripherals designed with
10396 parallel port interfaces.
10398 The chip has two modes: automatic mode and manual mode. In automatic
10399 mode, it looks to the computer like a standard USB printer. Only
10400 printers may be connected to the USS-720 in this mode. The generic
10401 USB printer driver ("USB Printer support", above) may be used in
10402 that mode, and you can say N here if you want to use the chip only
10405 Manual mode is not limited to printers, any parallel port
10406 device should work. This driver utilizes manual mode.
10407 Note however that some operations are three orders of magnitude
10408 slower than on a PCI/ISA Parallel Port, so timing critical
10409 applications might not work.
10411 Say Y here if you own an USS-720 USB->Parport cable and intend to
10412 connect anything other than a printer to it.
10414 This code is also available as a module ( = code which can be
10415 inserted in and removed from the running kernel whenever you want).
10416 The module will be called uss720.o. If you want to compile it as a
10417 module, say M here and read Documentation/modules.txt.
10419 USB device file system
10420 CONFIG_USB_DEVICEFS
10421 If you say Y here (and to "/proc file system support" below), you
10422 will get a file /proc/usb/devices which lists the devices currently
10423 connected to your USB busses, a file /proc/usb/drivers which lists
10424 the USB kernel client drivers currently loaded, and for every
10425 connected device a file named "/proc/usb/xxx/yyy", where xxx is the
10426 bus number and yyy the device number; the latter files can be used
10427 by user space programs to talk directly to the device. These files
10428 are "virtual", meaning they are generated on the fly and not stored
10431 For the format of the /proc/usb/ files, please read
10432 Documentation/usb/proc_usb_info.txt.
10434 Please note that this code is completely unrelated to devfs, the
10435 "/dev file system support".
10437 Most users want to say Y here.
10439 USB Bandwidth allocation
10440 CONFIG_USB_BANDWIDTH
10441 If you say Y here, the USB subsystem enforces USB bandwidth
10442 allocation and will prevent some device opens from succeeding
10443 if they would cause USB bandwidth usage to go above 90% of
10446 If you say N here, these conditions will cause warning messages
10447 about USB bandwidth usage to be logged and some devices or
10448 drivers may not work correctly.
10452 A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
10453 brought to you by the DAB-Team (http://dab.in.tum.de). This driver
10454 can be taken as an example for URB-based bulk, control, and
10455 isochronous transactions. URB's are explained in
10456 Documentation/usb/URB.txt.
10458 This code is also available as a module ( = code which can be
10459 inserted in and removed from the running kernel whenever you want).
10460 The module will be called dabusb.o. If you want to compile it as a
10461 module, say M here and read Documentation/modules.txt.
10465 A driver for the Prolific PL-2302 USB-to-USB network device. This
10466 'USB cable' connects two hosts via a point-to-point network with
10467 bandwidth of 5 Mbit/s. Configure this driver after connecting the
10468 USB cable via ifconfig plusb0 10.0.0.1 pointopoint 10.0.0.2 (and
10469 vice versa on the other host).
10471 This code is also available as a module ( = code which can be
10472 inserted in and removed from the running kernel whenever you want).
10473 The module will be called plusb.o. If you want to compile it as a
10474 module, say M here and read Documentation/modules.txt.
10476 USB Diamond Rio500 support
10478 Say Y here if you want to connect a USB Rio500 mp3 player to your
10479 computer's USB port. Please read Documentation/usb/rio.txt
10480 for more information.
10482 This code is also available as a module ( = code which can be
10483 inserted in and removed from the running kernel whenever you want).
10484 The module will be called rio500.o. If you want to compile it as
10485 a module, say M here and read Documentation/modules.txt.
10487 D-Link DSB-R100 FM radio support
10489 Say Y here if you want to connect this type of radio to your
10490 computer's USB port. Note that the audio is not digital, and
10491 you must connect the line out connector to a sound card or a
10494 This driver uses the Video For Linux API. You must enable
10495 (Y or M in config) Video For Linux (under Character Devices)
10496 to use this driver. Information on this API and pointers to
10497 "v4l" programs may be found on the WWW at
10498 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
10500 This code is also available as a module ( = code which can be
10501 inserted in and removed from the running kernel whenever you want).
10502 The module will be called dsbr100.o. If you want to compile it as a
10503 module, say M here and read Documentation/modules.txt.
10505 Microtek USB scanner support
10506 CONFIG_USB_MICROTEK
10507 Say Y here if you want support for the Microtek X6USB and possibly
10508 some other scanners by that vendor. The scanner will appear as a
10509 scsi generic device to the rest of the system.
10510 A patched version of SANE is necessary to use the
10511 scanner. It's available at
10512 http://fachschaft.cup.uni-muenchen.de/~neukum/scanner.html
10513 This driver can be compiled as a module.
10515 USB Bluetooth support
10516 CONFIG_USB_BLUETOOTH
10517 Say Y here if you want to connect a USB Bluetooth device to your
10518 computer's USB port. You will need the Bluetooth stack (available
10519 at http://developer.axis.com/software/index.shtml) to fully use
10522 This code is also available as a module ( = code which can be
10523 inserted in and removed from the running kernel whenever you want).
10524 The module will be called bluetooth.o. If you want to compile it as
10525 a module, say M here and read Documentation/modules.txt.
10529 Minix is a simple operating system used in many classes about OS's.
10530 The minix file system (method to organize files on a hard disk
10531 partition or a floppy disk) was the original file system for Linux,
10532 but has been superseded by the second extended file system ext2fs.
10533 You don't want to use the minix file system on your hard disk
10534 because of certain built-in restrictions, but it is sometimes found
10535 on older Linux floppy disks. This option will enlarge your kernel by
10536 about 28 KB. If unsure, 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
10541 called minix.o. Note that the file system of your root partition
10542 (the one containing the directory /) cannot be compiled as a module.
10544 Second extended fs support
10546 This is the de facto standard Linux file system (method to organize
10547 files on a storage device) for hard disks.
10549 You want to say Y here, unless you intend to use Linux exclusively
10550 from inside a DOS partition using the UMSDOS file system. The
10551 advantage of the latter is that you can get away without
10552 repartitioning your hard drive (which often implies backing
10553 everything up and restoring afterwards); the disadvantage is that
10554 Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
10555 slower than ext2fs. Even if you want to run Linux in this fashion,
10556 it might be a good idea to have ext2fs around: it enables you to
10557 read more floppy disks and facilitates the transition to a *real*
10558 Linux partition later. Another (rare) case which doesn't require
10559 ext2fs is a diskless Linux box which mounts all files over the
10560 network using NFS (in this case it's sufficient to say Y to "NFS
10561 file system support" below). Saying Y here will enlarge your kernel
10564 The Ext2fs-Undeletion mini-HOWTO, available from
10565 http://www.linuxdoc.org/docs.html#howto , gives information about
10566 how to retrieve deleted files on ext2fs file systems.
10568 To change the behavior of ext2 file systems, you can use the tune2fs
10569 utility ("man tune2fs"). To modify attributes of files and
10570 directories on ext2 file systems, use chattr ("man chattr").
10572 Ext2fs partitions can be read from within DOS using the ext2tool
10573 command line tool package (available via FTP (user: anonymous) from
10574 ftp://metalab.unc.edu/pub/Linux/system/filesystems/ext2 ) and from
10575 within Windows NT using the ext2nt command line tool package from
10576 ftp://metalab.unc.edu/pub/Linux/utils/dos . Explore2fs is a
10577 graphical explorer for ext2fs partitions which runs on Windows 95
10578 and Windows NT and includes experimental write support; it is
10580 http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm .
10582 If you want to compile this file system as a module ( = code which
10583 can be inserted in and removed from the running kernel whenever you
10584 want), say M here and read Documentation/modules.txt. The module
10585 will be called ext2.o. Be aware however that the file system of your
10586 root partition (the one containing the directory /) cannot be
10587 compiled as a module, and so this could be dangerous. Most everyone
10588 wants to say Y here.
10590 BFS file system support (EXPERIMENTAL)
10592 Boot File System (BFS) is a file system used under SCO UnixWare to
10593 allow the bootloader access to the kernel image and other important
10594 files during the boot process. It is usually mounted under /stand
10595 and corresponds to the slice marked as "STAND" in the UnixWare
10596 partition. You should say Y if you want to read or write
10597 the files on your /stand slice from within Linux. You then also
10598 need to say Y to "UnixWare slices support", below. More information
10599 about the BFS file system is contained in the file
10600 Documentation/filesystems/bfs.txt.
10602 If you don't know what this is about, say N.
10604 If you want to compile this as a module ( = code which can be
10605 inserted in and removed from the running kernel whenever you want),
10606 say M here and read Documentation/modules.txt. The module will be
10607 called bfs.o. Note that the file system of your root partition (the
10608 one containing the directory /) cannot be compiled as a module.
10610 Compressed ROM file system support
10612 Saying Y here includes support for CramFs (Compressed ROM File
10613 System). Cramfs is designed to be a simple, small, and compressed
10614 file system for ROM based embedded systems. CramFs is read-only,
10615 limited to 256MB file systems (with 16MB files), and doesn't support
10616 16/32 bits uid/gid, hard links and timestamps.
10618 See Documentation/filesystems/cramfs.txt and fs/cramfs/README
10619 for further information.
10621 If you want to compile this as a module ( = code which can be
10622 inserted in and removed from the running kernel whenever you want),
10623 say M here and read Documentation/modules.txt. The module will be
10624 called cramfs.o. Note that the root file system (the one containing
10625 the directory /) cannot be compiled as a module.
10629 Simple RAM-based file system support
10631 Ramfs is a file system which keeps all files in RAM. It allows
10632 read and write access.
10634 In contrast to RAM disks, which get allocated a fixed amount of RAM,
10635 ramfs grows and shrinks to accommodate the files it contains.
10637 Before you can use this RAM-based file system, it has to be mounted,
10638 meaning it has to be given a location in the directory hierarchy. If
10639 you want to use the location /ramfiles for example, you would have
10640 to create that directory first and then mount the file system by
10641 saying "mount -t ramfs ramfs /ramfiles" or the equivalent line in
10642 /etc/fstab. Everything is "virtual" in the sense that no files will
10643 be created on your hard drive; if you reboot, everything in
10644 /ramfiles will be lost.
10646 If you want to compile this as a module ( = code which can be
10647 inserted in and removed from the running kernel whenever you want),
10648 say M here and read Documentation/modules.txt. The module will be
10651 ISO 9660 CDROM file system support
10653 This is the standard file system used on CDROMs. It was previously
10654 known as "High Sierra File System" and is called "hsfs" on other
10655 Unix systems. The so-called Rock-Ridge extensions which allow for
10656 long Unix filenames and symbolic links are also supported by this
10657 driver. If you have a CDROM drive and want to do more with it than
10658 just listen to audio CDs and watch its LEDs, say Y (and read
10659 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
10660 from http://www.linuxdoc.org/docs.html#howto ), thereby enlarging
10661 your kernel by about 27 KB; otherwise say N.
10663 If you want to compile this as a module ( = code which can be
10664 inserted in and removed from the running kernel whenever you want),
10665 say M here and read Documentation/modules.txt. The module will be
10668 Microsoft Joliet CDROM extensions
10670 Joliet is a Microsoft extension for the ISO 9660 CDROM file system
10671 which allows for long filenames in unicode format (unicode is the
10672 new 16 bit character code, successor to ASCII, which encodes the
10673 characters of almost all languages of the world; see
10674 http://www.unicode.org for more information). Say Y here if you want
10675 to be able to read Joliet CDROMs under Linux.
10677 UDF File System support (read only)
10679 This is the new file system used on some CDROMs and DVDs. Say Y if
10680 you intend to mount DVD discs or CDRW's written in packet mode, or
10681 if written to by other UDF utilities, such as DirectCD. This UDF
10682 file system support is read-only. If you want to write to UDF
10683 file systems on some media, you need to say Y to "UDF read-write
10684 support" below in addition. Please read
10685 Documentation/filesystems/udf.txt.
10687 This file system support is also available as a module ( = code
10688 which can be inserted in and removed from the running kernel
10689 whenever you want). The module is called udf.o. If you want to
10690 compile it as a module, say M here and read
10691 Documentation/modules.txt.
10695 UDF write support (DANGEROUS)
10697 Say Y if you want to test write support for UDF file systems.
10698 Due to lack of support for writing to CDR/CDRW's, this option
10699 is only supported for hard discs, DVD-RAM, and loopback files.
10703 If you want to use one of the FAT-based file systems (the MS-DOS,
10704 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
10705 ordinary DOS partition) file systems), then you must say Y or M here
10706 to include FAT support. You will then be able to mount partitions or
10707 diskettes with FAT-based file systems and transparently access the
10708 files on them, i.e. MSDOS files will look and behave just like all
10711 This FAT support is not a file system in itself, it only provides
10712 the foundation for the other file systems. You will have to say Y or
10713 M to at least one of "MSDOS fs support" or "VFAT fs support" in
10714 order to make use of it.
10716 Another way to read and write MSDOS floppies and hard drive
10717 partitions from within Linux (but not transparently) is with the
10718 mtools ("man mtools") program suite. You don't need to say Y here in
10721 If you need to move large files on floppies between a DOS and a
10722 Linux box, say Y here, mount the floppy under Linux with an MSDOS
10723 file system and use GNU tar's M option. GNU tar is a program
10724 available for Unix and DOS ("man tar" or "info tar").
10726 It is now also becoming possible to read and write compressed FAT
10727 file systems; read Documentation/filesystems/fat_cvf.txt for
10730 The FAT support will enlarge your kernel by about 37 KB. If unsure,
10733 If you want to compile this as a module however ( = code which can
10734 be inserted in and removed from the running kernel whenever you
10735 want), say M here and read Documentation/modules.txt. The module
10736 will be called fat.o. Note that if you compile the FAT support as a
10737 module, you cannot compile any of the FAT-based file systems into
10738 the kernel -- they will have to be modules as well. The file system
10739 of your root partition (the one containing the directory /) cannot
10740 be a module, so don't say M here if you intend to use UMSDOS as your
10745 This allows you to mount MSDOS partitions of your hard drive (unless
10746 they are compressed; to access compressed MSDOS partitions under
10747 Linux, you can either use the DOS emulator DOSEMU, described in the
10748 DOSEMU-HOWTO, available from
10749 http://www.linuxdoc.org/docs.html#howto , or try dmsdosfs in
10750 ftp://metalab.unc.edu/pub/Linux/system/filesystems/dosfs . If you
10751 intend to use dosemu with a non-compressed MSDOS partition, say Y
10752 here) and MSDOS floppies. This means that file access becomes
10753 transparent, i.e. the MSDOS files look and behave just like all
10756 If you want to use UMSDOS, the Unix-like file system on top of a
10757 DOS file system, which allows you to run Linux from within a DOS
10758 partition without repartitioning, you'll have to say Y or M here.
10760 If you have Windows 95 or Windows NT installed on your MSDOS
10761 partitions, you should use the VFAT file system (say Y to "VFAT fs
10762 support" below), or you will not be able to see the long filenames
10763 generated by Windows 95 / Windows NT.
10765 This option will enlarge your kernel by about 7 KB. If unsure,
10766 answer Y. This will only work if you said Y to "DOS FAT fs support"
10767 as well. If you want to compile this as a module however ( = code
10768 which can be inserted in and removed from the running kernel
10769 whenever you want), say M here and read Documentation/modules.txt.
10770 The module will be called msdos.o.
10772 VFAT (Windows-95) fs support
10774 This option provides support for normal Windows file systems with
10775 long filenames. That includes non-compressed FAT-based file systems
10776 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
10777 programs from the mtools package.
10779 You cannot use the VFAT file system for your Linux root partition
10780 (the one containing the directory /); use UMSDOS instead if you
10781 want to run Linux from within a DOS partition (i.e. say Y to
10782 "UMSDOS: Unix like fs on top of std MSDOS fs", below).
10784 The VFAT support enlarges your kernel by about 10 KB and it only
10785 works if you said Y to the "DOS FAT fs support" above. Please read
10786 the file Documentation/filesystems/vfat.txt for details. If unsure,
10789 If you want to compile this as a module ( = code which can be
10790 inserted in and removed from the running kernel whenever you want),
10791 say M here and read Documentation/modules.txt. The module will be
10794 UMSDOS: Unix-like file system on top of standard MSDOS fs
10796 Say Y here if you want to run Linux from within an existing DOS
10797 partition of your hard drive. The advantage of this is that you can
10798 get away without repartitioning your hard drive (which often implies
10799 backing everything up and restoring afterwards) and hence you're
10800 able to quickly try out Linux or show it to your friends; the
10801 disadvantage is that Linux becomes susceptible to DOS viruses and
10802 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
10803 is to write files with long unix filenames to MSDOS floppies; it
10804 also allows Unix-style soft-links and owner/permissions of files on
10805 MSDOS floppies. You will need a program called umssync in order to
10806 make use of UMSDOS; read Documentation/filesystems/umsdos.txt.
10808 To get utilities for initializing/checking UMSDOS file system, or
10809 latest patches and/or information, visit the UMSDOS home page at
10810 http://www.voyager.hr/~mnalis/umsdos/ .
10812 This option enlarges your kernel by about 28 KB and it only works if
10813 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
10814 above. If you want to compile this as a module ( = code which can be
10815 inserted in and removed from the running kernel whenever you want),
10816 say M here and read Documentation/modules.txt. The module will be
10817 called umsdos.o. Note that the file system of your root partition
10818 (the one containing the directory /) cannot be a module, so saying M
10819 could be dangerous. If unsure, say N.
10821 /proc file system support
10823 This is a virtual file system providing information about the status
10824 of the system. "Virtual" means that it doesn't take up any space on
10825 your hard disk: the files are created on the fly by the kernel when
10826 you try to access them. Also, you cannot read the files with older
10827 version of the program less: you need to use more or cat.
10829 It's totally cool; for example, "cat /proc/interrupts" gives
10830 information about what the different IRQs are used for at the moment
10831 (there is a small number of Interrupt ReQuest lines in your computer
10832 that are used by the attached devices to gain the CPU's attention --
10833 often a source of trouble if two devices are mistakenly configured
10834 to use the same IRQ). The program procinfo to display some
10835 information about your system gathered from the /proc file system.
10837 Before you can use the /proc file system, it has to be mounted,
10838 meaning it has to be given a location in the directory hierarchy.
10839 That location should be /proc. A command such as "mount -t proc proc
10840 /proc" or the equivalent line in /etc/fstab does the job.
10842 The /proc file system is explained in the file
10843 Documentation/filesystems/proc.txt and on the proc(5) manpage ("man
10846 This option will enlarge your kernel by about 67 KB. Several
10847 programs depend on this, so everyone should say Y here.
10849 /dev file system support (EXPERIMENTAL)
10851 This is support for devfs, a virtual file system (like /proc) which
10852 provides the file system interface to device drivers, normally found
10853 in /dev. Devfs does not depend on major and minor number
10854 allocations. Device drivers register entries in /dev which then
10855 appear automatically, which means that the system administrator does
10856 not have to create character and block special device files in the
10857 /dev directory using the mknod command (or MAKEDEV script) anymore.
10859 This is work in progress. If you want to use this, you *must* read
10860 the material in Documentation/filesystems/devfs/, especially the
10865 Enable automatic mounting at boot
10867 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
10868 this to 'Y' will make the kernel automatically mount devfs onto /dev
10869 when the system is booted, before the init thread is started.
10870 You can override this with the "devfs=nomount" boot option.
10876 If you say Y here, then the /dev file system code will generate
10877 debugging messages. See the file
10878 Documentation/filesystems/devfs/boot-options for more details.
10882 NFS file system support
10884 If you are connected to some other (usually local) Unix computer
10885 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
10886 on that computer (the NFS server) using the Network File Sharing
10887 protocol, say Y. "Mounting files" means that the client can access
10888 the files with usual UNIX commands as if they were sitting on the
10889 client's hard disk. For this to work, the server must run the
10890 programs nfsd and mountd (but does not need to have NFS file system
10891 support enabled in its kernel). NFS is explained in the Network
10892 Administrator's Guide, available from
10893 http://www.linuxdoc.org/docs.html#guide , on its man page: "man
10894 nfs", and in the NFS-HOWTO.
10896 A superior but less widely used alternative to NFS is provided by
10897 the Coda file system; see "Coda file system support" below.
10899 If you say Y here, you should have said Y to TCP/IP networking also.
10900 This option would enlarge your kernel by about 27 KB.
10902 This file system is also available as a module ( = code which can be
10903 inserted in and removed from the running kernel whenever you want).
10904 The module is called nfs.o. If you want to compile it as a module,
10905 say M here and read Documentation/modules.txt.
10907 If you are configuring a diskless machine which will mount its root
10908 file system over NFS at boot time, say Y here and to "IP: kernel
10909 level autoconfiguration" above and to "Root file system on NFS"
10910 below. You cannot compile this driver as a module in this case.
10911 There are two packages designed for booting diskless machines over
10912 the net: netboot and etherboot, both available via FTP from
10913 ftp://metalab.unc.edu/pub/Linux/system/boot/ethernet/ .
10915 If you don't know what all this is about, say N.
10917 Provide NFSv3 client support (EXPERIMENTAL)
10919 Say Y here if you want your NFS client to be able to speak the newer
10920 version 3 of the NFS protocol.
10924 Root file system on NFS
10926 If you want your Linux box to mount its whole root file system (the
10927 one containing the directory /) from some other computer over the
10928 net via NFS (presumably because your box doesn't have a hard disk),
10929 say Y. Read Documentation/nfsroot.txt for details. It is likely that
10930 in this case, you also want to say Y to "IP: kernel level
10931 autoconfiguration" so that your box can discover its network address
10934 Most people say N here.
10938 If you want your Linux box to act as an NFS *server*, so that other
10939 computers on your local network which support NFS can access certain
10940 directories on your box transparently, you have two options: you can
10941 use the self-contained user space program nfsd, in which case you
10942 should say N here, or you can say Y and use the kernel based NFS
10943 server. The advantage of the kernel based solution is that it is
10946 In either case, you will need support software; the respective
10947 locations are given in the file Documentation/Changes in the NFS
10950 If you say Y here, you will get support for version 2 of the NFS
10951 protocol (NFSv2). If you also want NFSv3, say Y to the next question
10954 Please read the NFS-HOWTO, available from
10955 http://www.linuxdoc.org/docs.html#howto .
10957 The NFS server is also available as a module ( = code which can be
10958 inserted in and removed from the running kernel whenever you want).
10959 The module is called nfsd.o. If you want to compile it as a module,
10960 say M here and read Documentation/modules.txt. If unsure, say N.
10962 Provide NFSv3 server support
10964 If you would like to include the NFSv3 server as well as the NFSv2
10965 server, say Y here. If unsure, say Y.
10967 Provide NFS over TCP server support DEVELOPER ONLY
10969 If you are a developer and want to work on fixing problems with
10970 NFS server over TCP support, say Y here. If unsure, say N.
10972 Some problems can be found by looking for FIXME in net/sunrpc/svcsock.c
10974 OS/2 HPFS file system support
10976 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
10977 is the file system used for organizing files on OS/2 hard disk
10978 partitions. Say Y if you want to be able to read files from and
10979 write files to an OS/2 HPFS partition on your hard drive. OS/2
10980 floppies however are in regular MSDOS format, so you don't need this
10981 option in order to be able to read them. Read
10982 Documentation/filesystems/hpfs.txt.
10984 This file system is also available as a module ( = code which can be
10985 inserted in and removed from the running kernel whenever you want).
10986 The module is called hpfs.o. If you want to compile it as a module,
10987 say M here and read Documentation/modules.txt. If unsure, say N.
10989 NTFS support (read only)
10991 NTFS is the file system of Microsoft Windows NT. Say Y if you want
10992 to get read access to files on NTFS partitions of your hard drive.
10993 The Linux NTFS driver supports most of the mount options of the VFAT
10994 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
10995 give you read-only access to NTFS partitions.
10997 This code is also available as a module ( = code which can be
10998 inserted in and removed from the running kernel whenever you want).
10999 The module will be called ntfs.o. If you want to compile it as a
11000 module, say M here and read Documentation/modules.txt.
11002 NTFS write support (DANGEROUS)
11004 If you say Y here, you will (maybe) be able to write to NTFS file
11005 systems as well as read from them. The read-write support in
11006 NTFS is far from being complete and is not well tested. If you
11007 say Y here, back up your NTFS volume first since it may get
11008 damaged. Also, make sure to run chkdsk from within Microsoft
11009 Windows NT after having performed any writes to a NTFS partition
11010 from Linux to detect any problems as early as possible.
11011 Please note that write support is limited to Windows NT4 and
11016 System V and Coherent file system support (read only)
11018 SCO, Xenix and Coherent are commercial Unix systems for Intel
11019 machines. Saying Y here would allow you to read from their floppies
11020 and hard disk partitions. If you also want to write to these media,
11021 say Y to "SYSV file system write support" below.
11023 If you have floppies or hard disk partitions like that, it is likely
11024 that they contain binaries from those other Unix systems; in order
11025 to run these binaries, you will want to install iBCS2 (Intel Binary
11026 Compatibility Standard is a kernel module which lets you run SCO,
11027 Xenix, Wyse, UnixWare, Dell Unix and System V programs under Linux
11028 and is often needed to run commercial software that's only available
11029 for those systems. It's available via FTP (user: anonymous) from
11030 ftp://tsx-11.mit.edu/pub/linux/BETA ).
11032 If you only intend to mount files from some other Unix over the
11033 network using NFS, you don't need the System V file system support
11034 (but you need NFS file system support obviously).
11036 Note that this option is generally not needed for floppies, since a
11037 good portable way to transport files and directories between unixes
11038 (and even other operating systems) is given by the tar program ("man
11039 tar" or preferably "info tar"). Note also that this option has
11040 nothing whatsoever to do with the option "System V IPC". Read about
11041 the System V file system in Documentation/filesystems/sysv-fs.txt.
11042 Saying Y here will enlarge your kernel by about 27 KB.
11044 If you want to compile this as a module ( = code which can be
11045 inserted in and removed from the running kernel whenever you want),
11046 say M here and read Documentation/modules.txt. The module will be
11049 If you haven't heard about all of this before, it's safe to say N.
11051 SYSV file system write support (DANGEROUS)
11052 CONFIG_SYSV_FS_WRITE
11053 If you say Y here, you will be able to write to hard drive
11054 partitions and floppy disks which carry a SYSV file system used the
11055 commercial Unixes SCO, Xenix and Coherent.
11057 This support is experimental and you may destroy your data. If
11060 Amiga FFS file system support
11062 The Fast File System (FFS) is the common file system used on hard
11063 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
11064 if you want to be able to read and write files from and to an Amiga
11065 FFS partition on your hard drive. Amiga floppies however cannot be
11066 read with this driver due to an incompatibility of the floppy
11067 controller used in an Amiga and the standard floppy controller in
11068 PCs and workstations. Read Documentation/filesystems/affs.txt and
11071 With this driver you can also mount disk files used by Bernd
11072 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/ ).
11073 If you want to do this, you will also need to say Y or M to "Loop
11074 device support", above.
11076 This file system is also available as a module ( = code which can be
11077 inserted in and removed from the running kernel whenever you want).
11078 The module is called affs.o. If you want to compile it as a module,
11079 say M here and read Documentation/modules.txt. If unsure, say N.
11081 Apple Macintosh file system support (EXPERIMENTAL)
11083 If you say Y here, you will be able to mount Macintosh-formatted
11084 floppy disks and hard drive partitions with full read-write access.
11085 Please read fs/hfs/HFS.txt to learn about the available mount
11088 This file system support is also available as a module ( = code
11089 which can be inserted in and removed from the running kernel
11090 whenever you want). The module is called hfs.o. If you want to
11091 compile it as a module, say M here and read
11092 Documentation/modules.txt.
11094 ROM file system support
11096 This is a very small read-only file system mainly intended for
11097 initial ram disks of installation disks, but it could be used for
11098 other read-only media as well. Read
11099 Documentation/filesystems/romfs.txt for details.
11101 This file system support is also available as a module ( = code
11102 which can be inserted in and removed from the running kernel
11103 whenever you want). The module is called romfs.o. If you want to
11104 compile it as a module, say M here and read
11105 Documentation/modules.txt. Note that the file system of your root
11106 partition (the one containing the directory /) cannot be a module.
11108 If you don't know whether you need it, then you don't need it:
11111 QNX4 file system support (read only) (EXPERIMENTAL)
11113 This is the file system used by the operating system QNX 4. Say Y if
11114 you intend to mount QNX hard disks or floppies. Unless you say Y to
11115 "QNX4FS read-write support" below, you will only be able to read
11116 these file systems.
11118 This file system support is also available as a module ( = code
11119 which can be inserted in and removed from the running kernel
11120 whenever you want). The module is called qnx4.o. If you want to
11121 compile it as a module, say M here and read
11122 Documentation/modules.txt.
11124 If you don't know whether you need it, then you don't need it:
11127 QNX4FS write support (DANGEROUS)
11129 Say Y if you want to test write support for QNX4 file systems.
11131 Kernel automounter support
11133 The automounter is a tool to automatically mount remote file systems
11134 on demand. This implementation is partially kernel-based to reduce
11135 overhead in the already-mounted case; this is unlike the BSD
11136 automounter (amd), which is a pure user space daemon.
11138 To use the automounter you need the user-space tools from the autofs
11139 package; you can find the location in Documentation/Changes. You
11140 also want to answer Y to "NFS file system support", below.
11142 If you want to use the newer version of the automounter with more
11143 features, say N here and say Y to "Kernel automounter v4 support",
11146 If you want to compile this as a module ( = code which can be
11147 inserted in and removed from the running kernel whenever you want),
11148 say M here and read Documentation/modules.txt. The module will be
11151 If you are not a part of a fairly large, distributed network, you
11152 probably do not need an automounter, and can say N here.
11154 Kernel automounter v4 support
11156 The automounter is a tool to automatically mount remote file systems
11157 on demand. This implementation is partially kernel-based to reduce
11158 overhead in the already-mounted case; this is unlike the BSD
11159 automounter (amd), which is a pure user space daemon.
11161 To use the automounter you need the user-space tools from
11162 ftp://ftp.kernel.org/pub/linux/daemons/autofs/testing-v4 ; you also
11163 want to answer Y to "NFS file system support", below.
11165 If you want to compile this as a module ( = code which can be
11166 inserted in and removed from the running kernel whenever you want),
11167 say M here and read Documentation/modules.txt. The module will be
11168 called autofs4.o. You will need to add "alias autofs autofs4" to
11169 your modules configuration file.
11171 If you are not a part of a fairly large, distributed network or
11172 don't have a laptop which needs to dynamically reconfigure to the
11173 local network, you probably do not need an automounter, and can say
11176 EFS file system support (read-only) (EXPERIMENTAL)
11178 EFS is an older file system used for non-ISO9660 CDROMs and hard
11179 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
11180 uses the XFS file system for hard disk partitions however).
11182 This implementation only offers read-only access. If you don't know
11183 what all this is about, it's safe to say N. For more information
11184 about EFS see its home page at http://aeschi.ch.eu.org/efs/ .
11186 If you want to compile the EFS file system support as a module ( =
11187 code which can be inserted in and removed from the running kernel
11188 whenever you want), say M here and read Documentation/modules.txt.
11189 The module will be called efs.o.
11191 Journalling Flash File System (JFFS) support (EXPERIMENTAL)
11193 JFFS is a new file system designed for use on flash memory devices
11194 rather than on block devices. It was developed on the 2.0 kernel
11195 by Axis Communications AB for use on their Linux-based products,
11196 and released under GPL, then 'borrowed' and ported to work with
11197 the 2.4 kernel and the new Memory Technology Device system.
11199 The 2.4 port is experimental and not yet supported by Axis. Basically,
11200 the good bits are probably theirs, and if it's broken in 2.4 it's
11201 probably our fault. See http://www.developer.axis.com/software/jffs/
11202 for more information about JFFS.
11204 Any potential patches or queries should be sent to Axis' mailing
11205 list for JFFS: <jffs-dev@axis.com>
11207 UFS file system support (read-only)
11209 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
11210 OpenBSD and NeXTstep) use a file system called UFS. Some System V
11211 Unixes can create and mount hard disk partitions and diskettes using
11212 this file system as well. Saying Y here will allow you to read from
11213 these partitions; if you also want to write to them, say Y to the
11214 experimental "UFS file system write support", below. Please read the
11215 file Documentation/filesystems/ufs.txt for more information.
11217 If you only intend to mount files from some other Unix over the
11218 network using NFS, you don't need the UFS file system support (but
11219 you need NFS file system support obviously).
11221 Note that this option is generally not needed for floppies, since a
11222 good portable way to transport files and directories between unixes
11223 (and even other operating systems) is given by the tar program ("man
11224 tar" or preferably "info tar").
11226 When accessing NeXTstep files, you may need to convert them from the
11227 NeXT character set to the Latin1 character set; use the program
11228 recode ("info recode") for this purpose.
11230 If you want to compile the UFS file system support as a module ( =
11231 code which can be inserted in and removed from the running kernel
11232 whenever you want), say M here and read Documentation/modules.txt.
11233 The module will be called ufs.o.
11235 If you haven't heard about all of this before, it's safe to say N.
11237 UFS file system write support (DANGEROUS)
11238 CONFIG_UFS_FS_WRITE
11239 Say Y here if you want to try writing to UFS partitions. This is
11240 experimental, so you should back up your UFS partitions beforehand.
11242 Advanced partition selection
11243 CONFIG_PARTITION_ADVANCED
11244 Say Y here if you would like to use hard disks under Linux which
11245 were partitioned under an operating system running on a different
11246 architecture than your Linux system.
11248 Note that the answer to this question won't directly affect the
11249 kernel: saying N will just cause this configure script to skip all
11250 the questions about foreign partitioning schemes.
11254 Alpha OSF partition support
11255 CONFIG_OSF_PARTITION
11256 Say Y here if you would like to use hard disks under Linux which
11257 were partitioned on an Alpha machine.
11259 Macintosh partition map support
11260 CONFIG_MAC_PARTITION
11261 Say Y here if you would like to use hard disks under Linux which
11262 were partitioned on a Macintosh.
11264 PC BIOS (MSDOS partition tables) support
11265 CONFIG_MSDOS_PARTITION
11266 Say Y here if you would like to use hard disks under Linux which
11267 were partitioned on an x86 PC (not necessarily by DOS).
11269 BSD disklabel (FreeBSD partition tables) support
11270 CONFIG_BSD_DISKLABEL
11271 FreeBSD uses its own hard disk partition scheme on your PC. It
11272 requires only one entry in the primary partition table of your disk
11273 and manages it similarly to DOS extended partitions, putting in its
11274 first sector a new partition table in BSD disklabel format. Saying Y
11275 here allows you to read these disklabels and further mount FreeBSD
11276 partitions from within Linux if you have also said Y to "UFS
11277 file system support", above. If you don't know what all this is
11280 Sun partition tables support
11281 CONFIG_SUN_PARTITION
11282 Like most systems, SunOS uses its own hard disk partition table
11283 format, incompatible with all others. Saying Y here allows you to
11284 read these partition tables and further mount SunOS partitions from
11285 within Linux if you have also said Y to "UFS file system support",
11286 above. This is mainly used to carry data from a SPARC under SunOS to
11287 your Linux box via a removable medium like magneto-optical or ZIP
11288 drives; note however that a good portable way to transport files and
11289 directories between unixes (and even other operating systems) is
11290 given by the tar program ("man tar" or preferably "info tar"). If
11291 you don't know what all this is about, say N.
11293 Solaris (x86) partition table support
11294 CONFIG_SOLARIS_X86_PARTITION
11295 Like most systems, Solaris x86 uses its own hard disk partition
11296 table format, incompatible with all others. Saying Y here allows you
11297 to read these partition tables and further mount Solaris x86
11298 partitions from within Linux if you have also said Y to "UFS
11299 file system support", above.
11301 SGI partition support
11302 CONFIG_SGI_PARTITION
11303 Say Y here if you would like to be able to read the hard disk
11304 partition table format used by SGI machines.
11306 ADFS file system support (EXPERIMENTAL)
11308 The Acorn Disc Filing System is the standard file system of the
11309 RiscOS operating system which runs on Acorn's ARM-based Risc PC
11310 systems and the Acorn Archimedes range of machines. If you say Y
11311 here, Linux will be able to read from ADFS partitions on hard drives
11312 and from ADFS-formatted floppy discs. If you also want to be able to
11313 write to those devices, say Y to "ADFS write support" below.
11315 The ADFS partition should be the first partition (i.e.,
11316 /dev/[hs]d?1) on each of your drives. Please read the file
11317 Documentation/filesystems/adfs.txt for further details.
11319 This code is also available as a module called adfs.o ( = code which
11320 can be inserted in and removed from the running kernel whenever you
11321 want). If you want to compile it as a module, say M here and read
11322 Documentation/modules.txt.
11326 ADFS write support (DANGEROUS)
11328 If you say Y here, you will be able to write to ADFS partitions on
11329 hard drives and ADFS-formatted floppy disks. This is experimental
11330 codes, so if you're unsure, say N.
11332 /dev/pts file system for Unix98 PTYs
11334 You should say Y here if you said Y to "Unix98 PTY support" above.
11335 You'll then get a virtual file system which can be mounted on
11336 /dev/pts with "mount -t devpts". This, together with the pseudo
11337 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
11338 support as described in The Open Group's Unix98 standard: in order
11339 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
11340 of the pseudo terminal is then made available to the process and the
11341 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
11342 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
11344 The GNU C library glibc 2.1 contains the requisite support for this
11345 mode of operation; you also need client programs that use the Unix98
11346 API. Please read Documentation/Changes for more information about
11347 the Unix98 pty devices.
11349 Note that the experimental "/dev file system support"
11350 (CONFIG_DEVFS_FS) is a more general facility.
11352 UnixWare slices support (EXPERIMENTAL)
11353 CONFIG_UNIXWARE_DISKLABEL
11354 Like some systems, UnixWare uses its own slice table inside a
11355 partition (VTOC - Virtual Table of Contents). Its format is
11356 incompatible with all other OSes. Saying Y here allows you to read
11357 VTOC and further mount UnixWare partitions read-only from within
11358 Linux if you have also said Y to "UFS file system support" or
11359 "System V and Coherent file system support", above.
11361 This is mainly used to carry data from a UnixWare box to your
11362 Linux box via a removable medium like magneto-optical, ZIP or
11363 removable IDE drives. Note, however, that a good portable way to
11364 transport files and directories between unixes (and even other
11365 operating systems) is given by the tar program ("man tar" or
11366 preferably "info tar").
11368 If you don't know what all this is about, say N.
11370 SMB file system support (to mount Windows shares etc.)
11372 SMB (Server Message Block) is the protocol Windows for Workgroups
11373 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
11374 files and printers over local networks. Saying Y here allows you to
11375 mount their file systems (often called "shares" in this context) and
11376 access them just like any other Unix directory. Currently, this
11377 works only if the Windows machines use TCP/IP as the underlying
11378 transport protocol, and not NetBEUI. For details, read
11379 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available
11380 from http://www.linuxdoc.org/docs.html#howto .
11382 Note: if you just want your box to act as an SMB *server* and make
11383 files and printing services available to Windows clients (which need
11384 to have a TCP/IP stack), you don't need to say Y here; you can use
11385 the program samba (available via FTP (user: anonymous) in
11386 ftp://metalab.unc.edu/pub/Linux/system/network/samba ) for that.
11388 General information about how to connect Linux, Windows machines and
11389 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11391 If you want to compile the SMB support as a module ( = code which
11392 can be inserted in and removed from the running kernel whenever you
11393 want), say M here and read Documentation/modules.txt. The module
11394 will be called smbfs.o. Most people say N, however.
11397 CONFIG_SMB_NLS_DEFAULT
11398 Enabling this will make smbfs use nls translations by default. You
11399 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
11400 settings and you need to give the default nls for the SMB server as
11401 CONFIG_SMB_NLS_REMOTE.
11403 The nls settings can be changed at mount time, if your smbmount
11404 supports that, using the codepage and iocharset parameters.
11406 Currently no smbmount distributed with samba supports this, it is
11407 assumed future versions will. In the meantime you can get an
11408 unofficial patch for samba 2.0.7 from:
11409 http://www.hojdpunkten.ac.se/054/samba/index.html
11411 nls support setting
11412 CONFIG_SMB_NLS_REMOTE
11413 This setting allows you to specify a default value for which
11414 codepage the server uses. If this field is left blank no
11415 translations will be done by default. The local codepage/charset
11416 default to CONFIG_NLS_DEFAULT.
11418 The nls settings can be changed at mount time, if your smbmount
11419 supports that, using the codepage and iocharset parameters.
11421 Currently no smbmount distributed with samba supports this, it is
11422 assumed future versions will. In the meantime you can get an
11423 unofficial patch for samba 2.0.7 from:
11424 http://www.hojdpunkten.ac.se/054/samba/index.html
11426 Coda file system support (advanced network fs)
11428 Coda is an advanced network file system, similar to NFS in that it
11429 enables you to mount file systems of a remote server and access them
11430 with regular Unix commands as if they were sitting on your hard
11431 disk. Coda has several advantages over NFS: support for disconnected
11432 operation (e.g. for laptops), read/write server replication,
11433 security model for authentication and encryption, persistent client
11434 caches and write back caching.
11436 If you say Y here, your Linux box will be able to act as a Coda
11437 *client*. You will need user level code as well, both for the client
11438 and server. Servers are currently user level, i.e. they need no
11439 kernel support. Please read Documentation/filesystems/coda.txt and
11440 check out the Coda home page http://www.coda.cs.cmu.edu .
11442 If you want to compile the coda client support as a module ( = code
11443 which can be inserted in and removed from the running kernel
11444 whenever you want), say M here and read Documentation/modules.txt.
11445 The module will be called coda.o.
11447 NCP file system support (to mount NetWare volumes)
11449 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
11450 used by Novell NetWare clients to talk to file servers. It is to IPX
11451 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
11452 mount NetWare file server volumes and to access them just like any
11453 other Unix directory. For details, please read the file
11454 Documentation/filesystems/ncpfs.txt in the kernel source and the
11455 IPX-HOWTO from http://www.linuxdoc.org/docs.html#howto .
11457 You do not have to say Y here if you want your Linux box to act as a
11458 file *server* for Novell NetWare clients.
11460 General information about how to connect Linux, Windows machines and
11461 Macs is on the WWW at http://www.eats.com/linux_mac_win.html .
11463 If you want to compile this as a module ( = code which can be
11464 inserted in and removed from the running kernel whenever you want),
11465 say M here and read Documentation/modules.txt. The module will be
11466 called ncpfs.o. Say N unless you are connected to a Novell network.
11469 CONFIG_NCPFS_PACKET_SIGNING
11470 NCP allows packets to be signed for stronger security. If you want
11471 security, say Y. Normal users can leave it off. To be able to use
11472 packet signing you must use ncpfs > 2.0.12.
11474 Proprietary file locking
11475 CONFIG_NCPFS_IOCTL_LOCKING
11476 Allows locking of records on remote volumes. Say N unless you have
11477 special applications which are able to utilize this locking scheme.
11479 Clear remove/delete inhibit when needed
11480 CONFIG_NCPFS_STRONG
11481 Allows manipulation of files flagged as Delete or Rename Inhibit. To
11482 use this feature you must mount volumes with the ncpmount parameter
11483 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
11484 volumes with -f 444.
11486 Use NFS namespace when available
11487 CONFIG_NCPFS_NFS_NS
11488 Allows you to utilize NFS namespace on NetWare servers. It brings
11489 you case sensitive filenames. Say Y. You can disable it at
11490 mount-time with the `-N nfs' parameter of ncpmount.
11492 Use OS2/LONG namespace when available
11493 CONFIG_NCPFS_OS2_NS
11494 Allows you to utilize OS2/LONG namespace on NetWare servers.
11495 Filenames in this namespace are limited to 255 characters, they are
11496 case insensitive, and case in names is preserved. Say Y. You can
11497 disable it at mount time with the -N os2 parameter of ncpmount.
11499 Lowercase DOS filenames on LONG namespace volume
11500 CONFIG_NCPFS_SMALLDOS
11501 If you say Y here, every filename on a NetWare server volume using
11502 the OS2/LONG namespace and created under DOS or on a volume using
11503 DOS namespace will be converted to lowercase characters.
11504 Saying N here will give you these filenames in uppercase.
11506 This is only a cosmetic option since the OS2/LONG namespace is case
11507 insensitive. The only major reason for this option is backward
11508 compatibility when moving from DOS to OS2/LONG namespace support.
11509 Long filenames (created by Win95) will not be affected.
11511 This option does not solve the problem that filenames appear
11512 differently under Linux and under Windows, since Windows does an
11513 additional conversions on the client side. You can achieve similar
11514 effects by saying Y to "Allow using of Native Language Support"
11517 Allow mounting of volume subdirectories
11518 CONFIG_NCPFS_MOUNT_SUBDIR
11519 Allows you to mount not only whole servers or whole volumes, but
11520 also subdirectories from a volume. It can be used to reexport data
11521 and so on. There is no reason to say N, so Y is recommended unless
11522 you count every byte.
11524 To utilize this feature you must use ncpfs-2.0.12 or newer.
11526 NDS authentication support
11527 CONFIG_NCPFS_NDS_DOMAINS
11528 This allows storing NDS private keys in kernel space where they
11529 can be used to authenticate another server as interserver NDS
11530 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
11531 this feature. Say Y if you are using NDS connections to NetWare
11532 servers. Do not say Y if security is primary for you because root
11533 can read your session key (from /proc/kcore).
11535 Allow using of Native Language Support
11537 Allows you to use codepages and I/O charsets for file name
11538 translation between the server file system and input/output. This
11539 may be useful, if you want to access the server with other operating
11540 systems, e.g. Windows 95. See also NLS for more Information.
11542 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
11544 Symbolic links and mode permission bits
11545 CONFIG_NCPFS_EXTRAS
11546 This enables the use of symbolic links and an execute permission
11547 bit on NCPFS. The file server need not have long name space or NFS
11548 name space loaded for these to work.
11550 To use the new attributes, it is recommended to use the flags
11551 '-f 600 -d 755' on the ncpmount command line.
11553 nls default codepage
11555 The default NLS used when mounting filesystem. Currently, the valid
11557 big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
11558 cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
11559 cp949, cp950, euc-jp, euc-kr, gb2312, iso8859-1, iso8859-2, iso8859-3,
11560 iso8859-4, iso8859-5, iso8859-6, iso8859-7, iso8859-8, iso8859-9,
11561 iso8859-14, iso8859-15, koi8-r, sjis
11562 If you specify a wrong value, it will use the built-in NLS; compatible
11565 If unsure, specify it as "iso8859-1".
11568 CONFIG_NLS_CODEPAGE_437
11569 The Microsoft FAT file system family can deal with filenames in
11570 native language character sets. These character sets are stored
11571 in so-called DOS codepages. You need to include the appropriate
11572 codepage if you want to be able to read/write these filenames on
11573 DOS/Windows partitions correctly. This does apply to the filenames
11574 only, not to the file contents. You can include several codepages;
11575 say Y here if you want to include the DOS codepage that is used in
11576 the United States and parts of Canada. This is recommended.
11579 CONFIG_NLS_CODEPAGE_737
11580 The Microsoft FAT file system family can deal with filenames in
11581 native language character sets. These character sets are stored
11582 in so-called DOS codepages. You need to include the appropriate
11583 codepage if you want to be able to read/write these filenames on
11584 DOS/Windows partitions correctly. This does apply to the filenames
11585 only, not to the file contents. You can include several codepages;
11586 say Y here if you want to include the DOS codepage that is used for
11587 Greek. If unsure, say N.
11590 CONFIG_NLS_CODEPAGE_775
11591 The Microsoft FAT file system family can deal with filenames in
11592 native language character sets. These character sets are stored
11593 in so-called DOS codepages. You need to include the appropriate
11594 codepage if you want to be able to read/write these filenames on
11595 DOS/Windows partitions correctly. This does apply to the filenames
11596 only, not to the file contents. You can include several codepages;
11597 say Y here if you want to include the DOS codepage that is used
11598 for the Baltic Rim Languages. If unsure, say N.
11601 CONFIG_NLS_CODEPAGE_850
11602 The Microsoft FAT file system family can deal with filenames in
11603 native language character sets. These character sets are stored in
11604 so-called DOS codepages. You need to include the appropriate
11605 codepage if you want to be able to read/write these filenames on
11606 DOS/Windows partitions correctly. This does apply to the filenames
11607 only, not to the file contents. You can include several codepages;
11608 say Y here if you want to include the DOS codepage that is used for
11609 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
11610 more countries here]. It has some characters useful to many European
11611 languages that are not part of the US codepage 437.
11616 CONFIG_NLS_CODEPAGE_852
11617 The Microsoft FAT file system family can deal with filenames in
11618 native language character sets. These character sets are stored in
11619 so-called DOS codepages. You need to include the appropriate
11620 codepage if you want to be able to read/write these filenames on
11621 DOS/Windows partitions correctly. This does apply to the filenames
11622 only, not to the file contents. You can include several codepages;
11623 say Y here if you want to include the Latin 2 codepage used by DOS
11624 for much of Central and Eastern Europe. It has all the required
11625 characters for these languages: Albanian, Croatian, Czech, English,
11626 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
11627 transcription), Slovak, Slovenian, and Sorbian.
11630 CONFIG_NLS_CODEPAGE_855
11631 The Microsoft FAT file system family can deal with filenames in
11632 native language character sets. These character sets are stored in
11633 so-called DOS codepages. You need to include the appropriate
11634 codepage if you want to be able to read/write these filenames on
11635 DOS/Windows partitions correctly. This does apply to the filenames
11636 only, not to the file contents. You can include several codepages;
11637 say Y here if you want to include the DOS codepage for Cyrillic.
11640 CONFIG_NLS_CODEPAGE_857
11641 The Microsoft FAT file system family can deal with filenames in
11642 native language character sets. These character sets are stored in
11643 so-called DOS codepages. You need to include the appropriate
11644 codepage if you want to be able to read/write these filenames on
11645 DOS/Windows partitions correctly. This does apply to the filenames
11646 only, not to the file contents. You can include several codepages;
11647 say Y here if you want to include the DOS codepage for Turkish.
11650 CONFIG_NLS_CODEPAGE_860
11651 The Microsoft FAT file system family can deal with filenames in
11652 native language character sets. These character sets are stored in
11653 so-called DOS codepages. You need to include the appropriate
11654 codepage if you want to be able to read/write these filenames on
11655 DOS/Windows partitions correctly. This does apply to the filenames
11656 only, not to the file contents. You can include several codepages;
11657 say Y here if you want to include the DOS codepage for Portuguese.
11660 CONFIG_NLS_CODEPAGE_861
11661 The Microsoft FAT file system family can deal with filenames in
11662 native language character sets. These character sets are stored in
11663 so-called DOS codepages. You need to include the appropriate
11664 codepage if you want to be able to read/write these filenames on
11665 DOS/Windows partitions correctly. This does apply to the filenames
11666 only, not to the file contents. You can include several codepages;
11667 say Y here if you want to include the DOS codepage for Icelandic.
11670 CONFIG_NLS_CODEPAGE_862
11671 The Microsoft FAT file system family can deal with filenames in
11672 native language character sets. These character sets are stored in
11673 so-called DOS codepages. You need to include the appropriate
11674 codepage if you want to be able to read/write these filenames on
11675 DOS/Windows partitions correctly. This does apply to the filenames
11676 only, not to the file contents. You can include several codepages;
11677 say Y here if you want to include the DOS codepage for Hebrew.
11680 CONFIG_NLS_CODEPAGE_863
11681 The Microsoft FAT file system family can deal with filenames in
11682 native language character sets. These character sets are stored in
11683 so-called DOS codepages. You need to include the appropriate
11684 codepage if you want to be able to read/write these filenames on
11685 DOS/Windows partitions correctly. This does apply to the filenames
11686 only, not to the file contents. You can include several codepages;
11687 say Y here if you want to include the DOS codepage for Canadian
11691 CONFIG_NLS_CODEPAGE_864
11692 The Microsoft FAT file system family can deal with filenames in
11693 native language character sets. These character sets are stored in
11694 so-called DOS codepages. You need to include the appropriate
11695 codepage if you want to be able to read/write these filenames on
11696 DOS/Windows partitions correctly. This does apply to the filenames
11697 only, not to the file contents. You can include several codepages;
11698 say Y here if you want to include the DOS codepage for Arabic.
11701 CONFIG_NLS_CODEPAGE_865
11702 The Microsoft FAT file system family can deal with filenames in
11703 native language character sets. These character sets are stored in
11704 so-called DOS codepages. You need to include the appropriate
11705 codepage if you want to be able to read/write these filenames on
11706 DOS/Windows partitions correctly. This does apply to the filenames
11707 only, not to the file contents. You can include several codepages;
11708 say Y here if you want to include the DOS codepage for the Nordic
11709 European countries.
11712 CONFIG_NLS_CODEPAGE_866
11713 The Microsoft FAT file system family can deal with filenames in
11714 native language character sets. These character sets are stored in
11715 so-called DOS codepages. You need to include the appropriate
11716 codepage if you want to be able to read/write these filenames on
11717 DOS/Windows partitions correctly. This does apply to the filenames
11718 only, not to the file contents. You can include several codepages;
11719 say Y here if you want to include the DOS codepage for
11723 CONFIG_NLS_CODEPAGE_869
11724 The Microsoft FAT file system family can deal with filenames in
11725 native language character sets. These character sets are stored in
11726 so-called DOS codepages. You need to include the appropriate
11727 codepage if you want to be able to read/write these filenames on
11728 DOS/Windows partitions correctly. This does apply to the filenames
11729 only, not to the file contents. You can include several codepages;
11730 say Y here if you want to include the DOS codepage for Greek.
11733 CONFIG_NLS_CODEPAGE_874
11734 The Microsoft FAT file system family can deal with filenames in
11735 native language character sets. These character sets are stored in
11736 so-called DOS codepages. You need to include the appropriate
11737 codepage if you want to be able to read/write these filenames on
11738 DOS/Windows partitions correctly. This does apply to the filenames
11739 only, not to the file contents. You can include several codepages;
11740 say Y here if you want to include the DOS codepage for Thai.
11743 CONFIG_NLS_CODEPAGE_932
11744 The Microsoft fat filesystem family can deal with filenames in
11745 native language character sets. These character sets are stored in
11746 so-called DOS codepages. You need to include the appropriate
11747 codepage if you want to be able to read/write these filenames on
11748 DOS/Windows partitions correctly. This does apply to the filenames
11749 only, not to the file contents. You can include several codepages;
11750 say Y here if you want to include the DOS codepage for Shift-JIS
11751 or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
11752 NLS Default value during kernel configuration , instead of 'cp932'
11755 CONFIG_NLS_CODEPAGE_936
11756 The Microsoft fat filesystem family can deal with filenames in
11757 native language character sets. These character sets are stored in
11758 so-called DOS codepages. You need to include the appropriate
11759 codepage if you want to be able to read/write these filenames on
11760 DOS/Windows partitions correctly. This does apply to the filenames
11761 only, not to the file contents. You can include several codepages;
11762 say Y here if you want to include the DOS codepage for Simplified
11766 CONFIG_NLS_CODEPAGE_949
11767 The Microsoft fat filesystem family can deal with filenames in
11768 native language character sets. These character sets are stored in
11769 so-called DOS codepages. You need to include the appropriate
11770 codepage if you want to be able to read/write these filenames on
11771 DOS/Windows partitions correctly. This does apply to the filenames
11772 only, not to the file contents. You can include several codepages;
11773 say Y here if you want to include the DOS codepage for UHC.
11776 CONFIG_NLS_CODEPAGE_950
11777 The Microsoft fat filesystem family can deal with filenames in
11778 native language character sets. These character sets are stored in
11779 so-called DOS codepages. You need to include the appropriate
11780 codepage if you want to be able to read/write these filenames on
11781 DOS/Windows partitions correctly. This does apply to the filenames
11782 only, not to the file contents. You can include several codepages;
11783 say Y here if you want to include the DOS codepage for Traditional
11787 CONFIG_NLS_ISO8859_1
11788 If you want to display filenames with native language characters
11789 from the Microsoft FAT file system family or from JOLIET CDROMs
11790 correctly on the screen, you need to include the appropriate
11791 input/output character sets. Say Y here for the Latin 1 character
11792 set, which covers most West European languages such as Albanian,
11793 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
11794 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
11795 and Swedish. It is also the default for the US. If unsure, say Y.
11798 CONFIG_NLS_ISO8859_2
11799 If you want to display filenames with native language characters
11800 from the Microsoft FAT file system family or from JOLIET CDROMs
11801 correctly on the screen, you need to include the appropriate
11802 input/output character sets. Say Y here for the Latin 2 character
11803 set, which works for most Latin-written Slavic and Central European
11804 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
11808 CONFIG_NLS_ISO8859_3
11809 If you want to display filenames with native language characters
11810 from the Microsoft FAT file system family or from JOLIET CDROMs
11811 correctly on the screen, you need to include the appropriate
11812 input/output character sets. Say Y here for the Latin 3 character
11813 set, which is popular with authors of Esperanto, Galician, Maltese,
11817 CONFIG_NLS_ISO8859_4
11818 If you want to display filenames with native language characters
11819 from the Microsoft FAT file system family or from JOLIET CDROMs
11820 correctly on the screen, you need to include the appropriate
11821 input/output character sets. Say Y here for the Latin 4 character
11822 set which introduces letters for Estonian, Latvian, and
11823 Lithuanian. It is an incomplete predecessor of Latin 6.
11826 CONFIG_NLS_ISO8859_5
11827 If you want to display filenames with native language characters
11828 from the Microsoft FAT file system family or from JOLIET CDROMs
11829 correctly on the screen, you need to include the appropriate
11830 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
11831 character set with which you can type Bulgarian, Byelorussian,
11832 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
11833 KOI8-R is preferred in Russia.
11836 CONFIG_NLS_ISO8859_6
11837 If you want to display filenames with native language characters
11838 from the Microsoft FAT file system family or from JOLIET CDROMs
11839 correctly on the screen, you need to include the appropriate
11840 input/output character sets. Say Y here for ISO8859-6, the Arabic
11844 CONFIG_NLS_ISO8859_7
11845 If you want to display filenames with native language characters
11846 from the Microsoft FAT file system family or from JOLIET CDROMs
11847 correctly on the screen, you need to include the appropriate
11848 input/output character sets. Say Y here for ISO8859-7, the Modern
11849 Greek character set.
11852 CONFIG_NLS_ISO8859_8
11853 If you want to display filenames with native language characters
11854 from the Microsoft FAT file system family or from JOLIET CDROMs
11855 correctly on the screen, you need to include the appropriate
11856 input/output character sets. Say Y here for ISO8859-8, the Hebrew
11860 CONFIG_NLS_ISO8859_9
11861 If you want to display filenames with native language characters
11862 from the Microsoft FAT file system family or from JOLIET CDROMs
11863 correctly on the screen, you need to include the appropriate
11864 input/output character sets. Say Y here for the Latin 5 character
11865 set, and it replaces the rarely needed Icelandic letters in Latin 1
11866 with the Turkish ones. Useful in Turkey.
11869 CONFIG_NLS_ISO8859_10
11870 If you want to display filenames with native language characters
11871 from the Microsoft FAT file system family or from JOLIET CDROMs
11872 correctly on the screen, you need to include the appropriate
11873 input/output character sets. Say Y here for the Latin 6 character
11874 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
11875 letters that were missing in Latin 4 to cover the entire Nordic
11878 NLS ISO 8859-14 (Latin 8; Celtic)
11879 CONFIG_NLS_ISO8859_14
11880 If you want to display filenames with native language characters
11881 from the Microsoft FAT file system family or from JOLIET CDROMs
11882 correctly on the screen, you need to include the appropriate
11883 input/output character sets. Say Y here for the Latin 8 character
11884 set, which adds the last accented vowels for Welsh (aka Cymraeg)
11885 (and Manx Gaelic) hat were missing in Latin 1.
11886 http://linux.speech.cymru.org/ has further information.
11889 CONFIG_NLS_ISO8859_15
11890 If you want to display filenames with native language characters
11891 from the Microsoft FAT file system family or from JOLIET CDROMs
11892 correctly on the screen, you need to include the appropriate
11893 input/output character sets. Say Y here for the Latin 9 character
11894 set, which covers most West European languages such as Albanian,
11895 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
11896 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
11897 Portuguese, Spanish, and Swedish. Latin 9 is an update to
11898 Latin 1 (ISO 8859-1) that removes a handful of rarely used
11899 characters and instead adds support for Estonian, corrects the
11900 support for French and Finnish, and adds the new Euro character. If
11905 If you want to display filenames with native language characters
11906 from the Microsoft FAT file system family or from JOLIET CDROMs
11907 correctly on the screen, you need to include the appropriate
11908 input/output character sets. Say Y here for the preferred Russian
11913 If you say Y here, you will get support for terminal devices with
11914 display and keyboard devices. These are called "virtual" because you
11915 can run several virtual terminals (also called virtual consoles) on
11916 one physical terminal. This is rather useful, for example one
11917 virtual terminal can collect system messages and warnings, another
11918 one can be used for a text-mode user session, and a third could run
11919 an X session, all in parallel. Switching between virtual terminals
11920 is done with certain key combinations, usually Alt-<function key>.
11922 The setterm command ("man setterm") can be used to change the
11923 properties (such as colors or beeping) of a virtual terminal. The
11924 man page console_codes(4) ("man console_codes") contains the special
11925 character sequences that can be used to change those properties
11926 directly. The fonts used on virtual terminals can be changed with
11927 the setfont ("man setfont") command and the key bindings are defined
11928 with the loadkeys ("man loadkeys") command.
11930 You need at least one virtual terminal device in order to make use
11931 of your keyboard and monitor. Therefore, only people configuring an
11932 embedded system would want to say N here in order to save some
11933 memory; the only way to log into such a system is then via a serial
11934 or network connection.
11936 If unsure, say Y, or else you won't be able to do much with your new
11937 shiny Linux system :-)
11939 Support for console on virtual terminal
11941 The system console is the device which receives all kernel messages
11942 and warnings and which allows logins in single user mode. If you
11943 answer Y here, a virtual terminal (the device used to interact with
11944 a physical terminal) can be used as system console. This is the most
11945 common mode of operations, so you should say Y here unless you want
11946 the kernel messages be output only to a serial port (in which case
11947 you should say Y to "Console on serial port", below).
11949 If you do say Y here, by default the currently visible virtual
11950 terminal (/dev/tty0) will be used as system console. You can change
11951 that with a kernel command line option such as "console=tty3" which
11952 would use the third virtual terminal as system console. (Try "man
11953 bootparam" or see the documentation of your boot loader (lilo or
11954 loadlin) about how to pass options to the kernel at boot time.)
11958 Support for PowerMac keyboard
11959 CONFIG_MAC_KEYBOARD
11960 This option allows you to use an ADB keyboard attached to your
11961 machine. Note that this disables any other (ie. PS/2) keyboard
11962 support, even if your machine is physically capable of using both at
11965 If you use an ADB keyboard (4 pin connector), say Y here.
11966 If you use a PS/2 keyboard (6 pin connector), say N here.
11968 Standard/generic serial support
11970 This selects whether you want to include the driver for the standard
11971 serial ports. The standard answer is Y. People who might say N here
11972 are those that are setting up dedicated Ethernet WWW/FTP servers, or
11973 users that have one of the various bus mice instead of a serial
11974 mouse and don't intend to use their machine's standard serial port
11975 for anything. (Note that the Cyclades and Stallion multi serial port
11976 drivers do not need this driver built in for them to work.)
11978 If you want to compile this driver as a module, say M here and read
11979 Documentation/modules.txt. The module will be called serial.o.
11980 [WARNING: Do not compile this driver as a module if you are using
11981 non-standard serial ports, since the configuration information will
11982 be lost when the driver is unloaded. This limitation may be lifted
11985 BTW1: If you have a mouseman serial mouse which is not recognized by
11986 the X window system, try running gpm first.
11988 BTW2: If you intend to use a software modem (also called Winmodem)
11989 under Linux, forget it. These modems are crippled and require
11990 proprietary drivers which are only available under Windows.
11992 Most people will say Y or M here, so that they can use serial mice,
11993 modems and similar devices connecting to the standard serial ports.
11995 Support for console on serial port
11996 CONFIG_SERIAL_CONSOLE
11997 If you say Y here, it will be possible to use a serial port as the
11998 system console (the system console is the device which receives all
11999 kernel messages and warnings and which allows logins in single user
12000 mode). This could be useful if some terminal or printer is connected
12001 to that serial port.
12003 Even if you say Y here, the currently visible virtual console
12004 (/dev/tty0) will still be used as the system console by default, but
12005 you can alter that using a kernel command line option such as
12006 "console=ttyS1". (Try "man bootparam" or see the documentation of
12007 your boot loader (lilo or loadlin) about how to pass options to the
12008 kernel at boot time.)
12010 If you don't have a VGA card installed and you say Y here, the
12011 kernel will automatically use the first serial line, /dev/ttyS0, as
12016 Support for PowerMac serial ports
12018 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
12019 here. If you also have regular serial ports and enable the driver
12020 for them, you can't currently use the serial console feature.
12022 Comtrol Rocketport support
12024 This is a driver for the Comtrol Rocketport cards which provide
12025 multiple serial ports. You would need something like this to connect
12026 more than two modems to your Linux box, for instance in order to
12027 become a dial-in server.
12029 If you want to compile this driver as a module, say M here and read
12030 Documentation/modules.txt. The module will be called rocket.o.
12032 Digiboard Intelligent async support
12034 This is a driver for Digi International's Xx, Xeve, and Xem series
12035 of cards which provide multiple serial ports. You would need
12036 something like this to connect more than two modems to your Linux
12037 box, for instance in order to become a dial-in server. This driver
12038 supports the original PC (ISA) boards as well as PCI, and EISA. If
12039 you have a card like this, say Y here and read the file
12040 Documentation/digiepca.txt.
12042 NOTE: There is another, separate driver for the Digiboard PC boards:
12043 "Digiboard PC/Xx Support" below. You should (and can) only select
12044 one of the two drivers.
12046 If you want to compile this driver as a module, say M here and read
12047 Documentation/modules.txt. The module will be called epca.o.
12049 Digiboard PC/Xx Support
12051 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
12052 that give you many serial ports. You would need something like this
12053 to connect more than two modems to your Linux box, for instance in
12054 order to become a dial-in server. If you have a card like that, say
12055 Y here and read the file Documentation/digiboard.txt.
12057 If you want to compile this driver as a module, say M here and read
12058 Documentation/modules.txt. The module will be called pcxx.o.
12060 SDL RISCom/8 card support
12062 This is a driver for the SDL Communications RISCom/8 multiport card,
12063 which gives you many serial ports. You would need something like
12064 this to connect more than two modems to your Linux box, for instance
12065 in order to become a dial-in server. If you have a card like that,
12066 say Y here and read the file Documentation/riscom8.txt.
12068 Also it's possible to say M here and compile this driver as kernel
12069 loadable module; the module will be called riscom8.o.
12071 Computone IntelliPort Plus serial support
12073 This driver supports the entire family of Intelliport II/Plus
12074 controllers with the exception of the MicroChannel controllers and
12075 products previous to the Intelliport II. These are multiport cards,
12076 which give you many serial ports. You would need something like
12077 this to connect more than two modems to your Linux box, for
12078 instance in order to become a dial-in server. If you have a
12079 card like that, say Y here and read Documentation/computone.txt.
12081 If you want to compile this as a module ( = code which can be
12082 inserted in and removed from the running kernel whenever you want),
12083 say M here and read Documentation/modules.txt. You will get two
12084 modules called ip2.o and ip2main.o.
12086 Specialix IO8+ card support
12088 This is a driver for the Specialix IO8+ multiport card (both the
12089 ISA and the PCI version) which gives you many serial ports. You
12090 would need something like this to connect more than two modems to
12091 your Linux box, for instance in order to become a dial-in server.
12093 If you have a card like that, say Y here and read the file
12094 Documentation/specialix.txt. Also it's possible to say M here and
12095 compile this driver as kernel loadable module which will be called
12098 Specialix DTR/RTS pin is RTS
12099 CONFIG_SPECIALIX_RTSCTS
12100 The Specialix card can only support either RTS or DTR. If you say N
12101 here, the driver will use the pin as "DTR" when the tty is in
12102 software handshake mode. If you say Y here or hardware handshake is
12103 on, it will always be RTS. Read the file Documentation/specialix.txt
12104 for more information.
12106 Cyclades async mux support
12108 This is a driver for a card that gives you many serial ports. You
12109 would need something like this to connect more than two modems to
12110 your Linux box, for instance in order to become a dial-in server.
12111 For information about the Cyclades-Z card, read
12112 drivers/char/README.cycladesZ.
12114 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
12117 If you want to compile this as a module ( = code which can be
12118 inserted in and removed from the running kernel whenever you want),
12119 say M here and read Documentation/modules.txt. The module will be
12122 If you haven't heard about it, it's safe to say N.
12124 Cyclades-Z interrupt mode operation (EXPERIMENTAL)
12126 The Cyclades-Z family of multiport cards allows 2 (two) driver op
12127 modes: polling and interrupt. In polling mode, the driver will check
12128 the status of the Cyclades-Z ports every certain amount of time
12129 (which is called polling cycle and is configurable). In interrupt
12130 mode, it will use an interrupt line (IRQ) in order to check the
12131 status of the Cyclades-Z ports. The default op mode is polling. If
12134 Stallion multiport serial support
12136 Stallion cards give you many serial ports. You would need something
12137 like this to connect more than two modems to your Linux box, for
12138 instance in order to become a dial-in server. If you say Y here, you
12139 will be asked for your specific card model in the next questions.
12140 Make sure to read drivers/char/README.stallion in this case. If you
12141 have never heard about all this, it's safe to say N.
12143 Stallion EasyIO or EC8/32 support
12145 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
12146 card, then this is for you; say Y. Make sure to read
12147 Documentation/stallion.txt.
12149 If you want to compile this as a module ( = code which can be
12150 inserted in and removed from the running kernel whenever you want),
12151 say M here and read Documentation/modules.txt. The module will be
12154 Stallion EC8/64, ONboard, Brumby support
12156 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
12157 serial multiport card, say Y here. Make sure to read
12158 Documentation/stallion.txt.
12160 To compile it as a module ( = code which can be inserted in and
12161 removed from the running kernel whenever you want), say M here and
12162 read Documentation/modules.txt. The module will be called
12165 Microgate SyncLink adapter support
12167 Provides support for the SyncLink ISA and PCI
12168 multiprotocol serial adapters. These adapters
12169 support asynchronous and HDLC bit synchronous
12170 communication up to 10Mbps (PCI adapter).
12172 This driver can only be built as a module ( = code which can be
12173 inserted in and removed from the running kernel whenever you want).
12174 The module will be called synclink.o. If you want to do that, say M
12177 Synchronous HDLC line discipline support
12179 Allows synchronous HDLC communications with tty device drivers that
12180 support synchronous HDLC such as the Microgate SyncLink adapter.
12182 This driver can only be built as a module ( = code which can be
12183 inserted in and removed from the running kernel whenever you want).
12184 The module will be called n_hdlc.o. If you want to do that, say M
12187 Specialix SX (and SI) card support
12189 This is a driver for the SX and SI multiport serial cards.
12190 Please read the file Documentation/sx.txt for details.
12192 This driver can only be built as a module ( = code which can be
12193 inserted in and removed from the running kernel whenever you want).
12194 The module will be called sx.o. If you want to do that, say M here.
12196 Hayes ESP serial port support
12198 This is a driver which supports Hayes ESP serial ports. Both single
12199 port cards and multiport cards are supported. Make sure to read
12200 Documentation/hayes-esp.txt.
12202 To compile this driver as a module ( = code which can be inserted in
12203 and removed from the running kernel whenever you want), say M here
12204 and read Documentation/modules.txt. The module will be called esp.o.
12207 Moxa Intellio support
12208 CONFIG_MOXA_INTELLIO
12209 Say Y here if you have a Moxa Intellio multiport serial card.
12211 This driver can also be built as a module ( = code which can be
12212 inserted in and removed from the running kernel whenever you want).
12213 The module will be called moxa.o. If you want to do that, say M
12216 Moxa SmartIO support
12217 CONFIG_MOXA_SMARTIO
12218 Say Y here if you have a Moxa SmartIO multiport serial card.
12220 This driver can also be built as a module ( = code which can be
12221 inserted in and removed from the running kernel whenever you want).
12222 The module will be called mxser.o. If you want to do that, say M
12225 Multi-Tech multiport card support (EXPERIMENTAL)
12227 This is a driver for the Multi-Tech cards which provide several
12228 serial ports. The driver is experimental and can currently only be
12229 built as a module ( = code which can be inserted in and removed from
12230 the running kernel whenever you want). Please read
12231 Documentation/modules.txt. The module will be called isicom.o
12235 A pseudo terminal (PTY) is a software device consisting of two
12236 halves: a master and a slave. The slave device behaves identical to
12237 a physical terminal; the master device is used by a process to
12238 read data from and write data to the slave, thereby emulating a
12239 terminal. Typical programs for the master side are telnet servers
12242 Linux has traditionally used the BSD-like names /dev/ptyxx for
12243 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
12244 has a number of problems. The GNU C library glibc 2.1 and later,
12245 however, supports the Unix98 naming standard: in order to acquire a
12246 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
12247 terminal is then made available to the process and the pseudo
12248 terminal slave can be accessed as /dev/pts/<number>. What was
12249 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
12251 The entries in /dev/pts/ are created on the fly by a virtual
12252 file system; therefore, if you say Y here you should say Y to
12253 "/dev/pts file system for Unix98 PTYs" as well.
12255 If you want to say Y here, you need to have the C library glibc 2.1
12256 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
12257 Read the instructions in Documentation/Changes pertaining to pseudo
12258 terminals. It's safe to say N.
12260 Maximum number of Unix98 PTYs in use (0-2048)
12261 CONFIG_UNIX98_PTY_COUNT
12262 The maximum number of Unix98 PTYs that can be used at any one time.
12263 The default is 256, and should be enough for desktop systems. Server
12264 machines which support incoming telnet/rlogin/ssh connections and/or
12265 serve several X terminals may want to increase this: every incoming
12266 connection and every xterm uses up one PTY.
12268 When not in use, each additional set of 256 PTYs occupy
12269 approximately 8 KB of kernel memory on 32-bit architectures.
12271 Parallel printer support
12273 If you intend to attach a printer to the parallel port of your Linux
12274 box (as opposed to using a serial printer; if the connector at the
12275 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
12276 read the Printing-HOWTO, available from
12277 http://www.linuxdoc.org/docs.html#howto .
12279 It is possible to share one parallel port among several devices
12280 (e.g. printer and ZIP drive) and it is safe to compile the
12281 corresponding drivers into the kernel. If you want to compile this
12282 driver as a module however ( = code which can be inserted in and
12283 removed from the running kernel whenever you want), say M here and
12284 read Documentation/modules.txt and Documentation/parport.txt. The
12285 module will be called lp.o.
12287 If you have several parallel ports, you can specify which ports to
12288 use with the "lp" kernel command line option. (Try "man bootparam"
12289 or see the documentation of your boot loader (lilo or loadlin) about
12290 how to pass options to the kernel at boot time.) The syntax of the
12291 "lp" command line option can be found in drivers/char/lp.c.
12293 If you have more than 3 printers, you need to increase the LP_NO
12296 Support for console on line printer
12298 If you want kernel messages to be printed out as they occur, you
12299 can have a console on the printer. This option adds support for
12300 doing that; to actually get it to happen you need to pass the
12301 option "console=lp0" to the kernel at boot time.
12303 Note that kernel messages can get lost if the printer is out of
12304 paper (or off, or unplugged, or too busy..), but this behaviour
12305 can be changed. See drivers/char/lp.c (do this at your own risk).
12309 Support for user-space parallel port device drivers
12311 Saying Y to this adds support for /dev/parport device nodes. This
12312 is needed for programs that want portable access to the parallel
12313 port, for instance deviceid (which displays Plug-and-Play device
12316 This is the parallel port equivalent of SCSI generic support (sg).
12317 It is safe to say N to this -- it is not needed for normal printing
12318 or parallel port CD-ROM/disk support.
12320 This support is also available as a module. If you want to compile
12321 it as a module, say M here and read Documentation/modules.txt. The
12322 module will be called ppdev.o.
12328 I2C (pronounce: I-square-C) is a slow serial bus protocol used in
12329 many micro controller applications and developed by Philips. SMBus,
12330 or System Management Bus is a subset of the I2C protocol. More
12331 information is contained in the directory Documentation/i2c/,
12332 especially in the file called "summary" there.
12334 Both I2C and SMBus are supported here. You will need this for
12335 hardware sensors support, and also for Video for Linux support.
12336 Specifically, if you want to use a BT848 based frame grabber/overlay
12337 boards under Linux, say Y here and also to "I2C bit-banging
12338 interfaces", below.
12340 If you want I2C support, you should say Y here and also to the
12341 specific driver for your bus adapter(s) below. If you say Y to
12342 "/proc file system" below, you will then get a /proc interface which
12343 is documented in Documentation/i2c/proc-interface.
12345 This I2C support is also available as a module. If you want to
12346 compile it as a module, say M here and read
12347 Documentation/modules.txt. The module will be called i2c-core.o.
12349 I2C bit-banging interfaces
12351 This allows you to use a range of I2C adapters called bit-banging
12352 adapters. Say Y if you own an I2C adapter belonging to this class
12353 and then say Y to the specific driver for you adapter below.
12355 This support is also available as a module. If you want to compile
12356 it as a module, say M here and read Documentation/modules.txt. The
12357 module will be called i2c-algo-bit.o.
12359 Philips style parallel port adapter
12360 CONFIG_I2C_PHILIPSPAR
12361 This supports parallel-port I2C adapters made by Philips. Say Y if
12362 you own such an adapter.
12364 This driver is also available as a module. If you want to compile
12365 it as a module, say M here and read Documentation/modules.txt. The
12366 module will be called i2c-philips-par.o.
12368 Note that if you want support for different parallel port devices,
12369 life will be much easier if you compile them all as modules.
12373 This supports parallel-port I2C adapters called ELV. Say Y if you
12374 own such an adapter.
12376 This driver is also available as a module. If you want to compile
12377 it as a module, say M here and read Documentation/modules.txt. The
12378 module will be called i2c-elv.o.
12380 Velleman K9000 adapter
12381 CONFIG_I2C_VELLEMAN
12382 This supports the Velleman K9000 parallel-port I2C adapter. Say Y if
12383 you own such an adapter.
12385 This driver is also available as a module. If you want to compile
12386 it as a module, say M here and read Documentation/modules.txt. The
12387 module will be called i2c-velleman.o.
12389 I2C PCF 8584 interfaces
12391 This allows you to use a range of I2C adapters called PCF adapters.
12392 Say Y if you own an I2C adapter belonging to this class and then say
12393 Y to the specific driver for you adapter below.
12395 This support is also available as a module. If you want to compile
12396 it as a module, say M here and read Documentation/modules.txt. The
12397 module will be called i2c-algo-pcf.o.
12401 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own such
12404 This driver is also available as a module. If you want to compile
12405 it as a module, say M here and read Documentation/modules.txt. The
12406 module will be called i2c-elektor.o.
12408 I2C device interface
12410 Say Y here to use i2c-* device files, usually found in the /dev
12411 directory on your system. They make it possible to have user-space
12412 programs use the I2C bus. Information on how to do this is contained
12413 in the file Documentation/i2c/dev-interface.
12415 This code is also available as a module. If you want to compile
12416 it as a module, say M here and read Documentation/modules.txt. The
12417 module will be called i2c-dev.o.
12421 Say Y here if your machine has a bus mouse as opposed to a serial
12422 mouse. Most people have a regular serial MouseSystem or
12423 Microsoft mouse (made by Logitech) that plugs into a COM port
12424 (rectangular with 9 or 25 pins). These people say N here. If you
12425 have something else, read the Busmouse-HOWTO, available from
12426 http://www.linuxdoc.org/docs.html#howto , and say Y here.
12428 If you have a laptop, you either have to check the documentation or
12429 experiment a bit to find out whether the trackball is a serial mouse
12430 or not; it's best to say Y here for you.
12432 This is the generic bus mouse driver code. If you have a bus mouse,
12433 you will have to say Y here and also to the specific driver for your
12436 This code is also available as a module ( = code which can be
12437 inserted in and removed from the running kernel whenever you want).
12438 The module will be called busmouse.o. If you want to compile it as a
12439 module, say M here and read Documentation/modules.txt.
12441 Mouse Support (not serial and bus mice)
12443 This is for machines with a mouse which is neither a serial nor a
12444 bus mouse. Examples are PS/2 mice (such as the track balls on some
12445 laptops) and some digitizer pads. Most people have a regular serial
12446 MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
12447 COM port (rectangular with 9 or 25 pins). These people say N here.
12448 If you have something else, read the Busmouse-HOWTO, available from
12449 http://www.linuxdoc.org/docs.html#howto . This HOWTO contains
12450 information about all non-serial mice, not just bus mice.
12452 If you have a laptop, you either have to check the documentation or
12453 experiment a bit to find out whether the trackball is a serial mouse
12454 or not; it's best to say Y here for you.
12456 Note that the answer to this question won't directly affect the
12457 kernel: saying N will just cause this configure script to skip all
12458 the questions about non-serial mice. If unsure, say Y.
12460 Logitech busmouse support
12461 CONFIG_LOGIBUSMOUSE
12462 Logitech mouse connected to a proprietary interface card. It's
12463 generally a round connector with 9 pins. Note that the newer mice
12464 made by Logitech don't use the Logitech protocol anymore; for those,
12465 you don't need this option. You want to read the Busmouse-HOWTO ,
12466 available from http://www.linuxdoc.org/docs.html#howto .
12468 If you want to compile this as a module ( = code which can be
12469 inserted in and removed from the running kernel whenever you want),
12470 say M here and read Documentation/modules.txt. The module will be
12471 called busmouse.o. If you are unsure, say N and read the HOWTO
12472 nevertheless: it will tell you what you have.
12474 PS/2 mouse (aka "auxiliary device") support
12476 The PS/2 mouse connects to a special mouse port that looks much like
12477 the keyboard port (small circular connector with 6 pins). This way,
12478 the mouse does not use any serial ports. This port can also be used
12479 for other input devices like light pens, tablets, keypads. Compaq,
12480 AST and IBM all use this as their mouse port on currently shipping
12481 machines. The trackballs of some laptops are PS/2 mice also. In
12482 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
12484 Although PS/2 mice are not technically bus mice, they are explained
12485 in detail in the Busmouse-HOWTO, available from
12486 http://www.linuxdoc.org/docs.html#howto .
12488 When using a PS/2 mouse, you can get problems if you want to use the
12489 mouse both on the Linux console and under X. Using the "-R" option
12490 of the Linux mouse managing program gpm (available from
12491 ftp://metalab.unc.edu/pub/Linux/system/mouse ) solves this
12492 problem, or you can get the "mconv2" utility from the same location.
12494 C&T 82C710 mouse port support (as on TI Travelmate)
12495 CONFIG_82C710_MOUSE
12496 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
12497 you are unsure, try first to say N here and come back if the mouse
12498 doesn't work. Read the Busmouse-HOWTO, available from
12499 http://www.linuxdoc.org/docs.html#howto .
12501 PC110 digitizer pad support
12503 This drives the digitizer pad on the IBM PC110 palmtop. It can turn
12504 the digitizer pad into a PS/2 mouse emulation with tap gestures or
12505 into an absolute pad.
12507 If you want to compile this as a module ( = code which can be
12508 inserted in and removed from the running kernel whenever you want),
12509 say M here and read Documentation/modules.txt. The module will be
12512 Microsoft busmouse support
12514 These animals (also called Inport mice) are connected to an
12515 expansion board using a round connector with 9 pins. If this is what
12516 you have, say Y and read the Busmouse-HOWTO, available from
12517 http://www.linuxdoc.org/docs.html#howto .
12519 If you are unsure, say N and read the HOWTO nevertheless: it will
12520 tell you what you have. Also be aware that several vendors talk
12521 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
12522 count the pins on the connector.
12524 If you want to compile this as a module ( = code which can be
12525 inserted in and removed from the running kernel whenever you want),
12526 say M here and read Documentation/modules.txt. The module will be
12527 called msbusmouse.o.
12529 Apple Desktop Bus mouse support
12531 Say Y here if you have this type of bus mouse (4 pin connector) as
12532 is common on Macintoshes. You may want to read the Busmouse-HOWTO,
12533 available from http://www.linuxdoc.org/docs.html#howto .
12535 If you want to compile this as a module ( = code which can be
12536 inserted in and removed from the running kernel whenever you want),
12537 say M here and read Documentation/modules.txt. The module will be
12540 ATIXL busmouse support
12541 CONFIG_ATIXL_BUSMOUSE
12542 This is a rare type of busmouse that is connected to the back of an
12543 ATI video card. Say Y if you have one of those. Note however that
12544 most mice by ATI are actually Microsoft busmice; you should say Y to
12545 "Microsoft busmouse support" above if you have one of those. Read
12546 the Busmouse-HOWTO, available from
12547 http://www.linuxdoc.org/docs.html#howto .
12549 If you want to compile this as a module ( = code which can be
12550 inserted in and removed from the running kernel whenever you want),
12551 say M here and read Documentation/modules.txt. The module will be
12552 called atixlmouse.o.
12554 If you are unsure, say N and read the HOWTO nevertheless: it will
12555 tell you what you have.
12557 QIC-02 tape support
12559 If you have a non-SCSI tape drive like that, say Y. Or, if you want
12560 to compile this driver as a module ( = code which can be inserted in
12561 and removed from the running kernel whenever you want), say M here
12562 and read Documentation/modules.txt. The module will be called
12565 Do you want runtime configuration for QIC-02
12566 CONFIG_QIC02_DYNCONF
12567 You can either configure this driver once and for all by editing a
12568 header file (include/linux/tpqic02.h), in which case you should
12569 say N, or you can fetch a program via anonymous FTP which is able
12570 to configure this driver during runtime. The program to do this is
12571 called 'qic02conf' and it is part of the tpqic02-support-X.Y.tar.gz
12574 If you want to use the qic02conf program, say Y.
12576 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
12578 If you have a tape drive that is connected to your floppy
12579 controller, say Y here.
12581 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
12582 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
12583 controller of their own. These drives (and their companion
12584 controllers) are also supported if you say Y here.
12586 If you have a special controller (such as the CMS FC-10, FC-20,
12587 Mountain Mach-II, or any controller that is based on the Intel 82078
12588 FDC like the high speed controllers by Seagate and Exabyte and
12589 Iomega's "Ditto Dash") you must configure it by selecting the
12590 appropriate entries from the "Floppy tape controllers" sub-menu
12591 below and possibly modify the default values for the IRQ and DMA
12592 channel and the IO base in ftape's configuration menu.
12594 If you want to use your floppy tape drive on a PCI-bus based system,
12595 please read the file drivers/char/ftape/README.PCI.
12597 The ftape kernel driver is also available as a runtime loadable
12598 module ( = code which can be inserted in and removed from the
12599 running kernel whenever you want). If you want to compile it as a
12600 module, say M here and read Documentation/modules.txt. The module
12601 will be called ftape.o.
12603 Note that the Ftape-HOWTO is out of date (sorry) and documents the
12604 older version 2.08 of this software but still contains useful
12605 information. There is a web page with more recent documentation at
12606 http://www.math1.rwth-aachen.de/~heine/ftape/ . This page
12607 always contains the latest release of the ftape driver and useful
12608 information (backup software, ftape related patches and
12609 documentation, FAQ). Note that the file system interface has changed
12610 quite a bit compared to previous versions of ftape. Please read
12611 Documentation/ftape.txt.
12613 The file system interface for ftape
12615 Normally, you want to say Y or M. DON'T say N here or you
12616 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
12618 The ftape module itself no longer contains the routines necessary
12619 to interface with the kernel VFS layer (i.e. to actually write data
12620 to and read data from the tape drive). Instead the file system
12621 interface (i.e. the hardware independent part of the driver) has
12622 been moved to a separate module.
12624 If you say M zftape will be compiled as a runtime loadable
12625 module ( = code which can be inserted in and removed from the
12626 running kernel whenever you want). In this case you should read
12627 Documentation/modules.txt. The module will be called zftape.o.
12629 Regardless of whether you say Y or M here, an additional runtime
12630 loadable module called `zft-compressor.o' which contains code to
12631 support user transparent on-the-fly compression based on Ross
12632 William's lzrw3 algorithm will be produced. If you have enabled the
12633 kernel module loader (i.e. have said Y to "Kernel module loader
12634 support", above) then `zft-compressor.o' will be loaded
12635 automatically by zftape when needed.
12637 Despite its name, zftape does NOT use compression by default. The
12638 file Documentation/ftape.txt contains a short description of the
12639 most important changes in the file system interface compared to
12640 previous versions of ftape. The ftape home page
12641 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
12642 further information.
12644 IMPORTANT NOTE: zftape can read archives created by previous
12645 versions of ftape and provide file mark support (i.e. fast skipping
12646 between tape archives) but previous version of ftape will lack file
12647 mark support when reading archives produced by zftape.
12649 Default block size for zftape
12650 CONFIG_ZFT_DFLT_BLK_SZ
12651 If unsure leave this at its default value, i.e. 10240. Note that
12652 you specify only the default block size here. The block size can be
12653 changed at run time using the MTSETBLK tape operation with the
12654 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
12655 shell command line).
12657 The probably most striking difference between zftape and previous
12658 versions of ftape is the fact that all data must be written or read
12659 in multiples of a fixed block size. The block size defaults to
12660 10240 which is what GNU tar uses. The values for the block size
12661 should be either 1 or multiples of 1024 up to a maximum value of
12662 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
12663 compression will be disabled.
12665 Reasonable values are `10240' (GNU tar's default block size),
12666 `5120' (afio's default block size), `32768' (default block size some
12667 backup programs assume for SCSI tape drives) or `1' (no restriction
12668 on block size, but disables builtin compression).
12670 Number of DMA buffers
12671 CONFIG_FT_NR_BUFFERS
12672 Please leave this at `3' unless you REALLY know what you are doing.
12673 It is not necessary to change this value. Values below 3 make the
12674 proper use of ftape impossible, values greater than 3 are a waste of
12675 memory. You can change the amount of DMA memory used by ftape at
12676 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
12677 wastes 32 KB of memory. Please note that this memory cannot be
12680 Procfs entry for ftape
12682 Optional. Saying Y will result in creation of a directory
12683 `/proc/ftape' under the /proc file system. The files can be viewed
12684 with your favorite pager (i.e. use "more /proc/ftape/history" or
12685 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
12686 file will contain some status information about the inserted
12687 cartridge, the kernel driver, your tape drive, the floppy disk
12688 controller and the error history for the most recent use of the
12689 kernel driver. Saying Y will enlarge the size of the ftape driver
12690 by approximately 2 KB.
12692 WARNING: When compiling ftape as a module (i.e. saying M to "Floppy
12693 tape drive") it is dangerous to use ftape's /proc file system
12694 interface. Accessing `/proc/ftape' while the module is unloaded will
12695 result in a kernel Oops. This cannot be fixed from inside ftape.
12697 Controlling the amount of debugging output of ftape
12698 CONFIG_FT_NORMAL_DEBUG
12699 This option controls the amount of debugging output the ftape driver
12700 is ABLE to produce; it does not increase or diminish the debugging
12701 level itself. If unsure, leave this at its default setting,
12702 i.e. choose "Normal".
12704 Ftape can print lots of debugging messages to the system console
12705 resp. kernel log files. Reducing the amount of possible debugging
12706 output reduces the size of the kernel module by some KB, so it might
12707 be a good idea to use "None" for emergency boot floppies.
12709 If you want to save memory then the following strategy is
12710 recommended: leave this option at its default setting "Normal" until
12711 you know that the driver works as expected, afterwards reconfigure
12712 the kernel, this time specifying "Reduced" or "None" and recompile
12713 and install the kernel as usual. Note that choosing "Excessive"
12714 debugging output does not increase the amount of debugging output
12715 printed to the console but only makes it possible to produce
12716 "Excessive" debugging output.
12718 Please read Documentation/ftape.txt for a short description
12719 how to control the amount of debugging output.
12721 The floppy drive controller for ftape
12723 Only change this setting if you have a special controller. If you
12724 didn't plug any add-on card into your computer system but just
12725 plugged the floppy tape cable into the already existing floppy drive
12726 controller then you don't want to change the default setting,
12727 i.e. choose "Standard".
12729 Choose "MACH-2" if you have a Mountain Mach-2 controller.
12730 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
12732 Choose "Alt/82078" if you have another controller that is located at
12733 an IO base address different from the standard floppy drive
12734 controller's base address of `0x3f0', or uses an IRQ (interrupt)
12735 channel different from `6', or a DMA channel different from
12736 `2'. This is necessary for any controller card that is based on
12737 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
12738 speed" controllers.
12740 If you choose something other than "Standard" then please make
12741 sure that the settings for the IO base address and the IRQ and DMA
12742 channel in the configuration menus below are correct. Use the manual
12743 of your tape drive to determine the correct settings!
12745 If you are already successfully using your tape drive with another
12746 operating system then you definitely should use the same settings
12747 for the IO base, the IRQ and DMA channel that have proven to work
12748 with that other OS.
12750 Note that this menu lets you specify only the default setting for
12751 the hardware setup. The hardware configuration can be changed at
12752 boot time (when ftape is compiled into the kernel, i.e. if you
12753 have said Y to "Floppy tape drive") or module load time (i.e. if you
12754 have said M to "Floppy tape drive").
12756 Please read also the file Documentation/ftape.txt which
12757 contains a short description of the parameters that can be set at
12758 boot or load time. If you want to use your floppy tape drive on a
12759 PCI-bus based system, please read the file
12760 drivers/char/ftape/README.PCI.
12762 IO base of the floppy disk controller used with Ftape
12764 You don't need to specify a value if the following default
12765 settings for the base IO address are correct:
12766 <<< MACH-2 : 0x1E0 >>>
12767 <<< FC-10/FC-20: 0x180 >>>
12768 <<< Secondary : 0x370 >>>
12769 Secondary refers to a secondary FDC controller like the "high speed"
12770 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12771 Please make sure that the setting for the IO base address
12772 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12773 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12774 successfully using the tape drive with another operating system then
12775 you definitely should use the same settings for the IO base that has
12776 proven to work with that other OS.
12778 Note that this menu lets you specify only the default setting for
12779 the IO base. The hardware configuration can be changed at boot time
12780 (when ftape is compiled into the kernel, i.e. if you specified Y to
12781 "Floppy tape drive") or module load time (i.e. if you have said M to
12782 "Floppy tape drive").
12784 Please read also the file Documentation/ftape.txt which contains a
12785 short description of the parameters that can be set at boot or load
12788 IRQ channel for the floppy disk controller used with Ftape
12790 You don't need to specify a value if the following default
12791 settings for the interrupt channel are correct:
12793 <<< FC-10/FC-20: 9 >>>
12794 <<< Secondary : 6 >>>
12795 Secondary refers to secondary a FDC controller like the "high speed"
12796 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12797 Please make sure that the setting for the IO base address
12798 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12799 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12800 successfully using the tape drive with another operating system then
12801 you definitely should use the same settings for the IO base that has
12802 proven to work with that other OS.
12804 Note that this menu lets you specify only the default setting for
12805 the IRQ channel. The hardware configuration can be changed at boot
12806 time (when ftape is compiled into the kernel, i.e. if you said Y to
12807 "Floppy tape drive") or module load time (i.e. if you said M to
12808 "Floppy tape drive").
12810 Please read also the file Documentation/ftape.txt which contains a
12811 short description of the parameters that can be set at boot or load
12814 DMA channel for the floppy disk controller used with Ftape
12816 You don't need to specify a value if the following default
12817 settings for the DMA channel are correct:
12819 <<< FC-10/FC-20: 3 >>>
12820 <<< Secondary : 2 >>>
12821 Secondary refers to a secondary FDC controller like the "high speed"
12822 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
12823 Please make sure that the setting for the IO base address
12824 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
12825 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
12826 successfully using the tape drive with another operating system then
12827 you definitely should use the same settings for the IO base that has
12828 proven to work with that other OS.
12830 Note that this menu lets you specify only the default setting for
12831 the DMA channel. The hardware configuration can be changed at boot
12832 time (when ftape is compiled into the kernel, i.e. if you said Y to
12833 "Floppy tape drive") or module load time (i.e. if you said M to
12834 "Floppy tape drive").
12836 Please read also the file Documentation/ftape.txt which contains a
12837 short description of the parameters that can be set at boot or load
12840 FDC FIFO Threshold before requesting DMA service
12842 Set the FIFO threshold of the FDC. If this is higher the DMA
12843 controller may serve the FDC after a higher latency time. If this is
12844 lower, fewer DMA transfers occur leading to less bus contention.
12845 You may try to tune this if ftape annoys you with "reduced data
12846 rate because of excessive overrun errors" messages. However, this
12847 doesn't seem to have too much effect.
12849 If unsure, don't touch the initial value, i.e. leave it at "8".
12851 FDC maximum data rate
12852 CONFIG_FT_FDC_MAX_RATE
12853 With some motherboard/FDC combinations ftape will not be able to
12854 run your FDC/tape drive combination at the highest available
12855 speed. If this is the case you'll encounter "reduced data rate
12856 because of excessive overrun errors" messages and lots of retries
12857 before ftape finally decides to reduce the data rate.
12859 In this case it might be desirable to tell ftape beforehand that
12860 it need not try to run the tape drive at the highest available
12861 speed. If unsure, leave this disabled, i.e. leave it at 2000
12864 Direct Rendering Manager (XFree86 DRI support)
12866 Kernel-level support for the Direct Rendering Infrastructure (DRI)
12867 introduced in XFree86 4.0. If you say Y here, you need to select
12868 the module that's right for your graphics card from the list below.
12869 These modules provide support for synchronization, security, and
12870 DMA transfers. Please see http://dri.sourceforge.net for more
12871 details. You should also select and configure AGP
12872 (/dev/agpgart) support.
12874 3dfx Banshee/Voodoo3+
12876 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
12877 graphics card. If M is selected, the module will be called tdfx.o.
12881 Choose this option if you have a 3dlabs GMX 2000 graphics card.
12882 If M is selected, the module will be called gamma.o.
12886 Choose this option if you have an ATI Rage 128 graphics card. If M
12887 is selected, the module will be called r128.o. AGP support for
12888 this card is strongly suggested (unless you have a PCI version).
12892 Choose this option if you have an Intel I810 graphics card. If M is
12893 selected, the module will be called i810.o. AGP support is required
12894 for this driver to work.
12898 Choose this option if you have a Matrox g200 or g400 graphics card. If M
12899 is selected, the module will be called mga.o. AGP support is required
12900 for this driver to work.
12902 MTRR control and configuration
12904 On Intel P6 family processors (Pentium Pro, Pentium II and later)
12905 the Memory Type Range Registers (MTRRs) may be used to control
12906 processor access to memory ranges. This is most useful if you have
12907 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
12908 allows bus write transfers to be combined into a larger transfer
12909 before bursting over the PCI/AGP bus. This can increase performance
12910 of image write operations 2.5 times or more. Saying Y here creates a
12911 /proc/mtrr file which may be used to manipulate your processor's
12912 MTRRs. Typically the X server should use this.
12914 This code has a reasonably generic interface so that similar
12915 control registers on other processors can be easily supported
12918 The Cyrix 6x86, 6x86MX and M II processors have Address Range
12919 Registers (ARRs) which provide a similar functionality to MTRRs. For
12920 these, the ARRs are used to emulate the MTRRs.
12921 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
12922 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
12923 write-combining. All of these processors are supported by this code
12924 and it makes sense to say Y here if you have one of them.
12926 Saying Y here also fixes a problem with buggy SMP BIOSes which only
12927 set the MTRRs for the boot CPU and not for the secondary CPUs. This
12928 can lead to all sorts of problems, so it's good to say Y here.
12930 You can safely say Y even if your machine doesn't have MTRRs, you'll
12931 just add about 9 KB to your kernel.
12933 See Documentation/mtrr.txt for more information.
12935 Main CPU frequency, only for DEC alpha machine
12936 CONFIG_FT_ALPHA_CLOCK
12937 On some DEC Alpha machines the CPU clock frequency cannot be
12938 determined automatically, so you need to specify it here ONLY if
12939 running a DEC Alpha, otherwise this setting has no effect.
12941 Double Talk PC internal speech card support
12943 This driver is for the DoubleTalk PC, a speech synthesizer
12944 manufactured by RC Systems (http://www.rcsys.com/ ). It is also
12945 called the `internal DoubleTalk'. If you want to compile this as a
12946 module ( = code which can be inserted in and removed from the
12947 running kernel whenever you want), say M here and read
12948 Documentation/modules.txt. The module will be called dtlk.o.
12950 Siemens R3964 serial protocol support
12952 This driver allows synchronous communication with devices using the
12953 Siemens R3964 packet protocol. Unless you are dealing with special
12954 hardware like PLCs, you are unlikely to need this.
12956 To compile this driver as a module ( = code which can be inserted in
12957 and removed from the running kernel whenever you want), say M here
12958 and read Documentation/modules.txt. The module will be called
12963 Applicom intelligent fieldbus card support
12965 This driver provides the kernel-side support for the intelligent
12966 fieldbus cards made by Applicom International. More information
12967 about these cards can be found on the WWW at the address
12968 http://www.applicom-int.com/ , or by email from David Woodhouse
12969 <dwmw2@infradead.org>.
12971 To compile this driver as a module ( = code which can be inserted in
12972 and removed from the running kernel whenever you want), say M here
12973 and read Documentation/modules.txt. The module will be called
12978 Intel Random Number Generator support
12980 This driver provides kernel-side support for the Random Number
12981 Generator hardware found on Intel i8xx-based motherboards.
12983 Both a character driver, used to read() entropy data, and a timer
12984 function which automatically adds entropy directly into the
12985 kernel pool, are exported by this driver.
12987 To compile this driver as a module ( = code which can be inserted in
12988 and removed from the running kernel whenever you want), say M here
12989 and read Documentation/modules.txt. The module will be called
12994 Power Management support
12996 "Power Management" means that parts of your computer are shut
12997 off or put into a power conserving "sleep" mode if they are not
12998 being used. There are two competing standards for doing this: APM
12999 and ACPI. If you want to use either one, say Y here and then also to
13000 the requisite support below.
13002 Power Management is most important for battery powered laptop
13003 computers; if you have a laptop, check out the Linux Laptop home
13005 http://www.cs.utexas.edu/users/kharker/linux-laptop/ and the Battery
13006 Powered Linux mini-HOWTO, available from
13007 http://www.linuxdoc.org/docs.html#howto .
13009 Note that, even if you say N here, Linux on the x86 architecture
13010 will issue the hlt instruction if nothing is to be done, thereby
13011 sending the processor to sleep and saving power.
13015 The Advanced Configuration and Power Interface is a standard
13016 designed to allow the operating system more control over power
13017 management issues, such as suspending a computer in a low power
13018 consumption state after a certain time of inaction. It aims to be
13019 an improved version of APM (see below). ACPI has to be
13020 supported by the motherboard. You can read more about the standard
13021 at http://www.teleport.com/~acpi/ .
13023 If your computer supports ACPI and you want to use it, say Y here.
13024 You will then need supporting software; for location and more
13025 information, please read Documentation/pm.txt and the Battery
13026 Powered Linux mini-HOWTO, available from
13027 http://www.linuxdoc.org/docs.html#howto .
13029 If you say Y here and also to "Advanced Power Management" (APM)
13030 below, then ACPI has precedence in the sense that, if your hardware
13031 supports ACPI, it will be used and APM won't.
13033 ACPI interpreter (EXPERIMENTAL)
13034 CONFIG_ACPI_INTERPRETER
13035 If you say Y here, an ACPI interpreter will be included in your
13036 kernel, eventually making the full range of ACPI features
13037 available on systems that support ACPI. Note, this option will
13038 enlarge your kernel by about 120K.
13040 The interpreter is currently experimental so only say Y if
13041 you know what you are doing.
13043 Enter S1 for sleep (EXPERIMENTAL)
13044 CONFIG_ACPI_S1_SLEEP
13045 If you say Y here, ACPI compliant devices can enter level 1 of ACPI
13046 saving power levels. Basically, this will let them enter sleep mode.
13048 Advanced Power Management BIOS support
13050 APM is a BIOS specification for saving power using several different
13051 techniques. This is mostly useful for battery powered laptops with
13052 APM compliant BIOSes. If you say Y here, the system time will be
13053 reset after a RESUME operation, the /proc/apm device will provide
13054 battery status information, and user-space programs will receive
13055 notification of APM "events" (e.g. battery status change).
13057 If you select "Y" here, you can disable actual use of the APM
13058 BIOS by passing the "apm=off" option to the kernel at boot time.
13060 Note that the APM support is almost completely disabled for
13061 machines with more than one CPU.
13063 In order to use APM, you will need supporting software. For location
13064 and more information, read Documentation/pm.txt and the Battery
13065 Powered Linux mini-HOWTO, available from
13066 http://www.linuxdoc.org/docs.html#howto .
13068 This driver does not spin down disk drives (see the hdparm(8)
13069 manpage ("man 8 hdparm") for that), and it doesn't turn off
13070 VESA-compliant "green" monitors.
13072 This driver does not support the TI 4000M TravelMate and the ACER
13073 486/DX4/75 because they don't have compliant BIOSes. Many "green"
13074 desktop machines also don't have compliant BIOSes, and this driver
13075 may cause those machines to panic during the boot phase.
13077 Generally, if you don't have a battery in your machine, there isn't
13078 much point in using this driver and you should say N. If you get
13079 random kernel OOPSes or reboots that don't seem to be related to
13080 anything, try disabling/enabling this option (or disabling/enabling
13083 Some other things you should try when experiencing seemingly random,
13086 1) make sure that you have enough swap space and that it is
13088 2) pass the "no-hlt" option to the kernel
13089 3) switch on floating point emulation in the kernel and pass
13090 the "no387" option to the kernel
13091 4) pass the "floppy=nodma" option to the kernel
13092 5) pass the "mem=4M" option to the kernel (thereby disabling
13093 all but the first 4 MB of RAM)
13094 6) make sure that the CPU is not over clocked.
13095 7) read the sig11 FAQ at http://www.bitwizard.nl/sig11/
13096 8) disable the cache from your BIOS settings
13097 9) install a fan for the video card or exchange video RAM
13098 10) install a better fan for the CPU
13099 11) exchange RAM chips
13100 12) exchange the motherboard.
13102 To compile this driver as a module ( = code which can be inserted in
13103 and removed from the running kernel whenever you want), say M here
13104 and read Documentation/modules.txt. The module will be called
13107 Ignore USER SUSPEND
13108 CONFIG_APM_IGNORE_USER_SUSPEND
13109 This option will ignore USER SUSPEND requests. On machines with a
13110 compliant APM BIOS, you want to say N. However, on the NEC Versa M
13111 series notebooks, it is necessary to say Y because of a BIOS bug.
13113 Enable APM at boot time
13114 CONFIG_APM_DO_ENABLE
13115 Enable APM features at boot time. From page 36 of the APM BIOS
13116 specification: "When disabled, the APM BIOS does not automatically
13117 power manage devices, enter the Standby State, enter the Suspend
13118 State, or take power saving steps in response to CPU Idle calls."
13119 This driver will make CPU Idle calls when Linux is idle (unless this
13120 feature is turned off -- see "Do CPU IDLE calls", below). This
13121 should always save battery power, but more complicated APM features
13122 will be dependent on your BIOS implementation. You may need to turn
13123 this option off if your computer hangs at boot time when using APM
13124 support, or if it beeps continuously instead of suspending. Turn
13125 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
13126 T400CDT. This is off by default since most machines do fine without
13130 CONFIG_APM_CPU_IDLE
13131 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
13132 On some machines, this can activate improved power savings, such as
13133 a slowed CPU clock rate, when the machine is idle. These idle calls
13134 are made after the idle loop has run for some length of time (e.g.,
13135 333 mS). On some machines, this will cause a hang at boot time or
13136 whenever the CPU becomes idle. (On machines with more than one CPU,
13137 this option does nothing.)
13139 Enable console blanking using APM
13140 CONFIG_APM_DISPLAY_BLANK
13141 Enable console blanking using the APM. Some laptops can use this to
13142 turn off the LCD backlight when the screen blanker of the Linux
13143 virtual console blanks the screen. Note that this is only used by
13144 the virtual console screen blanker, and won't turn off the backlight
13145 when using the X Window system. This also doesn't have anything to
13146 do with your VESA-compliant power-saving monitor. Further, this
13147 option doesn't work for all laptops -- it might not turn off your
13148 backlight at all, or it might print a lot of errors to the console,
13149 especially if you are using gpm.
13151 RTC stores time in GMT
13152 CONFIG_APM_RTC_IS_GMT
13153 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
13154 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
13157 It is in fact recommended to store GMT in your RTC, because then you
13158 don't have to worry about daylight savings time changes. The only
13159 reason not to use GMT in your RTC is if you also run a broken OS
13160 that doesn't understand GMT.
13162 Allow interrupts during APM BIOS calls
13163 CONFIG_APM_ALLOW_INTS
13164 Normally we disable external interrupts while we are making calls to
13165 the APM BIOS as a measure to lessen the effects of a badly behaving
13166 BIOS implementation. The BIOS should reenable interrupts if it
13167 needs to. Unfortunately, some BIOSes do not -- especially those in
13168 many of the newer IBM Thinkpads. If you experience hangs when you
13169 suspend, try setting this to Y. Otherwise, say N.
13171 Use real mode APM BIOS call to power off
13172 CONFIG_APM_REAL_MODE_POWER_OFF
13173 Use real mode APM BIOS calls to switch off the computer. This is
13174 a work-around for a number of buggy BIOSes. Switch this option on if
13175 your computer crashes instead of powering off properly.
13177 Watchdog Timer Support
13179 If you say Y here (and to one of the following options) and create a
13180 character special file /dev/watchdog with major number 10 and minor
13181 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
13182 subsequently opening the file and then failing to write to it for
13183 longer than 1 minute will result in rebooting the machine. This
13184 could be useful for a networked machine that needs to come back
13185 online as fast as possible after a lock-up. There's both a watchdog
13186 implementation entirely in software (which can sometimes fail to
13187 reboot the machine) and a driver for hardware watchdog boards, which
13188 are more robust and can also keep track of the temperature inside
13189 your computer. For details, read Documentation/watchdog.txt in the
13192 The watchdog is usually used together with the watchdog daemon
13193 which is available via FTP (user: anonymous) from
13194 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/ . This daemon can also
13195 monitor NFS connections and can reboot the machine when the process
13200 Disable watchdog shutdown on close
13201 CONFIG_WATCHDOG_NOWAYOUT
13202 The default watchdog behaviour (which you get if you say N here) is
13203 to stop the timer if the process managing it closes the file
13204 /dev/watchdog. It's always remotely possible that this process might
13205 get killed. If you say Y here, the watchdog cannot be stopped once
13206 it has been started.
13210 If you have a WDT500P or WDT501P watchdog board, say Y here,
13211 otherwise N. It is not possible to probe for this board, which means
13212 that you have to inform the kernel about the IO port and IRQ using
13213 the "wdt=" kernel option (try "man bootparam" or see the
13214 documentation of your boot loader (lilo or loadlin) about how to
13215 pass options to the kernel at boot time).
13217 If you want to compile this as a module ( = code which can be
13218 inserted in and removed from the running kernel whenever you want),
13219 say M here and read Documentation/modules.txt. The module will be
13222 WDT PCI Watchdog timer
13224 If you have a PCI WDT500/501 watchdog board, say Y here,
13225 otherwise N. It is not possible to probe for this board, which means
13226 that you have to inform the kernel about the IO port and IRQ using
13227 the "wdt=" kernel option (try "man bootparam" or see the
13228 documentation of your boot loader (lilo or loadlin) about how to
13229 pass options to the kernel at boot time).
13231 If you want to compile this as a module ( = code which can be
13232 inserted in and removed from the running kernel whenever you want),
13233 say M here and read Documentation/modules.txt. The module will be
13238 Saying Y here and creating a character special file /dev/temperature
13239 with major number 10 and minor number 131 ("man mknod") will give
13240 you a thermometer inside your computer: reading from
13241 /dev/temperature yields one byte, the temperature in degrees
13242 Fahrenheit. This works only if you have a WDT501P watchdog board
13247 Enable the Fan Tachometer on the WDT501. Only do this if you have a
13248 fan tachometer actually set up.
13251 CONFIG_SOFT_WATCHDOG
13252 A software monitoring watchdog. This will fail to reboot your system
13253 from some situations that the hardware watchdog will recover
13254 from. Equally it's a lot cheaper to install.
13256 This driver is also available as a module ( = code which can be
13257 inserted in and removed from the running kernel whenever you want).
13258 If you want to compile it as a module, say M here and read
13259 Documentation/modules.txt. The module will be called softdog.o.
13261 Berkshire Products PC Watchdog
13263 This is the driver for the Berkshire Products PC Watchdog card.
13264 This card simply watches your kernel to make sure it doesn't freeze,
13265 and if it does, it reboots your computer after a certain amount of
13266 time. This driver is like the WDT501 driver but for different
13267 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
13268 watchdog cards can be ordered from http://www.berkprod.com .
13270 This driver is also available as a module ( = code which can be
13271 inserted in and removed from the running kernel whenever you want).
13272 The module is called pcwd.o. If you want to compile it as a module,
13273 say M here and read Documentation/modules.txt.
13275 Most people will say N.
13277 Acquire SBC Watchdog Timer
13279 This is the driver for the hardware watchdog on the PSC-6x86 Single
13280 Board Computer produced by Acquire Inc (and others). This watchdog
13281 simply watches your kernel to make sure it doesn't freeze, and if
13282 it does, it reboots your computer after a certain amount of time.
13284 This driver is like the WDT501 driver but for different hardware.
13285 This driver is also available as a module ( = code which can be
13286 inserted in and removed from the running kernel whenever you want).
13287 The module is called pscwdt.o. If you want to compile it as a
13288 module, say M here and read Documentation/modules.txt. Most people
13293 This is a driver for the Mixcom hardware watchdog cards. This
13294 watchdog simply watches your kernel to make sure it doesn't freeze,
13295 and if it does, it reboots your computer after a certain amount of
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 is called mixcomwd.o. If you want to compile it as a
13301 module, say M here and read Documentation/modules.txt. Most people
13304 /dev/cpu/microcode - Intel P6 CPU microcode support
13306 If you say Y here and also to "/dev file system support" in the
13307 'File systems' section, you will be able to update the microcode on
13308 Intel processors in the P6 family, e.g. Pentium Pro, Pentium II,
13309 Pentium III, Xeon etc. You will obviously need the actual microcode
13310 binary data itself which is not shipped with the Linux kernel.
13312 For latest news and information on obtaining all the required
13313 ingredients for this driver, check:
13314 http://www.urbanmyth.org/microcode/
13316 This driver is also available as a module ( = code which can be
13317 inserted in and removed from the running kernel whenever you want).
13318 The module will be called microcode.o. If you want to compile it as
13319 a module, say M here and read Documentation/modules.txt.
13321 /dev/cpu/*/msr - Model-specific register support
13323 This device gives privileged processes access to the x86
13324 Model-Specific Registers (MSRs). It is a character device with
13325 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
13326 MSR accesses are directed to a specific CPU on multi-processor
13329 /dev/cpu/*/cpuid - CPU information support
13331 This device gives processes access to the x86 CPUID instruction to
13332 be executed on a specific processor. It is a character device
13333 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
13336 Enhanced Real Time Clock Support
13338 If you say Y here and create a character special file /dev/rtc with
13339 major number 10 and minor number 135 using mknod ("man mknod"), you
13340 will get access to the real time clock (or hardware clock) built
13341 into your computer.
13343 Every PC has such a clock built in. It can be used to generate
13344 signals from as low as 1Hz up to 8192Hz, and can also be used
13345 as a 24 hour alarm. It reports status information via the file
13346 /proc/driver/rtc and its behaviour is set by various ioctls on
13349 If you run Linux on a multiprocessor machine and said Y to
13350 "Symmetric Multi Processing" above, you should say Y here to read
13351 and set the RTC in an SMP compatible fashion.
13353 If you think you have a use for such a device (such as periodic data
13354 sampling), then say Y here, and read Documentation/rtc.txt for
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 is called rtc.o. If you want to compile it as a module,
13360 say M here and read Documentation/modules.txt.
13363 #EFI Real Time Clock Services
13366 Tadpole ANA H8 Support
13368 The Hitachi H8/337 is a microcontroller used to deal with the power
13369 and thermal environment. If you say Y here, you will be able to
13370 communicate with it via a character special device.
13376 If you say Y here and create a character special file /dev/nvram
13377 with major number 10 and minor number 144 using mknod ("man mknod"),
13378 you get read and write access to the 50 bytes of non-volatile memory
13379 in the real time clock (RTC), which is contained in every PC and
13382 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
13383 on Ataris. /dev/nvram may be used to view settings there, or to
13384 change them (with some utility). It could also be used to frequently
13385 save a few bits of very important data that may not be lost over
13386 power-off and for which writing to disk is too insecure. Note
13387 however that most NVRAM space in a PC belongs to the BIOS and you
13388 should NEVER idly tamper with it. See Ralf Brown's interrupt list
13389 for a guide to the use of CMOS bytes by your BIOS.
13391 On Atari machines, /dev/nvram is always configured and does not need
13394 This driver is also available as a module ( = code which can be
13395 inserted in and removed from the running kernel whenever you want).
13396 The module will be called nvram.o. If you want to compile it as a
13397 module, say M here and read Documentation/modules.txt.
13401 If you have a joystick, 6dof controller, gamepad, steering wheel,
13402 weapon control system or something like that you can say Y here to
13403 enable generic support for these controllers. You will also need to
13404 say Y or M to at least one of the hardware specific drivers. This
13405 will make the controllers available as /dev/input/jsX devices.
13406 Please read the file Documentation/joystick.txt which contains more
13407 information and the location of the joystick package that you'll
13412 Say Y here if you have an ISA, ISAPnP or PCI standard gameport.
13413 For more information on how to use the driver please read
13414 Documentation/joystick.txt
13416 This driver is also available as a module ( = code which can be
13417 inserted in and removed from the running kernel whenever you want).
13418 The module will be called ns558.o. If you want to compile
13419 it as a module, say M here and read Documentation/modules.txt.
13421 PDPI Lightning 4 gamecard
13422 CONFIG_INPUT_LIGHTNING
13423 Say Y here if you have a PDPI Lightning 4 gamecard. For more
13424 information on how to use the driver please read
13425 Documentation/joystick.txt
13427 This driver is also available as a module ( = code which can be
13428 inserted in and removed from the running kernel whenever you want).
13429 The module will be called lightning.o. If you want to compile
13430 it as a module, say M here and read Documentation/modules.txt.
13432 Aureal Vortex and Trident 4DWave gameports
13433 CONFIG_INPUT_PCIGAME
13434 Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
13435 card. For more information on how to use the driver please read
13436 Documentation/joystick.txt
13438 This driver is also available as a module ( = code which can be
13439 inserted in and removed from the running kernel whenever you want).
13440 The module will be called pcigame.o. If you want to compile
13441 it as a module, say M here and read Documentation/modules.txt.
13443 Classic PC analog joysticks and gamepads
13444 CONFIG_INPUT_ANALOG
13445 Say Y here if you have a controller that connects to the PC
13446 gameport. This supports many different types, including joysticks
13447 with throttle control, with rudders, or with extensions like
13448 additional hats and buttons compatible with CH Flightstick Pro,
13449 ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg
13450 joysticks. For more information on how to use the driver please read
13451 Documentation/joystick.txt
13453 This driver is also available as a module ( = code which can be
13454 inserted in and removed from the running kernel whenever you want).
13455 The module will be called analog.o. If you want to compile
13456 it as a module, say M here and read Documentation/modules.txt.
13458 Assasin 3D and MadCatz Panther devices
13460 Say Y here if you have an FPGaming or MadCatz controller using the
13461 A3D protocol over the PC gameport. For more information on how to
13462 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 a3d.o. If you want to compile
13467 it as a module, say M here and read Documentation/modules.txt.
13469 Logitech ADI digital joysticks and gamepads
13471 Say Y here if you have a Logitech controller using the ADI
13472 protocol over the PC gameport. For more information on how to use
13473 the 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 adi.o. If you want to compile
13478 it as a module, say M here and read Documentation/modules.txt.
13480 Creative Labs Blaster Cobra gamepad
13482 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
13483 For more information on how to use the driver please read
13484 Documentation/joystick.txt
13486 This driver is also available as a module ( = code which can be
13487 inserted in and removed from the running kernel whenever you want).
13488 The module will be called cobra.o. If you want to compile
13489 it as a module, say M here and read Documentation/modules.txt.
13491 Genius Flight2000 Digital joysticks and gamepads
13493 Say Y here if you have a Genius Flight2000 or MaxFighter
13494 digitally communicating joystick or gamepad. For more information
13495 on how to use the driver please read Documentation/joystick.txt
13497 This driver is also available as a module ( = code which can be
13498 inserted in and removed from the running kernel whenever you want).
13499 The module will be called gf2k.o. If you want to compile
13500 it as a module, say M here and read Documentation/modules.txt.
13502 Gravis GrIP joysticks and gamepads
13504 Say Y here if you have a Gravis controller using the GrIP protocol
13505 over the PC gameport. For more information on how to use the driver
13506 please read Documentation/joystick.txt
13508 This driver is also available as a module ( = code which can be
13509 inserted in and removed from the running kernel whenever you want).
13510 The module will be called grip.o. If you want to compile
13511 it as a module, say M here and read Documentation/modules.txt.
13513 InterAct digital joysticks and gamepads
13514 CONFIG_INPUT_INTERACT
13515 Say Y hereif you have an InterAct gameport or joystick
13516 communicating digitally over the gameport. For more information on
13517 how to use the driver please read Documentation/joystick.txt
13519 This driver is also available as a module ( = code which can be
13520 inserted in and removed from the running kernel whenever you want).
13521 The module will be called interact.o. If you want to compile
13522 it as a module, say M here and read Documentation/modules.txt.
13524 ThrustMaster DirectConnect joysticks and gamepads
13526 Say Y here if you have a ThrustMaster controller using the
13527 DirectConnect (BSP) protocol over the PC gameport. For more
13528 information on how to use the driver please read
13529 Documentation/joystick.txt
13531 This driver is also available as a module ( = code which can be
13532 inserted in and removed from the running kernel whenever you want).
13533 The module will be called tmdc.o. If you want to compile
13534 it as a module, say M here and read Documentation/modules.txt.
13536 Microsoft SideWinder digital joysticks and gamepads
13537 CONFIG_INPUT_SIDEWINDER
13538 Say Y here if you have a Microsoft controller using the Digital
13539 Overdrive protocol over PC gameport. For more information on how to
13540 use the driver please read Documentation/joystick.txt
13542 This driver is also available as a module ( = code which can be
13543 inserted in and removed from the running kernel whenever you want).
13544 The module will be called sidewinder.o. If you want to compile
13545 it as a module, say M here and read Documentation/modules.txt.
13547 Serial port input line discipline
13548 CONFIG_INPUT_SERPORT
13549 Say Y hereif you plan to use a joystick that communicates over the
13550 serial (COM) port. For more information on how to use the driver
13551 please read Documentation/joystick.txt
13553 This driver is also available as a module ( = code which can be
13554 inserted in and removed from the running kernel whenever you want).
13555 The module will be called serport.o. If you want to compile
13556 it as a module, say M here and read Documentation/modules.txt.
13558 Logitech WingMan Warrior joystick
13559 CONFIG_INPUT_WARRIOR
13560 Say Y here if you have a Logitech WingMan Warrior joystick
13561 connected to your computer's serial port. For more information on
13562 how to use the driver please read Documentation/joystick.txt
13564 This driver is also available as a module ( = code which can be
13565 inserted in and removed from the running kernel whenever you want).
13566 The module will be called warrior.o. If you want to compile
13567 it as a module, say M here and read Documentation/modules.txt.
13569 LogiCad3d Magellan/SpaceMouse 6dof controller
13570 CONFIG_INPUT_MAGELLAN
13571 Say Y here if you have a Magellan or Space Mouse 6DOF controller
13572 connected to your computer's serial port. For more information on
13573 how to use the driver please read Documentation/joystick.txt
13575 This driver is also available as a module ( = code which can be
13576 inserted in and removed from the running kernel whenever you want).
13577 The module will be called magellan.o. If you want to compile
13578 it as a module, say M here and read Documentation/modules.txt.
13580 SpaceTec SpaceOrb/Avenger 6dof controller
13581 CONFIG_INPUT_SPACEORB
13582 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
13583 controller connected to your computer's serial port. For more
13584 information on how to use the driver please read
13585 Documentation/joystick.txt
13587 This driver is also available as a module ( = code which can be
13588 inserted in and removed from the running kernel whenever you want).
13589 The module will be called spaceorb.o. If you want to compile
13590 it as a module, say M here and read Documentation/modules.txt.
13592 SpaceTec SpaceBall 4000 FLX 6dof controller
13593 CONFIG_INPUT_SPACEBALL
13594 Say Y here if you have a SpaceTec SpaceBall 4000 FLX controller
13595 connected to your computer's serial port. For more information on
13596 how to use the driver please read Documentation/joystick.txt
13598 I-Force joysticks/wheels
13599 CONFIG_INPUT_IFORCE_232
13600 Say Y here if you have an I-Force joystick or steering wheel
13601 connected to your serial (COM) port. For more information on
13602 how to use the driver please read Documentation/joystick.txt
13604 This driver is also available as a module ( = code which can be
13605 inserted in and removed from the running kernel whenever you want).
13606 The module will be called iforce.o. If you want to compile
13607 it as a module, say M here and read Documentation/modules.txt.
13609 I-Force joysticks/wheels
13610 CONFIG_INPUT_IFORCE_USB
13611 Say Y here if you have an I-Force joystick or steering wheel
13612 connected to your USB port. For more information on how to use the
13613 driver please read Documentation/joystick.txt
13615 This driver is also available as a module ( = code which can be
13616 inserted in and removed from the running kernel whenever you want).
13617 The module will be called iforce.o. If you want to compile
13618 it as a module, say M here and read Documentation/modules.txt.
13620 Multisystem, Sega Genesis, Saturn joysticks and gamepads
13622 Say Y here if you have a Sega Master System gamepad, Sega Genesis
13623 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
13624 Commodore, Amstrad CPC joystick connected to your parallel port.
13625 For more information on how to use the driver please read
13626 Documentation/joystick.txt and Documentation/joystick-parport.txt.
13628 This driver is also available as a module ( = code which can be
13629 inserted in and removed from the running kernel whenever you want).
13630 The module will be called db9.o. If you want to compile
13631 it as a module, say M here and read Documentation/modules.txt.
13633 Multisystem, NES, SNES, N64, PSX joysticks and gamepads
13634 CONFIG_INPUT_GAMECON
13635 Say Y here if you have a Nintendo Entertainment System gamepad,
13636 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
13637 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
13638 Commodore, Amstrad CPC joystick connected to your parallel port.
13639 For more information on how to use the driver please read
13640 Documentation/joystick.txt and Documentation/joystick-parport.txt
13642 This driver is also available as a module ( = code which can be
13643 inserted in and removed from the running kernel whenever you want).
13644 The module will be called gamecon.o. If you want to compile
13645 it as a module, say M here and read Documentation/modules.txt.
13647 Multisystem joysticks via TurboGraFX device
13648 CONFIG_INPUT_TURBOGRAFX
13649 Say Y here if you have the TurboGraFX interface by Steffen
13650 Schwenke, and want to use it with Multiststem -- Atari, Amiga,
13651 Commodore, Amstrad CPC joystick. For more information on how to use
13652 the driver please read Documentation/joystick.txt and
13653 Documentation/joystick-parport.txt
13655 This driver is also available as a module ( = code which can be
13656 inserted in and removed from the running kernel whenever you want).
13657 The module will be called turbografx.o. If you want to compile
13658 it as a module, say M here and read Documentation/modules.txt.
13661 CONFIG_INPUT_AMIJOY
13662 Say Y here if you have an Amiga with a digital joystick connected
13663 to it. For more information on how to use the driver please read
13664 Documentation/joystick.txt
13666 This driver is also available as a module ( = code which can be
13667 inserted in and removed from the running kernel whenever you want).
13668 The module will be called joy-amiga.o. If you want to compile
13669 it as a module, say M here and read Documentation/modules.txt.
13671 Atomwide Serial Support
13672 CONFIG_ATOMWIDE_SERIAL
13673 If you have an Atomwide Serial card for an Acorn system, say Y to
13674 this option. The driver can handle 1, 2, or 3 port cards.
13677 The Serial Port Dual Serial Port
13678 CONFIG_DUALSP_SERIAL
13679 If you have the Serial Port's dual serial card for an Acorn system,
13680 say Y to this option. If unsure, say N
13684 If you say Y here and create a character device node /dev/nwbutton
13685 with major and minor numbers 10 and 158 ("man mknod"), then every
13686 time the orange button is pressed a number of times, the number of
13687 times the button was pressed will be written to that device.
13689 This is most useful for applications, as yet unwritten, which
13690 perform actions based on how many times the button is pressed in a
13693 Do not hold the button down for too long, as the driver does not
13694 alter the behaviour of the hardware reset circuitry attached to the
13695 button; it will still execute a hard reset if the button is held
13696 down for longer than approximately five seconds.
13698 This driver is also available as a module ( = code which can be
13699 inserted in and removed from the running kernel whenever you want).
13700 If you want to compile it as a module, say M here and read
13701 Documentation/modules.txt. The module will be called nwbutton.o.
13703 Most people will answer Y to this question and "Reboot Using Button"
13704 below to be able to initiate a system shutdown from the button.
13706 Reboot Using Button
13707 CONFIG_NWBUTTON_REBOOT
13708 If you say Y here, then you will be able to initiate a system
13709 shutdown and reboot by pressing the orange button a number of times.
13710 The number of presses to initiate the shutdown is two by default,
13711 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
13712 in nwbutton.h and recompiling the driver or, if you compile the
13713 driver as a module, you can specify the number of presses at load
13714 time with "insmod button reboot_count=<something>".
13718 If you have a sound card in your computer, i.e. if it can say more
13719 than an occasional beep, say Y. Be sure to have all the information
13720 about your sound card and its configuration down (I/O port,
13721 interrupt and DMA channel), because you will be asked for it.
13723 You want to read the Sound-HOWTO, available from
13724 http://www.linuxdoc.org/docs.html#howto . General information
13725 about the modular sound system is contained in the files
13726 Documentation/sound/Introduction. The file
13727 Documentation/sound/README.OSS contains some slightly outdated but
13728 still useful information as well.
13730 If you have a PnP sound card and you want to configure it at boot
13731 time using the ISA PnP tools (read
13732 http://www.roestock.demon.co.uk/isapnptools/ ), then you need to
13733 compile the sound card support as a module ( = code which can be
13734 inserted in and removed from the running kernel whenever you want)
13735 and load that module after the PnP configuration is finished. To do
13736 this, say M here and read Documentation/modules.txt as well as
13737 Documentation/sound/README.modules; the module will be called
13740 I'm told that even without a sound card, you can make your computer
13741 say more than an occasional beep, by programming the PC speaker.
13742 Kernel patches and supporting utilities to do that are in the pcsp
13743 package, available at ftp://ftp.infradead.org/pub/pcsp/ .
13747 OSS is the Open Sound System suite of sound card drivers. They make
13748 sound programming easier since they provide a common API. Say Y or M
13749 here (the module will be called sound.o) if you haven't found a
13750 driver for your sound card above, then pick your driver from the
13753 Persistent DMA buffers
13755 Linux can often have problems allocating DMA buffers for ISA sound
13756 cards on machines with more than 16MB of RAM. This is because ISA
13757 DMA buffers must exist below the 16MB boundary and it is quite
13758 possible that a large enough free block in this region cannot be
13759 found after the machine has been running for a while. If you say Y
13760 here the DMA buffers (64Kb) will be allocated at boot time and kept
13761 until the shutdown. This option is only useful if you said Y to
13762 "OSS sound modules", above. If you said M to "OSS sound modules"
13763 then you can get the persistent DMA buffer functionality by passing
13764 the command-line argument "dmabuf=1" to the sound.o module.
13766 Say Y unless you have 16MB or less RAM or a PCI sound card.
13768 Support for Aztech Sound Galaxy (non-PnP) cards
13769 CONFIG_SOUND_SGALAXY
13770 This module initializes the older non Plug and Play sound galaxy
13771 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
13772 Galaxy Washington 16.
13774 If you compile the driver into the kernel, you have to add
13775 "sgalaxy=<io>,<irq>,<dma>,<dma2>,<sgbase>" to the kernel command
13778 Support for AD1816(A) based cards (EXPERIMENTAL)
13779 CONFIG_SOUND_AD1816
13780 Say M here if you have a sound card based on the Analog Devices
13783 If you compile the driver into the kernel, you have to add
13784 "ad1816=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
13786 Yamaha OPL3-SA1 audio controller
13787 CONFIG_SOUND_OPL3SA1
13788 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
13789 usually built into motherboards. Read Documentation/sound/OPL3-SA
13792 If you compile the driver into the kernel, you have to add
13793 "opl3sa=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
13796 ProAudioSpectrum 16 support
13798 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
13799 16 or Logitech SoundMan 16 sound card. Answer N if you have some
13800 other card made by Media Vision or Logitech since those are not
13801 PAS16 compatible. Please read Documentation/sound/PAS16.
13803 If you compile the driver into the kernel, you have to add
13804 "pas2=<io>,<irq>,<dma>,<dma2>,<sbio>,<sbirq>,<sbdma>,<sbdma2>
13805 to the kernel command line.
13807 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
13809 Answer Y if you have an original Sound Blaster card made by Creative
13810 Labs or a 100% hardware compatible clone (like the Thunderboard or
13811 SM Games). For an unknown card you may answer Y if the card claims
13812 to be Sound Blaster-compatible.
13814 Please read the file Documentation/sound/Soundblaster.
13816 You should also say Y here for cards based on the Avance Logic
13817 ALS-007 and ALS-1X0 chips (read Documentation/sound/ALS) and for cards
13818 based on ESS chips (read Documentation/sound/ESS1868 and
13819 Documentation/sound/ESS). If you have an SB AWE 32 or SB AWE 64, say
13820 Y here and also to "AWE32 synth" below and read
13821 Documentation/sound/INSTALL.awe. If you have an IBM Mwave card, say
13822 Y here and read Documentation/sound/mwave.
13824 If you compile the driver into the kernel and don't want to use
13825 isapnp, you have to add "sb=<io>,<irq>,<dma>,<dma2>" to the kernel
13828 You can say M here to compile this driver as a module; the module is
13831 #Loopback MIDI device support
13832 #CONFIG_SOUND_VMIDI
13834 ### somebody please fill this in.
13837 Gravis Ultrasound support
13839 Say Y here for any type of Gravis Ultrasound card, including
13840 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
13841 more information on configuring this card with modules.
13843 If you compile the driver into the kernel, you have to add
13844 "gus=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
13846 MPU-401 support (NOT for SB16)
13847 CONFIG_SOUND_MPU401
13848 Be careful with this question. The MPU401 interface is supported by
13849 all sound cards. However, some natively supported cards have their
13850 own driver for MPU401. Enabling this MPU401 option with these cards
13851 will cause a conflict. Also, enabling MPU401 on a system that
13852 doesn't really have a MPU401 could cause some trouble. If your card
13853 was in the list of supported cards, look at the card specific
13854 instructions in the drivers/sound/Readme.cards file. It's safe to
13855 answer Y if you have a true MPU401 MIDI interface card.
13857 If you compile the driver into the kernel, you have to add
13858 "mpu401=<io>,<irq>" to the kernel command line.
13861 CONFIG_SOUND_UART6850
13862 This option enables support for MIDI interfaces based on the 6850
13863 UART chip. This interface is rarely found on sound cards. It's safe
13864 to answer N to this question.
13866 If you compile the driver into the kernel, you have to add
13867 "uart6850=<io>,<irq>" to the kernel command line.
13869 PSS (AD1848, ADSP-2115, ESC614) support
13871 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
13872 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
13873 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
13874 how to compile it into the kernel or as a module see the file
13875 Documentation/sound/PSS.
13877 If you compile the driver into the kernel, you have to add
13878 "pss=<io>,<mssio>,<mssirq>,<mssdma>,<mpuio>,<mpuirq>" to the kernel
13881 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
13883 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
13884 cards if they have master volume, bass, treble, and you can't
13885 control it under Linux. If you answer N for Beethoven ADSP-16, you
13886 can't control master volume, bass, treble and synth volume.
13888 If you said M to "PSS support" above, you may enable or disable this
13889 PSS mixer with the module parameter pss_mixer. For more information
13890 see the file Documentation/sound/PSS.
13892 Have DSPxxx.LD firmware file
13893 CONFIG_PSS_HAVE_BOOT
13894 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
13895 to include this file. Without this file the synth device (OPL) may
13898 Full pathname of DSPxxx.LD firmware file
13899 CONFIG_PSS_BOOT_FILE
13900 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
13903 Microsoft Sound System support
13905 Again think carefully before answering Y to this question. It's safe
13906 to answer Y if you have the original Windows Sound System card made
13907 by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may say Y
13908 in case your card is NOT among these:
13910 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
13911 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
13912 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
13913 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
13914 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
13915 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
13916 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
13917 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
13918 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
13919 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
13920 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
13921 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
13922 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
13924 For cards having native support in VoxWare, consult the card
13925 specific instructions in drivers/sound/Readme.cards. Some drivers
13926 have their own MSS support and saying Y to this option will cause a
13929 If you compile the driver into the kernel, you have to add
13930 "ad1848=<io>,<irq>,<dma>,<dma2>[,<type>]" to the kernel command
13933 SGI Visual Workstation on-board audio
13935 Say Y or M if you have an SGI Visual Workstation and you want to
13936 be able to use its on-board audio. Read Documentation/sound/visws
13937 for more info on this driver's capabilities.
13939 Ensoniq Soundscape support
13940 CONFIG_SOUND_SSCAPE
13941 Answer Y if you have a sound card based on the Ensoniq SoundScape
13942 chipset. Such cards are being manufactured at least by Ensoniq, Spea
13943 and Reveal (Reveal makes also other cards).
13945 If you compile the driver into the kernel, you have to add
13946 "sscape=<io>,<irq>,<dma>,<mpuio>,<mpuirq>" to the kernel command
13949 MediaTriX AudioTriX Pro support
13951 Answer Y if you have the AudioTriX Pro sound card manufactured
13954 Have TRXPRO.HEX firmware file
13955 CONFIG_TRIX_HAVE_BOOT
13956 The MediaTrix AudioTrix Pro has an on-board microcontroller which
13957 needs to be initialized by downloading the code from the file
13958 TRXPRO.HEX in the DOS driver directory. If you don't have the
13959 TRXPRO.HEX file handy you may skip this step. However, the SB and
13960 MPU-401 modes of AudioTrix Pro will not work without this file!
13962 Full pathname of TRXPRO.HEX firmware file
13963 CONFIG_TRIX_BOOT_FILE
13964 Enter the full pathname of your TRXPRO.HEX file, starting from /.
13966 Support for OPTi MAD16 and/or Mozart based cards
13968 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
13969 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931,
13970 please read drivers/sound/README.C931. These chips are currently
13971 quite common so it's possible that many no-name cards have one of
13972 them. In addition the MAD16 chip is used in some cards made by known
13973 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
13974 and Diamond (latest ones). Note however that the Tropez sound cards
13975 have their own driver; if you have one of those, say N here and Y or
13976 M to "Full support for Turtle Beach WaveFront", below.
13978 If you compile the driver into the kernel, you have to add
13979 "mad16=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the
13980 kernel command line.
13982 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
13983 more information on setting these cards up as modules.
13985 Full support for Turtle Beach WaveFront synth/sound cards
13986 CONFIG_SOUND_WAVEFRONT
13987 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
13988 and read the files Documentation/sound/Wavefront and
13989 Documentation/sound/Tropez+.
13991 Support MIDI in older MAD16 based cards (requires SB)
13992 CONFIG_MAD16_OLDCARD
13993 Answer Y (or M) if you have an older card based on the C928 or
13994 Mozart chipset and you want to have MIDI support. If you enable this
13995 option you also need to enable support for Sound Blaster.
13997 Support for Crystal CS4232 based (PnP) cards
13998 CONFIG_SOUND_CS4232
13999 Say Y here if you have a card based on the Crystal CS4232 chip set,
14000 which uses its own Plug and Play protocol.
14002 If you compile the driver into the kernel, you have to add
14003 "cs4232=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
14006 See Documentation/sound/CS4232 for more information on configuring
14009 Support for Yamaha OPL3-SA2, SA3, and SAx based PnP cards
14010 CONFIG_SOUND_OPL3SA2
14011 Say Y or M if you have a card based on one of these Yamaha
14012 sound chipsets. Read Documentation/sound/OPL3-SA2 for more
14013 information on configuring these cards.
14015 If you compile the driver into the kernel, you have to add
14016 "opl3sa2=<io>,<irq>,<dma>,<dma2>,<mssio>,<mpuio>" to the kernel
14019 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
14021 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
14024 If you compile the driver into the kernel, you have to add
14025 "maui=<io>,<irq>" to the kernel command line.
14027 Have OSWF.MOT firmware file
14028 CONFIG_MAUI_HAVE_BOOT
14029 Turtle Beach Maui and Tropez sound cards have a microcontroller
14030 which needs to be initialized prior to use. OSWF.MOT is a file
14031 distributed with the card's DOS/Windows drivers. Answer Y if you
14034 Full pathname of OSWF.MOT firmware file
14035 CONFIG_MAUI_BOOT_FILE
14036 Enter the full pathname of your OSWF.MOT file, starting from /.
14038 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
14039 CONFIG_SOUND_MSNDCLAS
14040 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
14041 Monterey (not for the Pinnacle or Fiji).
14043 See Documentation/sound/MultiSound for important information about
14046 Full pathname of MSNDINIT.BIN firmware file
14047 CONFIG_MSNDCLAS_INIT_FILE
14048 The MultiSound cards have two firmware files which are required for
14049 operation, and are not currently included. These files can be
14050 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14051 information on how to obtain this.
14053 Full pathname of MSNDPERM.BIN firmware file
14054 CONFIG_MSNDCLAS_PERM_FILE
14055 The MultiSound cards have two firmware files which are required for
14056 operation, and are not currently included. These files can be
14057 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14058 information on how to obtain this.
14060 Support for Turtle Beach MultiSound Pinnacle, Fiji
14061 CONFIG_SOUND_MSNDPIN
14062 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
14063 See Documentation/sound/MultiSound for important information about
14066 Full pathname of PNDSPINI.BIN firmware file
14067 CONFIG_MSNDPIN_INIT_FILE
14068 The MultiSound cards have two firmware files which are required for
14069 operation, and are not currently included. These files can be
14070 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14071 information on how to obtain this.
14073 Full pathname of PNDSPERM.BIN firmware file
14074 CONFIG_MSNDPIN_PERM_FILE
14075 The MultiSound cards have two firmware files which are required for
14076 operation, and are not currently included. These files can be
14077 obtained from Turtle Beach. See Documentation/sound/MultiSound for
14078 information on how to obtain this.
14080 MSND Pinnacle have S/PDIF I/O
14081 CONFIG_MSNDPIN_DIGITAL
14082 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
14083 answer Y here; otherwise, say N. If you have this, you will be able
14084 to play and record from the S/PDIF port (digital signal). See
14085 Documentation/sound/MultiSound for information on how to make use of
14088 MSND Pinnacle non-PnP Mode
14089 CONFIG_MSNDPIN_NONPNP
14090 The Pinnacle and Fiji card resources can be configured either with
14091 PnP, or through a configuration port. Say Y here if your card is NOT
14092 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
14093 use of the IDE and joystick peripherals on the card as well; these
14094 do not show up when the card is in PnP mode. Specifying zero for any
14095 resource of a device will disable the device. If you are running the
14096 card in PnP mode, you must say N here and use isapnptools to
14097 configure the card's resources.
14099 MSND Pinnacle config port
14101 This is the port which the Pinnacle and Fiji uses to configure the
14102 card's resources when not in PnP mode. If your card is in PnP mode,
14103 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
14106 MSND buffer size (kB)
14107 CONFIG_MSND_FIFOSIZE
14108 Configures the size of each audio buffer, in kilobytes, for
14109 recording and playing in the MultiSound drivers (both the Classic
14110 and Pinnacle). Larger values reduce the chance of data overruns at
14111 the expense of overall latency. If unsure, use the default.
14113 FM synthesizer (YM3812/OPL-3) support
14114 CONFIG_SOUND_YM3812
14115 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
14116 Answering Y is usually a safe and recommended choice, however some
14117 cards may have software (TSR) FM emulation. Enabling FM support with
14118 these cards may cause trouble (I don't currently know of any such
14120 Please read the file Documentation/sound/OPL3 if your card has an
14123 If you compile the driver into the kernel, you have to add
14124 "opl3=<io>" to the kernel command line.
14128 ACI mixer (miroPCM12/PCM20)
14129 CONFIG_SOUND_ACI_MIXER
14130 ACI (Audio Command Interface) is a protocol used to communicate with
14131 the microcontroller on some sound cards produced by miro, e.g. the
14132 miroSOUND PCM12 and PCM20. The main function of the ACI is to
14133 control the mixer and to get a product identification.
14135 This Voxware ACI driver currently only supports the ACI functions on
14136 the miroSOUND PCM12 and PCM20 cards. On the PCM20, ACI also controls
14137 the radio tuner. This is supported in the video4linux
14138 radio-miropcm20 driver.
14141 CONFIG_SOUND_AWE32_SYNTH
14142 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
14143 similar sound card. See Documentation/sound/README.awe,
14144 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
14145 available from http://www.linuxdoc.org/docs.html#howto for more
14148 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
14149 CONFIG_SOUND_AEDSP16
14150 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
14151 driver supports Audio Excel DSP 16 but not the III nor PnP versions
14154 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
14155 a Microsoft Sound System card, so you should have said Y to either
14156 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
14157 or "Microsoft Sound System support", above, and you need to answer
14158 the "MSS emulation" and "SBPro emulation" questions below
14159 accordingly. You should say Y to one and only one of these two
14162 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
14163 drivers/sound/lowlevel/aedsp16.c as well as
14164 Documentation/sound/AudioExcelDSP16 to get more information about
14165 this driver and its configuration.
14167 Audio Excel DSP 16 (SBPro emulation)
14168 CONFIG_AEDSP16_SBPRO
14169 Answer Y if you want your audio card to emulate Sound Blaster Pro.
14170 You should then say Y to "100% Sound Blaster compatibles
14171 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
14174 If you compile the driver into the kernel, you have to add
14175 "aedsp16=<io>,<irq>,<dma>,<mssio>,<mpuio>,<mouirq>" to the kernel
14178 Audio Excel DSP 16 (MSS emulation)
14180 Answer Y if you want your audio card to emulate Microsoft Sound
14181 System. You should then say Y to "Microsoft Sound System support"
14182 and say N to "Audio Excel DSP 16 (SBPro emulation)".
14184 SC-6600 based audio cards (new Audio Excel DSP 16)
14186 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
14187 16 cards. Find in the manual the FCC ID of your audio card and
14188 answer Y if you have an SC6600 DSP.
14190 SC-6600 Joystick Interface
14192 Say Y here in order to use the joystick interface of the Audio Excel
14195 SC-6600 CDROM Interface
14196 CONFIG_SC6600_CDROM
14197 This is used to activate the the CDROM interface of the Audio Excel
14198 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
14201 Audio Excel DSP 16 (MPU401 emulation)
14202 CONFIG_AEDSP16_MPU401
14203 Answer Y if you want your audio card to emulate the MPU-401 midi
14204 interface. You should then also say Y to "MPU-401 support".
14206 Note that the I/O base for MPU-401 support of aedsp16 is the same
14207 you have selected for "MPU-401 support". If you are using this
14208 driver as a module you have to specify the MPU I/O base address with
14209 the parameter 'mpu_base=0xNNN'.
14211 Creative EMU10K1 based PCI sound cards
14212 CONFIG_SOUND_EMU10K1
14213 Say Y or M if you have a PCI sound card using the EMU10K1
14214 chipset, such as the Creative SBLive!, SB PCI512 or Emu-APS.
14216 Crystal SoundFusion (CS4280/461x)
14217 CONFIG_SOUND_FUSION
14218 This module drives the Crystal SoundFusion devices (CS4280/46xx series)
14219 when wired as native sound drivers with AC97 codecs. If this driver
14220 does not work try the CS4232 driver.
14222 Ensoniq ES1370 based PCI sound cards
14223 CONFIG_SOUND_ES1370
14224 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14225 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
14226 out if your sound card uses an ES1370 without removing your
14227 computer's cover, use lspci -n and look for the PCI ID
14228 1274:5000. Since Ensoniq was bought by Creative Labs,
14229 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
14230 This driver differs slightly from OSS/Free, so PLEASE READ
14231 Documentation/sound/es1370.
14233 Ensoniq ES1371 based PCI sound cards
14234 CONFIG_SOUND_ES1371
14235 Say Y or M if you have a PCI sound card utilizing the Ensoniq
14236 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
14237 your sound card uses an ES1371 without removing your computer's
14238 cover, use lspci -n and look for the PCI ID 1274:1371. Since
14239 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
14240 models are either ES1370 or ES1371 based. This driver differs
14241 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
14243 ESS Solo1 based PCI sound cards (eg. SC1938)
14244 CONFIG_SOUND_ESSSOLO1
14245 Say Y or M if you have a PCI sound card utilizing the ESS Technology
14246 Solo1 chip. To find out if your sound card uses a
14247 Solo1 chip without removing your computer's cover, use
14248 lspci -n and look for the PCI ID 125D:1969. This driver
14249 differs slightly from OSS/Free, so PLEASE READ
14250 Documentation/sound/solo1.
14252 S3 SonicVibes based PCI sound cards
14253 CONFIG_SOUND_SONICVIBES
14254 Say Y or M if you have a PCI sound card utilizing the S3
14255 SonicVibes chipset. To find out if your sound card uses a
14256 SonicVibes chip without removing your computer's cover, use
14257 lspci -n and look for the PCI ID 5333:CA00. This driver
14258 differs slightly from OSS/Free, so PLEASE READ
14259 Documentation/sound/sonicvibes.
14261 Trident 4DWave DX/NX, SiS 7018 or ALi 5451 PCI Audio Core
14262 CONFIG_SOUND_TRIDENT
14263 Say Y or M if you have a PCI sound card utilizing the Trident
14264 4DWave-DX/NX chipset or your mother board chipset has SiS 7018
14265 or ALi 5451 built-in. The SiS 7018 PCI Audio Core is embedded
14266 in SiS960 Super South Bridge and SiS540/630 Single Chipset.
14267 The ALi 5451 PCI Audio Core is embedded in ALi M1535, M1535D,
14268 M1535+ or M1535D+ South Bridge.
14270 Use lspci -n to find out if your sound card or chipset uses
14271 Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands
14272 for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018. PCI ID
14273 10B9:5451 stands for ALi5451.
14275 This driver differs slightly from OSS/Free, so PLEASE READ the
14276 comments at the top of driver/sound/trident.c
14278 Rockwell WaveArtist
14279 CONFIG_SOUND_WAVEARTIST
14280 Say Y here to include support for the Rockwell WaveArtist sound
14281 system. This driver is mainly for the NetWinder.
14283 VIA 82Cxxx Audio Codec
14284 CONFIG_SOUND_VIA82CXXX
14285 Say Y here to include support for the audio codec found on VIA
14286 82Cxxx-based chips. Typically these are built into a motherboard. DO
14287 NOT select Sound Blaster or Adlib with this driver, unless you have
14288 a Sound Blaster or Adlib card in addition to your VIA audio chip.
14290 NeoMagic 256AV/256ZX sound chipsets
14292 Say M here to include audio support for the NeoMagic 256AV/256ZX
14293 chipsets. These are the audio chipsets found in the Sony
14294 Z505S/SX/DX, some Sony F-series, and the Dell Latitude CPi and CPt
14295 laptops. It includes support for an AC97-compatible mixer and an
14296 apparently proprietary sound engine.
14298 See Documentation/sound/NM256 for further information.
14300 ESS Maestro sound chipsets
14301 CONFIG_SOUND_MAESTRO
14302 Say Y or M if you have a sound system driven by ESS's Maestro line
14303 of PCI sound chips. These include the Maestro 1, Maestro 2, and
14304 Maestro 2E. See Documentation/sound/Maestro for more details.
14306 Are you using a crosscompiler
14307 CONFIG_CROSSCOMPILE
14308 Say Y here if you are compiling the kernel on a different
14309 architecture than the one it is intended to run on.
14311 Kernel support for Linux/MIPS 32-bit binary compatibility
14312 CONFIG_MIPS32_COMPAT
14313 Select this option if you want Linux/MIPS 32-bit binary
14314 compatibility. Since all software available for Linux/MIPS is
14315 currently 32-bit you should say Y here.
14317 Build fp exception handler module
14318 CONFIG_MIPS_FPE_MODULE
14319 Build the floating point exception handler module. This option is
14320 only useful for people working on the floating point exception
14321 handler. If you don't, say N.
14323 Remote GDB kernel debugging
14324 CONFIG_REMOTE_DEBUG
14325 If you say Y here, it will be possible to remotely debug the MIPS
14326 kernel using gdb. This enlarges your kernel image disk size by
14327 several megabytes and requires a machine with more than 16 MB,
14328 better 32 MB RAM to avoid excessive linking time. This is only
14329 useful for kernel hackers. If unsure, say N.
14331 Magic System Request Key support
14333 If you say Y here, you will have some control over the system even
14334 if the system crashes for example during kernel debugging (e.g., you
14335 will be able to flush the buffer cache to disk, reboot the system
14336 immediately or dump some status information). This is accomplished
14337 by pressing various keys while holding SysRq (Alt+PrintScreen). It
14338 also works on a serial console (on PC hardware at least), if you
14339 send a BREAK and then within 5 seconds a command keypress. The
14340 keys are documented in Documentation/sysrq.txt. Don't say Y unless
14341 you really know what this hack does.
14345 ISDN ("Integrated Services Digital Networks", called RNIS in France)
14346 is a special type of fully digital telephone service; it's mostly
14347 used to connect to your Internet service provider (with SLIP or
14348 PPP). The main advantage is that the speed is higher than ordinary
14349 modem/telephone connections, and that you can have voice
14350 conversations while downloading stuff. It only works if your
14351 computer is equipped with an ISDN card and both you and your service
14352 provider purchased an ISDN line from the phone company. For details,
14353 read http://alumni.caltech.edu/~dank/isdn/ on the WWW.
14355 This driver allows you to use an ISDN-card for networking
14356 connections and as dialin/out device. The isdn-tty's have a built in
14357 AT-compatible modem emulator. Network devices support autodial,
14358 channel-bundling, callback and caller-authentication without having
14359 a daemon running. A reduced T.70 protocol is supported with tty's
14360 suitable for German BTX. On D-Channel, the protocols EDSS1
14361 (Euro-ISDN) and 1TR6 (German style) are supported. See
14362 Documentation/isdn/README for more information.
14364 If you want to compile the ISDN code as a module ( = code which can
14365 be inserted in and removed from the running kernel whenever you
14366 want), say M here and read Documentation/modules.txt. The module
14367 will be called isdn.o. If unsure, say N.
14369 Support synchronous PPP
14371 Over digital connections such as ISDN, there is no need to
14372 synchronize sender and recipient's clocks with start and stop bits
14373 as is done over analog telephone lines. Instead, one can use
14374 "synchronous PPP". Saying Y here will include this protocol. This
14375 protocol is used by Cisco and Sun for example. So you want to say Y
14376 here if the other end of your ISDN connection supports it. You will
14377 need a special version of pppd (called ipppd) for using this
14378 feature. See Documentation/isdn/README.syncppp and
14379 Documentation/isdn/syncPPP.FAQ for more information.
14381 Support generic MP (RFC 1717)
14383 With synchronous PPP enabled, it is possible to increase throughput
14384 by bundling several ISDN-connections, using this protocol. See
14385 Documentation/isdn/README.syncppp for more information.
14387 Use VJ-compression with synchronous PPP
14389 This enables Van Jacobson header compression for synchronous PPP.
14390 Say Y if the other end of the connection supports it.
14392 Support audio via ISDN
14394 If you say Y here, the modem-emulator will support a subset of the
14395 EIA Class 8 Voice commands. Using a getty with voice-support
14396 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
14397 with the ISDN utility package for example), you will be able to use
14398 your Linux box as an ISDN-answering machine. Of course, this must be
14399 supported by the lowlevel driver also. Currently, the HiSax driver
14400 is the only voice-supporting driver. See
14401 Documentation/isdn/README.audio for more information.
14403 X.25 PLP on top of ISDN
14405 This feature provides the X.25 protocol over ISDN connections.
14406 See Documentation/isdn/README.x25 for more information
14407 if you are thinking about using this.
14409 ISDN diversion services support
14410 CONFIG_ISDN_DIVERSION
14411 This option allows you to use some supplementary diversion
14412 services in conjunction with the HiSax driver on an EURO/DSS1
14415 Supported options are CD (call deflection), CFU (Call forward
14416 unconditional), CFB (Call forward when busy) and CFNR (call forward
14417 not reachable). Additionally the actual CFU, CFB and CFNR state may
14420 The use of CFU, CFB, CFNR and interrogation may be limited to some
14421 countries. The keypad protocol is still not implemented. CD should
14422 work in all countries if the service has been subscribed to.
14424 Please read the file Documentation/isdn/README.diversion.
14426 ICN 2B and 4B support
14427 CONFIG_ISDN_DRV_ICN
14428 This enables support for two kinds of ISDN-cards made by a German
14429 company called ICN. 2B is the standard version for a single ISDN
14430 line with two B-channels, 4B supports two ISDN lines. For running
14431 this card, additional firmware is necessary, which has to be
14432 downloaded into the card using a utility which is distributed
14433 separately. See Documentation/isdn/README and README.icn for more
14436 If you want to compile this as a module ( = code which can be
14437 inserted in and removed from the running kernel whenever you want),
14438 say M here and read Documentation/modules.txt. The module will be
14442 CONFIG_ISDN_DRV_LOOP
14443 This driver provides a virtual ISDN card. Its primary purpose is
14444 testing of linklevel features or configuration without getting
14445 charged by your service-provider for lots of phone calls.
14446 You need will need the loopctrl utility from the latest isdn4k-utils
14447 package to set up this driver.
14449 HiSax SiemensChipSet driver support
14450 CONFIG_ISDN_DRV_HISAX
14451 This is a driver supporting the Siemens chipset on various
14452 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
14453 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
14456 HiSax is just the name of this driver, not the name of any hardware.
14458 If you have a card with such a chipset, you should say Y here and
14459 also to the configuration option of the driver for your particular
14462 If you want to compile this as a module ( = code which can be
14463 inserted in and removed from the running kernel whenever you want),
14464 say M here and read Documentation/modules.txt. The module will be
14465 called hisax.o. See Documentation/isdn/README.HiSax for more
14466 information on using this driver.
14468 HiSax Support for EURO/DSS1
14470 Say Y or N according to the D-channel protocol which your local
14471 telephone service company provides.
14473 The call control protocol E-DSS1 is used in most European countries.
14474 If unsure, say yes.
14476 Support for german charge info
14478 If you want that the HiSax hardware driver sends messages to the
14479 upper level of the isdn code on each AOCD (Advice Of Charge, During
14480 the call -- transmission of the fee information during a call) and
14481 on each AOCE (Advice Of Charge, at the End of the call --
14482 transmission of fee information at the end of the call), say Y here.
14483 This works only in Germany.
14485 Disable sending complete
14486 CONFIG_HISAX_NO_SENDCOMPLETE
14487 If you have trouble with some ugly exchanges or you live in
14488 Australia select this option.
14490 Disable sending low layer compatibility
14491 CONFIG_HISAX_NO_LLC
14492 If you have trouble with some ugly exchanges try to select this
14495 Disable keypad protocol option
14496 CONFIG_HISAX_NO_KEYPAD
14497 If you like to send special dial strings including * or # without
14498 using the keypad protocol, select this option.
14500 HiSax Support for German 1TR6
14502 Say Y or N according to the D-channel protocol which your local
14503 telephone service company provides.
14505 1TR6 is an old call control protocol which was used in Germany
14506 before E-DSS1 was established. Nowadays, all new lines in Germany
14509 HiSax Support for US NI1
14511 Enable this if you like to use ISDN in US on a NI1 basic rate interface.
14515 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
14516 and many compatibles.
14518 See Documentation/isdn/README.HiSax on how to configure it using the
14519 different cards, a different D-channel protocol, or non-standard
14520 IRQ/port/shmem settings.
14522 Teles 16.3 or PNP or PCMCIA
14524 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
14525 Teles/Creatix PnP and the Teles PCMCIA.
14527 See Documentation/isdn/README.HiSax on how to configure it using the
14528 different cards, a different D-channel protocol, or non-standard
14532 CONFIG_HISAX_TELESPCI
14533 This enables HiSax support for the Teles PCI.
14534 See Documentation/isdn/README.HiSax on how to configure it.
14538 This enables HiSax support for the Teles/Creatix parallel port
14539 S0BOX. See Documentation/isdn/README.HiSax on how to configure it.
14542 CONFIG_HISAX_AVM_A1
14543 This enables HiSax support for the AVM A1 (aka "Fritz").
14545 See Documentation/isdn/README.HiSax on how to configure it using the
14546 different cards, a different D-channel protocol, or non-standard
14549 AVM PnP/PCI (Fritz!PNP/PCI)
14550 CONFIG_HISAX_FRITZPCI
14551 This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI".
14552 See Documentation/isdn/README.HiSax on how to configure it.
14554 AVM A1 PCMCIA (Fritz)
14555 CONFIG_HISAX_AVM_A1_PCMCIA
14556 This enables HiSax support for the AVM A1 "Fritz!PCMCIA").
14557 See Documentation/isdn/README.HiSax on how to configure it.
14561 This enables HiSax support for the Elsa Mircolink ISA cards, for the
14562 Elsa Quickstep series cards and Elsa PCMCIA.
14564 See Documentation/isdn/README.HiSax on how to configure it using the
14565 different cards, a different D-channel protocol, or non-standard
14568 ITK ix1-micro Revision 2
14569 CONFIG_HISAX_IX1MICROR2
14570 This enables HiSax support for the ITK ix1-micro Revision 2 card.
14572 See Documentation/isdn/README.HiSax on how to configure it using the
14573 different cards, a different D-channel protocol, or non-standard
14576 Eicon.Diehl Diva cards
14577 CONFIG_HISAX_DIEHLDIVA
14578 This enables HiSax support for the Eicon.Diehl Diva none PRO
14579 versions passive ISDN cards.
14581 See Documentation/isdn/README.HiSax on how to configure it using the
14582 different cards, a different D-channel protocol, or non-standard
14586 CONFIG_HISAX_ASUSCOM
14587 This enables HiSax support for the AsusCom and their OEM versions
14588 passive ISDN ISA cards.
14590 See Documentation/isdn/README.HiSax on how to configure it using the
14591 different cards, a different D-channel protocol, or non-standard
14595 CONFIG_HISAX_TELEINT
14596 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
14598 See Documentation/isdn/README.HiSax on how to configure it using the
14599 different cards, a different D-channel protocol, or non-standard
14604 This enables HiSax support for the HFC-S 2BDS0 based cards, like
14607 See Documentation/isdn/README.HiSax on how to configure it using the
14608 different cards, a different D-channel protocol, or non-standard
14612 CONFIG_HISAX_SEDLBAUER
14613 This enables HiSax support for the Sedlbauer passive ISDN cards.
14615 See Documentation/isdn/README.HiSax on how to configure it using the
14616 different cards, a different D-channel protocol, or non-standard
14619 USR Sportster internal TA
14620 CONFIG_HISAX_SPORTSTER
14621 This enables HiSax support for the USR Sportster internal TA card.
14623 See Documentation/isdn/README.HiSax on how to configure it using a
14624 different D-channel protocol, or non-standard IRQ/port settings.
14628 This enables HiSax support for the ITH MIC card.
14630 See Documentation/isdn/README.HiSax on how to configure it using a
14631 different D-channel protocol, or non-standard IRQ/port settings.
14634 CONFIG_HISAX_NETJET
14635 This enables HiSax support for the NetJet from Traverse
14638 See Documentation/isdn/README.HiSax on how to configure it using a
14639 different D-channel protocol, or non-standard IRQ/port settings.
14642 CONFIG_HISAX_NETJET_U
14643 This enables HiSax support for the Netspider U interface ISDN card from
14644 Traverse Technologies.
14645 See Documentation/isdn/README.HiSax on how to configure it using a
14646 different D-channel protocol, or non-standard IRQ/port settings.
14650 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
14652 See Documentation/isdn/README.HiSax on how to configure it using a
14653 different D-channel protocol, or non-standard IRQ/port settings.
14655 Siemens I-Surf card
14657 This enables HiSax support for the Siemens I-Talk/I-Surf card with
14659 See Documentation/isdn/README.HiSax on how to configure it using a
14660 different D-channel protocol, or non-standard IRQ/port settings.
14663 CONFIG_HISAX_HSTSAPHIR
14664 This enables HiSax support for the HST Saphir card.
14666 See Documentation/isdn/README.HiSax on how to configure it using a
14667 different D-channel protocol, or non-standard IRQ/port settings.
14670 CONFIG_HISAX_BKM_A4T
14671 This enables HiSax support for the Telekom A4T card.
14673 See Documentation/isdn/README.HiSax on how to configure it using a
14674 different D-channel protocol, or non-standard IRQ/port settings.
14677 CONFIG_HISAX_SCT_QUADRO
14678 This enables HiSax support for the Scitel Quadro card.
14680 See Documentation/isdn/README.HiSax on how to configure it using a
14681 different D-channel protocol, or non-standard IRQ/port settings.
14685 This enables HiSax support for the Gazel cards.
14687 See Documentation/isdn/README.HiSax on how to configure it using a
14688 different D-channel protocol, or non-standard IRQ/port settings.
14691 CONFIG_HISAX_HFC_PCI
14692 This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
14694 For more informations see under Documentation/isdn/README.hfc-pci.
14696 Winbond W6692 based cards
14698 This enables HiSax support for Winbond W6692 based PCI ISDN cards.
14700 See Documentation/isdn/README.HiSax on how to configure it using a
14701 different D-channel protocol, or non-standard IRQ/port settings.
14703 HFC-S+, HFC-SP, HFC-PCMCIA cards (EXPERIMENTAL)
14704 CONFIG_HISAX_HFC_SX
14705 This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA
14706 cards. This code is not finished yet.
14708 Am7930 (EXPERIMENTAL)
14709 CONFIG_HISAX_AMD7930
14710 This enables HiSax support for the AMD7930 chips on some SPARCs.
14711 This code is not finished yet.
14714 CONFIG_ISDN_DRV_PCBIT
14715 This enables support for the PCBIT ISDN-card. This card is
14716 manufactured in Portugal by Octal. For running this card, additional
14717 firmware is necessary, which has to be downloaded into the card
14718 using a utility which is distributed separately. See
14719 Documentation/isdn/README and Documentation/isdn/README.pcbit for
14722 If you want to compile this as a module ( = code which can be
14723 inserted in and removed from the running kernel whenever you want),
14724 say M here and read Documentation/modules.txt. The module will be
14727 Spellcaster support (EXPERIMENTAL)
14729 This enables support for the Spellcaster BRI ISDN boards. This
14730 driver currently builds only in a modularized version ( = code which
14731 can be inserted in and removed from the running kernel whenever you
14732 want, details in Documentation/modules.txt); the module will be
14733 called sc.o. See Documentation/isdn/README.sc and
14734 http://www.spellcast.com for more information.
14736 Eicon active card support
14737 CONFIG_ISDN_DRV_EICON
14738 Say Y here if you have an Eicon active ISDN card. In order to use
14739 this card, additional firmware is necessary, which has to be loaded
14740 into the card using the eiconctrl utility which is part of the
14741 latest isdn4k-utils package. Please read the file
14742 Documentation/isdn/README.eicon for more information.
14744 Eicon Diva Server card support
14745 CONFIG_ISDN_DRV_EICON_PCI
14746 Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN card.
14747 Please read Documentation/isdn/README.eicon for more information.
14749 Eicon old-type card support
14750 CONFIG_ISDN_DRV_EICON_ISA
14751 Say Y here if you have an old-type Eicon active ISDN card. In order
14752 to use this card, additional firmware is necessary, which has to be
14753 loaded into the card using the eiconctrl utility which is part of
14754 the latest isdn4k-utils package. Please read the file
14755 Documentation/isdn/README.eicon for more information.
14757 Eicon driver type standalone
14758 CONFIG_ISDN_DRV_EICON_STANDALONE
14759 Enable this option if you want the eicon driver as standalone
14760 version with no interface to the ISDN4Linux isdn module. If you
14761 say Y here, the eicon module only supports the Diva Server PCI
14762 cards and will provide its own IDI interface. You should say N
14765 Support AT-Fax Class 1 and 2 commands
14766 CONFIG_ISDN_TTY_FAX
14767 If you say Y here, the modem-emulator will support a subset of the
14768 Fax Class 1 and 2 commands. Using a getty with fax-support
14769 (mgetty+sendfax, hylafax), you will be able to use your Linux box as
14770 an ISDN-fax-machine. This must be supported by the lowlevel driver
14771 also. See Documentation/isdn/README.fax for more information.
14775 This provides the CAPI (Common ISDN Application Programming
14776 Interface, a standard making it easy for programs to access ISDN
14777 hardware, see http://www.capi.org/ . This is needed for AVM's set of
14778 active ISDN controllers like B1, T1, M1.
14780 This code is also available as a module ( = code which can be
14781 inserted in and removed from the running kernel whenever you want).
14782 The modules will be called capi.o and kernelcapi.o. If you want to
14783 compile it as a module, say M here and read
14784 Documentation/modules.txt.
14787 CONFIG_ISDN_DRV_AVMB1_B1ISA
14788 Enable support for the ISA version of the AVM B1 card.
14791 CONFIG_ISDN_DRV_AVMB1_B1PCI
14792 Enable support for the PCI version of the AVM B1 card.
14794 AVM B1 PCI V4 support
14795 CONFIG_ISDN_DRV_AVMB1_B1PCIV4
14796 Enable support for the V4 version of AVM B1 PCI card.
14798 AVM T1/T1-B ISA support
14799 CONFIG_ISDN_DRV_AVMB1_T1ISA
14800 Enable support for the AVM T1 T1B card.
14801 Note: This is a PRI card and handle 30 B-channels.
14803 AVM B1/M1/M2 PCMCIA support
14804 CONFIG_ISDN_DRV_AVMB1_B1PCMCIA
14805 Enable support for the PCMCIA version of the AVM B1 card.
14807 AVM T1/T1-B PCI support
14808 CONFIG_ISDN_DRV_AVMB1_T1PCI
14809 Enable support for the AVM T1 T1B card.
14810 Note: This is a PRI card and handle 30 B-channels.
14813 CONFIG_ISDN_DRV_AVMB1_C4
14814 Enable support for the AVM C4 PCI card.
14815 This card handle 4 BRI ISDN lines (8 channels).
14817 Verbose reason code reporting (kernel size +=7K)
14818 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
14819 If you say Y here, the AVM B1 driver will give verbose reasons for
14820 disconnecting. This will increase the size of the kernel by 7 KB. If
14823 IBM Active 2000 support (EXPERIMENTAL)
14824 CONFIG_ISDN_DRV_ACT2000
14825 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
14826 this card, additional firmware is necessary, which has to be loaded
14827 into the card using a utility which is part of the latest
14828 isdn4k-utils package. Please read the file
14829 Documentation/isdn/README.act2000 for more information.
14831 Hypercope HYSDN cards (Champ, Ergo, Metro) support (module)
14833 Say Y here if you have one of Hypercope's active PCI ISDN cards
14834 Champ, Ergo and Metro. You will then get a module called hysdn.o.
14835 Please read the file Documentation/isdn/README.hysdn for more
14838 HYSDN CAPI 2.0 support
14840 Say Y here if you like to use Hypercope's CAPI 2.0 interface
14842 Support for Sun4 architecture
14844 Say Y here if, and only if, your machine is a Sun4. Note that
14845 a kernel compiled with this option will run only on Sun4.
14846 (And the current version will probably work only on sun4/330.)
14848 SPARC ESP SCSI support
14850 This is the driver for the Sun ESP SCSI host adapter. The ESP
14851 chipset is present in most SPARC SBUS-based computers.
14853 This support is also available as a module called esp.o ( = code
14854 which can be inserted in and removed from the running kernel
14855 whenever you want). If you want to compile it as a module, say M
14856 here and read Documentation/modules.txt.
14858 PTI Qlogic, ISP Driver
14859 CONFIG_SCSI_QLOGICPTI
14860 This driver supports SBUS SCSI controllers from PTI or QLogic. These
14861 controllers are known under Solaris as qpti and in the openprom as
14862 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
14863 driven by a different driver.
14865 This support is also available as a module called qlogicpti.o ( =
14866 code which can be inserted in and removed from the running kernel
14867 whenever you want). If you want to compile it as a module, say M
14868 here and read Documentation/modules.txt.
14870 SPARC /dev/openprom compatibility driver (EXPERIMENTAL)
14871 CONFIG_SUN_OPENPROMIO
14872 This driver provides user programs with an interface to the SPARC
14873 PROM device tree. The driver implements a SunOS-compatible
14874 interface and a NetBSD-compatible interface.
14876 If you want to compile this as a module ( = code which can be
14877 inserted in and removed from the running kernel whenever you want),
14878 say M and read Documentation/modules.txt. If unsure, say Y.
14880 Openprom tree appears in /proc/openprom
14881 CONFIG_SUN_OPENPROMFS
14882 If you say Y, the OpenPROM device tree will be available as a
14883 virtual file system, which you can mount to /proc/openprom by "mount
14884 -t openpromfs none /proc/openprom".
14886 If you want to compile the /proc/openprom support as a module ( =
14887 code which can be inserted in and removed from the running kernel
14888 whenever you want), say M here and read Documentation/modules.txt.
14889 The module will be called openpromfs.o. If unsure, say M.
14891 Kernel support for Linux/Sparc 32bit binary compatibility
14892 CONFIG_SPARC32_COMPAT
14893 This allows you to run 32-bit binaries on your Ultra.
14894 Everybody wants this; say Y.
14896 Kernel support for 32-bit ELF binaries
14897 CONFIG_BINFMT_ELF32
14898 This allows you to run 32-bit Linux/ELF binaries on your Ultra.
14899 Everybody wants this; say Y.
14901 Kernel support for 32-bit (ie. SunOS) a.out binaries
14902 CONFIG_BINFMT_AOUT32
14903 This allows you to run 32-bit a.out format binaries on your Ultra.
14904 If you want to run SunOS binaries (see SunOS binary emulation below)
14905 or other a.out binaries, say Y. If unsure, say N.
14907 SunOS binary emulation
14909 This allows you to run most SunOS binaries. If you want to do this,
14910 say Y here and place appropriate files in /usr/gnemul/sunos. See
14911 http://www.ultralinux.org/faq.html for more information. If you want
14912 to run SunOS binaries on an Ultra you must also say Y to "Kernel
14913 support for 32-bit a.out binaries" above.
14915 Mostek real time clock support
14916 CONFIG_SUN_MOSTEK_RTC
14917 The Mostek RTC chip is used on all known Sun computers except
14918 some JavaStations. For a JavaStation you need to say Y both here
14919 and to "Enhanced Real Time Clock Support".
14921 Say Y here unless you are building a special purpose kernel.
14923 OBP Flash Device support
14925 The OpenBoot PROM on Ultra systems is flashable. If you want to be
14926 able to upgrade the OBP firmware, say Y here.
14928 JavaStation OS Flash SIMM
14930 If you say Y here, you will be able to boot from your JavaStation's
14933 Siemens SAB82532 serial support
14935 This driver supports the serial ports on newer (PCI) Ultra systems.
14936 Say Y if you want to be able to use your serial ports.
14938 Aurora Multiboard 1600se (EXPERIMENTAL)
14940 The Aurora Multiboard is a multi-port high-speed serial controller.
14941 If you have one of these, say Y.
14943 Audio support (EXPERIMENTAL)
14945 This driver provides support for the build-in sound devices on most
14946 Sun machines. If you want to be able to use this, select this option
14947 and one or more of the lowlevel drivers below. See
14948 http://www.dementia.org/~shadow/sparcaudio.html for more
14951 AMD7930 Lowlevel Driver
14952 CONFIG_SPARCAUDIO_AMD7930
14953 This driver supports the AMD 7930 chip found on sun4c, 4/6xx, and
14954 SparcClassic systems.
14956 CS4231 Lowlevel Driver
14957 CONFIG_SPARCAUDIO_CS4231
14958 This driver supports the Crystal Semiconductor CS4231 chip found on
14959 the SS4, SS5, and Ultras.
14961 DBRI Lowlevel Driver
14962 CONFIG_SPARCAUDIO_DBRI
14963 This driver supports the DBRI audio interface found on the SS10,
14964 SS20, Sparcbook 3, and Voyager systems.
14966 Dummy lowlevel Driver
14967 CONFIG_SPARCAUDIO_DUMMY
14968 This is a pseudo-driver used for debugging and testing the
14969 sparcaudio subsystem. Say N unless you want to work on this
14972 Sparc hardware (EXPERIMENTAL)
14973 CONFIG_PARPORT_SUNBPP
14974 This driver provides support for the bidirectional parallel port
14975 found on many Sun machines. Note that many of the newer Ultras
14976 actually have pc style hardware instead.
14979 # m68k-specific kernel options
14980 # Documented by Chris Lawrence <quango@themall.net> et al.
14984 This option enables support for the Amiga series of computers. If
14985 you plan to use this kernel on an Amiga, say Y here and browse the
14986 material available in Documentation/m68k; otherwise say N.
14990 This option enables support for the 68000-based Atari series of
14991 computers (including the TT, Falcon and Medusa). If you plan to use
14992 this kernel on an Atari, say Y here and browse the material
14993 available in Documentation/m68k; otherwise say N.
14997 This option enables support for the Hades Atari clone. If you plan
14998 to use this kernel on a Hades, say Y here; otherwise say N.
15002 This option enables support for the Apple Macintosh series of
15003 computers (yes, there is experimental support now, at least for part
15006 Say N unless you're willing to code the remaining necessary support.
15011 This option enables support for the HP9000/300 series of
15012 workstations. Support for these machines is still very experimental.
15013 If you plan to try to use the kernel on such a machine say Y here.
15014 Everybody else says N.
15018 This option enables support for the Sun 3x series of workstations.
15019 Be warned that this support is very experimental. You will also want
15020 to say Y to 68020 support and N to the other processors below.
15022 If you don't want to compile a kernel for a Sun 3x, say N.
15026 If you anticipate running this kernel on a computer with a MC68020
15027 processor, say Y. Otherwise, say N. Note that the 68020 requires a
15028 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
15029 Sun 3, which provides its own version.
15033 If you anticipate running this kernel on a computer with a MC68030
15034 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
15035 work, as it does not include an MMU (Memory Management Unit).
15039 If you anticipate running this kernel on a computer with a MC68LC040
15040 or MC68040 processor, say Y. Otherwise, say N. Note that an
15041 MC68EC040 will not work, as it does not include an MMU (Memory
15046 If you anticipate running this kernel on a computer with a MC68060
15047 processor, say Y. Otherwise, say N.
15049 Math emulation support (EXPERIMENTAL)
15051 At some point in the future, this will cause floating-point math
15052 instructions to be emulated by the kernel on machines that lack a
15053 floating-point math coprocessor. Thrill-seekers and chronically
15054 sleep-deprived psychotic hacker types can say Y now, everyone else
15055 should probably wait a while.
15057 Math emulation only kernel
15058 CONFIG_M68KFPU_EMU_ONLY
15059 This option prevents any floating-point instructions from being
15060 compiled into the kernel, thereby the kernel doesn't save any
15061 floating point context anymore during task switches, so this
15062 kernel will only be usable on machines without a floating-point
15063 math coprocessor. This makes the kernel a bit faster as no tests
15064 needs to be executed whether a floating-point instruction in the
15065 kernel should be executed or not.
15067 Math emulation extra precision
15068 CONFIG_M68KFPU_EMU_EXTRAPREC
15069 The fpu uses normally a few bit more during calculations for
15070 correct rounding, the emulator can (often) do the same but this
15071 extra calculation can cost quite some time, so you can disable
15072 it here. The emulator will then "only" calculate with a 64 bit
15073 mantissa and round slightly incorrect, what is more then enough
15076 Advanced configuration options
15078 This gives you access to some advanced options for the CPU. The
15079 defaults should be fine for most users, but these options may make
15080 it possible for you to improve performance somewhat if you know what
15083 Note that the answer to this question won't directly affect the
15084 kernel: saying N will just cause this configure script to skip all
15085 the questions about these options.
15087 Most users should say N to this question.
15089 Use read-modify-write instructions
15091 This allows to use certain instructions that work with indivisible
15092 read-modify-write bus cycles. While this is faster than the
15093 workaround of disabling interrupts, it can conflict with DMA
15094 ( = direct memory access) on many Amiga systems, and it is also said
15095 to destabilize other machines. It is very likely that this will
15096 cause serious problems on any Amiga or Atari Medusa if set. The only
15097 configuration where it should work are 68030-based Ataris, where it
15098 apparently improves performance. But you've been warned! Unless you
15099 really know what you are doing, say N. Try Y only if you're quite
15102 Amiga AutoConfig Identification
15104 This enables support for automatic identification of Amiga expansion
15105 cards that obey the AutoConfig(tm) specification.
15106 Say Y if you want your expansion cards to be identified on bootup;
15107 it will enlarge your kernel by about 10 KB. The identification
15108 information is then also available through /proc/zorro (say Y to
15109 "/proc file system support"!). Read Documentation/zorro.txt for more
15112 Note that even if you say N here, you can still use your expansion
15113 cards. If in doubt, say Y.
15115 Amiga 1200/600 PCMCIA support (EXPERIMENTAL)
15116 CONFIG_AMIGA_PCMCIA
15117 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
15118 600. If you intend to use pcmcia cards say Y; otherwise say N.
15120 Amiga Zorro II ramdisk support
15122 This enables support for using Chip RAM and Zorro II RAM as a
15123 ramdisk or as a swap partition. Say Y if you want to include this
15124 driver in the kernel. This driver is also available as a module
15125 ( = code which can be inserted in and removed from the running
15126 kernel whenever you want). The module is called z2ram.o. If you want
15127 to compile it as a module, say M here and read
15128 Documentation/modules.txt.
15130 Atari ST-RAM swap support
15132 This enables support for using (parts of) ST-RAM as swap space,
15133 instead of as normal system memory. This can first enhance system
15134 performance if you have lots of alternate RAM (compared to the size
15135 of ST-RAM), because executable code always will reside in faster
15136 memory. ST-RAM will remain as ultra-fast swap space. On the other
15137 hand, it allows much improved dynamic allocations of ST-RAM buffers
15138 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
15139 sound). The probability that such allocations at module load time
15140 fail is drastically reduced.
15144 This enables support for the Atari ACSI interface. The driver
15145 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
15146 be switched to that mode. Due to the ACSI command format, only disks
15147 up to 1 GB are supported. Special support for certain ACSI to SCSI
15148 adapters, which could relax that, isn't included yet. The ACSI
15149 driver is also the basis for certain other drivers for devices
15150 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
15151 Ethernet, and PAMsNet Ethernet. If you want to use one of these
15152 devices, you need ACSI support, too.
15154 This driver is also available as a module ( = code which can be
15155 inserted in and removed from the running kernel whenever you want).
15156 The module will be called acsi.o.
15158 Probe all LUNs on each ACSI device
15159 CONFIG_ACSI_MULTI_LUN
15160 If you have a ACSI device that supports more than one LUN (Logical
15161 Unit Number), e.g. a CD jukebox, you should say Y here so that all
15162 will be found by the ACSI driver. An ACSI device with multiple LUNs
15163 acts logically like multiple ACSI devices. The vast majority of ACSI
15164 devices have only one LUN, and so most people can say N here and
15165 should in fact do so, because it is safer.
15167 Atari SLM laser printer support
15169 If you have an Atari SLM laser printer, say Y to include support for
15170 it in the kernel. Otherwise, say N. This driver is also available as
15171 a module ( = code which can be inserted in and removed from the
15172 running kernel whenever you want). The module will be called
15173 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
15174 problems due to that fact!
15176 A3000 WD33C93A support
15178 If you have an Amiga 3000 and have SCSI devices connected to the
15179 built-in SCSI controller, say Y. Otherwise, say N. This driver is
15180 also available as a module ( = code which can be inserted in and
15181 removed from the running kernel whenever you want). The module is
15182 called wd33c93.o. If you want to compile it as a module, say M here
15183 and read Documentation/modules.txt.
15185 A2091 WD33C93A support
15187 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
15188 say N. This driver is also available as a module ( = code which can
15189 be inserted in and removed from the running kernel whenever you
15190 want). The module is called wd33c93.o. If you want to compile it as
15191 a module, say M here and read Documentation/modules.txt.
15193 GVP Series II WD33C93A support
15195 If you have a Great Valley Products Series II SCSI controller,
15196 answer Y. Also say Y if you have a later model of GVP SCSI
15197 controller (such as the GVP A4008 or a Combo board). Otherwise,
15198 answer N. This driver does NOT work for the T-Rex series of
15199 accelerators from TekMagic and GVP-M.
15201 This driver is also available as a module ( = code which can be
15202 inserted in and removed from the running kernel whenever you
15203 want). The module will be called gvp11.o. If you want to compile it
15204 as a module, say M here and read Documentation/modules.txt.
15206 Cyberstorm SCSI support
15207 CONFIG_CYBERSTORM_SCSI
15208 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
15209 accelerator board and the optional Cyberstorm SCSI controller,
15210 answer Y. Otherwise, say N.
15212 Cyberstorm II SCSI support
15213 CONFIG_CYBERSTORMII_SCSI
15214 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
15215 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
15218 Blizzard 2060 SCSI support (EXPERIMENTAL)
15219 CONFIG_BLZ2060_SCSI
15220 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
15221 and want to use the onboard SCSI controller, say Y. Otherwise,
15224 Blizzard 1230IV/1260 SCSI support
15225 CONFIG_BLZ1230_SCSI
15226 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
15227 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
15230 Blizzard PowerUP 603e+ SCSI support
15231 CONFIG_BLZ603EPLUS_SCSI
15232 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
15233 accelerator, say Y. Otherwise, say N.
15235 Fastlane SCSI support
15236 CONFIG_FASTLANE_SCSI
15237 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
15238 one in the near future, say Y to this question. Otherwise, say N.
15240 Atari native SCSI support
15242 If you have an Atari with built-in NCR5380 SCSI controller (TT,
15243 Falcon, ...) say Y to get it supported. Of course also, if you have
15244 a compatible SCSI controller (e.g. for Medusa). This driver is also
15245 available as a module ( = code which can be inserted in and removed
15246 from the running kernel whenever you want). The module is called
15247 atari_scsi.o. If you want to compile it as a module, say M here and
15248 read Documentation/modules.txt. This driver supports both styles of
15249 NCR integration into the system: the TT style (separate DMA), and
15250 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
15251 other schemes, like in the Hades (without DMA).
15253 Long delays for Toshiba CD-ROMs
15254 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
15255 This option increases the delay after a SCSI arbitration to
15256 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
15257 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
15258 would impact performance a bit, so say N.
15260 Hades SCSI DMA emulator
15262 This option enables code which emulates the TT SCSI DMA chip on the
15263 Hades. This increases the SCSI transfer rates at least ten times
15264 compared to PIO transfers.
15268 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
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). The module is called ariadne.o. If you want to compile it as
15274 a module, say M here and read Documentation/modules.txt.
15278 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
15281 This driver is also available as a module ( = code which can be
15282 inserted in and removed from the running kernel whenever you
15283 want). The module is called ariadne2.o. If you want to compile it as
15284 a module, say M here and read Documentation/modules.txt.
15288 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
15291 This driver is also available as a module ( = code which can be
15292 inserted in and removed from the running kernel whenever you
15293 want). The module is called a2065.o. If you want to compile it as a
15294 module, say M here and read Documentation/modules.txt.
15298 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
15300 This driver is also available as a module ( = code which can be
15301 inserted in and removed from the running kernel whenever you
15302 want). The module is called hydra.o. If you want to compile it as a
15303 module, say M here and read Documentation/modules.txt.
15305 Pcmcia NE2000 compatible support
15307 If you have a pcmcia ne2000 compatible adapter, say Y. Otherwise,
15310 This driver is also available as a module ( = code which can be
15311 inserted in and removed from the running kernel whenever you
15312 want). The module is called apne.o. If you want to compile it as a
15313 module, say M here and read Documentation/modules.txt.
15315 Atari Lance support
15317 Say Y to include support for several Atari Ethernet adapters based
15318 on the AMD Lance chipset: RieblCard (with or without battery), or
15319 PAMCard VME (also the version by Rhotron, with different addresses).
15322 CONFIG_ATARI_BIONET
15323 Say Y to include support for BioData's BioNet-100 Ethernet adapter
15324 for the ACSI port. The driver works (has to work...) with a polled
15325 I/O scheme, so it's rather slow :-(
15328 CONFIG_ATARI_PAMSNET
15329 Say Y to include support for the PAMsNet Ethernet adapter for the
15330 ACSI port ("ACSI node"). The driver works (has to work...) with a
15331 polled I/O scheme, so it's rather slow :-(
15333 Amiga mouse support
15335 If you want to be able to use an Amiga mouse in Linux, say Y.
15337 This driver is also available as a module ( = code which can be
15338 inserted in and removed from the running kernel whenever you want).
15339 The module is called amigamouse.o. If you want to compile it as a
15340 module, say M here and read Documentation/modules.txt.
15342 Atari mouse support
15344 If you want to be able to use an Atari mouse in Linux, say Y.
15346 This driver is also available as a module ( = code which can be
15347 inserted in and removed from the running kernel whenever you want).
15348 The module is called atarimouse.o. If you want to compile it as a
15349 module, say M here and read Documentation/modules.txt.
15351 Atari MFP serial support
15352 CONFIG_ATARI_MFPSER
15353 If you like to use the MFP serial ports ("Modem1", "Serial1") under
15354 Linux, say Y. The driver equally supports all kinds of MFP serial
15355 ports and automatically detects whether Serial1 is available.
15357 This driver is also available as a module ( = code which can be
15358 inserted in and removed from the running kernel whenever you want).
15359 If you want to compile it as a module, say M here and read
15360 Documentation/modules.txt.
15362 Note for Falcon users: You also have an MFP port, it's just not
15363 wired to the outside... But you could use the port under Linux.
15365 Atari SCC serial support
15367 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
15368 LAN) and like to use them under Linux, say Y. All built-in SCC's are
15369 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
15370 two connectors for channel A (Serial2 and LAN), they are visible as
15371 two separate devices.
15373 This driver is also available as a module ( = code which can be
15374 inserted in and removed from the running kernel whenever you want).
15375 If you want to compile it as a module, say M here and read
15376 Documentation/modules.txt.
15378 Atari SCC serial DMA support
15379 CONFIG_ATARI_SCC_DMA
15380 This enables DMA support for receiving data on channel A of the SCC.
15381 If you have a TT you may say Y here and read
15382 drivers/char/atari_SCC.README. All other users should say N here,
15383 because only the TT has SCC-DMA, even if your machine keeps claiming
15386 Atari MIDI serial support
15388 If you want to use your Atari's MIDI port in Linux, say Y.
15390 This driver is also available as a module ( = code which can be
15391 inserted in and removed from the running kernel whenever you
15392 want). If you want to compile it as a module, say M here and read
15393 Documentation/modules.txt.
15395 Atari DSP56k Digital Signal Processor support (EXPERIMENTAL)
15396 CONFIG_ATARI_DSP56K
15397 If you want to be able to use the DSP56001 in Falcons, say Y. This
15398 driver is still experimental, and if you don't know what it is, or
15399 if you don't have this processor, just say N.
15401 This driver is also available as a module ( = code which can be
15402 inserted in and removed from the running kernel whenever you want).
15403 If you want to compile it as a module, say M here and read
15404 Documentation/modules.txt.
15406 Amiga builtin serial support
15407 CONFIG_AMIGA_BUILTIN_SERIAL
15408 If you want to use your Amiga's built-in serial port in Linux,
15411 This driver is also available as a module ( = code which can be
15412 inserted in and removed from the running kernel whenever you
15413 want). If you want to compile it as a module, say M here and read
15414 Documentation/modules.txt.
15416 GVP IO-Extender support
15418 If you want to use a GVP IO-Extender serial card in Linux, say Y.
15421 Multiface Card III serial support
15422 CONFIG_MULTIFACE_III_TTY
15423 If you want to use a Multiface III card's serial port in Linux,
15426 This driver is also available as a module ( = code which can be
15427 inserted in and removed from the running kernel whenever you want).
15428 If you want to compile it as a module, say M here and read
15429 Documentation/modules.txt.
15431 Atari DMA sound support
15432 CONFIG_DMASOUND_ATARI
15433 If you want to use the internal audio of your Atari in Linux, answer
15434 Y to this question. This will provide a Sun-like /dev/audio,
15435 compatible with the Linux/i386 sound system. Otherwise, say N.
15437 This driver is also available as a module ( = code which can be
15438 inserted in and removed from the running kernel whenever you
15439 want). If you want to compile it as a module, say M here and read
15440 Documentation/modules.txt.
15442 PowerMac DMA sound support
15443 CONFIG_DMASOUND_AWACS
15444 If you want to use the internal audio of your PowerMac in Linux,
15445 answer Y to this question. This will provide a Sun-like /dev/audio,
15446 compatible with the Linux/i386 sound system. Otherwise, say N.
15448 This driver is also available as a module ( = code which can be
15449 inserted in and removed from the running kernel whenever you
15450 want). If you want to compile it as a module, say M here and read
15451 Documentation/modules.txt.
15453 Amiga DMA sound support
15454 CONFIG_DMASOUND_PAULA
15455 If you want to use the internal audio of your Amiga in Linux, answer
15456 Y to this question. This will provide a Sun-like /dev/audio,
15457 compatible with the Linux/i386 sound system. Otherwise, say N.
15459 This driver is also available as a module ( = code which can be
15460 inserted in and removed from the running kernel whenever you
15461 want). If you want to compile it as a module, say M here and read
15462 Documentation/modules.txt.
15465 CONFIG_DMASOUND_Q40
15466 If you want to use the internal audio of your Q40 in Linux, answer
15467 Y to this question. This will provide a Sun-like /dev/audio,
15468 compatible with the Linux/i386 sound system. Otherwise, say N.
15470 This driver is also available as a module ( = code which can be
15471 inserted in and removed from the running kernel whenever you
15472 want). If you want to compile it as a module, say M here and read
15473 Documentation/modules.txt.
15475 HP DCA serial support
15477 If you want to use the internal "DCA" serial ports on an HP300
15478 machine, say Y here.
15480 HP on-board LANCE support
15482 If you want to use the builtin "LANCE" Ethernet controller on an
15483 HP300 machine, say Y here.
15487 Say Y here to enable support for the "DIO" expansion bus used in
15488 HP300 machines. If you are using such a system you almost certainly
15493 There are four types of PowerPC chips supported. The more common
15494 types (601, 603, 604, 740, 750), the Motorola embedded versions
15495 (821, 823, 850, 855, 860), the IBM embedded versions (403 and
15496 405) and the high end 64 bit Power processors (Power 3, Power 4).
15497 Unless you are building a kernel for one of the embedded
15498 processor systems, or a 64 bit IBM RS/6000, choose 6xx. Note that
15499 the kernel runs in 32-bit mode even on 64-bit chips.
15503 Linux currently supports several different kinds of PowerPC-based
15504 machines: Apple Power Macintoshes and clones (such as the Motorola
15505 Starmax series), PReP (PowerPC Reference Platform) machines such as
15506 the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP and the
15507 embedded MBX boards from Motorola. Currently, a single kernel binary
15508 only supports one type or the other. However, there is very early
15509 work on support for CHRP, PReP and PowerMac's from a single binary.
15511 Power management support for PowerBooks
15513 This provides support for putting a PowerBook to sleep; it also
15514 enables media bay support. Power management works on the
15515 PB2400/3400/3500, Wallstreet, Lombard, and Bronze PowerBook G3. You
15516 must get the power management daemon, pmud, to make it work and you
15517 must have the /dev/pmu device (see the pmud README).
15519 Get pmud from ftp://linuxcare.com.au/pub/ppclinux/pmud/
15521 If you have a PowerBook, you should say Y.
15523 You may also want to compile the dma sound driver as a module and
15524 have it autoloaded. The act of removing the module shuts down the
15525 sound hardware for more power savings.
15527 Mac-on-Linux support
15529 This option enables low-level support for Mac-on-Linux.
15530 MOL lets you run MacOS and Linux simultaneously. Please
15531 visit <http://www.maconlinux.org> for more information.
15534 ADB raw keycode support
15535 CONFIG_MAC_ADBKEYCODES
15536 This provides support for sending raw ADB keycodes to console
15537 devices. This is the default up to 2.4.0, but in future this may be
15538 phased out in favor of generic Linux keycodes. If you say Y here, you
15539 can dynamically switch via the
15540 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
15541 sysctl and with the "keyboard_sends_linux_keycodes=" kernel argument.
15543 If unsure, say Y here.
15545 Mouse button 2+3 emulation support
15546 CONFIG_MAC_EMUMOUSEBTN
15547 This provides generic support for emulating the 2nd and 3rd mouse
15548 button with keypresses. If you say Y here, the emulation is still
15549 disabled by default. The emulation is controlled by these sysctl entries:
15550 /proc/sys/dev/mac_hid/mouse_button_emulation
15551 /proc/sys/dev/mac_hid/mouse_button2_keycode
15552 /proc/sys/dev/mac_hid/mouse_button3_keycode
15554 Enhanced Real Time Clock Support
15556 If you say Y here and create a character special file /dev/rtc with
15557 major number 10 and minor number 135 using mknod ("man mknod"), you
15558 will get access to the real time clock (or hardware clock) built
15559 into your computer.
15561 If unsure, say Y here.
15563 Support for Open Firmware device tree in /proc
15564 CONFIG_PROC_DEVICETREE
15565 This option adds a device-tree directory under /proc which contains
15566 an image of the device tree that the kernel copies from Open
15567 Firmware. If unsure, say Y here.
15569 MESH (Power Mac internal SCSI) support
15571 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
15572 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
15573 other Power Macintoshes do). Say Y to include support for this SCSI
15574 adaptor. This driver is also available as a module called mesh.o
15575 ( = code which can be inserted in and removed from the running
15576 kernel whenever you want). If you want to compile it as a module,
15577 say M here and read Documentation/modules.txt.
15579 Maximum synchronous transfer rate
15580 CONFIG_SCSI_MESH_SYNC_RATE
15581 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
15582 drives a bus which is entirely internal to the machine (such as the
15583 7500, 7600, 8500, etc.), the MESH is capable of synchronous
15584 operation at up to 10 MB/s. On machines where the SCSI bus
15585 controlled by the MESH can have external devices connected, it is
15586 usually rated at 5 MB/s. 5 is a safe value here unless you know the
15587 MESH SCSI bus is internal only; in that case you can say 10. Say 0
15588 to disable synchronous operation.
15590 53C94 (Power Mac external SCSI) support
15591 CONFIG_SCSI_MAC53C94
15592 On Power Macintoshes (and clones) with two SCSI buses, the external
15593 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
15594 machines which only have one SCSI bus, such as the 7200, also use
15595 the 53C94. Say Y to include support for the 53C94.
15597 This driver is also available as a module called mac53c94.o ( = code
15598 which can be inserted in and removed from the running kernel
15599 whenever you want). If you want to compile it as a module, say M
15600 here and read Documentation/modules.txt.
15602 MACE (Power Mac Ethernet) support
15604 Power Macintoshes and clones with Ethernet built-in on the
15605 motherboard will usually use a MACE (Medium Access Control for
15606 Ethernet) interface. Say Y to include support for the MACE chip.
15608 This driver is also available as a module called mace.o ( = code
15609 which can be inserted in and removed from the running kernel
15610 whenever you want). If you want to compile it as a module, say M
15611 here and read Documentation/modules.txt.
15613 BMAC (G3 ethernet) support
15615 Say Y for support of BMAC Ethernet interfaces. These are used on G3
15618 This driver is also available as a module called bmac.o ( = code
15619 which can be inserted in and removed from the running kernel
15620 whenever you want). If you want to compile it as a module, say M
15621 here and read Documentation/modules.txt.
15623 GMAC (G4/iBook ethernet) support
15625 Say Y for support of GMAC Ethernet interfaces. These are used on G4
15626 and iBook computers.
15628 This driver is also available as a module called gmac.o ( = code
15629 which can be inserted in and removed from the running kernel
15630 whenever you want). If you want to compile it as a module, say M
15631 here and read Documentation/modules.txt.
15633 Symbios 53c885 (Synergy ethernet) support
15635 This is and Ethernet driver for the dual-function NCR 53C885
15636 SCSI/Ethernet controller.
15638 This driver is also available as a module called ncr885e.o ( = code
15639 which can be inserted in and removed from the running kernel
15640 whenever you want). If you want to compile it as a module, say M
15641 here and read Documentation/modules.txt.
15643 National DP83902AV (Oak ethernet) support
15645 Say Y if your machine has this type of Ethernet network card.
15647 This driver is also available as a module called oaknet.o ( = code
15648 which can be inserted in and removed from the running kernel
15649 whenever you want). If you want to compile it as a module, say M
15650 here and read Documentation/modules.txt.
15654 Support for audio/video capture and overlay devices and FM radio
15655 cards. The exact capabilities of each device vary. User tools for
15656 this are available from
15657 ftp://ftp.uk.linux.org/pub/linux/video4linux .
15659 If you are interested in writing a driver for such an audio/video
15660 device or user software interacting with such a driver, please read
15661 the file Documentation/video4linux/API.html.
15663 This driver is also available as a module called videodev.o ( = code
15664 which can be inserted in and removed from the running kernel
15665 whenever you want). If you want to compile it as a module, say M
15666 here and read Documentation/modules.txt.
15668 Video For Linux /proc file system information
15669 CONFIG_VIDEO_PROC_FS
15670 If you say Y here, you are able to access video device information
15673 To use this option, you have to check, that the "/proc file system
15674 support" (CONFIG_PROC_FS) is enabled too.
15676 AIMSlab RadioTrack (aka RadioReveal) support
15677 CONFIG_RADIO_RTRACK
15678 Choose Y here if you have one of these FM radio cards, and then fill
15679 in the port address below.
15681 Note that newer AIMSlab RadioTrack cards have a different chipset
15682 and are not supported by this driver. For these cards, use the
15683 RadioTrack II driver below.
15685 If you have a GemTeks combined (PnP) sound- and radio card you must
15686 use this driver as a module and setup the card with isapnptools. You
15687 must also pass the module a suitable io parameter, 0x248 has been
15688 reported to be used by these cards.
15690 In order to control your radio card, you will need to use programs
15691 that are compatible with the Video for Linux API. Information on
15692 this API and pointers to "v4l" programs may be found on the WWW at
15693 http://roadrunner.swansea.uk.linux.org/v4l.shtml . More information
15694 is contained in the file Documentation/video4linux/radiotrack.txt.
15696 If you want to compile this driver as a module ( = code which can be
15697 inserted in and removed from the running kernel whenever you want),
15698 say M here and read Documentation/modules.txt. The module will be
15699 called radio-aimslab.o.
15701 RadioTrack i/o port
15702 CONFIG_RADIO_RTRACK_PORT
15703 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
15704 haven't changed the jumper setting on the card.
15706 AIMSlab RadioTrack II support
15707 CONFIG_RADIO_RTRACK2
15708 Choose Y here if you have this FM radio card, and then fill in the
15709 port address below.
15711 In order to control your radio card, you will need to use programs
15712 that are compatible with the Video for Linux API. Information on
15713 this API and pointers to "v4l" programs may be found on the WWW at
15714 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15716 If you want to compile this driver as a module ( = code which can be
15717 inserted in and removed from the running kernel whenever you want),
15718 say M here and read Documentation/modules.txt. The module will be
15719 called radio-rtrack2.o.
15721 RadioTrack II i/o port
15722 CONFIG_RADIO_RTRACK2_PORT
15723 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
15724 haven't changed the jumper setting on the card.
15726 Aztech/Packard Bell Radio
15727 CONFIG_RADIO_AZTECH
15728 Choose Y here if you have one of these FM radio cards, and then fill
15729 in the port address below.
15731 In order to control your radio card, you will need to use programs
15732 that are compatible with the Video for Linux API. Information on
15733 this API and pointers to "v4l" programs may be found on the WWW at
15734 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15736 If you want to compile this driver as a module ( = code which can be
15737 inserted in and removed from the running kernel whenever you want),
15738 say M here and read Documentation/modules.txt. The module will be
15739 called radio-aztech.o.
15741 Aztech/Packard Bell radio card i/o port
15742 CONFIG_RADIO_AZTECH_PORT
15743 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
15744 haven't changed the setting of jumper JP3 on the card. Removing the
15745 jumper sets the card to 0x358.
15747 ADS Cadet AM/FM Radio Tuner Card
15749 Choose Y here if you have one of these AM/FM radio cards, and then
15750 fill in the port address below.
15752 In order to control your radio card, you will need to use programs
15753 that are compatible with the Video for Linux API. Information on
15754 this API and pointers to "v4l" programs may be found on the WWW at
15755 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15757 Further documentation on this driver can be found on the WWW at
15758 http://linux.blackhawke.net/cadet.html .
15760 If you want to compile this driver as a module ( = code which can be
15761 inserted in and removed from the running kernel whenever you want),
15762 say M here and read Documentation/modules.txt. The module will be
15763 called radio-cadet.o.
15766 CONFIG_RADIO_SF16FMI
15767 Choose Y here if you have one of these FM radio cards, and then fill
15768 in the port address below.
15770 In order to control your radio card, you will need to use programs
15771 that are compatible with the Video for Linux API. Information on
15772 this API and pointers to "v4l" programs may be found on the WWW at
15773 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15775 If you want to compile this driver as a module ( = code which can be
15776 inserted in and removed from the running kernel whenever you want),
15777 say M here and read Documentation/modules.txt. The module will be
15778 called radio-sf16fmi.o
15780 SF16FMI I/O port (0x284 or 0x384)
15781 CONFIG_RADIO_SF16FMI_PORT
15782 Enter the I/O port of your SF16FMI radio card.
15785 CONFIG_RADIO_TYPHOON
15786 Choose Y here if you have one of these FM radio cards, and then fill
15787 in the port address and the frequency used for muting below.
15789 In order to control your radio card, you will need to use programs
15790 that are compatible with the Video for Linux API. Information on
15791 this API and pointers to "v4l" programs may be found on the WWW at
15792 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15794 If you want to compile this driver as a module ( = code which can be
15795 inserted in and removed from the running kernel whenever you want),
15796 say M here and read Documentation/modules.txt. The module will be
15797 called radio-typhoon.o
15799 Support for /proc/radio-typhoon
15800 CONFIG_RADIO_TYPHOON_PROC_FS
15801 Say Y here if you want the typhoon radio card driver to write
15802 status information (frequency, volume, muted, mute frequency,
15803 base address) to /proc/radio-typhoon. The file can be viewed with
15804 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
15805 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
15807 Typhoon I/O port (0x316 or 0x336)
15808 CONFIG_RADIO_TYPHOON_PORT
15809 Enter the I/O port of your Typhoon or EcoRadio radio card.
15811 Typhoon frequency set when muting the device (kHz)
15812 CONFIG_RADIO_TYPHOON_MUTEFREQ
15813 Enter the frequency used for muting the radio. The device is never
15814 completely silent. If the volume is just turned down, you can still
15815 hear silent voices and music. For that reason, the frequency of the
15816 radio device is set to the frequency you can enter here whenever
15817 the device is muted. There should be no local radio station at that
15821 CONFIG_RADIO_ZOLTRIX
15822 Choose Y here if you have one of these FM radio cards, and then fill
15823 in the port address below.
15825 In order to control your radio card, you will need to use programs
15826 that are compatible with the Video for Linux API. Information on
15827 this API and pointers to "v4l" programs may be found on the WWW at
15828 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15830 If you want to compile this driver as a module ( = code which can be
15831 inserted in and removed from the running kernel whenever you want),
15832 say M here and read Documentation/modules.txt. The module will be
15833 called radio-zoltrix.o
15835 ZOLTRIX I/O port (0x20c or 0x30c)
15836 CONFIG_RADIO_ZOLTRIX_PORT
15837 Enter the I/O port of your Zoltrix radio card.
15839 IIC on parallel port
15841 I2C is a simple serial bus system used in many micro controller
15842 applications. Saying Y here will allow you to use your parallel port
15843 as an I2C interface.
15845 If you want to compile this driver as a module ( = code which can be
15846 inserted in and removed from the running kernel whenever you want),
15847 say M here and read Documentation/modules.txt. The module will be
15848 called i2c-parport.o.
15851 CONFIG_RADIO_MIROPCM20
15852 Choose Y here if you have this FM radio card. You also need to say Y
15853 to "ACI mixer (miroPCM12/PCM20)" (in "additional low level sound
15854 drivers") for this to work.
15856 In order to control your radio card, you will need to use programs
15857 that are compatible with the Video for Linux API. Information on
15858 this API and pointers to "v4l" programs may be found on the WWW at
15859 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15861 If you want to compile this driver as a module ( = code which can be
15862 inserted in and removed from the running kernel whenever you want),
15863 say M here and read Documentation/modules.txt. The module will be
15864 called radio-miropcm20.o
15867 CONFIG_RADIO_GEMTEK
15868 Choose Y here if you have this FM radio card, and then fill in the
15869 port address below.
15871 In order to control your radio card, you will need to use programs
15872 that are compatible with the Video for Linux API. Information on
15873 this API and pointers to "v4l" programs may be found on the WWW at
15874 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15876 If you want to compile this driver as a module ( = code which can be
15877 inserted in and removed from the running kernel whenever you want),
15878 say M here and read Documentation/modules.txt. The module will be
15879 called radio-gemtek.o.
15882 CONFIG_RADIO_GEMTEK_PORT
15883 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
15884 0x34c, if you haven't changed the jumper setting on the card. On
15885 Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM Gemtek), the i/o
15888 PlanB Video-In for PowerMacs
15890 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
15891 input hardware. If you want to experiment with this, say Y.
15892 Otherwise, or if you don't understand a word, say N.
15893 See http://www.cpu.lu/~mlan/planb.html for more info.
15895 Saying M will compile this driver as a module (planb.o).
15897 TerraTec ActiveRadio
15898 CONFIG_RADIO_TERRATEC
15899 Choose Y here if you have this FM radio card, and then fill in the
15900 port address below. (TODO)
15902 Note: This driver is in its early stages. Right now volume and
15903 frequency control and muting works at least for me, but
15904 unfortunately i have not found anybody who wants to use this card
15905 with Linux. So if it is this what YOU are trying to do right now,
15906 PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
15908 In order to control your radio card, you will need to use programs
15909 that are compatible with the Video for Linux API. Information on
15910 this API and pointers to "v4l" programs may be found on the WWW at
15911 http://roadrunner.swansea.uk.linux.org/v4l.shtml .
15913 If you want to compile this driver as a module ( = code which can be
15914 inserted in and removed from the running kernel whenever you want),
15915 say M here and read Documentation/modules.txt. The module will be
15916 called radio-terratec.o.
15918 Terratec i/o port (normally 0x590)
15919 CONFIG_RADIO_TERRATEC_PORT
15920 Fill in the i/o port of your TerraTec FM radio card. If unsure, go
15924 # Zoran ZR36057/36060 support
15925 # CONFIG_VIDEO_ZORAN
15927 # Include support for Iomega Buz
15930 Trust FM radio card
15932 This is a driver for the Trust FM radio cards. Say Y if you have
15933 such a card and want to use it under Linux.
15935 This driver is also available as a module called radio-trust.o ( =
15936 code which can be inserted in and removed from the running kernel
15937 whenever you want). If you want to compile it as a module, say M
15938 here and read Documentation/modules.txt.
15940 Trust i/o port (usually 0x350 or 0x358)
15941 CONFIG_RADIO_TRUST_PORT
15942 Enter the i/o port of your Trust FM radio card. If unsure, try the
15943 values "0x350" or "0x358".
15945 BT848 Video For Linux
15947 Support for BT848 based frame grabber/overlay boards. This includes
15948 the Miro, Hauppauge and STB boards. Please read the material in
15949 Documentation/video4linux/bttv for more information.
15951 If you say Y or M here, you need to say Y or M to "I2C support" and
15952 "I2C bit-banging interfaces" in the character device section.
15954 This driver is available as a module called bttv.o ( = code
15955 which can be inserted in and removed from the running kernel
15956 whenever you want). If you want to compile it as a module, say M
15957 here and read Documentation/modules.txt.
15959 ZR36120/36125 Video for Linux
15960 CONFIG_VIDEO_ZR36120
15961 Support for ZR36120/ZR36125 based frame grabber/overlay boards.
15962 This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV,
15963 and Buster boards. Please read the material in
15964 Documentation/video4linux/zr36120.txt for more information.
15966 This driver is also available as a module called zr36120.o ( = code
15967 which can be inserted in and removed from the running kernel
15968 whenever you want). If you want to compile it as a module, say M
15969 here and read Documentation/modules.txt.
15971 SAA5249 Teletext processor
15972 CONFIG_VIDEO_SAA5249
15973 Support for I2C bus based teletext using the SAA5249 chip. At the
15974 moment this is only useful on some European WinTV cards.
15976 This driver is also available as a module called saa5249.o ( = code
15977 which can be inserted in and removed from the running kernel
15978 whenever you want). If you want to compile it as a module, say M
15979 here and read Documentation/modules.txt.
15981 Quickcam BW Video For Linux
15982 CONFIG_VIDEO_BWQCAM
15983 Say Y have if you the black and white version of the QuickCam
15984 camera. See the next option for the color version.
15986 This driver is also available as a module called bw-qcam.o ( = code
15987 which can be inserted in and removed from the running kernel
15988 whenever you want). If you want to compile it as a module, say M
15989 here and read Documentation/modules.txt.
15991 Colour QuickCam Video For Linux
15993 This is the video4linux driver for the colour version of the
15994 Connectix Quickcam. If you have one of these cameras, say Y here,
15995 otherwise say N. This driver does not work with the original
15996 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
15997 as a module (c-qcam.o). Read Documentation/video4linux/CQcam.txt for
16000 CPiA Video For Linux
16002 This is the video4linux driver for cameras based on Vision's CPiA
16003 (Colour Processor Interface ASIC), such as the Creative Labs Video
16004 Blaster Webcam II. If you have one of these cameras, say Y here
16005 and select parallel port and/or USB lowlevel support below,
16006 otherwise say N. This will not work with the Creative Webcam III.
16008 Please read Documentation/video4linux/README.cpia for more
16011 This driver is also available as a module (cpia.o).
16013 CPiA Parallel Port Lowlevel Support
16014 CONFIG_VIDEO_CPIA_PP
16015 This is the lowlevel parallel port support for cameras based on
16016 Vision's CPiA (Colour Processor Interface ASIC), such as the
16017 Creative Webcam II. If you have the parallel port version of one
16018 of these cameras, say Y here, otherwise say N. It is also available
16019 as a module (cpia_pp.o).
16021 CPiA USB Lowlevel Support
16022 CONFIG_VIDEO_CPIA_USB
16023 This is the lowlevel USB support for cameras based on Vision's CPiA
16024 (Colour Processor Interface ASIC), such as the Creative Webcam II.
16025 If you have the USB version of one of these cameras, say Y here,
16026 otherwise say N. This will not work with the Creative Webcam III.
16027 It is also available as a module (cpia_usb.o).
16029 Mediavision Pro Movie Studio Video For Linux
16031 Say Y if you have such a thing. This driver is also available as a
16032 module called pms.o ( = code which can be inserted in and removed
16033 from the running kernel whenever you want). If you want to compile
16034 it as a module, say M here and read Documentation/modules.txt.
16036 SAB3036 tuner support
16038 Say Y here to include support for Philips SAB3036 compatible tuners.
16039 If in doubt, say N.
16041 Compaq SMART2 support
16043 This is the driver for Compaq Smart Array controllers.
16044 Everyone using these boards should say Y here.
16045 See the file Documentation/cpqarray.txt for the current list of
16046 boards supported by this driver, and for further information
16047 on the use of this driver.
16054 This selects what ARM system you wish to build the kernel for. It
16055 also selects to some extent the CPU type. If you are unsure what
16056 to set this option to, please consult any information supplied with
16059 2MB physical memory
16061 Say Y here if your Archimedes or A5000 system has only 2MB of
16062 memory, otherwise say N. The resulting kernel will not run on a
16063 machine with 4MB of memory.
16065 Include support for the CATS
16067 Say Y here if you intend to run this kernel on the CATS.
16069 Saying N will reduce the size of the Footbridge kernel.
16071 Include support for the EBSA285
16072 CONFIG_ARCH_EBSA285
16073 Say Y here if you intend to run this kernel on the EBSA285 card
16074 in host ("central function") mode.
16076 Saying N will reduce the size of the Footbridge kernel.
16078 Include support for the LinkUp Systems L7200 SDB
16080 Say Y here if you intend to run this kernel on a LinkUp Systems
16081 L7200 Software Development Board which uses an ARM720T processor.
16082 Information on this board can be obtained at:
16084 http://www.linkupsys.com/
16086 If you have any questions or comments about the Linux kernel port
16087 to this board, send e-mail to sjhill@cotw.com
16089 Include support for the NetWinder
16090 CONFIG_ARCH_NETWINDER
16091 Say Y here if you intend to run this kernel on the Rebel.COM
16092 NetWinder. Information about this machine can be found at:
16094 http://www.netwinder.org/
16096 Saying N will reduce the size of the Footbridge kernel.
16098 Include support for the Compaq Personal Server
16099 CONFIG_ARCH_PERSONAL_SERVER
16100 Say Y here if you intend to run this kernel on the Compaq
16103 Saying N will reduce the size of the Footbridge kernel.
16105 The Compaq Personal Server is not available for purchase.
16106 There are no product plans beyond the current research
16107 prototypes at this time. Information is available at:
16109 http://crl.research.compaq.com/projects/personalserver
16111 If you have any questions or comments about the Compaq Personal
16112 Server, send e-mail to skiff@crl.dec.com
16114 Include support for Assabet
16115 CONFIG_SA1100_ASSABET
16116 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
16117 Microprocessor Development Board (also known as the Assabet).
16119 Include support for Neponset
16120 CONFIG_ASSABET_NEPONSET
16121 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
16122 Microprocessor Development Board (Assabet) with the SA-1111
16123 Development Board (Nepon).
16125 Include support for the Compaq iPAQ H3600 (Bitsy)
16126 CONFIG_SA1100_BITSY
16127 Say Y here if you intend to run this kernel on the Compaq iPAQ
16128 H3600 handheld computer. Information about this machine and the
16129 Linux port to this machine can be found at:
16131 http://www.handhelds.org/Compaq/index.html#iPAQ_H3600
16132 http://www.compaq.com/products/handhelds/pocketpc/
16134 Include support for Brutus
16135 CONFIG_SA1100_BRUTUS
16136 Say Y here if you are using the Intel(R) StrongARM(R) SA-1100
16137 Microprocessor Development Board (also known as the Brutus).
16139 Include support for LART
16141 Say Y here if you are using the Linux Advanced Radio Terminal
16142 (also known as the LART). See http://www.lart.tudelft.nl/ for
16143 information on the LART.
16145 Include support for ThinClient
16146 CONFIG_SA1100_THINCLIENT
16147 Say Y here if you are using an Applied Data Systems Intel(R)
16148 StrongARM(R) SA-1100 based Thin Client SBC. See
16149 http://www.flatpanels.com/ for information on this system.
16151 Include support for GraphicsClient
16152 CONFIG_SA1100_GRAPHICSCLIENT
16153 Say Y here if you are using an Applied Data Systems Intel(R)
16154 StrongARM(R) SA-1100 based Graphics Client SBC. See
16155 http://www.flatpanels.com/ for information on this system.
16157 Include support for Victor
16158 CONFIG_SA1100_VICTOR
16159 Say Y here if you are using a Visu Aide Intel(R) StrongARM(R)
16160 SA-1100 based Victor Digital Talking Book Reader. See
16161 http://www.visuaide.com/pagevictor.en.html for information on
16164 Support ARM610 processor
16166 Say Y here if you wish to include support for the ARM610 processor.
16168 Support ARM710 processor
16170 Say Y here if you wish to include support for the ARM710 processor.
16172 Support StrongARM(R) SA-110 processor
16174 Say Y here if you wish to include support for the Intel(R)
16175 StrongARM(R) SA-110 processor.
16177 Support ARM720 processor
16179 Say Y here if you wish to include support for the ARM720 processor.
16183 Say Y here if you wish to include support for the ARM920 processor.
16187 Say Y to include the NWFPE floating point emulator in the kernel.
16188 This is necessary to run most binaries. Linux does not currently
16189 support floating point hardware so you need to say Y here even if
16190 your machine has an FPA or floating point co-processor podule.
16192 It is also possible to say M to build the emulator as a module
16193 (nwfpe.o) or indeed to leave it out altogether. However, unless you
16194 know what you are doing this can easily render your machine
16195 unbootable. Saying Y is the safe option.
16197 You may say N here if you are going to load the Acorn FPEmulator
16198 early in the bootup.
16200 DS1620 Thermometer support
16202 Say Y here to include support for the thermal management hardware
16203 found in the NetWinder. This driver allows the user to control the
16204 temperature set points and to read the current temperature.
16206 It is also possible to say M here to build it as a module (ds1620.o)
16207 It is recommended to be used on a NetWinder, but it is not a
16210 Verbose kernel error messages
16211 CONFIG_DEBUG_ERRORS
16212 This option controls verbose debugging information which can be
16213 printed when the kernel detects an internal error. This debugging
16214 information is useful to kernel hackers when tracking down problems,
16215 but mostly meaningless to other people. It's safe to say Y unless
16216 you are concerned with the code size or don't want to see these
16219 Compile kernel with frame pointer
16220 CONFIG_FRAME_POINTER
16221 If you say Y here, the resulting kernel will be slightly larger and
16222 slower, but it will give useful debugging information. If you don't
16223 debug the kernel, you can say N.
16225 User fault debugging
16227 When a user program crashes due to an exception, the kernel can
16228 print a brief message explaining what the problem was. This is
16229 sometimes helpful for debugging but serves no purpose on a
16230 production system. Most people should say N here.
16232 Include gdb debugging information in kernel binary
16234 Say Y here to include source-level debugging information in the
16235 `vmlinux' binary image. This is handy if you want to use gdb or
16236 addr2line to debug the kernel. It has no impact on the in-memory
16237 footprint of the running kernel but it can increase the amount of
16238 time and disk space needed for compilation of the kernel. If in
16241 Kernel low-level debugging functions
16243 Say Y here to include definitions of printascii, printchar, printhex
16244 in the kernel. This is helpful if you are debugging code that
16245 executes before the console is initialized.
16247 Kernel low-level debugging messages via footbridge serial port
16248 CONFIG_DEBUG_DC21285_PORT
16249 Say Y here if you want the low-level print routines to direct their
16250 output to the serial port in the DC21285 (Footbridge).
16252 Split initialisation functions into discardable section
16253 CONFIG_TEXT_SECTIONS
16254 If you say Y here, kernel code that is only used during
16255 initialisation is collected into a special area of the kernel so
16256 that it can be discarded and the memory reclaimed when
16257 initialisation is complete. In addition, if the kernel you wish to
16258 build is able to run on multiple architectures, it allows the unused
16259 code to be discarded. Some versions of binutils, however, have a bug
16260 that causes the kernel to crash during startup when this option is
16261 enabled. Say Y unless you experience problems that you suspect may
16264 Disable pgtable cache (EXPERIMENTAL)
16265 CONFIG_NO_PGT_CACHE
16266 Normally the kernel maintains a `quicklist' of preallocated
16267 pagetable structures in order to increase performance. On machines
16268 with very few pages this may however be a loss. Say Y here to
16269 disable the pgtable cache.
16271 RISC OS personality
16273 Say Y here to include the kernel code necessary if you want to run
16274 Acorn RISC OS/Arthur binaries under Linux. This code is still very
16275 experimental; if this sounds frightening, say N and sleep in peace.
16276 You can also say M here to compile this support as a module (which
16277 will be called arthur.o).
16279 Initial kernel command line
16281 On some architectures (EBSA110 and CATS), there is currently no way
16282 for the boot loader to pass arguments to the kernel. For these
16283 architectures, you should supply some command-line options at build
16284 time by entering them here. As a minimum, you should specify the
16285 memory size and the root device (e.g., mem=64M root=/dev/nfs)
16287 Hardware alignment trap (EXPERIMENTAL)
16288 CONFIG_ALIGNMENT_TRAP
16289 ARM processors can not fetch/store information which is not
16290 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
16291 address divisible by 4. On 32-bit ARM processors, these non-aligned
16292 fetch/store instructions will be emulated in software if you say
16293 here, which has a severe performance impact. This is necessary for
16294 correct operation of some network protocols. With an IP-only
16295 configuration it is safe to say N, otherwise say Y.
16297 21285 serial port support
16298 CONFIG_SERIAL_21285
16299 If you have a machine based on a 21285 (Footbridge) StrongARM(R)/
16300 PCI bridge you can enable its onboard serial port by enabling this
16301 option. The device has major ID 4, minor 64.
16303 Console on 21285 serial port
16304 CONFIG_SERIAL_21285_CONSOLE
16305 If you have enabled the serial port on the 21285 footbridge you can
16306 make it the console by answering Y to this option.
16308 L7200 serial port support
16309 CONFIG_SERIAL_L7200
16310 If you have a LinkUp Systems L7200 board you can enable its two
16311 onboard serial ports by enabling this option. The device numbers
16312 are major ID 4 with minor 64 and 65 respectively.
16314 Console on L7200 serial port
16315 CONFIG_SERIAL_L7200_CONSOLE
16316 If you have enabled the serial ports on the L7200 development board
16317 you can make the first serial port the console by answering Y to
16321 CONFIG_HOST_FOOTBRIDGE
16322 The 21285 Footbridge chip can operate in either `host mode' or
16323 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
16324 is the configuration master, otherwise say N. This must not be
16325 set to Y if the card is used in 'add-in' mode.
16327 MFM hard disk support
16329 Support the MFM hard drives on the Acorn Archimedes both
16330 on-board the A4x0 motherboards and via the Acorn MFM podules.
16331 Drives up to 64MB are supported. If you haven't got one of these
16332 machines or drives just say N.
16334 Old Archimedes floppy (1772) support
16335 CONFIG_BLK_DEV_FD1772
16336 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
16337 R140 and R260) series of computers; it supports only 720K floppies
16338 at the moment. If you don't have one of these machines just answer
16341 Autodetect hard drive geometry
16342 CONFIG_BLK_DEV_MFM_AUTODETECT
16343 If you answer Y, the MFM code will attempt to automatically detect
16344 the cylinders/heads/sectors count on your hard drive. WARNING: This
16345 sometimes doesn't work and it also does some dodgy stuff which
16346 potentially might damage your drive.
16348 NetWinder /dev/flash support
16350 If you say Y here and create a character device /dev/flash with
16351 major 10 and minor 160 you can manipulate the flash ROM containing
16352 the NetWinder firmware. Be careful as accidentally overwriting the
16353 flash contents can render your computer unbootable. On no account
16354 allow random users access to this device. :-)
16356 This driver is also available as a module ( = code which can be
16357 inserted in and removed from the running kernel whenever you want).
16358 The module will be called nwflash.o. If you want to compile it as a
16359 module, say M here and read Documentation/modules.txt.
16361 If you're not sure, say N.
16363 Footbridge internal watchdog
16364 CONFIG_21285_WATCHDOG
16365 The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
16366 here if you wish to use this. Alternatively say M to compile the
16367 driver as a module, which will be called wdt285.o.
16369 This driver does not work on all machines. In particular, early CATS
16370 boards have hardware problems that will cause the machine to simply
16371 lock up if the watchdog fires.
16373 "If in doubt, leave it out" - say N.
16375 NetWinder WB977 watchdog
16376 CONFIG_977_WATCHDOG
16377 Say Y here to include support for the WB977 watchdog included in
16378 NetWinder machines. Alternatively say M to compile the driver as
16379 a module, which will be called wdt977.o.
16381 Not sure? It's safe to say N.
16383 IrDA subsystem support
16385 Say Y here if you want to build support for the IrDA (TM) protocols.
16386 The Infrared Data Associations (tm) specifies standards for wireless
16387 infrared communication and is supported by most laptops and PDA's.
16389 To use Linux support for the IrDA (tm) protocols, you will also need
16390 some user-space utilities like the irmanager and probably irattach
16391 as well. For more information, see the file
16392 Documentation/networking/irda.txt. You also want to read the
16393 IR-HOWTO, available at http://www.linuxdoc.org/docs.html#howto .
16395 This support is also available as a module called irda.o. If you
16396 want to compile it as a module, say M here and read
16397 Documentation/modules.txt.
16399 IrDA Cache last LSAP
16400 CONFIG_IRDA_CACHE_LAST_LSAP
16401 Say Y here if you want IrLMP to cache the last LSAP used. This makes
16402 sense since most frames will be sent/received on the same
16403 connection. Enabling this option will save a hash-lookup per frame.
16408 CONFIG_IRDA_FAST_RR
16409 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
16410 when acting as a primary station. This will make IrLAP send out a RR
16411 frame immediately when receiving a frame if its own transmit queue
16412 is currently empty. This will give a lot of speed improvement when
16413 receiving much data since the secondary station will not have to
16414 wait the max. turn around time before it is allowed to transmit the
16415 next time. If the transmit queue of the secondary is also empty the
16416 primary will back off waiting longer for sending out the RR frame
16417 until the timeout reaches the normal value. Enabling this option
16418 will make the IR-diode burn more power and thus reduce your battery
16425 Say Y here if you want the IrDA subsystem to write debug information
16426 to your syslog. You can change the debug level in
16427 /proc/sys/net/irda/debug
16429 If unsure, say Y (since it makes it easier to find the bugs).
16431 IrLAP Compression support
16432 CONFIG_IRDA_COMPRESSION
16433 Compression is _not_ part of the IrDA(tm) protocol specification,
16434 but it's working great! Linux is the first to try out compression
16435 support at the IrLAP layer. This means that you will only benefit
16436 from compression if you are running a Linux <-> Linux configuration.
16438 If you say Y here, you also need to say Y or M to a compression
16441 IrLAP Deflate Compression Protocol (EXPERIMENTAL)
16442 CONFIG_IRDA_DEFLATE
16443 Say Y here if you want to build support for the Deflate compression
16444 protocol. The deflate compression (GZIP) is exactly
16445 the same as the one used by the PPP protocol.
16447 If you want to compile this compression support as a module, say M
16448 here and read Documentation/modules.txt. The module will be called
16453 Say Y here if you want to build support for the IrLAN protocol. If
16454 you want to compile it as a module (irlan.o), say M here and read
16455 Documentation/modules.txt. IrLAN emulates an Ethernet and makes it
16456 possible to put up a wireless LAN using infrared beams.
16458 The IrLAN protocol can be used to talk with infrared access points
16459 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
16460 to another Linux machine running the IrLAN protocol for ad-hoc
16465 Say Y here if you want to build support for the IrCOMM protocol. If
16466 you want to compile it as a module (you will get ircomm.o and
16467 ircomm-tty.o), say M here and read Documentation/modules.txt. IrCOMM
16468 implements serial port emulation, and makes it possible to use all
16469 existing applications that understands TTY's with an infrared link.
16470 Thus you should be able to use application like PPP, minicom and
16471 others. Enabling this option will create two modules called ircomm
16474 IrTTY IrDA Device Driver
16476 Say Y here if you want to build support for the IrTTY line
16477 discipline. If you want to compile it as a module (irtty.o), say M
16478 here and read Documentation/modules.txt. IrTTY makes it possible to
16479 use Linux's own serial driver for all IrDA ports that are 16550
16480 compatible. Most IrDA chips are 16550 compatible so you should
16481 probably say Y to this option. Using IrTTY will however limit the
16482 speed of the connection to 115200 bps (IrDA SIR mode)
16486 IrPORT IrDA Device Driver
16488 Say Y here if you want to build support for the IrPORT IrDA device
16489 driver. If you want to compile it as a module (irport.o), say M here
16490 and read Documentation/modules.txt. IrPORT can be used instead of
16491 IrTTY and sometimes this can be better. One example is if your IrDA
16492 port does not have echo-canceling, which will work OK with IrPORT
16493 since this driver is working in half-duplex mode only. You don't
16494 need to use irattach with IrPORT, but you just insert it the same
16495 way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice that
16496 IrPORT is a SIR device driver which means that speed is limited to
16501 Winbond W83977AF IrDA Device Driver
16503 Say Y here if you want to build IrDA support for the Winbond
16504 W83977AF super-io chipset. This driver should be used for the IrDA
16505 chipset in the Corel NetWinder. The driver supports SIR, MIR and FIR
16508 If you want to compile it as a module, say M here and read
16509 Documentation/modules.txt. The module will be called w83977af_ir.o.
16511 NSC PC87108 IrDA Device Driver
16513 Say Y here if you want to build support for the NSC PC87108 and
16514 PC87338 IrDA chipsets. This driver supports SIR,
16515 MIR and FIR (4Mbps) speeds.
16517 If you want to compile it as a module, say M here and read
16518 Documentation/modules.txt. The module will be called nsc-ircc.o.
16520 Toshiba Type-O IR Port Device Driver
16522 Say Y here if you want to build support for the Toshiba Type-O IR
16523 chipset. This chipset is used by the Toshiba Libretto 100CT, and
16524 many more laptops. If you want to compile it as a module, say M here
16525 and read Documentation/modules.txt. The module will be called
16528 SMC IrCC (Experimental)
16529 CONFIG_SMC_IRCC_FIR
16530 Say Y here if you want to build support for the SMC Infrared
16531 Communications Controller. It is used in the Fujitsu Lifebook 635t
16532 and Sony PCG-505TX. If you want to compile it as a module, say M
16533 here and read Documentation/modules.txt. The module will be called
16536 Serial dongle support
16538 Say Y here if you have an infrared device that connects to your
16539 computer's serial port. These devices are called dongles. Then say Y
16540 or M to the driver for your particular dongle below.
16542 Note that the answer to this question won't directly affect the
16543 kernel: saying N will just cause this configure script to skip all
16544 the questions about serial dongles.
16546 ESI JetEye PC Dongle
16548 Say Y here if you want to build support for the Extended Systems
16549 JetEye PC dongle. If you want to compile it as a module, say M here
16550 and read Documentation/modules.txt. The ESI dongle attaches to the
16551 normal 9-pin serial port connector, and can currently only be used
16552 by IrTTY. To activate support for ESI dongles you will have to
16553 start irattach like this: "irattach -d esi".
16555 ACTiSYS IR-220L and IR220L+ dongle
16556 CONFIG_ACTISYS_DONGLE
16557 Say Y here if you want to build support for the ACTiSYS
16558 IR-220L and IR220L+ dongles. If you want to compile it as a module,
16559 say M here and read Documentation/modules.txt. The ACTiSYS dongles
16560 attaches to the normal 9-pin serial port connector, and can
16561 currently only be used by IrTTY. To activate support for ACTiSYS
16562 dongles you will have to start irattach like this:
16563 "irattach -d actisys" or "irattach -d actisys+".
16565 Tekram IrMate 210B dongle
16566 CONFIG_TEKRAM_DONGLE
16567 Say Y here if you want to build support for the Tekram IrMate 210B
16568 dongle. If you want to compile it as a module, say M here
16569 and read Documentation/modules.txt. The Tekram dongle attaches to
16570 the normal 9-pin serial port connector, and can currently only be
16571 used by IrTTY. To activate support for Tekram dongles you will have
16572 to start irattach like this: "irattach -d tekram".
16574 Greenwich GIrBIL dongle
16575 CONFIG_GIRBIL_DONGLE
16576 Say Y here if you want to build support for the Greenwich GIrBIL
16577 dongle. If you want to compile it as a module, say M here and read
16578 Documentation/modules.txt. The Greenwich dongle attaches to the
16579 normal 9-pin serial port connector, and can currently only be used
16580 by IrTTY. To activate support for Greenwich dongles you will have to
16581 insert "irattach -d girbil" in the /etc/irda/drivers script.
16583 Parallax Litelink dongle
16584 CONFIG_LITELINK_DONGLE
16585 Say Y here if you want to build support for the Parallax Litelink
16586 dongle. If you want to compile it as a module, say M here and read
16587 Documentation/modules.txt. The Parallax dongle attaches to the
16588 normal 9-pin serial port connector, and can currently only be used
16589 by IrTTY. To activate support for Parallax dongles you will have to
16590 start irattach like this "irattach -d litelink".
16593 CONFIG_OLD_BELKIN_DONGLE
16594 Say Y here if you want to build support for the Adaptec Airport 1000
16595 and 2000 dongles. If you want to compile it as a module, say M here
16596 and read Documentation/modules.txt. The module will be called
16597 old_belkin.o. Some information is contained in the comments at the
16598 top of drivers/net/irda/old_belkin.c.
16600 VME (Motorola and BVM) support
16602 Say Y here if you want to build a kernel for a 680x0 based VME
16603 board. Boards currently supported include Motorola boards MVME162,
16604 MVME166, MVME167, MVME172, and MVME177. BVME4000 and BVME6000
16605 boards from BVM Ltd are also supported.
16607 MVME162, 166 and 167 support
16609 Say Y to include support for Motorola VME boards. This will build a
16610 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
16611 MVME177 boards. If you select this option you will have to select
16612 the appropriate drivers for SCSI, Ethernet and serial ports later
16615 BVME4000 and BVME6000 support
16617 Say Y to include support for VME boards from BVM Ltd. This will
16618 build a kernel which can run on BVME4000 and BVME6000 boards. If
16619 you select this option you will have to select the appropriate
16620 drivers for SCSI, Ethernet and serial ports later on.
16622 Use write-through caching for 68060 supervisor accesses
16623 CONFIG_060_WRITETHROUGH
16624 The 68060 generally uses copyback caching of recently accessed data.
16625 Copyback caching means that memory writes will be held in an on-chip
16626 cache and only written back to memory some time later. Saying Y
16627 here will force supervisor (kernel) accesses to use writethrough
16628 caching. Writethrough caching means that data is written to memory
16629 straight away, so that cache and memory data always agree.
16630 Writethrough caching is less efficient, but is needed for some
16631 drivers on 68060 based systems where the 68060 bus snooping signal
16632 is hardwired on. The 53c710 SCSI driver is known to suffer from
16635 NCR53C710 SCSI driver for MVME16x
16636 CONFIG_MVME16x_SCSI
16637 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
16638 SCSI controller chip. Almost everyone using one of these boards
16639 will want to say Y to this question.
16641 NCR53C710 SCSI driver for BVME6000
16642 CONFIG_BVME6000_SCSI
16643 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
16644 SCSI controller chip. Almost everyone using one of these boards
16645 will want to say Y to this question.
16647 MVME16x Ethernet support
16649 This is the driver for the Ethernet interface on the Motorola
16650 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
16651 driver for this chip in your kernel. If you want to compile it as
16652 a module, say M here and read Documentation/modules.txt.
16654 BVME6000 Ethernet support
16655 CONFIG_BVME6000_NET
16656 This is the driver for the Ethernet interface on BVME4000 and
16657 BVME6000 VME boards. Say Y here to include the driver for this chip
16658 in your kernel. If you want to compile it as a module, say M here
16659 and read Documentation/modules.txt.
16661 CD2401 support for MVME166/7 serial ports
16663 This is the driver for the serial ports on the Motorola MVME166,
16664 167, and 172 boards. Everyone using one of these boards should say
16667 SCC support for MVME162 serial ports
16669 This is the driver for the serial ports on the Motorola MVME162 and
16670 172 boards. Everyone using one of these boards should say Y here.
16672 SCC support for BVME6000 serial ports
16673 CONFIG_BVME6000_SCC
16674 This is the driver for the serial ports on the BVME4000 and BVME6000
16675 boards from BVM Ltd. Everyone using one of these boards should say
16678 7-Segment Display support
16680 This is the driver for the 7-segment display and LED present on
16681 Sun Microsystems CompactPCI models CP1400 and CP1500.
16683 This driver is also available as a module ( = code which can be
16684 inserted in and removed from the running kernel whenever you want).
16685 The module will be called display7seg.o. If you want to compile it
16686 as a module, say M here and read Documentation/modules.txt.
16688 If you do not have a CompactPCI model CP1400 or CP1500, or
16689 another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
16690 you should say N to this option.
16693 # A couple of things I keep forgetting:
16694 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
16695 # Intel, IRQ, ISDN, Linux, MSDOS, NetWare, NetWinder,
16696 # NFS, PCI, SCSI, SPARC
16697 # two words: file system, hard drive, hard disk, home page,
16698 # user space, web site
16699 # other: it's safe to save; daemon; use --, not - or ---;
16700 # use KB for 1024 bytes, not kB or K.
16703 # This is used by Emacs' spell checker ispell.el:
16705 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp metalab
16706 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
16707 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
16708 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
16709 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
16710 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
16711 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
16712 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
16713 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
16714 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
16715 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
16716 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
16717 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
16718 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
16719 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
16720 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
16721 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
16722 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
16723 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
16724 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
16725 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
16726 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
16727 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
16728 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
16729 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
16730 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
16731 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
16732 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
16733 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
16734 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
16735 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
16736 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
16737 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
16738 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
16739 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
16740 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
16741 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
16742 # LocalWords: carleton DECstation SUNFD JENSEN Noname XXXM SLiRP LILO's amifb
16743 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
16744 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
16745 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
16746 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
16747 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
16748 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
16749 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
16750 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
16751 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
16752 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
16753 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
16754 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
16755 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
16756 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
16757 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
16758 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
16759 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
16760 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles XXXX LVM lvm
16762 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
16763 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
16764 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
16765 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
16766 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
16767 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
16768 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
16769 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
16770 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
16771 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
16772 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
16773 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
16774 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
16775 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
16776 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
16777 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
16778 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
16779 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
16780 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
16781 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
16782 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
16783 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
16784 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
16785 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
16786 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
16787 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
16788 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
16789 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
16790 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
16791 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
16792 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
16793 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
16794 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
16795 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
16796 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
16797 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
16798 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
16799 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
16800 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
16801 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
16802 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
16803 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
16804 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
16805 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
16806 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
16807 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
16808 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
16809 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
16810 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
16811 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
16812 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
16813 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
16814 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
16815 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
16816 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
16817 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
16818 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
16819 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
16820 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
16821 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
16822 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
16823 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
16824 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
16825 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
16826 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
16827 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
16828 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
16829 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
16830 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
16831 # LocalWords: adm Nodename hostname uname Kernelname bootp nmi DI OV StegFS
16832 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
16833 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
16834 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
16835 # LocalWords: Sitor Amtor Pactor GTOR hayes TX TMOUT JFdocs BIGMEM DAC IRQ's
16836 # LocalWords: IDEPCI IDEDMA PDC pdc TRM trm raidtools luthien nuclecu BAGET VR
16837 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
16838 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
16839 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
16840 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
16841 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
16842 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
16843 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
16844 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
16845 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
16846 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
16847 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
16848 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
16849 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
16850 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
16851 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
16852 # LocalWords: charset Inuit Greenlandic Sami Lappish koi Alexey Kuznetsov's sa
16853 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
16854 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
16855 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
16856 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
16857 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
16858 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
16859 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
16860 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
16861 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
16862 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
16863 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
16864 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
16865 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
16866 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
16867 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
16868 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
16869 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
16870 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
16871 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
16872 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
16873 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
16874 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
16875 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
16876 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
16877 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
16878 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
16879 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
16880 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
16881 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
16882 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SNA PAE
16883 # LocalWords: SysKonnect tms sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
16884 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
16885 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
16886 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
16887 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
16888 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
16889 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
16890 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
16891 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
16892 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
16893 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
16894 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
16895 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
16896 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
16897 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
16898 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
16899 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
16900 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
16901 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
16902 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
16903 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
16904 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
16905 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
16906 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
16907 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
16908 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
16909 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
16910 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
16911 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
16912 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
16913 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
16914 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
16915 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
16916 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
16917 # LocalWords: ACTiSYS Dongle dongle dongles esi actisys IrMate tekram BVM MVME
16918 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
16919 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
16920 # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
16921 # LocalWords: IrLPT UIRCC Tecra Strebel jstrebel suse Eichwalder ke INI INIA
16922 # LocalWords: FCP qlogicfc sym isapnp DTLK DoubleTalk rcsys dtlk DMAP SGIVW ar
16923 # LocalWords: dmabuf EcoRadio MUTEFREQ GIrBIL girbil tepkom vol mha diplom PQS
16924 # LocalWords: bmac Microgate SyncLink synclink hdlc excl ioaddr Tane tanep TCQ
16925 # LocalWords: PDS SMALLDOS charsets bigfoot kernelfr mcs cls fw rsvp SKnet sk
16926 # LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd
16927 # LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu
16928 # LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable
16929 # LocalWords: FPEmulator ds vmlinux initialisation discardable pgtable PGT mdw
16930 # LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect
16931 # LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY
16932 # LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC
16933 # LocalWords: mainboard's Digital's alim FastTrak aec PIIXn piix Gayle Eyetech
16934 # LocalWords: Catweasel IDEDOUBLER Powerbook Centris ICSIDE RapIDE OSM HDM IOP
16935 # LocalWords: HDM's OSM's lan FibreChannel ECP autoprobe itg lbl ipmasq cjb IC
16936 # LocalWords: bieringer Caulfield's dreamtime decnet SIOCFIGCONF SIOCGIFCONF
16937 # LocalWords: rtnetlink Endnode Aironet Arlan Telxon ylenurme arlan ACB aeschi
16938 # LocalWords: Sealevel sealevel Cyclom br wanconfig tarball conectiva cycsyn
16939 # LocalWords: devel bazar cyclomx NetGear GA IBMOL Lanstreamer uhci eu efs CYZ
16940 # LocalWords: olympic linuxtr usbcore acm EZUSB downloader EFS XFS INTR op IIC
16941 # LocalWords: heine soundcore JavaStations JavaStation GemTeks TerraTec TODO
16942 # LocalWords: ActiveRadio Standalone terratec Rolf Offermanns rolf offermanns
16943 # LocalWords: Zoran ZR Buz LML CPQ DA cpqarray PPDEV deviceid vlp ppdev atyfb
16944 # LocalWords: AcceleRAID eXtremeRAID NETFILTER Netfilter masqueraded netfilter
16945 # LocalWords: kernelnotes Cardbus PCMCIA's CardBus clgenfb Permedia YAM MMAP
16946 # LocalWords: mmapped ATM atm PVCs SVCs InARP ATMARP neighbour neighbours MPOA
16947 # LocalWords: VCs ENI FPGA Tonga MMF MF UTP printks ZeitNet ZN ZATM uPD SAR PN
16948 # LocalWords: approx NICStAR NICs ForeRunnerLE Madge Collage ATMizer Dxxxx VCI
16949 # LocalWords: ServeRAID IPS ips ipslinux gzip BSDCOMP LZW RAYCS Interphase app
16950 # LocalWords: Tachyon IPHASE Surfboard NextLevel SURFboard jacksonville Tigon
16951 # LocalWords: fventuri adelphia siglercm linuxpower AceNICs Starfire starfire
16952 # LocalWords: ISOC CPiA cpia uss ACPI UDF DirectCD udf CDRW's OSF Manx acpi DM
16953 # LocalWords: Unixware cymru Computone IntelliPort Intelliport computone SI sx
16954 # LocalWords: adbmouse DRI DRM dlabs GMX PLCs Applicom fieldbus applicom int
16955 # LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU
16956 # LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator SBNI tw
16957 # LocalWords: LOGIBUSMOUSE Granch granch sbni Raylink NOHIGHMEM Athlon SIM sim
16958 # LocalWords: hpl Tourrilhes DuraLAN starfile Davicom davicom dmfe auk tms tr
16959 # LocalWords: TokenExpress Belkin Peracom eTek DVDs infradead Cxxx Adlib AV ZX
16960 # LocalWords: NeoMagic CPi CPt Celeron decapsulation Undeletion BFS bfs nVidia
16961 # LocalWords: OnStream Irongate Riva phonedev QuickNet LineJack PhoneJack IXJ
16962 # LocalWords: Quicknet PhoneJACK LineJACK ixj pnpdump Quicknet's Joandi SSID
16963 # LocalWords: aironet quickconfig adhoc btw bap NONCS cardservices Xircom lin
16964 # LocalWords: Netwave AirSurfer netwave HomePNA failover MVP iMacs ALi aktual
16965 # LocalWords: Aladin HIDBP usbkbd KEYBDEV MOUSEDEV JOYDEV EVDEV UAB WhiteHEAT
16966 # LocalWords: Handspring ov DABUSB URB URB's dabusb CRAMFS NFSv ELV IOAPIC WIP
16967 # LocalWords: NLMv SMBus ALGOBIT algo PHILIPSPAR philips elv Velleman velleman
16968 # LocalWords: ALGOPCF Elektor elektor CHARDEV dfx TDFX tdfx Extensa dof gravis
16969 # LocalWords: assasin logitech Overdrive thrustmaster DWave Aureal magellan db
16970 # LocalWords: SpaceTec SpaceOrb SpaceBall spaceorb FLX spaceball turbografx zr
16971 # LocalWords: amiga ESS's WaveWatcher Maxi belkin RW's ata glx GART MPV Baget
16972 # LocalWords: OpenGL Xserver agpgart HOTPLUG CyberPro Integraphics Netwinder
16973 # LocalWords: aty FONTWIDTH eni zatm nicstar ForeRunner OC DECstations DEC's
16974 # LocalWords: PHYsical SUNI reinsertion ChipSAR KVC PHY ClassID iphase iadbg
16975 # LocalWords: DEVS FireWire PCILynx pcilynx LOCALRAM miro's DV RAWIO GRED Mk
16976 # LocalWords: Diffserv DSMARK Ingress Qdisc TCINDEX TMSPCI tmspci Ringode JE
16977 # LocalWords: MADGEMC madgemc TokenRing SMCTR TokenCard smctr Wacom Graphire
16978 # LocalWords: WMFORCE mousedev ConnectTech HandSpring Xirlink IBMCAM ibmcam SN
16979 # LocalWords: DEVICEFS yyy Cymraeg Dwave SIMM JSFLASH JavaStation's multilink
16980 # LocalWords: nsc ircc DDB Vrc CMN TB PROMs Vino rivafb DDC Matroxes MGA TVO
16981 # LocalWords: MAVEN fbdev crtc maven matroxset NTSC PCA SBA AAL SKFP DAS SAS
16982 # LocalWords: skfp Intuos ADMtek's pegasus PLUSB plusb pointopoint mp rio Xeon
16983 # LocalWords: DEVFS devfs dd bs EDSS german TELESPCI FRITZPCI HFC HFCS BDS HST
16984 # LocalWords: ISURF ISAR Saphir HSTSAPHIR Telekom BKM Scitel Quadro SCT Gazel
16985 # LocalWords: SP PRI Hypercope HYSDN Hypercope's hysdn IbssJoinNetTimeout FTDI
16986 # LocalWords: ARCNet Keyspan PDA ADMtek sgalaxy sgbase opl mpuio mpuirq sbio
16987 # LocalWords: sbirq sbdma gus uart mssio mssirq mssdma sscape maui mouirq iph
16988 # LocalWords: CHDLC UPS's usbmouse wacom wmforce keybdev joydev fibre Trunking
16989 # LocalWords: Etherchannel IOC Moxa Intellio moxa SmartIO mxser Mixcom EFI ir
16990 # LocalWords: MIXCOMWD mixcomwd SENDCOMPLETE GMAC iBook gmac OAKNET oaknet PCG
16991 # LocalWords: diffserv irlan irtty toshoboe IrCC Lifebook idex AUTODMA FIP Cxx
16992 # LocalWords: Yenta Databook TCIC FMVJ fmvj NMCLAN LiveWire nmclan XIRC xirc
16993 # LocalWords: loadkeys setfont shm SuperIO soc SOCAL socal FCAL fc fcal COMX
16994 # LocalWords: MultiGate ITConsult comx CMX HiCOMX downloadable hw LoCOMX PROTO
16995 # LocalWords: locomx MixCOM mixcom proto MyriCOM MYRI Sbus myri sbus IBMLS hme
16996 # LocalWords: lanstreamer baseT HAPPYMEAL qfe sunhme SUNLANCE sunlance BigMAC
16997 # LocalWords: SUNBMAC sunbmac QuadEthernet SUNQE qe FastEthernet sunqe DSB PTI
16998 # LocalWords: DSBR dsbr procinfo QLOGICPTI qpti ptisp QLGC qlogicpti se LBA NF
16999 # LocalWords: OPENPROMFS OpenPROM openpromfs OBP OpenBoot flashable Multiboard
17000 # LocalWords: SPARCAUDIO SparcClassic Ultras DBRI Sparcbook sparcaudio SUNBPP
17001 # LocalWords: UltraDMA WDC CRC CONNTRACK IPTABLES iptables nfmark interface's
17002 # LocalWords: tdfxfb TNTx HGA hgafb VERBOSEDEBUG SunTrunking SunSoft XIRTULIP
17003 # LocalWords: ethercards PNIC Macronix MXIC ASIX xircom Mustek MDC gphoto mdc
17004 # LocalWords: CramFs Cramfs uid cramfs AVM's kernelcapi PCIV cdrdao Cdparanoia
17005 # LocalWords: DMX Domex dmx wellington ftdi sio Accton Billington Corega FEter
17006 # LocalWords: MELCO LUA PNA Linksys SNC chkdsk AWACS Webcam RAMFS Ramfs ramfs
17007 # LocalWords: ramfiles MAKEDEV pty WDTPCI APA apa