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.1.x. Be aware that these are
5 # development kernels and need not be completely stable.
7 # Translations of this file available on the WWW:
9 # - http://jf.gee.kyoto-u.ac.jp/JF/JF-ftp/euc/Configure.help.euc
10 # is a Japanese translation, maintained by Tetsuyasu YAMADA
11 # (tetsu@cauchy.nslab.ntt.co.jp).
12 # - http://nevod.perm.su/service/linux/doc/kernel/Configure.help
13 # is a Russian translation, maintained by kaf@linux.nevod.perm.su.
14 # - http://www.linux-kheops.com/traduc/kernels/
15 # has a French translation of the whole kernel, including
16 # Configure.help. This is maintained by David Bourgin
18 # - http://visar.csustan.edu/~carlos/ contains Spanish translations
19 # of the 2.0 kernel documentation files, produced by Carlos Perelló
20 # Marín (fperllo@ehome.encis.es).
21 # - ftp://ftp-pavia1.linux.it/pub/linux/Configure.help
22 # is a work-in-progress effort of the Italian translation team,
23 # currently only for the 2.0 version of this file, maintained
25 # - http://www.cs.net.pl/~cezar/Kernel is the beginning of a Polish
26 # translation of the 2.0 version of this file, maintained by Cezar
27 # Cichocki (cezar@cs.net.pl).
29 # Information about what a kernel is, what it does, how to patch and
30 # compile it and much more is contained in the Kernel-HOWTO, available
31 # via FTP (user: anonymous) from sunsite.unc.edu in the directory
32 # /pub/Linux/docs/HOWTO. Before you start compiling, make sure that
33 # you have the necessary versions of all programs and libraries
34 # required to compile and run this kernel; they are listed in the file
35 # Documentation/Changes. Make sure to read the toplevel kernel README
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-1998 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, filesystems, 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, Documentation/BUG-HUNTING, and
81 Documentation/oops-tracing.txt in the kernel source).
83 Unless you intend to help test and develop a feature or driver that
84 falls into this category, or you have a situation that requires
85 using these features you should probably say N here, which will
86 cause this configure script to present you with fewer choices. If
87 you say Y here, you will be offered the choice of using features or
88 drivers that are currently considered to be in the alpha-test phase.
92 Linux can emulate a math coprocessor (used for floating point
93 operations) if you don't have one. 486DX and Pentium processors have
94 a math coprocessor built in, 486SX and 386 do not, unless you added
95 a 487DX or 387, respectively. (The messages during boot time can
96 give you some hints here ["man dmesg"].) Everyone needs either a
97 coprocessor or this emulation.
99 If you don't have a math coprocessor, you need to say Y here; if you
100 say Y here even though you have a coprocessor, the coprocessor will
101 be used nevertheless. (This behavior can be changed with the kernel
102 command line option "no387", which comes handy if your coprocessor
103 is broken. Try "man bootparam" or see the documentation of your boot
104 loader (lilo or loadlin) about how to pass options to the kernel at
105 boot time. The lilo procedure is also explained in the SCSI-HOWTO,
106 available via FTP (user: anonymous) in
107 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.) This means that it is a
108 good idea to say Y here if you intend to use this kernel on
109 different machines. More information about the internals of Linux
110 math coprocessor emulation can be found in
111 arch/i386/math-emu/README.
113 If you are not sure, say Y; apart from resulting in a 45kB bigger
114 kernel, it won't hurt.
116 Normal PC floppy disk support
118 If you want to use the floppy disk drive(s) of your PC under Linux,
119 say Y. Information about this driver, especially important for IBM
120 Thinkpad users, is contained in drivers/block/README.fd. This file
121 also contains the location of the Floppy driver FAQ as well as
122 location of the fdutils package used to configure additional
123 parameters of the driver at run time.
125 This driver is also available as a module ( = code which can be
126 inserted in and removed from the running kernel whenever you want).
127 The module will be called floppy.o. If you want to compile it as a
128 module, say M here and read Documentation/modules.txt.
132 Saying Y here will allow you to use a portion of your RAM memory as
133 a block device, so that you can make filesystems on it, read and
134 write to it and do all the other things that you can do with normal
135 block devices (such as hard drives). It is usually used to load and
136 store a copy of a minimal root file system off of a floppy into RAM
137 during the initial install of Linux. Note that the kernel command
138 line option "ramdisk=XX" is now obsolete. For details, read
139 Documentation/ramdisk.txt.
141 If you want to compile this as a module ( = code which can be
142 inserted in and removed from the running kernel whenever you want),
143 say M and read Documentation/modules.txt. The module will be called
146 Most normal users won't need the RAM disk functionality, and can
149 Initial RAM disk (initrd) support
150 CONFIG_BLK_DEV_INITRD
151 The initial RAM disk is a RAM disk that is loaded by the boot loader
152 (loadlin or lilo) and that is mounted as root before the normal boot
153 procedure. It is typically used to load modules needed to mount the
154 "real" root file system, etc. See Documentation/initrd.txt for
159 Saying Y here will allow you to use a regular file as a block
160 device; you can then create a file system on that block device and
161 mount it just as you would mount other block devices such as hard drive
162 partitions, CDROM drives or floppy drives.
164 This is useful if you want to check an ISO 9660 file system before
165 burning the CD, or if you want to use floppy images without first
166 writing them to floppy.
168 The loop device driver can also be used to "hide" a filesystem in a
169 disk partition, floppy, or regular file, either using encryption
170 (scrambling the data) or steganography (hiding the data in the low
171 bits of, say, a sound file). This is also safe if the file resides
172 on a remote file server. If you want to do this, you will first have
173 to acquire and install a kernel patch from
174 ftp://ftp.replay.com/pub/crypto/linux/all, and then you need to say
177 Note that alternative ways to use encrypted filesystems are provided
178 by the cfs package, which can be gotten via FTP (user: anonymous)
179 from ftp://ftp.replay.com/pub/crypto/disk/, and the newer tcfs
180 package, available at http://tcfs.dia.unisa.it/. You do not need to
181 say Y here if you want to use one of these. However, using cfs
182 requires saying Y to "NFS filesystem support" below while using tcfs
183 requires applying a kernel patch.
185 To use the loop device, you need the losetup utility and a recent
186 version of the mount program, both contained in the util-linux
187 package (available via FTP (user: anonymous) from
188 ftp://ftp.win.tue.nl/pub/linux/util/).
190 Note that this loop device has nothing to do with the loopback
191 device used for network connections from the machine to itself.
193 If you want to compile this driver as a module ( = code which can be
194 inserted in and removed from the running kernel whenever you want),
195 say M here and read Documentation/modules.txt. The module will be
198 Most users will answer N here.
200 Network Block Device support
202 Saying Y here will allow your computer to be a client for network
203 block devices -- it will be able to use block devices exported by
204 servers (mount filesystems on them etc.). Communication between
205 client and server works over TCP/IP networking, but to the client
206 program this is hidden: it looks like a regular local file access to
207 a special file such as /dev/nd0. It also allows you to run a
208 block-device in userland (making server and client physically the
209 same computer, communicating using the loopback network device).
210 Read Documentation/nbd.txt for more information, especially about
211 where to find the server code.
213 Note that this has nothing to do with the network file system NFS;
214 you can say N here even if you intend to use NFS.
216 If you want to compile this driver as a module ( = code which can be
217 inserted in and removed from the running kernel whenever you want),
218 say M here and read Documentation/modules.txt. The module will be
223 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
225 If you say Y here, you will use the full-featured IDE driver to
226 control up to four IDE interfaces, each being able to serve a
227 "master" and a "slave" device, for a total of up to eight IDE
228 disk/cdrom/tape/floppy drives. People with SCSI-only systems
231 Useful information about large (>540MB) IDE disks, sound card IDE
232 ports, module support, and other topics, is contained in
233 Documentation/ide.txt. For detailed information about hard drives,
234 consult the Disk-HOWTO, available via FTP (user: anonymous) from
235 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. To fine-tune IDE
236 drive/interface parameters for improved performance, look for the
238 sunsite.unc.edu:/pub/Linux/kernel/patches/diskdrives/
240 If you have one or more IDE drives, say Y here. If your system has
241 no IDE drives, or if memory requirements are really tight, you could
242 say N here, and select the "Old hard disk driver" instead to save
243 about 13kB of memory in the kernel.
245 Old hard disk (MFM/RLL/IDE) driver
246 CONFIG_BLK_DEV_HD_ONLY
247 There are two drivers for MFM/RLL/IDE hard disks. Most people use
248 the newer enhanced driver, but this old one is still around for two
249 reasons. Some older systems have strange timing problems and seem to
250 work only with the old driver (which itself does not work with some
251 newer systems). The other reason is that the old driver is smaller,
252 since it lacks the enhanced functionality of the new one. This makes
253 it a good choice for systems with very tight memory restrictions, or
254 for systems with only older MFM/RLL/ESDI drives. Choosing the old
255 driver can save 13kB or so of kernel memory. If you are unsure, then
256 just choose the Enhanced IDE/MFM/RLL driver instead of this one. For
257 more detailed information, read the Disk-HOWTO, available via FTP
258 (user: anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
260 People with SCSI-only systems can say 'N' here.
262 Use old disk-only driver on primary interface
263 CONFIG_BLK_DEV_HD_IDE
264 There are two drivers for MFM/RLL/IDE disks. Most people use just
265 the new enhanced driver by itself. This option however installs the
266 old hard disk driver to control the primary IDE/disk interface in
267 the system, leaving the new enhanced IDE driver to take care of only
268 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
269 having an IDE/ATAPI CDROM or tape drive connected to the primary IDE
270 interface. Choosing this option may be useful for older systems
271 which have MFM/RLL/ESDI controller+drives at the primary port
272 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
273 addresses. Normally, just say N here; you will then use the new
274 driver for all 4 interfaces.
276 People with SCSI-only systems can say 'N' here.
278 Include IDE/ATA-2 DISK support
279 CONFIG_BLK_DEV_IDEDISK
280 This will include enhanced support for MFM/RLL/IDE hard disks. If you
281 have a MFM/RLL/IDE disk, and there is no special reason to use the
282 old hard disk driver instead, say Y. If all your disks are SCSI, say 'N'.
284 If you want to compile this driver as a module ( = code which can be
285 inserted in and removed from the running kernel whenever you want),
286 say M here and read Documentation/modules.txt. The module will be
287 called ide-disk.o. Do not compile this driver as a module if your
288 root filesystem (the one containing the directory /) is located on
289 the IDE disk. If unsure, say Y.
291 Include IDE/ATAPI CDROM support
293 If you have a CDROM drive using the ATAPI protocol, say Y. ATAPI is
294 a newer protocol used by IDE CDROM and TAPE drives, similar to the
295 SCSI protocol. Most new CDROM drives use ATAPI, including the
296 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
297 double(2X), quad(4X), and six(6X) speed drives.
299 If you say Y here, the CDROM drive will be identified at boot time
300 along with other IDE devices, as "hdb" or "hdc", or something
301 similar (check the boot messages with dmesg). If this is your only
302 CDROM drive, you can say N to all other CDROM options, but be sure
303 to say Y or M to "ISO 9660 CDROM filesystem support".
305 Read the CDROM-HOWTO, available via FTP (user: anonymous) in
306 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO and the file
307 Documentation/cdrom/ide-cd. Note that older versions of lilo (the
308 Linux boot loader) cannot properly deal with IDE/ATAPI CDROMs, so
309 install lilo-16 or higher, available from
310 ftp://sunsite.unc.edu/pub/Linux/system/Linux-boot/lilo.
312 If you want to compile the driver as a module ( = code which can be
313 inserted in and removed from the running kernel whenever you want),
314 say M here and read Documentation/modules.txt. The module will be
317 Include IDE/ATAPI TAPE support
318 CONFIG_BLK_DEV_IDETAPE
319 If you have an IDE tape drive using the ATAPI protocol, say Y.
320 ATAPI is a newer protocol used by IDE tape and CDROM drives, similar
321 to the SCSI protocol (but say 'N' if your tape is a SCSI device).
323 If you say Y here, the tape drive will be identified at boot time
324 along with other IDE devices, as "hdb" or "hdc", or something
325 similar, and will be mapped to a character device such as "ht0"
326 (check the boot messages with dmesg). Be sure to consult the
327 drivers/block/ide-tape.c and Documentation/ide.txt files for usage
330 If you want to compile the driver as a module ( = code which can be
331 inserted in and removed from the running kernel whenever you want),
332 say M here and read Documentation/modules.txt. The module will be
335 Include IDE/ATAPI FLOPPY support
336 CONFIG_BLK_DEV_IDEFLOPPY
337 If you have an IDE floppy drive which uses the ATAPI protocol, say
338 Y. ATAPI is a newer protocol used by IDE CDROM/tape/floppy drives,
339 similar to the SCSI protocol. IDE floppy drives include the LS-120
340 and the ATAPI ZIP (ATAPI PD-CD/CDR drives are not supported by this
341 driver; support for PD-CD/CDR drives is available if you say Y to
342 "SCSI emulation support", below).
344 If you say Y here, the FLOPPY drive will be identified along with
345 other IDE devices, as "hdb" or "hdc", or something similar (check
346 the boot messages with dmesg).
348 If you want to compile the driver as a module ( = code which can be
349 inserted in and removed from the running kernel whenever you want),
350 say M here and read Documentation/modules.txt. The module will be
353 SCSI emulation support
354 CONFIG_BLK_DEV_IDESCSI
355 This will provide SCSI host adapter emulation for IDE ATAPI devices,
356 and will allow you to use a SCSI device driver instead of a native
359 This is useful if you have an ATAPI device for which no native
360 driver has been written (for example, an ATAPI PD-CD or CDR drive);
361 you can then use this emulation together with an appropriate SCSI
362 device driver. In order to do this, say Y here and to "SCSI support"
363 and "SCSI generic support", below.
365 Note that this option does NOT allow you to attach SCSI devices to a
366 box that doesn't have a SCSI host adapter installed.
368 If both this SCSI emulation and native ATAPI support are compiled
369 into the kernel, the native support will be used.
371 People with SCSI-only systems should say 'N' here. If unsure, say N.
373 CMD640 chipset bugfix/support
374 CONFIG_BLK_DEV_CMD640
375 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
376 Pentium motherboards, usually in combination with a "Neptune" or
377 "SiS" chipset. Unfortunately, it has a number of rather nasty
378 design flaws that can cause severe data corruption under many common
379 conditions. Say Y here to include code which tries to automatically
380 detect and correct the problems under Linux. This option also
381 enables access to the secondary IDE ports in some CMD640 based
384 This driver will work automatically in PCI based systems (most new
385 systems have PCI slots). But if your system uses VESA local bus
386 (VLB) instead of PCI, you must also supply a kernel boot parameter
387 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
388 bootparam" or see the documentation of your boot loader about how to
389 pass options to the kernel. The lilo procedure is also explained in
390 the SCSI-HOWTO, available via FTP (user: anonymous) in
391 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.)
393 The CMD640 chip is also used on add-in cards by Acculogic, and on
394 the "CSA-6400E PCI to IDE controller" that some people have. For
395 details, read Documentation/ide.txt.
397 People with SCSI-only systems should say 'N' here. If unsure, say Y.
399 CMD640 enhanced support
400 CONFIG_BLK_DEV_CMD640_ENHANCED
401 This option includes support for setting/autotuning PIO modes and
402 prefetch on CMD640 IDE interfaces. For details, read
403 Documentation/ide.txt. If you have a CMD640 IDE interface and your
404 BIOS does not already do this for you, then say Y here. Otherwise
407 RZ1000 chipset bugfix/support
408 CONFIG_BLK_DEV_RZ1000
409 The PC-Technologies RZ1000 chip is used on many common 486 and
410 Pentium motherboards, usually along with the "Neptune" chipset.
411 Unfortunately, it has a rather nasty design flaw that can cause
412 severe data corruption under many conditions. Say Y here to include
413 code which automatically detects and corrects the problem under
414 Linux. This may slow disk throughput by a few percent, but at least
415 things will operate 100% reliably.
417 People with SCSI-only systems can say 'N' here. If unsure, say Y.
419 Generic PCI IDE chipset support
420 CONFIG_BLK_DEV_IDEPCI
421 Enable this for PCI systems which use IDE drive(s).
422 This option helps the IDE driver to automatically detect and
423 configure all PCI-based IDE interfaces in your system.
425 People with SCSI-only systems should say 'N' here. It is safe to
426 say 'Y' to this question.
428 Generic PCI bus-master DMA support
429 CONFIG_BLK_DEV_IDEDMA
430 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
431 is capable of bus-master DMA operation (most Pentium PCI systems),
432 you will want to say Y here to reduce CPU overhead. You can then use
433 the "hdparm" utility to enable DMA for drives for which it was not
434 enabled automatically. By default, DMA is not enabled automatically
435 for these drives, but you can change that by saying Y to the
436 following question "Use DMA by default when available". You can get
437 the latest version of the hdparm utility via anonymous FTP from
438 ftp://sunsite.unc.edu/pub/Linux/system/hardware/.
440 Read the comments at the beginning of drivers/block/idedma.c and the
441 file Documentation/ide.txt for more information.
443 It is safe to say Y to this question.
445 Boot off-board chipsets first support
446 CONFIG_BLK_DEV_OFFBOARD
447 Normally, IDE controllers built into the motherboard (on-board
448 controllers) are assigned to ide0 and ide1 while those on add-in
449 PCI cards (off-board controllers) are relegated to ide2 and ide3.
450 Saying Y to here will reverse the situation, with off-board
451 controllers on ide0/1 and on-board controllers on ide2/3. This
452 can improve the usability of some boot managers such as LILO
453 when booting from a drive on an off-board controller.
454 Note that this will rearrange the order of the hd* devices and
455 may require modification of fstab and other files.
459 Use DMA by default when available
461 Prior to kernel version 2.1.112, Linux used to automatically use
462 DMA for IDE drives and chipsets which support it. Due to concerns
463 about a couple of cases where buggy hardware may have caused damage,
464 the default is now to NOT use DMA automatically. To revert to the
465 previous behaviour, say Y to this question.
467 If you suspect your hardware is at all flakey, say N here.
468 Do NOT email the IDE kernel people regarding this issue!
470 It is nearly always safe to say Y to this question.
472 Other IDE chipset support
474 Say Y here if you want to include enhanced support for various IDE
475 interface chipsets used on motherboards and add-on cards. This
476 enhanced support may be necessary for Linux to be able to access the
477 3rd/4th drives in some systems. It may also enable setting of
478 higher speed I/O rates to improve system performance with these
479 chipsets. Most of these also require special kernel boot parameters
480 to actually turn on the support at runtime.
482 People with SCSI-only systems should say 'N' here.
484 Generic 4 drives/port support
485 CONFIG_BLK_DEV_4DRIVES
486 Certain older chipsets, including the Tekram 690CD, use a
487 single set of I/O ports at 0x1f0 to control up to four drives,
488 instead of the customary two drives per port. Support for this
489 can be enabled at runtime using the "ide0=four" kernel boot
490 parameter if you say Y here.
493 CONFIG_BLK_DEV_DTC2278
494 This driver is enabled at runtime using the "ide0=dtc2278" kernel
495 boot parameter. It enables support for the secondary IDE interface
496 of the DTC-2278 card, and permits faster I/O speeds to be set as
497 well. See the Documentation/ide.txt and dtc2278.c files for more
500 Holtek HT6560B support
501 CONFIG_BLK_DEV_HT6560B
502 This driver is enabled at runtime using the "ide0=ht6560b" kernel
503 boot parameter. It enables support for the secondary IDE interface
504 of the Holtek card, and permits faster I/O speeds to be set as well.
505 See the Documentation/ide.txt and ht6560b.c files for more info.
507 PROMISE DC4030 support (EXPERIMENTAL)
508 CONFIG_BLK_DEV_PDC4030
509 This driver provides support for the secondary IDE interface and
510 cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
511 is known to incur timeouts/retries during heavy I/O to drives
512 attached to the secondary interface. CDROM and TAPE devices are not
513 supported yet. This driver is enabled at runtime using the
514 "ide0=dc4030" kernel boot parameter. See the Documentation/ide.txt
515 and drivers/block/pdc4030.c files for more info.
517 PS/2 ESDI hard disk support
519 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
522 Tekram TRM290 chipset support (EXPERIMENTAL)
523 CONFIG_BLK_DEV_TRM290
524 This driver adds support for bus master DMA transfers
525 using the Tekram TRM290 PCI IDE chip. Volunteers are
526 needed for further tweaking and development.
527 Please read the comments at the top of drivers/block/trm290.c.
529 OPTi 82C621 enhanced support (EXPERIMENTAL)
530 CONFIG_BLK_DEV_OPTI621
531 This is a driver for the OPTi 82C621 EIDE controller.
532 Please read the comments at the top of drivers/block/opti621.c.
534 NS87415 support (EXPERIMENTAL)
535 CONFIG_BLK_DEV_NS87415
536 This driver adds detection and support for the NS87415 chip
537 (used in SPARC64, among others).
539 Please read the comments at the top of drivers/block/ns87415.c.
541 VIA82C586 chipset support (EXPERIMENTAL)
542 CONFIG_BLK_DEV_VIA82C586
543 This adds initial timing settings for VIA (U)DMA onboard ide
544 controllers that are ATA3 compliant. May work with ATA4 systems,
545 but not tested to date.
547 This requires CONFIG_IDEDMA_AUTO to be enabled.
548 Please read the comments at the top of drivers/block/via82C586.c
552 HPT343 chipset support (EXPERIMENTAL)
553 CONFIG_BLK_DEV_HPT343
554 This driver adds up to 4 more eide devices sharing a single interrupt.
555 The HPT343 chipset in it's current form is a non-bootable PCI
556 UDMA controller. This driver requires dynamic tuning of the
557 chipset during the ide-probe at boot. It is reported to support
558 DVD II drives, by the manufacturer.
560 Please read the comments at the top of drivers/block/hpt343.c
563 CONFIG_BLK_DEV_QD6580
564 This driver is enabled at runtime using the "ide0=qd6580" kernel
565 boot parameter. It permits faster I/O speeds to be set. See the
566 files Documentation/ide.txt and qd6580.c for more info.
569 CONFIG_BLK_DEV_UMC8672
570 This driver is enabled at runtime using the "ide0=umc8672" kernel
571 boot parameter. It enables support for the secondary IDE interface
572 of the UMC-8672, and permits faster I/O speeds to be set as well.
573 See the files Documentation/ide.txt and umc8672.c for more info.
576 CONFIG_BLK_DEV_ALI14XX
577 This driver is enabled at runtime using the "ide0=ali14xx" kernel
578 boot parameter. It enables support for the secondary IDE interface
579 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
580 I/O speeds to be set as well. See the files Documentation/ide.txt
581 and ali14xx.c for more info.
585 Very old 8 bit hard disk controllers used in the IBM XT computer
586 will be supported if you say Y here.
588 If you want to compile the driver as a module ( = code which can be
589 inserted in and removed from the running kernel whenever you want),
590 say M here and read Documentation/modules.txt. The module will be
593 It's pretty unlikely that you have one of these: say N.
595 Parallel port IDE device support
597 There are many external CD-ROM and disk devices that connect through
598 your computer's parallel port. Most of them are actually IDE devices
599 using a parallel port IDE adapter. This option enables the PARIDE
600 subsystem which contains drivers for many of these external drives.
601 Read linux/Documentation/paride.txt for more information.
603 If you have said Y to the "Parallel-port support" configuration
604 option, you may share a single port between your printer and other
605 parallel port devices. Answer Y to build PARIDE support into your
606 kernel, or M if you would like to build it as a loadable module. If
607 your parallel port support is in a loadable module, you must build
608 PARIDE as a module. If you built PARIDE support into your kernel,
609 you may still build the individual protocol modules and high-level
610 drivers as loadable modules. If you build this support as a module,
611 it will be called paride.o.
613 To use the PARIDE support, you must say Y or M here and also to at
614 least one high-level driver (e.g. "Parallel port IDE disks",
615 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
616 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
617 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
620 Parallel port IDE disks
622 This option enables the high-level driver for IDE-type disk devices
623 connected through a parallel port. If you chose to build PARIDE
624 support into your kernel, you may answer Y here to build in the
625 parallel port IDE driver, otherwise you should answer M to build
626 it as a loadable module. The module will be called pd.o. You
627 must also have at least one parallel port protocol driver in your
628 system. Among the devices supported by this driver are the SyQuest
629 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
630 hard drives from MicroSolutions.
632 Parallel port ATAPI CD-ROMs
634 This option enables the high-level driver for ATAPI CD-ROM devices
635 connected through a parallel port. If you chose to build PARIDE
636 support into your kernel, you may answer Y here to build in the
637 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
638 build it as a loadable module. The module will be called pcd.o. You
639 must also have at least one parallel port protocol driver in your
640 system. Among the devices supported by this driver are the
641 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
642 you have such a CD-ROM drive, you should also say Y or M to "ISO 9660
643 CDROM filesystem support" below, because that's the filesystem used
646 Parallel port ATAPI disks
648 This option enables the high-level driver for ATAPI disk devices
649 connected through a parallel port. If you chose to build PARIDE
650 support into your kernel, you may answer Y here to build in the
651 parallel port ATAPI disk driver, otherwise you should answer M
652 to build it as a loadable module. The module will be called pf.o.
653 You must also have at least one parallel port protocol driver in
654 your system. Among the devices supported by this driver are the
655 MicroSolutions backpack PD/CD drive and the Imation Superdisk
658 Parallel port ATAPI tapes
660 This option enables the high-level driver for ATAPI tape devices
661 connected through a parallel port. If you chose to build PARIDE
662 support into your kernel, you may answer Y here to build in the
663 parallel port ATAPI disk driver, otherwise you should answer M
664 to build it as a loadable module. The module will be called pt.o.
665 You must also have at least one parallel port protocol driver in
666 your system. Among the devices supported by this driver is the
667 parallel port version of the HP 5GB drive.
669 Parallel port generic ATAPI devices
671 This option enables a special high-level driver for generic ATAPI
672 devices connected through a parallel port. The driver allows user
673 programs, such as cdrecord, to send ATAPI commands directly to a
674 device. If you chose to build PARIDE support into your kernel, you
675 may answer Y here to build in the parallel port generic ATAPI driver,
676 otherwise you should answer M to build it as a loadable module.
677 The module will be called pg.o. You must also have at least one
678 parallel port protocol driver in your system. This driver
679 implements an API loosely related to the generic SCSI driver.
680 See /usr/include/linux/pg.h for details.
682 You can obtain the most recent version of cdrecord from
683 ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/ . Versions 1.6.1a3 and
684 later fully support the pg driver.
688 This option enables support for the ATEN EH-100 parallel port IDE
689 protocol. This protocol is used in some inexpensive low performance
690 parallel port kits made in Hong Kong. If you chose to build PARIDE
691 support into your kernel, you may answer Y here to build in the
692 protocol driver, otherwise you should answer M to build it as a
693 loadable module. The module will be called aten.o. You must also
694 have a high-level driver for the type of device that you want to
697 MicroSolutions backpack protocol
699 This option enables support for the MicroSolutions backpack
700 parallel port IDE protocol. If you chose to build PARIDE support
701 into your kernel, you may answer Y here to build in the protocol
702 driver, otherwise you should answer M to build it as a loadable
703 module. The module will be called bpck.o. You must also have
704 a high-level driver for the type of device that you want to support.
706 DataStor Commuter protocol
708 This option enables support for the Commuter parallel port IDE
709 protocol from DataStor. If you chose to build PARIDE support
710 into your kernel, you may answer Y here to build in the protocol
711 driver, otherwise you should answer M to build it as a loadable
712 module. The module will be called comm.o. You must also have
713 a high-level driver for the type of device that you want to support.
715 DataStor EP-2000 protocol
717 This option enables support for the EP-2000 parallel port IDE
718 protocol from DataStor. If you chose to build PARIDE support
719 into your kernel, you may answer Y here to build in the protocol
720 driver, otherwise you should answer M to build it as a loadable
721 module. The module will be called dstr.o. You must also have
722 a high-level driver for the type of device that you want to support.
724 Shuttle EPAT/EPEZ protocol
726 This option enables support for the EPAT parallel port IDE protocol.
727 EPAT is a parallel port IDE adapter manufactured by Shuttle
728 Technology and widely used in devices from major vendors such as
729 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
730 PARIDE support into your kernel, you may answer Y here to build in
731 the protocol driver, otherwise you should answer M to build it as a
732 loadable module. The module will be called epat.o. You must also
733 have a high-level driver for the type of device that you want to
736 Shuttle EPIA protocol
738 This option enables support for the (obsolete) EPIA parallel port
739 IDE protocol from Shuttle Technology. This adapter can still be
740 found in some no-name kits. If you chose to build PARIDE support
741 into your kernel, you may answer Y here to build in the protocol
742 driver, otherwise you should answer M to build it as a loadable
743 module. The module will be called epia.o. You must also have a
744 high-level driver for the type of device that you want to support.
748 This option enables support for the TD-2000 parallel port IDE
749 protocol from Fidelity International Technology. This is a simple
750 (low speed) adapter that is used in some portable hard drives. If
751 you chose to build PARIDE support into your kernel, you may answer Y
752 here to build in the protocol driver, otherwise you should answer M
753 to build it as a loadable module. The module will be called ktti.o.
754 You must also have a high-level driver for the type of device that
759 This option enables support for the TD-3000 parallel port IDE
760 protocol from Fidelity International Technology. This protocol is
761 used in newer models of their portable disk, CD-ROM and PD/CD
762 devices. If you chose to build PARIDE support into your kernel, you
763 may answer Y here to build in the protocol driver, otherwise you
764 should answer M to build it as a loadable module. The module will be
765 called fit3.o. You must also have a high-level driver for the type
766 of device that you want to support.
768 FreeCom power protocol
770 This option enables support for the Freecom power parallel port IDE
771 protocol. If you chose to build PARIDE support into your kernel, you
772 may answer Y here to build in the protocol driver, otherwise you
773 should answer M to build it as a loadable module. The module will be
774 called frpw.o. You must also have a high-level driver for the type
775 of device that you want to support.
777 KingByte KBIC-951A/971A protocols
779 This option enables support for the KBIC-951A and KBIC-971A parallel
780 port IDE protocols from KingByte Information Corp. KingByte's
781 adapters appear in many no-name portable disk and CD-ROM products,
782 especially in Europe. If you chose to build PARIDE support into your
783 kernel, you may answer Y here to build in the protocol driver,
784 otherwise you should answer M to build it as a loadable module. The
785 module will be called kbic.o. You must also have a high-level driver
786 for the type of device that you want to support.
790 This option enables support for the "PHd" parallel port IDE protocol
791 from KT Technology. This is a simple (low speed) adapter that is
792 used in some 2.5" portable hard drives. If you chose to build PARIDE
793 support into your kernel, you may answer Y here to build in the
794 protocol driver, otherwise you should answer M to build it as a
795 loadable module. The module will be called ktti.o. You must also
796 have a high-level driver for the type of device that you want to
799 OnSpec 90c20 protocol
801 This option enables support for the (obsolete) 90c20 parallel port
802 IDE protocol from OnSpec (often marketed under the ValuStore brand
803 name). If you chose to build PARIDE support into your kernel, you
804 may answer Y here to build in the protocol driver, otherwise you
805 should answer M to build it as a loadable module. The module will
806 be called on20.o. You must also have a high-level driver for the
807 type of device that you want to support.
809 OnSpec 90c26 protocol
811 This option enables support for the 90c26 parallel port IDE protocol
812 from OnSpec Electronics (often marketed under the ValuStore brand
813 name). If you chose to build PARIDE support into your kernel, you
814 may answer Y here to build in the protocol driver, otherwise you
815 should answer M to build it as a loadable module. The module will
816 be called on26.o. You must also have a high-level driver for the
817 type of device that you want to support.
819 Multiple devices driver support
821 This driver lets you combine several hard disk partitions into one
822 logical block device. This can be used to combine several redundant
823 hard disks to a RAID1/4/5 device so as to provide protection against
824 hard disk failures. More information and the necessary tools are
825 available over FTP (user: anonymous) from
826 ftp://sweet-smoke.ufr-info-p7.ibp.fr/pub/Linux in the md package and
827 the md-FAQ. Please read drivers/block/README.md and the relevant
828 section of the Disk-HOWTO, available via FTP (user: anonymous) from
829 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If unsure, say N.
833 If you say Y here, then your multiple devices driver will be able to
834 use the so-called linear mode, i.e. it will combine the hard disk
835 partitions by simply appending one to the other. If you want to
836 compile this as a module ( = code which can be inserted in and
837 removed from the running kernel whenever you want), say M here and
838 read Documentation/modules.txt. The module will be called
839 linear.o. If unsure, say Y.
841 RAID-0 (striping) mode
843 If you say Y here, then your multiple devices driver will be able to
844 use the so-called raid0 mode, i.e. it will combine the hard disk
845 partitions into one logical device in such a fashion as to fill them
846 up evenly, one chunk here and one chunk there. This will increase
847 the throughput rate if the partitions reside on distinct disks. If
848 you want to compile this as a module ( = code which can be inserted
849 in and removed from the running kernel whenever you want), say M
850 here and read Documentation/modules.txt. The module will be called
851 raid0.o. If unsure, say Y.
853 Are you using a crosscompiler
855 Set this if you are using another architecture to compile the
856 kernel for your MIPS machine.
858 Support for Acer PICA 1 chipset
860 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
861 kernel that runs on these, say Y here. For details about Linux on
862 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
863 http://lena.fnet.fr/ (To browse the WWW, you need to have access to
864 a machine on the Internet that has a program like lynx or
867 Support for Algorithmics P4032
869 This is an evaluation board of the British company Algorithmics. The
870 board uses the R4300 and a R5230 CPUs. For more information about
871 this board see www.algor.co.uk.
873 RAID-1 (mirroring) mode
875 A RAID-1 set consists of several disk drives which are exact copies
876 of each other. In the event of a mirror failure, the RAID driver
877 will continue to use the operational mirrors in the set, providing
878 an error free MD (multiple device) to the higher levels of the
879 kernel. In a set with N drives, the available space is the capacity
880 of a single drive, and the set protects against a failure of (N - 1)
883 Raidtools, a set of user-space tools which create and maintain
884 RAID1/4/5 sets, is available at:
885 ftp://ftp.kernel.org/pub/linux/daemons/raid
886 http://luthien.nuclecu.unam.mx/~miguel/raid
888 If you want to use such a RAID-1 set, say Y. This code is also
889 available as a module called raid1.o ( = code which can be inserted
890 in and removed from the running kernel whenever you want). If you
891 want to compile it as a module, say M here and read
892 Documentation/modules.txt. If unsure, say Y.
894 Boot support (linear, striped)
896 To boot with an initial linear or striped md device you have to say
897 Y here. For lilo and loadlin options see Documentation/md.txt.
901 A RAID-5 set of N drives with a capacity of C MB per drive provides
902 the capacity of C * (N - 1) drives, and protects against a failure
903 of a single drive. For a given sector (row) number, (N - 1) drives
904 contain data sectors, and one drive contains the parity protection.
905 For a RAID-4 set, the parity blocks are present on a single drive,
906 while a RAID-5 set distributes the parity across the drives in one
907 of the available parity distribution methods.
909 Raidtools, a set of user-space tools which create and maintain
910 RAID1/4/5 sets, is available at:
911 ftp://ftp.kernel.org/pub/linux/daemons/raid
912 http://luthien.nuclecu.unam.mx/~miguel/raid
914 If you want to use such a RAID-5 set, say Y. This code is also
915 available as a module called raid5.o ( = code which can be inserted
916 in and removed from the running kernel whenever you want). If you
917 want to compile it as a module, say M here and read
918 Documentation/modules.txt. If unsure, say Y.
920 Support for Mips Magnum 4000
921 CONFIG_MIPS_MAGNUM_4000
922 This is a machine with a R4000 100 MHz CPU. To compile a Linux
923 kernel that runs on these, say Y here. For details about Linux on
924 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
925 http://lena.fnet.fr/ (To browse the WWW, you need to have access to
926 a machine on the Internet that has a program like lynx or netscape).
928 Support for Olivetti M700
930 This is a machine with a R4000 100 MHz CPU. To compile a Linux
931 kernel that runs on these, say Y here. For details about Linux on
932 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
933 http://lena.fnet.fr/ (To browse the WWW, you need to have access to
934 a machine on the Internet that has a program like lynx or netscape).
938 Give the type of your machine's MIPS CPU. For this question,
939 it suffices to give a unique prefix of the option you want to
940 choose. In case of doubt select the R3000 CPU. This kernel will
941 run on other MIPS machines but with slightly reduced performance.
943 Compile the kernel into the ECOFF object format
945 Some machines require a kernel in the ECOFF format. You will have to
946 Choose this option for example if you want to a Mips Magnum 3000 or a
947 DECstation over network.
949 Generate little endian code
950 CONFIG_CPU_LITTLE_ENDIAN
951 Some MIPS machines can be configured for either little or big endian
952 byte order. Both modes require different kernels. Say yes if your
953 machine is little endian, no if it's a big endian machine.
955 Kernel support for IRIX binaries
957 This option enables the kernel support for IRIX binaries. Running
958 IRIX binaries additionally requires IRIX libraries.
962 Unless you really know what you are doing, you should say Y here.
963 The reason is that some programs need kernel networking support even
964 when running on a stand-alone machine that isn't connected to any
965 other computer. If you are upgrading from an older kernel, you
966 should consider updating your networking tools too because changes
967 in the kernel and the tools often go hand in hand. The tools are
968 contained in the package net-tools, the location and version number
969 of which are given in Documentation/Changes.
973 If you say Y here, you will be able to set multiple network
974 addresses on the same low-level network device driver. This is
975 typically used for services that act differently based on the
976 address they listen on (e.g. "multihosting" or "virtual domains" or
977 "virtual hosting services" on the web server apache and the ftp
978 server wuftpd -- read the Virtual-Services-HOWTO, available via FTP
979 (user: anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO)
980 or for connecting to different logical networks through the same
981 physical interface (most commonly an Ethernet networking card). See
982 Documentation/networking/alias.txt for more info.
984 This is the generic part, later when configuring network protocol
985 options you will be asked for protocol-specific aliasing support,
986 and you will have to say Y to at least one of them, most likely to
987 "IP: aliasing support". If you need this feature (for any protocol,
988 like IP) say Y; if unsure, say N.
992 The Linux Socket Filter is derived from the Berkeley Packet Filter.
993 If you say Y here, user-space programs can attach a filter to any
994 socket and thereby tell the kernel that it should allow or disallow
995 certain types of data to get through the socket. Linux Socket
996 Filtering works on all socket types except TCP for now. See the text
997 file linux/Documentation/networking/filter.txt for more information.
1002 A firewall is a computer which protects a local network from the
1003 rest of the world: all traffic to and from computers on the local
1004 net is inspected by the firewall first, and sometimes blocked or
1005 modified. The type of firewall you'll get if you say Y here is
1006 called a "packet filter": it can block network traffic based on
1007 type, origin and destination. By contrast, "proxy-based" firewalls
1008 are more secure but more intrusive and more bothersome to set up;
1009 they inspect the network traffic much more closely, modify it and
1010 have knowledge about the higher level protocols, which packet
1011 filters lack. They also often require changes in the programs
1012 running on the local clients. Proxy-based firewalls don't need
1013 support by the kernel, but they are often combined with packet
1014 filters, which only works if you say Y here.
1016 If you want to configure your Linux box as a packet filter firewall
1017 for a local network, say Y here. If your local network is TCP/IP
1018 based, you will then also have to say Y to "IP: firewalling", below.
1020 You also need to say Y here and to "IP firewalling" below in order
1021 to be able to use IP masquerading (i.e. local computers can chat
1022 with an outside host, but that outside host is made to think that it
1023 is talking to the firewall box -- makes the local network completely
1024 invisible to the outside world and avoids the need to allocate
1025 globally valid IP host addresses for the machines on the local net)
1026 and IP transparent proxying (makes the computers on the local
1027 network think they're talking to a remote computer, while in reality
1028 the traffic is redirected by your Linux firewall to a local proxy
1031 Make sure to say N to "Fast switching" below if you intend to say Y
1034 Chances are that you should say Y here for every machine which is
1035 run as a router and N for every regular host. If unsure, say N.
1037 SYN flood protection
1039 Normal TCP/IP networking is open to an attack known as "SYN flooding".
1040 This denial-of-service attack prevents legitimate remote users from
1041 being able to connect to your computer and requires very little work
1042 from the attacker, who can operate from anywhere on the Internet.
1044 SYN cookies provide protection against this type of attack. If you
1045 say Y here, the TCP/IP stack will use a cryptographic challenge
1046 protocol known as "SYN cookies" to enable legitimate users to
1047 continue to connect, even when your machine is under attack. There
1048 is no need for the legitimate users to change their TCP/IP software;
1049 SYN cookies work transparently to them. For technical information
1050 about SYN cookies, check out
1051 ftp://koobera.math.uic.edu/pub/docs/syncookies-archive.
1053 If you are SYN flooded, the source address reported by the kernel is
1054 likely to have been forged by the attacker; it is only reported as
1055 an aid in tracing the packets to their actual source and should not
1056 be taken as absolute truth.
1058 If you say Y here, note that SYN cookies aren't enabled by default;
1059 you can enable them by saying Y to "/proc filesystem support" and
1060 "Sysctl support" below and executing the command
1062 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
1064 at boot time after the proc filesystem has been mounted.
1068 Sun floppy controller support
1069 CONFIG_BLK_DEV_SUNFD
1070 This is support for floppy drives on Sun SPARC workstations. Say Y
1071 if you have a floppy drive, otherwise N. Easy.
1075 Find out what type of Alpha motherboard you have. You will probably
1076 want to read the Linux/Alpha home page on the WWW at
1077 http://www.azstarnet.com/~axplinux/ (to browse the WWW, you need to
1078 have access to a machine on the Internet that has a program like
1079 lynx or netscape) and also the Alpha-HOWTO, available via FTP (user:
1080 anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. For this
1081 question, it suffices to give a unique prefix of the option you want
1082 to choose. The choices:
1083 ** Avanti: This is for Mustang (AS200), M3 (AS250), Avanti (AS400)
1084 AlphaStations. These usually come with a TGA graphics adapter,
1085 so you'll want to say Y to "TGA Console support", below, if you
1087 ** Alpha-XL: A.k.a. "Windows NT Dream Machine" :-) These usually
1088 come with a TGA graphics adapter, so you'll want to say Y to "TGA
1089 Console support", below, if you have one of these.
1090 ** Jensen: a.k.a. DEC 2000 a.k.a. DECpc AXP 150, the oldest Alpha
1091 PC; it sports an EISA bus. The boot process on Jensen machines is
1092 difficult (no booting from floppies, MILO doesn't work). You need
1093 to have access to a second Linux workstation. The Linux/Alpha
1094 FAQ, accessible from the above mentioned WWW page, has details.
1095 ** Noname: a.k.a. AXPpci33, a PCI-bus based board using the 21066
1096 Alpha CPU, running at either 166 or 233 MHz. You also want to
1097 choose this option if you have a UDB (Universal Desktop Box
1098 a.k.a. Multia) machine.
1099 ** Cabriolet: also called AlphaPC64, a PCI-bus based board using the
1100 21064 Alpha CPU typically running at 275 or 300 MHz.
1101 ** EB66: "Evaluation Board"
1102 ** EB66+: "Evaluation Board"
1104 ### Add info about Platform2000, EB164, etc.
1107 Using SRM as bootloader
1109 There are two different types of booting firmware on Alphas: SRM,
1110 which is command line driven, and ARC, which uses menus and arrow
1111 keys. Details about the Linux/Alpha booting process are contained in
1112 the Linux/Alpha FAQ, accessible on the WWW from
1113 http://www.azstarnet.com/~axplinux/ (To browse the WWW, you need to
1114 have access to a machine on the Internet that has a program like
1117 The usual way to load Linux on an Alpha machine is to use MILO
1118 (a bootloader that lets you pass command line parameters to the
1119 kernel just like lilo does for the x86 architecture) which can be
1120 loaded either from ARC or can be installed directly as a permanent
1121 firmware replacement from floppy (which requires changing a certain
1122 jumper on the motherboard). If you want to do either of these, say N
1123 here. If MILO doesn't work on your system (true for Jensen
1124 motherboards), you can bypass it altogether and boot Linux directly
1125 from an SRM console; say Y here in order to do that. Note that you
1126 won't be able to boot from an IDE disk using SRM.
1130 Non-standard serial port support
1131 CONFIG_SERIAL_NONSTANDARD
1132 Say Y here if you have any non-standard serial boards -- boards
1133 which aren't supported using the standard "dumb" serial driver.
1134 This includes intelligent serial boards such as Cyclades,
1135 Digiboards, etc. These are usually used for systems that need many
1136 serial ports because they serve many terminals or dial-in
1137 connections. Note that the answer to this question won't directly
1138 affect the kernel: saying N will just cause this configure script to
1139 skip all the questions about non-standard serial boards. Most people
1142 Extended dumb serial driver options
1143 CONFIG_SERIAL_EXTENDED
1144 If you wish to use any non-standard features of the standard "dumb"
1145 driver, say Y here. This includes HUB6 support, shared serial
1146 interrupts, special multiport support, support for more than the
1147 four COM 1/2/3/4 boards, etc. Note that the answer to this question
1148 won't directly affect the kernel: saying N will just cause this
1149 configure script to skip all the questions about serial driver
1150 options. If unsure, say N.
1152 Support more than 4 serial ports
1153 CONFIG_SERIAL_MANY_PORTS
1154 Say Y here if you have dumb serial boards other than the four
1155 standard COM 1/2/3/4 ports. This may happen if you have an AST
1156 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
1157 via FTP (user: anonymous) from
1158 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini), or other custom
1159 serial port hardware which acts similar to standard serial port
1160 hardware. If you only use the standard COM 1/2/3/4 ports, you can
1161 say N here to save some memory. You can also say Y if you have an
1162 "intelligent" multiport card such as Cyclades, Digiboards, etc.
1164 Support for sharing serial interrupts
1165 CONFIG_SERIAL_SHARE_IRQ
1166 Some serial boards have hardware support which allows multiple dumb
1167 serial ports on the same board to share a single IRQ. To enable
1168 support for this in the serial driver, say Y here.
1170 Auto detect IRQ on standard ports (unsafe)
1171 CONFIG_SERIAL_DETECT_IRQ
1172 Say Y here if you want the kernel to try to guess which IRQ
1173 to use for your serial port.
1175 This is considered unsafe; it is far better to configure the IRQ in
1176 a boot script using the setserial command.
1180 Support special multiport boards
1181 CONFIG_SERIAL_MULTIPORT
1182 Some multiport serial ports have special ports which are used to
1183 signal when there are any serial ports on the board which need
1184 servicing. Say Y here to enable the serial driver to take advantage
1185 of those special I/O ports.
1187 SGI Zilog85C30 serial support
1189 If you want to use your SGI's built-in serial ports under Linux, say Y.
1191 SGI graphics support
1193 If you have an SGI machine and you want to compile the graphic drivers
1194 select this option. This will include the code for the /dev/graphics
1195 and /dev/gfx drivers into the kernel for supporting the virtualized
1196 access to your graphics hardware.
1198 Remote GDB kernel debugging
1200 This enables remote debugging support for the MIPS kernel. Enabling
1201 this option enlarges you kernel image disk size by several megabytes
1202 and requires a machine with more than 16mb, better 32mb RAM to avoid
1203 excessive linking time.
1205 Support the Bell Technologies HUB6 card
1207 Say Y here to enable support in the dumb serial driver to support
1212 Find out whether you have a PCI motherboard. PCI is the name of a
1213 bus system, i.e. the way the CPU talks to the other stuff inside
1214 your box. Other bus systems are ISA, EISA, Microchannel (MCA) or
1215 VESA. If you have PCI, say Y, otherwise N. The PCI-HOWTO, available
1216 via FTP (user: anonymous) in
1217 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, contains valuable
1218 information about which PCI hardware does work under Linux and which
1221 If some of your PCI devices don't work and you get a warning during
1222 boot time ("man dmesg"), please follow the instructions at the top
1223 of include/linux/pci.h.
1227 If you have enabled PCI bus support above, you probably want to
1228 allow Linux to use your PCI BIOS to detect the PCI devices and
1229 determine their configuration. Note: some old PCI motherboards have
1230 BIOS bugs and may crash if you say Y here -- for such motherboards,
1231 you should say N here and say Y to "PCI direct access support"
1234 Except for some special cases (embedded systems with no BIOS), you
1235 probably should say Y here.
1237 PCI direct access support
1239 If you don't want to use the PCI BIOS (e.g., because you run some
1240 embedded system with no BIOS at all) or Linux says it cannot use
1241 your PCI BIOS, you can enable direct PCI hardware here. It might fail
1242 if your machine is based on some unusual chipset, but it usually
1243 works. If both PCI BIOS and direct PCI access are enabled, the use
1244 of BIOS is preferred. If unsure, say Y.
1248 If you have a broken BIOS, it may fail to set up the PCI bus in a
1249 correct or optimal fashion. Saying Y here will correct that problem.
1250 If your BIOS is fine you can say N here for a very slightly smaller
1251 kernel. If unsure, say Y.
1253 PCI bridge optimization (experimental)
1255 This can improve access times for some hardware devices if you have
1256 a really broken BIOS and your computer uses a PCI bus system. Set to
1257 Y if you think it might help, but try turning it off if you
1258 experience any problems with the PCI bus. N is the safe answer.
1260 Backward-compatible /proc/pci
1262 Older kernels supported a /proc/pci file containing brief textual
1263 descriptions of all PCI devices in the system. Several programs
1264 tried to parse this file, so it became almost impossible to add new
1265 fields without breaking compatibility. So a new /proc interface to
1266 PCI (/proc/bus/pci) has been implemented and the old one is
1267 supported for compatibility reasons only; you'll get the old one (in
1268 addition to the new one) if you say Y here and to "/proc filesystem
1269 support", below. If unsure, say Y.
1271 If you say Y here and to the "/proc filesystem support" below, you
1272 will get a directory /proc/pci with information about your PCI
1273 hardware. If unsure, say Y.
1277 MicroChannel Architecture is found in some IBM PS/2 machines and
1278 laptops. It is a bus system similar to PCI or ISA. See
1279 Documentation/mca.txt (and especially the web page given there)
1280 before attempting to build an MCA bus kernel. Note that this is
1281 still experimental code.
1285 Inter Process Communication is a suite of library functions and
1286 system calls which let processes (= running programs) synchronize
1287 and exchange information. It is generally considered to be a good
1288 thing, and some programs won't run unless you say Y here. In
1289 particular, if you want to run the DOS emulator dosemu under Linux
1290 (read the DOSEMU-HOWTO, available via FTP (user: anonymous) in
1291 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO), you'll need to say Y
1294 You can find documentation about IPC with "info ipc" and also in
1295 section 6.4 of the Linux Programmer's Guide, available via FTP
1296 (user: anonymous) from
1297 ftp://sunsite.unc.edu/pub/Linux/docs/LDP/programmers-guide.
1299 Saying Y here enlarges your kernel by about 7kB. Just say Y.
1301 BSD Process Accounting
1302 CONFIG_BSD_PROCESS_ACCT
1303 If you say Y here, a user level program will be able to instruct the
1304 kernel (via a special system call) to write process accounting
1305 information to a file: whenever a process exits, information about
1306 that process will be appended to the file by the kernel. The
1307 information includes things such as creation time, owning user,
1308 command name, memory usage, controlling terminal etc. (the complete
1309 list is in the struct acct in include/linux/acct.h). It is up to the
1310 user level program to do useful things with this information. This
1311 is generally a good idea, so say Y.
1315 The sysctl interface provides a means of dynamically changing
1316 certain kernel parameters and variables on the fly without requiring
1317 a recompile of the kernel or reboot of the system. The primary
1318 interface consists of a system call, but if the /proc filesystem is
1319 enabled, a tree of modifiable sysctl entries will be generated
1320 beneath the /proc/sys directory. They are explained in the files in
1321 Documentation/sysctl/. Note that enabling this option will enlarge
1322 the kernel by at least 8kB. As it is generally a good thing, you
1323 should say Y here unless building a kernel for install/rescue disks
1324 or your system is very limited in memory.
1326 Kernel support for ELF binaries
1328 ELF (Executable and Linkable Format) is a format for libraries and
1329 executables used across different architectures and operating
1330 systems. Saying Y here will enable your kernel to run ELF binaries and
1331 enlarge it by about 2kB. ELF support under Linux has now all but
1332 replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
1333 because it is portable (this does *not* mean that you will be able
1334 to run executables from different architectures or operating
1335 systems!) and makes building run-time libraries very easy. Many new
1336 executables are distributed solely in ELF format. You definitely
1339 Information about ELF is on the WWW at
1340 http://www.sjc.ox.ac.uk/users/barlow/elf-howto.html (to browse the
1341 WWW, you need to have access to a machine on the Internet that has a
1342 program like lynx or netscape). If you find that after upgrading
1343 from Linux kernel 1.2 and saying Y here, you still can't run any ELF
1344 binaries (they just crash), then you'll have to install the newest
1345 ELF runtime libraries, including ld.so (check the file
1346 Documentation/Changes for location and latest version).
1348 If you want to compile this as a module ( = code which can be
1349 inserted in and removed from the running kernel whenever you want),
1350 say M here and read Documentation/modules.txt. The module will be
1351 called binfmt_elf.o. Saying M or N here is dangerous because some
1352 crucial programs on your system might be in ELF format.
1354 Kernel support for A.OUT binaries
1356 A.out (Assembler.OUTput) is a set of formats for libraries and
1357 executables used in the earliest versions of UNIX. Linux used the
1358 a.out formats QMAGIC and ZMAGIC until they were replaced with the
1361 As more and more programs are converted to ELF, the use for a.out
1362 will gradually diminish. If you disable this option it will reduce
1363 your kernel by one page. This is not much and by itself does not
1364 warrant removing support. However its removal is a good idea if you
1365 wish to ensure that absolutely none of your programs will use this
1366 older executable format. If you don't know what to answer at this
1367 point then answer Y. If someone told you "You need a kernel with
1368 QMAGIC support" then you'll have to say Y here. You may answer M to
1369 compile a.out support as a module and later load the module when you
1370 want to use a program or library in a.out format. The module will be
1371 called binfmt_aout.o. Saying M or N here is dangerous though,
1372 because some crucial programs on your system might still be in A.OUT
1375 Kernel support for JAVA binaries (obsolete)
1377 JAVA(tm) is an object oriented programming language developed by
1378 SUN; JAVA programs are compiled into "JAVA bytecode" binaries which
1379 can then be interpreted by run time systems on many different
1380 architectures and operating systems. These JAVA binaries are
1381 becoming a universal executable format.
1383 If you want to execute JAVA binaries, read the Java on Linux HOWTO,
1384 available via FTP (user: anonymous) at
1385 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You will then need to
1386 install the run time system contained in the Java Developers Kit
1387 (JDK) as described in the HOWTO. This is completely independent of
1388 the Linux kernel and you do NOT need to say Y here for this to work.
1390 Saying Y here allows you to execute a JAVA bytecode binary just like
1391 any other Linux program: by simply typing in its name. (You also
1392 need to have the JDK installed for this to work). As more and more
1393 Java programs become available, the use for this will gradually
1394 increase. You can even execute HTML files containing JAVA applets
1395 (= JAVA binaries) if those files start with the string
1396 "<!--applet-->". If you want to use this, say Y here and read
1397 Documentation/java.txt.
1399 If you disable this option it will reduce your kernel by about 4kB.
1400 This is not much and by itself does not warrant removing support.
1401 However its removal is a good idea if you do not have the JDK
1402 installed. You may answer M for module support and later load the
1403 module when you install the JDK or find an interesting Java program
1404 that you can't live without. The module will be called
1407 The complete functionality of this Java support is also provided by
1408 the more general option "Kernel support for MISC binaries",
1409 below. This option is therefore considered obsolete and you should
1410 say N here and Y to "Kernel support for MISC binaries" if you're
1411 interested in transparently executing Java programs.
1413 Kernel support for Linux/Intel ELF binaries
1415 Say Y here if you want to be able to execute Linux/Intel ELF
1416 binaries just like native Alpha binaries on your Alpha machine. For
1417 this to work, you need to have the emulator /usr/bin/em86 in place.
1418 You may answer M to compile the emulation support as a module and
1419 later load the module when you want to use a Linux/Intel binary. The
1420 module will be called binfmt_em86.o. If unsure, say Y.
1422 Kernel support for MISC binaries
1424 If you say Y here, it will be possible to plug wrapper-driven binary
1425 formats into the kernel. You will like this especially when you use
1426 programs that need an interpreter to run like Java, Python or
1427 Emacs-Lisp. It's also useful if you often run DOS executables under
1428 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available in
1429 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO). Once you have
1430 registered such a binary class with the kernel, you can start one of
1431 those programs simply by typing in its name at a shell prompt; Linux
1432 will automatically feed it to the correct interpreter.
1434 If you say Y here, you won't need "Kernel support for JAVA binaries"
1435 (CONFIG_BINFMT_JAVA) or "Kernel support for Linux/Intel ELF
1436 binaries" (CONFIG_BINFMT_EM86), as this is a more general solution.
1438 You can do other nice things, too. Read
1439 Documentation/binfmt_misc.txt to learn how to use this feature, and
1440 Documentation/java.txt for information about how to include Java
1443 You must say Y to "proc filesystem support" (CONFIG_PROC_FS) to
1444 use this part of the kernel.
1446 You may say M here for module support and later load the module when
1447 you have use for it; the module is called binfmt_misc.o. If you
1448 don't know what to answer at this point, say Y.
1450 Solaris binary emulation
1452 This is experimental code which will enable you to run (many)
1453 Solaris binaries on your SPARC Linux machine.
1455 This code is also available as a module ( = code which can be
1456 inserted in and removed from the running kernel whenever you want).
1457 The module will be called solaris.o. If you want to compile it as a
1458 module, say M here and read Documentation/modules.txt.
1462 This is the processor type of your CPU. This information is used for
1463 optimizing purposes. In order to compile a kernel that can run on
1464 all x86 CPU types (albeit not optimally fast), you can specify
1465 "386" here. If you specify one of "486" or "Pentium" or "PPro",
1466 then the kernel will run on all of these CPUs: 486 and Pentium
1467 (=586) and Pentium Pro (=686). In rare cases, it can make sense to
1468 specify "Pentium" even if running on a 486: the kernel will be
1471 If you have a single processor machine, make sure that the line
1472 "SMP=1" at the top of the toplevel kernel Makefile is commented out;
1473 if you have a multi processor machine and want Linux to use all the
1474 processors in parallel (Symmetric Multi Processing), make sure that
1475 the line "SMP=1" is not commented out and read Documentation/smp and
1476 Documentation/IO-APIC.txt and the SMP-FAQ on the WWW at
1477 http://www.irisa.fr/prive/mentre/smp-faq/ (to browse the WWW, you
1478 need to have access to a machine on the Internet that has a program
1479 like lynx or netscape). People using multiprocessor machines should
1480 also say Y to "Enhanced Real Time Clock Support", below.
1482 If you want to compile a kernel that should work on both single
1483 processor and multi processor machines, it is possible to set SMP=1.
1484 The "Advanced Power Management" code (see configuration option
1485 below) will not work in that scenario, though. In addition, the
1486 kernel will be slower on single processor machines, and other
1487 problems may appear, so this is not recommended.
1489 If you don't know what to do, choose "386".
1493 Saying Y here will allow you to use Linux in text mode through a
1494 display that complies with the generic VGA standard. Virtually
1495 everyone wants that. Say Y.
1497 Video mode selection support
1499 This enables support for text mode selection on kernel startup. If
1500 you want to take advantage of some high-resolution text mode your
1501 card's BIOS offers, but the traditional Linux utilities like
1502 SVGATextMode don't, you can say Y here and set the mode using the
1503 "vga=" option from your boot loader (lilo or loadlin) or set
1504 "vga=ask" which brings up a video mode menu on kernel startup. Try
1505 "man bootparam" or see the documentation of your boot loader about
1506 how to pass options to the kernel. The lilo procedure is also
1507 explained in the SCSI-HOWTO, available via FTP (user: anonymous) in
1508 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Read
1509 Documentation/svga.txt for more information about the Video mode
1510 selection support. If unsure, say N.
1512 Support for frame buffer devices (EXPERIMENTAL)
1514 The frame buffer device provides an abstraction for the graphics
1515 hardware. It represents the frame buffer of some video hardware and
1516 allows application software to access the graphics hardware through
1517 a well-defined interface, so the software doesn't need to know
1518 anything about the low-level (hardware register) stuff.
1520 Frame buffer devices work identically across the different
1521 architectures supported by Linux and make the implementation of
1522 application programs easier and more portable; at this point, an X
1523 server exists which uses the frame buffer device exclusively.
1524 On several non-X86 architectures, the frame buffer device is the
1525 only way to use the graphics hardware.
1527 The device is accessed through special device nodes, usually located
1528 in the /dev directory, i.e. /dev/fb*.
1530 You need an utility program called fbset to make full use of frame
1531 buffer devices. Please read the file
1532 Documentation/fb/framebuffer.txt for more information.
1534 If you want to play with it, say Y here and also to the driver for
1535 your graphics board, below. If unsure, say N, unless you are
1536 compiling a kernel for a non-X86 architecture, in which case you
1541 This is the frame buffer device driver for the Acorn VIDC graphics
1544 Apollo frame buffer device
1546 This is the frame buffer device driver for the monochrome graphics
1547 hardware found in some Apollo workstations.
1549 Amiga native chipset support
1551 This is the frame buffer device driver for the builtin graphics
1552 chipset found in Amigas.
1554 Amiga OCS chipset support
1556 This enables support for the original Agnus and Denise video chips,
1557 found in the Amiga 1000 and most A500's and A2000's. If you intend
1558 to run Linux on any of these systems, say Y; otherwise say N.
1560 Amiga ECS chipset support
1562 This enables support for the Enhanced Chip Set, found in later
1563 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
1564 you intend to run Linux on any of these systems, say Y; otherwise
1567 Amiga AGA chipset support
1569 This enables support for the Advanced Graphics Architecture (also
1570 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
1571 and CD32. If you intend to run Linux on any of these systems, say Y;
1574 Amiga CyberVision support
1576 This enables support for the Cybervision 64 graphics card from
1577 Phase5. Please note that its use is not all that intuitive (i.e. if
1578 you have any questions, be sure to ask!). Say N unless you have a
1579 Cybervision 64 or plan to get one before you next recompile the
1580 kernel. Please note that this driver DOES NOT support the
1581 Cybervision 64 3D card, as they use incompatible video chips.
1583 Amiga CyberVision3D support (EXPERIMENTAL)
1585 This enables support for the Cybervision 64/3D graphics card from
1586 Phase5. Please note that its use is not all that intuitive (i.e. if
1587 you have any questions, be sure to ask!). Say N unless you have a
1588 Cybervision 64/3D or plan to get one before you next recompile the
1589 kernel. Please note that this driver DOES NOT support the older
1590 Cybervision 64 card, as they use incompatible video chips.
1592 Amiga RetinaZ3 support (EXPERIMENTAL)
1594 This enables support for the Retina Z3 graphics card. Say N unless
1595 you have a Retina Z3 or plan to get one before you next recompile
1598 Amiga CLgen driver (EXPERIMENTAL)
1600 This enables support for Cirrus Logic GD542x/543x based boards on
1601 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
1602 Say N unless you have such a graphics board or plan to get one
1603 before you next recompile the kernel.
1605 Atari native chipset support
1607 This is the frame buffer device driver for the builtin graphics
1608 chipset found in Ataris.
1610 Open Firmware frame buffer device support
1612 Say Y if you want support with Open Firmware for your graphics board.
1614 S3 Trio frame buffer device support
1616 If you have a S3 Trio say Y. Say N for S3 Virge.
1618 ATI Mach64 display support
1620 This driver supports graphics boards with the ATI Mach64 chips.
1622 PowerMac "control" frame buffer device support
1624 This driver supports a frame buffer for the graphics adapter in the
1625 Power Macintosh 7300 and others.
1627 PowerMac "platinum" frame buffer device support
1629 This driver supports a frame buffer for the "platinum" graphics adapter
1630 in some Power Macintoshes.
1632 PowerMac "valkyrie" frame buffer device support
1634 This driver supports a frame buffer for the "valkyrie" graphics adapter
1635 in some Power Macintoshes.
1637 Chips 65550 display support
1639 This is the frame buffer device driver for the Chips & Technologies
1640 65550 graphics chip in PowerBooks.
1642 Mac frame buffer device
1644 This is the frame buffer device driver for the graphics hardware in
1647 HP300 frame buffer device
1649 This is the frame buffer device driver for the Topcat graphics
1650 hardware found in HP300 workstations.
1652 TGA frame buffer support
1654 This is the frame buffer device driver for generic TGA graphic cards.
1655 Say Y if you have one of those.
1657 VESA VGA graphics console
1659 This is the frame buffer device driver for generic VESA graphic cards.
1660 Please read Documentation/fb/vesafb.txt.
1662 MDA text console (dual-headed)
1664 Say Y here if you have an old MDA or monochrome Hercules graphics
1665 adapter in your system acting as a second head ( = video card). Do
1666 not enable this driver if your MDA card is the primary card in your
1667 system; the normal VGA driver will handle it.
1669 This driver is also available as a module ( = code which can be
1670 inserted and removed from the running kernel whenever you want).
1671 The module will be called mdacon.o. If you want to compile it as
1672 a module, say M here and read Documentation/modules.txt.
1676 SBUS and UPA framebuffers
1678 Say Y if you want support for SBUS or UPA based frame buffer device.
1680 Creator/Creator3D support
1682 This is the frame buffer device driver for the Creator and Creator3D
1685 CGsix (GX,TurboGX) support
1687 This is the frame buffer device driver for the CGsix (GX, TurboGX)
1692 This is the frame buffer device driver for the BWtwo frame buffer.
1696 This is the frame buffer device driver for the CGthree frame buffer.
1698 TCX (SS4/SS5 only) support
1700 This is the frame buffer device driver for the TCX 24/8bit frame buffer.
1702 Virtual Frame Buffer support (ONLY FOR TESTING!)
1704 This is a `virtual' frame buffer device. It operates on a chunk of
1705 unswapable kernel memory instead of on the memory of a graphics
1706 board. This means you cannot see any output sent to this frame
1707 buffer device, while it does consume precious memory. The main use
1708 of this frame buffer device is testing and debugging the frame
1709 buffer subsystem. Do NOT enable it for normal systems! To protect
1710 the innocent, it has to be enabled explicitly at boot time using the
1711 kernel option `video=vfb:'.
1713 This driver is also available as a module ( = code which can be
1714 inserted and removed from the running kernel whenever you want).
1715 The module will be called vfb.o. If you want to compile it as
1716 a module, say M here and read Documentation/modules.txt.
1720 Advanced low level driver options
1721 CONFIG_FBCON_ADVANCED
1722 The frame buffer console uses character drawing routines that are
1723 tailored to the specific organization of pixels in the memory of your
1724 graphics hardware. These are called the low level frame buffer console
1725 drivers. Note that they are used for text console output only; they are
1726 NOT needed for graphical applications.
1728 If you say N here, the needed low level drivers are automatically
1729 enabled, depending on what frame buffer devices you selected above.
1730 This is recommended for most users.
1732 If you say Y here, you have more fine-grained control over which low
1733 level drivers are enabled. You can e.g. leave out low level drivers
1734 for color depths you do not intend to use for text consoles.
1736 Low level frame buffer console drivers can be modules ( = code which
1737 can be inserted and removed from the running kernel whenever you want).
1738 The modules will be called fbcon-*.o. If you want to compile (some of)
1739 them as modules, read Documentation/modules.txt.
1745 This is the low level frame buffer console driver for monochrome
1746 (2 colors) packed pixels.
1748 2 bpp packed pixels support
1750 This is the low level frame buffer console driver for 2 bits per pixel
1751 (4 colors) packed pixels.
1753 4 bpp packed pixels support
1755 This is the low level frame buffer console driver for 4 bits per pixel
1756 (16 colors) packed pixels.
1758 8 bpp packed pixels support
1760 This is the low level frame buffer console driver for 8 bits per pixel
1761 (256 colors) packed pixels.
1763 16 bpp packed pixels support
1765 This is the low level frame buffer console driver for 15 or 16 bits
1766 per pixel (32K or 64K colors, also known as `hicolor') packed pixels.
1768 24 bpp packed pixels support
1770 This is the low level frame buffer console driver for 24 bits per
1771 pixel (16M colors, also known as `truecolor') packed pixels. It is
1772 NOT for `sparse' 32 bits per pixel mode.
1774 32 bpp packed pixels support
1776 This is the low level frame buffer console driver for 32 bits per pixel
1777 (16M colors, also known as `truecolor') sparse packed pixels.
1779 Amiga bitplanes support
1781 This is the low level frame buffer console driver for 1 to 8 bitplanes
1782 (2 to 256 colors) on Amiga.
1784 Amiga interleaved bitplanes support
1786 This is the low level frame buffer console driver for 1 to 8
1787 interleaved bitplanes (2 to 256 colors) on Amiga.
1789 Atari interleaved bitplanes (2 planes) support
1790 CONFIG_FBCON_IPLAN2P2
1791 This is the low level frame buffer console driver for 2 interleaved
1792 bitplanes (4 colors) on Atari.
1794 Atari interleaved bitplanes (4 planes) support
1795 CONFIG_FBCON_IPLAN2P4
1796 This is the low level frame buffer console driver for 4 interleaved
1797 bitplanes (16 colors) on Atari.
1799 Atari interleaved bitplanes (8 planes) support
1800 CONFIG_FBCON_IPLAN2P8
1801 This is the low level frame buffer console driver for 8 interleaved
1802 bitplanes (256 colors) on Atari.
1804 Mac variable bpp packed pixels support
1806 This is the low level frame buffer console driver for 1/2/4/8/16/32
1807 bits per pixel packed pixels on Mac. It supports variable font widths
1808 for low resolution screens.
1810 VGA characters/attributes support
1812 This is the low level frame buffer console driver for VGA text mode;
1813 it is used if you said Y to "VGA chipset support (text only)" above.
1815 Parallel-port support
1817 If you want to use devices connected to your machine's parallel port
1818 (the connector at the computer with 25 holes), e.g. printer, Zip
1819 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
1820 create a mini network by connecting the parallel ports of two local
1821 machines) etc., then you need to say Y here; please read
1822 Documentation/parport.txt and drivers/misc/BUGS-parport.
1824 For extensive information about drivers for many devices attaching
1825 to the parallel port see http://www.torque.net/linux-pp.html on the
1826 WWW (To browse the WWW, you need to have access to a machine on the
1827 Internet that has a program like lynx or netscape).
1829 It is possible to share a single parallel port among several devices
1830 and it is safe to compile all the corresponding drivers into the
1831 kernel. If you want to compile parallel port support as a module
1832 ( = code which can be inserted in and removed from the running kernel
1833 whenever you want), say M here and read Documentation/modules.txt.
1834 The module will be called parport.o. If you have more than one
1835 parallel port and want to specify which port and IRQ to be used by
1836 this driver at module load time, read
1837 Documentation/networking/net-modules.txt.
1843 You should say Y here if you have a PC-style parallel port. All IBM
1844 PC compatible computers and some Alphas have PC-style parallel
1845 ports. This code is also available as a module. If you want to it as
1846 a module ( = code which can be inserted in and removed from the
1847 running kernel whenever you want), say M here and read
1848 Documentation/modules.txt. The module will be called parport_pc.o.
1851 Support foreign hardware
1852 CONFIG_PARPORT_OTHER
1853 Say Y here if you want to be able to load driver modules to support
1854 other non-standard types of parallel ports. This causes a
1855 performance loss, so most people say N.
1857 Sun Ultra/AX-style hardware
1859 Say Y here if you need support for the parallel port hardware on Sun
1860 Ultra/AX machines. This code is also available as a module (say M),
1861 called parport_ax.o. If in doubt, saying N is the safe plan.
1863 Generate little endian code
1864 CONFIG_CPU_LITTLE_ENDIAN
1865 If your compiler is mipsel-linux-gcc or mipsel-linuxelf-gcc (as
1866 opposed to mips-linux-gcc or mips-linuxelf-gcc), say Y here,
1867 otherwise N. Most MIPS machines use little-endian code, but it might
1868 be necessary to run older Mips systems, such as the Sony News and
1869 MIPS RC3xxx, in big endian mode.
1871 Build fp execption handler module
1872 CONFIG_MIPS_FPE_MODULE
1873 Build the floating point exception handler module. This option is only
1874 useful for people working on the floating point exception handler. If
1877 Plug and Play support
1879 Plug and Play support allows the kernel to automatically configure
1880 some peripheral devices. Say Y to enable PnP.
1882 Auto-probe for parallel devices
1884 Some IEEE-1284 conforming parallel-port devices can identify
1885 themselves when requested. Say Y to enable this feature, or M to
1886 compile it as a module (parport_ieee1284.o). If in doubt, say N.
1888 Enable loadable module support
1890 Kernel modules are small pieces of compiled code which can be
1891 inserted in or removed from the running kernel, using the programs
1892 insmod and rmmod. This is described in the file
1893 Documentation/modules.txt, including the fact that you have to say
1894 "make modules" in order to compile the modules that you chose during
1895 kernel configuration. Modules can be device drivers, file systems,
1896 binary executable formats, and so on. If you think that you may want
1897 to make use of modules with this kernel in the future, then say Y
1898 here. If unsure, say Y.
1900 Set version information on all symbols for modules
1902 Usually, modules have to be recompiled whenever you switch to a new
1903 kernel. Saying Y here makes it possible, and safe, to use the
1904 same modules even after compiling a new kernel; this requires the
1905 program modprobe. All the software needed for module support is in
1906 the modutils package (check the file Documentation/Changes for
1907 location and latest version). NOTE: if you say Y here but don't
1908 have the program genksyms (which is also contained in the above
1909 mentioned modutils package), then the building of your kernel will
1910 fail. If you are going to use modules that are generated from
1911 non-kernel sources, you would benefit from this option. Otherwise
1912 it's not that important. So, N ought to be a safe bet.
1914 Kernel module loader support
1916 Normally when you have selected some drivers and/or filesystems to
1917 be created as loadable modules, you also have the responsibility to
1918 load the corresponding modules (using the programs insmod or
1919 modprobe) before you can use them. If you say Y here however, the
1920 kernel will be able to load modules for itself: when a part of the
1921 kernel needs a module, it runs modprobe with the appropriate
1922 arguments. (This is a replacement for kerneld.) Say Y here and read
1923 about configuring it in Documentation/kmod.txt.
1925 ARP daemon support (EXPERIMENTAL)
1927 Normally, the kernel maintains an internal cache which maps IP
1928 addresses to hardware addresses on the local network, so that
1929 Ethernet/Token Ring/ etc. frames are sent to the proper address on
1930 the physical networking layer. For small networks having a few
1931 hundred directly connected hosts or less, keeping this address
1932 resolution (ARP) cache inside the kernel works well. However,
1933 maintaining an internal ARP cache does not work well for very large
1934 switched networks, and will use a lot of kernel memory if TCP/IP
1935 connections are made to many machines on the network.
1937 If you say Y here, the kernel's internal ARP cache will never grow
1938 to more than 256 entries (the oldest entries are expired in a LIFO
1939 manner) and communication will be attempted with the user space ARP
1940 daemon arpd. Arpd then answers the address resolution request either
1941 from its own cache or by asking the net.
1943 This code is still experimental. If you do say Y here, you should
1944 obtain a copy of arpd from
1945 http://www.loran.com/~layes/arpd/index.html, and you should also say
1946 Y to "Kernel/User network link driver", below. If unsure, say N.
1950 These are the protocols used on the Internet and on most local
1951 Ethernets. The safest is to say Y here (which will enlarge your
1952 kernel by about 35 kB), since some programs (e.g. the X window
1953 system) use TCP/IP even if your machine is not connected to any
1954 other computer. You will get the so-called loopback device which
1955 allows you to ping yourself (great fun, that!). This option is also
1956 necessary if you want to use the full power of term (term is a
1957 program which gives you almost full Internet connectivity if you
1958 have a regular dial up shell account on some Internet connected Unix
1959 computer. Read http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html).
1961 If you say Y here and also to "/proc filesystem support" and "Sysctl
1962 support" below, you can change various aspects of the behavior of
1963 the TCP/IP code by writing to the (virtual) files in
1964 /proc/sys/net/ipv4/*; the options are explained in the file
1965 Documentation/Networking/ip-sysctl.txt.
1967 Short answer: say Y.
1971 This is code for addressing several networked computers at once,
1972 enlarging your kernel by about 2 kB. You need multicasting if you
1973 intend to participate in the MBONE, a high bandwidth network on top
1974 of the Internet which carries audio and video broadcasts. More
1975 information about the MBONE is on the WWW at
1976 http://www.best.com/~prince/techinfo/mbone.html (to browse the WWW,
1977 you need to have access to a machine on the Internet that has a
1978 program like lynx or netscape). Information about the multicast
1979 capabilities of the various network cards is contained in
1980 Documentation/networking/multicast.txt. For most people, it's safe
1984 CONFIG_IP_ADVANCED_ROUTER
1985 If you intend to run your Linux box mostly as a router, i.e. as a
1986 computer that forwards and redistributes network packets, say Y; you
1987 will then be presented with several options that allow more precise
1988 control about the routing process.
1990 The answer to this question won't directly affect the kernel: saying
1991 N will just cause this configure script to skip all the questions
1992 about advanced routing.
1994 Note that your box can only act as a router if you enable IP
1995 forwarding in your kernel; you can do that by saying Y to "/proc
1996 filesystem support" and "Sysctl support" below and executing the line
1998 echo "1" > /proc/sys/net/ipv4/ip_forward
2000 at boot time after the /proc filesystem has been mounted.
2002 If unsure, say N here.
2005 CONFIG_IP_MULTIPLE_TABLES
2006 Normally, a router decides what to do with a received packet based
2007 solely on the packet's final destination address. If you say Y here,
2008 routing can also take into account the originating address and the
2009 network device from which the packet reached us.
2011 IP: equal cost multipath
2012 CONFIG_IP_ROUTE_MULTIPATH
2013 Normally, the routing tables specify a single action to be taken in
2014 a deterministic manner for a given packet. If you say Y here
2015 however, it becomes possible to attach several actions to a packet
2016 pattern, in effect specifying several alternative paths to travel
2017 for those packets. The router considers all these paths to be of
2018 equal "cost" and chooses one of them in a non-deterministic fashion
2019 if a matching packet arrives.
2021 IP: use TOS value as routing key
2023 The header of every IP packet carries a TOS (Type of Service) value
2024 with which the packet requests a certain treatment, e.g. low latency
2025 (for interactive traffic), high throughput, or high reliability.
2026 Normally, these values are ignored, but if you say Y here, you will
2027 be able to specify different routes for packets with different TOS
2030 IP: verbose route monitoring
2031 CONFIG_IP_ROUTE_VERBOSE
2032 If you say Y here, which is recommended, then the kernel will print
2033 verbose messages regarding the routing, for example warnings about
2034 received packets which look strange and could be evidence of an
2035 attack or a misconfigured system somewhere. The information is
2036 handled by the klogd daemon which is responsible for kernel messages
2039 IP: large routing tables
2040 CONFIG_IP_ROUTE_LARGE_TABLES
2041 If you have routing zones that grow to more than about 64 entries,
2042 you may want to say Y here to speed up the routing process.
2044 IP: fast network address translation
2046 If you say Y here, your router will be able to modify source and
2047 destination addresses of packets that pass through it.
2049 IP: optimize as router not host
2051 Some Linux network drivers use a technique called copy and checksum
2052 to optimize host performance. For a machine which acts as a router
2053 most of the time and is forwarding most packets to another host this
2054 is however a loss. If you say Y here, copy and checksum will be
2055 switched off. In the future, it may make other changes which
2056 optimize for router operation.
2058 Note that your box can only act as a router if you enable IP
2059 forwarding in your kernel; you can do that by saying Y to "/proc
2060 filesystem support" and "Sysctl support" below and executing the line
2062 echo "1" > /proc/sys/net/ipv4/ip_forward
2064 at boot time after the /proc filesystem has been mounted.
2066 If unsure, say N here.
2070 If you want to configure your Linux box as a packet filter firewall
2071 for a local TCP/IP based network, say Y here. You may want to read
2072 the FIREWALL-HOWTO, available via FTP (user: anonymous) in
2073 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
2075 Also, you will need the ipchains tool (available on the WWW at
2076 http://www.adelaide.net.au/~rustcorp/) to allow selective blocking
2077 of Internet traffic based on type, origin and destination.
2078 Note that the Linux firewall code has changed and the old program
2079 called ipfwadm won't work anymore.
2081 The type of firewall provided by ipchains and this kernel support is
2082 called a "packet filter". The other type of firewall, a
2083 "proxy-based" one, is more secure but more intrusive and more
2084 bothersome to set up; it inspects the network traffic much more
2085 closely, modifies it and has knowledge about the higher level
2086 protocols, which a packet filter lacks. Moreover, proxy-based
2087 firewalls often require changes to the programs running on the local
2088 clients. Proxy-based firewalls don't need support by the kernel, but
2089 they are often combined with a packet filter, which only works if
2092 The firewalling code will only work if IP forwarding is enabled in
2093 your kernel. You can do that by saying Y to "/proc filesystem
2094 support" and "Sysctl support" below and executing the line
2096 echo "1" > /proc/sys/net/ipv4/ip_forward
2098 at boot time after the /proc filesystem has been mounted.
2100 You need to say Y to "IP firewalling" in order to be able to use IP
2101 masquerading (masquerading means that local computers can chat with
2102 an outside host, but that outside host is made to think that it is
2103 talking to the firewall box -- makes the local network completely
2104 invisible to the outside world and avoids the need to allocate
2105 globally valid IP host addresses for the machines on the local net)
2106 and IP packet logging and accounting (keeping track of what is using
2107 all your network bandwidth) and IP transparent proxying (makes the
2108 computers on the local network think they're talking to a remote
2109 computer, while in reality the traffic is redirected by your Linux
2110 firewall to a local proxy server).
2112 If in doubt, say N here.
2114 IP: firewall packet netlink device
2115 CONFIG_IP_FIREWALL_NETLINK
2116 If you say Y here, then the first 128 bytes of each packet that hit
2117 your Linux firewall and was blocked are passed on to optional user
2118 space monitoring software that can then look for attacks and take
2119 actions such as paging the administrator of the site.
2121 To use this, you need to create a character special file under /dev
2122 with major number 36 and minor number 3 using mknod ("man mknod"),
2123 and you need (to write) a program that reads from that device and
2124 takes appropriate action.
2126 With the ipchains tool you can specify which packets you want to go
2127 to this device, as well as how many bytes from each packet.
2129 IP: kernel level autoconfiguration
2131 This enables automatic configuration of IP addresses of devices and
2132 of the routing table during kernel boot, based on either information
2133 supplied at the kernel command line or by BOOTP or RARP protocols.
2134 You need to say Y only for diskless machines requiring network access
2135 to boot (in which case you want to say Y to "Root file system on
2136 NFS" as well), because all other machines configure the network in
2137 their startup scripts.
2141 If you want your Linux box to mount its whole root filesystem from
2142 some other computer over the net via NFS and you want the IP address
2143 of your computer to be discovered automatically at boot time using
2144 the BOOTP protocol (a special protocol designed for doing this job),
2145 say Y here. In case the boot ROM of your network card was designed
2146 for booting Linux and does BOOTP itself, providing all necessary
2147 information on the kernel command line, you can say N here. If
2148 unsure, say Y. Note that if you want to use BOOTP, a BOOTP server
2149 must be operating on your network. Read Documentation/nfsroot.txt
2154 If you want your Linux box to mount its whole root filesystem from
2155 some other computer over the net via NFS and you want the IP address
2156 of your computer to be discovered automatically at boot time using
2157 the RARP protocol (an older protocol which is being obsoleted by
2158 BOOTP and DHCP), say Y here. Note that if you want to use RARP, a
2159 RARP server must be operating on your network. Read
2160 Documentation/nfsroot.txt for details.
2164 Tunneling means encapsulating data of one protocol type within
2165 another protocol and sending it over a channel that understands the
2166 encapsulating protocol. This particular tunneling driver implements
2167 encapsulation of IP within IP, which sounds kind of pointless, but
2168 can be useful if you want to make your (or some other) machine
2169 appear on a different network than it physically is, or to use
2170 mobile-IP facilities (allowing laptops to seamlessly move between
2171 networks without changing their IP addresses; check out
2172 http://anchor.cs.binghamton.edu/~mobileip/LJ/index.html).
2174 Saying Y to this option will produce two modules ( = code which can
2175 be inserted in and removed from the running kernel whenever you
2176 want), one encapsulator called tunnel.o and one decapsulator called
2177 ipip.o. You can read details in drivers/net/README.tunnel. Most
2178 people won't need this and can say N.
2180 IP: GRE tunnels over IP
2182 Tunneling means encapsulating data of one protocol type within
2183 another protocol and sending it over a channel that understands the
2184 encapsulating protocol. This particular tunneling driver implements
2185 GRE (Generic Routing Encapsulation) and at this time allows
2186 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
2187 This driver is useful if the other endpoint is a Cisco router: Cisco
2188 likes GRE much better than the other Linux tunneling driver ("IP:
2189 tunneling" above). In addition, GRE allows multicast redistribution
2192 IP: broadcast GRE over IP
2193 CONFIG_NET_IPGRE_BROADCAST
2194 One application of GRE/IP is to construct a broadcast WAN (Wide Area
2195 Network), which looks like a normal Ethernet LAN (Local Area
2196 Network), but can be distributed all over the Internet. If you want
2197 to do that, say Y here and to "IP: multicast routing" below.
2199 IP: transparent proxying
2200 CONFIG_IP_TRANSPARENT_PROXY
2201 This enables your Linux firewall to transparently redirect any
2202 network traffic originating from the local network and destined
2203 for a remote host to a local server, called a "transparent proxy
2204 server". This makes the local computers think they are talking to
2205 the remote end, while in fact they are connected to the local
2206 proxy. Redirection is activated by defining special input firewall
2207 rules (using the ipchains utility) and/or by doing an appropriate
2211 CONFIG_IP_MASQUERADE
2212 If one of the computers on your local network for which your Linux
2213 box acts as a firewall wants to send something to the outside, your
2214 box can "masquerade" as that computer, i.e. it forwards the traffic
2215 to the intended outside destination, but makes it look like it came
2216 from the firewall box itself. It works both ways: if the outside
2217 host replies, the Linux firewall will silently forward the traffic
2218 to the corresponding local computer. This way, the computers on your
2219 local net are completely invisible to the outside world, even though
2220 they can reach the outside and can be reached. This makes it
2221 possible to have the computers on the local network participate on
2222 the Internet even if they don't have officially registered IP
2223 addresses. (This last problem can also be solved by connecting the
2224 Linux box to the Internet using SLiRP [SLiRP is a SLIP/PPP emulator
2225 that works if you have a regular dial up shell account on some UNIX
2226 computer; get it via FTP (user: anonymous) from
2227 ftp://sunsite.unc.edu/pub/Linux/system/network/serial/ ].)
2229 The IP masquerading code will only work if IP forwarding is enabled
2230 in your kernel; you can do this by saying Y to "/proc
2231 filesystem support" and "Sysctl support" below and then executing a
2234 echo "1" > /proc/sys/net/ipv4/ip_forward
2236 from a boot time script after the /proc filesystem has been mounted.
2238 Details on how to set things up are contained in the IP Masquerade
2239 mini-HOWTO, available via FTP (user: anonymous) from
2240 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini; there's also some
2241 information on the WWW at
2242 http://www.tor.shaw.wave.ca/~ambrose/kernel21.html.
2244 If you say Y here, you should also say Y to "IP: always defragment",
2247 If you say Y here, then the modules ip_masq_ftp.o (for ftp transfers
2248 through the firewall), ip_masq_irc.o (for irc chats through the
2249 firewall), and ip_masq_raudio.o (for RealAudio downloads through the
2250 firewall) will automatically be compiled. Modules are pieces of code
2251 which can be inserted in and removed from the running kernel
2252 whenever you want; read Documentation/modules.txt for details.
2254 IP: ICMP masquerading
2255 CONFIG_IP_MASQUERADE_ICMP
2256 The basic masquerade code described for "IP: masquerading" above only
2257 handles TCP or UDP packets (and ICMP errors for existing
2258 connections). This option adds additional support for masquerading
2259 ICMP packets, such as ping or the probes used by the Windows 95
2262 If you want this, say Y.
2264 IP: ipautofw masquerade support (Experimental)
2265 CONFIG_IP_MASQUERADE_IPAUTOFW
2266 ipautofw is a program by Richard Lynch allowing additional support
2267 for masquerading protocols which do not (as yet) have their own
2268 protocol helpers. Information and source for ipautofw is available
2269 via FTP (user: anonymous) from
2270 ftp://ftp.netis.com/pub/members/rlynch/
2272 For 2.1 kernels, you will need "ipmasqadm" tool from
2273 http://juanjox.home.ml.org
2275 The ipautofw code is still under development and so is currently
2276 marked EXPERIMENTAL. If you want to try it, say Y.
2278 This code is also available as a module ( = code which can be
2279 inserted in and removed from the running kernel whenever you want).
2280 The module will be called ip_masq_autofw.o. If you want to compile
2281 it as a module, say M here and read Documentation/modules.txt.
2283 IP: masquerading special modules support
2284 CONFIG_IP_MASQUERADE_MOD
2285 This provides support for special modules that can modify rewriting
2286 rules to achieve, for example, input port forwarding.
2287 Beware that this feature adds a little overhead in the input packet
2290 You will need user space program "ipmasqadm" to use these
2291 additional modules, you can download it from
2292 http://juanjox.home.ml.org/
2294 All this additional code is still under development and so is currently
2295 marked EXPERIMENTAL.
2297 If you want to try, for example, PORT FORWARDING, say Y.
2299 IP: ipportfw masquerade support
2300 CONFIG_IP_MASQUERADE_IPPORTFW
2301 Port Forwarding is an addition to IP Masquerading written by Steven
2302 Clarke to allow some forwarding of packets from outside to inside a
2303 firewall on given ports. This could be useful if, for example, you
2304 want to run a web server behind the firewall or masquerading host
2305 and this web server should be visible to the outside world. An
2306 external client connects to port 80 of the firewall, the firewall
2307 forwards requests to this port to the web server, the web server
2308 handles the request and the results are sent through the firewall to
2309 the original client. The client thinks that the firewall machine
2310 itself is running the web server.
2312 Information about it is available from
2313 http://www.monmouth.demon.co.uk/ipsubs/portforwarding.html (to
2314 browse the WWW, you need to have access to a machine on the Internet
2315 that has a program like lynx or netscape). You will need the user
2316 space program "ipmasqadm" which can be downloaded from
2317 http://juanjox.home.ml.org/
2319 For general info, please see
2320 ftp://ftp.compsoc.net/users/steve/ipportfw/linux21/
2322 The portfw code is still under development and so is currently
2323 marked EXPERIMENTAL. If you want to try it, say Y.
2325 This code is also available as a module ( = code which can be
2326 inserted in and removed from the running kernel whenever you want).
2327 The module will be called ip_masq_portfw.o. If you want to compile
2328 it as a module, say M here and read Documentation/modules.txt.
2330 IP: ipmarkfw masquerade support
2331 CONFIG_IP_MASQUERADE_IPMARKFW
2332 This provides functionally equivalent to port forwarding, the difference
2333 is that Mark Forwarding uses "firewalling mark" to select which packets
2334 must forward (see ipchains(8), "-m" argument).
2336 The markfw code is still under development and so is currently
2337 marked EXPERIMENTAL. If you want to try it, say Y.
2339 This code is also available as a module ( = code which can be
2340 inserted in and removed from the running kernel whenever you want).
2341 The module will be called ip_masq_markfw.o. If you want to compile
2342 it as a module, say M here and read Documentation/modules.txt.
2344 IP: always defragment
2345 CONFIG_IP_ALWAYS_DEFRAG
2346 This option means that all incoming fragments (= parts of IP packets
2347 that arose when some host between origin and destination decided
2348 that the IP packets were too large and cut them into pieces) will be
2349 reassembled (defragmented) before being processed, even if they are
2350 about to be forwarded.
2352 This option is highly recommended if you have said Y to "IP:
2353 masquerading" because that facility requires that second and further
2354 fragments can be related to TCP or UDP port numbers, which are only
2355 stored in the first fragment. When using "IP: firewalling" support ,
2356 you might also want to say Y here, to have a more reliable firewall
2357 (otherwise second and further fragments will always be accepted by
2358 the firewall). When using "IP: transparent proxying", this option is
2359 implicit, although it is safe to say Y here. Only say Y here if
2360 running either a firewall that is the sole link to your network or a
2361 transparent proxy; never ever say Y here for a normal router or
2364 IP: aliasing support
2366 Sometimes it is useful to give several IP addresses to a single
2367 physical network interface (= serial port or Ethernet card). The
2368 most common case is that you want to serve different WWW or ftp
2369 documents to the outside according to which of your host names was
2370 used to connect to you. This is called "multihosting" or "virtual
2371 domains" or "virtual hosting services" and is explained in detail on
2372 the WWW at http://www.thesphere.com/~dlp/TwoServers/ (to browse the
2373 WWW, you need to have access to a machine on the Internet that has a
2374 program like lynx or netscape) and also in the
2375 Virtual-Hosting-HOWTO, available via FTP (user: anonymous) from
2376 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
2378 Another scenario would be
2379 that there are two logical networks living on your local Ethernet
2380 and you want to access them both with the same Ethernet card. This
2381 can be done if you say Y here.
2383 The configuration of these alias addresses is done with a special
2384 name syntax explained in Documentation/networking/alias.txt and in
2385 the IP-Alias mini-HOWTO. If you want this, say Y. Most people don't
2388 IP: multicast routing
2390 This is used if you want your machine to act as a router for IP
2391 packets that have several destination addresses. It is needed on the
2392 MBONE, a high bandwidth network on top of the Internet which carries
2393 audio and video broadcasts. In order to do that, you would most
2394 likely run the program mrouted. Information about the multicast
2395 capabilities of the various network cards is contained in
2396 Documentation/networking/multicast.txt. If you haven't heard about
2397 it, you don't need it.
2399 IP: PIM-SM version 1 support
2401 Kernel side support for Sparse Mode PIM (Protocol Independent
2402 Multicast) version 1. This multicast routing protocol is used widely
2403 because Cisco supports it. You need special software to use it
2404 (pimd-v1). Please see http://netweb.usc.edu/pim/ for more
2405 information about PIM (to browse the WWW, you need to have access to
2406 a machine on the Internet that has a program like lynx or
2407 netscape). Say Y if you want to use PIM-SM v1. Note that you can say
2408 N here if you just want to use Dense Mode PIM.
2410 IP: PIM-SM version 2 support
2412 Kernel side support for Sparse Mode PIM version 2. In order to use
2413 this, you need an experimental routing daemon supporting it (pimd or
2414 gated-5). This routing protocol is not used widely, so say N unless
2415 you want to play with it.
2417 PC/TCP compatibility mode
2419 If you have been having difficulties telnetting to your Linux machine
2420 from a DOS system that uses (broken) PC/TCP networking software (all
2421 versions up to OnNet 2.0) over your local Ethernet try saying Y
2422 here. Everyone else says N. People having problems with NCSA telnet
2423 should see the file linux/Documentation/networking/ncsa-telnet.
2427 If there are (usually diskless or portable) machines on your local
2428 network that know their hardware Ethernet addresses but don't know
2429 their IP addresses upon startup, they can send out a Reverse Address
2430 Resolution Protocol (RARP) request to find out their own IP
2431 addresses. Diskless Sun 3 machines use this procedure at boot time,
2432 and diskless Linux boxes can be configured to do it as well.
2434 If you want your Linux box to be able to *answer* such requests, say
2435 Y here; you'll then have to run the program rarp ("man rarp") on
2438 If you actually want to use a diskless Sun 3 machine as an X
2439 terminal to Linux, say Y here and fetch Linux-Xkernel from
2440 ftp://sunsite.unc.edu/pub/Linux/system/network/boot.net/.
2442 Superior solutions to the problem of booting and configuring
2443 machines over a net connection are given by the protocol BOOTP and
2444 its successor DHCP. See the DHCP FAQ
2445 http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html for details (to
2446 browse the WWW, you need to have access to a machine on the Internet
2447 that has a program like lynx or netscape).
2449 If you want to compile RARP support as a module ( = code which can
2450 be inserted in and removed from the running kernel whenever you
2451 want), say M here and read Documentation/modules.txt. The module
2452 will be called rarp.o.
2454 If you don't understand a word of the above, say N and rest in
2457 Assume subnets are local
2459 Say Y if you are on a subnetted network with all machines connected
2460 by Ethernet segments only, as this option optimizes network access
2461 for this special case. If there are other connections, e.g. SLIP
2462 links, between machines of your IP network, say N. If in doubt, say
2463 N. The PATH mtu discovery facility will cover most cases anyway.
2465 Path MTU Discovery (normally enabled)
2466 CONFIG_PATH_MTU_DISCOVERY
2467 MTU (maximal transfer unit) is the size of the chunks we send out
2468 over the net. "Path MTU Discovery" means that, instead of always
2469 sending very small chunks, we start out sending big ones and if we
2470 then discover that some host along the way likes its chunks smaller,
2471 we adjust to a smaller size. This is good, so most people say
2474 However, some DOS software (versions of DOS NCSA telnet and Trumpet
2475 Winsock in PPP mode) is broken and won't be able to connect to your
2476 Linux machine correctly in all cases (especially through a terminal
2477 server) unless you say N here. See
2478 Documentation/networking/ncsa-telnet for the location of fixed NCSA
2479 telnet clients. If in doubt, say Y.
2481 Disable NAGLE algorithm (normally enabled)
2482 CONFIG_TCP_NAGLE_OFF
2483 The NAGLE algorithm works by requiring an acknowledgment before
2484 sending small IP frames (= packets). This keeps tiny telnet and
2485 rlogin packets from congesting Wide Area Networks. Most people
2486 strongly recommend to say N here, thereby leaving NAGLE
2487 enabled. Those programs that would benefit from disabling this
2488 facility can do it on a per connection basis themselves.
2490 IP: Drop source routed frames
2492 Usually, the originator of an IP frame (= packet) specifies only the
2493 destination, and the hosts along the way do the routing, i.e. they
2494 decide how to forward the frame. However, there is a feature of the
2495 IP protocol that allows to specify the full route for a given frame
2496 already at its origin. A frame with such a fully specified route is
2497 called "source routed". The question now is whether we should honour
2498 these route requests when such frames arrive, or if we should
2499 drop all those frames instead. Honouring them can introduce security
2500 problems (and is rarely a useful feature), and hence it is recommended
2501 that you say Y here unless you really know what you're doing.
2503 IP: Allow large windows (not recommended if <16Mb of memory)
2505 On high speed, long distance networks the performance limit on
2506 networking becomes the amount of data a machine can buffer until the
2507 other end confirms its reception. (At 45Mbit/second there are a lot
2508 of bits between New York and London ...). This option allows larger
2509 amounts of data to be "in flight" at a given time. It also means a
2510 user process can require a lot more memory for network buffers and
2511 thus this option is best used only on machines with 16Mb of memory
2512 or higher. Unless you are using long links with end to end speeds of
2513 over 2Mbit a second or satellite links this option will make no
2514 difference to performance.
2518 This includes Unix domain sockets, the standard Unix mechanism for
2519 establishing and accessing network connections. Many commonly used
2520 programs such as the X Window system and syslog use these sockets
2521 even if your machine is not connected to any network. Unless you are
2522 working on an embedded system or something similar, you therefore
2523 definitely want to say Y here.
2525 The socket support is also available as a module ( = code which can
2526 be inserted in and removed from the running kernel whenever you
2527 want). The module will be called unix.o. If you want to compile it
2528 as a module, say M here and read Documentation/modules.txt. If you
2529 try building this as a module and you have said Y to "Kernel module
2530 loader support" above, be sure to add 'alias net-pf-1 unix' to your
2531 /etc/conf.modules file.
2537 This is experimental support for the next version of the Internet
2538 Protocol: IP version 6 (also called IPng "IP next generation").
2539 Features of this new protocol include: expanded address space,
2540 authentication and privacy, and seamless interoperability with the
2541 current version of IP (IP version 4). For general information about
2542 IPv6, see http://playground.sun.com/pub/ipng/html/ipng-main.html (to
2543 browse the WWW, you need to have access to a machine on the Internet
2544 that has a program like lynx or netscape); for specific information
2545 about IPv6 under Linux read the HOWTO at http://www.terra.net/ipv6/
2546 and the file net/ipv6/README in the kernel source.
2548 If you want to use IPv6, please upgrade to the newest net-tools as
2549 given in Documentation/Changes. You will still be able to do regular
2550 IPv4 networking as well.
2552 It is safe to say N here for now.
2554 IPv6: enable EUI-64 token format
2556 6bone, the network of computers using the IPv6 protocol, is moving
2557 to a new aggregatable address format and a new link local address
2558 assignment (EUI-64). Say Y if your site has upgraded already, or
2559 has started to upgrade.
2561 IPv6: disable provider based addresses
2563 Linux tries to operate correctly when your site has moved to EUI-64
2564 only partially. Unfortunately, the two address formats (old:
2565 "provider based" and new: "aggregatable") are incompatible. Say Y if
2566 your site finished the upgrade to EUI-64, and/or you encountered
2567 some problems caused by the presence of two link-local addresses on
2570 IPv6: routing messages via old netlink
2572 You can say Y here to receive routing messages from the IPv6 code
2573 through the old netlink interface. However, a better option is to
2574 say Y to "Kernel/User network link driver" and to "Routing
2579 This is support for the Novell networking protocol, IPX, commonly
2580 used for local networks of Windows machines. You need it if you want
2581 to access Novell NetWare file or print servers using the Linux
2582 Novell client ncpfs (available via FTP (user: anonymous) from
2583 ftp://sunsite.unc.edu/pub/Linux/system/filesystems/) or from within
2584 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available in
2585 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO). In order to do the
2586 former, you'll also have to say Y to "NCP filesystem support",
2589 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
2590 is similar to TCP. There is also experimental support for SPX in
2591 Linux (see "SPX networking", below).
2593 To turn your Linux box into a fully featured NetWare file server and
2594 IPX router, say Y here and fetch either lwared from
2595 ftp://sunsite.unc.edu/pub/Linux/system/network/daemons/ or mars_nwe
2596 from ftp://ftp.gwdg.de/pub/linux/misc/ncpfs. For more information,
2597 read the IPX-HOWTO in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
2599 General information about how to connect Linux, Windows machines and
2600 Macs is on the WWW at http://www.eats.com/linux_mac_win.html (to
2601 browse the WWW, you need to have access to a machine on the Internet
2602 that has a program like lynx or netscape).
2604 The IPX driver would enlarge your kernel by about 5 kB. This driver
2605 is also available as a module ( = code which can be inserted in and
2606 removed from the running kernel whenever you want). The module will
2607 be called ipx.o. If you want to compile it as a module, say M here
2608 and read Documentation/modules.txt. Unless you want to integrate
2609 your Linux box with a local Novell network, say N.
2611 IPX: Full internal IPX network
2613 Every IPX network has an address that identifies it. Sometimes it is
2614 useful to give an IPX "network" address to your Linux box as well
2615 (for example if your box is acting as a file server for different IPX
2616 networks: it will then be accessible from everywhere using the same
2617 address). The way this is done is to create a virtual internal
2618 "network" inside your box and to assign an IPX address to this
2619 network. Say Y here if you want to do this; read the IPX-HOWTO at
2620 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO for details.
2622 The full internal IPX network enables you to allocate sockets on
2623 different virtual nodes of the internal network. This is done by
2624 evaluating the field sipx_node of the socket address given to the
2625 bind call. So applications should always initialize the node field
2626 to 0 when binding a socket on the primary network. In this case the
2627 socket is assigned the default node that has been given to the
2628 kernel when the internal network was created. By enabling the full
2629 internal IPX network the cross-forwarding of packets targeted at
2630 'special' sockets to sockets listening on the primary network is
2631 disabled. This might break existing applications, especially RIP/SAP
2632 daemons. A RIP/SAP daemon that works well with the full internal net
2633 can be found on ftp://ftp.gwdg.de/pub/linux/misc/ncpfs. If you don't
2634 know what you are doing, say N.
2636 IPX: SPX networking (EXPERIMENTAL)
2638 The Sequenced Packet eXchange protocol is a transport layer protocol
2639 built on top of IPX. It is used in Novell NetWare systems for
2640 client-server applications and is similar to TCP (which runs on top
2643 Note that Novell NetWare file sharing does not use SPX; it uses a
2644 protocol called NCP, for which separate Linux support is available
2645 ("NCP filesystem support" below for the client side, and the user
2646 space programs lwared or mars_nwe for the server side).
2648 Say Y here if you have use for SPX; read the IPX-HOWTO at
2649 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO for details.
2651 This driver is also available as a module ( = code which can be
2652 inserted in and removed from the running kernel whenever you want).
2653 The module will be called af_spx.o. If you want to compile it as a
2654 module, say M here and read Documentation/modules.txt.
2658 AppleTalk is the way Apple computers speak to each other on a
2659 network. If your Linux box is connected to such a network and you
2660 want to join the conversation, say Y. You will need to use the
2661 netatalk package so that your Linux box can act as a print and file
2662 server for Macs as well as access AppleTalk printers. Check out
2663 http://threepio.hitchcock.org/cgi-bin/faq/netatalk/faq.pl on the WWW
2664 for details (to browse the WWW, you need to have access to a machine
2665 on the Internet that has a program like lynx or netscape). EtherTalk
2666 is the name used for AppleTalk over Ethernet and the cheaper and
2667 slower LocalTalk is AppleTalk over a proprietary apple network using
2668 serial links. EtherTalk and LocalTalk are fully supported by Linux.
2669 The NET-2-HOWTO, available via FTP (user: anonymous) in
2670 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO contains valuable
2671 information as well.
2673 General information about how to connect Linux, Windows machines and
2674 Macs is on the WWW at http://www.eats.com/linux_mac_win.html
2676 This driver is also available as a module ( = code which can be
2677 inserted in and removed from the running kernel whenever you want).
2678 The module is called appletalk.o. If you want to compile it as a
2679 module, say M here and read Documentation/modules.txt. I hear that
2680 the GNU boycott of Apple is over, so even politically correct people
2681 are allowed to say Y here.
2683 AppleTalk-IP driver support
2685 This allows IP networking for users who only have AppleTalk
2686 networking available. This feature is experimental. With this
2687 driver, you can either encapsulate IP inside AppleTalk (e.g. if your
2688 Linux box is stuck on an AppleTalk only network) or decapsulate
2689 (e.g. if you want your Linux box to act as an Internet gateway for a
2690 zoo of AppleTalk connected Macs). You decide which one of the two
2691 you want in the following two questions; you can say Y to only one
2692 of them. Please see Documentation/networking/ipddp.txt for more
2695 This driver is also available as a module ( = code which can be
2696 inserted in and removed from the running kernel whenever you want).
2697 The module is called ipddp.o. If you want to compile it as a module,
2698 say M here and read Documentation/modules.txt.
2700 IP to AppleTalk-IP Encapsulation support
2702 If you say Y here, the kernel will be able to encapsulate IP packets
2703 inside AppleTalk frames; this is useful if your Linux box is stuck
2704 on an AppleTalk network (which hopefully contains a decapsulator
2705 somewhere). Please see Documentation/networking/ipddp.txt for more
2706 information. If you say Y here, you cannot say Y to "AppleTalk-IP to
2707 IP Decapsulation support", below.
2709 AppleTalk-IP to IP Decapsulation support
2711 If you say Y here, the kernel will be able to decapsulate
2712 AppleTalk-IP frames to IP packets; this is useful if you want your
2713 Linux box to act as an Internet gateway for an AppleTalk
2714 network. Please see Documentation/networking/ipddp.txt for more
2715 information. If you say Y here, you cannot say Y to "IP to
2716 AppleTalk-IP Encapsulation support", above.
2718 Apple/Farallon LocalTalk PC card support
2720 This allows you to use the AppleTalk PC card to connect to LocalTalk
2721 networks. The card is also known as the Farallon PhoneNet PC card.
2722 If you are in doubt, this card is the one with the 65C02 chip on it.
2723 You also need version 1.3.3 or later of the netatalk package.
2724 This driver is experimental, which means that it may not work.
2725 See the file Documentation/networking/ltpc.txt.
2727 COPS LocalTalk PC card support
2729 This allows you to use COPS AppleTalk cards to connect to LocalTalk
2730 networks. You also need version 1.3.3 or later of the netatalk
2731 package. This driver is experimental, which means that it may not
2732 work. This driver will only work if you choose "AppleTalk DDP"
2733 networking support, above.
2734 Please read the file Documentation/networking/cops.txt.
2736 Dayna firmware support
2738 Support COPS compatible cards with Dayna style firmware (Dayna
2739 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
2740 III, Farallon PhoneNET PC II).
2742 Tangent firmware support
2744 Support COPS compatible cards with Tangent style firmware (Tangent
2745 ATB_II, Novell NL-1000, Daystar Digital LT-200.
2747 Amateur Radio support
2749 If you want to connect your Linux computer to an amateur radio, say
2750 Y here. You want to read http://www.tapr.org/tapr/html/pkthome.html
2751 (to browse the WWW, you need to have access to a machine on the
2752 Internet that has a program like lynx or netscape) and the HAM-HOWTO
2753 and the AX25-HOWTO, both available via FTP (user: anonymous) from
2754 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that the answer to
2755 this question won't directly affect the kernel: saying N will just
2756 cause this configure script to skip all the questions about amateur
2759 Amateur Radio AX.25 Level 2
2761 This is the protocol used for computer communication over amateur
2762 radio. It is either used by itself for point-to-point links, or to
2763 carry other protocols such as tcp/ip. To use it, you need a device
2764 that connects your Linux box to your amateur radio. You can either
2765 use a low speed TNC (a Terminal Node Controller acts as a kind of
2766 modem connecting your computer's serial port to your radio's
2767 microphone input and speaker output) supporting the KISS protocol or
2768 one of the various SCC cards that are supported by the generic Z8530
2769 or the DMA SCC driver. Another option are the Baycom modem serial
2770 and parallel port hacks or the sound card modem (supported by their
2771 own drivers). If you say Y here, you also have to say Y to one of
2774 Information about where to get supporting software for Linux amateur
2775 radio as well as information about how to configure an AX.25 port is
2776 contained in the AX25-HOWTO, available via FTP (user: anonymous) in
2777 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You might also want to
2778 check out the file Documentation/networking/ax25.txt in the kernel
2779 source. More information about digital amateur radio in general is
2780 on the WWW at http://www.tapr.org/tapr/html/pkthome.html. (To browse
2781 the WWW, you need to have access to a machine on the Internet that
2782 has a program like lynx or netscape).
2784 This driver is also available as a module ( = code which can be
2785 inserted in and removed from the running kernel whenever you want).
2786 The module will be called ax25.o. If you want to compile it as a
2787 module, say M here and read Documentation/modules.txt.
2789 AX.25 DAMA Slave support
2790 CONFIG_AX25_DAMA_SLAVE
2791 DAMA is a mechanism to prevent collisions when doing AX.25
2792 networking. A DAMA server (called "master") accepts incoming traffic
2793 from clients (called "slaves") and redistributes it to other slaves.
2794 If you say Y here, your Linux box will act as a DAMA slave; this is
2795 transparent in that you don't have to do any special DAMA
2796 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
2799 AX.25 DAMA Master support
2800 CONFIG_AX25_DAMA_MASTER
2801 DAMA is a mechanism to prevent collisions when doing AX.25
2802 networking. A DAMA server (called "master") accepts incoming traffic
2803 from clients (called "slaves") and redistributes it to other
2804 slaves. If you say Y here, your Linux box will act as a DAMA server.
2807 Amateur Radio NET/ROM
2809 NET/ROM is a network layer protocol on top of AX.25 useful for
2812 A comprehensive listing of all the software for Linux amateur radio
2813 users as well as information about how to configure an AX.25 port is
2814 contained in the AX25-HOWTO, available via FTP (user: anonymous) in
2815 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You also might want to
2816 check out the file Documentation/networking/ax25.txt. More
2817 information about digital amateur radio in general is on the WWW at
2818 http://www.tapr.org/tapr/html/pkthome.html (To browse the WWW, you
2819 need to have access to a machine on the Internet that has a program
2820 like lynx or netscape).
2822 This driver is also available as a module ( = code which can be
2823 inserted in and removed from the running kernel whenever you want).
2824 The module will be called netrom.o. If you want to compile it as a
2825 module, say M here and read Documentation/modules.txt.
2827 Amateur Radio X.25 PLP (Rose)
2829 The Packet Layer Protocol (PLP) is a way to route packets over X.25
2830 connections in general and amateur radio AX.25 connections in
2831 particular, essentially an alternative to NET/ROM.
2833 A comprehensive listing of all the software for Linux amateur radio
2834 users as well as information about how to configure an AX.25 port is
2835 contained in the AX25-HOWTO, available via FTP (user: anonymous) in
2836 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You also might want to
2837 check out the file Documentation/networking/ax25.txt. More
2838 information about digital amateur radio in general is on the WWW at
2839 http://www.tapr.org/tapr/html/pkthome.html (To browse the WWW, you
2840 need to have access to a machine on the Internet that has a program
2841 like lynx or netscape).
2843 This driver is also available as a module ( = code which can be
2844 inserted in and removed from the running kernel whenever you want).
2845 The module will be called rose.o. If you want to compile it as a
2846 module, say M here and read Documentation/modules.txt.
2848 Serial port KISS driver for AX.25
2850 KISS is a protocol used for the exchange of data between a computer
2851 and a Terminal Node Controller (a small embedded system commonly
2852 used for networking over AX25 amateur radio connections).
2853 Although KISS is less advanced than the 6pack protocol, it has
2854 the advantage that it is already supported by most modern TNCs
2855 without the need for a firmware upgrade.
2857 If you want to compile this driver as a module ( = code which can be
2858 inserted in and removed from the running kernel whenever you want),
2859 say M here and read Documentation/modules.txt. The module will be
2862 Serial port 6PACK driver for AX.25
2864 6pack is a transmission protocol for the data exchange between your
2865 PC and your TNC (the Terminal Node Controller acts as a kind of
2866 modem connecting your computer's serial port to your radio's
2867 microphone input and speaker output). This protocol can be used as
2868 an alternative to KISS for networking over AX.25 amateur radio
2869 connections, but it has some extended functionality.
2871 Note that this driver is still experimental and might cause
2872 problems. For details about the features and the usage of the
2873 driver, read Documentation/networking/6pack.txt.
2875 If you want to compile this driver as a module ( = code which can be
2876 inserted in and removed from the running kernel whenever you want),
2877 say M here and read Documentation/modules.txt. The module will be
2882 AX.25 is the protocol used for computer communication over amateur
2883 radio. If you say Y here, you will be able to send and receive AX.25
2884 traffic over Ethernet (also called "BPQ AX.25"), which could be
2885 useful if some other computer on your local network has a direct
2886 amateur radio connection.
2888 High-speed (DMA) SCC driver for AX.25
2890 This is a driver for high-speed SCC boards, i.e. those supporting
2891 DMA on one port. You usually use those boards to connect your
2892 computer to an amateur radio modem (such as the WA4DSY 56kbps
2893 modem), in order to send and receive AX.25 packet radio network
2896 Currently, this driver supports Ottawa PI/PI2
2897 (http://hydra.carleton.ca/info/pi2.html) and Gracilis PackeTwin
2898 (http://www.paccomm.com/gracilis.html) boards. They are detected
2899 automatically. If you have one of these cards, say Y here and read
2900 the AX25-HOWTO, available via FTP (user: anonymous) in
2901 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/.
2903 This driver can operate multiple boards simultaneously. If you compile
2904 it as a module (by saying M instead of Y), it will be called dmascc.o.
2905 If you don't pass any parameter to the driver, all possible I/O
2906 addresses are probed. This could irritate other devices that are
2907 currently not in use. You may specify the list of addresses to be
2908 probed by "dmascc=addr1,addr2,..." (when compiled into the kernel
2909 image) or "io=addr1,addr2,..." (when loaded as a module). The network
2910 interfaces will be called dmascc0 and dmascc1 for the board detected
2911 first, dmascc2 and dmascc3 for the second one, and so on.
2913 Before you configure each interface with ifconfig, you MUST set
2914 certain parameters, such as channel access timing, clock mode, and
2915 DMA channel. This is accomplished with a small utility program,
2916 dmascc_cfg, available at
2917 http://www.nt.tuwien.ac.at/~kkudielk/Linux/. (To browse the WWW, you
2918 need to have access to a machine on the Internet that has a program
2919 like lynx or netscape).
2921 Z8530 SCC driver for AX.25
2923 These cards are used to connect your Linux box to an amateur radio
2924 in order to communicate with other computers. If you want to use
2925 this, read Documentation/networking/z8530drv.txt and the
2926 AX25-HOWTO, available via FTP (user: anonymous) at
2927 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Also make sure to say Y
2928 to "Amateur Radio AX.25 Level 2" support.
2930 If you want to compile this as a module ( = code which can be
2931 inserted in and removed from the running kernel whenever you want),
2932 say M here and read Documentation/modules.txt. The module will be
2935 additional delay for PA0HZP OptoSCC compatible boards
2937 Say Y here if you experience problems with the SCC driver not
2938 working properly; please read Documentation/networking/z8530drv.txt
2939 for details. If unsure, say N.
2941 #support for TRX that feedback the tx signal to rx
2944 ### Don't know what's going on here.
2947 BAYCOM picpar and par96 driver for AX.25
2949 This is a driver for Baycom style simple amateur radio modems that
2950 connect to a parallel interface. The driver supports the picpar and
2951 par96 designs. To configure the driver, use the sethdlc utility
2952 available in the standard ax25 utilities package. For information on
2953 the modems, see http://www.baycom.de (to browse the WWW, you need to
2954 have access to a machine on the Internet that has a program like
2955 lynx or netscape) and Documentation/networking/baycom.txt.
2957 If you want to compile this driver as a module ( = code which can be
2958 inserted in and removed from the running kernel whenever you want),
2959 say M here and read Documentation/modules.txt. This is recommended.
2960 The module will be called baycom_par.o.
2962 BAYCOM EPP driver for AX.25
2964 This is a driver for Baycom style simple amateur radio modems that
2965 connect to a parallel interface. The driver supports the EPP
2966 designs. To configure the driver, use the sethdlc utility available
2967 in the standard ax25 utilities package. For information on the
2968 modems, see http://www.baycom.de (to browse the WWW, you need to
2969 have access to a machine on the Internet that has a program like
2970 lynx or netscape) and Documentation/networking/baycom.txt.
2972 If you want to compile this driver as a module ( = code which can be
2973 inserted in and removed from the running kernel whenever you want),
2974 say M here and read Documentation/modules.txt. This is recommended.
2975 The module will be called baycom_par.o.
2977 BAYCOM ser12 full duplex driver for AX.25
2978 CONFIG_BAYCOM_SER_FDX
2979 This is one of two drivers for Baycom style simple amateur radio
2980 modems that connect to a serial interface. The driver supports the
2981 ser12 design in full duplex mode. In addition, it allows the
2982 baudrate to be set between 300 and 4800 baud (however not all modems
2983 support all baudrates). This is the preferred driver. The next
2984 driver, "BAYCOM ser12 half duplex driver for AX.25" is the old
2985 driver and still provided in case this driver does not work with
2986 your serial interface chip. To configure the driver, use the sethdlc
2987 utility available in the standard ax25 utilities package. For
2988 information on the modems, see http://www.baycom.de (to browse the
2989 WWW, you need to have access to a machine on the Internet that has a
2990 program like lynx or netscape) and
2991 Documentation/networking/baycom.txt.
2993 If you want to compile this driver as a module ( = code which can be
2994 inserted in and removed from the running kernel whenever you want),
2995 say M here and read Documentation/modules.txt. This is recommended.
2996 The module will be called baycom_ser_fdx.o.
2998 BAYCOM ser12 half duplex driver for AX.25
2999 CONFIG_BAYCOM_SER_HDX
3000 This is one of two drivers for Baycom style simple amateur radio
3001 modems that connect to a serial interface. The driver supports the
3002 ser12 design in full duplex mode. This is the old driver. It is
3003 still provided in case your serial interface chip does not work with
3004 the full duplex driver. This driver is depreciated. To configure
3005 the driver, use the sethdlc utility available in the standard ax25
3006 utilities package. For information on the modems, see
3007 http://www.baycom.de (to browse the WWW, you need to have access to
3008 a machine on the Internet that has a program like lynx or netscape)
3009 and Documentation/networking/baycom.txt.
3011 If you want to compile this driver as a module ( = code which can be
3012 inserted in and removed from the running kernel whenever you want),
3013 say M here and read Documentation/modules.txt. This is recommended.
3014 The module will be called baycom_ser_hdx.o.
3016 Sound card modem driver for AX.25
3018 This experimental driver allows a standard Sound Blaster or
3019 WindowsSoundSystem compatible sound card to be used as a packet radio
3020 modem (NOT as a telephone modem!), to send digital traffic over
3023 To configure the driver, use the sethdlc, smdiag and smmixer
3024 utilities available in the standard ax25 utilities package. For
3025 information on how to key the transmitter, see
3026 http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html (to browse
3027 the WWW, you need to have access to a machine on the Internet that
3028 has a program like lynx or netscape) and
3029 Documentation/networking/soundmodem.txt.
3031 If you want to compile this driver as a module ( = code which can be
3032 inserted in and removed from the running kernel whenever you want),
3033 say M here and read Documentation/modules.txt. This is recommended.
3034 The module will be called soundmodem.o.
3036 Sound card modem support for Sound Blaster and compatible cards
3037 CONFIG_SOUNDMODEM_SBC
3038 This option enables the soundmodem driver to use Sound Blaster and
3039 compatible cards. If you have a dual mode card (i.e. a WSS cards
3040 with a Sound Blaster emulation) you should say N here and Y to
3041 "Sound card modem support for WSS and Crystal cards", below, because
3042 this usually results in better performance. This option also supports
3043 SB16/32/64 in full duplex mode.
3045 Sound card modem support for WSS and Crystal cards
3046 CONFIG_SOUNDMODEM_WSS
3047 This option enables the soundmodem driver to use WindowsSoundSystem
3048 compatible cards. These cards feature a codec chip from either
3049 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
3050 Semiconductors (such as CS4248, CS423x). This option also supports
3051 the WSS full duplex operation which currently works with Crystal
3052 CS423x chips. If you don't need full duplex operation, do not enable
3053 it to save performance.
3055 Sound card modem support for 1200 baud AFSK modulation
3056 CONFIG_SOUNDMODEM_AFSK1200
3057 This option enables the soundmodem driver 1200 baud AFSK modem,
3058 compatible to popular modems using TCM3105 or AM7911. The demodulator
3059 requires about 12% of the CPU power of a Pentium 75 CPU per channel.
3061 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
3062 CONFIG_SOUNDMODEM_AFSK2400_7
3063 This option enables the soundmodem driver 2400 baud AFSK modem,
3064 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
3065 crystal. Note that the availability of this driver does _not_ imply
3066 that I recommend building such links. It is only here since users
3067 especially in eastern Europe have asked me to do so. In fact this
3068 modulation scheme has many disadvantages, mainly its incompatibility
3069 with many transceiver designs and the fact that the TCM3105 (if
3070 used) is operated widely outside its specifications.
3072 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
3073 CONFIG_SOUNDMODEM_AFSK2400_8
3074 This option enables the soundmodem driver 2400 baud AFSK modem,
3075 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
3076 Note that the availability of this driver does _not_ imply that I
3077 recommend building such links. It is only here since users
3078 especially in eastern Europe have asked me to do so. In fact this
3079 modulation scheme has many disadvantages, mainly its incompatibility
3080 with many transceiver designs and the fact that the TCM3105 (if
3081 used) is operated widely outside its specifications.
3083 Sound card modem support for 2666 baud AFSK modulation
3084 CONFIG_SOUNDMODEM_AFSK2666
3085 This option enables the soundmodem driver 2666 baud AFSK modem.
3086 This modem is experimental, and not compatible to anything
3089 Sound card modem support for 4800 baud 8PSK modulation
3090 CONFIG_SOUNDMODEM_PSK4800
3091 This option enables the soundmodem driver 4800 baud 8PSK modem.
3092 This modem is experimental, and not compatible to anything
3095 Sound card modem support for 4800 baud HAPN-1 modulation
3096 CONFIG_SOUNDMODEM_HAPN4800
3097 This option enables the soundmodem driver 4800 baud HAPN-1
3098 compatible modem. This modulation seems to be widely used 'down
3099 under' and in the Netherlands. Here, nobody uses it, so I could not
3100 test if it works. It is compatible to itself, however :-)
3102 Sound card modem support for 9600 baud FSK G3RUH modulation
3103 CONFIG_SOUNDMODEM_FSK9600
3104 This option enables the soundmodem driver 9600 baud FSK modem,
3105 compatible to the G3RUH standard. The demodulator requires about 4%
3106 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
3107 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
3108 can only use one protocol at a time, depending on what the other end
3111 CCITT X.25 Packet Layer
3113 X.25 is a set of standardized network protocols, similar in scope to
3114 frame relay; the one physical line from your box to the X.25 network
3115 entry point can carry several logical point-to-point connections
3116 (called "virtual circuits") to other computers connected to the X.25
3117 network. Governments, banks, and other organizations tend to use it
3118 to connect to each other or to form Wide Area Networks (WANs). Many
3119 countries have public X.25 networks. X.25 consists of two
3120 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
3121 if you want that) and the lower level data link layer protocol LAPB
3122 (say Y to "LAPB Data Link Driver" below if you want that).
3124 You can read more about X.25 at http://www.sangoma.com/x25.html and
3125 http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm
3126 (to browse the WWW, you need to have access to a machine on the
3127 Internet that has a program like lynx or netscape). Information
3128 about X.25 for Linux is contained in the files
3129 Documentation/networking/x25.txt and
3130 Documentation/networking/x25-iface.txt.
3132 One connects to an X.25 network either with a dedicated network card
3133 using the X.21 protocol (not yet supported by Linux) or one can do
3134 X.25 over a standard telephone line using an ordinary modem (say Y
3135 to "X.25 async driver" below) or over Ethernet using an ordinary
3136 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
3137 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
3138 and "LAPB over Ethernet driver" below).
3140 If you want to compile this driver as a module ( = code which can be
3141 inserted in and removed from the running kernel whenever you want),
3142 say M here and read Documentation/modules.txt. The module will be
3143 called x25.o. If unsure, say N.
3145 LAPB Data Link Driver (EXPERIMENTAL)
3147 Link Access Procedure, Balanced (LAPB) is the data link layer
3148 (i.e. the lower) part of the X.25 protocol. It offers a reliable
3149 connection service to exchange data frames with one other host, and
3150 it is used to transport higher level protocols (mostly X.25 Packet
3151 Layer, the higher part of X.25, but others are possible as
3152 well). Usually, LAPB is used with specialized X.21 network cards, but
3153 Linux currently supports LAPB only over Ethernet connections. If you
3154 want to use LAPB connections over Ethernet, say Y here and to "LAPB
3155 over Ethernet driver" below. Read
3156 Documentation/networking/lapb-module.txt for technical details.
3158 If you want to compile this driver as a module though ( = code which
3159 can be inserted in and removed from the running kernel whenever you
3160 want), say M here and read Documentation/modules.txt. The module
3161 will be called lapb.o. If unsure, say N.
3163 802.2 LLC (VERY EXPERIMENTAL)
3165 This is a Logical Link Layer protocol used for X.25 connections over
3166 Ethernet, using ordinary Ethernet cards.
3168 Bridging (EXPERIMENTAL)
3170 If you say Y here, then your Linux box will be able to act as an
3171 Ethernet bridge, which means that the different Ethernet segments it
3172 is connected to will appear as one Ethernet to the participants.
3173 Several such bridges can work together to create even larger
3174 networks of Ethernets using the IEEE802.1 spanning tree algorithm.
3175 As this is a standard, Linux bridges will interwork properly with
3176 other third party bridge products.
3178 In order to use this, you'll need the bridge configuration tools
3179 available via FTP (user: anonymous) from
3180 ftp://shadow.cabi.net/pub/Linux. Please read the Bridge mini-HOWTO
3181 for more information. Note that if your box acts as a bridge, it
3182 probably contains several Ethernet devices, but the kernel is not
3183 able to recognize more than one at boot time without help; for
3184 details read the Ethernet-HOWTO, available via FTP (user: anonymous)
3185 in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. The Bridging code is
3186 still in test. If unsure, say N.
3190 The Packet protocol is used by applications which communicate
3191 directly with network devices without an intermediate network
3192 protocol implemented in the kernel, e.g. tcpdump. If you want them
3193 to work, choose Y. This driver is also available as a module called
3194 af_packet.o ( = code which can be inserted in and removed from the
3195 running kernel whenever you want). If you want to compile it as a
3196 module, say M here and read Documentation/modules.txt. If unsure,
3199 Kernel/User network link driver
3201 This driver allows for two-way communication between certain parts
3202 of the kernel or modules and user processes; the user processes are
3203 able to read from and write to character special files in the /dev
3204 directory having major mode 36. So far, the kernel uses it to
3205 publish some network related information if you say Y to "Routing
3206 messages", below. It is also used by the firewall code to publish
3207 information about possible attacks if you say Y to "IP: firewall
3208 packet netlink device" further down. You also need to say Y here if
3209 you want to use arpd, a daemon that helps keep the internal ARP
3210 cache (a mapping between IP addresses and hardware addresses on the
3211 local network) small. The ethertap device, which lets user space
3212 programs read and write raw Ethernet frames, also needs the network
3213 link driver. If unsure, say Y.
3217 If you say Y here and create a character special file /dev/route
3218 with major number 36 and minor number 0 using mknod ("man mknod"),
3219 you (or some user space utility) can read some network related
3220 routing information from that file. Everything you write to that
3221 file will be discarded.
3223 Netlink device emulation
3225 This is a backward compatibility option, choose Y for now.
3226 This option will be removed soon.
3228 HIgh Performance Parallel Interface support (EXPERIMENTAL)
3230 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
3231 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
3232 can run over copper (25m) or fiber (300m on multi-mode or 10km on
3233 single-mode). If you are connected to a HIPPI network, and want
3234 to enable HIPPI support in the kernel, say Y here (you must also
3235 remember to enable the driver for your HIPPI card below). Most
3236 people will say N here.
3240 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CDROM or
3241 any other SCSI device under Linux, say Y and make sure that you know
3242 the name of your SCSI host adapter (the card inside your computer
3243 that "speaks" the SCSI protocol, also called SCSI controller),
3244 because you will be asked for it.
3246 You also need to say Y here if you want support for the parallel
3247 port version of the 100MB IOMEGA ZIP drive.
3249 Please read the SCSI-HOWTO, available via FTP (user: anonymous) in
3250 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3252 This driver is also available as a module ( = code which can be
3253 inserted in and removed from the running kernel whenever you want).
3254 The module will be called scsi_mod.o. If you want to compile it as a
3255 module, say M here and read Documentation/modules.txt and
3256 Documentation/scsi.txt. However, do not compile this as a module if
3257 your root filesystem (the one containing the directory /) is located
3262 If you want to use a SCSI hard disk or the SCSI or parallel port
3263 version of the IOMEGA ZIP drive under Linux, say Y and read the
3264 SCSI-HOWTO and the Disk-HOWTO, both available via FTP (user:
3265 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. This is
3266 NOT for SCSI CDROMs.
3268 This driver is also available as a module ( = code which can be
3269 inserted in and removed from the running kernel whenever you want).
3270 The module will be called sd_mod.o. If you want to compile it as a
3271 module, say M here and read Documentation/modules.txt and
3272 Documentation/scsi.txt. Do not compile this driver as a module if
3273 your root filesystem (the one containing the directory /) is located
3274 on a SCSI disk. In this case, do not compile the driver for your
3275 SCSI host adapter (below) as a module either.
3279 If you want to use a SCSI tape drive under Linux, say Y and read the
3280 SCSI-HOWTO, available via FTP (user: anonymous) in
3281 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO and
3282 drivers/scsi/README.st in the kernel source. This is NOT for SCSI
3285 This driver is also available as a module ( = code which can be
3286 inserted in and removed from the running kernel whenever you want).
3287 The module will be called st.o. If you want to compile it as a
3288 module, say M here and read Documentation/modules.txt and
3289 Documentation/scsi.txt .
3293 If you want to use a SCSI CDROM under Linux, say Y and read the
3294 SCSI-HOWTO and the CDROM-HOWTO from
3295 sunsite.unc.edu:/pub/Linux/docs/HOWTO. Also make sure to say Y or M
3296 to "ISO 9660 CDROM filesystem support" later.
3298 This driver is also available as a module ( = code which can be
3299 inserted in and removed from the running kernel whenever you want).
3300 The module will be called sr_mod.o. If you want to compile it as a
3301 module, say M here and read Documentation/modules.txt and
3302 Documentation/scsi.txt .
3304 Enable vendor-specific extensions (for SCSI CDROM)
3305 CONFIG_BLK_DEV_SR_VENDOR
3306 This enables the usage of vendor specific SCSI commands. This is
3307 required to support multisession CDs with old NEC/TOSHIBA cdrom
3308 drives (and HP Writers). If you have such a drive and get the first
3309 session only, try saying Y here; everybody else says N.
3311 SCSI generic support
3313 If you want to use SCSI scanners, synthesizers or CD-writers or just
3314 about anything having "SCSI" in its name other than hard disks,
3315 CDROMs or tapes, say Y here. These won't be supported by the kernel
3316 directly, so you need some additional software which knows how to
3317 talk to these devices using the SCSI protocol. For CD-writers, you
3318 would need the program cdwrite, available via FTP (user: anonymous)
3319 from ftp://sunsite.unc.edu/pub/Linux/utils/disk-management; for other
3320 devices, it's possible that you'll have to write the driver software
3321 yourself, so have a look at the SCSI-HOWTO and at the
3322 SCSI-Programming-HOWTO, both available via FTP (user: anonymous) in
3323 sunsite.unc.edu:/pub/Linux/docs/HOWTO.
3325 If you want to compile this as a module ( = code which can be
3326 inserted in and removed from the running kernel whenever you want),
3327 say M here and read Documentation/modules.txt and
3328 Documentation/scsi.txt. The module will be called sg.o. If unsure,
3331 Probe all LUNs on each SCSI device
3332 CONFIG_SCSI_MULTI_LUN
3333 If you have a SCSI device that supports more than one LUN (Logical
3334 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
3335 can say Y here to force the SCSI driver to probe for multiple LUNs.
3336 A SCSI device with multiple LUNs acts logically like multiple SCSI
3337 devices. The vast majority of SCSI devices have only one LUN, and
3338 so most people can say N here and should in fact do so, because it
3341 Verbose SCSI error reporting (kernel size +=12K)
3342 CONFIG_SCSI_CONSTANTS
3343 The error messages regarding your SCSI hardware will be easier to
3344 understand if you say Y here; it will enlarge your kernel by about
3345 12KB. If in doubt, say Y.
3347 SCSI logging facility
3349 This turns on a logging facility that can be used to debug a number
3350 of problems. Normally no logging output will appear, but you can
3351 enable logging with a shell command like:
3353 echo "scsi log token [level]" > /proc/scsi/scsi
3355 There are a number of things that can be used for 'token' (you can
3356 find them in the source: drivers/scsi/scsi.c), and this allows you
3357 to select the types of information you want, and the level allows
3358 you to select the level of verbosity. If you say N here, it may be
3359 harder to track down some types of SCSI problems. If you say Y here
3360 your kernel will be somewhat larger, but there should be no
3361 noticeable performance impact as long as you have logging turned
3364 AdvanSys SCSI support
3365 CONFIG_SCSI_ADVANSYS
3366 This is a driver for all SCSI host adapters manufactured by
3367 AdvanSys. It is documented in the kernel source in
3368 drivers/scsi/advansys.c.
3370 This driver is also available as a module ( = code which can be
3371 inserted in and removed from the running kernel whenever you want).
3372 If you want to compile it as a module, say M here and read
3373 Documentation/modules.txt. The module will be called advansys.o.
3375 Adaptec AHA152X/2825 support
3377 This is support for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
3378 SCSI host adapters. It is explained in section 3.3 of the
3379 SCSI-HOWTO, available via FTP (user: anonymous) at
3380 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You might also want to
3381 read the comments at the top of drivers/scsi/aha152x.c.
3383 This driver is also available as a module ( = code which can be
3384 inserted in and removed from the running kernel whenever you want).
3385 The module will be called aha152x.o. If you want to compile it as a
3386 module, say M here and read Documentation/modules.txt.
3388 Adaptec AHA1542 support
3390 This is support for a SCSI host adapter. It is explained in section
3391 3.4 of the SCSI-HOWTO, available via FTP (user: anonymous) at
3392 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that Trantor was
3393 recently purchased by Adaptec, and some former Trantor products are
3394 being sold under the Adaptec name. If it doesn't work out of the
3395 box, you may have to change some settings in drivers/scsi/aha1542.h.
3397 If you want to compile this as a module ( = code which can be
3398 inserted in and removed from the running kernel whenever you want),
3399 say M here and read Documentation/modules.txt. The module will be
3402 Adaptec AHA1740 support
3404 This is support for a SCSI host adapter. It is explained in section
3405 3.5 of the SCSI-HOWTO, available via FTP (user: anonymous) at
3406 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
3407 of the box, you may have to change some settings in
3408 drivers/scsi/aha1740.h.
3410 This driver is also available as a module ( = code which can be
3411 inserted in and removed from the running kernel whenever you want).
3412 The module will be called aha17400.o. If you want to compile it as a
3413 module, say M here and read Documentation/modules.txt.
3415 Adaptec AIC7xxx chipset SCSI controller support
3417 This is support for the various aic7xxx based Adaptec SCSI
3418 controllers. These include the 274x EISA cards, 284x VLB cards, 294x
3419 PCI cards, 394x PCI cards, 3985 PCI card, and several versions of
3420 the Adaptec built-in SCSI controllers on various PC motherboards.
3421 Information on the configuration options for this controller can be
3422 found by checking the help file for each of the available
3423 configuration options. You also want to read
3424 drivers/scsi/README.aic7xxx and the SCSI-HOWTO, available via FTP
3425 (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note
3426 that the AHA2920 SCSI host adapter is *not* supported by this
3427 driver; choose "Future Domain 16xx SCSI support" instead if you have
3430 If you want to compile this driver as a module ( = code which can be
3431 inserted in and removed from the running kernel whenever you want),
3432 say M here and read Documentation/modules.txt. The module will be
3435 Override driver defaults for commands per LUN
3436 CONFIG_OVERRIDE_CMDS
3437 Say Y here if you want to override the default maximum number of
3438 commands that a single device on the aic7xxx controller is allowed
3439 to have active at one time. This option only affects tagged queueing
3440 capable devices. The driver uses a "failsafe" value of 8 by default.
3441 This is much lower than many devices can handle, but left in place
3442 for safety's sake. If you say Y here, you can adjust the number of
3443 commands per LUN with the following configuration option.
3445 NOTE: This does not actually enable tagged queueing on any
3446 particular device. The driver has changed in this respect. Please
3447 see the file drivers/scsi/README.aic7xxx for more information on how
3448 to get particular devices to use tagged command queueing.
3452 Maximum number of commands per LUN
3453 CONFIG_AIC7XXX_CMDS_PER_LUN
3454 Specify the maximum number of commands you would like to allocate
3455 per LUN (a LUN is a Logical Unit Number -- some physical SCSI devices,
3456 e.g. CD jukeboxes, act logically as several separate units, each of
3457 which gets its own number).
3459 Reasonable figures are in the range of 14 to 32 commands per device,
3460 but depending on hardware could be increased or decreased from that
3461 figure. If the number is too high for any particular device, the
3462 driver will automatically compensate usually after only 10 minutes
3463 of uptime and will issue a message to alert you to the fact that the
3464 number of commands for that device has been reduced. It will not
3465 hinder performance if some of your devices eventually have their
3466 commands per LUN reduced, but is a waste of memory if all of your
3467 devices end up reducing this number down to a more reasonable
3470 Collect statistics to report in /proc
3471 CONFIG_AIC7XXX_PROC_STATS
3472 This option tells the driver to keep track of how many commands have
3473 been sent to each particular device and report that information to
3474 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
3475 the aic7xxx controller you want the information on. This adds a
3476 small amount of overhead to each and every SCSI command the aic7xxx
3477 driver handles, so if you aren't really interested in this
3478 information, it is best to leave it disabled. This will only work if
3479 you also say Y to "/proc filesystem support", below. If unsure, say N.
3481 Delay in seconds after SCSI bus reset
3482 CONFIG_AIC7XXX_RESET_DELAY
3483 This sets how long the driver will wait after resetting the SCSI bus
3484 before attempting to communicate with the devices on the SCSI bus
3485 again. This delay will be used during the reset phase at bootup time
3486 as well as after any reset that might occur during normal operation.
3487 Reasonable numbers range anywhere from 5 to 15 seconds depending on
3488 your devices. DAT tape drives are notorious for needing more time
3489 after a bus reset to be ready for the next command, but most hard
3490 drives and CD-ROM devices are ready in only a few seconds. This
3491 option has a maximum upper limit of 20 seconds to avoid bad
3492 interactions between the aic7xxx driver and the rest of the linux
3493 kernel. The default value has been reduced to 5 seconds. If this
3494 doesn't work with your hardware, try increasing this value.
3496 BusLogic SCSI support
3497 CONFIG_SCSI_BUSLOGIC
3498 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
3499 Adapters. Consult the SCSI-HOWTO, available via anonymous FTP from
3500 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, and the files
3501 README.BusLogic and README.FlashPoint in drivers/scsi for more
3502 information. If this driver does not work correctly without
3503 modification, please contact the author, Leonard N. Zubkoff, by
3504 email to lnz@dandelion.com.
3506 You can also build this driver as a module ( = code which can be
3507 inserted in and removed from the running kernel whenever you want),
3508 but only a single instance may be loaded. If you want to compile it
3509 as a module, say M here and read Documentation/modules.txt. The
3510 module will be called BusLogic.o.
3512 Omit BusLogic SCSI FlashPoint support
3513 CONFIG_SCSI_OMIT_FLASHPOINT
3514 This option allows you to omit the FlashPoint support from the
3515 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
3516 substantial, so users of MultiMaster Host Adapters may wish to omit
3519 DTC3180/3280 SCSI support
3521 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
3522 the SCSI-HOWTO, available via FTP (user: anonymous) at
3523 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO and the file
3524 drivers/scsi/README.dtc3x80.
3526 This driver is also available as a module (= code which can be
3527 inserted in and removed from the running kernel whenever you want).
3528 The module will be called dtc.o. If you want to compile it as a
3529 module, say M here and read Documentation/modules.txt.
3531 EATA-DMA (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
3532 CONFIG_SCSI_EATA_DMA
3533 This is support for the EATA-DMA protocol compliant SCSI Host
3534 Adapters like the SmartCache III/IV, SmartRAID controller families
3535 and the DPT PM2011B and PM2012B controllers. Note that there is
3536 also another driver for the same hardware: "EATA ISA/EISA/PCI
3537 support". You should only say Y to one of them. Please read the
3538 SCSI-HOWTO, available via FTP (user: anonymous) at
3539 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3541 This driver is also available as a module (= code which can be
3542 inserted in and removed from the running kernel whenever you want).
3543 The module will be called eata_dma.o. If you want to compile it as a
3544 module, say M here and read Documentation/modules.txt.
3546 EATA-PIO (old DPT PM2001, PM2012A) support
3547 CONFIG_SCSI_EATA_PIO
3548 This driver supports all EATA-PIO protocol compliant SCSI Host
3549 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
3550 host adapters could also use this driver but are discouraged from
3551 doing so, since this driver only supports hard disks and lacks
3552 numerous features. You might want to have a look at the SCSI-HOWTO,
3553 available via FTP (user: anonymous) at
3554 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3556 If you want to compile this as a module ( = code which can be
3557 inserted in and removed from the running kernel whenever you want),
3558 say M here and read Documentation/modules.txt. The module will be
3561 UltraStor 14F/34F support
3563 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
3564 The source at drivers/scsi/u14-34f.c contains some information about
3565 this hardware. If the driver doesn't work out of the box, you may
3566 have to change some settings in drivers/scsi/u14-34f.c. Read the
3567 SCSI-HOWTO, available via FTP (user: anonymous) at
3568 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that there is also
3569 another driver for the same hardware: "UltraStor SCSI support",
3570 below. You should say Y to both only if you want 24F support as
3573 This driver is also available as a module ( = code which can be
3574 inserted in and removed from the running kernel whenever you want).
3575 The module will be called u14-34f.o. If you want to compile it as a
3576 module, say M here and read Documentation/modules.txt.
3578 enable elevator sorting
3579 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
3580 This is a feature of SCSI-2 which improves performance: the host
3581 adapter can send a whole list of commands to a device in one
3582 batch. Some SCSI devices might not implement this properly, so the
3585 maximum number of queued commands
3586 CONFIG_SCSI_U14_34F_MAX_TAGS
3587 This specifies how many SCSI commands can be maximally queued for a
3588 given SCSI device. Go with the default unless you know what you're
3589 doing. Minimum is 2 and maximum is 8.
3591 Future Domain 16xx SCSI/AHA 2920 support
3592 CONFIG_SCSI_FUTURE_DOMAIN
3593 This is support for Future Domain's 16-bit SCSI host adapters
3594 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
3595 other adapters based on the Future Domain chipsets (Quantum
3596 ISA-200S, ISA-250MG; Adaptec AHA-2920; and at least one IBM board).
3597 It is explained in section 3.7 of the SCSI-HOWTO, available via FTP
3598 (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3600 This driver is also available as a module ( = code which can be
3601 inserted in and removed from the running kernel whenever you want).
3602 The module will be called fdomain.o. If you want to compile it as a
3603 module, say M here and read Documentation/modules.txt.
3605 Generic NCR5380/53c400 SCSI support
3606 CONFIG_SCSI_GENERIC_NCR5380
3607 This is the generic NCR family of SCSI controllers, not to be
3608 confused with the NCR 53c7 or 8xx controllers. It is explained in
3609 section 3.8 of the SCSI-HOWTO, available via FTP (user: anonymous)
3610 at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work
3611 out of the box, you may have to change some settings in
3612 drivers/scsi/g_NCR5380.h.
3614 This driver is also available as a module ( = code which can be
3615 inserted in and removed from the running kernel whenever you want).
3616 The module will be called g_NCR5380.o. If you want to compile it as
3617 a module, say M here and read Documentation/modules.txt.
3619 Enable NCR53c400 extensions
3620 CONFIG_SCSI_GENERIC_NCR53C400
3621 This enables certain optimizations for the NCR53c400 SCSI cards. You
3622 might as well try it out. Note that this driver will only probe for
3623 the Trantor T130B in its default configuration; you might have to
3624 pass a command line option to the kernel at boot time if it doesn't
3625 detect your card. See the file drivers/scsi/README.g_NCR5380 for
3628 NCR5380/53c400 mapping method (use Port for T130B)
3629 CONFIG_SCSI_G_NCR5380_PORT
3630 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
3631 port or memory mapped. You should know what you have. The most
3632 common card, Trantor T130B, uses port mapped mode.
3634 NCR53c7,8xx SCSI support
3635 CONFIG_SCSI_NCR53C7xx
3636 This is the 53c7 and 8xx NCR family of SCSI controllers, not to be
3637 confused with the NCR 5380 controllers. It is explained in section
3638 3.8 of the SCSI-HOWTO, available via FTP (user: anonymous) at
3639 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
3640 of the box, you may have to change some settings in
3641 drivers/scsi/53c7,8xx.h.
3643 This driver is also available as a module ( = code which can be
3644 inserted in and removed from the running kernel whenever you want).
3645 The module will be called 53c7,8xx.o. If you want to compile it as a
3646 module, say M here and read Documentation/modules.txt.
3648 always negotiate synchronous transfers
3649 CONFIG_SCSI_NCR53C7xx_sync
3650 In general, this is good; however, it is a bit dangerous since there
3651 are some broken SCSI devices out there. Take your chances. Safe bet
3654 allow FAST-SCSI [10MHz]
3655 CONFIG_SCSI_NCR53C7xx_FAST
3656 This will enable 10MHz FAST-SCSI transfers with your host
3657 adapter. Some systems have problems with that speed, so it's safest
3661 CONFIG_SCSI_NCR53C7xx_DISCONNECT
3662 This enables the disconnect/reconnect feature of the NCR SCSI
3663 controller. When you say Y here, a slow SCSI device will not lock
3664 the SCSI bus while processing a request, allowing simultaneous use
3665 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
3666 providing much better performance when using slow and fast SCSI
3667 devices at the same time. Some devices, however, do not operate
3668 properly with this option enabled, and will cause your SCSI system
3669 to hang, which might cause a system crash. The safe answer
3670 therefore is to say N.
3672 NCR53C8XX SCSI support
3673 CONFIG_SCSI_NCR53C8XX
3674 This is the BSD ncr driver adapted to linux for the NCR53C8XX family
3675 of PCI-SCSI controllers. This driver supports parity checking,
3676 tagged command queuing and fast synchronous data transfers up to 80
3677 MB/s with wide FAST-40 LVD devices and controllers.
3679 The NCR53C860 and NCR53C875 support FAST-20 transfers. The NCR53C895
3680 supports FAST-40 transfers with Ultra2 LVD devices.
3682 Please read drivers/scsi/README.ncr53c8xx for more information.
3684 synchronous data transfers frequency
3685 CONFIG_SCSI_NCR53C8XX_SYNC
3686 The SCSI Parallel Interface-2 Standard defines 4 classes of transfer
3687 rates: FAST-5, FAST-10, FAST-20 and FAST-40. The numbers are
3688 respectively the maximum data transfer rates in mega-transfers per
3689 second for each class. For example, a FAST-20 Wide 16 device is able
3690 to transfer data at 20 million 16 bit packets per second for a total
3693 You may specify 0 if you want to only use asynchronous data
3694 transfers. This is the safest and slowest option. Otherwise, specify
3695 a value between 5 and 40, depending on the capability of your SCSI
3696 controller. The higher the number, the faster the data transfer.
3697 Note that 40 should normally be ok since the driver decreases the
3698 value automatically according to the controller's capabilities.
3700 Your answer to this question is ignored for controllers with NVRAM,
3701 since the driver will get this information from the user set-up. It
3702 also can be overridden using a boot setup option, as follows
3703 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
3704 for FAST-20 synchronous data transfer (20 mega-transfers per
3707 The normal answer therefore is not to go with the default but to
3708 select the maximum value 40 allowing the driver to use the maximum
3709 value supported by each controller. If this causes problems with
3710 your SCSI devices, you should come back and decrease the value.
3712 There is no safe option other than using good cabling, right
3713 terminations and SCSI conformant devices.
3716 CONFIG_SCSI_NCR53C8XX_IOMAPPED
3717 If you say Y here, the driver will use normal IO, as opposed to
3718 memory mapped IO. Memory mapped IO has less latency than normal IO
3719 and works for most Intel-based hardware. Under Linux/Alpha only
3720 normal IO is currently supported by the driver and so, this option
3721 has no effect on those systems.
3723 The normal answer therefore is N; try Y only if you encounter SCSI
3726 not allow targets to disconnect
3727 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
3728 This option is only provided for safety if you suspect some SCSI
3729 device of yours to not support properly the target-disconnect
3730 feature. In that case, you would say Y here. In general however, to
3731 not allow targets to disconnect is not reasonable if there is more
3732 than 1 device on a SCSI bus. The normal answer therefore is N.
3734 default tagged command queue depth
3735 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
3736 "Tagged command queuing" is a feature of SCSI-2 which improves
3737 performance: the host adapter can send several SCSI commands to a
3738 device's queue even if previous commands haven't finished yet. Some
3739 SCSI devices don't implement this properly; if you want to disable
3740 this feature, enter 0 or 1 here (it doesn't matter which).
3742 The default value is 8 and should be supported by most hard disks.
3743 This option has no effect for adapters with NVRAM, since the driver
3744 will get this information from the user set-up. It also can be
3745 overridden using a boot setup option, as follows (example):
3746 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to 4,
3747 set queue depth to 16 for target 2 and target 3 on controller 0 and
3748 set queue depth to 10 for target 0 / lun 2 on controller 1.
3750 The normal answer therefore is to go with the default 8 and to use
3751 a boot command line option for devices that need to use a different
3752 command queue depth.
3754 There is no safe option other than using good SCSI devices.
3756 maximum number of queued commands
3757 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
3758 This option allows you to specify the maximum number of commands
3759 that can be queued to any device, when tagged command queuing is
3760 possible. The default value is 32. Minimum is 2, maximum is 64.
3761 For value less than 32, this option only saves a little memory
3762 (8*7*(32-MAXTAGS) bytes), so using less than 32 isn't worth it.
3763 For value greater than 32, latency on reselection will be increased
3764 by 1 or 2 micro-seconds. So, the normal answer here is to go with the
3765 default value 32 unless you are using very large hard disks with
3766 large cache (>= 1MB) that are able to take advantage of more than
3769 There is no safe option and the default answer is recommended.
3771 assume boards are SYMBIOS compatible
3772 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
3773 This option allows you to enable some features depending on GPIO
3774 wiring. These General Purpose Input/Output pins can be used for
3775 vendor specific features or implementation of the standard SYMBIOS
3776 features. Genuine SYMBIOS controllers use GPIO0 in output for
3777 controller LED and GPIO3 bit as a flag indicating
3778 singled-ended/differential interface. The Tekram DC-390U/F boards
3779 uses a different GPIO wiring.
3781 Your answer to this question is ignored if all your controllers have
3782 NVRAM, since the driver is able to detect the board type from the
3785 If all the controllers in your system are genuine SYMBIOS boards or
3786 use BIOS and drivers from SYMBIOS, you would want to say Y here,
3787 otherwise N. N is the safe answer.
3789 enable profiling statistics gathering
3790 CONFIG_SCSI_NCR53C8XX_PROFILE
3791 This option allows you to enable profiling information gathering.
3792 These statistics are not very accurate due to the low frequency
3793 of the kernel clock (100 Hz on i386) and have performance impact
3794 on systems that use very fast devices.
3796 The normal answer therefore is N.
3800 This is support for the IBM SCSI adapter found in many of the PS/2
3801 series computers. These machines have an MCA bus, so you need to say
3802 Y to "MCA support" as well and read Documentation/mca.txt.
3804 If the adapter isn't found during boot (a common problem for models
3805 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
3806 option, where <pun> is the id of the SCSI subsystem (usually 7, but
3807 if that doesn't work check your reference diskette). Owners of model
3808 95 with a LED-matrix-display can in addition activate some activity
3809 info like under OS/2, but more informative, by setting
3810 'ibmmcascsi=display' as an additional kernel parameter. Try "man
3811 bootparam" or see the documentation of your boot loader about how to
3812 pass options to the kernel. The lilo procedure is also explained in
3813 the SCSI-HOWTO, available via FTP (user: anonymous) in
3814 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3816 If you want to compile this driver as a module ( = code which can be
3817 inserted in and removed from the running kernel whenever you want),
3818 say M here and read Documentation/modules.txt. The module will be
3822 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
3823 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
3824 are assigned to the drive letters, starting with the lowest SCSI-id
3825 (physical number -- pun) to be drive C:, as seen from DOS and
3826 similar operating systems. When looking into papers describing the
3827 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
3828 The SCSI-standard follows a hardware-hierarchy which says that id 7
3829 has the highest priority and id 0 the lowest. Therefore, the host
3830 adapters are still today everywhere placed as SCSI-id 7 by default.
3831 In the SCSI-standard, the drive letters express the priority of the
3832 disk. C: should be the hard disk, or a partition on it, with the
3833 highest priority. This must therefore be the disk with the highest
3834 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
3835 original definition of the SCSI-standard as also industrial- and
3836 process-control-machines, like VME-CPUs running under realtime-OSs
3837 (e.g. LynxOS, OS9) do.
3839 If you like to run Linux on your MCA-machine with the same
3840 assignment of hard disks as seen from e.g. DOS or OS/2 on your
3841 machine, which is in addition conformant to the SCSI-standard, you
3842 must say Y here. This is also necessary for MCA-Linux users who want
3843 to keep downward- compatibility to older releases of the
3844 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
3847 If you like to have the lowest SCSI-id assigned as drive C:, as
3848 modern SCSI-BIOSes do, which does not conform to the standard, but
3849 is widespread and common in the PC-world of today, you must say N
3850 here. If unsure, say Y.
3852 Reset SCSI-devices at boot time
3853 CONFIG_IBMMCA_SCSI_DEV_RESET
3854 By default, SCSI-devices are reset when the machine is powered on.
3855 However, some devices exist, like special-control-devices,
3856 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
3857 not reset when switched on. If you say Y here, each device connected
3858 to your SCSI-bus will be issued a reset-command after it has been
3859 probed, while the kernel is booting. This may cause problems with
3860 more modern devices, like hard disks, which do not appreciate these
3861 reset commands, and can cause your system to hang. So say Y only if
3862 you know that one of your older devices needs it; N is the safe
3865 Always IN2000 SCSI support
3867 This is support for an ISA bus SCSI host adapter. You'll find more
3868 information in drivers/scsi/in2000.readme. If it doesn't work out of
3869 the box, you may have to change the jumpers for IRQ or address
3872 If you want to compile this as a module ( = code which can be
3873 inserted in and removed from the running kernel whenever you want),
3874 say M here and read Documentation/modules.txt. The module will be
3879 This is support for a SCSI host adapter. It is explained in section
3880 3.10 of the SCSI-HOWTO, available via FTP (user: anonymous) at
3881 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
3882 of the box, you may have to change some settings in
3883 drivers/scsi/pas16.h.
3885 This driver is also available as a module ( = code which can be
3886 inserted in and removed from the running kernel whenever you want).
3887 The module will be called pas16.o. If you want to compile it as a
3888 module, say M here and read Documentation/modules.txt.
3892 This is support for the PCI2000I EIDE interface card which acts as a
3893 SCSI host adapter. Please read the SCSI-HOWTO, available via FTP
3894 (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3896 This driver is also available as a module called pci2000.o ( = code
3897 which can be inserted in and removed from the running kernel
3898 whenever you want). If you want to compile it as a module, say M
3899 here and read Documentation/modules.txt.
3902 CONFIG_SCSI_PCI2220I
3903 This is support for the PCI2220i EIDE interface card which acts as a
3904 SCSI host adapter. Please read the SCSI-HOWTO, available via FTP
3905 (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3907 This driver is also available as a module called pci2220i.o ( = code
3908 which can be inserted in and removed from the running kernel
3909 whenever you want). If you want to compile it as a module, say M
3910 here and read Documentation/modules.txt.
3914 This is support for the PSI240i EIDE interface card which acts as a
3915 SCSI host adapter. Please read the SCSI-HOWTO, available via FTP
3916 (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3918 This driver is also available as a module called psi240i.o ( = code
3919 which can be inserted in and removed from the running kernel
3920 whenever you want). If you want to compile it as a module, say M
3921 here and read Documentation/modules.txt.
3923 Qlogic FAS SCSI support
3924 CONFIG_SCSI_QLOGIC_FAS
3925 This driver works only with the ISA, VLB, and PCMCIA versions of the
3926 Qlogic FastSCSI! cards as well as any other card based on the FASXX
3927 chip (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards); it
3928 does NOT support the PCI version. The PCI versions are supported by
3929 the Qlogic ISP driver though. Information about this driver is
3930 contained in drivers/scsi/README.qlogicfas. You should also read
3931 the SCSI-HOWTO, available via FTP (user: anonymous) at
3932 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3934 This driver is also available as a module ( = code which can be
3935 inserted in and removed from the running kernel whenever you want).
3936 The module will be called qlogicfas.o. If you want to compile it as
3937 a module, say M here and read Documentation/modules.txt.
3939 Qlogic ISP SCSI support (EXPERIMENTAL)
3940 CONFIG_SCSI_QLOGIC_ISP
3941 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
3942 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
3943 card is supported by the "AM53/79C974 PCI SCSI" driver). If you say
3944 Y here, make sure to say Y to "PCI BIOS support" as well. More
3945 information is contained in the file
3946 drivers/scsi/README.qlogicisp. You should also read the SCSI-HOWTO,
3947 available via FTP (user: anonymous) at
3948 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
3950 This driver is also available as a module ( = code which can be
3951 inserted in and removed from the running kernel whenever you want).
3952 The module will be called qlogicisp.o. If you want to compile it as
3953 a module, say M here and read Documentation/modules.txt.
3955 Seagate ST-02 and Future Domain TMC-8xx SCSI support
3957 These are 8-bit SCSI controllers; the ST-01 is also supported by
3958 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
3959 available via FTP (user: anonymous) at
3960 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
3961 of the box, you may have to change some settings in
3962 drivers/scsi/seagate.h.
3964 This driver is also available as a module ( = code which can be
3965 inserted in and removed from the running kernel whenever you want).
3966 The module will be called seagate.o. If you want to compile it as a
3967 module, say M here and read Documentation/modules.txt.
3969 Trantor T128/T128F/T228 SCSI support
3971 This is support for a SCSI host adapter. It is explained in section
3972 3.11 of the SCSI-HOWTO, available via FTP (user: anonymous) at
3973 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
3974 of the box, you may have to change some settings in
3975 drivers/scsi/t128.h. Note that Trantor was purchased by Adaptec, and
3976 some former Trantor products are being sold under the Adaptec name.
3978 This driver is also available as a module ( = code which can be
3979 inserted in and removed from the running kernel whenever you want).
3980 The module will be called t128.o. If you want to compile it as a
3981 module, say M here and read Documentation/modules.txt.
3983 UltraStor SCSI support
3984 CONFIG_SCSI_ULTRASTOR
3985 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
3986 adapter family. This driver is explained in section 3.12 of the
3987 SCSI-HOWTO, available via FTP (user: anonymous) at
3988 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If it doesn't work out
3989 of the box, you may have to change some settings in
3990 drivers/scsi/ultrastor.h.
3992 Note that there is also another driver for the same hardware:
3993 "UltraStor 14F/34F support", above.
3995 If you want to compile this as a module ( = code which can be
3996 inserted in and removed from the running kernel whenever you want),
3997 say M here and read Documentation/modules.txt. The module will be
4000 7000FASST SCSI support
4001 CONFIG_SCSI_7000FASST
4002 This driver supports the Western Digital 7000 SCSI host adapter
4003 family. Some information is in the source: drivers/scsi/wd7000.c.
4005 This driver is also available as a module ( = code which can be
4006 inserted in and removed from the running kernel whenever you
4007 want). The module will be called wd7000.o. If you want to compile it
4008 as a module, say M here and read Documentation/modules.txt.
4010 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
4012 This driver supports all the EATA/DMA-compliant SCSI host adapters
4013 and does not need any BIOS32 service. DPT ISA and all EISA i/o
4014 addresses are probed looking for the "EATA" signature. If you said Y
4015 to "PCI BIOS support", the addresses of all the PCI SCSI controllers
4016 reported by BIOS32 are probed as well. You want to read
4017 the start of drivers/scsi/eata.c and the SCSI-HOWTO, available via
4018 FTP (user: anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
4020 Note that there is also another driver for the same hardware
4021 available: "EATA-DMA support". You should say Y to only one of them.
4023 If you want to compile this as a module ( = code which can be
4024 inserted in and removed from the running kernel whenever you want),
4025 say M here and read Documentation/modules.txt. The module will be
4028 enable tagged command queuing
4029 CONFIG_SCSI_EATA_TAGGED_QUEUE
4030 This is a feature of SCSI-2 which improves performance: the host
4031 adapter can send several SCSI commands to a device's queue even if
4032 previous commands haven't finished yet. Some SCSI devices don't
4033 implement this properly, so the safe answer is N.
4035 enable elevator sorting
4036 CONFIG_SCSI_EATA_LINKED_COMMANDS
4037 This is a feature of SCSI-2 which improves performance: the host
4038 adapter can send a whole list of commands to a device in one
4039 batch. Some SCSI devices might not implement this properly, so the
4042 maximum number of queued commands
4043 CONFIG_SCSI_EATA_MAX_TAGS
4044 This specifies how many SCSI commands can be maximally queued for a
4045 given SCSI device. Go with the default unless you know what you're
4046 doing. Minimum is 2 and maximum is 16. This number will only have an
4047 effect if you said Y to "enable tagged command queuing", above.
4049 NCR53c406a SCSI support
4050 CONFIG_SCSI_NCR53C406A
4051 This is support for the NCR53c406a SCSI host adapter. For user
4052 configurable parameters, check out drivers/scsi/NCR53c406.c in the
4053 kernel source. Also read the SCSI-HOWTO, available via FTP (user:
4054 anonymous) at ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
4056 If you want to compile this driver as a module ( = code which can be
4057 inserted in and removed from the running kernel whenever you want),
4058 say M here and read Documentation/modules.txt. The module will be
4061 Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support
4063 This driver supports PCI SCSI host adapters based on the Am53C974A
4064 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
4065 PCscsi/PCnet (Am53/79C974) solutions.
4066 Documentation can be found in linux/drivers/scsi/README.tmscsim.
4068 Note that this driver does NOT support Tekram DC390W/U/F, which are
4069 based on NCR/Symbios chips. Use the NCR53C8XX driver for those.
4070 Also note, that there is another generic Am53C974 driver.
4072 If you want to compile this driver as a module ( = code which can be
4073 inserted in and removed from the running kernel whenever you want),
4074 say M here and read Documentation/modules.txt. The module will be
4077 Skip support for other Am53/79C974 based SCSI adapters
4078 CONFIG_SCSI_DC390T_NOGENSUPP
4079 Normally, the DC390(T) SCSI driver relies on the DC390 EEPROM to get
4080 initial values for its settings, such as speed, termination, etc.
4081 If it can't find this EEPROM, it will use defaults or the user
4082 supplied boot/module parameters. For details on driver configuration
4083 see linux/drivers/scsi/README.tmscsim.
4085 With this option set, if no EEPROM is found, the driver gives up and
4086 thus only supports Tekram DC390(T) adapters. This can be useful if
4087 you have a DC390(T) and another Am53C974 based adapter, which, for
4088 some reason, you want to drive with the other AM53C974 driver.
4092 AM53/79C974 PCI SCSI support
4093 CONFIG_SCSI_AM53C974
4094 This is support for the AM53/79C974 SCSI host adapters. Please read
4095 drivers/scsi/README.AM53C974 for details. Also, the SCSI-HOWTO,
4096 available via FTP (user: anonymous) at
4097 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, is for you.
4099 Note that there is another driver for AM53C974 based adapters: The
4100 Tekram DC390(T) driver.
4102 If you want to compile this driver as a module ( = code which can be
4103 inserted in and removed from the running kernel whenever you want),
4104 say M here and read Documentation/modules.txt. The module will be
4107 GDT SCSI Disk Array Controller support
4109 This is a driver for all SCSI Disk Array Controllers (EISA/ISA/PCI)
4110 manufactured by ICP vortex. It is documented in the kernel source in
4111 drivers/scsi/gdth.c and drivers/scsi/gdth.h.
4113 This driver is also available as a module ( = code which can be
4114 inserted in and removed from the running kernel whenever you want).
4115 If you want to compile it as a module, say M here and read
4116 Documentation/modules.txt.
4118 IOMEGA Parallel Port ZIP drive SCSI support
4120 This driver supports the parallel port version of IOMEGA's ZIP drive
4121 (a 100Mb removable media device). For more information about this
4122 driver and how to use it you should read the file
4123 drivers/scsi/README.ppa. You should also read the SCSI-HOWTO, which
4124 is available via FTP (user: anonymous) from
4125 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If you use this driver,
4126 you will still be able to use the parallel port for other tasks,
4127 such as a printer; it is safe to compile both drivers into the
4130 Note that you can say N here if you have the SCSI version of the ZIP
4131 drive: it will be supported automatically if you said Y to the
4132 generic "SCSI disk support", above.
4134 This driver is also available as a module which can be inserted in
4135 and removed from the running kernel whenever you want. To compile
4136 this driver as a module, say M here and read
4137 Documentation/modules.txt. The module will be called ppa.o.
4140 CONFIG_SCSI_PPA_HAVE_PEDANTIC
4141 EPP (Enhanced Parallel Port) is a standard for parallel ports which
4142 allows them to act as expansion buses that can handle up to 64
4143 peripheral devices. Some parallel port chipsets are slower than
4144 their motherboard, and so we have to control the state of the FIFO
4145 every now and then to avoid data loss. The permitted values for
4146 this option are 0 (don't check FIFO), 1 (check FIFO every 4 bytes),
4147 2 (check FIFO every other byte) and 3 (check FIFO every time). If
4148 your EPP chipset is from the SMC series, you are likely to have to
4149 set this value greater than 0.
4151 SGI wd93 Scsi Driver
4153 This is the SCSI driver for WD33C93 / WD33C95 SCSI chips used in many
4156 SCSI Debug host simulator.
4158 This is a host adapter simulator that can be programmed to simulate
4159 a large number of conditions that could occur on a real bus. The
4160 advantage is that many hard to reproduce problems can be tested in a
4161 controlled environment where there is reduced risk of losing
4162 important data. This is primarily of use to people trying to debug
4163 the middle and upper layers of the SCSI subsystem. If unsure, say N.
4165 Fibre Channel support
4167 This is an experimental support for storage arrays connected to
4168 the system using Fibre Optic and the "X3.269-199X Fibre Channel
4169 Protocol for SCSI" specification. You'll also need the generic SCSI
4170 support, as well as the drivers for the storage array itself and
4171 for the interface adapter such as SOC. This subsystem could even
4172 serve for IP networking, with some code extensions.
4178 Serial Optical Channel is an interface card with one or two Fibre Optic
4179 ports, each of which can be connected to a disk array. Only the SBus
4180 incarnation of the adapter is supported at the moment.
4182 SparcSTORAGE Array 100 and 200 series
4184 If you never bought a disk array made by Sun, go with N.
4187 CONFIG_SCSI_ACORNSCSI_3
4188 This enables support for the Acorn SCSI card (aka30). If you have an
4189 Acorn system with one of these, say Y. If unsure, say N.
4191 Acorn SCSI tagged queue support
4192 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
4193 Say Y here to enable tagged queuing support on the Acorn SCSI card.
4195 This is a feature of SCSI-2 which improves performance: the host
4196 adapter can send several SCSI commands to a device's queue even if
4197 previous commands haven't finished yet. Some SCSI devices don't
4198 implement this properly, so the safe answer is N.
4200 Acorn SCSI Synchronous transfers support
4201 CONFIG_SCSI_ACORNSCSI_SYNC
4202 Say Y here to enable synchronous transfer negotiation with all targets
4203 on the Acorn SCSI card.
4205 In general, this improves performance; however some SCSI devices
4206 don't implement it properly, so the safe answer is N.
4210 This enables support for the Oak SCSI card. If you have an Acorn system
4211 with one of these, say Y. If unsure, say N.
4213 Cumana SCSI I support
4214 CONFIG_SCSI_CUMANA_1
4215 This enables support for the Cumana SCSI I card. If you have an Acorn
4216 system with one of these, say Y. If unsure, say N.
4218 Cumana SCSI II support
4219 CONFIG_SCSI_CUMANA_2
4220 This enables support for the Cumana SCSI II card. If you have an Acorn
4221 system with one of these, say Y. If unsure, say N.
4225 This enables support for the EcoSCSI card -- a small card that sits in
4226 the Econet socket. If you have an Acorn system with one of these,
4227 say Y. If unsure, say N.
4230 CONFIG_SCSI_EESOXSCSI
4231 This enables support for the EESOX SCSI card. If you have an Acorn
4232 system with one of these, say Y, otherwise say N.
4234 Powertec SCSI support
4235 CONFIG_SCSI_POWERTECSCSI
4236 This enables support for the Powertec SCSI card on Acorn systems. If
4237 you have one of these, say Y. If unsure, say N.
4239 Network device support?
4241 You can say N here if you don't intend to connect to any other
4242 computer at all or if all your connections will be over a telephone
4243 line with a modem either via UUCP (UUCP is a protocol to forward
4244 mail and news between unix hosts over telephone lines; read the
4245 UUCP-HOWTO, available via FTP (user: anonymous) in
4246 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO) or dialing up a shell
4247 account or a BBS, even using term (term is a program which gives you
4248 almost full Internet connectivity if you have a regular dial up
4249 shell account on some Internet connected Unix computer. Read
4250 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
4251 the WWW, you need to have access to a machine on the Internet that
4252 has a program like lynx or netscape)).
4254 You'll have to say Y if your computer contains a network card that
4255 you want to use under Linux (make sure you know its name because you
4256 will be asked for it and read the Ethernet-HOWTO (especially if you
4257 plan to use more than one network card under Linux), available from
4258 sunsite.unc.edu:/pub/Linux/docs/HOWTO/mini) or if you want to use
4259 SLIP (Serial Line Internet Protocol is the protocol used to send
4260 Internet traffic over telephone lines or null modem cables) or CSLIP
4261 (compressed SLIP) or PPP (Point to Point Protocol, a better and
4262 newer replacement for SLIP) or PLIP (Parallel Line Internet Protocol
4263 is mainly used to create a mini network by connecting the parallel
4264 ports of two local machines) or AX.25/KISS (protocol for sending
4265 Internet traffic over radio links).
4267 Make sure to read the NET-2-HOWTO. Eventually, you will have to read
4268 Olaf Kirch's excellent and free book "Network Administrator's
4269 Guide", to be found in sunsite.unc.edu:/pub/Linux/docs/LDP. If
4272 Dummy net driver support
4274 This is essentially a bit-bucket device (i.e. traffic you send to
4275 this device is consigned into oblivion) with a configurable IP
4276 address. It is most commonly used in order to make your currently
4277 inactive SLIP address seem like a real address for local programs.
4278 If you use SLIP or PPP, you might want to say Y here. Read about it
4279 in the Network Administrator's Guide, available via FTP (user:
4280 anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/LDP. Since this
4281 thing often comes in handy, the default is Y. It won't enlarge your
4282 kernel either. What a deal.
4284 If you want to compile this as a module ( = code which can be
4285 inserted in and removed from the running kernel whenever you want),
4286 say M here and read Documentation/modules.txt. The module will be
4287 called dummy.o. If you want to use more than one dummy device at a
4288 time, you need to compile this driver as a module. Instead of
4289 'dummy', the devices will then be called 'dummy0', 'dummy1' etc.
4291 SLIP (serial line) support
4293 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
4294 connect to your Internet service provider or to connect to some
4295 other local Unix box or if you want to configure your Linux box as a
4296 Slip/CSlip server for other people to dial in. SLIP (Serial Line
4297 Internet Protocol) is a protocol used to send Internet traffic
4298 over telephone lines or serial cables (also known as
4299 null modems); nowadays, the PPP is a more common protocol than SLIP.
4301 Normally, your access provider has to support SLIP in order for you
4302 to be able to use it, but there is now a SLIP emulator called SLiRP
4303 around (available via FTP (user: anonymous) from
4304 ftp://sunsite.unc.edu/pub/Linux/system/network/serial/ ) which
4305 allows you to use SLIP over a regular dial up shell connection. If
4306 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
4307 NET-2-HOWTO, available via FTP (user: anonymous) in
4308 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, explains how to
4309 configure SLIP. Note that you don't need this option if you just
4310 want to run term (term is a program which gives you almost full
4311 Internet connectivity if you have a regular dial up shell account on
4312 some Internet connected Unix computer. Read
4313 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
4314 the WWW, you need to have access to a machine on the Internet that
4315 has a program like lynx or netscape)). SLIP support will enlarge
4316 your kernel by about 4kB. If unsure, say N.
4318 If you want to compile this as a module ( = code which can be
4319 inserted in and removed from the running kernel whenever you want),
4320 say M here and read Documentation/modules.txt as well as
4321 Documentation/networking/net-modules.txt. The module will be called
4324 CSLIP compressed headers
4325 CONFIG_SLIP_COMPRESSED
4326 This protocol is faster than SLIP because it uses compression on the
4327 TCP/IP headers (not on the data itself), but it has to be supported
4328 on both ends. Ask your access provider if you are not sure and say
4329 Y, just in case. You will still be able to use plain SLIP. If you
4330 plan to use SLiRP, the SLIP emulator (available via FTP (user:
4332 ftp://sunsite.unc.edu/pub/Linux/system/network/serial/) which allows
4333 you to use SLIP over a regular dial up shell connection, you
4334 definitely want to say Y here. The NET-2-HOWTO, available via FTP
4335 (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO,
4336 explains how to configure CSLIP. This won't enlarge your kernel.
4338 Keepalive and linefill
4340 Adds additional capabilities to the SLIP driver to support the
4341 RELCOM line fill and keepalive monitoring. Ideal on poor quality
4344 Six bit SLIP encapsulation
4345 CONFIG_SLIP_MODE_SLIP6
4346 Just occasionally you may need to run IP over hostile serial
4347 networks that don't pass all control characters or are only seven
4348 bit. Saying Y here adds an extra mode you can use with SLIP:
4349 "slip6". In this mode, SLIP will only send normal ASCII symbols over
4350 the serial device. Naturally, this has to be supported at the other
4351 end of the link as well. It's good enough, for example, to run IP
4352 over the async ports of a Camtec JNT Pad. If unsure, say N.
4354 PPP (point-to-point) support
4356 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
4357 the same purpose: sending Internet traffic over telephone (and other
4358 serial) lines. Ask your access provider if they support it, because
4359 otherwise you can't use it (not quite true any more: the free
4360 program SLiRP can emulate a PPP line if you just have a regular dial
4361 up shell account on some UNIX computer; get it via FTP (user:
4363 ftp://sunsite.unc.edu/pub/Linux/system/network/serial/). Note that
4364 you don't need "PPP support" if you just want to run term (term is a
4365 program which gives you almost full Internet connectivity if you
4366 have a regular dial up shell account on some Internet connected UNIX
4368 http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html (to browse
4369 the WWW, you need to have access to a machine on the Internet that
4370 has a program like lynx or netscape)).
4372 To use PPP, you need an additional program called pppd as described
4373 in Documentation/networking/ppp.txt and in the PPP-HOWTO, available
4374 from sunsite.unc.edu:/pub/Linux/docs/HOWTO. If you upgrade from an
4375 older kernel, you might need to upgrade pppd as well. The PPP option
4376 enlarges your kernel by about 16kB.
4378 This driver is also available as a module ( = code which can be
4379 inserted in and removed from the running kernel whenever you want).
4380 If you said Y to "Version information on all symbols" above, then
4381 you cannot compile the PPP driver into the kernel; you can then only
4382 compile it as a module. The module will be called ppp.o. If you want
4383 to compile it as a module, say M here and read
4384 Documentation/modules.txt as well as
4385 Documentation/networking/net-modules.txt. Note that, no matter what
4386 you do, the BSD compression code (used to compress the IP packets
4387 sent over the serial line; has to be supported at the other end as
4388 well) will always be compiled as a module; it is called bsd_comp.o
4389 and will show up in the directory modules once you have said "make
4390 modules". If unsure, say N.
4392 Wireless LAN (non-hamradio)
4394 Support for wireless LANs and everything having to do with radio,
4395 but not with amateur radio. Note that the answer to this question
4396 won't directly affect the kernel: saying N will just cause this
4397 configure script to skip all the questions about radio
4400 Some user-level drivers for scarab devices which don't require
4401 special kernel support are available via FTP (user: anonymous) from
4402 ftp://shadow.cabi.net/pub/Linux.
4404 STRIP (Metricom Starmode radio IP)
4406 Say Y if you have a Metricom radio and intend to use Starmode Radio
4407 IP. STRIP is a radio protocol developed for the MosquitoNet project
4408 (On the WWW at http://mosquitonet.stanford.edu/; to browse the WWW,
4409 you need to have access to a machine on the Internet that has a
4410 program like lynx or netscape) to send Internet traffic using
4411 Metricom radios. Metricom radios are small, battery powered,
4412 100kbit/sec packet radio transceivers, about the size and weight of
4413 a cellular telephone. (You may also have heard them called
4414 "Metricom modems" but we avoid the term "modem" because it misleads
4415 many people into thinking that you can plug a Metricom modem into a
4416 phone line and use it as a modem.)
4418 You can use STRIP on any Linux machine with a serial port, although
4419 it is obviously most useful for people with laptop computers. If you
4420 think you might get a Metricom radio in the future, there is no harm
4421 in saying Y to STRIP now, except that it makes the kernel a bit
4424 You can also compile this as a module ( = code which can be inserted
4425 in and removed from the running kernel whenever you want), say M
4426 here and read Documentation/modules.txt. The module will be called
4429 AT&T WaveLAN & DEC RoamAbout DS support
4431 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
4432 a Radio LAN (wireless Ethernet-like Local Area Network) using the
4433 radio frequencies 900 MHz and 2.4 GHz.
4435 This driver support the ISA version of the WaveLAN card. A separate
4436 driver for the pcmcia hardware is available in David Hinds'
4437 pcmcia-cs package (see the file Documentation/Changes for location).
4439 If you want to use an ISA WaveLAN card under Linux, say Y and read
4440 the Ethernet-HOWTO, available via FTP (user: anonymous) in
4441 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Some more specific
4442 information is contained in Documentation/networking/wavelan.txt and
4443 in the source code drivers/net/wavelan.p.h.
4445 You will also need the wireless tools package available from
4446 ftp://ftp.inka.de/pub/comp/Linux/networking/NetTools/contrib/.
4447 Please read the man pages contained therein.
4449 This driver is also available as a module ( = code which can be
4450 inserted in and removed from the running kernel whenever you want).
4451 The module will be called wavelan.o. If you want to compile it as a
4452 module, say M here and read Documentation/modules.txt as well as
4453 Documentation/networking/net-modules.txt.
4455 LAPB over Ethernet driver
4457 This is a driver for a pseudo device (typically called /dev/lapb0)
4458 which allows you to open an LAPB point-to-point connection to some
4459 other computer on your Ethernet network. In order to do this, you
4460 need to say Y or M to the driver for your Ethernet card as well as
4461 to "LAPB Data Link Driver".
4463 If you want to compile this driver as a module ( = code which can be
4464 inserted in and removed from the running kernel whenever you want),
4465 say M here and read Documentation/modules.txt. The module will be
4466 called lapbether.o. If unsure, say N.
4470 This is a driver for sending and receiving X.25 frames over regular
4471 asynchronous serial lines such as telephone lines equipped with
4472 ordinary modems. Experts should note that this driver doesn't
4473 currently comply with the asynchronous HDLS framing protocols in
4474 CCITT recommendation X.25.
4476 If you want to compile this driver as a module ( = code which can be
4477 inserted in and removed from the running kernel whenever you want),
4478 say M here and read Documentation/modules.txt. The module will be
4479 called x25_asy.o. If unsure, say N.
4481 Shortwave radio modem driver
4483 This experimental driver is used by a package (to be released)
4484 that implements the shortwave radio protocols RTTY, Sitor (Amtor),
4485 Pactor 1 and GTOR using a standard PC sound card. If unsure,
4488 Shortwave radio modem driver support for Sound Blaster and compatible cards
4490 This option enables the hfmodem driver to use Sound Blaster and
4491 compatible cards. It requires a 16bit capable card, i.e.
4492 SB16 or better, or ESS1688 or newer.
4494 Shortwave radio modem driver support for WSS and Crystal cards
4496 This option enables the hfmodem driver to use WindowsSoundSystem
4497 compatible cards. These cards feature a codec chip from either
4498 Analog Devices (such as AD1848, AD1845) or Crystal
4499 Semiconductors (such as CS4248, CS423x).
4501 PLIP (parallel port) support
4503 PLIP (Parallel Line Internet Protocol) is used to create a
4504 reasonably fast mini network consisting of two (or, rarely, more)
4505 local machines. A PLIP link from a Linux box is a popular means to
4506 install a Linux distribution on a machine which doesn't have a CDROM
4507 drive (a minimal system has to be transferred with floppies
4508 first). The kernels on both machines need to have this PLIP option
4509 enabled for this to work.
4511 The PLIP driver has two modes, mode 0 and mode 1. The parallel ports
4512 (the connectors at the computers with 25 holes) are connected with
4513 "null printer" or "Turbo Laplink" cables which can transmit 4 bits
4514 at a time (mode 0) or with special PLIP cables, to be used on
4515 bidirectional parallel ports only, which can transmit 8 bits at a
4516 time (mode 1); you can find the wiring of these cables in
4517 Documentation/networking/PLIP.txt. The cables can be up to 15m long.
4518 Mode 0 works also if one of the machines runs DOS/Windows and has
4519 some PLIP software installed, e.g. the Crynwr PLIP packet driver
4520 (http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html; to browse
4521 the WWW, you need to have access to a machine on the Internet that
4522 has a program like lynx or netscape) and winsock or NCSA's telnet.
4524 If you want to use PLIP, say Y and read the PLIP mini-HOWTO,
4525 available via FTP (user: anonymous) in
4526 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini as well as the
4527 NET-2-HOWTO in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that
4528 the PLIP protocol was changed and this PLIP driver won't work
4529 together with the PLIP support in Linux versions 1.0.x. This option
4530 enlarges your kernel by about 8kB.
4532 If you want to compile this as a module (= code which can be
4533 inserted in and removed from the running kernel whenever you want),
4534 say M here and read Documentation/modules.txt as well as
4535 Documentation/networking/net-modules.txt. The module will be called
4536 plip.o. If unsure, say Y or M, in case you buy a laptop later.
4538 EQL (serial line load balancing) support
4540 If you have two serial connections to some other computer (this
4541 usually requires two modems and two telephone lines) and you use
4542 SLIP (= the protocol for sending Internet traffic over telephone
4543 lines) or PPP (= a better SLIP) on them, you can make them behave
4544 like one double speed connection using this driver. Naturally, this
4545 has to be supported at the other end as well, either with a similar
4546 EQL Linux driver or with a Livingston Portmaster 2e. Say Y if you
4547 want this and read Documentation/networking/eql.txt.
4549 This driver is also available as a module ( = code which can be
4550 inserted in and removed from the running kernel whenever you want).
4551 The module will be called eql.o. If you want to compile it as a
4552 module, say M here and read Documentation/modules.txt. If unsure,
4555 Ethertap network tap
4557 If you say Y here (and have said Y to "Kernel/User network link
4558 driver", above) and create a character special file /dev/tap0 with
4559 major number 36 and minor number 16 using mknod ("man mknod"), you
4560 will be able to have a user space program read and write raw
4561 Ethernet frames from/to that special file. tap0 can be configured
4562 with ifconfig and route like any other Ethernet device but it is not
4563 connected to any physical LAN; everything written by the user to
4564 /dev/tap0 is treated by the kernel as if it had come in from a LAN
4565 to the device tap0; everything the kernel wants to send out over the
4566 device tap0 can instead be read by the user from /dev/tap0: the user
4567 mode program replaces the LAN that would be attached to an ordinary
4568 Ethernet device. Please read the file
4569 Documentation/networking/ethertap.txt for more information.
4571 This driver is also available as a module ( = code which can be
4572 inserted in and removed from the running kernel whenever you want).
4573 The module will be called ethertap.o. If you want to compile it as a
4574 module, say M here and read Documentation/modules.txt. If you don't
4575 know what to use this for, you don't need it.
4577 Frame Relay (DLCI) support
4579 This is support for the frame relay protocol; frame relay is a fast
4580 low-cost way to connect to a remote Internet access provider or to
4581 form a private wide area network. The one physical line from your
4582 box to the local "switch" (i.e. the entry point to the frame relay
4583 network, usually at the phone company) can carry several logical
4584 point-to-point connections to other computers connected to the frame
4585 relay network. For a general explanation of the protocol, check out
4586 http://www.frforum.com/ on the WWW. (To browse the WWW, you need to
4587 have access to a machine on the Internet that has a program like
4588 lynx or netscape.) To use frame relay, you need supporting hardware
4589 (called FRAD) and certain programs from the net-tools package as
4590 explained in Documentation/networking/framerelay.txt.
4592 This driver is also available as a module ( = code which can be
4593 inserted in and removed from the running kernel whenever you want).
4594 The module will be called dlci.o. If you want to compile it as a
4595 module, say M here and read Documentation/modules.txt.
4599 This is the maximal number of logical point-to-point frame relay
4600 connections (the identifiers of which are called DCLIs) that
4601 the driver can handle. The default is probably fine.
4605 You can specify here how many logical point-to-point frame relay
4606 connections (the identifiers of which are called DCLIs) should be
4607 handled by each of your hardware frame relay access devices. Go with
4610 Sangoma S502A FRAD support
4612 Say Y here if you need a driver for the Sangoma S502A, S502E, and
4613 S508 Frame Relay Access Devices. These are multi-protocol cards, but
4614 only frame relay is supported by the driver at this time. Please
4615 read Documentation/framerelay.txt.
4617 This driver is also available as a module ( = code which can be
4618 inserted in and removed from the running kernel whenever you want).
4619 The module will be called sdla.o. If you want to compile it as a
4620 module, say M here and read Documentation/modules.txt.
4622 Acorn Econet/AUN protocols (EXPERIMENTAL)
4624 Econet is a fairly old and slow networking protocol mainly used by
4625 Acorn computers to access file and print servers. It uses native
4626 Econet network cards. AUN is an implementation of the higher level
4627 parts of Econet that runs over ordinary Ethernet connections, on
4628 top of the UDP packet protocol, which in turn runs on top of the
4629 Internet protocol IP.
4631 If you say Y here, you can choose with the next two options whether
4632 to send Econet/AUN traffic over a UDP Ethernet connection or over
4633 a native Econet network card.
4635 This driver is also available as a module ( = code which can be
4636 inserted in and removed from the running kernel whenever you want).
4637 The module will be called econet.o. If you want to compile it as a
4638 module, say M here and read Documentation/modules.txt.
4641 CONFIG_ECONET_AUNUDP
4642 Say Y here if you want to send Econet/AUN traffic over a a UDP
4643 connection (UDP is a packet based protocol that runs on top of the
4644 Internet protocol IP) using an ordinary Ethernet network card.
4647 CONFIG_ECONET_NATIVE
4648 Say Y here if you have a native Econet network card installed in
4653 Wide Area Networks (WANs), such as X.25, frame relay and leased
4654 lines, are used to interconnect Local Area Networks (LANs) over vast
4655 distances with data transfer rates significantly higher than those
4656 achievable with commonly used asynchronous modem connections.
4657 Usually, a quite expensive external device called a `WAN router' is
4658 needed to connect to a WAN.
4660 As an alternative, WAN routing can be built into the Linux kernel.
4661 With relatively inexpensive WAN interface cards available on the
4662 market, a perfectly usable router can be built for less than half
4663 the price of an external router. If you have one of those cards and
4664 wish to use your Linux box as a WAN router, say Y here and to the
4665 WAN driver for your card, below. You will also need a wan-tools
4666 package available via FTP (user: anonymous) from
4667 ftp://ftp.sangoma.com. Read Documentation/networking/wan-router.txt
4668 for more information.
4670 WAN routing support is always built as a module ( = code which can
4671 be inserted in and removed from the running kernel whenever you
4672 want). The module is called wanrouter.o. For general information
4673 about modules read Documentation/modules.txt.
4675 Fast switching (read help!)
4676 CONFIG_NET_FASTROUTE
4677 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
4678 Card) data transfers, which is fast.
4680 *** This option is NOT COMPATIBLE with several important ***
4681 *** networking options: especially CONFIG*FIREWALL. ***
4683 However, it will work with all options in CONFIG_IP_ADVANCED_ROUTER
4684 section (except for CONFIG_IP_ROUTE_TOS). At the moment, few devices
4685 support fast switching (tulip is one of them, modified 8390 can be
4686 found at ftp://ftp.inr.ac.ru/ip-routing/fastroute-8390.tar.gz).
4690 Forwarding between high speed interfaces
4691 CONFIG_NET_HW_FLOWCONTROL
4692 This option enables NIC (Network Interface Card) hardware throttling
4693 during periods of extremal congestion. At the moment only a couple
4694 of device drivers support it (really only one -- tulip, modified
4695 8390 can be found at
4696 ftp://ftp.inr.ac.ru/ip-routing/fastroute-8390.tar.gz). Really, this
4697 option is applicable to any machine attached to a fast enough
4698 network, and even a 10Mb NIC is able to kill a not very slow box,
4699 such as a 120MHz Pentium.
4701 However, do not say Y here if you did not experience any serious
4704 CPU is too slow to handle full bandwidth
4706 If you suspect that your CPU is not fast enough to handle the
4707 full bandwidth of your network connection, try saying Y here. If
4710 QoS and/or fair queueing
4712 When the kernel has several packets to send out over the network
4713 devices, it has to make a decision which one to send first. This is
4714 especially important if some of the network devices are real time
4715 devices that need a certain minimum data flow rate. There are
4716 several different algorithms for how to do this "fairly"; they are
4717 called packet schedulers. You can attach different schedulers to
4718 different network devices. If you want to stick to the default
4719 scheduling algorithm, say N here. If you want to experiment with a
4720 couple of different algorithms, say Y. Currently, this is only
4721 recommended for experts.
4723 To administer these schedulers, you'll need the user-level utilities
4724 from the package iproute2+tc at ftp://ftp.inr.ac.ru/ip-routing/
4726 If you say Y here and to "/proc filesystem" below, you will be able
4727 to read status information about priority schedulers from
4728 the file /proc/net/psched.
4730 The available schedulers are listed in the following questions; you
4731 can say Y to as many as you like. If unsure, say N now.
4733 CBQ packet scheduler
4735 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
4736 scheduling algorithm for some of your network devices. This
4737 algorithm classifies the waiting packets into a tree-like hierarchy
4738 of classes; the leaves of this tree are in turn scheduled by
4739 separate algorithms (called "disciplines" in this context) which you
4740 can choose below from among the various queueing algorithms. See the
4741 top of net/sched/sch_cbq.c for references about the CBQ algorithm.
4743 This code is also available as a module called sch_cbq.o ( = code
4744 which can be inserted in and removed from the running kernel
4745 whenever you want). If you want to compile it as a module, say M
4746 here and read Documentation/modules.txt.
4748 CSZ packet scheduler
4750 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
4751 scheduling algorithm for some of your network devices. At the
4752 moment, this is the only algorithm that can guarantee service for
4753 real-time applications (see the top of net/sched/sch_csz.c for
4754 details and references about the algorithm).
4756 Note: this scheduler is currently broken.
4758 This code is also available as a module called sch_csz.o ( = code
4759 which can be inserted in and removed from the running kernel
4760 whenever you want). If you want to compile it as a module, say M
4761 here and read Documentation/modules.txt.
4763 The simplest PRIO pseudo scheduler
4765 Say Y here if you want to use an n-band priority queue packet
4766 "scheduler" for some of your network devices or as a leaf discipline
4767 for the CBQ scheduling algorithm.
4769 This code is also available as a module called sch_prio.o ( = code
4770 which can be inserted in and removed from the running kernel
4771 whenever you want). If you want to compile it as a module, say M
4772 here and read Documentation/modules.txt.
4776 Say Y here if you want to use the Random Early Detection (RED)
4777 packet scheduling algorithm for some of your network devices (see
4778 the top of net/sched/sch_red.c for details and references about the
4781 This code is also available as a module called sch_red.o ( = code
4782 which can be inserted in and removed from the running kernel
4783 whenever you want). If you want to compile it as a module, say M
4784 here and read Documentation/modules.txt.
4788 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
4789 packet scheduling algorithm for some of your network devices or as a
4790 leaf discipline for the CBQ scheduling algorithm (see the top of
4791 net/sched/sch_sfq.c for details and references about the SFQ
4794 This code is also available as a module called sch_sfq.o ( = code
4795 which can be inserted in and removed from the running kernel
4796 whenever you want). If you want to compile it as a module, say M
4797 here and read Documentation/modules.txt.
4801 Say Y here if you want to use the True Link Equalizer (TLE) packet
4802 scheduling algorithm for some of your network devices or as a leaf
4803 discipline for the CBQ scheduling algorithm. This queueing
4804 discipline allows the combination of several physical devices into
4805 one virtual device. (see the top of net/sched/sch_teql.c for
4808 This code is also available as a module called sch_teql.o ( = code
4809 which can be inserted in and removed from the running kernel
4810 whenever you want). If you want to compile it as a module, say M
4811 here and read Documentation/modules.txt.
4815 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
4816 packet scheduling algorithm for some of your network devices or as a
4817 leaf discipline for the CBQ scheduling algorithm (see the top of
4818 net/sched/sch_tbf.c for a description of the TBF algorithm).
4820 This code is also available as a module called sch_tbf.o ( = code
4821 which can be inserted in and removed from the running kernel
4822 whenever you want). If you want to compile it as a module, say M
4823 here and read Documentation/modules.txt.
4827 Say Y here if you want to include Quality Of Service scheduling
4828 features, which means that you will be able to request certain
4829 rate-of-flow limits for your net devices.
4831 Note that the answer to this question won't directly affect the
4832 kernel: saying N will just cause this configure script to skip all
4833 the questions about QoS support.
4836 CONFIG_NET_ESTIMATOR
4837 In order for Quality of Service scheduling to work, the current
4838 rate-of-flow for a network device has to be estimated; if you say Y
4839 here, the kernel will do just that.
4841 Packet classifier API
4843 The CBQ scheduling algorithm requires that network packets which are
4844 scheduled to be sent out over a network device be classified in some
4845 way. If you say Y here, you will get a choice of several different
4846 packet classifiers with the following questions.
4848 # Routing tables based classifier
4849 # CONFIG_NET_CLS_ROUTE
4851 # Firewall based classifier
4855 # CONFIG_NET_CLS_U32
4857 # Special RSVP classifier
4858 # CONFIG_NET_CLS_RSVP
4860 # Special RSVP classifier for IPv6
4861 # CONFIG_NET_CLS_RSVP6
4863 # Ingres traffic policing
4864 # CONFIG_NET_CLS_POLICE
4866 ### Some expert please fill these in
4869 Network code profiler
4871 If you say Y here and to "/proc filesystem support" below, some
4872 obscure and undocumented information about the network code's
4873 performance will be written to /proc/net/profile. If you don't know
4874 what it is about, you don't need it: say N.
4876 #Comtrol Hostess SV-11 support
4877 #CONFIG_HOSTESS_SV11
4879 ### I don't know what this is.
4884 Say Y to this option if your Linux box contains a WAN card and you
4885 are planning to use the box as a WAN ( = Wide Area Network) router
4886 ( = device used to interconnect local area networks over wide area
4887 communication links, such as leased lines and public data networks,
4888 e.g. X.25 and frame relay) and you will be offered a list of drivers
4889 for WAN cards currently available. For more information, read
4890 Documentation/networking/wan-router.txt. Note that the answer to
4891 this question won't directly affect the kernel: saying N will just
4892 cause this configure script to skip all the questions about WAN
4893 card drivers. If unsure, say N.
4895 Sangoma WANPIPE(tm) multiprotocol cards
4896 CONFIG_VENDOR_SANGOMA
4897 WANPIPE from Sangoma Technologies Inc. (http://www.sangoma.com; to
4898 browse the WWW, you need to have access to a machine on the Internet
4899 that has a program like lynx or netscape) is a family of intelligent
4900 multiprotocol WAN adapters with data transfer rates up to T1 (1.544
4901 Mbps). They are also known as Synchronous Data Link Adapters (SDLA)
4902 and designated S502E(A), S503 or S508. These cards support the X.25,
4903 Frame Relay, and PPP protocols. If you have one or more of these
4904 cards, say Y to this option and read
4905 Documentation/networking/wanpipe.txt. The next questions will ask
4906 you about the protocols you want the driver to support.
4908 The driver will be compiled as a module ( = code which can be
4909 inserted in and removed from the running kernel whenever you want).
4910 The module will be called wanpipe.o. For general information about
4911 modules read Documentation/modules.txt.
4913 Maximum number of cards
4914 CONFIG_WANPIPE_CARDS
4915 Enter number of WANPIPE adapters installed in your machine. The
4916 driver can support up to 8 cards. You may enter more than you
4917 actually have if you plan to add more cards in the future without
4918 re-compiling the driver, but remember that in this case you'll waste
4919 some kernel memory (about 1K per card).
4921 WANPIPE X.25 support
4923 Say Y to this option if you are planning to connect a WANPIPE card
4924 to an X.25 network. You should then also have said Y to "CCITT X.25
4925 Packet Layer" and "LAPB Data Link Driver", above. If you say N, the
4926 X.25 support will not be included in the driver (saves about 16K of
4929 WANPIPE Frame Relay support
4931 Say Y to this option if you are planning to connect a WANPIPE card
4932 to a frame relay network. You should then also have said Y to "Frame
4933 Relay (DLCI) support", above. If you say N, the frame relay
4934 support will not be included in the driver (saves about 16K of
4939 Say Y to this option if you are planning to connect a WANPIPE card
4940 to a leased line using Point-to-Point protocol (PPP). You should
4941 then also have said Y to "PPP (point-to-point) support", above. If
4942 you say N, the PPP support will not be included in the driver (saves
4943 about 16K of kernel memory).
4945 Ethernet (10 or 100Mbit)
4947 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
4948 type of Local Area Network (LAN) in universities and companies.
4950 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
4951 coaxial cable, linking computers in a chain), 10BASE-T or twisted
4952 pair (10 Mbps over twisted pair cable, linking computers to central
4953 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
4954 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
4955 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
4956 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
4957 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
4958 Ethernet (1 Gbps over optical fiber or short copper links).
4960 If your Linux machine will be connected to an Ethernet and you have
4961 an Ethernet network interface card (NIC) installed in your computer,
4962 say Y here and read the Ethernet-HOWTO, available via FTP (user:
4963 anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. You will
4964 then also have to say Y to the driver for your particular NIC.
4966 Note that the answer to this question won't directly affect the
4967 kernel: saying N will just cause this configure script to skip all
4968 the questions about Ethernet network cards. If unsure, say N.
4970 Sun LANCE Ethernet support
4972 This is support for lance Ethernet cards on Sun workstations such as
4973 the SPARCstation IPC (any SPARC with a network interface 'le0' under
4976 This driver is also available as a module ( = code which can be
4977 inserted in and removed from the running kernel whenever you want).
4978 The module will be called lance.o. If you want to compile it as a
4979 module, say M here and read Documentation/modules.txt.
4981 Sun Intel Ethernet support
4983 This is support for the Intel Ethernet cards on some Sun workstations
4984 (all those with a network interface 'ie0' under SunOS).
4986 Western Digital/SMC cards
4987 CONFIG_NET_VENDOR_SMC
4988 If you have a network (Ethernet) card belonging to this class, say Y
4989 and read the Ethernet-HOWTO, available via FTP (user: anonymous) in
4990 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
4992 Note that the answer to this question doesn't directly affect the
4993 kernel: saying N will just cause this configure script to skip all
4994 the questions about Western Digital cards. If you say Y, you will be
4995 asked for your specific card in the following questions.
4999 If you have a network (Ethernet) card of this type, say Y and read
5000 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5001 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5003 This driver is also available as a module ( = code which can be
5004 inserted in and removed from the running kernel whenever you want).
5005 The module will be called wd.o. If you want to compile it as a
5006 module, say M here and read Documentation/modules.txt as well as
5007 Documentation/networking/net-modules.txt.
5009 SMC Ultra MCA support
5011 If you have a network (Ethernet) card of this type and are running
5012 an MCA based system (PS/2), say Y and read
5013 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5014 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5016 This driver is also available as a module ( = code which can be
5017 inserted in and removed from the running kernel whenever you want).
5018 The module will be called smc-mca.o. If you want to compile it as a
5019 module, say M here and read Documentation/modules.txt as well as
5020 Documentation/networking/net-modules.txt.
5024 If you have a network (Ethernet) card of this type, say Y and read
5025 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5026 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5028 Important: There have been many reports that, with some motherboards
5029 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
5030 such as some BusLogic models) causes corruption problems with many
5031 operating systems. The Linux smc-ultra driver has a work-around for
5032 this but keep it in mind if you have such a SCSI card and have
5035 This driver is also available as a module ( = code which can be
5036 inserted in and removed from the running kernel whenever you want).
5037 The module will be called smc-ultra.o. If you want to compile it as
5038 a module, say M here and read Documentation/modules.txt as well as
5039 Documentation/networking/net-modules.txt.
5041 SMC Ultra32 EISA support
5043 If you have a network (Ethernet) card of this type, say Y and read
5044 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5045 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5047 This driver is also available as a module ( = code which can be
5048 inserted in and removed from the running kernel whenever you want).
5049 The module will be called smc-ultra32.o. If you want to compile it
5050 as a module, say M here and read Documentation/modules.txt as well
5051 as Documentation/networking/net-modules.txt.
5055 This is support for the SMC9xxx based Ethernet cards. Choose this
5056 option if you have a DELL laptop with the docking station, or
5057 another SMC9192/9194 based chipset. Say Y if you want it compiled
5058 into the kernel, and read the file
5059 Documentation/networking/smc9.txt and the Ethernet-HOWTO, available
5060 via FTP (user: anonymous) in
5061 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5063 This driver is also available as a module ( = code which can be
5064 inserted in and removed from the running kernel whenever you
5065 want). The module will be called smc9194.o. If you want to compile
5066 it as a module, say M here and read Documentation/modules.txt as
5067 well as Documentation/networking/net-modules.txt.
5071 This driver is for NE2000 compatible PCI cards. It will not work
5072 with ISA NE2000 cards. If you have a PCI NE2000 network (Ethernet)
5073 card, say Y and read the Ethernet-HOWTO, available via FTP (user:
5074 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5076 This driver is also available as a module ( = code which can be
5077 inserted in and removed from the running kernel whenever you want).
5078 The module will be called ne2k-pci.o. If you want to compile it as a
5079 module, say M here and read Documentation/modules.txt as well as
5080 Documentation/networking/net-modules.txt.
5082 Racal-Interlan (Micom) NI cards
5083 CONFIG_NET_VENDOR_RACAL
5084 If you have a network (Ethernet) card belonging to this class, such
5085 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
5086 available via FTP (user: anonymous) in
5087 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5089 Note that the answer to this question doesn't directly affect the
5090 kernel: saying N will just cause this configure script to skip all
5091 the questions about NI cards. If you say Y, you will be asked for
5092 your specific card in the following questions.
5096 If you have a network (Ethernet) card of this type, say Y and read
5097 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5098 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that this is still
5101 This driver is also available as a module ( = code which can be
5102 inserted in and removed from the running kernel whenever you want).
5103 The module will be called ni5010.o. If you want to compile it as a
5104 module, say M here and read Documentation/modules.txt as well as
5105 Documentation/networking/net-modules.txt.
5109 If you have a network (Ethernet) card of this type, say Y and read
5110 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5111 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5113 This driver is also available as a module ( = code which can be
5114 inserted in and removed from the running kernel whenever you want).
5115 The module will be called ni52.o. If you want to compile it as a
5116 module, say M here and read Documentation/modules.txt as well as
5117 Documentation/networking/net-modules.txt.
5121 If you have a network (Ethernet) card of this type, say Y and read
5122 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5123 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5125 This driver is also available as a module ( = code which can be
5126 inserted in and removed from the running kernel whenever you want).
5127 The module will be called ni65.o. If you want to compile it as a
5128 module, say M here and read Documentation/modules.txt as well as
5129 Documentation/networking/net-modules.txt.
5131 RealTek 8129/8139 (not 8019/8029!) support
5133 This is a driver for the Fast Ethernet PCI network cards based on
5134 the RTL8129 and RTL8139 chips. If you have one of those, say Y and
5135 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
5136 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5138 If you want to compile this driver as a module ( = code which can be
5139 inserted in and removed from the running kernel whenever you want),
5140 say M here and read Documentation/modules.txt. This is recommended.
5141 The module will be called rtl8139.o.
5143 Packet Engines Yellowfin Gigabit-NIC support
5145 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
5146 adapter. This adapter is used by the Beowulf Linux cluster project.
5147 See http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html for
5148 more information about this driver in particular and Beowulf in
5149 general (to browse the WWW, you need to have access to a machine on
5150 the Internet that has a program like lynx or netscape).
5152 If you want to compile this driver as a module ( = code which can be
5153 inserted in and removed from the running kernel whenever you want),
5154 say M here and read Documentation/modules.txt. This is recommended.
5155 The module will be called yellowfin.o.
5157 AMD LANCE and PCnet (AT1500 and NE2100) support
5159 If you have a network (Ethernet) card of this type, say Y and read
5160 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5161 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Some LinkSys cards are
5165 CONFIG_NET_VENDOR_3COM
5166 If you have a network (Ethernet) card belonging to this class, say Y
5167 and read the Ethernet-HOWTO, available via FTP (user: anonymous) in
5168 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5170 Note that the answer to this question doesn't directly affect the
5171 kernel: saying N will just cause this configure script to skip all
5172 the questions about 3COM cards. If you say Y, you will be asked for
5173 your specific card in the following questions.
5177 If you have a network (Ethernet) card of this type, say Y and read
5178 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5179 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Also, consider buying a
5180 new card, since the 3c501 is slow, broken, and obsolete: you will
5181 have problems. Some people suggest to ping ("man ping") a nearby
5182 machine every minute ("man cron") when using this card.
5184 This driver is also available as a module ( = code which can be
5185 inserted in and removed from the running kernel whenever you want).
5186 The module will be called 3c501.o. If you want to compile it as a
5187 module, say M here and read Documentation/modules.txt as well as
5188 Documentation/networking/net-modules.txt.
5192 If you have a network (Ethernet) card of this type, say Y and read
5193 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5194 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5196 This driver is also available as a module ( = code which can be
5197 inserted in and removed from the running kernel whenever you want).
5198 The module will be called 3c503.o. If you want to compile it as a
5199 module, say M here and read Documentation/modules.txt as well as
5200 Documentation/networking/net-modules.txt.
5204 Information about this network (Ethernet) card can be found in
5205 Documentation/networking/3c505.txt. If you have a card of this type,
5206 say Y and read the Ethernet-HOWTO, available via FTP (user:
5207 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5209 If you want to compile this as a module ( = code which can be
5210 inserted in and removed from the running kernel whenever you want),
5211 say M here and read Documentation/modules.txt as well as
5212 Documentation/networking/net-modules.txt. The module will be called
5217 If you have a network (Ethernet) card of this type, say Y and read
5218 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5219 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5221 This driver is also available as a module ( = code which can be
5222 inserted in and removed from the running kernel whenever you want).
5223 The module will be called 3c507.o. If you want to compile it as a
5224 module, say M here and read Documentation/modules.txt as well as
5225 Documentation/networking/net-modules.txt.
5229 If you have a network (Ethernet) card of this type, say Y and read
5230 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5231 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5233 This driver is also available as a module ( = code which can be
5234 inserted in and removed from the running kernel whenever you want).
5235 The module will be called 3c523.o. If you want to compile it as a
5236 module, say M here and read Documentation/modules.txt as well as
5237 Documentation/networking/net-modules.txt.
5241 If you have a network (Ethernet) card belonging to the 3Com
5242 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
5243 via FTP (user: anonymous) in
5244 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5246 If your card is not working you may need to use the DOS
5247 setup disk to disable Plug & Play mode, and to select the default
5250 If you want to compile this as a module ( = code which can be
5251 inserted in and removed from the running kernel whenever you want),
5252 say M here and read Documentation/modules.txt as well as
5253 Documentation/networking/net-modules.txt. The module will be called
5256 3c590 series (592/595/597) "Vortex" support
5258 If you have a 3Com "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597)
5259 or "Boomerang" series (EtherLink XL 3c900 or 3c905) network
5260 (Ethernet) card, say Y and read the Ethernet-HOWTO, available via FTP
5261 (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5262 More specific information is in Documentation/networking/vortex.txt
5263 and in the comments at the beginning of drivers/net/3c59x.c.
5265 If you want to compile this as a module ( = code which can be
5266 inserted in and removed from the running kernel whenever you want),
5267 say M here and read Documentation/modules.txt as well as
5268 Documentation/networking/net-modules.txt.
5272 If your network (Ethernet) card hasn't been mentioned yet and its
5273 bus system (that's the way the cards talks to the other components
5274 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
5275 Make sure you know the name of your card. Read the Ethernet-HOWTO,
5276 available via FTP (user: anonymous) in
5277 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. If unsure, say Y.
5279 Note that the answer to this question doesn't directly affect the
5280 kernel: saying N will just cause this configure script to skip all
5281 the remaining ISA network card questions. If you say Y, you will be
5282 asked for your specific card in the following questions.
5284 Generic ARCnet support
5286 If you have a network card of this type, say Y and check out the
5287 (arguably) beautiful poetry in Documentation/networking/arcnet.txt.
5289 You need both this driver, and the driver for the particular ARCnet
5290 chipset of your card. If you don't know, then it's probably a
5291 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset support"
5294 You might also want to have a look at the Ethernet-HOWTO, available
5295 via FTP (user: anonymous) in
5296 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO (even though ARCnet is
5297 not really Ethernet).
5299 This driver is also available as a module ( = code which can be
5300 inserted in and removed from the running kernel whenever you want).
5301 The module will be called arcnet.o. If you want to compile it as a
5302 module, say M here and read Documentation/modules.txt as well as
5303 Documentation/networking/net-modules.txt.
5305 Enable arc0e (ARCnet "ether-encap" packet format)
5307 This allows you to use "Ethernet encapsulation" with your ARCnet
5308 card via the virtual arc0e device. You only need arc0e if you want
5309 to talk to nonstandard ARCnet software, specifically,
5310 DOS/Windows-style "NDIS" drivers. You do not need to say Y here to
5311 communicate with industry-standard RFC1201 implementations, like the
5312 arcether.com packet driver or most DOS/Windows ODI drivers. RFC1201
5313 is included automatically as the arc0 device. Please read the
5314 ARCnet documentation in Documentation/networking/arcnet.txt for more
5315 information about using arc0e and arc0s.
5317 Enable arc0s (ARCnet RFC1051 packet format)
5319 This allows you to use RFC1051 with your ARCnet card via the virtual
5320 arc0s device. You only need arc0s if you want to talk to ARCnet
5321 software complying with the "old" standard, specifically, the DOS
5322 arcnet.com packet driver, Amigas running AmiTCP, and some variants
5323 of NetBSD. You do not need to say Y here to communicate with
5324 industry-standard RFC1201 implementations, like the arcether.com
5325 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
5326 automatically as the arc0 device. Please read the ARCnet
5327 documentation in Documentation/networking/arcnet.txt for more
5328 information about using arc0e and arc0s.
5330 ARCnet COM90xx (normal) chipset driver
5331 CONFIG_ARCNET_COM90xx
5332 This is the chipset driver for the standard COM90xx cards. If you
5333 have always used the old ARCnet driver without knowing what type of
5334 card you had, this is probably the one for you.
5336 This driver is also available as a module ( = code which can be
5337 inserted in and removed from the running kernel whenever you want).
5338 The module will be called com90xx.o. If you want to compile it as a
5339 module, say M here and read Documentation/modules.txt as well as
5340 Documentation/networking/net-modules.txt.
5342 ARCnet COM90xx (IO mapped) chipset driver
5343 CONFIG_ARCNET_COM90xxIO
5344 This is the chipset driver for the COM90xx cards, using them in
5345 IO-mapped mode instead of memory-mapped mode. This is slower than
5346 the normal driver. Only use it if your card doesn't support shared
5349 This driver is also available as a module ( = code which can be
5350 inserted in and removed from the running kernel whenever you want).
5351 The module will be called com90io.o. If you want to compile it as a
5352 module, say M here and read Documentation/modules.txt as well as
5353 Documentation/networking/net-modules.txt.
5355 ARCnet COM90xx (RIM I) chipset driver
5357 This is yet another chipset driver for the COM90xx cards, but this
5358 time only using memory-mapped mode, and no IO ports at all. This
5359 driver is completely untested, so if you have one of these cards,
5360 please mail David.Woodhouse@mvhi.com, especially if it works!
5362 This driver is also available as a module ( = code which can be
5363 inserted in and removed from the running kernel whenever you
5364 want). The module will be called arc-rimi.o. If you want to compile
5365 it as a module, say M here and read Documentation/modules.txt as
5366 well as Documentation/networking/net-modules.txt.
5368 ARCnet COM20020 chipset driver
5369 CONFIG_ARCNET_COM20020
5370 This is the driver for the new COM20020 chipset. It supports such
5371 things as promiscuous mode, so packet sniffing is possible, and
5372 extra diagnostic information.
5374 This driver is also available as a module ( = code which can be
5375 inserted in and removed from the running kernel whenever you want).
5376 The module will be called com20020.o. If you want to compile it as a
5377 module, say M here and read Documentation/modules.txt as well as
5378 Documentation/networking/net-modules.txt.
5380 Cabletron E21xx support
5382 If you have a network (Ethernet) card of this type, say Y and read
5383 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5384 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5386 This driver is also available as a module ( = code which can be
5387 inserted in and removed from the running kernel whenever you want).
5388 The module will be called e2100.o. If you want to compile it as a
5389 module, say M here and read Documentation/modules.txt as well as
5390 Documentation/networking/net-modules.txt.
5394 Support for CS89x0 chipset based Ethernet cards. If you have a
5395 network (Ethernet) card of this type, say Y and read the
5396 Ethernet-HOWTO, available via FTP (user: anonymous) in
5397 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO as well as
5398 Documentation/networking/cs89x0.txt.
5400 If you want to compile this as a module ( = code which can be
5401 inserted in and removed from the running kernel whenever you want),
5402 say M here and read Documentation/modules.txt as well as
5403 Documentation/networking/net-modules.txt. The module will be called
5408 If you have a network (Ethernet) card of this type, say Y and read
5409 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5410 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO as well as
5411 drivers/net/depca.c.
5413 If you want to compile this as a module ( = code which can be
5414 inserted in and removed from the running kernel whenever you want),
5415 say M here and read Documentation/modules.txt as well as
5416 Documentation/networking/net-modules.txt. The module will be called
5419 EtherWorks 3 support
5421 This driver supports the DE203, DE204 and DE205 network (Ethernet)
5422 cards. If this is for you, say Y and read
5423 Documentation/networking/ewrk3.txt in the kernel source as well as
5424 the Ethernet-HOWTO, available via FTP (user: anonymous) from
5425 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5427 If you want to compile this as a module ( = code which can be
5428 inserted in and removed from the running kernel whenever you want),
5429 say M here and read Documentation/modules.txt as well as
5430 Documentation/networking/net-modules.txt. The module will be called
5435 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
5436 is for you, read the Ethernet-HOWTO, available via FTP (user:
5437 anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5441 If you have a network (Ethernet) card of this type, say Y and read
5442 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5443 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5445 This driver is also available as a module ( = code which can be
5446 inserted in and removed from the running kernel whenever you want).
5447 If you want to compile it as a module, say M here and read
5448 Documentation/modules.txt as well as
5449 Documentation/networking/net-modules.txt. The module will be called
5452 FMV-181/182/183/184 support
5454 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
5455 say Y and read the Ethernet-HOWTO, available via FTP (user:
5456 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5458 If you use an FMV-183 or FMV-184 and it is not working, you may need
5459 to disable Plug & Play mode of the card.
5461 This driver is also available as a module ( = code which can be
5462 inserted in and removed from the running kernel whenever you want).
5463 The module will be called fmv18x.o. If you want to compile it as a
5464 module, say M here and read Documentation/modules.txt as well as
5465 Documentation/networking/net-modules.txt.
5467 EtherExpress PRO support
5469 If you have a network (Ethernet) card of this type, say Y. Note
5470 however that the EtherExpress PRO/100 Ethernet card has its own
5471 separate driver. Please read the Ethernet-HOWTO, available via FTP
5472 (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5474 This driver is also available as a module ( = code which can be
5475 inserted in and removed from the running kernel whenever you want).
5476 The module will be called eepro.o. If you want to compile it as a
5477 module, say M here and read Documentation/modules.txt as well as
5478 Documentation/networking/net-modules.txt.
5480 EtherExpress support
5482 If you have an EtherExpress16 network (Ethernet) card, say Y and
5483 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
5484 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that the Intel
5485 EtherExpress16 card used to be regarded as a very poor choice
5486 because the driver was very unreliable. We now have a new driver
5487 that should do better.
5489 If you want to compile this driver as a module ( = code which can be
5490 inserted in and removed from the running kernel whenever you want),
5491 say M here and read Documentation/modules.txt as well as
5492 Documentation/networking/net-modules.txt. The module will be called
5495 HP PCLAN+ (27247B and 27252A) support
5497 If you have a network (Ethernet) card of this type, say Y and read
5498 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5499 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5501 This driver is also available as a module ( = code which can be
5502 inserted in and removed from the running kernel whenever you want).
5503 The module will be called hp-plus.o. If you want to compile it as a
5504 module, say M here and read Documentation/modules.txt as well as
5505 Documentation/networking/net-modules.txt.
5507 HP PCLAN (27245 and other 27xxx series) support
5509 If you have a network (Ethernet) card of this type, say Y and read
5510 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5511 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5513 This driver is also available as a module ( = code which can be
5514 inserted in and removed from the running kernel whenever you want).
5515 The module will be called hp.o. If you want to compile it as a
5516 module, say M here and read Documentation/modules.txt as well as
5517 Documentation/networking/net-modules.txt.
5519 HP 10/100VG PCLAN (ISA, EISA, PCI) support
5521 If you have a network (Ethernet) card of this type, say Y and read
5522 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5523 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5525 If you want to compile this as a module ( = code which can be
5526 inserted in and removed from the running kernel whenever you want),
5527 say M here and read Documentation/modules.txt as well as
5528 Documentation/networking/net-modules.txt. The module will be called
5531 NE2000/NE1000 support
5533 If you have a network (Ethernet) card of this type, say Y and read
5534 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5535 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Many Ethernet cards
5536 without a specific driver are compatible with NE2000.
5538 This driver is also available as a module ( = code which can be
5539 inserted in and removed from the running kernel whenever you want).
5540 The module will be called ne.o. If you want to compile it as a
5541 module, say M here and read Documentation/modules.txt as well as
5542 Documentation/networking/net-modules.txt.
5546 If you have a network (Ethernet) card of this type, say Y and read
5547 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5548 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5550 EISA, VLB, PCI and on board controllers
5552 This is another class of network cards which attach directly to the
5553 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
5554 available via FTP (user: anonymous) from
5555 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5557 Note that the answer to this question doesn't directly affect the
5558 kernel: saying N will just cause this configure script to skip all
5559 the questions about this class of network cards. If you say Y, you
5560 will be asked for your specific card in the following questions. If
5561 you are unsure, say Y.
5563 AMD PCnet32 (VLB and PCI) support
5565 If you have a PCnet32 or PCnetPCI based network (Ethernet) card, say
5566 Y here and read the Ethernet-HOWTO, available via FTP (user:
5567 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5569 This driver is also available as a module ( = code which can be
5570 inserted in and removed from the running kernel whenever you want).
5571 The module will be called pcnet32.o. If you want to compile it as a
5572 module, say M here and read Documentation/modules.txt as well as
5573 Documentation/networking/net-modules.txt.
5575 Ansel Communications EISA 3200 support
5577 If you have a network (Ethernet) card of this type, say Y and read
5578 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5579 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5581 This driver is also available as a module ( = code which can be
5582 inserted in and removed from the running kernel whenever you want).
5583 The module will be called ac3200.o. If you want to compile it as a
5584 module, say M here and read Documentation/modules.txt as well as
5585 Documentation/networking/net-modules.txt.
5587 Racal-Interlan EISA ES3210 support
5589 If you have a network (Ethernet) card of this type, say Y and read
5590 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5591 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
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 es3210.o. If you want to compile it as a
5596 module, say M here and read Documentation/modules.txt as well as
5597 Documentation/networking/net-modules.txt.
5599 Mylex EISA LNE390A/LNE390B support
5601 If you have a network (Ethernet) card of this type, say Y and read
5602 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5603 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5605 This driver is also available as a module ( = code which can be
5606 inserted in and removed from the running kernel whenever you want).
5607 The module will be called lne390.o. If you want to compile it as a
5608 module, say M here and read Documentation/modules.txt as well as
5609 Documentation/networking/net-modules.txt.
5611 Novell/Eagle/Microdyne NE3210 EISA support
5613 If you have a network (Ethernet) card of this type, say Y and read
5614 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5615 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Note that this driver
5616 will NOT WORK for NE3200 cards as they are completely different.
5618 This driver is also available as a module ( = code which can be
5619 inserted in and removed from the running kernel whenever you want).
5620 The module will be called ne3210.o. If you want to compile it as a
5621 module, say M here and read Documentation/modules.txt as well as
5622 Documentation/networking/net-modules.txt.
5624 Apricot Xen-II on board Ethernet
5626 If you have a network (Ethernet) controller of this type, say Y and
5627 read the Ethernet-HOWTO, available via FTP (user: anonymous) in
5628 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5630 If you want to compile this as a module ( = code which can be
5631 inserted in and removed from the running kernel whenever you want),
5632 say M here and read Documentation/modules.txt as well as
5633 Documentation/networking/net-modules.txt. The module will be called
5636 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
5638 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
5639 These include the DE425, DE434, DE435, DE450 and DE500 models. If
5640 you have a network card of this type, say Y and read the
5641 Ethernet-HOWTO, available via FTP (user: anonymous) in
5642 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. More specific
5643 information is contained in Documentation/networking/de4x5.txt.
5645 This driver is also available as a module ( = code which can be
5646 inserted in and removed from the running kernel whenever you want).
5647 The module will be called de4x5.o. If you want to compile it as a
5648 module, say M here and read Documentation/modules.txt as well as
5649 Documentation/networking/net-modules.txt.
5651 DECchip Tulip (dc21x4x) PCI support
5653 This driver is developed for the SMC EtherPower series Ethernet
5654 cards and also works with cards based on the DECchip
5655 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
5656 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
5657 (smc9332dst), you can also try the driver for "Generic DECchip"
5658 cards, above. However, most people with a network card of this type
5659 will say Y here.) Do read the Ethernet-HOWTO, available via FTP
5660 (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5661 More specific information is contained in
5662 Documentation/networking/tulip.txt.
5664 This driver is also available as a module ( = code which can be
5665 inserted in and removed from the running kernel whenever you want).
5666 The module will be called tulip.o. If you want to compile it as a
5667 module, say M here and read Documentation/modules.txt as well as
5668 Documentation/networking/net-modules.txt.
5670 Digi Intl. RightSwitch support
5672 This is support for the Digi International RightSwitch series of
5673 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
5674 models. If you have a network card of this type, say Y and read the
5675 Ethernet-HOWTO, available via FTP (user: anonymous) in
5676 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. More specific
5677 information is contained in Documentation/networking/dgrs.txt.
5679 This driver is also available as a module ( = code which can be
5680 inserted in and removed from the running kernel whenever you want).
5681 The module will be called dgrs.o. If you want to compile it as a
5682 module, say M here and read Documentation/modules.txt as well as
5683 Documentation/networking/net-modules.txt.
5685 EtherExpress PRO/100 support
5686 CONFIG_EEXPRESS_PRO100
5687 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
5688 card, say Y and read the Ethernet-HOWTO, available via FTP (user:
5689 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5691 This driver is also available as a module ( = code which can be
5692 inserted in and removed from the running kernel whenever you want).
5693 The module will be called eepro100.o. If you want to compile it as a
5694 module, say M here and read Documentation/modules.txt as well as
5695 Documentation/networking/net-modules.txt.
5697 ICL EtherTeam 16i/32 support
5699 If you have a network (Ethernet) card of this type, say Y and read
5700 the Ethernet-HOWTO, available via FTP (user: anonymous) in
5701 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5703 This driver is also available as a module ( = code which can be
5704 inserted in and removed from the running kernel whenever you want).
5705 The module will be called eth16i.o. If you want to compile it as a
5706 module, say M here and read Documentation/modules.txt as well as
5707 Documentation/networking/net-modules.txt.
5709 TI ThunderLAN support (EXPERIMENTAL)
5711 If you have a PCI Ethernet network card based on the ThunderLAN chip
5712 which is supported by this driver, say Y and read the
5713 Ethernet-HOWTO, available via FTP (user: anonymous) in
5714 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5716 Devices currently supported by this driver are Compaq Netelligent,
5717 Compaq NetFlex and Olicom cards. Please read the file
5718 Documentation/networking/tlan.txt for more details.
5720 This driver is also available as a module ( = code which can be
5721 inserted in and removed from the running kernel whenever you want).
5722 The module will be called tlan.o. If you want to compile it as a
5723 module, say M here and read Documentation/modules.txt as well as
5724 Documentation/networking/net-modules.txt.
5726 Please email feedback to james.banks@caldera.com.
5728 SMC EtherPower II (EXPERIMENTAL)
5730 If you have an SMC EtherPower II 9432 PCI Ethernet network card
5731 which is based on the SMC83c170, say Y and read the Ethernet-HOWTO,
5732 available via FTP (user: anonymous) in
5733 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5735 This driver is also available as a module ( = code which can be
5736 inserted in and removed from the running kernel whenever you want).
5737 The module will be called epic100.o. If you want to compile it as a
5738 module, say M here and read Documentation/modules.txt as well as
5739 Documentation/networking/net-modules.txt.
5743 If you have a VIA "rhine" based network card (Rhine-I (3043) or
5744 Rhine-2 (VT86c100A)), say Y here. To build this driver as a module
5747 Zenith Z-Note support
5749 The Zenith Z-Note notebook computer has a built-in network
5750 (Ethernet) card, and this is the Linux driver for it. Note that the
5751 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
5752 by this driver. Read the Ethernet-HOWTO, available via FTP (user:
5753 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5755 Pocket and portable adapters
5757 Cute little network (Ethernet) devices which attach to the parallel
5758 port ("pocket adapters"), commonly used with laptops. If you have
5759 one of those, say Y and read the Ethernet-HOWTO, available via FTP
5760 (user: anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5762 If you want to plug a network card into the PCMCIA slot of your
5763 laptop instead (PCMCIA is the standard for credit card size
5764 extension cards used by all modern laptops), look on the FTP site
5765 (user: anonymous) ftp://cb-iris.stanford.edu/pub/pcmcia and say N
5768 Laptop users should read the Linux Laptop home page at
5769 http://www.cs.utexas.edu/users/kharker/linux-laptop/ (to browse the
5770 WWW, you need to have access to a machine on the Internet that has a
5771 program like lynx or netscape).
5773 Note that the answer to this question doesn't directly affect the
5774 kernel: saying N will just cause this configure script to skip all
5775 the questions about this class of network devices. If you say Y, you
5776 will be asked for your specific device in the following questions.
5778 AT-LAN-TEC/RealTek pocket adapter support
5780 This is a network (Ethernet) device which attaches to your parallel
5781 port. Read drivers/net/atp.c as well as the Ethernet-HOWTO,
5782 available via FTP (user: anonymous) from
5783 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
5784 If you intend to use this driver, you should have said N to the
5785 Parallel Printer support, because the two drivers don't like each
5788 D-Link DE600 pocket adapter support
5790 This is a network (Ethernet) device which attaches to your parallel
5791 port. Read Documentation/networking/DLINK.txt as well as the
5792 Ethernet-HOWTO, available via FTP (user: anonymous) from
5793 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
5794 It is possible to have several devices share a single parallel port
5795 and it is safe to compile the corresponding drivers into the kernel.
5797 If you want to compile this driver as a module however ( = code
5798 which can be inserted in and removed from the running kernel
5799 whenever you want), say M here and read Documentation/modules.txt.
5800 The module will be called de600.o.
5802 D-Link DE620 pocket adapter support
5804 This is a network (Ethernet) device which attaches to your parallel
5805 port. Read Documentation/networking/DLINK.txt as well as the
5806 Ethernet-HOWTO, available via FTP (user: anonymous) from
5807 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO if you want to use this.
5808 It is possible to have several devices share a single parallel port
5809 and it is safe to compile the corresponding drivers into the kernel.
5811 If you want to compile this driver as a module however ( = code
5812 which can be inserted in and removed from the running kernel
5813 whenever you want), say M here and read Documentation/modules.txt.
5814 The module will be called de620.o.
5816 Token Ring driver support
5818 Token Ring is IBM's way of communication on a local network; the
5819 rest of the world uses Ethernet. To participate on a Token Ring
5820 network, you need a special Token ring network card. If you are
5821 connected to such a Token Ring network and want to use your Token
5822 Ring card under Linux, say Y here and to the driver for your
5823 particular card below and read the Token-Ring mini-HOWTO, available
5824 via FTP (user:anonymous) from
5825 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. Most people can say N
5828 IBM Tropic chipset based adapter support
5830 This is support for all IBM Token Ring cards that don't use DMA. If
5831 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
5832 available via FTP (user:anonymous) from
5833 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5835 Warning: this driver will almost definitely fail if more than one
5836 active Token Ring card is present.
5838 This driver is also available as a module ( = code which can be
5839 inserted in and removed from the running kernel whenever you want).
5840 The module will be called ibmtr.o. If you want to compile it as a
5841 module, say M here and read Documentation/modules.txt.
5843 SysKonnect adapter support
5845 This is support for all SysKonnect Token Ring cards, specifically
5846 SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect TR4/16(+) PCI
5847 (SK-4590), SysKonnect TR4/16 PCI (SK-4591) adapters.
5849 If you have such an adapter and would like to use it, say Y or M and
5850 read the Token-Ring mini-HOWTO, available via FTP (user: anonymous)
5851 from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5853 Also read the file linux/Documentation/networking/sktr.txt or check
5854 the Linux-SNA WWW site for the latest information at
5855 http://samba.anu.edu.au/linux-sna/documents/drivers/SysKonnect/
5857 Traffic Shaper (EXPERIMENTAL)
5859 The traffic shaper is a virtual network device that allows you to
5860 limit the rate of outgoing data flow over some other network
5861 device. See Documentation/networking/shaper.txt for more
5862 information. To set up and configure shaper devices, you need the
5863 shapecfg program, available via FTP (user: anonymous) from
5864 ftp://shadow.cabi.net/pub/Linux in the shaper package.
5866 This driver is also available as a module ( = code which can be
5867 inserted in and removed from the running kernel whenever you want).
5868 The module will be called shaper.o. If you want to compile it as a
5869 module, say M here and read Documentation/modules.txt. If unsure,
5874 Fiber Distributed Data Interface is a high speed local area network
5875 design; essentially a replacement for high speed Ethernet. FDDI can
5876 run over copper or fiber. If you are connected to such a network and
5877 want a driver for the FDDI card in your computer, say Y here (and
5878 then also Y to the driver for your FDDI card, below). Most people
5881 Digital DEFEA and DEFPA adapter support
5883 This is support for the DIGITAL series of EISA (DEFEA) and PCI
5884 (DEFPA) controllers which can connect you to a local FDDI network.
5886 SGI Seeq ethernet controller support
5887 This is a driver for the Seeq based Ethernet adapters used in many
5888 Silicon Graphics machines.
5892 If you have an Acorn system with one of these (AKA25) network cards,
5893 you should say Y to this option if you wish to use it with Linux.
5895 Acorn/ANT Ether3 card
5897 If you have an Acorn system with one of these network cards, you
5898 should say Y to this option if you wish to use it with Linux.
5902 If you have an Acorn system with one of these network cards, you
5903 should say Y to this option if you wish to use it with Linux.
5905 EBSA-110 Ethernet interface
5907 If you wish to compile a kernel for the EBSA-110, then you should
5908 always answer Y to this.
5910 Support CDROM drives that are not SCSI or IDE/ATAPI
5911 CONFIG_CD_NO_IDESCSI
5912 If you have a CDROM drive that is neither SCSI nor IDE/ATAPI, say Y
5913 here, otherwise N. Read the CDROM-HOWTO, available via FTP (user:
5914 anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
5916 Note that the answer to this question doesn't directly affect the
5917 kernel: saying N will just cause this configure script to skip all
5918 the questions about these CDROM drives. If you are unsure what you
5919 have, say Y and find out whether you have one of the following
5922 For each of these drivers, a file Documentation/cdrom/<driver_name>
5923 exists. Especially in cases where you do not know exactly which kind
5924 of drive you have you should read there. Most of these drivers use a
5925 file drivers/cdrom/<driver_name>.h where you can define your
5926 interface parameters and switch some internal goodies.
5928 All these CDROM drivers are also usable as a module (= code which
5929 can be inserted in and removed from the running kernel whenever you
5930 want). If you want to compile them as module, say M instead of Y and
5931 read Documentation/modules.txt.
5933 If you want to use any of these CDROM drivers, you also have to say
5934 Y or M to "ISO 9660 CDROM filesystem support" below (this answer will
5935 get "defaulted" for you if you enable any of the Linux CDROM
5938 Sony CDU31A/CDU33A CDROM support
5940 These CDROM drives have a spring-pop-out caddyless drawer, and a
5941 rectangular green LED centered beneath it. NOTE: these CDROM drives
5942 will not be auto detected by the kernel at boot time; you have to
5943 provide the interface address as an option to the kernel at boot
5944 time as described in Documentation/cdrom/cdu31a or fill in your
5945 parameters into drivers/cdrom/cdu31a.c. Try "man bootparam" or
5946 see the documentation of your boot loader (lilo or loadlin) about
5947 how to pass options to the kernel. The lilo procedure is also
5948 explained in the SCSI-HOWTO.
5950 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
5951 filesystem support" below, because that's the filesystem used on
5954 This driver is also available as a module ( = code which can be
5955 inserted in and removed from the running kernel whenever you want).
5956 The module will be called cdu31a.o. If you want to compile it as a
5957 module, say M here and read Documentation/modules.txt.
5959 Standard Mitsumi [no XA/Multisession] CDROM support
5961 This is the older of the two drivers for the older Mitsumi models
5962 LU-005, FX-001 and FX-001D. This is not the right driver for the
5963 FX-001DE and the triple or quad speed models (all these are
5964 IDE/ATAPI models). Please also the file Documentation/cdrom/mcd.
5966 With the old LU-005 model, the whole drive chassis slides out for cd
5967 insertion. The FX-xxx models use a motorized tray type mechanism.
5968 Note that this driver does not support XA or MultiSession CDs
5969 (PhotoCDs). There is a new driver (next question) which can do
5970 this. If you want that one, say N here.
5972 If the driver doesn't work out of the box, you might want to have a
5973 look at drivers/cdrom/mcd.h.
5975 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
5976 filesystem support" below, because that's the filesystem used on
5979 This driver is also available as a module ( = code which can be
5980 inserted in and removed from the running kernel whenever you want).
5981 The module will be called mcd.o. If you want to compile it as a
5982 module, say M here and read Documentation/modules.txt.
5984 Mitsumi [XA/MultiSession] support
5986 Use this driver if you want to be able to read XA or MultiSession
5987 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
5988 FX-001 or FX-001D CDROM drive. In addition, this driver uses much less
5989 kernel memory than the old one, if that is a concern. This driver is
5990 able to support more than one drive, but each drive needs a separate
5991 interface card. Please read the file Documentation/cdrom/mcdx.
5993 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
5994 filesystem support" below, because that's the filesystem used on
5997 This driver is also available as a module ( = code which can be
5998 inserted in and removed from the running kernel whenever you want).
5999 The module will be called mcdx.o. If you want to compile it as a
6000 module, say M here and read Documentation/modules.txt.
6002 Matsushita/Panasonic/Creative, Longshine, TEAC CDROM support
6004 This driver supports most of the drives which use the Panasonic or
6005 Sound Blaster interface. Please read the file
6006 Documentation/cdrom/sbpcd.
6008 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
6009 (sometimes labeled "Creative"), the Creative Labs CD200, the
6010 Longshine LCS-7260, the "IBM External ISA CDROM" (in fact a CR-56x
6011 model), the TEAC CD-55A fall under this category. Some other
6012 "electrically compatible" drives (Vertos, Genoa, some Funai models)
6013 are currently not supported; for the Sanyo H94A drive currently a
6014 separate driver (asked later) is responsible. Most drives have a
6015 uniquely shaped faceplate, with a caddyless motorized drawer, but
6016 without external brand markings. The older CR-52x drives have a
6017 caddy and manual loading/eject, but still no external markings. The
6018 driver is able to do an extended auto-probing for interface
6019 addresses and drive types; this can help to find facts in cases you
6020 are not sure, but can consume some time during the boot process if
6021 none of the supported drives gets found. Once your drive got found,
6022 you should enter the reported parameters into drivers/cdrom/sbpcd.h
6023 and set "DISTRIBUTION 0" there.
6025 This driver can support up to four CDROM controller cards, and each
6026 card can support up to four CDROM drives; if you say Y here, you
6027 will be asked how many controller cards you have. If compiled as a
6028 module, only one controller card (but with up to four drives) is
6031 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
6032 filesystem support" below, because that's the filesystem used on
6035 This driver is also available as a module ( = code which can be
6036 inserted in and removed from the running kernel whenever you want).
6037 The module will be called sbpcd.o. If you want to compile it as a
6038 module, say M here and read Documentation/modules.txt.
6040 Matsushita/Panasonic, ... second CDROM controller support
6042 Say Y here only if you have two CDROM controller cards of this type
6043 (usually only if you have more than four drives). You should enter
6044 the parameters for the second, third and fourth interface card into
6045 linux/include/linux/sbpcd.h before compiling the new kernel. Read
6046 the file Documentation/cdrom/sbpcd.
6048 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CDROM support
6050 This is your driver if you have an Aztech CDA268-01A, Orchid
6051 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCDROM CR520 or
6052 CR540 CDROM drive. This driver -- just like all these CDROM drivers
6053 -- is NOT for CDROM drives with IDE/ATAPI interfaces, such as Aztech
6054 CDA269-031SE. Please read the file Documentation/cdrom/aztcd.
6056 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
6057 filesystem support" below, because that's the filesystem used on
6060 This driver is also available as a module ( = code which can be
6061 inserted in and removed from the running kernel whenever you want).
6062 The module will be called aztcd.o. If you want to compile it as a
6063 module, say M here and read Documentation/modules.txt.
6065 Sony CDU535 CDROM support
6067 This is the driver for the older Sony CDU-535 and CDU-531 CDROM
6068 drives. Please read the file Documentation/cdrom/sonycd535.
6070 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
6071 filesystem support" below, because that's the filesystem used on
6074 This driver is also available as a module ( = code which can be
6075 inserted in and removed from the running kernel whenever you want).
6076 The module will be called sonycd535.o. If you want to compile it as
6077 a module, say M here and read Documentation/modules.txt.
6079 Goldstar R420 CDROM support
6081 If this is your CDROM drive, say Y here. As described in
6082 linux/Documentation/cdrom/gscd, you might have to change a setting
6083 in the file linux/drivers/cdrom/gscd.h before compiling the
6084 kernel. Please read the file Documentation/cdrom/gscd.
6086 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
6087 filesystem support" below, because that's the filesystem used on
6090 This driver is also available as a module ( = code which can be
6091 inserted in and removed from the running kernel whenever you want).
6092 The module will be called gscd.o. If you want to compile it as a
6093 module, say M here and read Documentation/modules.txt.
6095 Philips/LMS CM206 CDROM support
6097 If you have a Philips/LMS CDROM drive cm206 in combination with a
6098 cm260 host adapter card, say Y here. Please also read the file
6099 Documentation/cdrom/cm206.
6101 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
6102 filesystem support" below, because that's the filesystem used on
6105 This driver is also available as a module ( = code which can be
6106 inserted in and removed from the running kernel whenever you want).
6107 The module will be called cm206.o. If you want to compile it as a
6108 module, say M here and read Documentation/modules.txt.
6110 Optics Storage DOLPHIN 8000AT CDROM support
6112 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
6113 compatible interface. It also works with the Lasermate CR328A. If
6114 you have one of those, say Y. This driver does not work for the
6115 Optics Storage 8001 drive; use the IDE-ATAPI CDROM driver for that
6116 one. Please read the file Documentation/cdrom/optcd.
6118 If you say Y here, you should also say Y or M to "ISO 9660 CDROM
6119 filesystem support" below, because that's the filesystem used on
6122 This driver is also available as a module ( = code which can be
6123 inserted in and removed from the running kernel whenever you want).
6124 The module will be called optcd.o. If you want to compile it as a
6125 module, say M here and read Documentation/modules.txt.
6127 Sanyo CDR-H94A CDROM support
6129 If this is your CDROM drive, say Y here and read the file
6130 Documentation/cdrom/sjcd. You should then also say Y or M to
6131 "ISO 9660 CDROM filesystem support" below, because that's the
6132 filesystem used on CDROMs.
6134 This driver is also available as a module ( = code which can be
6135 inserted in and removed from the running kernel whenever you want).
6136 The module will be called sjcd.o. If you want to compile it as a
6137 module, say M here and read Documentation/modules.txt.
6139 Soft configurable cdrom interface card support
6141 If you want to include boot-time initialization of any cdrom
6142 interface card that is software configurable, say Y here. Currently
6143 only the ISP16/MAD16/Mozart sound cards with built-in cdrom
6144 interfaces are supported.
6146 Note that the answer to this question doesn't directly affect the
6147 kernel: saying N will just cause this configure script to skip all
6148 the questions about these CDROM drives.
6150 ISP16/MAD16/Mozart soft configurable cdrom interface support
6152 These are sound cards with with built-in cdrom interfaces using the
6153 OPTi 82C928 or 82C929 chips. Say Y here to have them detected and
6154 possibly configured at boot time. In addition, You'll have to say Y
6155 to a driver for the particular cdrom drive you have attached to the
6156 card. Read Documentation/cdrom/isp16 for details.
6158 This driver is also available as a module ( = code which can be
6159 inserted in and removed from the running kernel whenever you want).
6160 The module will be called isp16.o. If you want to compile it as a
6161 module, say M here and read Documentation/modules.txt.
6165 If you say Y here, you will be able to set per user limits for disk
6166 usage (also called disk quotas). Currently, it works only for the
6167 ext2 filesystem. You need additional software in order to use quota
6168 support; for details, read the Quota mini-HOWTO, available via FTP
6169 (user: anonymous) in
6170 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini. Probably the quota
6171 support is only useful for multi user systems. If unsure, say N.
6175 Minix is a simple operating system used in many classes about
6176 OS's. The minix filesystem (= method to organize files on a hard disk
6177 partition or a floppy disk) was the original filesystem for Linux,
6178 has been superseded by the second extended filesystem ext2fs but is
6179 still used for root/boot and other floppies or ram disks since it is
6180 leaner. You don't want to use it on your hard disk because of certain
6181 built-in restrictions. This option will enlarge your kernel by about
6182 25 kB. Everyone should say Y or M so that they are able to read this
6183 common floppy format.
6185 If you want to compile this as a module ( = code which can be
6186 inserted in and removed from the running kernel whenever you want),
6187 say M here and read Documentation/modules.txt. The module will be
6188 called minix.o. Note that the filesystem of your root partition
6189 cannot be compiled as a module.
6191 Second extended fs support
6193 This is the de facto standard Linux filesystem (= method to organize
6194 files on a storage device) for hard disks.
6196 You want to say Y here, unless you intend to use Linux exclusively
6197 from inside a DOS partition using the umsdos filesystem. The
6198 advantage of the latter is that you can get away without
6199 repartitioning your hard drive (which often implies backing
6200 everything up and restoring afterwards); the disadvantage is that
6201 Linux becomes susceptible to DOS viruses and that umsdos is somewhat
6202 slower than ext2fs. Even if you want to run Linux in this fashion,
6203 it might be a good idea to have ext2fs around: it enables you to
6204 read more floppy disks and facilitates the transition to a *real*
6205 Linux partition later. Another (rare) case which doesn't require
6206 ext2fs is a diskless Linux box which mounts all files over the
6207 network using NFS (in this case it's sufficient to say Y to "NFS
6208 filesystem support" below). Saying Y here will enlarge your kernel
6211 The Ext2fs-Undeletion mini-HOWTO, available via FTP (user:
6212 anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini,
6213 gives information about how to retrieve deleted files on ext2fs
6216 To change the behavior of ext2 filesystems, you can use the tune2fs
6217 utility ("man tune2fs"). To modify attributes of files and
6218 directories on ext2 filesystems, use chattr ("man chattr").
6220 Ext2fs partitions can be read from within DOS using the ext2tool
6221 package (available via FTP (user: anonymous) from
6222 ftp://sunsite.unc.edu/pub/Linux/system/filesystems/ext2) and from
6223 within Windows 95 and Windows NT using the ex2fs explorer available
6224 from http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm.
6226 If you want to compile this filesystem as a module ( = code which
6227 can be inserted in and removed from the running kernel whenever you
6228 want), say M here and read Documentation/modules.txt. The module
6229 will be called ext2.o. Be aware however that the filesystem of your
6230 root partition cannot be compiled as a module, and so this could be
6231 dangerous. Most everyone wants to say Y here.
6233 ISO 9660 CDROM filesystem support
6235 This is the standard filesystem used on CDROMs. It was previously
6236 known as "High Sierra Filesystem" and is called "hsfs" on other Unix
6237 systems. The so-called Rock-Ridge extensions which allow for long
6238 Unix filenames and symbolic links are also supported by this driver.
6239 If you have a CDROM drive and want to do more with it than just
6240 listen to audio CDs and watch its LEDs, say Y (and read
6241 Documentation/filesystems/isofs.txt and the CDROM-HOWTO, available
6242 via FTP (user: anonymous) from
6243 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO), thereby enlarging your
6244 kernel by about 27 kB; otherwise say N.
6246 If you want to compile this as a module ( = code which can be
6247 inserted in and removed from the running kernel whenever you want),
6248 say M here and read Documentation/modules.txt. The module will be
6251 Microsoft Joliet cdrom extensions
6253 Joliet is a Microsoft extension for the ISO 9660 CDROM filesystem
6254 which allows for long filenames in unicode format (unicode is the
6255 new 16 bit character code, successor to ASCII, which encodes the
6256 characters of almost all languages of the world; see
6257 http://www.unicode.org for more information; to browse the WWW, you
6258 need to have access to a machine on the Internet that has a program
6259 like lynx or netscape). Say Y here if you want to be able to read
6260 Joliet CDROMs under Linux.
6264 If you want to use one of the FAT-based filesystems (the MS-DOS,
6265 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
6266 ordinary DOS partition) filesystems), then you must include FAT
6267 support. This is not a filesystem in itself, but it provides the
6268 foundation for the other filesystems. It is now also becoming
6269 possible to read and write compressed FAT filesystems; read
6270 Documentation/filesystems/fat_cvf.txt for details. This option will
6271 enlarge your kernel by about 24 kB. If unsure, say Y.
6273 If you want to compile this as a module however ( = code which can
6274 be inserted in and removed from the running kernel whenever you
6275 want), say M here and read Documentation/modules.txt. The module
6276 will be called fat.o. Note that if you compile the FAT support as a
6277 module, you cannot compile any of the FAT-based filesystems into the
6278 kernel -- they will have to be modules as well. The filesystem of
6279 your root partition cannot be a module, so don't say M here if you
6280 intend to use UMSDOS as your root filesystem.
6284 This allows you to mount MSDOS partitions of your hard drive (unless
6285 they are compressed; to access compressed MSDOS partitions under
6286 Linux, you can either use the DOS emulator DOSEMU, described in the
6287 DOSEMU-HOWTO, available via FTP (user: anonymous) at
6288 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO, or try dmsdosfs in
6289 ftp://sunsite.unc.edu/pub/Linux/system/filesystems/dosfs. If you
6290 intend to use dosemu with a non-compressed MSDOS partition, say Y
6291 here) and MSDOS floppies. This means that file access becomes
6292 transparent, i.e. the MSDOS files look and behave just like all
6295 Another way to read and write MSDOS floppies from within Linux (but
6296 not transparently) is with the mtools ("man mtools") program suite,
6297 which doesn't require the msdos filesystem support.
6299 If you want to use umsdos, the Unix-like filesystem on top of DOS,
6300 which allows you to run Linux from within a DOS partition without
6301 repartitioning, you'll have to say Y or M here. If you have Windows
6302 95 or Windows NT installed on your MSDOS partitions, you should use
6303 the VFAT filesystem instead, or you will not be able to see the long
6304 filenames generated by Windows 95 / Windows NT.
6306 This option will enlarge your kernel by about 7 kB. If unsure, say
6307 Y. This will only work if you said Y to "fat fs support" as well. If
6308 you want to compile this as a module however ( = code which can be
6309 inserted in and removed from the running kernel whenever you want),
6310 say M here and read Documentation/modules.txt. The module will be
6315 This allows you to mount MSDOS partitions of your hard drive. It
6316 will let you use filenames in a way compatible with the long
6317 filenames used by Windows 95 and Windows NT fat-based (not NTFS)
6318 partitions. It does not support Windows 95 compressed filesystems.
6319 You cannot use the VFAT filesystem for your root partition; use
6320 UMSDOS instead. This option enlarges your kernel by about 10 kB and
6321 it only works if you said Y to the "fat fs support" above. Please read
6322 the file Documentation/filesystems/vfat.txt for details.
6325 If you want to compile this as a module ( = code which can be
6326 inserted in and removed from the running kernel whenever you want),
6327 say M here and read Documentation/modules.txt. The module will be
6330 umsdos: Unix like fs on top of std MSDOS fs
6332 Say Y here if you want to run Linux from within an existing DOS
6333 partition of your hard drive. The advantage of this is that you can
6334 get away without repartitioning your hard drive (which often implies
6335 backing everything up and restoring afterwards) and hence you're
6336 able to quickly try out Linux or show it to your friends; the
6337 disadvantage is that Linux becomes susceptible to DOS viruses and
6338 that UMSDOS is somewhat slower than ext2fs. Another use of umsdos
6339 is to write files with long unix filenames to MSDOS floppies; it
6340 also allows Unix-style softlinks and owner/permissions of files on
6341 MSDOS floppies. You will need a program called umssync in order to
6342 make use of umsdos; read Documentation/filesystems/umsdos.txt.
6344 This option enlarges your kernel by about 25 kB and it only works if
6345 you said Y to both "fat fs support" and "msdos fs support" above. If
6346 you want to compile this as a module ( = code which can be inserted
6347 in and removed from the running kernel whenever you want), say M
6348 here and read Documentation/modules.txt. The module will be called
6349 umsdos.o. Note that the filesystem of your root partition cannot be
6350 a module, so this could be dangerous. If unsure, say N.
6352 /proc filesystem support
6354 This is a virtual filesystem providing information about the status
6355 of the system. "Virtual" means that it doesn't take up any space on
6356 your hard disk: the files are created on the fly by the kernel when
6357 you try to access them. Also, you cannot read the files with older
6358 version of the program less: you need to use more or cat. The
6359 filesystem is explained in the Kernel Hacker's Guide at
6360 http://www.redhat.com:8080/HyperNews/get/khg.html on the WWW (to
6361 browse the WWW, you need to have access to a machine on the Internet
6362 that has a program like lynx or netscape), and also on the proc(8)
6363 manpage ("man 8 proc").
6365 It's totally cool; for example, "cat /proc/interrupts" gives
6366 information about what the different IRQs are used for at the moment
6367 (there is a small number of Interrupt ReQuest lines in your computer
6368 that are used by the attached devices to gain the CPU's attention --
6369 often a source of trouble if two devices are mistakenly configured
6370 to use the same IRQ). This option will enlarge your kernel by about
6371 18 kB. Several programs depend on this, so everyone should say Y
6374 NFS filesystem support
6376 If you are connected to some other (usually local) Unix computer
6377 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
6378 on that computer (the NFS server) using the Network File Sharing
6379 protocol, say Y. "Mounting files" means that the client can access
6380 the files with usual UNIX commands as if they were sitting on the
6381 client's hard disk. For this to work, the server must run the
6382 programs nfsd and mountd (but does not need to have NFS filesystem
6383 support enabled in its kernel). NFS is explained in the Network
6384 Administrator's Guide, available via FTP (user: anonymous) in
6385 ftp://sunsite.unc.edu/pub/Linux/docs/LDP, on its man page: "man
6386 nfs", and in the NFS-HOWTO.
6388 An superior but less widely used alternative to NFS is provided by
6389 the Coda filesystem; see "Coda filesystem support" below.
6391 If you say Y here, you should have said Y to TCP/IP networking also.
6392 This option would enlarge your kernel by about 27 kB.
6394 This filesystem is also available as a module ( = code which can be
6395 inserted in and removed from the running kernel whenever you want).
6396 The module is called nfs.o. If you want to compile it as a module,
6397 say M here and read Documentation/modules.txt.
6399 If you are configuring a diskless machine which will mount its root
6400 filesystem over NFS at boot time, say Y here and to "Root file
6401 system on NFS" and to "IP: kernel level autoconfiguration". You
6402 cannot compile this driver as a module in this case. There are two
6403 packages designed for booting diskless machines over the net:
6404 netboot and etherboot, both available via FTP (user: anonymous) from
6405 ftp://sunsite.unc.edu/pub/Linux/system/boot/ethernet/ .
6407 If you don't know what all this is about, say N.
6409 Root file system on NFS
6411 If you want your Linux box to mount its whole root filesystem from
6412 some other computer over the net via NFS (presumably because your
6413 box doesn't have a hard disk), say Y. Read Documentation/nfsroot.txt
6414 for details. It is likely that in this case, you also want to say Y
6415 to "IP: kernel level autoconfiguration" so that your box can
6416 discover its network address at boot time.
6418 Most people say N here.
6422 If you want your Linux box to act as a NFS *server*, so that other
6423 computers on your local network which support NFS can access certain
6424 directories on your box transparently, you have two options: you can
6425 use the self-contained user space program nfsd, in which case you
6426 should say N here, or you can say Y and use this new experimental
6427 kernel based NFS server. The advantage of the kernel based solution
6428 is that it is faster; it might not be completely stable yet, though.
6429 You will need the support software from the linux-nfs package
6430 available at ftp://ftp.mathematik.th-darmstadt.de/pub/linux/okir/.
6431 Please read the NFS-HOWTO, available via FTP (user: anonymous) from
6432 sunsite.unc.edu:/pub/Linux/docs/HOWTO.
6434 The NFS server is also available as a module ( = code which can be
6435 inserted in and removed from the running kernel whenever you want).
6436 The module is called nfsd.o. If you want to compile it as a module,
6437 say M here and read Documentation/modules.txt. If unsure, say N.
6439 Emulate Sun NFS daemon
6441 If you would like for the server to allow clients to access
6442 directories that are mountpoints on the local filesystem (this is
6443 how nfsd behaves on Sun systems), say yes here. If unsure, say N.
6445 OS/2 HPFS filesystem support (read only)
6447 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
6448 is the filesystem used for organizing files on OS/2 hard disk
6449 partitions. Say Y if you want to be able to read files from an OS/2
6450 HPFS partition of your hard drive. OS/2 floppies however are in
6451 regular MSDOS format, so you don't need this option in order to be
6452 able to read them. Read Documentation/filesystems/hpfs.txt.
6454 This filesystem is also available as a module ( = code which can be
6455 inserted in and removed from the running kernel whenever you want).
6456 The module is called hpfs.o. If you want to compile it as a module,
6457 say M here and read Documentation/modules.txt. If unsure, say N.
6459 Windows NT NTFS support (read only)
6461 NTFS is the file system of Microsoft Windows NT. Say Y if you want
6462 to get read access to files on NTFS partitions of your hard drive.
6463 The Linux NTFS driver supports most of the mount options of the VFAT
6464 driver, see Documentation/filesystems/ntfs.txt. Saying Y here will
6465 give you read-only access to NTFS partitions.
6467 This code is also available as a module ( = code which can be
6468 inserted in and removed from the running kernel whenever you want).
6469 The module will be called ntfs.o. If you want to compile it as a
6470 module, say M here and read Documentation/modules.txt.
6472 NTFS read-write support (experimental)
6474 If you say Y here, you will (hopefully) be able to write to NTFS
6475 file systems as well as read from them. The read-write support
6476 in NTFS is far from being complete and is not well tested. If you
6477 enable this, back up your NTFS volume first since it may get
6482 System V and Coherent filesystem support
6484 SCO, Xenix and Coherent are commercial Unix systems for Intel
6485 machines. Saying Y here would allow you to read and write to and
6486 from their floppies and hard disk partitions.
6488 If you have a floppy or hard disk partition like that, it is likely
6489 that they contain binaries from those other Unix systems; in order
6490 to run these binaries, you will want to install iBCS2 (iBCS2 [Intel
6491 Binary Compatibility Standard] is a kernel module which lets you run
6492 SCO, Xenix, Wyse, UnixWare, Dell Unix and System V programs under
6493 Linux and is often needed to run commercial software that's only
6494 available for those systems. It's available via FTP (user:
6495 anonymous) from ftp://tsx-11.mit.edu/pub/linux/BETA).
6497 If you only intend to mount files from some other Unix over the
6498 network using NFS, you don't need the System V filesystem support
6499 (but you need NFS filesystem support obviously). Note that this
6500 option is generally not needed for floppies, since a good portable
6501 way to transport files and directories between unixes (and even
6502 other operating systems) is given by the tar program ("man tar" or
6503 preferably "info tar"). Note also that this option has nothing
6504 whatsoever to do with the option "System V IPC". Read about the
6505 System V filesystem in Documentation/filesystems/sysv-fs.txt. This
6506 option will enlarge your kernel by about 34 kB.
6508 If you want to compile this as a module ( = code which can be
6509 inserted in and removed from the running kernel whenever you want),
6510 say M here and read Documentation/modules.txt. The module will be
6511 called sysv.o. If you haven't heard about all of this before, it's
6514 Amiga FFS filesystem support
6516 The Fast File System (FFS) is the common filesystem used on hard
6517 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
6518 if you want to be able to read and write files from and to an Amiga
6519 FFS partition on your hard drive. Amiga floppies however cannot be
6520 read with this driver due to an incompatibility of the floppy
6521 controller used in an Amiga and the standard floppy controller in
6522 PCs and workstations. Read Documentation/filesystems/affs.txt and
6525 With this driver you can also mount disk files used by Bernd
6526 Schmidt's Un*X Amiga Emulator (http://www.freiburg.linux.de/~uae/;
6527 to browse the WWW, you need to have access to a machine on the
6528 Internet that has a program like lynx or netscape). If you want to
6529 do this, you will also need to say Y or M to "Loop device support",
6532 This filesystem is also available as a module ( = code which can be
6533 inserted in and removed from the running kernel whenever you want).
6534 The module is called affs.o. If you want to compile it as a module,
6535 say M here and read Documentation/modules.txt. If unsure, say N.
6537 Apple Macintosh filesystem support (experimental)
6539 If you say Y here, you will be able to mount Macintosh-formatted
6540 floppy disks and hard drive partitions with full read-write access.
6541 Please read fs/hfs/HFS.txt to learn about the available mount
6544 This filesystem support is also available as a module ( = code which
6545 can be inserted in and removed from the running kernel whenever you
6546 want). The module is called hfs.o. If you want to compile it as a
6547 module, say M here and read Documentation/modules.txt.
6549 ROM filesystem support
6551 This is a very small read-only filesystem mainly intended for
6552 initial ram disks of installation disks, but it could be used for
6553 other read-only media as well. Read
6554 Documentation/filesystems/romfs.txt for details.
6556 This filesystem support is also available as a module ( = code which
6557 can be inserted in and removed from the running kernel whenever you
6558 want). The module is called romfs.o. If you want to compile it as a
6559 module, say M here and read Documentation/modules.txt.
6561 If you don't know whether you need it, then you don't need it: say
6564 QNX filesystem support (EXPERIMENTAL)
6566 This is the filesystem used by the operating system QNX 4. Say Y if
6567 you intend to mount QNX hard disks or floppies.
6569 This filesystem support is also available as a module ( = code which
6570 can be inserted in and removed from the running kernel whenever you
6571 want). The module is called qnx4.o. If you want to compile it as a
6572 module, say M here and read Documentation/modules.txt.
6576 Kernel automounter support
6578 The automounter is a tool to automatically mount remote filesystems
6579 on demand. This implementation is partially kernel-based to reduce
6580 overhead in the already-mounted case; this is unlike the BSD
6581 automounter (amd), which is a pure user space daemon.
6583 To use the automounter you need the user-space tools from
6584 ftp://ftp.kernel.org/pub/linux/daemons/autofs; you also want to say
6585 Y to "NFS filesystem support", above.
6587 If you want to compile this as a module ( = code which can be
6588 inserted in and removed from the running kernel whenever you want),
6589 say M here and read Documentation/modules.txt. The module will be
6592 If you are not a part of a fairly large, distributed network, you
6593 probably do not need an automounter, and can say N here.
6595 UFS filesystem support
6597 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
6598 OpenBSD and NeXTstep) use a filesystem called UFS. Some System V
6599 Unixes can create and mount hard disk partitions and diskettes using
6600 this filesystem as well. Saying Y here allows you to mount these
6601 partitions and diskettes.
6603 If you only intend to mount files from some other Unix over the
6604 network using NFS, you don't need the UFS filesystem support (but
6605 you need NFS filesystem support obviously).
6607 Note that this option is generally not needed for floppies, since a
6608 good portable way to transport files and directories between unixes
6609 (and even other operating systems) is given by the tar program ("man
6610 tar" or preferably "info tar").
6612 When accessing NeXTstep files, you may need to convert them from the
6613 NeXT character set to the Latin1 character set; use the program
6614 recode ("info recode") for this purpose.
6616 If you want to compile the UFS filesystem support as a module ( =
6617 code which can be inserted in and removed from the running kernel
6618 whenever you want), say M here and read Documentation/modules.txt.
6619 The module will be called ufs.o.
6621 If you haven't heard about all of this before, it's safe to say N.
6623 BSD disklabel (FreeBSD partition tables) support
6624 CONFIG_BSD_DISKLABEL
6625 FreeBSD uses its own hard disk partition scheme on your PC. It
6626 requires only one entry in the primary partition table of your disk
6627 and manages it similarly to DOS extended partitions, putting in its
6628 first sector a new partition table in disklabel format. Saying Y
6629 here allows you to read these disklabels and further mount FreeBSD
6630 partitions read-only from within Linux if you have also said Y to
6631 "UFS filesystem support", above. If you don't know what all this
6634 SMD disklabel (Sun partition tables) support
6635 CONFIG_SMD_DISKLABEL
6636 Like most systems, SunOS uses its own hard disk partition table
6637 format, incompatible with all others. Saying Y here allows you to
6638 read these partition tables and further mount SunOS disks read-only
6639 from within Linux if you have also said Y to "UFS filesystem
6640 support", above. This is mainly used to carry data from a SPARC
6641 under SunOS to your Linux box via a removable medium like
6642 magneto-optical or ZIP drives; note however that a good portable way
6643 to transport files and directories between unixes (and even other
6644 operating systems) is given by the tar program ("man tar" or
6645 preferably "info tar"). If you don't know what all this is about,
6648 Solaris (x86) partition table support
6649 CONFIG_SOLARIS_X86_PARTITION
6650 Like most systems, Solaris x86 uses its own hard disk partition
6651 table format, incompatible with all others. Saying Y here allows you
6652 to read these partition tables and further mount Solaris x86 disks
6653 read-only from within Linux if you have also said Y to "UFS
6654 filesystem support", above.
6656 ADFS filesystem support (read only) (EXPERIMENTAL)
6658 The Acorn Disc Filing System is the standard filesystem of the
6659 RiscOS operating system which runs on Acorn's ARM-based Risc PC
6660 systems and the Acorn Archimedes range of machines. If you say Y
6661 here, Linux will be able to read from ADFS partitions on hard drives
6662 and from ADFS-formatted floppy discs.
6664 The ADFS partition should be the first partition (i.e.,
6665 /dev/[hs]d?1) on each of your drives.
6667 This code is also available as a module called adfs.o ( = code which
6668 can be inserted in and removed from the running kernel whenever you
6669 want). If you want to compile it as a module, say M here and read
6670 Documentation/modules.txt.
6674 /dev/pts filesystem (experimental)
6676 You should say Y here if you said Y to "Unix98 PTY support" above.
6677 You'll then get a virtual filesystem which can be mounted on
6678 /dev/pts with "mount -t devpts". This, together with the pseudo
6679 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
6680 support as described in the Open Group's Unix98 standard: in order
6681 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
6682 of the pseudo terminal is then made available to the process and the
6683 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
6684 traditionally /dev/ttyp2 will then be /dev/pts/2, for example. The
6685 GNU C library glibc 2.1 contains the requisite support for this mode
6688 This code is also available as a module called devpts.o ( = code
6689 which can be inserted in and removed from the running kernel
6690 whenever you want). If you want to compile it as a module, say M
6691 here and read Documentation/modules.txt.
6693 Macintosh partition map support
6694 CONFIG_MAC_PARTITION
6695 Say Y here if you want your Linux system to be able to read the
6696 partition tables of Macintosh hard drives, and thus use partitions
6699 SMB filesystem support (to mount WfW shares etc..)
6701 SMB (Server Message Block) is the protocol Windows for Workgroups
6702 (WfW), Windows 95, Windows NT and Lan Manager use to share files and
6703 printers over local networks. Saying Y here allows you to mount
6704 their filesystems (often called "shares" in this context) and access
6705 them just like any other Unix directory. Currently, this works only
6706 if the Windows machines use TCP/IP as the underlying transport
6707 protocol, and not NetBEUI. For details, read
6708 Documentation/filesystems/smbfs.txt and the SMB-HOWTO, available via
6709 FTP (user: anonymous) from
6710 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
6712 Note: if you just want your box to act as an SMB *server* and make
6713 files and printing services available to Windows clients (which need
6714 to have a TCP/IP stack), you don't need to say Y here; you can use
6715 the program samba (available via FTP (user: anonymous) in
6716 ftp://sunsite.unc.edu/pub/Linux/system/network/samba) for that.
6718 General information about how to connect Linux, Windows machines and
6719 Macs is on the WWW at http://www.eats.com/linux_mac_win.html (to
6720 browse the WWW, you need to have access to a machine on the Internet
6721 that has a program like lynx or netscape).
6723 If you want to compile the SMB support as a module ( = code which
6724 can be inserted in and removed from the running kernel whenever you
6725 want), say M here and read Documentation/modules.txt. The module
6726 will be called smbfs.o. Most people say N, however.
6728 SMB Win95 bug work-around
6730 If you want to connect to a share exported by Windows 95, you should
6731 say Y here. The Windows 95 server contains a bug that makes listing
6732 directories unreliable. This option slows down the listing of
6733 directories. This makes the Windows 95 server a bit more stable.
6735 Coda filesystem support
6737 Coda is an advanced network filesystem, similar to NFS in that it
6738 enables you to mount filesystems of a remote server and access them
6739 with regular Unix commands as if they were sitting on your hard
6740 disk. Coda has several advantages over NFS: support for disconnected
6741 operation for laptops, read/write server replication, security model
6742 for authentication and encryption, persistent client caches and
6745 If you say Y here, your Linux box will be able to act as a Coda
6746 *client*. You will need user level code as well, both for the client
6747 and server. Servers are currently user level, i.e. need no kernel
6748 support. For technical information, read
6749 Documentation/filesystems/coda.txt. For further information see
6750 http://www.coda.cs.cmu.edu (to browse the WWW, you need to have
6751 access to a machine on the Internet that has a program like lynx or
6752 netscape) or contact Peter Braam <braam@cs.cmu.edu>.
6754 If you want to compile the coda client support as a module ( = code
6755 which can be inserted in and removed from the running kernel
6756 whenever you want), say M here and read Documentation/modules.txt.
6757 The module will be called coda.o.
6759 NCP filesystem support (to mount NetWare volumes)
6761 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
6762 used by Novell NetWare clients to talk to file servers. It is to IPX
6763 what NFS is to TCP/IP, if that helps. Saying Y here allows you to
6764 mount NetWare file server volumes and to access them just like any
6765 other Unix directory. For details, please read the file
6766 Documentation/filesystems/ncpfs.txt in the kernel source and the
6767 IPX-HOWTO on sunsite.unc.edu:/pub/Linux/docs/howto.
6769 You do not have to say Y here if you want your Linux box to act as a
6770 file *server* for Novell NetWare clients.
6772 General information about how to connect Linux, Windows machines and
6773 Macs is on the WWW at http://www.eats.com/linux_mac_win.html (to
6774 browse the WWW, you need to have access to a machine on the Internet
6775 that has a program like lynx or netscape).
6777 If you want to compile this as a module ( = code which can be
6778 inserted in and removed from the running kernel whenever you want),
6779 say M here and read Documentation/modules.txt. The module will be
6780 called ncpfs.o. Say N unless you are connected to a Novell network.
6783 CONFIG_NCPFS_PACKET_SIGNING
6784 NCP allows packets to be signed for stronger security. If you want
6785 security, say Y. Normal users can leave it off. To be able to use
6786 packet signing you must use ncpfs > 2.0.12.
6788 Proprietary file locking
6789 CONFIG_NCPFS_IOCTL_LOCKING
6790 Allows locking of records on remote volumes. Say N unless you have
6791 special applications which are able to utilize this locking scheme.
6793 Clear remove/delete inhibit when needed
6795 Allows manipulation of files flagged as Delete or Rename Inhibit. To
6796 use this feature you must mount volumes with the ncpmount parameter
6797 "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not mounting
6798 volumes with -f 444.
6800 Use NFS namespace when available
6802 Allows you to utilize NFS namespace on NetWare servers. It brings
6803 you case sensitive filenames. Say Y. You can disable it at
6804 mount-time with the `-N nfs' parameter of ncpmount.
6806 Use OS2/LONG namespace when available
6808 Allows you to utilize OS2/LONG namespace on NetWare servers.
6809 Filenames in this namespace are limited to 255 characters, they are
6810 case insensitive, and case in names is preserved. Say Y. You can
6811 disable it at mount time with the -N os2 parameter of ncpmount.
6813 Allow mounting of volume subdirectories
6814 CONFIG_NCPFS_MOUNT_SUBDIR
6815 Allows you to mount not only whole servers or whole volumes, but
6816 also subdirectories from a volume. It can be used to reexport data
6817 and so on. There is no reason to say N, so Y is recommended unless
6818 you count every byte.
6820 To utilize this feature you must use ncpfs-2.0.12 or newer.
6822 NDS interserver authentication domains
6823 CONFIG_NCPFS_NDS_DOMAINS
6824 This allows storing NDS private keys in kernel space where they
6825 can be used to authenticate another server as interserver NDS
6826 accesses need it. You must use ncpfs-2.0.12.1 or newer to utilize
6827 this feature. Say Y if you are using NDS connections to NetWare
6828 servers. Do not say Y if security is primary for you because root
6829 can read your session key (from /proc/kcore).
6831 nls: Native language codepages and Unicode support
6833 This is required by the FAT and NTFS filesystems and by the ISO 9660
6834 filesystem when it is compiled with Joliet support. Joliet is a
6835 Microsoft extension for CDROMs that supports Unicode. This allows
6836 translation between different character sets.
6838 When dealing with the FAT based filesystems, there are two character
6839 sets that are important. The first is the codepage. Codepages are
6840 character sets that are used by DOS to allow filenames to have
6841 native language characters when character sets were limited to 256
6842 characters. The codepage is the character set that is used to store
6843 native language characters on disk. The two most common codepages
6844 are 437 in the United States and 850 in much of Europe.
6846 The second important character set is the input/output character
6847 set. This is the character set that is displayed on the screen. In
6848 the United States, this will almost always be the ISO 8859-1
6849 character set. This is the default.
6851 Linux will only translate the FAT filenames, not the contents of the
6855 CONFIG_NLS_CODEPAGE_437
6856 The Microsoft fat filesystem family can deal with filenames in
6857 native language character sets. These character sets are stored
6858 in so-called DOS codepages. You need to include the appropriate
6859 codepage if you want to be able to read/write these filenames on
6860 DOS/Windows partitions correctly. This does apply to the filenames
6861 only, not to the file contents. You can include several codepages;
6862 say Y here if you want to include the DOS codepage that is used in
6863 the United States and parts of Canada. This is recommended.
6866 CONFIG_NLS_CODEPAGE_737
6867 The Microsoft fat filesystem family can deal with filenames in
6868 native language character sets. These character sets are stored
6869 in so-called DOS codepages. You need to include the appropriate
6870 codepage if you want to be able to read/write these filenames on
6871 DOS/Windows partitions correctly. This does apply to the filenames
6872 only, not to the file contents. You can include several codepages;
6873 say Y here if you want to include the DOS codepage that is used for
6874 Greek. If unsure, say N.
6877 CONFIG_NLS_CODEPAGE_775
6878 The Microsoft fat filesystem family can deal with filenames in
6879 native language character sets. These character sets are stored
6880 in so-called DOS codepages. You need to include the appropriate
6881 codepage if you want to be able to read/write these filenames on
6882 DOS/Windows partitions correctly. This does apply to the filenames
6883 only, not to the file contents. You can include several codepages;
6884 say Y here if you want to include the DOS codepage that is used
6885 for the Baltic Rim Languages. If unsure, say N.
6888 CONFIG_NLS_CODEPAGE_850
6889 The Microsoft fat filesystem family can deal with filenames in
6890 native language character sets. These character sets are stored
6891 in so-called DOS codepages. You need to include the appropriate
6892 codepage if you want to be able to read/write these filenames on
6893 DOS/Windows partitions correctly. This does apply to the filenames
6894 only, not to the file contents. You can include several codepages;
6895 say Y here if you want to include the DOS codepage that is used for
6896 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add more
6897 countries here]. It has some characters useful to many European
6898 languages that are not part of the US codepage 437. If unsure, say
6902 CONFIG_NLS_CODEPAGE_852
6903 The Microsoft fat filesystem family can deal with filenames in
6904 native language character sets. These character sets are stored in
6905 so-called DOS codepages. You need to include the appropriate
6906 codepage if you want to be able to read/write these filenames on
6907 DOS/Windows partitions correctly. This does apply to the filenames
6908 only, not to the file contents. You can include several codepages;
6909 say Y here if you want to include the Latin 2 codepage used by DOS
6910 for much of Central and Eastern Europe. It has all the required
6911 characters for these languages: Albanian, Croatian, Czech, English,
6912 Finnish, Hungarian, Irish, German, Polish, Romanian, Serbian (Latin
6913 transcription), Slovak, Slovenian, and Sorbian.
6916 CONFIG_NLS_CODEPAGE_855
6917 The Microsoft fat filesystem family can deal with filenames in
6918 native language character sets. These character sets are stored in
6919 so-called DOS codepages. You need to include the appropriate
6920 codepage if you want to be able to read/write these filenames on
6921 DOS/Windows partitions correctly. This does apply to the filenames
6922 only, not to the file contents. You can include several codepages;
6923 say Y here if you want to include the DOS codepage for Cyrillic.
6926 CONFIG_NLS_CODEPAGE_857
6927 The Microsoft fat filesystem family can deal with filenames in
6928 native language character sets. These character sets are stored in
6929 so-called DOS codepages. You need to include the appropriate
6930 codepage if you want to be able to read/write these filenames on
6931 DOS/Windows partitions correctly. This does apply to the filenames
6932 only, not to the file contents. You can include several codepages;
6933 say Y here if you want to include the DOS codepage for Turkish.
6936 CONFIG_NLS_CODEPAGE_860
6937 The Microsoft fat filesystem family can deal with filenames in
6938 native language character sets. These character sets are stored in
6939 so-called DOS codepages. You need to include the appropriate
6940 codepage if you want to be able to read/write these filenames on
6941 DOS/Windows partitions correctly. This does apply to the filenames
6942 only, not to the file contents. You can include several codepages;
6943 say Y here if you want to include the DOS codepage for Portuguese.
6946 CONFIG_NLS_CODEPAGE_861
6947 The Microsoft fat filesystem family can deal with filenames in
6948 native language character sets. These character sets are stored in
6949 so-called DOS codepages. You need to include the appropriate
6950 codepage if you want to be able to read/write these filenames on
6951 DOS/Windows partitions correctly. This does apply to the filenames
6952 only, not to the file contents. You can include several codepages;
6953 say Y here if you want to include the DOS codepage for Icelandic.
6956 CONFIG_NLS_CODEPAGE_862
6957 The Microsoft fat filesystem family can deal with filenames in
6958 native language character sets. These character sets are stored in
6959 so-called DOS codepages. You need to include the appropriate
6960 codepage if you want to be able to read/write these filenames on
6961 DOS/Windows partitions correctly. This does apply to the filenames
6962 only, not to the file contents. You can include several codepages;
6963 say Y here if you want to include the DOS codepage for Hebrew.
6966 CONFIG_NLS_CODEPAGE_863
6967 The Microsoft fat filesystem family can deal with filenames in
6968 native language character sets. These character sets are stored in
6969 so-called DOS codepages. You need to include the appropriate
6970 codepage if you want to be able to read/write these filenames on
6971 DOS/Windows partitions correctly. This does apply to the filenames
6972 only, not to the file contents. You can include several codepages;
6973 say Y here if you want to include the DOS codepage for Canadian
6977 CONFIG_NLS_CODEPAGE_864
6978 The Microsoft fat filesystem family can deal with filenames in
6979 native language character sets. These character sets are stored in
6980 so-called DOS codepages. You need to include the appropriate
6981 codepage if you want to be able to read/write these filenames on
6982 DOS/Windows partitions correctly. This does apply to the filenames
6983 only, not to the file contents. You can include several codepages;
6984 say Y here if you want to include the DOS codepage for Arabic.
6987 CONFIG_NLS_CODEPAGE_865
6988 The Microsoft fat filesystem family can deal with filenames in
6989 native language character sets. These character sets are stored in
6990 so-called DOS codepages. You need to include the appropriate
6991 codepage if you want to be able to read/write these filenames on
6992 DOS/Windows partitions correctly. This does apply to the filenames
6993 only, not to the file contents. You can include several codepages;
6994 say Y here if you want to include the DOS codepage for the Nordic
6998 CONFIG_NLS_CODEPAGE_866
6999 The Microsoft fat filesystem family can deal with filenames in
7000 native language character sets. These character sets are stored in
7001 so-called DOS codepages. You need to include the appropriate
7002 codepage if you want to be able to read/write these filenames on
7003 DOS/Windows partitions correctly. This does apply to the filenames
7004 only, not to the file contents. You can include several codepages;
7005 say Y here if you want to include the DOS codepage for
7009 CONFIG_NLS_CODEPAGE_869
7010 The Microsoft fat filesystem family can deal with filenames in
7011 native language character sets. These character sets are stored in
7012 so-called DOS codepages. You need to include the appropriate
7013 codepage if you want to be able to read/write these filenames on
7014 DOS/Windows partitions correctly. This does apply to the filenames
7015 only, not to the file contents. You can include several codepages;
7016 say Y here if you want to include the DOS codepage for Greek.
7018 ### Why do we have two codepages for Greek and Cyrillic?
7022 CONFIG_NLS_CODEPAGE_874
7023 The Microsoft fat filesystem family can deal with filenames in
7024 native language character sets. These character sets are stored in
7025 so-called DOS codepages. You need to include the appropriate
7026 codepage if you want to be able to read/write these filenames on
7027 DOS/Windows partitions correctly. This does apply to the filenames
7028 only, not to the file contents. You can include several codepages;
7029 say Y here if you want to include the DOS codepage for Thai.
7032 CONFIG_NLS_ISO8859_1
7033 If you want to display filenames with native language characters
7034 from the Microsoft fat filesystem family or from JOLIET CDROMs
7035 correctly on the screen, you need to include the appropriate
7036 input/output character sets. Say Y here for the Latin 1 character
7037 set, which covers most West European languages such as Albanian,
7038 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
7039 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
7040 Swedish, and Valencian. It is also the default for the US. If
7044 CONFIG_NLS_ISO8859_2
7045 If you want to display filenames with native language characters
7046 from the Microsoft fat filesystem family or from JOLIET CDROMs
7047 correctly on the screen, you need to include the appropriate
7048 input/output character sets. Say Y here for the Latin 2 character
7049 set, which works for most Latin-written Slavic and Central European
7050 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
7054 CONFIG_NLS_ISO8859_3
7055 If you want to display filenames with native language characters
7056 from the Microsoft fat filesystem family or from JOLIET CDROMs
7057 correctly on the screen, you need to include the appropriate
7058 input/output character sets. Say Y here for the Latin 3 character
7059 set, which is popular with authors of Esperanto, Galician, Maltese,
7063 CONFIG_NLS_ISO8859_4
7064 If you want to display filenames with native language characters
7065 from the Microsoft fat filesystem family or from JOLIET CDROMs
7066 correctly on the screen, you need to include the appropriate
7067 input/output character sets. Say Y here for the Latin 4 character
7068 set which introduces letters for Estonian, Latvian, and
7069 Lithuanian. It is an incomplete predecessor of Latin 6.
7072 CONFIG_NLS_ISO8859_5
7073 If you want to display filenames with native language characters
7074 from the Microsoft fat filesystem family or from JOLIET CDROMs
7075 correctly on the screen, you need to include the appropriate
7076 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
7077 character set with which you can type Bulgarian, Byelorussian,
7078 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
7079 KOI8-R is preferred in Russia.
7082 CONFIG_NLS_ISO8859_6
7083 If you want to display filenames with native language characters
7084 from the Microsoft fat filesystem family or from JOLIET CDROMs
7085 correctly on the screen, you need to include the appropriate
7086 input/output character sets. Say Y here for ISO8859-6, the Arabic
7090 CONFIG_NLS_ISO8859_7
7091 If you want to display filenames with native language characters
7092 from the Microsoft fat filesystem family or from JOLIET CDROMs
7093 correctly on the screen, you need to include the appropriate
7094 input/output character sets. Say Y here for ISO8859-7, the Modern
7095 Greek character set.
7098 CONFIG_NLS_ISO8859_8
7099 If you want to display filenames with native language characters
7100 from the Microsoft fat filesystem family or from JOLIET CDROMs
7101 correctly on the screen, you need to include the appropriate
7102 input/output character sets. Say Y here for ISO8859-8, the Hebrew
7106 CONFIG_NLS_ISO8859_9
7107 If you want to display filenames with native language characters
7108 from the Microsoft fat filesystem family or from JOLIET CDROMs
7109 correctly on the screen, you need to include the appropriate
7110 input/output character sets. Say Y here for the Latin 5 character
7111 set, and it replaces the rarely needed Icelandic letters in Latin 1
7112 with the Turkish ones. Useful in Turkey.
7115 CONFIG_NLS_ISO8859_10
7116 If you want to display filenames with native language characters
7117 from the Microsoft fat filesystem family or from JOLIET CDROMs
7118 correctly on the screen, you need to include the appropriate
7119 input/output character sets. Say Y here for the Latin 6 character
7120 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
7121 letters that were missing in Latin 4 to cover the entire Nordic
7126 If you want to display filenames with native language characters
7127 from the Microsoft fat filesystem family or from JOLIET CDROMs
7128 correctly on the screen, you need to include the appropriate
7129 input/output character sets. Say Y here for the preferred Russian
7134 If you say Y here, you will get support for a terminal device with
7135 display and keyboard devices. These are called "virtual" because you
7136 can run several virtual terminals on one physical terminal; however,
7137 you need at least one virtual terminal device in order to make use
7138 of a physical terminal. Only people using embedded systems want to
7139 say N here; most everybody else says Y. If unsure, say Y, or else
7140 you won't be able to do much with your new shiny Linux system :-)
7142 Support for console on virtual terminal
7144 If you say Y here, by default all kernel messages will be sent to
7145 the device /dev/tty0 which corresponds to the virtual terminal that
7146 is visible on your display. You should say Y here unless you only
7147 want to have the kernel messages output to a serial port (in which
7148 case you probably want to say Y to "Console on serial port", below).
7150 Software generated cursor
7152 If you say Y here, you'll be able to do lots of nice things with the
7153 cursors of your virtual consoles -- for example turn them into
7154 non-blinking block cursors which are more visible on laptop screens,
7155 or change their color depending on the virtual console you're on.
7156 See Documentation/VGA-softcursor.txt for more information.
7158 Standard/generic serial support
7160 This selects whether you want to include the driver for the standard
7161 serial ports. The standard answer is Y. People who might say N here
7162 are those that are setting up dedicated Ethernet WWW/FTP servers, or
7163 users that have one of the various bus mice instead of a serial
7164 mouse and don't intend to use their machine's standard serial port
7165 for anything. (Note that the Cyclades and Stallion multi serial port
7166 drivers do not need this driver built in for them to work.)
7168 If you want to compile this driver as a module, say M here and read
7169 Documentation/modules.txt. The module will be called serial.o.
7170 [WARNING: Do not compile this driver as a module if you are using
7171 non-standard serial ports, since the configuration information will
7172 be lost if you unload the driver. This limitation may be lifted in
7175 BTW1: If you have a mouseman serial mouse which is not recognized by
7176 the X window system, try running gpm first.
7178 BTW2: If you intend to connect a so-called Winmodem to your
7179 machine's serial port, forget it. These modems require proprietary
7180 drivers which are only available under Windows.
7182 Most people will say Y or M here, so that they can use serial mice,
7183 modems and similar devices connecting to the standard serial ports.
7185 Support for console on serial port
7186 CONFIG_SERIAL_CONSOLE
7187 If you say Y here, it is possible to use a serial port as the
7188 console. By default still the currently visible virtual console will
7189 be used as the system console but you can alter that using a kernel
7190 command line option such as "console=ttyS1". (Try "man bootparam" or
7191 see the documentation of your boot loader (lilo or loadlin) about
7192 how to pass options to the kernel at boot time. The lilo procedure
7193 is also explained in the SCSI-HOWTO, available via FTP (user:
7194 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.) If you
7195 don't have a VGA card installed and you say Y here, the kernel will
7196 automatically use /dev/ttyS0 as system console.
7198 Comtrol Rocketport support
7200 This is a driver for the Comtrol Rocketport cards which provide
7201 multiple serial ports. You would need something like this to
7202 connect more than two modems to your Linux box, for instance in
7203 order to become a BBS.
7205 If you want to compile this driver as a module, say M here and read
7206 Documentation/modules.txt. The module will be called rocket.o.
7208 Digiboard Intelligent async support
7210 This is a driver for Digi International's Xx, Xeve, and Xem series
7211 of cards which provide multiple serial ports. You would need
7212 something like this to connect more than two modems to your Linux
7213 box, for instance in order to become a BBS. This driver supports the
7214 original PC (ISA) boards as well as PCI, and EISA. If you have a
7215 card like this, say Y here and read the file
7216 Documentation/digiepca.txt.
7218 NOTE: There is another, separate driver for the Digiboard PC boards:
7219 "Digiboard PC/Xx Support" below. You should (and can) only select
7220 one of the two drivers.
7222 If you want to compile this driver as a module, say M here and read
7223 Documentation/modules.txt. The module will be called epca.o.
7225 Digiboard PC/Xx Support
7227 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
7228 that give you many serial ports. You would need something like this
7229 to connect more than two modems to your Linux box, for instance in
7230 order to become a BBS. If you have a card like that, say Y here and
7231 read the file Documentation/digiboard.txt.
7233 If you want to compile this driver as a module, say M here and read
7234 Documentation/modules.txt. The module will be called pcxx.o.
7236 SDL RISCom/8 card support
7238 This is a driver for the SDL Communications RISCom/8 multiport card,
7239 which gives you many serial ports. You would need something like
7240 this to connect more than two modems to your Linux box, for instance
7241 in order to become a BBS. If you have a card like that, say Y here
7242 and read the file Documentation/riscom8.txt.
7244 Also it's possible to say M here and compile this driver as kernel
7245 loadable module; the module will be called riscom8.o.
7247 Specialix IO8+ card support
7249 This is a driver for the Specialix IO8+ multiport card (both the
7250 ISA and the PCI version) which gives you many serial ports. You
7251 would need something like this to connect more than two modems to
7252 your Linux box, for instance in order to become a BBS.
7254 If you have a card like that, say Y here and read the file
7255 Documentation/specialix.txt. Also it's possible to say M here and
7256 compile this driver as kernel loadable module which will be called
7259 Specialix DTR/RTS pin is RTS
7260 CONFIG_SPECIALIX_RTSCTS
7261 The Specialix card can only support either RTS or DTR. If you say
7262 N here, the driver will use the pin as "DTR" when the tty is in
7263 software handshake mode. If you say Y here or hardware handshake
7264 is on, it will always be RTS. Read the file
7265 Documentation/specialix.txt for more information.
7267 Cyclades async mux support
7269 This is a driver for a card that gives you many serial ports. You
7270 would need something like this to connect more than two modems to
7271 your Linux box, for instance in order to become a BBS. For
7272 information about the Cyclades-Z card, read
7273 drivers/char/README.cycladesZ.
7275 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
7278 If you want to compile this as a module ( = code which can be
7279 inserted in and removed from the running kernel whenever you want),
7280 say M here and read Documentation/modules.txt. The module will be
7283 If you haven't heard about it, it's safe to say N.
7285 Stallion multiport serial support
7287 Stallion cards give you many serial ports. You would need something
7288 like this to connect more than two modems to your Linux box, for
7289 instance in order to become a BBS. If you say Y here, you will be
7290 asked for your specific card model in the next questions. Make sure
7291 to read drivers/char/README.stallion in this case. If you have never
7292 heard about all this, it's safe to say N.
7294 Stallion EasyIO or EC8/32 support
7296 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
7297 card, then this is for you; say Y. Make sure to read
7298 Documentation/stallion.txt.
7300 If you want to compile this as a module ( = code which can be
7301 inserted in and removed from the running kernel whenever you want),
7302 say M here and read Documentation/modules.txt. The module will be
7305 Stallion EC8/64, ONboard, Brumby support
7307 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
7308 serial multiport card, say Y here. Make sure to read
7309 Documentation/stallion.txt.
7311 To compile it as a module ( = code which can be inserted in and
7312 removed from the running kernel whenever you want), say M here and
7313 read Documentation/modules.txt. The module will be called
7316 Hayes ESP serial port support
7318 This is a driver which supports Hayes ESP serial ports. Both single
7319 port cards and multiport cards are supported. Make sure to read
7320 Documentation/hayes-esp.txt.
7322 To compile this driver as a module ( = code which can be inserted in
7323 and removed from the running kernel whenever you want), say M here
7324 and read Documentation/modules.txt. The module will be called esp.o.
7329 A pseudo terminal (PTY) is a software device consisting of two
7330 halves: a master and a slave. The slave device behaves identical to
7331 a physical terminal; the master device is used by a process to
7332 read data from and write data to the slave, thereby emulating a
7333 terminal. Typical programs for the master side are xterm and telnet
7336 Linux has traditionally used the BSD-like names /dev/ptyxx for
7337 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
7338 has a number of problems. The GNU C library glibc 2.1 and later,
7339 however, supports the Unix98 naming standard: in order to acquire a
7340 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
7341 terminal is then made available to the process and the pseudo
7342 terminal slave can be accessed as /dev/pts/<number>. What was
7343 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
7345 The entries in /dev/pts/ are created on the fly by a virtual
7346 filesystem; therefore, if you say Y here you should say Y to
7347 "/dev/pts filesystem for Unix98 PTYs" as well.
7349 Say Y here if you are uncertain, unless you are very short on
7352 Maximum number of Unix98 PTYs in use (0-2048)
7353 CONFIG_UNIX98_PTY_COUNT
7354 The maximum number of Unix98 PTYs that can be used at any one time.
7355 The default is 256, and should be enough for desktop systems. Server
7356 machines which support incoming telnet/rlogin/ssh connections and/or
7357 serve several X terminals may want to increase this: every incoming
7358 connection and every xterm uses up one PTY.
7360 When not in use, each additional set of 256 PTYs occupy
7361 approximately 8K of kernel memory on 32-bit architectures.
7363 Parallel printer support
7365 If you intend to attach a printer to the parallel port of your Linux
7366 box (as opposed to using a serial printer; if the connector at the
7367 printer has 9 or 25 holes ["female"], then it's serial), say Y. Also
7368 read the Printing-HOWTO, available via FTP (user: anonymous) in
7369 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
7371 It is possible to share one parallel port among several devices
7372 (e.g. printer and ZIP drive) and it is safe to compile the
7373 corresponding drivers into the kernel. If you want to compile this
7374 driver as a module however ( = code which can be inserted in and
7375 removed from the running kernel whenever you want), say M here and
7376 read Documentation/modules.txt. The module will be called lp.o.
7378 If you have several parallel ports, you should specify the base
7379 address for the port to be used by the printer with the "lp" kernel
7380 command line option. (Try "man bootparam" or see the documentation
7381 of your boot loader (lilo or loadlin) about how to pass options to
7382 the kernel at boot time. The lilo procedure is also explained in the
7383 SCSI-HOWTO, available via FTP (user: anonymous) in
7384 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.) The standard base
7385 addresses as well as the syntax of the "lp" command line option can
7386 be found in drivers/char/lp.c.
7388 If you have more than 3 printers, you need to increase the LP_NO
7391 Support IEEE1284 status readback
7392 CONFIG_PRINTER_READBACK
7393 If your printer conforms to IEEE 1284, it may be able to provide a
7394 status indication when you read from it (for example, with `cat
7395 /dev/lp1'). To use this feature, say Y here.
7397 Mouse Support (not serial mice)
7399 This is for machines with a bus mouse or a PS/2 mouse as opposed to
7400 a serial mouse. Most people have a regular serial MouseSystem or
7401 Microsoft mouse (made by Logitech) that plugs into a COM port
7402 (rectangular with 9 or 25 pins). These people say N here. If you
7403 have something else, read the Busmouse-HOWTO, available via FTP
7404 (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO and
7407 If you have a laptop, you either have to check the documentation or
7408 experiment a bit to find out whether the trackball is a serial mouse
7409 or not; it's best to say Y here for you.
7411 Note that the answer to this question won't directly affect the
7412 kernel: saying N will just cause this configure script to skip all
7413 the questions about non-serial mice. If unsure, say Y.
7415 Logitech busmouse support
7417 Logitech mouse connected to a proprietary interface card. It's
7418 generally a round connector with 9 pins. Note that the newer mice
7419 made by Logitech don't use the Logitech protocol anymore; for those,
7420 you don't need this option. You want to read the Busmouse-HOWTO,
7421 available via FTP (user: anonymous) in
7422 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
7424 If you want to compile this as a module ( = code which can be
7425 inserted in and removed from the running kernel whenever you want),
7426 say M here and read Documentation/modules.txt. The module will be
7427 called busmouse.o. If you are unsure, say N and read the HOWTO
7428 nevertheless: it will tell you what you have.
7430 PS/2 mouse (aka "auxiliary device") support
7432 The PS/2 mouse connects to a special mouse port that looks much like
7433 the keyboard port (small circular connector with 6 pins). This way,
7434 the mouse does not use any serial ports. This port can also be used
7435 for other input devices like light pens, tablets, keypads. Compaq,
7436 AST and IBM all use this as their mouse port on currently shipping
7437 machines. The trackballs of some laptops are PS/2 mice also. In
7438 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
7439 Although PS/2 mice are not technically bus mice, they are explained
7440 in detail in the Busmouse-HOWTO, available via FTP (user: anonymous)
7441 in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. When using a PS/2
7442 mouse, you can get problems if you want to use the mouse both on the
7443 Linux console and under X. Using the "-R" option of the Linux mouse
7444 managing program gpm (available from
7445 sunsite.unc.edu:/pub/Linux/system/Daemons) solves this problem, or
7446 you can get the "mconv" utility also from sunsite.
7448 If you want to compile this mouse driver as a module ( = code which
7449 can be inserted in and removed from the running kernel whenever you
7450 want), say M here and read Documentation/modules.txt. The module
7451 will be called psaux.o. If you are unsure, say N and read the HOWTO
7452 nevertheless: it will tell you what you have.
7454 C&T 82C710 mouse port support (as on TI Travelmate)
7456 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
7457 you are unsure, try first to say N here and come back if the mouse
7458 doesn't work. Read the Busmouse-HOWTO, available via FTP (user:
7459 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
7461 PC110 digitizer pad support
7463 This drives the digitizer pad on the IBM PC110 palmtop (see
7464 http://toy.cabi.net; to browse the WWW, you need to have access to a
7465 machine on the Internet that has a program like lynx or
7466 netscape). It can turn the digitizer pad into a PS/2 mouse emulation
7467 with tap gestures or into an absolute pad.
7469 If you want to compile this as a module ( = code which can be
7470 inserted in and removed from the running kernel whenever you want),
7471 say M here and read Documentation/modules.txt. The module will be
7474 Microsoft busmouse support
7476 These animals (also called Inport mice) are connected to an
7477 expansion board using a round connector with 9 pins. If this is what
7478 you have, say Y and read the Busmouse-HOWTO, available via FTP
7479 (user: anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
7481 If you are unsure, say N and read the HOWTO nevertheless: it will
7482 tell you what you have. Also be aware that several vendors talk
7483 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
7484 count the pins on the connector.
7486 If you want to compile this as a module ( = code which can be
7487 inserted in and removed from the running kernel whenever you want),
7488 say M here and read Documentation/modules.txt. The module will be
7489 called msbusmouse.o.
7491 ATIXL busmouse support
7492 CONFIG_ATIXL_BUSMOUSE
7493 This is a rare type of busmouse that is connected to the back of an
7494 ATI video card. Note that most ATI mice are actually Microsoft
7495 busmice. Read the Busmouse-HOWTO, available via FTP (user:
7496 anonymous) in ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO.
7498 If you want to compile this as a module ( = code which can be
7499 inserted in and removed from the running kernel whenever you want),
7500 say M here and read Documentation/modules.txt. The module will be
7501 called atixlmouse.o.
7503 If you are unsure, say N and read the HOWTO nevertheless: it will
7504 tell you what you have.
7506 Support for user miscellaneous modules
7508 This option forces generic miscellaneous minor device support in the
7509 kernel, and allows later loading of user miscellaneous character
7510 device modules, such as drivers for optic pens and touchscreens.
7511 Unless you need such specific modules, or are willing to write/test
7516 If you have a non-SCSI tape drive like that, say Y. Or, if you want
7517 to compile this driver as a module ( = code which can be inserted in
7518 and removed from the running kernel whenever you want), say M here
7519 and read Documentation/modules.txt. The module will be called
7522 Do you want runtime configuration for QIC-02
7523 CONFIG_QIC02_DYNCONF
7524 You can either configure this driver once and for all by editing a
7525 header file (include/linux/tpqic02.h), in which case you should
7526 say N, or you can fetch a program via anonymous FTP which is able
7527 to configure this driver during runtime. The program to do this is
7528 called 'qic02conf' and it is part of the 'tpqic02-support-X.Y.tar.gz'
7531 If you want to use the qic02conf program, say Y.
7533 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
7535 If you have a tape drive that is connected to your floppy
7536 controller, say Y here.
7538 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
7539 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
7540 controller of their own. These drives (and their companion
7541 controllers) are also supported if you say Y here.
7543 If you have a special controller (such as the CMS FC-10, FC-20,
7544 Mountain Mach-II, or any controller that is based on the Intel 82078
7545 FDC like the high speed controllers by Seagate and Exabyte and
7546 Iomega's "Ditto Dash") you must configure it by selecting the
7547 appropriate entries from the "Floppy tape controllers" sub-menu
7548 below and possibly modify the default values for the IRQ and DMA
7549 channel and the IO base in ftape's configuration menu.
7551 If you want to use your floppy tape drive on a PCI-bus based system,
7552 please read the file drivers/char/ftape/README.PCI.
7554 The ftape kernel driver is also available as a runtime loadable
7555 module ( = code which can be inserted in and removed from the
7556 running kernel whenever you want). If you want to compile it as a
7557 module, say M here and read Documentation/modules.txt. The module
7558 will be called ftape.o.
7560 Note that the Ftape-HOWTO is out of date (sorry) and documents the
7561 older version 2.08 of this software but still contains useful
7562 information. There is a web page with more recent documentation at
7563 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ . This page
7564 always contains the latest release of the ftape driver and useful
7565 information (backup software, ftape related patches and
7566 documentation, FAQ). (To browse the WWW, you need to have access to
7567 a machine on the Internet that has a program like lynx or netscape.)
7568 Note that the file system interface has changed quite a bit compared
7569 to previous versions of ftape. Please read Documentation/ftape.txt.
7571 The file system interface for ftape
7573 Normally, you want to say Y or M. DON'T say N here or you
7574 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
7576 The ftape module itself no longer contains the routines necessary
7577 to interface with the kernel VFS layer (i.e. to actually write data
7578 to and read data from the tape drive). Instead the file system
7579 interface (i.e. the hardware independent part of the driver) has
7580 been moved to a separate module.
7582 If you say M zftape will be compiled as a runtime loadable
7583 module ( = code which can be inserted in and removed from the
7584 running kernel whenever you want). In this case you should read
7585 Documentation/modules.txt. The module will be called zftape.o.
7587 Regardless of whether you say Y or M here, an additional runtime
7588 loadable module called `zft-compressor.o' which contains code to
7589 support user transparent on-the-fly compression based on Ross
7590 William's lzrw3 algorithm will be produced. If you have enabled the
7591 kernel module loader (i.e. have said Y to "Kernel module loader
7592 support", above) then `zft-compressor.o' will be loaded
7593 automatically by zftape when needed.
7595 Despite its name, zftape does NOT use compression by default. The
7596 file Documentation/ftape.txt contains a short description of the
7597 most important changes in the file system interface compared to
7598 previous versions of ftape. The ftape home page
7599 http://www-math.math.rwth-aachen.de/~LBFM/claus/ftape/ contains
7600 further information (to browse the WWW, you need to have access to a
7601 machine on the Internet that has a program like lynx or netscape).
7603 IMPORTANT NOTE: zftape can read archives created by previous
7604 versions of ftape and provide file mark support (i.e. fast skipping
7605 between tape archives) but previous version of ftape will lack file
7606 mark support when reading archives produced by zftape.
7608 Default block size for zftape
7609 CONFIG_ZFT_DFLT_BLK_SZ
7610 If unsure leave this at its default value, i.e. 10240. Note that
7611 you specify only the default block size here. The block size can be
7612 changed at run time using the MTSETBLK tape operation with the
7613 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
7614 shell command line).
7616 The probably most striking difference between zftape and previous
7617 versions of ftape is the fact that all data must be written or read
7618 in multiples of a fixed block size. The block size defaults to
7619 10240 which is what GNU tar uses. The values for the block size
7620 should be either 1 or multiples of 1024 up to a maximum value of
7621 63488 (i.e. 62k). If you specify `1' then zftape's builtin
7622 compression will be disabled.
7624 Reasonable values are `10240' (GNU tar's default block size),
7625 `5120' (afio's default block size), `32768' (default block size some
7626 backup programs assume for SCSI tape drives) or `1' (no restriction
7627 on block size, but disables builtin compression).
7629 Number of DMA buffers
7630 CONFIG_FT_NR_BUFFERS
7631 Please leave this at `3' unless you REALLY know what you are
7632 doing. It is not necessary to change this value. Values below 3 make
7633 the proper use of ftape impossible, values greater than 3 are a waste
7634 of memory. You can change the amount of DMA memory used by ftape at
7635 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
7636 wastes 32kb of memory. Please note that this memory cannot be
7639 Procfs entry for ftape
7641 Optional. Saying Y will result in creation of a directory
7642 `/proc/ftape' under the proc file system. The files can be viewed
7643 with your favorite pager (i.e. use "more /proc/ftape/history" or
7644 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
7645 file will contain some status information about the inserted
7646 cartridge, the kernel driver, your tape drive, the floppy disk
7647 controller and the error history for the most recent use of the
7648 kernel driver. Saying Y will enlarge the size of the ftape driver
7649 by approximately 2k.
7651 WARNING: When compiling ftape as a module (i.e. saying `M' to
7652 "Floppy tape drive") it is dangerous to use ftape's proc file system
7653 interface. Accessing `/proc/ftape' while the module is unloaded will
7654 result in a kernel Oops. This cannot be fixed from inside ftape.
7656 Controlling the amount of debugging output of ftape
7657 CONFIG_FT_NORMAL_DEBUG
7658 This option controls the amount of debugging output the ftape driver
7659 is ABLE to produce; it does not increase or diminish the debugging
7660 level itself. If unsure, leave this at its default setting,
7661 i.e. choose "Normal".
7663 Ftape can print lots of debugging messages to the system console
7664 resp. kernel log files. Reducing the amount of possible debugging
7665 output reduces the size of the kernel module by some kb, so it might
7666 be a good idea to use "None" for emergency boot floppies.
7668 If you want to save memory then the following strategy is
7669 recommended: leave this option at its default setting "Normal" until
7670 you know that the driver works as expected, afterwards reconfigure
7671 the kernel, this time specifying "Reduced" or "None" and recompile
7672 and install the kernel as usual. Note that choosing "Excessive"
7673 debugging output does not increase the amount of debugging output
7674 printed to the console but only makes it possible to produce
7675 "Excessive" debugging output.
7677 Please read Documentation/ftape.txt for a short description
7678 how to control the amount of debugging output.
7680 The floppy drive controller for ftape
7682 Only change this setting if you have a special controller. If you
7683 didn't plug any add-on card into your computer system but just
7684 plugged the floppy tape cable into the already existing floppy drive
7685 controller then you don't want to change the default setting,
7686 i.e. choose "Standard".
7688 Choose "MACH-2" if you have a Mountain Mach-2 controller.
7689 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
7691 Choose "Alt/82078" if you have another controller that is located at
7692 an IO base address different from the standard floppy drive
7693 controller's base address of `0x3f0', or uses an IRQ (interrupt)
7694 channel different from `6', or a DMA channel different from
7695 `2'. This is necessary for any controller card that is based on
7696 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
7699 If you choose something other than "Standard" then please make
7700 sure that the settings for the IO base address and the IRQ and DMA
7701 channel in the configuration menus below are correct. Use the manual
7702 of your tape drive to determine the correct settings!
7704 If you are already successfully using your tape drive with another
7705 operating system then you definitely should use the same settings
7706 for the IO base, the IRQ and DMA channel that have proven to work
7709 Note that this menu lets you specify only the default setting for
7710 the hardware setup. The hardware configuration can be changed at
7711 boot time (when ftape is compiled into the kernel, i.e. if you
7712 have said Y to "Floppy tape drive") or module load time (i.e. if you
7713 have said M to "Floppy tape drive").
7715 Please read also the file Documentation/ftape.txt which
7716 contains a short description of the parameters that can be set at
7717 boot or load time. If you want to use your floppy tape drive on a
7718 PCI-bus based system, please read the file
7719 drivers/char/ftape/README.PCI.
7721 IO base of the floppy disk controller used with Ftape
7723 You don't need to specify a value if the following default
7724 settings for the base IO address are correct:
7725 <<< MACH-2 : 0x1E0 >>>
7726 <<< FC-10/FC-20: 0x180 >>>
7727 <<< Secondary : 0x370 >>>
7728 Secondary refers to a secondary FDC controller like the "high speed"
7729 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
7730 Please make sure that the setting for the IO base address
7731 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
7732 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
7733 successfully using the tape drive with another operating system then
7734 you definitely should use the same settings for the IO base that has
7735 proven to work with that other OS.
7737 Note that this menu lets you specify only the default setting for
7738 the IO base. The hardware configuration can be changed at boot time
7739 (when ftape is compiled into the kernel, i.e. if you specified Y to
7740 "Floppy tape drive") or module load time (i.e. if you have said M to
7741 "Floppy tape drive").
7743 Please read also the file Documentation/ftape.txt which contains a
7744 short description of the parameters that can be set at boot or load
7747 IRQ channel for the floppy disk controller used with Ftape
7749 You don't need to specify a value if the following default
7750 settings for the interrupt channel are correct:
7752 <<< FC-10/FC-20: 9 >>>
7753 <<< Secondary : 6 >>>
7754 Secondary refers to secondary a FDC controller like the "high speed"
7755 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
7756 Please make sure that the setting for the IO base address
7757 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
7758 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
7759 successfully using the tape drive with another operating system then
7760 you definitely should use the same settings for the IO base that has
7761 proven to work with that other OS.
7763 Note that this menu lets you specify only the default setting for
7764 the IRQ channel. The hardware configuration can be changed at boot
7765 time (when ftape is compiled into the kernel, i.e. if you specified
7766 Y to "Floppy tape drive") or module load time (i.e. if you have said M
7767 to "Floppy tape drive").
7769 Please read also the file Documentation/ftape.txt which contains a
7770 short description of the parameters that can be set at boot or load
7773 DMA channel for the floppy disk controller used with Ftape
7775 You don't need to specify a value if the following default
7776 settings for the DMA channel are correct:
7778 <<< FC-10/FC-20: 3 >>>
7779 <<< Secondary : 2 >>>
7780 Secondary refers to a secondary FDC controller like the "high speed"
7781 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
7782 Please make sure that the setting for the IO base address
7783 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
7784 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
7785 successfully using the tape drive with another operating system then
7786 you definitely should use the same settings for the IO base that has
7787 proven to work with that other OS.
7789 Note that this menu lets you specify only the default setting for
7790 the DMA channel. The hardware configuration can be changed at boot
7791 time (when ftape is compiled into the kernel, i.e. if you specified
7792 Y to "Floppy tape drive") or module load time (i.e. if you have said M
7793 to "Floppy tape drive").
7795 Please read also the file Documentation/ftape.txt which contains a
7796 short description of the parameters that can be set at boot or load
7799 FDC FIFO Threshold before requesting DMA service
7801 Set the FIFO threshold of the FDC. If this is higher the DMA
7802 controller may serve the FDC after a higher latency time. If this is
7803 lower, fewer DMA transfers occur leading to less bus contention.
7804 You may try to tune this if ftape annoys you with "reduced data
7805 rate because of excessive overrun errors" messages. However, this
7806 doesn't seem to have too much effect.
7808 If unsure, don't touch the initial value, i.e. leave it at "8".
7810 FDC maximum data rate
7811 CONFIG_FT_FDC_MAX_RATE
7812 With some motherboard/FDC combinations ftape will not be able to
7813 run your FDC/tape drive combination at the highest available
7814 speed. If this is the case you'll encounter "reduced data rate
7815 because of excessive overrun errors" messages and lots of retries
7816 before ftape finally decides to reduce the data rate.
7818 In this case it might be desirable to tell ftape beforehand that
7819 it need not try to run the tape drive at the highest available
7820 speed. If unsure, leave this disabled, i.e. leave it at 2000
7823 MTRR control and configuration
7825 On Intel Pentium Pro and Pentium II systems the Memory Type Range
7826 Registers (MTRRs) may be used to control processor access to memory
7827 ranges. This is most useful when you have a video (VGA) card on a
7828 PCI or AGP bus. Enabling write-combining allows bus write transfers
7829 to be combined into a larger transfer before bursting over the
7830 PCI/AGP bus. This can increase performance of image write operations
7832 This option creates a /proc/mtrr file which may be used to manipulate
7833 your MTRRs. Typically the X server should use this. This should have
7834 a reasonably generic interface so that similar control registers on
7835 other processors can be easily supported.
7837 Saying Y here also fixes a problem with buggy SMP BIOSes which only
7838 set the MTRRs for the boot CPU and not the secondary CPUs. This can
7839 lead to all sorts of problems.
7841 In general you should compile this into the kernel, rather than as a
7842 loadable module, because the BIOS fix needs to be done early in the
7843 boot sequence. If you compile this as a module, the BIOS fix will be
7844 delayed until when you load the module. You do this at your own risk.
7846 See Documentation/mtrr.txt for more information.
7848 Main CPU frequency, only for DEC alpha machine
7849 CONFIG_FT_ALPHA_CLOCK
7850 On some DEC Alpha machines the CPU clock frequency cannot be
7851 determined automatically, so you need to specify it here ONLY if
7852 running a DEC Alpha, otherwise this setting has no effect.
7854 Zilog serial support
7856 This driver does not exist at this point, so you might as well say
7859 Advanced Power Management
7861 APM is a BIOS specification for saving power using several different
7862 techniques. This is mostly useful for battery powered laptops with
7863 APM compliant BIOSes. If you say Y here, the system time will be
7864 reset after a USER RESUME operation, the /proc/apm device will
7865 provide battery status information, and user-space programs will
7866 receive notification of APM "events" (e.g., battery status change).
7868 Supporting software is available; for more information, read the
7869 Battery Powered Linux mini-HOWTO, available via FTP (user:
7870 anonymous) from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini.
7872 This driver does not spin down disk drives (see the hdparm(8)
7873 manpage ("man 8 hdparm") for that), and it doesn't turn off
7874 VESA-compliant "green" monitors.
7876 This driver does not support the TI 4000M TravelMate and the ACER
7877 486/DX4/75 because they don't have compliant BIOSes. Many "green"
7878 desktop machines also don't have compliant BIOSes, and this driver
7879 will cause those machines to panic during the boot phase (typically,
7880 these machines are using a data segment of 0040, which is reserved
7881 for the Linux kernel).
7883 If you are running Linux on a laptop, you may also want to read the
7884 Linux Laptop home page on the WWW at
7885 http://www.cs.utexas.edu/users/kharker/linux-laptop/ (to browse the
7886 WWW, you need to have access to a machine on the Internet that has a
7887 program like lynx or netscape).
7889 Generally, if you don't have a battery in your machine, there isn't
7890 much point in using this driver and you should say N. If you get
7891 random kernel OOPSes or reboots that don't seem to be related to
7892 anything, try disabling/enabling this option (or disabling/enabling
7895 Some other things to try when experiencing seemingly random, "weird"
7897 1) passing the "no-hlt" option to the kernel
7898 2) switching on floating point emulation in the kernel and passing
7899 the "no387" option to the kernel
7900 3) passing the "floppy=nodma" option to the kernel
7901 4) passing the "mem=4M" option to the kernel (thereby disabling
7902 all but the first 4M of RAM)
7903 5) making sure that the CPU is not over clocked.
7904 6) reading the sig11 FAQ at http://www.bitwizard.nl/sig11/
7905 7) disabling the cache from your BIOS settings
7906 8) installing a better fan
7907 9) exchanging RAM chips
7908 10) exchanging the motherboard.
7911 CONFIG_APM_IGNORE_USER_SUSPEND
7912 This option will ignore USER SUSPEND requests. On machines with a
7913 compliant APM BIOS, you want to say N. However, on the NEC Versa M
7914 series notebooks, it is necessary to say Y because of a BIOS bug.
7916 Enable APM at boot time
7917 CONFIG_APM_DO_ENABLE
7918 Enable APM features at boot time. From page 36 of the APM BIOS
7919 specification: "When disabled, the APM BIOS does not automatically
7920 power manage devices, enter the Standby State, enter the Suspend
7921 State, or take power saving steps in response to CPU Idle calls."
7922 This driver will make CPU Idle calls when Linux is idle (unless this
7923 feature is turned off -- see "Do CPU IDLE calls", below). This
7924 should always save battery power, but more complicated APM features
7925 will be dependent on your BIOS implementation. You may need to turn
7926 this option off if your computer hangs at boot time when using APM
7927 support, or if it beeps continuously instead of suspending. Turn
7928 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
7929 T400CDT. This is off by default since most machines do fine without
7934 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
7935 On some machines, this can activate improved power savings, such as
7936 a slowed CPU clock rate, when the machine is idle. These idle calls
7937 are made after the idle loop has run for some length of time (e.g.,
7938 333 mS). On some machines, this will cause a hang at boot time or
7939 whenever the CPU becomes idle. (On machines with more than one CPU,
7940 this option does nothing.)
7942 Enable console blanking using APM
7943 CONFIG_APM_DISPLAY_BLANK
7944 Enable console blanking using the APM. Some laptops can use this to
7945 turn off the LCD backlight when the screen blanker of the Linux
7946 virtual console blanks the screen. Note that this is only used by
7947 the virtual console screen blanker, and won't turn off the backlight
7948 when using the X Window system. This also doesn't have anything to
7949 do with your VESA-compliant power-saving monitor. Further, this
7950 option doesn't work for all laptops -- it might not turn off your
7951 backlight at all, or it might print a lot of errors to the console,
7952 especially if you are using gpm.
7954 Power off on shutdown
7955 CONFIG_APM_POWER_OFF
7956 Enable the ability to power off the computer after the Linux kernel
7957 is halted. You will need software (e.g., a suitable version of the
7958 halt(8) command ("man 8 halt")) to cause the computer to power down.
7959 Recent versions of the sysvinit package available from
7960 ftp://sunsite.unc.edu/pub/Linux/system/daemons/init/ (user:
7961 anonymous) contain support for this ("halt -p" shuts down Linux and
7962 powers off the computer). As with the other APM options, this
7963 option may not work reliably with some APM BIOS implementations.
7965 Ignore multiple suspend/standby events
7966 CONFIG_APM_IGNORE_MULTIPLE_SUSPEND
7967 This option is necessary on the IBM Thinkpad 560, but should work on
7968 all other laptops. When the APM BIOS returns multiple suspend or
7969 standby events while one is already being processed they will be
7970 ignored. Without this the Thinkpad 560 has troubles with the user
7971 level daemon apmd, and with the PCMCIA package pcmcia-cs.
7973 Watchdog Timer Support
7975 If you say Y here (and to one of the following options) and create a
7976 character special file /dev/watchdog with major number 10 and minor
7977 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
7978 subsequently opening the file and then failing to write to it for
7979 longer than 1 minute will result in rebooting the machine. This
7980 could be useful for a networked machine that needs to come back
7981 online as fast as possible after a lock-up. There's both a watchdog
7982 implementation entirely in software (which can sometimes fail to
7983 reboot the machine) and a driver for hardware watchdog boards, which
7984 are more robust and can also keep track of the temperature inside
7985 your computer. For details, read Documentation/watchdog.txt in the
7988 The watchdog is usually used together with the watchdog daemon which
7989 is available via FTP (user: anonymous) from
7990 ftp://tsx-11.mit.edu/pub/linux/sources/sbin/. This daemon can also
7991 monitor NFS connections and can reboot the machine when the process
7996 Disable watchdog shutdown on close
7997 CONFIG_WATCHDOG_NOWAYOUT
7998 The default watchdog behaviour (which you get if you say N here) is
7999 to stop the timer if the process managing it closes the file
8000 /dev/watchdog. It's always remotely possible that this process might
8001 get killed. If you say Y here, the watchdog cannot be stopped once
8002 it has been started.
8006 If you have a WDT500P or WDT501P watchdog board, say Y here,
8007 otherwise N. It is not possible to probe for this board, which means
8008 that you have to set the IO port and IRQ it uses in the kernel
8009 source at the top of drivers/char/wdt.c.
8011 If you want to compile this as a module ( = code which can be
8012 inserted in and removed from the running kernel whenever you want),
8013 say M here and read Documentation/modules.txt. The module will be
8018 Saying Y here and creating a character special file /dev/temperature
8019 with major number 10 and minor number 131 ("man mknod") will give
8020 you a thermometer inside your computer: reading from
8021 /dev/temperature yields one byte, the temperature in degrees
8022 Fahrenheit. This works only if you have a WDT501P watchdog board
8027 Enable the Fan Tachometer on the WDT501. Only do this if you have a
8028 fan tachometer actually set up.
8031 CONFIG_SOFT_WATCHDOG
8032 A software monitoring watchdog. This will fail to reboot your system
8033 from some situations that the hardware watchdog will recover
8034 from. Equally it's a lot cheaper to install.
8036 This driver is also available as a module ( = code which can be
8037 inserted in and removed from the running kernel whenever you want).
8038 If you want to compile it as a module, say M here and read
8039 Documentation/modules.txt. The module will be called softdog.o.
8041 Berkshire Products PC Watchdog
8043 This is the driver for the Berkshire Products PC Watchdog card.
8044 This card simply watches your kernel to make sure it doesn't freeze,
8045 and if it does, it reboots your computer after a certain amount of
8046 time. This driver is like the WDT501 driver but for different
8047 hardware. Please read Documentation/pcwd-watchdog.txt. The PC
8048 watchdog cards can be ordered from http://www.berkprod.com. Some
8049 example rc.local files are available from ftp://ftp.bitgate.com.
8051 This driver is also available as a module ( = code which can be
8052 inserted in and removed from the running kernel whenever you want).
8053 The module is called pcwd.o. If you want to compile it as a module,
8054 say M here and read Documentation/modules.txt. Most people will say
8057 Acquire SBC Watchdog Timer
8059 This is the driver for the hardware watchdog on the PSC-6x86 Single
8060 Board Computer produced by Acquire Inc (and others). This watchdog
8061 simply watches your kernel to make sure it doesn't freeze, and if
8062 it does, it reboots your computer after a certain amount of time.
8064 This driver is like the WDT501 driver but for different hardware.
8065 This driver is also available as a module ( = code which can be
8066 inserted in and removed from the running kernel whenever you want).
8067 The module is called pscwdt.o. If you want to compile it as a module,
8068 say M here and read Documentation/modules.txt. Most people will say N.
8070 Enhanced Real Time Clock Support
8072 If you say Y here and create a character special file /dev/rtc with
8073 major number 10 and minor number 135 using mknod ("man mknod"), you
8074 will get access to the real time clock built into your
8075 computer. Every PC has such a clock built in. It can be used to
8076 generate signals from as low as 1Hz up to 8192Hz, and can also be
8077 used as a 24 hour alarm. It reports status information via the file
8078 /proc/rtc and its behaviour is set by various ioctls on
8081 People running SMP (= multiprocessor) versions of Linux should say Y
8082 here to read and set the RTC clock in a SMP compatible
8083 fashion. (They should also read Documentation/smp and
8084 Documentation/IO-APIC.txt and the SMP-FAQ on the WWW at
8085 http://www.irisa.fr/prive/mentre/smp-faq/ (to browse the WWW, you
8086 need to have access to a machine on the Internet that has a program
8087 like lynx or netscape)).
8089 If you think you have a use for such a device (such as periodic data
8090 sampling), then say Y here, and go read the file
8091 Documentation/rtc.txt for details.
8093 Tadpole ANA H8 Support
8095 The Hitachi H8/337 is a microcontroller used to deal with the power
8096 and thermal environment. If you say Y here, you will be able to
8097 communicate with it via via a character special device. If unsure,
8102 If you say Y here and create a character special file /dev/nvram
8103 with major number 10 and minor number 144 using mknod ("man mknod"),
8104 you get access to the 50 bytes of non-volatile memory in the real
8105 time clock (RTC), which is contained in every PC and most
8106 Ataris. This memory is conventionally called "CMOS RAM" on PCs and
8107 "NVRAM" on Ataris. /dev/nvram may be used to view settings there, or
8108 to change them (with some utility). It could also be used to
8109 frequently save a few bits of very important data that may not be
8110 lost over power-off and for which writing to disk is too
8111 insecure. On Atari machines, /dev/nvram is always configured and
8112 does not need to be selected.
8114 This driver is also available as a module ( = code which can be
8115 inserted in and removed from the running kernel whenever you want).
8116 The module will be called nvram.o. If you want to compile it as a
8117 module, say M here and read Documentation/modules.txt.
8121 If you have a joystick, you can say Y here to enable generic
8122 joystick support. You will also need to say Y or M to at least one
8123 of the hardware specific joystick drivers. This will make the
8124 joysticks available under /dev/jsX devices. Please read the file
8125 Documentation/joystick.txt which contains more information and the
8126 location of the joystick package that you'll need.
8128 This driver is also available as a module ( = code which can be
8129 inserted in and removed from the running kernel whenever you want).
8130 The module will be called joystick.o. If you want to compile it as a
8131 module, say M here and read Documentation/modules.txt.
8133 Classic PC analog joysticks
8135 Say Y here if you have an analog joystick or gamepad that connects
8136 to the PC gameport. This supports many different types, including
8137 joysticks with throttle control, and with CHF / FCS / 6-button
8138 extensions. For more information on how to use the driver please
8139 read Documentation/joystick.txt
8141 FPGaming and MadCatz A3D controllers
8143 Say Y here if you have an FPGaming Assasin 3D, MadCatz Panther or
8144 MadCatz Panther XL. For more information on how to use the driver
8145 please read Documentation/joystick.txt
8147 Gravis GrIP gamepads
8149 Say Y here if you have a Gravis GamePad Pro. For more information
8150 on how to use the driver please read Documentation/joystick.txt
8152 PDPI Lightning L4 gamecards
8153 CONFIG_JOY_LIGHTNING
8154 Say Y here if you have a PDPI Lightning L4 gamecard and an analog
8155 joystick or gamepad connected to it. For more information on how to
8156 use the driver please read Documentation/joystick.txt
8158 Logitech Digital joysticks
8160 Say Y here if you have a Logitech WingMan Extreme Digital,
8161 Logitech ThunderPad Digital or Logitech CyberMan 2. For more
8162 information on how to use the driver please read
8163 Documentation/joystick.txt
8165 Microsoft SideWinder, Genius Digital joysticks
8166 CONFIG_JOY_SIDEWINDER
8167 Say Y here if you have a Microsoft SideWinder 3d Pro, Microsoft
8168 SideWinder Precision Pro, Microsoft SideWinder Force Feedback Pro,
8169 Microsoft Sidewinder GamePad or Genius Flight2000 F-23 Digital. For
8170 more information on how to use the driver please read
8171 Documentation/joystick.txt
8173 ThrustMaster DirectConnect (BSP) joysticks
8174 CONFIG_JOY_THRUSTMASTER
8175 Say Y here if you have a ThrustMaster Millenium 3D Inceptor, ThrustMaster
8176 3D Rage Pad, or ThrustMaster WCS III. For more information on how to use the
8177 driver please read Documentation/joystick.txt
8179 NES, SNES, PSX, Multisystem gamepads
8181 Say Y here if you have a Nintendo Entertainment System gamepad,
8182 Super Nintendo Entertainment System gamepad, Sony PlayStation
8183 gamepad or a Multisystem - Atari, Amiga, Commodore, Amstrad CPC
8184 joystick. For more information on how to use the driver please read
8185 Documentation/joystick.txt
8187 Sega, Multisystem gamepads
8189 Say Y here if you have a Sega Master System gamepad, Sega Genesis
8190 gamepad, Sega Saturn gamepad, or a Multisystem - Atari, Amiga,
8191 Commodore, Amstrad CPC joystick. For more information on how to use
8192 the driver please read Documentation/joystick.txt
8194 TurboGraFX Multisystem joystick interface
8195 CONFIG_JOY_TURBOGRAFX
8196 Say Y here if you have the TurboGraFX interface by Steffen Schwenke, and
8197 want to use it with Multiststem - Atari, Amiga, Commodore, Amstrad CPC
8198 joystick. For more information on how to use the driver please read
8199 Documentation/joystick-parport.txt
8203 Say Y here if you have an Amiga with a digital joystick connected
8204 to it. For more information on how to use the driver please read
8205 Documentation/joystick.txt
8207 Atomwide Serial Support
8208 CONFIG_ATOMWIDE_SERIAL
8209 If you have an Atomwide Serial card for an Acorn system, say Y to
8210 this option. The driver can handle 1, 2, or 3 port cards.
8213 The Serial Port Dual Serial Port
8214 CONFIG_DUALSP_SERIAL
8215 If you have the Serial Port's dual serial card for an Acorn system,
8216 say Y to this option. If unsure, say N
8220 If you have a sound card in your computer, i.e. if it can say more
8221 than an occasional beep, say Y. Be sure to have all the information
8222 about your sound card and its configuration down (I/O port,
8223 interrupt and DMA channel), because you will be asked for it. You
8224 want to read the Sound-HOWTO, available via FTP (user: anonymous)
8225 from ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO. There is also some
8226 information in various README files in drivers/sound, esp. in
8227 Readme.cards which you should read first to find out whether your
8228 card is supported by Linux, and, if yes, which driver to use.
8230 If you have a PnP sound card and you want to configure it at boot
8231 time using the ISA PnP tools (read
8232 http://www.roestock.demon.co.uk/isapnptools/ (to browse the WWW, you
8233 need to have access to a machine on the Internet that has a program
8234 like lynx or netscape)), then you need to compile the sound card
8235 support as a module ( = code which can be inserted in and removed
8236 from the running kernel whenever you want) and load that module
8237 after the PnP configuration is finished. To do this, say M here and
8238 read Documentation/modules.txt as well as
8239 drivers/sound/Readme.modules; the module will be called sound.o.
8241 I'm told that even without a sound card, you can make your computer
8242 say more than an occasional beep, by programming the PC speaker.
8243 Kernel patches and programs to do that are in the pcsndrv package on
8244 ftp://sunsite.unc.edu/pub/Linux/kernel/patches/console/ and in the
8245 pcsp patch at http://www.imladris.demon.co.uk/pcsp/
8249 OSS is the Open Sound System suite of sound card drivers. They make
8250 sound programming easier since they provide a common API. Say Y or M
8251 here (the module will be called sound.o) if you haven't found a
8252 driver for your sound card above, then pick your driver from the
8255 Support for Aztech Sound Galaxy (non-PnP) cards
8256 CONFIG_SOUND_SGALAXY
8257 This module initializes the older non Plug and Play sound galaxy
8258 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
8259 Galaxy Washington 16.
8261 Yamaha OPL3-SA1 audio controller
8262 CONFIG_SOUND_OPL3SA1
8263 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
8264 usually built into motherboards. Read Documentation/sound/OPL3-SA
8267 ProAudioSpectrum 16 support
8269 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
8270 16 or Logitech SoundMan 16 sound card. Don't answer Y if you have
8271 some other card made by Media Vision or Logitech since they are not
8274 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
8276 Answer Y if you have an original Sound Blaster card made by
8277 Creative Labs or a 100% hardware compatible clone (like the
8278 Thunderboard or SM Games). If your card was in the list of supported
8279 cards look at the card specific instructions in the
8280 drivers/sound/Readme.cards file before answering this question. For
8281 an unknown card you may answer Y if the card claims to be
8282 Sound Blaster-compatible.
8284 You can say M here to compile this driver as a module; the module is
8287 You should also say Y here for cards based on the Avance Logic
8288 ALS-007 chip (read Documentation/sound/ALS007) and for ESS1688 and
8289 ESS1868 cards (read Documentation/sound/ESS1868). If you have an SB
8290 AWE 32 or SB AWE 64, say Y here and also to "Additional lowlevel
8291 drivers" and to "SB32/AWE support" below. If you have an IBM Mwave
8292 card, say Y here and read Documentation/sound/mwave.
8294 Please read Documentation/sound/Soundblaster.
8296 Generic OPL2/OPL3 FM synthesizer support
8298 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
8299 Answering Y is usually a safe and recommended choice, however some
8300 cards may have software (TSR) FM emulation. Enabling FM support with
8301 these cards may cause trouble (I don't currently know of any such
8304 Please read the file Documentation/sound/OPL3 if your card has an
8310 #Loopback MIDI device support
8313 ### somebody please fill this in.
8316 Gravis Ultrasound support
8318 Say Y here for any type of Gravis Ultrasound card, including
8319 the GUS or GUS MAX. See also Documentation/sound/ultrasound for
8320 more information on configuring this card with modules.
8322 MPU-401 support (NOT for SB16)
8324 Be careful with this question. The MPU401 interface is supported by
8325 all sound cards. However, some natively supported cards have their
8326 own driver for MPU401. Enabling this MPU401 option with these cards
8327 will cause a conflict. Also, enabling MPU401 on a system that
8328 doesn't really have a MPU401 could cause some trouble. If your card
8329 was in the list of supported cards, look at the card specific
8330 instructions in the drivers/sound/Readme.cards file. It's safe to
8331 answer Y if you have a true MPU401 MIDI interface card.
8333 6850 UART Midi support
8334 CONFIG_SOUND_UART6850
8335 This option enables support for MIDI interfaces based on the 6850
8336 UART chip. This interface is rarely found on sound cards. It's safe
8337 to answer N to this question.
8339 PSS (AD1848, ADSP-2115, ESC614) support
8341 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
8342 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
8343 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
8344 how to compile it into the kernel or as a module see the file
8345 Documentation/sound/PSS.
8347 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
8349 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
8350 cards if they have master volume, bass, treble, and you can't
8351 control it under Linux. If you answer N for Beethoven ADSP-16, you
8352 can't control master volume, bass, treble and synth volume.
8354 If you said M to "PSS support" above, you may enable or disable this
8355 PSS mixer with the module parameter pss_mixer. For more information
8356 see the file Documentation/sound/PSS.
8358 Have DSPxxx.LD firmware file
8359 CONFIG_PSS_HAVE_BOOT
8360 If you have the DSPxxx.LD file or SYNTH.LD file for you card, answer
8361 Y to include this file. Without this file the synth device (OPL) may
8364 Full pathname of DSPxxx.LD firmware file
8365 CONFIG_PSS_BOOT_FILE
8366 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
8369 16 bit sampling option of GUS (_NOT_ GUS MAX)
8371 Answer Y if you have installed the 16 bit sampling daughtercard on
8372 your GUS. Answer N if you have a GUS MAX, since saying Y here
8373 disables GUS MAX support.
8377 Answer Y only if you have a Gravis Ultrasound MAX.
8379 Microsoft Sound System support
8381 Again think carefully before answering Y to this question. It's
8382 safe to answer Y if you have the original Windows Sound System card
8383 made by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may
8384 answer Y in case your card is NOT among these:
8386 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
8387 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
8388 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
8389 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
8390 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
8391 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
8392 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
8393 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
8394 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
8395 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
8396 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
8397 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
8398 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
8400 For cards having native support in VoxWare, consult the card
8401 specific instructions in drivers/sound/Readme.cards. Some drivers
8402 have their own MSS support and saying Y to this option will cause a
8405 Ensoniq Soundscape support
8407 Answer Y if you have a sound card based on the Ensoniq SoundScape
8408 chipset. Such cards are being manufactured at least by Ensoniq, Spea
8409 and Reveal (Reveal makes also other cards).
8411 MediaTriX AudioTriX Pro support
8413 Answer Y if you have the AudioTriX Pro sound card manufactured
8416 Have TRXPRO.HEX firmware file
8417 CONFIG_TRIX_HAVE_BOOT
8418 The MediaTrix AudioTrix Pro has an on-board microcontroller which
8419 needs to be initialized by downloading the code from the file
8420 TRXPRO.HEX in the DOS driver directory. If you don't have the
8421 TRXPRO.HEX file handy you may skip this step. However, the SB and
8422 MPU-401 modes of AudioTrix Pro will not work without this file!
8424 Full pathname of TRXPRO.HEX firmware file
8425 CONFIG_TRIX_BOOT_FILE
8426 Enter the full pathname of your TRXPRO.HEX file, starting from /.
8428 Support for OPTi MAD16 and/or Mozart based cards
8430 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
8431 82C928 or 82C929 or 82C931) audio interface chip. For the 82C931,
8432 please read drivers/sound/README.C931. These chips are currently
8433 quite common so it's possible that many no-name cards have one of
8434 them. In addition the MAD16 chip is used in some cards made by known
8435 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
8436 and Diamond (latest ones). Note however that the Tropez sound cards
8437 have their own driver; if you have one of those, say N here and Y or
8438 M to "Full support for Turtle Beach WaveFront", below.
8440 See also Documentation/sound/Opti and Documentation/sound/MAD16 for
8441 more information on setting these cards up as modules.
8443 Full support for Turtle Beach WaveFront synth/sound cards
8444 CONFIG_SOUND_WAVEFRONT
8445 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
8446 and read the files Documentation/sound/Wavefront and
8447 Documentation/sound/Tropez+.
8449 Support MIDI in older MAD16 based cards (requires SB)
8450 CONFIG_MAD16_OLDCARD
8451 Answer Y (or M) if you have an older card based on the C928
8452 or Mozart chipset and you want to have MIDI support. If you
8453 enable this option you also need to enable support for Sound Blaster.
8455 Support for Crystal CS4232 based (PnP) cards
8457 Say Y here if you have a card based on the Crystal CS4232 chip set,
8458 which uses its own Plug and Play protocol. See
8459 Documentation/sound/CS4232 for more information on configuring this
8462 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
8464 Say Y here if you have a Turtle Beach Wave Front, Maui, or
8467 Have OSWF.MOT firmware file
8468 CONFIG_MAUI_HAVE_BOOT
8469 Turtle Beach Maui and Tropez sound cards have a microcontroller which
8470 needs to be initialized prior to use. OSWF.MOT is a file distributed
8471 with the card's DOS/Windows drivers. Answer Y if you have this file.
8473 Full pathname of OSWF.MOT firmware file
8474 CONFIG_MAUI_BOOT_FILE
8475 Enter the full pathname of your OSWF.MOT file, starting from /.
8477 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
8478 CONFIG_SOUND_MSNDCLAS
8479 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
8480 Monterey (not for the Pinnacle or Fiji). See
8481 Documentation/sound/MultiSound for important information about this
8484 Full pathname of MSNDINIT.BIN firmware file
8485 CONFIG_MSNDCLAS_INIT_FILE
8486 The MultiSound cards have two firmware files which are required for
8487 operation, and are not currently included. These files can be
8488 obtained from Turtle Beach. See Documentation/sound/MultiSound for
8489 information on how to obtain this.
8491 Full pathname of MSNDPERM.BIN firmware file
8492 CONFIG_MSNDCLAS_PERM_FILE
8493 The MultiSound cards have two firmware files which are required for
8494 operation, and are not currently included. These files can be
8495 obtained from Turtle Beach. See Documentation/sound/MultiSound for
8496 information on how to obtain this.
8498 Support for Turtle Beach MultiSound Pinnacle, Fiji
8499 CONFIG_SOUND_MSNDPIN
8500 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
8501 See Documentation/sound/MultiSound for important information about
8504 Full pathname of PNDSPINI.BIN firmware file
8505 CONFIG_MSNDPIN_INIT_FILE
8506 The MultiSound cards have two firmware files which are required for
8507 operation, and are not currently included. These files can be
8508 obtained from Turtle Beach. See Documentation/sound/MultiSound for
8509 information on how to obtain this.
8511 Full pathname of PNDSPERM.BIN firmware file
8512 CONFIG_MSNDPIN_PERM_FILE
8513 The MultiSound cards have two firmware files which are required for
8514 operation, and are not currently included. These files can be
8515 obtained from Turtle Beach. See Documentation/sound/MultiSound for
8516 information on how to obtain this.
8518 MSND Pinnacle have S/PDIF I/O
8519 CONFIG_MSNDPIN_DIGITAL
8520 If you have the S/PDIF daughterboard for the Pinnacle or Fiji, say Y
8521 here; otherwise, say N. If you have this, you will be able to play
8522 and record from the S/PDIF port (digital signal). See
8523 Documentation/sound/MultiSound for information on how to make use of
8526 MSND Pinnacle non-PnP Mode
8527 CONFIG_MSNDPIN_NONPNP
8528 The Pinnacle and Fiji card resources can be configured either with
8529 PnP, or through a configuration port. For the Pinnacle,
8530 configuration in non-PnP mode allows use of the IDE and joystick
8531 peripherals on the card as well, since they do not show up when the
8532 card is in PnP mode. Specifying zero for any resource of a device
8533 will disable the device. If you are running the card in PnP mode,
8534 you must say N here and use isapnptools to configure the card's
8537 MSND Pinnacle config port
8539 This is the port which the Pinnacle and Fiji uses to configure
8540 the card's resources when not in PnP mode. If your card is in
8541 PnP mode, then be sure to say N to the previous option,
8542 CONFIG_MSNDPIN_NONPNP.
8544 MSND buffer size (kB)
8545 CONFIG_MSND_FIFOSIZE
8546 Configures the size of each audio buffer, in kilobytes, for
8547 recording and playing in the MultiSound drivers (both the Classic
8548 and Pinnacle). Larger values reduce the chance of data overruns at
8549 the expense of overall latency. If unsure, use the default.
8551 /dev/dsp and /dev/audio support
8553 Answering N disables /dev/dsp and /dev/audio, the A/D and D/A
8554 converter devices. Answer N only if you know you will not need
8555 the option. They are usually required. Answer Y.
8557 MIDI interface support
8559 Answering N disables /dev/midixx devices and access to any MIDI
8560 ports using /dev/sequencer and /dev/music. This option also affects
8561 any MPU401 and/or General MIDI compatible devices. Answer Y.
8563 FM synthesizer (YM3812/OPL-3) support
8565 Answer Y here, unless you know you will not need the option.
8569 This is support for the sound cards on Sun workstations. The code
8570 does not exist yet, so you might as well say N here.
8572 Additional low level drivers
8573 CONFIG_LOWLEVEL_SOUND
8574 If you need additional low level sound drivers which have not yet
8575 appeared, say Y. The answer to this question does not directly
8576 affect the kernel; saying Y will simply cause this configure script
8577 to present you with more options. If unsure, say Y.
8579 ACI mixer (miroPCM12)
8581 Audio Command Interface (ACI) driver. ACI is a protocol used to
8582 communicate with the microcontroller on some sound cards produced
8583 by miro, e.g. the miroSOUND PCM12 and PCM20. The main function
8584 of the ACI is to control the mixer and to get a product
8585 identification. This Voxware ACI driver currently only supports
8586 the ACI functions on the miroSOUND PCM12 card. On the PCM20, ACI
8587 also controls the radio tuner on this card, however this is not
8588 yet supported in this software.
8592 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
8593 similar sound card. See drivers/sound/lowlevel/README.awe,
8594 Documentation/sound/AWE32 and the Soundblaster-AWE mini-HOWTO,
8595 available via FTP (user: anonymous) from
8596 ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/mini for more info.
8598 Gallant's Audio Excel DSP 16 support (SC-6000 and SC-6600)
8600 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
8601 driver supports Audio Excel DSP 16 but not the III nor PnP versions
8604 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
8605 a Microsoft Sound System card, so you should have said Y to either
8606 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
8607 or "Microsoft Sound System support", above, and you need to answer
8608 the "MSS emulation" and "SBPro emulation" questions below
8609 accordingly. You should say Y to one and only one of these two
8612 Read the drivers/sound/lowlevel/README.aedsp16 file and the head of
8613 drivers/sound/lowlevel/aedsp16.c as well as
8614 Documentation/sound/AudioExcelDSP16 to get more information about
8615 this driver and its configuration.
8617 SC-6600 based audio cards (new Audio Excel DSP 16)
8619 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
8620 16 cards. Find in the manual the FCC ID of your audio card and
8621 answer Y if you have an SC6600 DSP.
8623 Audio Excel DSP 16 (MSS emulation)
8625 Answer Y if you want your audio card to emulate Microsoft Sound
8626 System. You should then say Y to "Microsoft Sound System support"
8627 and say N to "Audio Excel DSP 16 (SBPro emulation)".
8629 Audio Excel DSP 16 (SBPro emulation)
8630 CONFIG_AEDSP16_SBPRO
8631 Answer Y if you want your audio card to emulate Sound Blaster Pro.
8632 You should then say Y to "100% Sound Blaster compatibles
8633 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
8636 Ensoniq ES1370 based PCI sound cards
8638 Say Y or M if you have a PCI sound card utilizing the Ensoniq
8639 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
8640 out if your sound card uses an ES1370 without removing your
8641 computer's cover, use lspci -n and look for the PCI ID
8642 1274:5000. Since Ensoniq was bought by Creative Labs,
8643 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
8644 This driver differs slightly from OSS/Free, so PLEASE READ
8645 Documentation/sound/es1370.
8647 Ensoniq ES1371 based PCI sound cards
8649 Say Y or M if you have a PCI sound card utilizing the Ensoniq
8650 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
8651 your sound card uses an ES1371 without removing your computer's
8652 cover, use lspci -n and look for the PCI ID 1274:1371. Since
8653 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
8654 models are either ES1370 or ES1371 based. This driver differs
8655 slightly from OSS/Free, so PLEASE READ Documentation/sound/es1371.
8657 S3 SonicVibes based PCI sound cards
8658 CONFIG_SOUND_SONICVIBES
8659 Say Y or M if you have a PCI sound card utilizing the S3
8660 SonicVibes chipset. To find out if your sound card uses a
8661 SonicVibes chip without removing your computer's cover, use
8662 lspci -n and look for the PCI ID 5333:CA00. This driver
8663 differs slightly from OSS/Free, so PLEASE READ
8664 Documentation/sound/sonicvibes.
8666 Magic System Request Key support
8668 If you say Y here, you will have some control over the system even
8669 if the system crashes for example during kernel debugging (e.g., you
8670 will be able to flush the buffer cache to disk, reboot the system
8671 immediately or dump some status information). This is accomplished
8672 by pressing various keys while holding SysRq (Alt+PrintScreen). The
8673 keys are documented in Documentation/sysrq.txt. Don't say Y unless
8674 you really know what this hack does.
8678 ISDN ("Integrated Services Digital Networks", called RNIS in France)
8679 is a special type of fully digital telephone service; it's mostly
8680 used to connect to your Internet service provider (with SLIP or
8681 PPP). The main advantage is that the speed is higher than ordinary
8682 modem/telephone connections, and that you can have voice
8683 conversations while downloading stuff. It only works if your
8684 computer is equipped with an ISDN card and both you and your service
8685 provider purchased an ISDN line from the phone company. For
8686 details, read http://alumni.caltech.edu/~dank/isdn/ on the WWW. (To
8687 browse the WWW, you need to have access to a machine on the Internet
8688 that has a program like lynx or netscape.)
8690 This driver allows you to use an ISDN-card for networking
8691 connections and as dialin/out device. The isdn-tty's have a built in
8692 AT-compatible modem emulator. Network devices support autodial,
8693 channel-bundling, callback and caller-authentication without having
8694 a daemon running. A reduced T.70 protocol is supported with tty's
8695 suitable for German BTX. On D-Channel, the protocols EDSS1
8696 (Euro-ISDN) and 1TR6 (German style) are supported. See
8697 Documentation/isdn/README for more information.
8699 If you want to compile the ISDN code as a module ( = code which can
8700 be inserted in and removed from the running kernel whenever you
8701 want), say M here and read Documentation/modules.txt. The module
8702 will be called isdn.o. If unsure, say N.
8704 Support synchronous PPP
8706 Over digital connections such as ISDN, there is no need to
8707 synchronize sender and recipient's clocks with start and stop bits
8708 as is done over analog telephone lines. Instead, one can use
8709 "synchronous PPP". Saying Y here will include this protocol. This
8710 protocol is used by Cisco and Sun for example. So you want to say Y
8711 here if the other end of your ISDN connection supports it. You will
8712 need a special version of pppd (called ipppd) for using this
8713 feature. See Documentation/isdn/README.syncppp and
8714 Documentation/isdn/syncPPP.FAQ for more information.
8716 Support generic MP (RFC 1717)
8718 With synchronous PPP enabled, it is possible to increase throughput
8719 by bundling several ISDN-connections, using this protocol. See
8720 Documentation/isdn/README.syncppp for more information.
8722 Use VJ-compression with synchronous PPP
8724 This enables Van Jacobson header compression for synchronous PPP.
8725 Say Y if the other end of the connection supports it.
8727 Support audio via ISDN
8729 If you say Y here, the modem-emulator will support a subset of the
8730 EIA Class 8 Voice commands. Using a getty with voice-support
8731 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
8732 with the ISDN utility package for example), you will be able to use
8733 your Linux box as an ISDN-answering machine. Of course, this must be
8734 supported by the lowlevel driver also. Currently, the HiSax driver
8735 is the only voice-supporting driver. See
8736 Documentation/isdn/README.audio for more information.
8738 X.25 PLP on top of ISDN (EXPERIMENTAL)
8740 This experimental feature provides the X.25 protocol over ISDN
8741 connections. See Documentation/isdn/README.x25 for more information
8742 if you are thinking about using this.
8744 ICN 2B and 4B support
8746 This enables support for two kinds of ISDN-cards made by a German
8747 company called ICN. 2B is the standard version for a single ISDN
8748 line with two B-channels, 4B supports two ISDN lines. For running
8749 this card, additional firmware is necessary, which has to be
8750 downloaded into the card using a utility which is distributed
8751 separately. See Documentation/isdn/README and README.icn for more
8754 If you want to compile this as a module ( = code which can be
8755 inserted in and removed from the running kernel whenever you want),
8756 say M here and read Documentation/modules.txt. The module will be
8760 CONFIG_ISDN_DRV_LOOP
8761 This driver provides a virtual ISDN card. Its primary purpose is
8762 testing of linklevel features or configuration without getting
8763 charged by your service-provider for lots of phone calls.
8764 You need will need the loopctrl utility from the latest isdn4k-utils
8765 package to set up this driver.
8767 HiSax SiemensChipSet driver support
8768 CONFIG_ISDN_DRV_HISAX
8769 This is a driver supporting the Siemens chipset on various
8770 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
8771 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
8774 HiSax is just the name of this driver, not the name of any hardware.
8776 If you have a card with such a chipset, you should say Y here and
8777 also to the configuration option of the driver for your particular
8780 If you want to compile this as a module ( = code which can be
8781 inserted in and removed from the running kernel whenever you want),
8782 say M here and read Documentation/modules.txt. The module will be
8783 called hisax.o. See Documentation/isdn/README.HiSax for more
8784 information on using this driver.
8786 HiSax Support for Teles 16.0/8.0
8788 This enables HiSax support for the Teles ISDN-cards S0-16.0,
8789 S0-8 and many compatibles.
8790 See Documentation/isdn/README.HiSax on how to configure it
8791 using the different cards, a different D-channel protocol, or
8792 non-standard IRQ/port/shmem settings.
8794 HiSax Support for Teles 16.3 or PNP or PCMCIA
8796 This enables HiSax support for the Teles ISDN-cards S0-16.3
8797 the Teles/Creatix PnP and the Teles PCMCIA.
8798 See Documentation/isdn/README.HiSax on how to configure it
8799 using the different cards, a different D-channel protocol, or
8800 non-standard IRQ/port settings.
8802 HiSax Support for Teles 16.3c
8803 CONFIG_HISAX_TELES3C
8804 This enables HiSax support for the Teles ISDN-cards 16.3c.
8805 See Documentation/isdn/README.HiSax on how to configure it
8806 using the different cards, a different D-channel protocol, or
8807 non-standard IRQ/port settings.
8809 HiSax Support for AVM A1 (Fritz)
8811 This enables HiSax support for the AVM A1 (aka "Fritz").
8812 See Documentation/isdn/README.HiSax on how to configure it
8813 using the different cards, a different D-channel protocol, or
8814 non-standard IRQ/port settings.
8816 HiSax Support for Elsa ISA cards
8818 This enables HiSax support for the Elsa Mircolink ISA cards,
8819 for the Elsa Quickstep series cards and Elsa PCMCIA.
8820 See Documentation/isdn/README.HiSax on how to configure it
8821 using the different cards, a different D-channel protocol, or
8822 non-standard IRQ/port settings.
8824 HiSax Support for ITK ix1-micro Revision 2
8825 CONFIG_HISAX_IX1MICROR2
8826 This enables HiSax support for the ITK ix1-micro Revision 2 card.
8827 See Documentation/isdn/README.HiSax on how to configure it
8828 using the different cards, a different D-channel protocol, or
8829 non-standard IRQ/port settings.
8831 HiSax Support for Eicon.Diehl Diva cards
8832 CONFIG_HISAX_DIEHLDIVA
8833 This enables HiSax support for the Eicon.Diehl Diva none PRO versions
8836 See Documentation/isdn/README.HiSax on how to configure it
8837 using the different cards, a different D-channel protocol, or
8838 non-standard IRQ/port settings.
8840 HiSax Support for ASUSCOM cards
8841 CONFIG_HISAX_ASUSCOM
8842 This enables HiSax support for the AsusCom and their OEM versions
8845 See Documentation/isdn/README.HiSax on how to configure it
8846 using the different cards, a different D-channel protocol, or
8847 non-standard IRQ/port settings.
8849 HiSax Support for TELEINT cards
8850 CONFIG_HISAX_TELEINT
8851 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
8852 See Documentation/isdn/README.HiSax on how to configure it
8853 using the different cards, a different D-channel protocol, or
8854 non-standard IRQ/port settings.
8856 HiSax Support for Sedlbauer speed card/win-star
8857 CONFIG_HISAX_SEDLBAUER
8858 This enables HiSax support for the Sedlbauer passive ISDN cards.
8859 See Documentation/isdn/README.HiSax on how to configure it
8860 using the different cards, a different D-channel protocol, or
8861 non-standard IRQ/port settings.
8863 HiSax Support for USR Sportster internal TA
8864 CONFIG_HISAX_SPORTSTER
8865 This enables HiSax support for the USR Sportster internal TA card.
8866 See Documentation/isdn/README.HiSax on how to configure it using a
8867 different D-channel protocol, or non-standard IRQ/port settings.
8869 HiSax Support for MIC card
8871 This enables HiSax support for the ITH MIC card. See
8872 Documentation/isdn/README.HiSax on how to configure it using a
8873 different D-channel protocol, or non-standard IRQ/port settings.
8875 HiSax Support for NETjet card
8877 This enables HiSax support for the NetJet from Traverse
8878 Technologies. See Documentation/isdn/README.HiSax on how to
8879 configure it using a different D-channel protocol, or non-standard
8882 HiSax Support for Niccy PnP/PCI card
8884 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI. See
8885 Documentation/isdn/README.HiSax on how to configure it using a
8886 different D-channel protocol, or non-standard IRQ/port settings.
8888 HiSax Support for Am7930 (EXPERIMENTAL)
8889 CONFIG_HISAX_AMD7930
8890 This enables HiSax support for the AMD7930 chips on some SPARCs.
8891 This code is not finished yet.
8893 HiSax Support for EURO/DSS1
8895 Say Y or N according to the D-channel protocol which your local
8896 telephone service company provides.
8898 NOTE: If you say Y here and you have only one ISDN card installed,
8899 you cannot say Y to "HiSax Support for German 1TR6", below. And vice
8902 Support for German tariff info
8904 If you want that the HiSax hardware driver sends messages to the
8905 upper level of the isdn code on each AOCD (Advice Of Charge, During
8906 the call -- transmission of the fee information during a call) and on
8907 each AOCE (Advice Of Charge, at the End of the call -- transmission
8908 of fee information at the end of the call), say Y here. This works
8911 Support for Australian Microlink service (not for std. EURO)
8913 If you are in Australia and connected to the Microlink telephone
8914 network, enable this, because there are little differences in
8917 Please don't enable this in other countries.
8919 HiSax Support for US/NI-1 (not released yet)
8921 Say Y or N according to the D-channel protocol which your local
8922 telephone service company provides.
8924 HiSax Support for German 1TR6
8926 Say Y or N according to the D-channel protocol which your local
8927 telephone service company provides.
8929 NOTE: If you say Y here and you have only one ISDN card installed,
8930 you cannot say Y to "HiSax Support for EURO/DSS1", above. And vice
8934 CONFIG_ISDN_DRV_PCBIT
8935 This enables support for the PCBIT ISDN-card. This card is
8936 manufactured in Portugal by Octal. For running this card, additional
8937 firmware is necessary, which has to be downloaded into the card
8938 using a utility which is distributed separately. See
8939 Documentation/isdn/README and Documentation/isdn/README.pcbit for
8942 If you want to compile this as a module ( = code which can be
8943 inserted in and removed from the running kernel whenever you want),
8944 say M here and read Documentation/modules.txt. The module will be
8947 Spellcaster support (EXPERIMENTAL)
8949 This enables support for the Spellcaster BRI ISDN boards. This
8950 driver currently builds only in a modularized version ( = code which
8951 can be inserted in and removed from the running kernel whenever you
8952 want, details in Documentation/modules.txt); the module will be
8953 called sc.o. See Documentation/isdn/README.sc and
8954 http://www.spellcast.com for more information (to browse the WWW,
8955 you need to have access to a machine on the Internet that has a
8956 program like lynx or netscape).
8958 AVM-B1 with CAPI2.0 support
8959 CONFIG_ISDN_DRV_AVMB1
8960 This enables support for the AVM B1 ISDN networking cards. In
8961 addition, a CAPI (Common ISDN Application Programming Interface, a
8962 standard making it easy for programs to access ISDN hardware, see
8963 http://www.capi.org/; to browse the WWW, you need to have access to
8964 a machine on the Internet that has a program like lynx or netscape)
8965 interface for this card is provided. In order to use this card,
8966 additional firmware is necessary, which has to be downloaded into
8967 the card using a utility which is distributed separately. Please
8968 read the file Documentation/isdn/README.avmb1.
8970 This code is also available as a module ( = code which can be
8971 inserted in and removed from the running kernel whenever you want).
8972 The module will be called avmb1.o. If you want to compile it as a
8973 module, say M here and read Documentation/modules.txt.
8975 Verbose reason code reporting (kernel size +=7K)
8976 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
8977 If you say Y here, the AVM B1 driver will give verbose reasons for
8978 disconnecting. This will increase the size of the kernel by 7K. If
8981 IBM Active 2000 support (EXPERIMENTAL)
8982 CONFIG_ISDN_DRV_ACT2000
8983 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
8984 this card, additional firmware is necessary, which has to be loaded
8985 into the card using a utility which is part of the latest
8986 isdn4k-utils package. Please read the file
8987 Documentation/isdn/README.act2000 for more information.
8989 Support for AP1000 multicomputer
8991 This enables support for a SPARC based parallel multi-computer
8992 called AP1000+. For details on our efforts to port Linux to this
8993 machine see http://cap.anu.edu.au/cap/projects/linux (to browse the
8994 WWW, you need to have access to a machine on the Internet that has a
8995 program like lynx or netscape) or mail to hackers@cafe.anu.edu.au
8997 Support for Sun4 architecture
8999 Say Y here if, and only if, your machine is a Sun4. Note that
9000 a kernel compiled with this option will run only on Sun4.
9001 (And the current version will probably work only on sun4/330.)
9003 SPARC ESP SCSI support
9005 This is the driver for the Sun ESP SCSI host adapter. The ESP
9006 chipset is present in most SPARC-based computers.
9008 SPARC /dev/openprom compatibility driver
9009 CONFIG_SUN_OPENPROMIO
9010 This driver provides user programs with an interface to the SPARC
9011 PROM device tree. The driver implements a SunOS-compatible
9012 interface and a NetBSD-compatible interface.
9014 If you want to compile this as a module ( = code which can be
9015 inserted in and removed from the running kernel whenever you want),
9016 say M and read Documentation/modules.txt. If unsure, say Y.
9018 #Mostek real time clock support
9019 #CONFIG_SUN_MOSTEK_RTC
9021 #Siemens SAB82532 serial support
9024 ### Please someone fill these in.
9028 # m68k-specific kernel options
9029 # Documented by Chris Lawrence <quango@themall.net> et al.
9033 This option enables support for the Amiga series of computers. If
9034 you plan to use this kernel on an Amiga, say Y here and browse the
9035 material available in Documentation/m68k; otherwise say N.
9039 This option enables support for the 68000-based Atari series of
9040 computers (including the TT, Falcon and Medusa). If you plan to use
9041 this kernel on an Atari, say Y here and browse the material
9042 available in Documentation/m68k; otherwise say N.
9046 This option enables support for the Hades Atari clone. If you plan to
9047 use this kernel on a Hades, say Y here; otherwise say N.
9051 This option enables support for the Apple Macintosh series of
9052 computers (yes, there is experimental support now, at least for part
9055 Say N unless you're willing to code the remaining necessary support.
9058 # CONFIG_APOLLO, etc. coming soon (?)
9062 If you anticipate running this kernel on a computer with a MC68020
9063 processor, say Y. Otherwise, say N. Note that the 68020 requires a
9064 68851 MMU (= memory management unit) to run Linux/m68k.
9068 If you anticipate running this kernel on a computer with a MC68030
9069 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
9070 work, as it does not include an MMU (= memory management unit).
9074 If you anticipate running this kernel on a computer with a MC68LC040
9075 or MC68040 processor, say Y. Otherwise, say N. Note that an
9076 MC68EC040 will not work, as it does not include an MMU (= memory
9079 Use -m68040 flag for 68040 specific optimizations
9081 If you will only be running this kernel on a 68040-series processor,
9082 this will make the kernel run somewhat faster. However, it will no
9083 longer run on a 68020 or 68030, no matter whether you included 68020
9084 and 68030 support or not. Say N unless the only processor you are
9085 compiling support for is the 68040 (or 68LC040).
9089 If you anticipate running this kernel on a computer with a MC68060
9090 processor, say Y. Otherwise, say N.
9092 Use -m68060 flag for 68060 specific optimizations
9094 If you will only be running this kernel on a 68060-series processor,
9095 this will make the kernel run somewhat faster. However, it will no
9096 longer run on a 68020, 68030 or 68040, no matter whether you
9097 included support for those processors or not. Say N unless the only
9098 processor you are compiling support for is the 68060.
9100 Advanced processor options
9102 This gives you access to some advanced options for the CPU. The
9103 defaults should be fine for most users, but these options may make
9104 it possible for you to improve performance somewhat if you know what
9105 you are doing. Most users should say N to this question.
9107 Use read-modify-write instructions
9109 This allows to use certain instructions that work with indivisible
9110 read-modify-write bus cycles. While this is faster than the
9111 workaround of disabling interrupts, it can conflict with DMA
9112 ( = direct memory access) on many Amiga systems, and it is also said
9113 to destabilize other machines. It is very likely that this will
9114 cause serious problems on any Amiga or Atari Medusa if set. The only
9115 configuration where it should work are 68030-based Ataris, where it
9116 apparently improves performance. But you've been warned! Unless you
9117 really know what you are doing, say N. Try Y only if you're quite
9120 Amiga AutoConfig Identification
9122 This enables support for automatic identification of Amiga expansion
9123 cards that obey the AutoConfig(tm) specification.
9124 Say Y if you want your expansion cards to be identified on bootup;
9125 it will enlarge your kernel by about 10KB. The identification
9126 information is also available through /proc/zorro (say Y to
9127 "/proc filesystem support"!).
9129 Note that even if you say N here, you can still use your expansion
9130 cards. If in doubt, say Y.
9132 Amiga OCS chipset support
9134 This enables support for the original Agnus and Denise video chips,
9135 found in the Amiga 1000 and most A500's and A2000's. If you intend
9136 to run Linux on any of these systems, say Y; otherwise say N.
9138 Amiga ECS chipset support
9140 This enables support for the Enhanced Chip Set, found in later
9141 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
9142 you intend to run Linux on any of these systems, say Y; otherwise
9145 Amiga AGA chipset support
9147 This enables support for the Advanced Graphics Architecture (also
9148 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
9149 and CD32. If you intend to run Linux on any of these systems, say Y;
9152 Amiga GSP (TMS340x0) support
9154 Include support for Amiga graphics cards that use the Texas
9155 Instruments TMS340x0 GSP (= graphics signal processor) chips. Say Y
9156 if you want to use a DMI Resolver or Commodore A2410 (Lowell)
9157 graphics card on an Amiga; otherwise, say N.
9159 DMI Resolver support
9161 Include support in the kernel for the DMI Resolver graphics card. If
9162 you have one, say Y; otherwise, say N.
9166 Include support in the kernel for the Commodore/University of Lowell
9167 A2410 graphics card. If you have one, say Y; otherwise, say N.
9169 Amiga Zorro II ramdisk support
9171 This enables support for using Chip RAM and Zorro II RAM as a
9172 ramdisk or as a swap partition. Say Y if you want to include this
9173 driver in the kernel. This driver is also available as a module
9174 ( = code which can be inserted in and removed from the running
9175 kernel whenever you want). The module is called z2ram.o. If you want
9176 to compile it as a module, say M here and read
9177 Documentation/modules.txt.
9179 Atari ST-RAM swap support
9181 This enables support for using (parts of) ST-RAM as swap space,
9182 instead of as normal system memory. This can first enhance system
9183 performance if you have lots of alternate RAM (compared to the size
9184 of ST-RAM), because executable code always will reside in faster
9185 memory. ST-RAM will remain as ultra-fast swap space. On the other
9186 hand, it allows much improved dynamic allocations of ST-RAM buffers
9187 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
9188 sound). The probability that such allocations at module load time
9189 fail is drastically reduced.
9193 This enables support for the Atari ACSI interface. The driver
9194 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
9195 be switched to that mode. Due to the ACSI command format, only disks
9196 up to 1 GB are supported. Special support for certain ACSI to SCSI
9197 adapters, which could relax that, isn't included yet. The ACSI
9198 driver is also the basis for certain other drivers for devices
9199 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
9200 Ethernet, and PAMsNet Ethernet. If you want to use one of these
9201 devices, you need ACSI support, too.
9203 This driver is also available as a module ( = code which can be
9204 inserted in and removed from the running kernel whenever you want).
9205 The module will be called acsi.o.
9207 Probe all LUNs on each ACSI device
9208 CONFIG_ACSI_MULTI_LUN
9209 If you have a ACSI device that supports more than one LUN (Logical
9210 Unit Number), e.g. a CD jukebox, you should say Y here so that all
9211 will be found by the ACSI driver. An ACSI device with multiple LUNs
9212 acts logically like multiple ACSI devices. The vast majority of ACSI
9213 devices have only one LUN, and so most people can say N here and
9214 should in fact do so, because it is safer.
9216 Atari SLM laser printer support
9218 If you have an Atari SLM laser printer, say Y to include support for
9219 it in the kernel. Otherwise, say N. This driver is also available as
9220 a module ( = code which can be inserted in and removed from the
9221 running kernel whenever you want). The module will be called
9222 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
9223 problems due to that fact!
9225 A3000 WD33C93A support
9227 If you have an Amiga 3000 and have SCSI devices connected to the
9228 built-in SCSI controller, say Y. Otherwise, say N. This driver is
9229 also available as a module ( = code which can be inserted in and
9230 removed from the running kernel whenever you want). The module is
9231 called wd33c93.o. If you want to compile it as a module, say M here
9232 and read Documentation/modules.txt.
9234 A2091 WD33C93A support
9236 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
9237 say N. This driver is also available as a module ( = code which can
9238 be inserted in and removed from the running kernel whenever you
9239 want). The module is called wd33c93.o. If you want to compile it as
9240 a module, say M here and read Documentation/modules.txt.
9242 GVP Series II WD33C93A support
9244 If you have a Great Valley Products Series II SCSI controller, say
9245 Y. Also say Y if you have a later model of GVP SCSI controller
9246 (such as the GVP A4008 or a Combo board). Otherwise, say N.
9247 This driver does NOT work for the T-Rex series of accelerators from
9250 This driver is also available as a module ( = code which can be
9251 inserted in and removed from the running kernel whenever you
9252 want). The module will be called gvp11.o. If you want to compile it
9253 as a module, say M here and read Documentation/modules.txt.
9255 Cyberstorm SCSI support
9256 CONFIG_CYBERSTORM_SCSI
9257 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
9258 accelerator board and the optional Cyberstorm SCSI controller, say
9259 Y. Otherwise, say N.
9261 Cyberstorm II SCSI support
9262 CONFIG_CYBERSTORMII_SCSI
9263 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
9264 and the optional Cyberstorm SCSI controller, say Y. Otherwise, say
9267 Blizzard 2060 SCSI support
9269 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
9270 and want to use the onboard SCSI controller, say Y. Otherwise, say
9273 Blizzard 1230IV/1260 SCSI support
9275 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
9276 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
9279 Blizzard PowerUP 603e+ SCSI support
9280 CONFIG_BLZ603EPLUS_SCSI
9281 If you have an Amiga 1200 with a Phase5 Blizzard PowerUP 603e+
9282 accelerator, say Y. Otherwise, say N.
9284 Fastlane SCSI support
9285 CONFIG_FASTLANE_SCSI
9286 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
9287 one in the near future, say Y to this question. Otherwise, say N.
9289 Atari native SCSI support
9291 If you have an Atari with built-in NCR5380 SCSI controller (TT,
9292 Falcon, ...) say Y to get it supported. Of course also, if you have
9293 a compatible SCSI controller (e.g. for Medusa). This driver is also
9294 available as a module ( = code which can be inserted in and removed
9295 from the running kernel whenever you want). The module is called
9296 atari_scsi.o. If you want to compile it as a module, say M here and
9297 read Documentation/modules.txt. This driver supports both styles of
9298 NCR integration into the system: the TT style (separate DMA), and
9299 the Falcon style (via ST-DMA, replacing ACSI). It does NOT support
9300 other schemes, like in the Hades (without DMA).
9302 Long delays for Toshiba CD-ROMs
9303 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
9304 This option increases the delay after a SCSI arbitration to
9305 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
9306 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
9307 would impact performance a bit, so say N.
9309 Hades SCSI DMA emulator (EXPERIMENTAL)
9311 This option enables code which emulates the TT SCSI DMA chip on the
9312 Hades. This increases the SCSI transfer rates at least ten times
9313 compared to PIO transfers. Note that this code is experimental and
9314 has only been tested on a Hades with a 68060 processor. Before you
9315 use this, make backups of your entire hard disk.
9319 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
9322 This driver is also available as a module ( = code which can be
9323 inserted in and removed from the running kernel whenever you
9324 want). The module is called ariadne.o. If you want to compile it as
9325 a module, say M here and read Documentation/modules.txt.
9329 If you have a Village Tronic Ariadne II Ethernet adapter, say Y.
9332 This driver is also available as a module ( = code which can be
9333 inserted in and removed from the running kernel whenever you
9334 want). The module is called ariadne2.o. If you want to compile it as
9335 a module, say M here and read Documentation/modules.txt.
9339 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
9342 This driver is also available as a module ( = code which can be
9343 inserted in and removed from the running kernel whenever you
9344 want). The module is called a2065.o. If you want to compile it as a
9345 module, say M here and read Documentation/modules.txt.
9349 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
9351 This driver is also available as a module ( = code which can be
9352 inserted in and removed from the running kernel whenever you
9353 want). The module is called hydra.o. If you want to compile it as a
9354 module, say M here and read Documentation/modules.txt.
9358 Say Y to include support for several Atari Ethernet adapters based
9359 on the AMD Lance chipset: RieblCard (with or without battery), or
9360 PAMCard VME (also the version by Rhotron, with different addresses).
9364 Say Y to include support for BioData's BioNet-100 Ethernet adapter
9365 for the ACSI port. The driver works (has to work...) with a polled
9366 I/O scheme, so it's rather slow :-(
9369 CONFIG_ATARI_PAMSNET
9370 Say Y to include support for the PAMsNet Ethernet adapter for the
9371 ACSI port ("ACSI node"). The driver works (has to work...) with a
9372 polled I/O scheme, so it's rather slow :-(
9374 Multiface Card III parallel support
9375 CONFIG_MULTIFACE_III_LP
9376 If you have a Multiface III card for your Amiga, and want to use its
9377 parallel port in Linux, say Y. Otherwise, say N.
9379 This driver is also available as a module ( = code which can be
9380 inserted in and removed from the running kernel whenever you want).
9381 The module is called lp_m68k.o. If you want to compile it as a
9382 module, say M here and read Documentation/modules.txt.
9386 If you want to be able to use an Amiga mouse in Linux, say Y.
9388 This driver is also available as a module ( = code which can be
9389 inserted in and removed from the running kernel whenever you want).
9390 The module is called amigamouse.o. If you want to compile it as a
9391 module, say M here and read Documentation/modules.txt.
9393 Amiga Copper Console
9395 This configures the console to use the Amiga's graphics coprocessor
9396 for scrolling, instead of using the CPU. This option markedly
9397 improves response times in the high color modes (5 bitplanes and
9398 up). If you would like to use this, say Y; otherwise, say N.
9402 If you want to be able to use an Atari mouse in Linux, say Y.
9404 This driver is also available as a module ( = code which can be
9405 inserted in and removed from the running kernel whenever you want).
9406 The module is called atarimouse.o. If you want to compile it as a
9407 module, say M here and read Documentation/modules.txt.
9409 Atari MFP serial support
9411 If you like to use the MFP serial ports ("Modem1", "Serial1") under
9412 Linux, say Y. The driver equally supports all kinds of MFP serial
9413 ports and automatically detects whether Serial1 is available.
9415 This driver is also available as a module ( = code which can be
9416 inserted in and removed from the running kernel whenever you want).
9417 If you want to compile it as a module, say M here and read
9418 Documentation/modules.txt.
9420 Note for Falcon users: You also have an MFP port, it's just not
9421 wired to the outside... But you could use the port under Linux.
9423 Atari SCC serial support
9425 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
9426 LAN) and like to use them under Linux, say Y. All built-in SCC's are
9427 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
9428 two connectors for channel A (Serial2 and LAN), they are visible as
9429 two separate devices.
9431 This driver is also available as a module ( = code which can be
9432 inserted in and removed from the running kernel whenever you want).
9433 If you want to compile it as a module, say M here and read
9434 Documentation/modules.txt.
9436 Atari SCC serial DMA support
9437 CONFIG_ATARI_SCC_DMA
9438 This enables DMA support for receiving data on channel A of the
9439 SCC. If you have a TT you may say Y here and read
9440 drivers/char/atari_SCC.README. All other users should say N here,
9441 because only the TT has SCC-DMA, even if your machine keeps claiming
9444 Atari MIDI serial support
9446 If you want to use your Atari's MIDI port in Linux, say Y.
9448 This driver is also available as a module ( = code which can be
9449 inserted in and removed from the running kernel whenever you
9450 want). If you want to compile it as a module, say M here and read
9451 Documentation/modules.txt.
9453 Atari DSP56k Digital Signal Processor support
9455 If you want to be able to use the DSP56001 in Falcons, say Y.
9456 This driver is still experimental, and if you don't know what it is,
9457 or if you don't have this processor, just say N.
9459 This driver is also available as a module ( = code which can be inserted
9460 in and removed from the running kernel whenever you want). If you
9461 want to compile it as a module, say M here and read
9462 Documentation/modules.txt.
9464 Amiga builtin serial support
9465 CONFIG_AMIGA_BUILTIN_SERIAL
9466 If you want to use your Amiga's built-in serial port in Linux, say
9469 This driver is also available as a module ( = code which can be
9470 inserted in and removed from the running kernel whenever you
9471 want). If you want to compile it as a module, say M here and read
9472 Documentation/modules.txt.
9474 GVP IO-Extender support
9476 If you want to use a GVP IO-Extender serial card in Linux, say Y.
9479 Multiface Card III serial support
9480 CONFIG_MULTIFACE_III_TTY
9481 If you want to use a Multiface III card's serial port in Linux, say
9484 This driver is also available as a module ( = code which can be
9485 inserted in and removed from the running kernel whenever you want).
9486 If you want to compile it as a module, say M here and read
9487 Documentation/modules.txt.
9489 Amiga or Atari DMA sound support
9491 If you want to use the internal audio of your Atari or Amiga in
9492 Linux, answer Y to this question. This will provide a Sun-like
9493 /dev/audio, compatible with the Linux/i386 sound system. Otherwise,
9496 This driver is also available as a module ( = code which can be
9497 inserted in and removed from the running kernel whenever you
9498 want). If you want to compile it as a module, say M here and read
9499 Documentation/modules.txt.
9501 MSDOS partition support
9502 CONFIG_MSDOS_PARTITION
9503 This option enables support for using hard disks that were
9504 partitioned on an MS-DOS system. This may be useful if you are
9505 sharing a hard disk between i386 and m68k Linux boxes, for example.
9506 Say Y if you need this feature; users who are only using their
9507 system-native partitioning scheme can say N here.
9511 There are two types of PowerPC chips supported. The more common
9512 types (601,603,604,740,750) and the embedded versions (821 and 860).
9513 Unless you are building a kernel for one of the embedded boards using
9514 the 821 or 860 choose 6xx.
9518 Linux currently supports several different kinds of PowerPC-based
9519 machines: Apple Power Macintoshes and clones (such as the
9520 Motorola Starmax series), PReP (PowerPC Reference Platform) machines
9521 such as the Motorola PowerStack, Amiga Power-Up systems (APUS), CHRP
9522 and the embedded MBX boards from Motorola. Currently, a single
9523 kernel binary only supports one type or the other. However, there is
9524 very early work on support for CHRP, PReP and PowerMac's from a
9527 Support for Open Firmware device tree in /proc
9528 CONFIG_PROC_DEVICETREE
9529 This option adds a device-tree directory under /proc which contains
9530 an image of the device tree that the kernel copies from Open
9531 Firmware. If unsure, say Y here.
9533 MESH (Power Mac internal SCSI) support
9535 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
9536 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
9537 other Power Macintoshes do). Say Y to include support for this SCSI
9538 adaptor. This driver is also available as a module called mesh.o
9539 ( = code which can be inserted in and removed from the running
9540 kernel whenever you want). If you want to compile it as a module,
9541 say M here and read Documentation/modules.txt.
9543 Maximum synchronous transfer rate
9544 CONFIG_SCSI_MESH_SYNC_RATE
9545 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
9546 drives a bus which is entirely internal to the machine (such as the
9547 7500, 7600, 8500, etc.), the MESH is capable of synchronous
9548 operation at up to 10MB/s. On machines where the SCSI bus
9549 controlled by the MESH can have external devices connected, it is
9550 usually rated at 5MB/s. 5 is a safe value here unless you know the
9551 MESH SCSI bus is internal only; in that case you can say 10. Say 0
9552 to disable synchronous operation.
9554 53C94 (Power Mac external SCSI) support
9555 CONFIG_SCSI_MAC53C94
9556 On Power Macintoshes (and clones) with two SCSI buses, the external
9557 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
9558 machines which only have one SCSI bus, such as the 7200, also use
9559 the 53C94. Say Y to include support for the 53C94.
9561 This driver is also available as a module called mac53c94.o ( = code
9562 which can be inserted in and removed from the running kernel
9563 whenever you want). If you want to compile it as a module, say M
9564 here and read Documentation/modules.txt.
9566 MACE (Power Mac Ethernet) support
9568 Power Macintoshes and clones with Ethernet built-in on the
9569 motherboard will usually use a MACE (Medium Access Control for
9570 Ethernet) interface. Say Y to include support for the MACE chip.
9572 BMAC (G3 ethernet) support
9574 Say Y for support of BMAC Ethernet interfaces. These are used on G3
9579 Support for audio/video capture and overlay devices and FM radio
9580 cards. The exact capabilities of each device vary. User tools for
9581 this are available from
9582 ftp://ftp.uk.linux.org/pub/linux/video4linux.
9584 If you are interested in writing a driver for such an audio/video
9585 device or user software interacting with such a driver, please read
9586 the file Documentation/video4linux/API.html.
9588 This driver is also available as a module called videodev.o ( = code
9589 which can be inserted in and removed from the running kernel
9590 whenever you want). If you want to compile it as a module, say M
9591 here and read Documentation/modules.txt.
9593 AIMSlab RadioTrack (aka RadioReveal) support
9595 Choose Y here if you have one of these FM radio cards, and then fill
9596 in the port address below.
9598 Note that newer AIMSlab RadioTrack cards have a different chipset
9599 and are not supported by this driver. For these cards, use the
9600 RadioTrack II driver below.
9602 In order to control your radio card, you will need to use programs
9603 that are compatible with the Video for Linux API. Information on
9604 this API and pointers to "v4l" programs may be found on the WWW at
9605 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
9606 you need to have access to a machine on the Internet that has a
9607 program like lynx or netscape. More information is contained in the
9608 file Documentation/video4linux/radiotrack.txt.
9610 If you want to compile this driver as a module ( = code which can be
9611 inserted in and removed from the running kernel whenever you want),
9612 say M here and read Documentation/modules.txt. The module will be
9613 called radio-aimslab.o.
9616 CONFIG_RADIO_RTRACK_PORT
9617 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
9618 haven't changed the jumper setting on the card.
9620 AIMSlab RadioTrack II support
9621 CONFIG_RADIO_RTRACK2
9622 Choose Y here if you have this FM radio card, and then fill in the
9625 In order to control your radio card, you will need to use programs
9626 that are compatible with the Video for Linux API. Information on
9627 this API and pointers to "v4l" programs may be found on the WWW at
9628 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
9629 you need to have access to a machine on the Internet that has a
9630 program like lynx or netscape.
9632 If you want to compile this driver as a module ( = code which can be
9633 inserted in and removed from the running kernel whenever you want),
9634 say M here and read Documentation/modules.txt. The module will be
9635 called radio-rtrack2.o.
9637 RadioTrack II i/o port
9638 CONFIG_RADIO_RTRACK2_PORT
9639 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
9640 haven't changed the jumper setting on the card.
9642 Aztech/Packard Bell Radio
9644 Choose Y here if you have one of these FM radio cards, and then fill
9645 in the port address below.
9647 In order to control your radio card, you will need to use programs
9648 that are compatible with the Video for Linux API. Information on
9649 this API and pointers to "v4l" programs may be found on the WWW at
9650 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
9651 you need to have access to a machine on the Internet that has a
9652 program like lynx or netscape.
9654 If you want to compile this driver as a module ( = code which can be
9655 inserted in and removed from the running kernel whenever you want),
9656 say M here and read Documentation/modules.txt. The module will be
9657 called radio-aztech.o.
9659 Aztech/Packard Bell radio card i/o port
9660 CONFIG_RADIO_AZTECH_PORT
9661 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
9662 haven't changed the setting of jumper JP3 on the card. Removing the
9663 jumper sets the card to 0x358.
9666 CONFIG_RADIO_SF16FMI
9667 Choose Y here if you have one of these FM radio cards, and then fill
9668 in the port address below.
9670 In order to control your radio card, you will need to use programs
9671 that are compatible with the Video for Linux API. Information on
9672 this API and pointers to "v4l" programs may be found on the WWW at
9673 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
9674 you need to have access to a machine on the Internet that has a
9675 program like lynx or netscape.
9677 If you want to compile this driver as a module ( = code which can be
9678 inserted in and removed from the running kernel whenever you want),
9679 say M here and read Documentation/modules.txt. The module will be
9680 called radio-sf16fmi.o
9682 SF16FMI I/O port (0x284 or 0x384)
9683 CONFIG_RADIO_SF16FMI_PORT
9684 Enter the I/O port of your SF16FMI radio card.
9687 CONFIG_RADIO_ZOLTRIX
9688 Choose Y here if you have one of these FM radio cards, and then fill
9689 in the port address below.
9691 In order to control your radio card, you will need to use programs
9692 that are compatible with the Video for Linux API. Information on
9693 this API and pointers to "v4l" programs may be found on the WWW at
9694 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
9695 you need to have access to a machine on the Internet that has a
9696 program like lynx or netscape.
9698 If you want to compile this driver as a module ( = code which can be
9699 inserted in and removed from the running kernel whenever you want),
9700 say M here and read Documentation/modules.txt. The module will be
9701 called radio-zoltrix.o
9703 ZOLTRIX I/O port (0x20c or 0x30c)
9704 CONFIG_RADIO_ZOLTRIX_PORT
9705 Enter the I/O port of your Zoltrix radio card.
9708 CONFIG_RADIO_MIROPCM20
9709 Choose Y here if you have one of these FM radio cards, and then fill
9710 in the port address below.
9712 In order to control your radio card, you will need to use programs
9713 that are compatible with the Video for Linux API. Information on
9714 this API and pointers to "v4l" programs may be found on the WWW at
9715 http://roadrunner.swansea.uk.linux.org/v4l.shtml; to browse the WWW,
9716 you need to have access to a machine on the Internet that has a
9717 program like lynx or netscape.
9719 If you want to compile this driver as a module ( = code which can be
9720 inserted in and removed from the running kernel whenever you want),
9721 say M here and read Documentation/modules.txt. The module will be
9722 called radio-miropcm20.o
9724 BT848 Video For Linux
9726 Support for BT848 based frame grabber/overlay boards. This includes
9727 the Miro, Hauppauge and STB boards. Please read the material in
9728 Documentation/video4linux/bttv for more information.
9730 This driver is also available as a module called bttv.o ( = code
9731 which can be inserted in and removed from the running kernel
9732 whenever you want). If you want to compile it as a module, say M
9733 here and read Documentation/modules.txt.
9735 SAA5249 Teletext processor
9736 CONFIG_VIDEO_SAA5249
9737 Support for I2C bus based teletext using the SAA5249 chip. At the
9738 moment this is only useful on some European WinTV cards.
9740 This driver is also available as a module called saa5249.o ( = code
9741 which can be inserted in and removed from the running kernel
9742 whenever you want). If you want to compile it as a module, say M
9743 here and read Documentation/modules.txt.
9745 Quickcam BW Video For Linux
9747 Say Y have if you the black and white version of the QuickCam
9748 camera. See the next option for the color version.
9750 This driver is also available as a module called bw-qcam.o ( = code
9751 which can be inserted in and removed from the running kernel
9752 whenever you want). If you want to compile it as a module, say M
9753 here and read Documentation/modules.txt.
9755 Colour QuickCam Video For Linux
9757 This is the video4linux driver for the colour version of the
9758 Connectix Quickcam. If you have one of these cameras, say Y here,
9759 otherwise say N. This driver does not work with the original
9760 monochrome Quickcam, Quickcam VC or QuickClip. It is also available
9761 as a module (c-qcam.o).
9763 Mediavision Pro Movie Studio Video For Linux
9765 Say Y if you have such a thing. This driver is also available as a
9766 module called pms.o ( = code which can be inserted in and removed
9767 from the running kernel whenever you want). If you want to compile
9768 it as a module, say M here and read Documentation/modules.txt.
9772 This selects the processor type of your CPU. This is only used to
9773 determine C compiler optimization options, and can affect the
9774 compatibility of the kernel on other processors. If you specify
9775 ARM6, the kernel should work on all 32-bit processors. If you
9776 specify ARM2, ARM250 or ARM3, it should work on all 26-bit
9777 processors. If you're not sure, set it to "None".
9781 This selects what ARM system you wish to build the kernel for. It
9782 also selects to some extent the CPU type. If you are unsure what
9783 to set this option to, please consult any information supplied with
9786 Build Tools Selection
9788 Say Y here if and only if you're using GCC 2.8.1/EGCS with a
9789 binutils version >= 2.8.1 to compile the kernel (check with "gcc
9790 --version" and "ld -v").
9792 Compile kernel with frame pointer
9793 CONFIG_FRAME_POINTER
9794 If you say Y here, the resulting kernel will be slightly larger, but
9795 it will give useful debugging/error results. If you don't debug the
9796 kernel, you can say N.
9800 Say 'Y' here for ARM systems with the VIDC video controller and 16-bit
9801 Linear sound DACs. If unsure, say N.
9803 Backward compatibility mode for Xpmac
9804 CONFIG_FB_COMPAT_XPMAC
9805 If you use the Xpmac X server (common with mklinux), you'll need
9806 to enable this to use X. You should consider changing to XFree86
9807 which includes a server that supports the frame buffer device
9808 directly (XF68_FBDev).
9810 Support for PowerMac keyboard
9812 This option allows you to use an ADB keyboard attached to your
9813 machine. Note that this disables any other (ie. PS/2) keyboard
9814 support, even if your machine is physically capable of using both
9817 If you use an ADB keyboard (4 pin connector), say Y here.
9818 If you use a PS/2 keyboard (6 pin connector), say N here.
9820 Support for PowerMac floppy
9822 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
9823 floppy controller, say Y here. Most commonly found in PowerMacs.
9825 Support for PowerMac serial ports
9827 If you have Macintosh style serial ports (8 pin mini-DIN), this
9828 is the driver for them. If you also have regular serial ports
9829 and enable the driver for them, you can't currently use the
9830 serial console feature.
9832 Support for PowerMac ADB mouse
9834 If you have an ADB mouse (4 pin connector) as is common on
9835 Macintoshes, say Y here.
9837 Winbond SL82c105 support
9838 CONFIG_BLK_DEV_SL82C105
9839 If you have a Winbond SL82c105 IDE controller, say Y here to
9840 enable special configuration for this chip. This is common
9841 on various CHRP motherboards, but could be used elsewhere.
9844 # A couple of things I keep forgetting:
9845 # capitalize: AppleTalk, Ethernet, DMA, FTP, Internet, Intel, IRQ,
9846 # Linux, NetWare, NFS, PCI, SCSI, SPARC
9847 # two words: hard drive, hard disk, sound card, home page
9848 # other: it's safe to save; daemon; use --, not - or ---
9850 # This is used by Emacs' spell checker ispell.el:
9852 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp sunsite
9853 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
9854 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
9855 # LocalWords: HD CDROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
9856 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
9857 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
9858 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
9859 # LocalWords: genksyms INET loopback gatewaying ethernet PPP ARP Arp MEMSIZE
9860 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
9861 # LocalWords: proc acct IPIP encapsulator decapsulator klogd PCTCP RARP EXT PS
9862 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
9863 # LocalWords: Mb SKB IPX Novell dosemu Appletalk DDP ATALK vmalloc visar ehome
9864 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
9865 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
9866 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
9867 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
9868 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
9869 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
9870 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
9871 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
9872 # LocalWords: PCMCIA cb stanford pcmcia LAN TEC RealTek ATP atp DLINK NetTools
9873 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
9874 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
9875 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
9876 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
9877 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
9878 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
9879 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
9880 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
9881 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
9882 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
9883 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
9884 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
9885 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
9886 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
9887 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
9888 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
9889 # LocalWords: carleton Deskstation DECstation SUNFD JENSEN Noname XXXM SLiRP
9890 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
9891 # LocalWords: RTNETLINK mknod xos MTU lwared Macs mac netatalk macs cs Wolff
9892 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
9893 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
9894 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ chipsets MG
9895 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
9896 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
9897 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
9898 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrecord pg
9899 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
9900 # LocalWords: KERNELD kerneld callouts AdvanSys advansys Admin WDT DataStor EP
9901 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
9902 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet axplinux cdr fb MDA
9903 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
9904 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
9905 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
9906 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
9907 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles ICN EDSS Cisco
9908 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
9909 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
9910 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
9911 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
9912 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
9913 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
9914 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu ethernets HBAs MEX
9915 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
9916 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
9917 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
9918 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCDROM FreeBSD NeXT
9919 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
9920 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
9921 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
9922 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
9923 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
9924 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
9925 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
9926 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
9927 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
9928 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
9929 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
9930 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
9931 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
9932 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
9933 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
9934 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
9935 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
9936 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
9937 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
9938 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
9939 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
9940 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
9941 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
9942 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
9943 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
9944 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
9945 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
9946 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
9947 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
9948 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
9949 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
9950 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
9951 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
9952 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
9953 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
9954 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
9955 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
9956 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
9957 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
9958 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
9959 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
9960 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
9961 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
9962 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
9963 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
9964 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
9965 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
9966 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
9967 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
9968 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
9969 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
9970 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
9971 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
9972 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
9973 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
9974 # LocalWords: caldera Preload dcache Preloading slowdowns schoebel uni NBD nbd
9975 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
9976 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
9977 # LocalWords: transname filespace adm Nodename hostname uname Kernelname bootp
9978 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
9979 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
9980 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
9981 # LocalWords: HFMODEM shortwave Sitor Amtor Pactor GTOR hfmodem hayes TX TMOUT
9982 # LocalWords: IDEPCI IDEDMA idedma PDC pdc TRM trm raidtools luthien nuclecu
9983 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
9984 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
9985 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
9986 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
9987 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
9988 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
9989 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
9990 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
9991 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
9992 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
9993 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
9994 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
9995 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
9996 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
9997 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Byelorussian KOI mt
9998 # LocalWords: charset Inuit Greenlandic Sami Lappish koi SOFTCURSOR softcursor
9999 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
10000 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
10001 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
10002 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
10003 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
10004 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
10005 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
10006 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
10007 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
10008 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
10009 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
10010 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
10011 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
10012 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
10013 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
10014 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
10015 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
10016 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
10017 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
10018 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
10019 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
10020 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
10021 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
10022 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
10023 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
10024 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
10025 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
10026 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
10027 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
10028 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SKTR SNA
10029 # LocalWords: SysKonnect sktr sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
10030 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
10031 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
10032 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
10033 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
10034 # LocalWords: CGthree TCX unswapable vfb fbcon hicolor truecolor AFB ILBM SOC
10035 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
10036 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss
10037 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX
10038 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm