2 # Eric S. Raymond <mailto:esr@thyrsus.com>
3 # Steven Cole <mailto:elenstev@mesatop.com>
5 # Translations of this file available on the WWW:
7 # - Japanese, maintained by the JF Project <mailto:JF@linux.or.jp>, at
8 # <http://www.linux.or.jp/JF/JFdocs/Configure.help/>
9 # - Russian, by <mailto:kaf@linux.nevod.perm.su>, at
10 # <http://nevod.perm.su/service/linux/doc/kernel/Configure.help>
11 # - French, by Pierre Tane <mailto:tanep@bigfoot.com>, at
12 # <http://www.traduc.org/kernelfr/>
13 # - Polish, by Dominik Mierzejewski <mailto:dominik@piorunek.pl>, at
14 # <http://www.piorunek.pl/~dominik/linux/kernel/>
15 # - German, by SuSE, at <http://www.suse.de/~ke/kernel/>. This patch
16 # also includes infrastructure to support different languages.
17 # - Catalan, by Antoni Bella <mailto:bella5@teleline.es>, at
18 # <http://www.terra.es/personal7/bella5/traduccions.htm>
20 # Information about what a kernel is, what it does, how to patch and
21 # compile it and much more is contained in the Kernel-HOWTO, available
22 # at <http://www.tldp.org/docs.html#howto>. Before you start
23 # compiling, make sure that you have the necessary versions of all
24 # programs and libraries required to compile and run this kernel; they
25 # are listed in the <file:Documentation/Changes>. Make sure to read the
26 # toplevel kernel README file as well.
28 # Format of this file: description<nl>variable<nl>help text<nl><nl>.
29 # The help texts may contain empty lines, but every non-empty line must
30 # be indented two positions. Order of the help texts does not matter,
31 # however, no variable should be documented twice: if it is, only the
32 # first occurrence will be used. We try to keep the help texts of related
33 # variables close together. Lines starting with `#' are ignored. To be
34 # nice to menuconfig, limit your line length to 70 characters. Use emacs'
35 # kfill.el to edit and ispell.el to spell check this file or you lose.
37 # Comments of the form "# Choice:" followed by a menu name are used
38 # internally by the maintainers' consistency-checking tools.
40 # If you add a help text to this file, please try to be as gentle as
41 # possible. Don't use unexplained acronyms and generally write for the
42 # hypothetical ignorant but intelligent user who has just bought a PC,
43 # removed Windows, installed Linux and is now recompiling the kernel
44 # for the first time. Tell them what to do if they're unsure. Technical
45 # information should go in a README in the Documentation directory.
47 # Mention all the relevant READMEs and HOWTOs in the help text.
48 # Make them file URLs relative to the top level of the source tree so
49 # that help browsers can turn them into hotlinks. All URLs should be
52 # Repetitions are fine since the help texts are not meant to be read
53 # in sequence. It is good style to include URLs pointing to more
54 # detailed technical information, pictures of the hardware, etc.
56 # The most important thing to include in a help entry is *motivation*.
57 # Explain why someone configuring a kernel might want to select your
60 # All this was shamelessly stolen from numerous different sources. Many
61 # thanks to all the contributors. Feel free to use these help texts in
62 # your own kernel configuration tools. The texts are copyrighted (c)
63 # 1995-2000 by Axel Boldt and many others and are governed by the GNU
64 # General Public License.
66 Prompt for development and/or incomplete code/drivers
68 Some of the various things that Linux supports (such as network
69 drivers, file systems, network protocols, etc.) can be in a state
70 of development where the functionality, stability, or the level of
71 testing is not yet high enough for general use. This is usually
72 known as the "alpha-test" phase among developers. If a feature is
73 currently in alpha-test, then the developers usually discourage
74 uninformed widespread use of this feature by the general public to
75 avoid "Why doesn't this work?" type mail messages. However, active
76 testing and use of these systems is welcomed. Just be aware that it
77 may not meet the normal level of reliability or it may fail to work
78 in some special cases. Detailed bug reports from people familiar
79 with the kernel internals are usually welcomed by the developers
80 (before submitting bug reports, please read the documents
81 <file:README>, <file:MAINTAINERS>, <file:REPORTING-BUGS>,
82 <file:Documentation/BUG-HUNTING>, and
83 <file:Documentation/oops-tracing.txt> in the kernel source).
85 This option will also make obsoleted drivers available. These are
86 drivers that have been replaced by something else, and/or are
87 scheduled to be removed in a future kernel release.
89 Unless you intend to help test and develop a feature or driver that
90 falls into this category, or you have a situation that requires
91 using these features, you should probably say N here, which will
92 cause the configurator to present you with fewer choices. If
93 you say Y here, you will be offered the choice of using features or
94 drivers that are currently considered to be in the alpha-test phase.
96 Prompt for drivers for obsolete features and hardware
98 Obsolete drivers have usually been replaced by more recent software
99 that can talk to the same hardware. Obsolete hardware is things
100 like MGA monitors that you are very unlikely to see on today's
103 Prompt for advanced kernel configuration options
104 CONFIG_ADVANCED_OPTIONS
105 This option will enable prompting for a variety of advanced kernel
106 configuration options. These options can cause the kernel to not
107 work if they are set incorrectly, but can be used to optimize certain
108 aspects of kernel memory management.
110 Unless you know what you are doing you *should not* enable this option.
112 Symmetric Multi-Processing support
114 This enables support for systems with more than one CPU. If you have
115 a system with only one CPU, like most personal computers, say N. If
116 you have a system with more than one CPU, say Y.
118 If you say N here, the kernel will run on single and multiprocessor
119 machines, but will use only one CPU of a multiprocessor machine. If
120 you say Y here, the kernel will run on many, but not all,
121 single machines. On a singleprocessor machine, the kernel
122 will run faster if you say N here.
124 Note that if you say Y here and choose architecture "586" or
125 "Pentium" under "Processor family", the kernel will not work on 486
126 architectures. Similarly, multiprocessor kernels for the "PPro"
127 architecture may not work on all Pentium based boards.
129 People using multiprocessor machines who say Y here should also say
130 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
131 Management" code will be disabled if you say Y here.
133 See also the <file:Documentation/smp.tex>,
134 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
135 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
136 <http://www.tldp.org/docs.html#howto>.
138 If you don't know what to do here, say N.
140 Maximum number of CPUs
142 This allows you to specify the maximum number of CPUs which this
143 kernel will support. The maximum supported value is 32 and the
144 mimimum value which makes sense is 2.
146 This is purely to save memory - each supported CPU adds
147 approximately eight kilobytes to the kernel image.
149 Intel or compatible 80x86 processor
151 This is Linux's home port. Linux was originally native to the Intel
152 386, and runs on all the later x86 processors including the Intel
153 486, 586, Pentiums, and various instruction-set-compatible chips by
154 AMD, Cyrix, and others.
158 The Alpha is a 64-bit general-purpose processor designed and
159 marketed by the Digital Equipment Corporation of blessed memory, now
160 Compaq. Alpha Linux dates from 1995-1996 and was the first non-x86
161 port. The Alpha Linux project has a home page at
162 <http://www.alphalinux.org/>.
166 SPARC is a family of RISC microprocessors designed and marketed by
167 Sun Microsystems, incorporated. They are very widely found in Sun
168 workstations and clones. This port covers the original 32-bit SPARC;
169 it is old and stable and usually considered one of the "big three"
170 along with the Intel and Alpha ports. The UltraLinux project
171 maintains both the SPARC32 and SPARC64 ports; its web page is
172 available at <http://www.ultralinux.org/>.
176 SPARC is a family of RISC microprocessors designed and marketed by
177 Sun Microsystems, incorporated. This port covers the newer 64-bit
178 UltraSPARC. The UltraLinux project maintains both the SPARC32 and
179 SPARC64 ports; its web page is available at
180 <http://www.ultralinux.org/>.
184 The PowerPC is a very capable 32-bit RISC processor from Motorola,
185 the successor to their 68000 and 88000 series. It powers recent
186 Macintoshes and also a widely-used series of single-board computers
187 from Motorola. The Linux PowerPC port has a home page at
188 <http://penguinppc.org/>.
190 Motorola 68K processors
192 The Motorola 68K microprocessors are now obsolete, having been
193 superseded by the PowerPC line also from Motorola. But they powered
194 the first wave of workstation hardware in the 1980s, including Sun
195 workstations; they were also the basis of the original Amiga and
196 later Atari personal computers. A lot of this hardware is still
197 around. The m68k project has a home page at
198 <http://www.linux-m68k.org/>.
202 The ARM series is a line of low-power-consumption RISC chip designs
203 licensed by ARM ltd and targeted at embedded applications and
204 handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
205 manufactured, but legacy ARM-based PC hardware remains popular in
206 Europe. There is an ARM Linux project with a web page at
207 <http://www.arm.linux.org.uk/>.
211 The SuperH is a RISC processor targeted for use in embedded systems
212 and consumer electronics; it was also used in the Sega Dreamcast
213 gaming console. The SuperH port has a home page at
214 <http://www.sh-linux.org/>.
216 IA64 processors, including Intel Itanium
218 The Itanium is Intel's 64-bit successor to the 32-bit X86 line. As
219 of early 2001 it is not yet in widespread production use. The Linux
220 IA-64 project has a home page at <http://www.linuxia64.org/>.
224 The PA-RISC microprocessor is a RISC chip designed by
225 Hewlett-Packard and used in their line of workstations. The PA-RISC
226 Linux project has a home page at <www.parisc-linux.org>.
230 Linux now runs on the venerable System/390 mainframe from IBM, in a
231 guest partition under VM. In fact, over 40,000 simultaneous Linux
232 images have been run on a single mainframe! The S390 Linux project
233 has a home page at <http://linux.s390.org/>.
235 Axis Communications ETRAX 100LX embedded network CPU
237 Linux has been ported to run on the Axis Communications ETRAX 100LX
238 CPU and the single-board computers built around it, targeted for
239 network and embedded applications. For more information see the
240 Axis Communication site, <http://developer.axis.com/>.
243 CONFIG_X86_TSC_DISABLE
244 This option is used for getting Linux to run on a NUMA multi-node
245 boxes, laptops and other systems suffering from unsynced TSCs or
246 TSC drift, which can cause gettimeofday to return non-monotonic values.
247 Choosing this option will disable the CONFIG_X86_TSC optimization,
248 and allows you to then specify "notsc" as a boot option regardless of
249 which processor you have compiled for.
251 NOTE: If your system hangs when init should run, you are probably
252 using a i686 compiled glibc which reads the TSC without checking for
253 availability. Boot without "notsc" and install a i386 compiled glibc
254 to solve the problem.
258 Multiquad support for NUMAQ systems
260 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
261 multiquad box. This changes the way that processors are bootstrapped,
262 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
263 You will need a new lynxer.elf file to flash your firmware with - send
264 email to Martin.Bligh@us.ibm.com
266 Support for IBM Summit (EXA) systems
268 This option is needed for IBM systems that use the Summit/EXA chipset.
269 (EXA: Extendable Xseries Architecture)In particular, it is needed for
270 the x440 (even for the 4-CPU model).
272 If you don't have this computer, you may safely say N.
274 IO-APIC support on uniprocessors
276 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
277 SMP-capable replacement for PC-style interrupt controllers. Most
278 SMP systems and a small number of uniprocessor systems have one.
279 If you have a single-CPU system with an IO-APIC, you can say Y here
280 to use it. If you say Y here even though your machine doesn't have
281 an IO-APIC, then the kernel will still run with no slowdown at all.
283 If you have a system with several CPUs, you do not need to say Y
284 here: the IO-APIC will be used automatically.
286 Local APIC Support on Uniprocessors
288 A local APIC (Advanced Programmable Interrupt Controller) is an
289 integrated interrupt controller in the CPU. If you have a single-CPU
290 system which has a processor with a local APIC, you can say Y here to
291 enable and use it. If you say Y here even though your machine doesn't
292 have a local APIC, then the kernel will still run with no slowdown at
293 all. The local APIC supports CPU-generated self-interrupts (timer,
294 performance counters), and the NMI watchdog which detects hard lockups.
296 If you have a system with several CPUs, you do not need to say Y
297 here: the local APIC will be used automatically.
299 Kernel math emulation
300 CONFIG_MATH_EMULATION
301 Linux can emulate a math coprocessor (used for floating point
302 operations) if you don't have one. 486DX and Pentium processors have
303 a math coprocessor built in, 486SX and 386 do not, unless you added
304 a 487DX or 387, respectively. (The messages during boot time can
305 give you some hints here ["man dmesg"].) Everyone needs either a
306 coprocessor or this emulation.
308 If you don't have a math coprocessor, you need to say Y here; if you
309 say Y here even though you have a coprocessor, the coprocessor will
310 be used nevertheless. (This behaviour can be changed with the kernel
311 command line option "no387", which comes handy if your coprocessor
312 is broken. Try "man bootparam" or see the documentation of your boot
313 loader (lilo or loadlin) about how to pass options to the kernel at
314 boot time.) This means that it is a good idea to say Y here if you
315 intend to use this kernel on different machines.
317 More information about the internals of the Linux math coprocessor
318 emulation can be found in <file:arch/i386/math-emu/README>.
320 If you are not sure, say Y; apart from resulting in a 66 KB bigger
321 kernel, it won't hurt.
323 Timer and CPU usage LEDs
325 If you say Y here, the LEDs on your machine will be used
326 to provide useful information about your current system status.
328 If you are compiling a kernel for a NetWinder or EBSA-285, you will
329 be able to select which LEDs are active using the options below. If
330 you are compiling a kernel for the EBSA-110 or the LART however, the
331 red LED will simply flash regularly to indicate that the system is
332 still functional. It is safe to say Y here if you have a CATS
333 system, but the driver will do nothing.
337 If you say Y here, one of the system LEDs (the green one on the
338 NetWinder, the amber one on the EBSA285, or the red one on the LART)
339 will flash regularly to indicate that the system is still
340 operational. This is mainly useful to kernel hackers who are
341 debugging unstable kernels.
343 The LART uses the same LED for both Timer LED and CPU usage LED
344 functions. You may choose to use both, but the Timer LED function
345 will overrule the CPU usage LED.
349 If you say Y here, the red LED will be used to give a good real
350 time indication of CPU usage, by lighting whenever the idle task
351 is not currently executing.
353 The LART uses the same LED for both Timer LED and CPU usage LED
354 functions. You may choose to use both, but the Timer LED function
355 will overrule the CPU usage LED.
357 Kernel FP software completion
359 This option is required for IEEE compliant floating point arithmetic
360 on the Alpha. The only time you would ever not say Y is to say M in
361 order to debug the code. Say Y unless you know what you are doing.
366 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
367 However, the address space of 32-bit x86 processors is only 4
368 Gigabytes large. That means that, if you have a large amount of
369 physical memory, not all of it can be "permanently mapped" by the
370 kernel. The physical memory that's not permanently mapped is called
373 If you are compiling a kernel which will never run on a machine with
374 more than 960 megabytes of total physical RAM, answer "off" here (default
375 choice and suitable for most users). This will result in a "3GB/1GB"
376 split: 3GB are mapped so that each process sees a 3GB virtual memory
377 space and the remaining part of the 4GB virtual memory space is used
378 by the kernel to permanently map as much physical memory as
381 If the machine has between 1 and 4 Gigabytes physical RAM, then
384 If more than 4 Gigabytes is used then answer "64GB" here. This
385 selection turns Intel PAE (Physical Address Extension) mode on.
386 PAE implements 3-level paging on IA32 processors. PAE is fully
387 supported by Linux, PAE mode is implemented on all recent Intel
388 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
389 then the kernel will not boot on CPUs that don't support PAE!
391 The actual amount of total physical memory will either be auto
392 detected or can be forced by using a kernel command line option such
393 as "mem=256M". (Try "man bootparam" or see the documentation of your
394 boot loader (grub, lilo or loadlin) about how to pass options to the
395 kernel at boot time.)
397 If unsure, say "off".
401 Select this if you have a 32-bit processor and between 1 and 4
402 gigabytes of physical RAM.
406 Select this if you have a 32-bit processor and more than 4
407 gigabytes of physical RAM.
411 If you want to be able to do I/O to high memory pages, say Y.
412 Otherwise low memory pages are used as bounce buffers causing a
413 degrade in performance.
417 This option selects the kernel behaviour during total out of memory
420 The default behaviour is to, as soon as no freeable memory and no swap
421 space are available, kill the task which tries to allocate memory.
422 The default behaviour is very reliable.
424 If you select this option, as soon as no freeable memory is available,
425 the kernel will try to select the "best" task to be killed.
429 Normal floppy disk support
431 If you want to use the floppy disk drive(s) of your PC under Linux,
432 say Y. Information about this driver, especially important for IBM
433 Thinkpad users, is contained in <file:Documentation/floppy.txt>.
434 That file also contains the location of the Floppy driver FAQ as
435 well as location of the fdutils package used to configure additional
436 parameters of the driver at run time.
438 This driver is also available as a module ( = code which can be
439 inserted in and removed from the running kernel whenever you want).
440 The module will be called floppy.o. If you want to compile it as a
441 module, say M here and read <file:Documentation/modules.txt>.
443 iSeries Virtual I/O Disk Support
445 If you are running on an iSeries system and you want to use
446 virtual disks created and managed by OS/400, say Y.
448 iSeries Virtual I/O Disk IDE Emulation
450 This causes the iSeries virtual disks to look like IDE disks.
451 If you have programs or utilities that only support certain
452 kinds of disks, this option will cause iSeries virtual disks
453 to pretend to be IDE disks, which may satisfy the program.
455 Support for PowerMac floppy
457 If you have a SWIM-3 (Super Woz Integrated Machine 3; from Apple)
458 floppy controller, say Y here. Most commonly found in PowerMacs.
462 Saying Y here will allow you to use a portion of your RAM memory as
463 a block device, so that you can make file systems on it, read and
464 write to it and do all the other things that you can do with normal
465 block devices (such as hard drives). It is usually used to load and
466 store a copy of a minimal root file system off of a floppy into RAM
467 during the initial install of Linux.
469 Note that the kernel command line option "ramdisk=XX" is now
470 obsolete. For details, read <file:Documentation/ramdisk.txt>.
472 If you want to compile this as a module ( = code which can be
473 inserted in and removed from the running kernel whenever you want),
474 say M and read <file:Documentation/modules.txt>. The module will be
477 Most normal users won't need the RAM disk functionality, and can
480 Default RAM disk size
481 CONFIG_BLK_DEV_RAM_SIZE
482 The default value is 4096. Only change this if you know what are
483 you doing. If you are using IBM S/390, then set this to 8192.
485 Initial RAM disk (initrd) support
486 CONFIG_BLK_DEV_INITRD
487 The initial RAM disk is a RAM disk that is loaded by the boot loader
488 (loadlin or lilo) and that is mounted as root before the normal boot
489 procedure. It is typically used to load modules needed to mount the
490 "real" root file system, etc. See <file:Documentation/initrd.txt>
493 Embed root filesystem ramdisk into the kernel
494 CONFIG_EMBEDDED_RAMDISK
495 Select this option if you want to build the ramdisk image into the
496 the final kernel binary.
498 Filename of gziped ramdisk image
499 CONFIG_EMBEDDED_RAMDISK_IMAGE
500 This is the filename of the ramdisk image to be built into the
501 kernel. Relative pathnames are relative to arch/mips/ramdisk/.
502 The ramdisk image is not part of the kernel distribution; you must
503 provide one yourself.
505 Loopback device support
507 Saying Y here will allow you to use a regular file as a block
508 device; you can then create a file system on that block device and
509 mount it just as you would mount other block devices such as hard
510 drive partitions, CD-ROM drives or floppy drives. The loop devices
511 are block special device files with major number 7 and typically
512 called /dev/loop0, /dev/loop1 etc.
514 This is useful if you want to check an ISO 9660 file system before
515 burning the CD, or if you want to use floppy images without first
516 writing them to floppy. Furthermore, some Linux distributions avoid
517 the need for a dedicated Linux partition by keeping their complete
518 root file system inside a DOS FAT file using this loop device
521 The loop device driver can also be used to "hide" a file system in a
522 disk partition, floppy, or regular file, either using encryption
523 (scrambling the data) or steganography (hiding the data in the low
524 bits of, say, a sound file). This is also safe if the file resides
525 on a remote file server. If you want to do this, you will first have
526 to acquire and install a kernel patch from
527 <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
528 say Y to this option.
530 Note that alternative ways to use encrypted file systems are
531 provided by the cfs package, which can be gotten from
532 <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
533 package, available at <http://tcfs.dia.unisa.it/>. You do not need
534 to say Y here if you want to use one of these. However, using cfs
535 requires saying Y to "NFS file system support" below while using
536 tcfs requires applying a kernel patch. An alternative steganography
537 solution is provided by StegFS, also available from
538 <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
540 To use the loop device, you need the losetup utility and a recent
541 version of the mount program, both contained in the util-linux
542 package. The location and current version number of util-linux is
543 contained in the file <file:Documentation/Changes>.
545 Note that this loop device has nothing to do with the loopback
546 device used for network connections from the machine to itself.
548 If you want to compile this driver as a module ( = code which can be
549 inserted in and removed from the running kernel whenever you want),
550 say M here and read <file:Documentation/modules.txt>. The module
551 will be called loop.o.
553 Most users will answer N here.
555 Micro Memory MM5415 Battery Backed RAM support (EXPERIMENTAL)
557 Saying Y here will include support for the MM5415 family of
558 battery backed (Non-volatile) RAM cards.
559 <http://www.umem.com/>
561 The cards appear as block devices that can be partitioned into
562 as many as 15 partitions.
564 If you want to compile this driver as a module ( = code which can be
565 inserted in and removed from the running kernel whenever you want),
566 say M here and read Documentation/modules.txt. The module will be
569 The umem driver has been allocated block major number 116.
570 See Documentation/devices.txt for recommended device naming.
572 Promise SATA SX8 support
574 Saying Y or M here will enable support for the
575 Promise SATA SX8 controllers.
577 If you want to compile this driver as a module ( = code which can be
578 inserted in and removed from the running kernel whenever you want),
579 say M here and read Documentation/modules.txt. The module will be
582 The sx8 driver has been allocated block major numbers 160, 161.
583 See Documentation/devices.txt for recommended device naming.
585 Network block device support
587 Saying Y here will allow your computer to be a client for network
588 block devices, i.e. it will be able to use block devices exported by
589 servers (mount file systems on them etc.). Communication between
590 client and server works over TCP/IP networking, but to the client
591 program this is hidden: it looks like a regular local file access to
592 a block device special file such as /dev/nd0.
594 Network block devices also allows you to run a block-device in
595 userland (making server and client physically the same computer,
596 communicating using the loopback network device).
598 Read <file:Documentation/nbd.txt> for more information, especially
599 about where to find the server code, which runs in user space and
600 does not need special kernel support.
602 Note that this has nothing to do with the network file systems NFS
603 or Coda; you can say N here even if you intend to use NFS or Coda.
605 If you want to compile this driver as a module ( = code which can be
606 inserted in and removed from the running kernel whenever you want),
607 say M here and read <file:Documentation/modules.txt>. The module
608 will be called nbd.o.
612 Per partition statistics in /proc/partitions
614 If you say yes here, your kernel will keep statistical information
615 for every partition. The information includes things as numbers of
616 read and write accesses, the number of merged requests etc.
618 This is required for the full functionality of sar(8) and interesting
619 if you want to do performance tuning, by tweaking the elevator, e.g.
620 On the other hand, it will cause random and mysterious failures for
621 fdisk, mount and other programs reading /proc/partitions.
625 ATA/IDE/MFM/RLL support
627 If you say Y here, your kernel will be able to manage low cost mass
628 storage units such as ATA/(E)IDE and ATAPI units. The most common
629 cases are IDE hard drives and ATAPI CD-ROM drives.
631 If your system is pure SCSI and doesn't use these interfaces, you
634 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
635 for mass storage units such as hard disks. It was designed by
636 Western Digital and Compaq Computer in 1984. It was then named
637 ST506. Quite a number of disks use the IDE interface.
639 AT Attachment (ATA) is the superset of the IDE specifications.
640 ST506 was also called ATA-1.
642 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
643 ATA-3. It provides support for larger disks (up to 8.4GB by means of
644 the LBA standard), more disks (4 instead of 2) and for other mass
645 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
646 ATA-4 and provides faster (and more CPU friendly) transfer modes
647 than previous PIO (Programmed processor Input/Output) from previous
648 ATA/IDE standards by means of fast DMA controllers.
650 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
651 CD-ROM drives, similar in many respects to the SCSI protocol.
653 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
654 designed in order to prevent data corruption and disk crash by
655 detecting pre hardware failure conditions (heat, access time, and
656 the like...). Disks built since June 1995 may follow this standard.
657 The kernel itself don't manage this; however there are quite a
658 number of user programs such as smart that can query the status of
659 SMART parameters disk.
661 If you want to compile this driver as a module ( = code which can be
662 inserted in and removed from the running kernel whenever you want),
663 say M here and read <file:Documentation/modules.txt>. The module
664 will be called ide.o.
666 For further information, please read <file:Documentation/ide.txt>.
670 Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
672 If you say Y here, you will use the full-featured IDE driver to
673 control up to ten ATA/IDE interfaces, each being able to serve a
674 "master" and a "slave" device, for a total of up to twenty ATA/IDE
675 disk/cdrom/tape/floppy drives.
677 Useful information about large (>540 MB) IDE disks, multiple
678 interfaces, what to do if ATA/IDE devices are not automatically
679 detected, sound card ATA/IDE ports, module support, and other
680 topics, is contained in <file:Documentation/ide.txt>. For detailed
681 information about hard drives, consult the Disk-HOWTO and the
682 Multi-Disk-HOWTO, available from
683 <http://www.tldp.org/docs.html#howto>.
685 To fine-tune ATA/IDE drive/interface parameters for improved
686 performance, look for the hdparm package at
687 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
689 If you want to compile this driver as a module ( = code which can be
690 inserted in and removed from the running kernel whenever you want),
691 say M here and read <file:Documentation/modules.txt> and
692 <file:Documentation/ide.txt>. The module will be called ide-mod.o.
693 Do not compile this driver as a module if your root file system (the
694 one containing the directory /) is located on an IDE device.
696 If you have one or more IDE drives, say Y or M here. If your system
697 has no IDE drives, or if memory requirements are really tight, you
698 could say N here, and select the "Old hard disk driver" below
699 instead to save about 13 KB of memory in the kernel.
701 Support for SATA (deprecated; conflicts with libata SATA driver)
702 CONFIG_BLK_DEV_IDE_SATA
703 There are two drivers for Serial ATA controllers.
705 The main driver, "libata", exists inside the SCSI subsystem
706 and supports most modern SATA controllers.
708 The IDE driver (which you are currently configuring) supports
709 a few first-generation SATA controllers.
711 In order to eliminate conflicts between the two subsystems,
712 this config option enables the IDE driver's SATA support.
713 Normally this is disabled, as it is preferred that libata
714 supports SATA controllers, and this (IDE) driver supports
719 Old hard disk (MFM/RLL/IDE) driver
720 CONFIG_BLK_DEV_HD_ONLY
721 There are two drivers for MFM/RLL/IDE hard disks. Most people use
722 the newer enhanced driver, but this old one is still around for two
723 reasons. Some older systems have strange timing problems and seem to
724 work only with the old driver (which itself does not work with some
725 newer systems). The other reason is that the old driver is smaller,
726 since it lacks the enhanced functionality of the new one. This makes
727 it a good choice for systems with very tight memory restrictions, or
728 for systems with only older MFM/RLL/ESDI drives. Choosing the old
729 driver can save 13 KB or so of kernel memory.
731 If you are unsure, then just choose the Enhanced IDE/MFM/RLL driver
732 instead of this one. For more detailed information, read the
733 Disk-HOWTO, available from
734 <http://www.tldp.org/docs.html#howto>.
736 Use old disk-only driver on primary interface
737 CONFIG_BLK_DEV_HD_IDE
738 There are two drivers for MFM/RLL/IDE disks. Most people use just
739 the new enhanced driver by itself. This option however installs the
740 old hard disk driver to control the primary IDE/disk interface in
741 the system, leaving the new enhanced IDE driver to take care of only
742 the 2nd/3rd/4th IDE interfaces. Doing this will prevent you from
743 having an IDE/ATAPI CD-ROM or tape drive connected to the primary
744 IDE interface. Choosing this option may be useful for older systems
745 which have MFM/RLL/ESDI controller+drives at the primary port
746 address (0x1f0), along with IDE drives at the secondary/3rd/4th port
749 Normally, just say N here; you will then use the new driver for all
752 Include IDE/ATA-2 DISK support
753 CONFIG_BLK_DEV_IDEDISK
754 This will include enhanced support for MFM/RLL/IDE hard disks. If
755 you have a MFM/RLL/IDE disk, and there is no special reason to use
756 the old hard disk driver instead, say Y. If you have an SCSI-only
757 system, you can say N here.
759 If you want to compile this driver as a module ( = code which can be
760 inserted in and removed from the running kernel whenever you want),
761 say M here and read <file:Documentation/modules.txt>. The module
762 will be called ide-disk.o. Do not compile this driver as a module
763 if your root file system (the one containing the directory /) is
764 located on the IDE disk. If unsure, say Y.
766 Use multi-mode by default
767 CONFIG_IDEDISK_MULTI_MODE
768 If you get this error, try to say Y here:
770 hda: set_multmode: status=0x51 { DriveReady SeekComplete Error }
771 hda: set_multmode: error=0x04 { DriveStatusError }
777 Support for outboard IDE disks, tape drives, and CD-ROM drives
778 connected through a PCMCIA card.
780 This driver is also available as a module ( = code which can be
781 inserted in and removed from the running kernel whenever you want).
782 If you want to compile it as a module, say M here and read
783 <file:Documentation/modules.txt>. The module will be called
786 Cardbus IDE support (Delkin/ASKA/Workbit)
787 CONFIG_BLK_DEV_DELKIN
788 Support for Delkin/ASKA/Workbit cardbus CompactFlash Adapters.
789 This may also work for similar SD and XD adapters. If you want
790 to be able to use one of these, then say M here. The module will
791 be called delkin_cb.o
793 Include IDE/ATAPI CD-ROM support
795 If you have a CD-ROM drive using the ATAPI protocol, say Y. ATAPI is
796 a newer protocol used by IDE CD-ROM and TAPE drives, similar to the
797 SCSI protocol. Most new CD-ROM drives use ATAPI, including the
798 NEC-260, Mitsumi FX400, Sony 55E, and just about all non-SCSI
799 double(2X) or better speed drives.
801 If you say Y here, the CD-ROM drive will be identified at boot time
802 along with other IDE devices, as "hdb" or "hdc", or something
803 similar (check the boot messages with dmesg). If this is your only
804 CD-ROM drive, you can say N to all other CD-ROM options, but be sure
805 to say Y or M to "ISO 9660 CD-ROM file system support".
807 Note that older versions of LILO (LInux LOader) cannot properly deal
808 with IDE/ATAPI CD-ROMs, so install LILO 16 or higher, available from
809 <ftp://brun.dyndns.org/pub/linux/lilo/>.
811 If you want to compile the driver as a module ( = code which can be
812 inserted in and removed from the running kernel whenever you want),
813 say M here and read <file:Documentation/modules.txt>. The module
814 will be called ide-cd.o.
816 Include IDE/ATAPI TAPE support
817 CONFIG_BLK_DEV_IDETAPE
818 If you have an IDE tape drive using the ATAPI protocol, say Y.
819 ATAPI is a newer protocol used by IDE tape and CD-ROM drives,
820 similar to the SCSI protocol. If you have an SCSI tape drive
821 however, you can say N here.
823 You should also say Y if you have an OnStream DI-30 tape drive; this
824 will not work with the SCSI protocol, until there is support for the
825 SC-30 and SC-50 versions.
827 If you say Y here, the tape drive will be identified at boot time
828 along with other IDE devices, as "hdb" or "hdc", or something
829 similar, and will be mapped to a character device such as "ht0"
830 (check the boot messages with dmesg). Be sure to consult the
831 <file:drivers/ide/ide-tape.c> and <file:Documentation/ide.txt> files
832 for usage information.
834 If you want to compile the driver as a module ( = code which can be
835 inserted in and removed from the running kernel whenever you want),
836 say M here and read <file:Documentation/modules.txt>. The module
837 will be called ide-tape.o.
839 Include IDE/ATAPI FLOPPY support
840 CONFIG_BLK_DEV_IDEFLOPPY
841 If you have an IDE floppy drive which uses the ATAPI protocol,
842 answer Y. ATAPI is a newer protocol used by IDE CD-ROM/tape/floppy
843 drives, similar to the SCSI protocol.
845 The LS-120 and the IDE/ATAPI Iomega ZIP drive are also supported by
846 this driver. For information about jumper settings and the question
847 of when a ZIP drive uses a partition table, see
848 <http://www.win.tue.nl/~aeb/linux/zip/zip-1.html>.
849 (ATAPI PD-CD/CDR drives are not supported by this driver; support
850 for PD-CD/CDR drives is available if you answer Y to
851 "SCSI emulation support", below).
853 If you say Y here, the FLOPPY drive will be identified along with
854 other IDE devices, as "hdb" or "hdc", or something similar (check
855 the boot messages with dmesg).
857 If you want to compile the driver as a module ( = code which can be
858 inserted in and removed from the running kernel whenever you want),
859 say M here and read <file:Documentation/modules.txt>. The module
860 will be called ide-floppy.o.
862 AWARD Bios Work-Around
863 CONFIG_IDEDISK_STROKE
864 Should you have a system w/ an AWARD Bios and your drives are larger
865 than 32GB and it will not boot, one is required to perform a few OEM
866 operations first. The option is called "STROKE" because it allows
867 one to "soft clip" the drive to work around a barrier limit. For
868 Maxtor drives it is called "jumpon.exe". Please search Maxtor's
869 web-site for "JUMPON.EXE". IBM has a similar tool at:
870 <http://www.storage.ibm.com/hdd/support/download.htm>.
872 If you are unsure, say N here.
875 CONFIG_IDE_TASK_IOCTL
876 This is a direct raw access to the media. It is a complex but
877 elegant solution to test and validate the domain of the hardware and
878 perform below the driver data recover if needed. This is the most
879 basic form of media-forensics.
881 If you are unsure, say N here.
884 CONFIG_IDE_TASKFILE_IO
885 This is the "Jewel" of the patch. It will go away and become the new
886 driver core. Since all the chipsets/host side hardware deal w/ their
887 exceptions in "their local code" currently, adoption of a
888 standardized data-transport is the only logical solution.
889 Additionally we packetize the requests and gain rapid performance and
890 a reduction in system latency. Additionally by using a memory struct
891 for the commands we can redirect to a MMIO host hardware in the next
892 generation of controllers, specifically second generation Ultra133
895 Since this is a major transition, it was deemed necessary to make the
896 driver paths buildable in separate models. Therefore if using this
897 option fails for your arch then we need to address the needs for that
900 If you want to test this functionality, say Y here.
903 CONFIG_BLK_DEV_IDEDMA_FORCED
904 This is an old piece of lost code from Linux 2.0 Kernels.
906 Generally say N here.
909 CONFIG_IDEDMA_ONLYDISK
910 This is used if you know your ATAPI Devices are going to fail DMA
913 Generally say N here.
915 SCSI emulation support
916 CONFIG_BLK_DEV_IDESCSI
917 This will provide SCSI host adapter emulation for IDE ATAPI devices,
918 and will allow you to use a SCSI device driver instead of a native
921 This is useful if you have an ATAPI device for which no native
922 driver has been written (for example, an ATAPI PD-CD or CDR drive);
923 you can then use this emulation together with an appropriate SCSI
924 device driver. In order to do this, say Y here and to "SCSI support"
925 and "SCSI generic support", below. You must then provide the kernel
926 command line "hdx=scsi" (try "man bootparam" or see the
927 documentation of your boot loader (lilo or loadlin) about how to
928 pass options to the kernel at boot time) for devices if you want the
929 native EIDE sub-drivers to skip over the native support, so that
930 this SCSI emulation can be used instead. This is required for use of
933 Note that this option does NOT allow you to attach SCSI devices to a
934 box that doesn't have a SCSI host adapter installed.
936 If both this SCSI emulation and native ATAPI support are compiled
937 into the kernel, the native support will be used.
939 This driver is also available as a module ( = code which can be
940 inserted in and removed from the running kernel whenever you want).
941 If you want to compile it as a module, say M here and read
942 <file:Documentation/modules.txt>. The module will be called
945 Use the NOOP Elevator (WARNING)
946 CONFIG_BLK_DEV_ELEVATOR_NOOP
947 If you are using a raid class top-level driver above the ATA/IDE core,
948 one may find a performance boost by preventing a merging and re-sorting
954 CONFIG_BLK_DEV_ISAPNP
955 If you have an ISA EIDE card that is PnP (Plug and Play) and
956 requires setup first before scanning for devices, say Y here.
960 CMD640 chipset bugfix/support
961 CONFIG_BLK_DEV_CMD640
962 The CMD-Technologies CMD640 IDE chip is used on many common 486 and
963 Pentium motherboards, usually in combination with a "Neptune" or
964 "SiS" chipset. Unfortunately, it has a number of rather nasty
965 design flaws that can cause severe data corruption under many common
966 conditions. Say Y here to include code which tries to automatically
967 detect and correct the problems under Linux. This option also
968 enables access to the secondary IDE ports in some CMD640 based
971 This driver will work automatically in PCI based systems (most new
972 systems have PCI slots). But if your system uses VESA local bus
973 (VLB) instead of PCI, you must also supply a kernel boot parameter
974 to enable the CMD640 bugfix/support: "ide0=cmd640_vlb". (Try "man
975 bootparam" or see the documentation of your boot loader about how to
976 pass options to the kernel.)
978 The CMD640 chip is also used on add-in cards by Acculogic, and on
979 the "CSA-6400E PCI to IDE controller" that some people have. For
980 details, read <file:Documentation/ide.txt>.
982 CMD640 enhanced support
983 CONFIG_BLK_DEV_CMD640_ENHANCED
984 This option includes support for setting/autotuning PIO modes and
985 prefetch on CMD640 IDE interfaces. For details, read
986 <file:Documentation/ide.txt>. If you have a CMD640 IDE interface
987 and your BIOS does not already do this for you, then say Y here.
990 RZ1000 chipset bugfix/support
991 CONFIG_BLK_DEV_RZ1000
992 The PC-Technologies RZ1000 IDE chip is used on many common 486 and
993 Pentium motherboards, usually along with the "Neptune" chipset.
994 Unfortunately, it has a rather nasty design flaw that can cause
995 severe data corruption under many conditions. Say Y here to include
996 code which automatically detects and corrects the problem under
997 Linux. This may slow disk throughput by a few percent, but at least
998 things will operate 100% reliably.
1000 Generic PCI IDE chipset support
1001 CONFIG_BLK_DEV_IDEPCI
1002 Say Y here for PCI systems which use IDE drive(s).
1003 This option helps the IDE driver to automatically detect and
1004 configure all PCI-based IDE interfaces in your system.
1006 Support for sharing PCI IDE interrupts
1007 CONFIG_IDEPCI_SHARE_IRQ
1008 Some ATA/IDE chipsets have hardware support which allows for
1009 sharing a single IRQ with other cards. To enable support for
1010 this in the ATA/IDE driver, say Y here.
1012 It is safe to say Y to this question, in most cases.
1015 Generic PCI bus-master DMA support
1016 CONFIG_BLK_DEV_IDEDMA_PCI
1017 If your PCI system uses IDE drive(s) (as opposed to SCSI, say) and
1018 is capable of bus-master DMA operation (most Pentium PCI systems),
1019 you will want to say Y here to reduce CPU overhead. You can then use
1020 the "hdparm" utility to enable DMA for drives for which it was not
1021 enabled automatically. By default, DMA is not enabled automatically
1022 for these drives, but you can change that by saying Y to the
1023 following question "Use DMA by default when available". You can get
1024 the latest version of the hdparm utility from
1025 <ftp://ibiblio.org/pub/Linux/system/hardware/>.
1027 Read the comments at the beginning of <file:drivers/ide/ide-dma.c>
1028 and the file <file:Documentation/ide.txt> for more information.
1030 It is safe to say Y to this question.
1032 Good-Bad DMA Model-Firmware (WIP)
1033 CONFIG_IDEDMA_NEW_DRIVE_LISTINGS
1034 If you say Y here, the model and firmware revision of your drive
1035 will be compared against a blacklist of buggy drives that claim to
1036 be (U)DMA capable but aren't. This is a blanket on/off test with no
1037 speed limit options.
1039 Straight GNU GCC 2.7.3/2.8.X compilers are known to be safe;
1040 whereas, many versions of EGCS have a problem and miscompile if you
1045 Attempt to HACK around Chipsets that TIMEOUT (WIP)
1046 CONFIG_BLK_DEV_IDEDMA_TIMEOUT
1047 If you say Y here, this is a NASTY UGLY HACK!
1049 We have to issue an abort and requeue the request DMA engine got
1050 turned off by a goofy ASIC, and we have to clean up the mess, and
1051 here is as good as any. Do it globally for all chipsets.
1055 Boot off-board chipsets first support
1056 CONFIG_BLK_DEV_OFFBOARD
1057 Normally, IDE controllers built into the motherboard (on-board
1058 controllers) are assigned to ide0 and ide1 while those on add-in PCI
1059 cards (off-board controllers) are relegated to ide2 and ide3.
1060 Answering Y here will allow you to reverse the situation, with
1061 off-board controllers on ide0/1 and on-board controllers on ide2/3.
1062 This can improve the usability of some boot managers such as lilo
1063 when booting from a drive on an off-board controller.
1065 If you say Y here, and you actually want to reverse the device scan
1066 order as explained above, you also need to issue the kernel command
1067 line option "ide=reverse". (Try "man bootparam" or see the
1068 documentation of your boot loader (lilo or loadlin) about how to
1069 pass options to the kernel at boot time.)
1071 Note that, if you do this, the order of the hd* devices will be
1072 rearranged which may require modification of fstab and other files.
1076 Use PCI DMA by default when available
1077 CONFIG_IDEDMA_PCI_AUTO
1078 Prior to kernel version 2.1.112, Linux used to automatically use
1079 DMA for IDE drives and chipsets which support it. Due to concerns
1080 about a couple of cases where buggy hardware may have caused damage,
1081 the default is now to NOT use DMA automatically. To revert to the
1082 previous behaviour, say Y to this question.
1084 If you suspect your hardware is at all flakey, say N here.
1085 Do NOT email the IDE kernel people regarding this issue!
1087 It is normally safe to answer Y to this question unless your
1088 motherboard uses a VIA VP2 chipset, in which case you should say N.
1090 IGNORE word93 Validation BITS
1092 There are unclear terms in ATA-4 and ATA-5 standards how certain
1093 hardware (an 80c ribbon) should be detected. Different interpretations
1094 of the standards have been released in hardware. This causes problems:
1095 for example, a host with Ultra Mode 4 (or higher) will not run
1096 in that mode with an 80c ribbon.
1098 If you are experiencing compatibility or performance problems, you
1099 MAY try to answering Y here. However, it does not necessarily solve
1100 any of your problems, it could even cause more of them.
1102 It is normally safe to answer Y; however, the default is N.
1104 ATA Work(s) In Progress (EXPERIMENTAL)
1105 CONFIG_IDEDMA_PCI_WIP
1106 If you enable this you will be able to use and test highly
1107 developmental projects. If you say N, the configurator will
1108 simply skip those options.
1110 It is SAFEST to say N to this question.
1112 Asynchronous DMA support (EXPERIMENTAL)
1114 Please read the comments at the top of
1115 <file:drivers/ide/ide-adma.c>.
1117 Pacific Digital A-DMA support (EXPERIMENTAL)
1118 CONFIG_BLK_DEV_PDC_ADMA
1119 Please read the comments at the top of <file:drivers/ide/setup-pci.c>.
1121 3ware Hardware ATA-RAID support
1122 CONFIG_BLK_DEV_3W_XXXX_RAID
1123 3ware is the only hardware ATA-Raid product in Linux to date.
1124 This card is 2,4, or 8 channel master mode support only.
1125 SCSI support required!!!
1127 <http://www.3ware.com/>
1129 Please read the comments at the top of
1130 <file:drivers/scsi/3w-xxxx.c>.
1132 If you want to compile the driver as a module ( = code which can be
1133 inserted in and removed from the running kernel whenever you want),
1134 say M here and read <file:Documentation/modules.txt>. The module
1135 will be called 3w-xxxx.o.
1137 AEC62XX chipset support
1138 CONFIG_BLK_DEV_AEC62XX
1139 This driver adds up to 4 more EIDE devices sharing a single
1140 interrupt. This add-on card is a bootable PCI UDMA controller. In
1141 order to get this card to initialize correctly in some cases, you
1142 should say Y here, and preferably also to "Use DMA by default when
1145 The ATP850U/UF is an UltraDMA 33 chipset base.
1146 The ATP860 is an UltraDMA 66 chipset base.
1147 The ATP860M(acintosh) version is an UltraDMA 66 chipset base.
1149 Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
1150 If you say Y here, then say Y to "Use DMA by default when available"
1153 AEC62XX Tuning support
1154 CONFIG_AEC62XX_TUNING
1155 Please read the comments at the top of <file:drivers/ide/pci/aec62xx.c>.
1158 ALI M15x3 chipset support
1159 CONFIG_BLK_DEV_ALI15X3
1160 This driver ensures (U)DMA support for ALI 1533, 1543 and 1543C
1161 onboard chipsets. It also tests for Simplex mode and enables
1162 normal dual channel support.
1164 If you say Y here, you also need to say Y to "Use DMA by default
1165 when available", above. Please read the comments at the top of
1166 <file:drivers/ide/pci/alim15x3.c>.
1170 ALI M15x3 WDC support (DANGEROUS)
1172 This allows for UltraDMA support for WDC drives that ignore CRC
1173 checking. You are a fool for enabling this option, but there have
1174 been requests. DO NOT COMPLAIN IF YOUR DRIVE HAS FS CORRUPTION, IF
1175 YOU ENABLE THIS! No one will listen, just laugh for ignoring this
1178 Using this option can allow WDC drives to run at ATA-4/5 transfer
1179 rates with only an ATA-2 support structure.
1183 AMD and nVidia IDE support
1184 CONFIG_BLK_DEV_AMD74XX
1185 This driver adds explicit support for AMD-7xx and AMD-8111 chips
1186 and also for the nVidia nForce chip. This allows the kernel to
1187 change PIO, DMA and UDMA speeds and to configure the chip to
1188 optimum performance.
1190 If you say Y here, you also need to say Y to "Use DMA by default
1191 when available", above.
1192 Please read the comments at the top of <file:drivers/ide/pci/amd74xx.c>.
1196 AMD Viper ATA-66 Override support (WIP)
1197 CONFIG_AMD74XX_OVERRIDE
1198 This option auto-forces the ata66 flag.
1199 This effect can be also invoked by calling "idex=ata66"
1202 ATI IXP chipset IDE support
1203 CONFIG_BLK_DEV_ATIIXP
1204 This driver adds explicit support for ATI IXP chipset.
1205 This allows the kernel to change PIO, DMA and UDMA speeds
1206 and to configure the chip to optimum performance.
1208 Say Y here if you have an ATI IXP chipset IDE controller.
1210 CMD64X/CMD680 chipset support
1211 CONFIG_BLK_DEV_CMD64X
1212 Say Y here if you have an IDE controller which uses any of these
1213 chipsets: CMD643, CMD646 and CMD648.
1215 Compaq Triflex IDE support
1216 CONFIG_BLK_DEV_TRIFLEX
1217 Say Y here if you have a Compaq Triflex IDE controller, such
1218 as those commonly found on Compaq Pentium-Pro systems
1220 If you want to compile it as a module, say M here and read
1221 <file:Documentation/modules.txt>. The module will be called
1224 CY82C693 chipset support
1225 CONFIG_BLK_DEV_CY82C693
1226 This driver adds detection and support for the CY82C693 chipset
1227 used on Digital's PC-Alpha 164SX boards.
1229 If you say Y here, you need to say Y to "Use DMA by default
1230 when available" as well.
1232 Cyrix CS5530 MediaGX chipset support
1233 CONFIG_BLK_DEV_CS5530
1234 Include support for UDMA on the Cyrix MediaGX 5530 chipset. This
1235 will automatically be detected and configured if found.
1237 It is safe to say Y to this question.
1239 People with SCSI-only systems should say N here. If unsure, say Y.
1241 HPT34X chipset support
1242 CONFIG_BLK_DEV_HPT34X
1243 This driver adds up to 4 more EIDE devices sharing a single
1244 interrupt. The HPT343 chipset in its current form is a non-bootable
1245 controller; the HPT345/HPT363 chipset is a bootable (needs BIOS FIX)
1246 PCI UDMA controllers. This driver requires dynamic tuning of the
1247 chipset during the ide-probe at boot time. It is reported to support
1248 DVD II drives, by the manufacturer.
1250 HPT34X AUTODMA support (WIP)
1251 CONFIG_HPT34X_AUTODMA
1252 This is a dangerous thing to attempt currently! Please read the
1253 comments at the top of <file:drivers/ide/pci/hpt34x.c>. If you say Y
1254 here, then say Y to "Use DMA by default when available" as well.
1258 HPT36X/37X chipset support
1259 CONFIG_BLK_DEV_HPT366
1260 HPT366 is an Ultra DMA chipset for ATA-66.
1261 HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
1262 HPT370 is an Ultra DMA chipset for ATA-100.
1263 HPT372 is an Ultra DMA chipset for ATA-133.
1264 HPT374 is an Ultra DMA chipset for ATA-133.
1266 This driver adds up to 4 more EIDE devices sharing a single
1269 The HPT366 chipset in its current form is bootable. One solution
1270 for this problem are special LILO commands for redirecting the
1271 reference to device 0x80. The other solution is to say Y to "Boot
1272 off-board chipsets first support" (CONFIG_BLK_DEV_OFFBOARD) unless
1273 your mother board has the chipset natively mounted. Regardless one
1274 should use the fore mentioned option and call at LILO or include
1275 "ide=reverse" in LILO's append-line.
1277 This driver requires dynamic tuning of the chipset during the
1278 ide-probe at boot. It is reported to support DVD II drives, by the
1281 NS87415 chipset support (EXPERIMENTAL)
1282 CONFIG_BLK_DEV_NS87415
1283 This driver adds detection and support for the NS87415 chip
1284 (used in SPARC64, among others).
1286 Please read the comments at the top of <file:drivers/ide/pci/ns87415.c>.
1288 OPTi 82C621 chipset enhanced support (EXPERIMENTAL)
1289 CONFIG_BLK_DEV_OPTI621
1290 This is a driver for the OPTi 82C621 EIDE controller.
1291 Please read the comments at the top of <file:drivers/ide/pci/opti621.c>.
1293 National SCx200 chipset support
1294 CONFIG_BLK_DEV_SC1200
1295 This driver adds support for the built in IDE on the National
1296 SCx200 series of embedded x86 "Geode" systems
1298 If you want to compile it as a module, say M here and read
1299 <file:Documentation/modules.txt>. The module will be called
1302 ServerWorks OSB4/CSB5 chipset support
1303 CONFIG_BLK_DEV_SVWKS
1304 This driver adds PIO/(U)DMA support for the ServerWorks OSB4/CSB5
1307 SGI IOC4 chipset support
1308 CONFIG_BLK_DEV_SGIIOC4
1309 This driver adds PIO & MultiMode DMA-2 support for the SGI IOC4
1310 chipset. Please say Y here, if you have an Altix System from
1311 Silicon Graphics Inc.
1313 Intel PIIXn chipsets support
1315 This driver adds PIO mode setting and tuning for all PIIX IDE
1316 controllers by Intel. Since the BIOS can sometimes improperly tune
1317 PIO 0-4 mode settings, this allows dynamic tuning of the chipset
1318 via the standard end-user tool 'hdparm'.
1320 Please read the comments at the top of <file:drivers/ide/pci/piix.c>.
1324 Promise PDC202{46|62|65|67} support
1325 CONFIG_BLK_DEV_PDC202XX_OLD
1326 Promise Ultra 33 [PDC20246]
1327 Promise Ultra 66 [PDC20262]
1328 Promise FastTrak 66 [PDC20263]
1329 Promise MB Ultra 100 [PDC20265]
1330 Promise Ultra 100 [PDC20267]
1332 This driver adds up to 4 more EIDE devices sharing a single
1333 interrupt. This add-on card is a bootable PCI UDMA controller. Since
1334 multiple cards can be installed and there are BIOS ROM problems that
1335 happen if the BIOS revisions of all installed cards (three-max) do
1336 not match, the driver attempts to do dynamic tuning of the chipset
1337 at boot-time for max-speed. Ultra33 BIOS 1.25 or newer is required
1338 for more than one card. This card may require that you say Y to
1339 "Force (U)DMA burst transfers" (old name: "Special UDMA Feature").
1341 If you say Y here, you need to say Y to "Use DMA by default when
1344 Please read the comments at the top of
1345 <file:drivers/ide/pci/pdc202xx_old.c>.
1349 Promise PDC202{68|69|70|71|75|76|77} support
1350 CONFIG_BLK_DEV_PDC202XX_NEW
1351 Promise Ultra 100 TX2 [PDC20268]
1352 Promise Ultra 133 PTX2 [PDC20269]
1353 Promise FastTrak LP/TX2/TX4 [PDC20270]
1354 Promise FastTrak TX2000 [PDC20271]
1355 Promise MB Ultra 133 [PDC20275]
1356 Promise MB FastTrak 133 [PDC20276]
1357 Promise FastTrak 133 [PDC20277]
1359 This driver adds up to 4 more EIDE devices sharing a single
1360 interrupt. This device is a bootable PCI UDMA controller. Since
1361 multiple cards can be installed and there are BIOS ROM problems that
1362 happen if the BIOS revisions of all installed cards (max of five) do
1363 not match, the driver attempts to do dynamic tuning of the chipset
1364 at boot-time for max speed.
1366 If you say Y here, you need to say Y to "Use DMA by default when
1371 Force (U)DMA burst transfers
1372 CONFIG_PDC202XX_BURST
1373 This option causes the pdc202xx_old driver to enable UDMA modes on the
1374 PDC202xx even when the PDC202xx BIOS has not done so.
1376 It was originally designed for the PDC20246/Ultra33, whose BIOS will
1377 only setup UDMA on the first two PDC20246 cards. It has also been
1378 used successfully on a PDC20265/Ultra100, allowing use of UDMA modes
1379 when the PDC20265 BIOS has been disabled (for faster boot up).
1381 Please read the comments at the top of
1382 <file:drivers/ide/pci/pdc202xx_old.c>.
1386 Ignore BIOS port disabled setting on FastTrak
1387 CONFIG_PDC202XX_FORCE
1390 PDC202{46|62|63|65|67}
1391 (pdc202xx_old driver)
1394 (pdc202xx_new driver)
1396 Say Y unless you want to use Promise proprietary driver.
1398 SiS5513 chipset support
1399 CONFIG_BLK_DEV_SIS5513
1400 This driver ensures (U)DMA support for SIS5513 chipset family based
1403 The following chipsets are supported:
1404 ATA16: SiS5511, SiS5513
1405 ATA33: SiS5591, SiS5597, SiS5598, SiS5600
1406 ATA66: SiS530, SiS540, SiS620, SiS630, SiS640
1407 ATA100: SiS635, SiS645, SiS650, SiS730, SiS735, SiS740,
1410 If you say Y here, you need to say Y to "Use DMA by default when
1413 Please read the comments at the top of <file:drivers/ide/pci/sis5513.c>.
1415 Silicon Image chipset support
1416 CONFIG_BLK_DEV_SIIMAGE
1417 This driver provides (U)DMA support for the SII3112 SATA controllers and
1418 for the CMD/SI680 UDMA/DMA ATA controller.
1420 SLC90E66 chipset support
1421 CONFIG_BLK_DEV_SLC90E66
1422 This driver ensures (U)DMA support for Victroy66 SouthBridges for
1423 SMsC with Intel NorthBridges. This is an Ultra66 based chipset.
1424 The nice thing about it is that you can mix Ultra/DMA/PIO devices
1425 and it will handle timing cycles. Since this is an improved
1426 look-a-like to the PIIX4 it should be a nice addition.
1428 If you say Y here, you need to say Y to "Use DMA by default when
1431 Please read the comments at the top of
1432 <file:drivers/ide/pci/slc90e66.c>.
1434 Winbond SL82c105 support
1435 CONFIG_BLK_DEV_SL82C105
1436 If you have a Winbond SL82c105 IDE controller, say Y here to enable
1437 special configuration for this chip. This is common on various CHRP
1438 motherboards, but could be used elsewhere. If in doubt, say Y.
1440 Tekram TRM290 chipset support
1441 CONFIG_BLK_DEV_TRM290
1442 This driver adds support for bus master DMA transfers
1443 using the Tekram TRM290 PCI IDE chip. Volunteers are
1444 needed for further tweaking and development.
1445 Please read the comments at the top of <file:drivers/ide/pci/trm290.c>.
1447 VIA82CXXX chipset support
1448 CONFIG_BLK_DEV_VIA82CXXX
1449 This allows you to configure your chipset for a better use while
1450 running PIO/(U)DMA, it will allow you to enable efficiently the
1451 second channel dma usage, as it may not be set by BIOS. It will try
1452 to set fifo configuration at its best. It will allow you to get
1453 information from /proc/ide/via provided you enabled "/proc file
1456 Please read the comments at the top of
1457 <file:drivers/ide/pci/via82cxxx.c>.
1459 If you say Y here, then say Y to "Use DMA by default when available"
1464 RapIDE interface support
1465 CONFIG_BLK_DEV_IDE_RAPIDE
1466 Say Y here if you want to support the Yellowstone RapIDE controller
1467 manufactured for use with Acorn computers.
1469 Other IDE chipset support
1471 Say Y here if you want to include enhanced support for various IDE
1472 interface chipsets used on motherboards and add-on cards. You can
1473 then pick your particular IDE chip from among the following options.
1474 This enhanced support may be necessary for Linux to be able to
1475 access the 3rd/4th drives in some systems. It may also enable
1476 setting of higher speed I/O rates to improve system performance with
1477 these chipsets. Most of these also require special kernel boot
1478 parameters to actually turn on the support at runtime; you can find
1479 a list of these in the file <file:Documentation/ide.txt>.
1481 People with SCSI-only systems can say N here.
1483 Generic 4 drives/port support
1484 CONFIG_BLK_DEV_4DRIVES
1485 Certain older chipsets, including the Tekram 690CD, use a single set
1486 of I/O ports at 0x1f0 to control up to four drives, instead of the
1487 customary two drives per port. Support for this can be enabled at
1488 runtime using the "ide0=four" kernel boot parameter if you say Y
1492 CONFIG_BLK_DEV_ALI14XX
1493 This driver is enabled at runtime using the "ide0=ali14xx" kernel
1494 boot parameter. It enables support for the secondary IDE interface
1495 of the ALI M1439/1443/1445/1487/1489 chipsets, and permits faster
1496 I/O speeds to be set as well. See the files
1497 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/ali14xx.c> for
1501 CONFIG_BLK_DEV_DTC2278
1502 This driver is enabled at runtime using the "ide0=dtc2278" kernel
1503 boot parameter. It enables support for the secondary IDE interface
1504 of the DTC-2278 card, and permits faster I/O speeds to be set as
1505 well. See the <file:Documentation/ide.txt> and
1506 <file:drivers/ide/legacy/dtc2278.c> files for more info.
1508 Holtek HT6560B support
1509 CONFIG_BLK_DEV_HT6560B
1510 This driver is enabled at runtime using the "ide0=ht6560b" kernel
1511 boot parameter. It enables support for the secondary IDE interface
1512 of the Holtek card, and permits faster I/O speeds to be set as well.
1513 See the <file:Documentation/ide.txt> and
1514 <file:drivers/ide/legacy/ht6560b.c> files for more info.
1516 PROMISE DC4030 support (EXPERIMENTAL)
1517 CONFIG_BLK_DEV_PDC4030
1518 This driver provides support for the secondary IDE interface and
1519 cache of Promise IDE chipsets, e.g. DC4030 and DC5030. This driver
1520 is known to incur timeouts/retries during heavy I/O to drives
1521 attached to the secondary interface. CD-ROM and TAPE devices are
1522 not supported yet. This driver is enabled at runtime using the
1523 "ide0=dc4030" kernel boot parameter. See the
1524 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/pdc4030.c> files
1528 CONFIG_BLK_DEV_QD65XX
1529 This driver is enabled at runtime using the "ide0=qd65xx" kernel
1530 boot parameter. It permits faster I/O speeds to be set. See the
1531 <file:Documentation/ide.txt> and <file:drivers/ide/legacy/qd65xx.c> for
1535 CONFIG_BLK_DEV_UMC8672
1536 This driver is enabled at runtime using the "ide0=umc8672" kernel
1537 boot parameter. It enables support for the secondary IDE interface
1538 of the UMC-8672, and permits faster I/O speeds to be set as well.
1539 See the files <file:Documentation/ide.txt> and
1540 <file:drivers/ide/legacy/umc8672.c> for more info.
1542 Amiga Gayle IDE interface support
1543 CONFIG_BLK_DEV_GAYLE
1544 This is the IDE driver for the Amiga Gayle IDE interface. It supports
1545 both the `A1200 style' and `A4000 style' of the Gayle IDE interface,
1546 This includes builtin IDE interfaces on some Amiga models (A600,
1547 A1200, A4000, and A4000T), and IDE interfaces on the Zorro expansion
1548 bus (M-Tech E-Matrix 530 expansion card).
1549 Say Y if you have an Amiga with a Gayle IDE interface and want to use
1550 IDE devices (hard disks, CD-ROM drives, etc.) that are connected to it.
1551 Note that you also have to enable Zorro bus support if you want to
1552 use Gayle IDE interfaces on the Zorro expansion bus.
1554 Falcon IDE interface support
1555 CONFIG_BLK_DEV_FALCON_IDE
1556 This is the IDE driver for the builtin IDE interface on the Atari
1557 Falcon. Say Y if you have a Falcon and want to use IDE devices (hard
1558 disks, CD-ROM drives, etc.) that are connected to the builtin IDE
1561 Amiga Buddha/Catweasel/X-Surf IDE interface support (EXPERIMENTAL)
1562 CONFIG_BLK_DEV_BUDDHA
1563 This is the IDE driver for the IDE interfaces on the Buddha,
1564 Catweasel and X-Surf expansion boards. It supports up to two interfaces
1565 on the Buddha, three on the Catweasel and two on the X-Surf.
1567 Say Y if you have a Buddha or Catweasel expansion board and want to
1568 use IDE devices (hard disks, CD-ROM drives, etc.) that are connected
1569 to one of its IDE interfaces.
1571 Amiga IDE Doubler support (EXPERIMENTAL)
1572 CONFIG_BLK_DEV_IDEDOUBLER
1573 This driver provides support for the so-called `IDE doublers' (made
1574 by various manufacturers, e.g. Eyetech) that can be connected to the
1575 builtin IDE interface of some Amiga models. Using such an IDE
1576 doubler, you can connect up to four instead of two IDE devices on
1577 the Amiga's builtin IDE interface.
1579 Note that the normal Amiga Gayle IDE driver may not work correctly
1580 if you have an IDE doubler and don't enable this driver!
1582 Say Y if you have an IDE doubler. The driver is enabled at kernel
1583 runtime using the "ide=doubler" kernel boot parameter.
1585 Builtin PowerMac IDE support
1586 CONFIG_BLK_DEV_IDE_PMAC
1587 This driver provides support for the built-in IDE controller on
1588 most of the recent Apple Power Macintoshes and PowerBooks.
1591 PowerMac IDE DMA support
1592 CONFIG_BLK_DEV_IDEDMA_PMAC
1593 This option allows the driver for the built-in IDE controller on
1594 Power Macintoshes and PowerBooks to use DMA (direct memory access)
1595 to transfer data to and from memory. Saying Y is safe and improves
1598 Broadcom SiByte onboard IDE support
1599 CONFIG_BLK_DEV_IDE_SIBYTE
1600 Include the driver for on-board IDE on the SiByte Generic Bus. Note
1601 that this limits the number of IDE devices to 4 (ide0...ide3).
1604 CONFIG_BLK_DEV_IDEDMA_PMAC_AUTO
1605 This option allows the driver for the built-in IDE controller on
1606 Power Macintoshes and PowerBooks to use DMA automatically, without
1607 it having to be explicitly enabled. This option is provided because
1608 of concerns about a couple of cases where using DMA on buggy PC
1609 hardware may have caused damage. Saying Y should be safe on all
1612 Macintosh Quadra/Powerbook IDE interface support
1613 CONFIG_BLK_DEV_MAC_IDE
1614 This is the IDE driver for the builtin IDE interface on some m68k
1615 Macintosh models. It supports both the `Quadra style' (used in
1616 Quadra/ Centris 630 and Performa 588 models) and `Powerbook style'
1617 (used in the Powerbook 150 and 190 models) IDE interface.
1619 Say Y if you have such an Macintosh model and want to use IDE
1620 devices (hard disks, CD-ROM drives, etc.) that are connected to the
1621 builtin IDE interface.
1623 ICS IDE interface support
1624 CONFIG_BLK_DEV_IDE_ICSIDE
1625 On Acorn systems, say Y here if you wish to use the ICS IDE
1626 interface card. This is not required for ICS partition support.
1627 If you are unsure, say N to this.
1630 CONFIG_BLK_DEV_IDEDMA_ICS
1631 Say Y here if you want to add DMA (Direct Memory Access) support to
1634 Use ICS DMA by default
1635 CONFIG_IDEDMA_ICS_AUTO
1636 Prior to kernel version 2.1.112, Linux used to automatically use
1637 DMA for IDE drives and chipsets which support it. Due to concerns
1638 about a couple of cases where buggy hardware may have caused damage,
1639 the default is now to NOT use DMA automatically. To revert to the
1640 previous behaviour, say Y to this question.
1642 If you suspect your hardware is at all flakey, say N here.
1643 Do NOT email the IDE kernel people regarding this issue!
1645 XT hard disk support
1647 Very old 8 bit hard disk controllers used in the IBM XT computer
1648 will be supported if you say Y here.
1650 If you want to compile the driver as a module ( = code which can be
1651 inserted in and removed from the running kernel whenever you want),
1652 say M here and read <file:Documentation/modules.txt>. The module
1653 will be called xd.o.
1655 It's pretty unlikely that you have one of these: say N.
1657 PS/2 ESDI hard disk support
1659 Say Y here if you have a PS/2 machine with a MCA bus and an ESDI
1662 If you want to compile the driver as a module ( = code which can be
1663 inserted in and removed from the running kernel whenever you want),
1664 say M here and read <file:Documentation/modules.txt>. The module
1665 will be called ps2esdi.o.
1667 Mylex DAC960/DAC1100 PCI RAID Controller support
1668 CONFIG_BLK_DEV_DAC960
1669 This driver adds support for the Mylex DAC960, AcceleRAID, and
1670 eXtremeRAID PCI RAID controllers. See the file
1671 <file:Documentation/README.DAC960> for further information about
1674 If you want to compile the driver as a module ( = code which can be
1675 inserted in and removed from the running kernel whenever you want),
1676 say M here and read <file:Documentation/modules.txt>. The module
1677 will be called DAC960.o.
1679 Parallel port IDE device support
1681 There are many external CD-ROM and disk devices that connect through
1682 your computer's parallel port. Most of them are actually IDE devices
1683 using a parallel port IDE adapter. This option enables the PARIDE
1684 subsystem which contains drivers for many of these external drives.
1685 Read <file:Documentation/paride.txt> for more information.
1687 If you have said Y to the "Parallel-port support" configuration
1688 option, you may share a single port between your printer and other
1689 parallel port devices. Answer Y to build PARIDE support into your
1690 kernel, or M if you would like to build it as a loadable module. If
1691 your parallel port support is in a loadable module, you must build
1692 PARIDE as a module. If you built PARIDE support into your kernel,
1693 you may still build the individual protocol modules and high-level
1694 drivers as loadable modules. If you build this support as a module,
1695 it will be called paride.o.
1697 To use the PARIDE support, you must say Y or M here and also to at
1698 least one high-level driver (e.g. "Parallel port IDE disks",
1699 "Parallel port ATAPI CD-ROMs", "Parallel port ATAPI disks" etc.) and
1700 to at least one protocol driver (e.g. "ATEN EH-100 protocol",
1701 "MicroSolutions backpack protocol", "DataStor Commuter protocol"
1704 Parallel port IDE disks
1706 This option enables the high-level driver for IDE-type disk devices
1707 connected through a parallel port. If you chose to build PARIDE
1708 support into your kernel, you may answer Y here to build in the
1709 parallel port IDE driver, otherwise you should answer M to build
1710 it as a loadable module. The module will be called pd.o. You
1711 must also have at least one parallel port protocol driver in your
1712 system. Among the devices supported by this driver are the SyQuest
1713 EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
1714 hard drives from MicroSolutions.
1716 Parallel port ATAPI CD-ROMs
1718 This option enables the high-level driver for ATAPI CD-ROM devices
1719 connected through a parallel port. If you chose to build PARIDE
1720 support into your kernel, you may answer Y here to build in the
1721 parallel port ATAPI CD-ROM driver, otherwise you should answer M to
1722 build it as a loadable module. The module will be called pcd.o. You
1723 must also have at least one parallel port protocol driver in your
1724 system. Among the devices supported by this driver are the
1725 MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
1726 you have such a CD-ROM drive, you should also say Y or M to "ISO
1727 9660 CD-ROM file system support" below, because that's the file
1728 system used on CD-ROMs.
1730 Parallel port ATAPI disks
1732 This option enables the high-level driver for ATAPI disk devices
1733 connected through a parallel port. If you chose to build PARIDE
1734 support into your kernel, you may answer Y here to build in the
1735 parallel port ATAPI disk driver, otherwise you should answer M
1736 to build it as a loadable module. The module will be called pf.o.
1737 You must also have at least one parallel port protocol driver in
1738 your system. Among the devices supported by this driver are the
1739 MicroSolutions backpack PD/CD drive and the Imation Superdisk
1742 Parallel port ATAPI tapes
1744 This option enables the high-level driver for ATAPI tape devices
1745 connected through a parallel port. If you chose to build PARIDE
1746 support into your kernel, you may answer Y here to build in the
1747 parallel port ATAPI disk driver, otherwise you should answer M
1748 to build it as a loadable module. The module will be called pt.o.
1749 You must also have at least one parallel port protocol driver in
1750 your system. Among the devices supported by this driver is the
1751 parallel port version of the HP 5GB drive.
1753 Parallel port generic ATAPI devices
1755 This option enables a special high-level driver for generic ATAPI
1756 devices connected through a parallel port. The driver allows user
1757 programs, such as cdrtools, to send ATAPI commands directly to a
1760 If you chose to build PARIDE support into your kernel, you may
1761 answer Y here to build in the parallel port generic ATAPI driver,
1762 otherwise you should answer M to build it as a loadable module. The
1763 module will be called pg.o.
1765 You must also have at least one parallel port protocol driver in
1768 This driver implements an API loosely related to the generic SCSI
1769 driver. See <file:include/linux/pg.h>. for details.
1771 You can obtain the most recent version of cdrtools from
1772 <ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/>. Versions 1.6.1a3 and
1773 later fully support this driver.
1775 ATEN EH-100 protocol
1777 This option enables support for the ATEN EH-100 parallel port IDE
1778 protocol. This protocol is used in some inexpensive low performance
1779 parallel port kits made in Hong Kong. If you chose to build PARIDE
1780 support into your kernel, you may answer Y here to build in the
1781 protocol driver, otherwise you should answer M to build it as a
1782 loadable module. The module will be called aten.o. You must also
1783 have a high-level driver for the type of device that you want to
1786 Micro Solutions BACKPACK Series 5 protocol
1788 This option enables support for the Micro Solutions BACKPACK
1789 parallel port Series 5 IDE protocol. (Most BACKPACK drives made
1790 before 1999 were Series 5) Series 5 drives will NOT always have the
1791 Series noted on the bottom of the drive. Series 6 drivers will.
1793 In other words, if your BACKPACK drive dosen't say "Series 6" on the
1794 bottom, enable this option.
1796 If you chose to build PARIDE support into your kernel, you may
1797 answer Y here to build in the protocol driver, otherwise you should
1798 answer M to build it as a loadable module. The module will be
1799 called bpck.o. You must also have a high-level driver for the type
1800 of device that you want to support.
1802 Micro Solutions BACKPACK Series 6 protocol
1804 This option enables support for the Micro Solutions BACKPACK
1805 parallel port Series 6 IDE protocol. (Most BACKPACK drives made
1806 after 1999 were Series 6) Series 6 drives will have the Series noted
1807 on the bottom of the drive. Series 5 drivers don't always have it
1810 In other words, if your BACKPACK drive says "Series 6" on the
1811 bottom, enable this option.
1813 If you chose to build PARIDE support into your kernel, you may
1814 answer Y here to build in the protocol driver, otherwise you should
1815 answer M to build it as a loadable module. The module will be
1816 called bpck6.o. You must also have a high-level driver for the type
1817 of device that you want to support.
1819 DataStor Commuter protocol
1821 This option enables support for the Commuter parallel port IDE
1822 protocol from DataStor. If you chose to build PARIDE support
1823 into your kernel, you may answer Y here to build in the protocol
1824 driver, otherwise you should answer M to build it as a loadable
1825 module. The module will be called comm.o. You must also have
1826 a high-level driver for the type of device that you want to support.
1828 DataStor EP-2000 protocol
1830 This option enables support for the EP-2000 parallel port IDE
1831 protocol from DataStor. If you chose to build PARIDE support
1832 into your kernel, you may answer Y here to build in the protocol
1833 driver, otherwise you should answer M to build it as a loadable
1834 module. The module will be called dstr.o. You must also have
1835 a high-level driver for the type of device that you want to support.
1837 Shuttle EPAT/EPEZ protocol
1839 This option enables support for the EPAT parallel port IDE protocol.
1840 EPAT is a parallel port IDE adapter manufactured by Shuttle
1841 Technology and widely used in devices from major vendors such as
1842 Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
1843 PARIDE support into your kernel, you may answer Y here to build in
1844 the protocol driver, otherwise you should answer M to build it as a
1845 loadable module. The module will be called epat.o. You must also
1846 have a high-level driver for the type of device that you want to
1849 Shuttle EPAT c7/c8 extension
1850 CONFIG_PARIDE_EPATC8
1851 This option enables support for the newer Shuttle EP1284 (aka c7 and
1852 c8) chip. You need this if you are using any recent Imation SuperDisk
1855 Shuttle EPIA protocol
1857 This option enables support for the (obsolete) EPIA parallel port
1858 IDE protocol from Shuttle Technology. This adapter can still be
1859 found in some no-name kits. If you chose to build PARIDE support
1860 into your kernel, you may answer Y here to build in the protocol
1861 driver, otherwise you should answer M to build it as a loadable
1862 module. The module will be called epia.o. You must also have a
1863 high-level driver for the type of device that you want to support.
1865 FIT TD-2000 protocol
1867 This option enables support for the TD-2000 parallel port IDE
1868 protocol from Fidelity International Technology. This is a simple
1869 (low speed) adapter that is used in some portable hard drives. If
1870 you chose to build PARIDE support into your kernel, you may answer Y
1871 here to build in the protocol driver, otherwise you should answer M
1872 to build it as a loadable module. The module will be called fit2.o.
1873 You must also have a high-level driver for the type of device that
1874 you want to support.
1876 FIT TD-3000 protocol
1878 This option enables support for the TD-3000 parallel port IDE
1879 protocol from Fidelity International Technology. This protocol is
1880 used in newer models of their portable disk, CD-ROM and PD/CD
1881 devices. If you chose to build PARIDE support into your kernel, you
1882 may answer Y here to build in the protocol driver, otherwise you
1883 should answer M to build it as a loadable module. The module will be
1884 called fit3.o. You must also have a high-level driver for the type
1885 of device that you want to support.
1887 Freecom IQ ASIC-2 protocol
1889 This option enables support for version 2 of the Freecom IQ parallel
1890 port IDE adapter. This adapter is used by the Maxell Superdisk
1891 drive. If you chose to build PARIDE support into your kernel, you
1892 may answer Y here to build in the protocol driver, otherwise you
1893 should answer M to build it as a loadable module. The module will be
1894 called friq.o. You must also have a high-level driver for the type
1895 of device that you want to support.
1897 FreeCom power protocol
1899 This option enables support for the Freecom power parallel port IDE
1900 protocol. If you chose to build PARIDE support into your kernel, you
1901 may answer Y here to build in the protocol driver, otherwise you
1902 should answer M to build it as a loadable module. The module will be
1903 called frpw.o. You must also have a high-level driver for the type
1904 of device that you want to support.
1906 KingByte KBIC-951A/971A protocols
1908 This option enables support for the KBIC-951A and KBIC-971A parallel
1909 port IDE protocols from KingByte Information Corp. KingByte's
1910 adapters appear in many no-name portable disk and CD-ROM products,
1911 especially in Europe. If you chose to build PARIDE support into your
1912 kernel, you may answer Y here to build in the protocol driver,
1913 otherwise you should answer M to build it as a loadable module. The
1914 module will be called kbic.o. You must also have a high-level driver
1915 for the type of device that you want to support.
1919 This option enables support for the "PHd" parallel port IDE protocol
1920 from KT Technology. This is a simple (low speed) adapter that is
1921 used in some 2.5" portable hard drives. If you chose to build PARIDE
1922 support into your kernel, you may answer Y here to build in the
1923 protocol driver, otherwise you should answer M to build it as a
1924 loadable module. The module will be called ktti.o. You must also
1925 have a high-level driver for the type of device that you want to
1928 OnSpec 90c20 protocol
1930 This option enables support for the (obsolete) 90c20 parallel port
1931 IDE protocol from OnSpec (often marketed under the ValuStore brand
1932 name). If you chose to build PARIDE support into your kernel, you
1933 may answer Y here to build in the protocol driver, otherwise you
1934 should answer M to build it as a loadable module. The module will
1935 be called on20.o. You must also have a high-level driver for the
1936 type of device that you want to support.
1938 OnSpec 90c26 protocol
1940 This option enables support for the 90c26 parallel port IDE protocol
1941 from OnSpec Electronics (often marketed under the ValuStore brand
1942 name). If you chose to build PARIDE support into your kernel, you
1943 may answer Y here to build in the protocol driver, otherwise you
1944 should answer M to build it as a loadable module. The module will be
1945 called on26.o. You must also have a high-level driver for the type
1946 of device that you want to support.
1948 Logical Volume Manager (LVM) support
1950 This driver lets you combine several hard disks, hard disk
1951 partitions, multiple devices or even loop devices (for evaluation
1952 purposes) into a volume group. Imagine a volume group as a kind of
1953 virtual disk. Logical volumes, which can be thought of as virtual
1954 partitions, can be created in the volume group. You can resize
1955 volume groups and logical volumes after creation time, corresponding
1956 to new capacity needs. Logical volumes are accessed as block
1957 devices named /dev/VolumeGroupName/LogicalVolumeName.
1959 For details see <file:Documentation/LVM-HOWTO>. You will need
1960 supporting user space software; location is in
1961 <file:Documentation/Changes>.
1963 If you want to compile this support as a module ( = code which can
1964 be inserted in and removed from the running kernel whenever you
1965 want), say M here and read <file:Documentation/modules.txt>. The
1966 module will be called lvm-mod.o.
1968 Multiple devices driver support (RAID and LVM)
1970 Support multiple physical spindles through a single logical device.
1971 Required for RAID and logical volume management (LVM).
1973 Multiple devices driver support
1975 This driver lets you combine several hard disk partitions into one
1976 logical block device. This can be used to simply append one
1977 partition to another one or to combine several redundant hard disks
1978 into a RAID1/4/5 device so as to provide protection against hard
1979 disk failures. This is called "Software RAID" since the combining of
1980 the partitions is done by the kernel. "Hardware RAID" means that the
1981 combining is done by a dedicated controller; if you have such a
1982 controller, you do not need to say Y here.
1984 More information about Software RAID on Linux is contained in the
1985 Software RAID mini-HOWTO, available from
1986 <http://www.tldp.org/docs.html#howto>. There you will also learn
1987 where to get the supporting user space utilities raidtools.
1989 This driver is also available as a module ( = code which can be
1990 inserted in and removed from the running kernel whenever you want).
1991 If you want to compile it as a module, say M here and read
1992 <file:Documentation/modules.txt>. The module will be called
1997 Linear (append) mode
1999 If you say Y here, then your multiple devices driver will be able to
2000 use the so-called linear mode, i.e. it will combine the hard disk
2001 partitions by simply appending one to the other.
2003 If you want to compile this as a module ( = code which can be
2004 inserted in and removed from the running kernel whenever you want),
2005 say M here and read <file:Documentation/modules.txt>. The module
2006 will be called linear.o.
2010 RAID-0 (striping) mode
2012 If you say Y here, then your multiple devices driver will be able to
2013 use the so-called raid0 mode, i.e. it will combine the hard disk
2014 partitions into one logical device in such a fashion as to fill them
2015 up evenly, one chunk here and one chunk there. This will increase
2016 the throughput rate if the partitions reside on distinct disks.
2018 Information about Software RAID on Linux is contained in the
2019 Software-RAID mini-HOWTO, available from
2020 <http://www.tldp.org/docs.html#howto>. There you will also
2021 learn where to get the supporting user space utilities raidtools.
2023 If you want to compile this as a module ( = code which can be
2024 inserted in and removed from the running kernel whenever you want),
2025 say M here and read <file:Documentation/modules.txt>. The module
2026 will be called raid0.o.
2030 RAID-1 (mirroring) mode
2032 A RAID-1 set consists of several disk drives which are exact copies
2033 of each other. In the event of a mirror failure, the RAID driver
2034 will continue to use the operational mirrors in the set, providing
2035 an error free MD (multiple device) to the higher levels of the
2036 kernel. In a set with N drives, the available space is the capacity
2037 of a single drive, and the set protects against a failure of (N - 1)
2040 Information about Software RAID on Linux is contained in the
2041 Software-RAID mini-HOWTO, available from
2042 <http://www.tldp.org/docs.html#howto>. There you will also
2043 learn where to get the supporting user space utilities raidtools.
2045 If you want to use such a RAID-1 set, say Y. This code is also
2046 available as a module called raid1.o ( = code which can be inserted
2047 in and removed from the running kernel whenever you want). If you
2048 want to compile it as a module, say M here and read
2049 <file:Documentation/modules.txt>.
2055 A RAID-5 set of N drives with a capacity of C MB per drive provides
2056 the capacity of C * (N - 1) MB, and protects against a failure
2057 of a single drive. For a given sector (row) number, (N - 1) drives
2058 contain data sectors, and one drive contains the parity protection.
2059 For a RAID-4 set, the parity blocks are present on a single drive,
2060 while a RAID-5 set distributes the parity across the drives in one
2061 of the available parity distribution methods.
2063 Information about Software RAID on Linux is contained in the
2064 Software-RAID mini-HOWTO, available from
2065 <http://www.tldp.org/docs.html#howto>. There you will also
2066 learn where to get the supporting user space utilities raidtools.
2068 If you want to use such a RAID-4/RAID-5 set, say Y. This code is
2069 also available as a module called raid5.o ( = code which can be
2070 inserted in and removed from the running kernel whenever you want).
2071 If you want to compile it as a module, say M here and read
2072 <file:Documentation/modules.txt>.
2076 Multipath I/O support
2078 Multipath-IO is the ability of certain devices to address the same
2079 physical disk over multiple 'IO paths'. The code ensures that such
2080 paths can be defined and handled at runtime, and ensures that a
2081 transparent failover to the backup path(s) happens if a IO errors
2082 arrives on the primary path.
2084 This driver is also available as a module ( = code which can be
2085 inserted in and removed from the running kernel whenever you want).
2086 If you want to compile it as a module, say M here and read
2087 <file:Documentation/modules.txt>. The module will be called
2092 Support for IDE Raid controllers
2093 CONFIG_BLK_DEV_ATARAID
2094 Say Y or M if you have an IDE Raid controller and want linux
2095 to use its softwareraid feature. You must also select an
2096 appropriate for your board low-level driver below.
2098 Note, that Linux does not use the Raid implementation in BIOS, and
2099 the main purpose for this feature is to retain compatibility and
2100 data integrity with other OS-es, using the same disk array. Linux
2101 has its own Raid drivers, which you should use if you need better
2104 This driver is also available as a module ( = code which can be
2105 inserted in and removed from the running kernel whenever you want).
2106 If you want to compile it as a module, say M here and read
2107 <file:Documentation/modules.txt>. The module will be called
2110 Support Promise software RAID (Fasttrak(tm))
2111 CONFIG_BLK_DEV_ATARAID_PDC
2112 Say Y or M if you have a Promise Fasttrak (tm) Raid controller
2113 and want linux to use the softwareraid feature of this card.
2114 This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
2117 If you choose to compile this as a module, the module will be called
2120 Highpoint 370 software RAID
2121 CONFIG_BLK_DEV_ATARAID_HPT
2122 Say Y or M if you have a Highpoint HPT 370 Raid controller
2123 and want linux to use the softwareraid feature of this card.
2124 This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
2127 If you choose to compile this as a module, the module will be called
2130 CMD/Silicon Image Medley Software RAID
2131 CONFIG_BLK_DEV_ATARAID_MEDLEY
2132 Say Y or M if you have a Silicon Image 3112 SATA RAID controller,
2133 a CMD680 based controller, or another IDE RAID controller that uses
2134 CMD's Medley software RAID, and want Linux to use the software RAID
2135 feature of this card. This driver uses /dev/ataraid/dXpY (X and Y
2136 numbers) as device names.
2138 This driver currently only supports RAID0 (striped) mode, so if you
2139 are using RAID1 (mirroring) this will not work for you. In that
2140 case, you may want to try the Silicon Image Medley Software RAID
2143 Support for mirroring is planned in the future.
2145 If you choose to compile this as a module, the module will be called
2148 Silicon Image Medley Software RAID (old driver)
2149 CONFIG_BLK_DEV_ATARAID_SII
2150 Say Y or M if you have a Silicon Image SATARaid controller
2151 and want Linux to use the softwareraid feature of this card.
2152 This driver uses /dev/ataraid/dXpY (X and Y numbers) as device
2155 This driver does not reliably detect all Medley RAID sets, and could
2156 be dangerous if you have a striped set with disks of different size.
2158 You should use the new Medley RAID driver (above), unless you use
2159 RAID1 (mirroring), which the new driver does not yet support.
2161 If you choose to compile this as a module, the module will be called
2164 Support for Acer PICA 1 chipset
2166 This is a machine with a R4400 133/150 MHz CPU. To compile a Linux
2167 kernel that runs on these, say Y here. For details about Linux on
2168 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
2169 <http://www.linux-mips.org/>.
2171 Support for Algorithmics P4032 (EXPERIMENTAL)
2173 This is an evaluation board of the British company Algorithmics.
2174 The board uses the R4300 and a R5230 CPUs. For more information
2175 about this board see <http://www.algor.co.uk/>.
2177 SGI SN2 L1 serial port support
2178 CONFIG_SGI_L1_SERIAL
2179 If you have an SGI SN2 and you want to use the serial port connected
2180 to the system controller (you want this!), say Y. Otherwise, say N.
2182 SGI SN2 L1 serial console support
2183 CONFIG_SGI_L1_SERIAL_CONSOLE
2184 If you have an SGI SN2 and you would like to use the system
2185 controller serial port as your console (you want this!), say Y.
2188 Support for BAGET MIPS series
2190 This enables support for the Baget, a Russian embedded system. For
2191 more details about the Baget see the Linux/MIPS FAQ on
2192 <http://www.linux-mips.org/>.
2194 Baget AMD LANCE support
2196 Say Y to enable kernel support for AMD Lance Ethernet cards on the
2197 MIPS-32-based Baget embedded system. This chipset is better known
2198 via the NE2100 cards.
2200 Support for DECstations
2202 This enables support for DEC's MIPS based workstations. For details
2203 see the Linux/MIPS FAQ on <http://www.linux-mips.org/> and the
2204 DECstation porting pages on <http://decstation.unix-ag.org/>.
2206 If you have one of the following DECstation Models you definitely
2207 want to choose R4xx0 for the CPU Type:
2214 otherwise choose R3000.
2216 Support for Cobalt Micro Server
2217 CONFIG_COBALT_MICRO_SERVER
2218 Support for MIPS-based Cobalt boxes (they have been bought by Sun
2219 and are now the "Server Appliance Business Unit") including the 2700
2220 series -- versions 1 of the Qube and Raq. To compile a Linux kernel
2221 for this hardware, say Y here.
2223 Support for Cobalt 2800
2225 Support for the second generation of MIPS-based Cobalt boxes (they
2226 have been bought by Sun and are now the "Server Appliance Business
2227 Unit") including the 2800 series -- versions 2 of the Qube and Raq.
2228 To compile a Linux kernel for this hardware, say Y here.
2230 Support for the Momentum Computer Ocelot SBC
2231 CONFIG_MOMENCO_OCELOT
2232 The Ocelot is a MIPS-based Single Board Computer (SBC) made by
2233 Momentum Computer <http://www.momenco.com/>.
2235 Support for NEC DDB Vrc-5074
2237 This enables support for the VR5000-based NEC DDB Vrc-5074
2240 Support for NEC DDB Vrc-5476
2242 This enables support for the R5432-based NEC DDB Vrc-5476
2245 Features : kernel debugging, serial terminal, NFS root fs, on-board
2246 ether port (Need an additional patch at <http://linux.junsun.net/>),
2247 USB, AC97, PCI, PCI VGA card & framebuffer console, IDE controller,
2248 PS2 keyboard, PS2 mouse, etc.
2250 Support for NEC DDB Vrc-5477
2252 This enables support for the R5432-based NEC DDB Vrc-5477
2255 Features : kernel debugging, serial terminal, NFS root fs, on-board
2256 ether port (Need an additional patch at <http://linux.junsun.net/>),
2257 USB, AC97, PCI, etc.
2259 Support for MIPS Atlas board
2261 This enables support for the QED R5231-based MIPS Atlas evaluation
2264 Support for MIPS Malta board
2266 This enables support for the VR5000-based MIPS Malta evaluation
2270 Support for Broadcom SiByte boards
2272 Enable support for boards based on the Broadcom SiByte family:
2274 BCM91250A-SWARM BCM1250 ATX size Eval Board (BCM91250A-SWARM)
2276 BCM91250E-Sentosa BCM1250 PCI card Eval Board (BCM91250E-Sentosa)
2278 BCM91125E-Rhone BCM1125 PCI card Eval Board (BCM91125E-Rhone)
2280 Other Non-Broadcom SiByte-based platform
2283 Support for Broadcom BCM1xxx SOCs
2284 CONFIG_SIBYTE_SB1250
2286 BCM1250 Dual-CPU SB1 with PCI and HyperTransport.
2288 BCM1120 Uniprocessor SB1.
2290 BCM1125 Uniprocessor SB1 with PCI (and HyperTransport for 1125H).
2293 CONFIG_CPU_SB1_PASS_1
2294 Which pass of the SOC is supported (see the "system_revision"
2295 register in the User Manual for more discussion of revisions):
2306 CONFIG_CPU_SB1_PASS_2
2307 Which pass of the SOC is supported (see the "system_revision"
2308 register in the User Manual for more discussion of revisions):
2310 Hybrid 1250 "Pass 2"
2316 Make use of the CFE API for enumerating available memory,
2317 controlling secondary CPUs, and possibly console output.
2319 Use firmware console
2320 CONFIG_SIBYTE_CFE_CONSOLE
2321 Use the CFE API's console write routines during boot. Other console
2322 options (VT console, sb1250 duart console, etc.) should not be
2325 Support for Bus Watcher statistics
2326 CONFIG_SIBYTE_BUS_WATCHER
2327 Handle and keep statistics on the bus error interrupts (COR_ECC,
2330 Bus trace dump on bus error
2331 CONFIG_SIBYTE_BW_TRACE
2332 Run a continuous bus trace, dumping the raw data as soon as a ZBbus
2333 error is detected. Cannot work if ZBbus profiling is turned on, and
2334 also will interfere with JTAG-based trace buffer activity. Raw
2335 buffer data is dumped to console, and must be processed off-line.
2338 CONFIG_SB1XXX_CORELIS
2339 Select compile flags that produce code that can be processed by the
2340 Corelis mksym utility and UDB Emulator.
2342 DMA for page clear and copy
2343 CONFIG_SIBYTE_DMA_PAGEOPS
2344 Instead of using the CPU to zero and copy pages, use a Data Mover
2345 channel. These DMA channels are otherwise unused by the standard
2346 SiByte Linux port. Seems to give a small performance benefit.
2348 Support for Galileo Evaluation board or CoSine Orion
2350 Say Y if configuring for the Galileo evaluation board
2351 or CoSine Orion. More information is available at
2352 <http://tochna.technion.ac.il/project/linux/html/linux.html>.
2356 Support for Mips Magnum 4000
2357 CONFIG_MIPS_MAGNUM_4000
2358 This is a machine with a R4000 100 MHz CPU. To compile a Linux
2359 kernel that runs on these, say Y here. For details about Linux on
2360 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
2361 <http://www.linux-mips.org/>.
2363 Enable Qtronix 990P Keyboard Support
2364 CONFIG_QTRONIX_KEYBOARD
2365 Images of Qtronix keyboards are at
2366 <http://www.qtronix.com/keyboard.html>.
2368 Support for Olivetti M700
2369 CONFIG_OLIVETTI_M700
2370 This is a machine with a R4000 100 MHz CPU. To compile a Linux
2371 kernel that runs on these, say Y here. For details about Linux on
2372 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
2373 <http://www.linux-mips.org/>.
2375 Support for SNI RM200 PCI
2376 CONFIG_SNI_RM200_PCI
2377 The SNI RM200 PCI was a MIPS-based platform manufactured by Siemens
2378 Nixdorf Informationssysteme (SNI), parent company of Pyramid
2379 Technology and now in turn merged with Fujitsu. Say Y here to
2380 support this machine type.
2382 Support for SGI-IP22 (Indy/Indigo2)
2384 This are the SGI Indy, Challenge S and Indigo2, as well as certain
2385 OEM variants like the Tandem CMN B006S. To compile a Linux kernel
2386 that runs on these, say Y here.
2388 Support for SGI IP27 (Origin200/2000)
2390 This are the SGI Origin 200, Origin 2000 and Onyx 2 Graphics
2391 workstations. To compile a Linux kernel that runs on these, say Y
2395 CONFIG_SGI_SN0_N_MODE
2396 The nodes of Origin 200, Origin 2000 and Onyx 2 systems can be
2397 configured in either N-Modes which allows for more nodes or M-Mode
2398 which allows for more memory. Your system is most probably
2399 running in M-Mode, so you should say N here.
2403 Say Y here to support the on-board Intel 82596 ethernet controller
2404 built into Hewlett-Packard PA-RISC machines.
2406 MIPS JAZZ onboard SONIC Ethernet support
2407 CONFIG_MIPS_JAZZ_SONIC
2408 This is the driver for the onboard card of MIPS Magnum 4000,
2409 Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
2411 MIPS JAZZ FAS216 SCSI support
2413 This is the driver for the onboard SCSI host adapter of MIPS Magnum
2414 4000, Acer PICA, Olivetti M700-10 and a few other identical OEM
2417 MIPS GT96100 Ethernet support
2418 CONFIG_MIPS_GT96100ETH
2419 Say Y here to support the Ethernet subsystem on your GT96100 card.
2423 The Zalon is an interface chip that sits between the PA-RISC
2424 processor and the NCR 53c720 SCSI controller on K-series PA-RISC
2425 boards (these are used, among other places, on some HP 780
2426 workstations). Say Y here to make sure it gets initialized
2427 correctly before the Linux kernel tries to talk to the controller.
2429 SGI PROM Console Support
2430 CONFIG_SGI_PROM_CONSOLE
2431 Say Y here to set up the boot console on serial port 0.
2433 DECstation serial support
2435 This selects whether you want to be asked about drivers for
2436 DECstation serial ports.
2438 Note that the answer to this question won't directly affect the
2439 kernel: saying N will just cause the configurator to skip all
2440 the questions about DECstation serial ports.
2444 Support for console on a DECstation serial port
2445 CONFIG_SERIAL_DEC_CONSOLE
2446 If you say Y here, it will be possible to use a serial port as the
2447 system console (the system console is the device which receives all
2448 kernel messages and warnings and which allows logins in single user
2449 mode). Note that the firmware uses ttyS0 as the serial console on
2450 the Maxine and ttyS2 on the others.
2456 DZ11-family serial controllers for VAXstations, including the
2457 DC7085, M7814, and M7819.
2459 TURBOchannel support
2461 TurboChannel is a DEC (now Compaq) bus for Alpha and MIPS processors.
2462 Documentation on writing device drivers for TurboChannel is available at:
2463 <http://www.cs.arizona.edu/computer.help/policy/DIGITAL_unix/AA-PS3HD-TET1_html/TITLE.html>.
2465 # Choice: galileo_clock
2468 Configure the kernel for clock speed of your Galileo board.
2469 The choices are 75MHz, 83.3MHz, and 100MHz.
2473 Configure the Galileo kernel for a clock speed of 83.3 MHz.
2477 Configure the Galileo kernel for a clock speed of 100 MHz.
2479 Z85C30 Serial Support
2481 Documentation on the Zilog 85C350 serial communications controller
2482 is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>.
2484 PCMCIA SCSI adapter support
2486 Say Y here if you intend to attach a PCMCIA or CardBus card to your
2487 computer which acts as a SCSI host adapter. These are credit card
2488 size devices often used with laptops.
2490 Note that the answer to this question won't directly affect the
2491 kernel: saying N will just cause the configurator to skip all
2492 the questions PCMCIA SCSI host adapters.
2494 Adaptec APA1480 CardBus support
2495 CONFIG_PCMCIA_APA1480
2496 Say Y here if you intend to attach this type of CardBus SCSI host
2497 adapter to your computer.
2499 This driver is also available as a module called apa1480_cb.o ( =
2500 code which can be inserted in and removed from the running kernel
2501 whenever you want). If you want to compile it as a module, say M
2502 here and read <file:Documentation/modules.txt>.
2504 NinjaSCSI-3 / NinjaSCSI-32Bi (16bit) PCMCIA support
2505 CONFIG_PCMCIA_NINJA_SCSI
2506 If you intend to attach this type of PCMCIA SCSI host adapter to
2507 your computer, say Y here and read
2508 <file:Documentation/README.nsp_cs.eng>.
2510 This driver is also available as a module called nsp_cs.o ( =
2511 code which can be inserted in and removed from the running kernel
2512 whenever you want). If you want to compile it as a module, say M
2513 here and read <file:Documentation/modules.txt>.
2515 Adaptec AHA152X PCMCIA support
2516 CONFIG_PCMCIA_AHA152X
2517 Say Y here if you intend to attach this type of PCMCIA SCSI host
2518 adapter to your computer.
2520 This driver is also available as a module called aha152x_cs.o ( =
2521 code which can be inserted in and removed from the running kernel
2522 whenever you want). If you want to compile it as a module, say M
2523 here and read <file:Documentation/modules.txt>.
2525 Qlogic PCMCIA support
2526 CONFIG_PCMCIA_QLOGIC
2527 Say Y here if you intend to attach this type of PCMCIA SCSI host
2528 adapter to your computer.
2530 This driver is also available as a module called qlogic_cs.o ( =
2531 code which can be inserted in and removed from the running kernel
2532 whenever you want). If you want to compile it as a module, say M
2533 here and read <file:Documentation/modules.txt>.
2535 Future Domain PCMCIA support
2536 CONFIG_PCMCIA_FDOMAIN
2537 Say Y here if you intend to attach this type of PCMCIA SCSI host
2538 adapter to your computer.
2540 This driver is also available as a module called fdomain_cs.o ( =
2541 code which can be inserted in and removed from the running kernel
2542 whenever you want). If you want to compile it as a module, say M
2543 here and read <file:Documentation/modules.txt>.
2548 Please make sure to pick the right CPU type. Linux/MIPS is not
2549 designed to be generic, i.e. kernels compiled for R3000 CPUs will
2550 *not* work on R4000 machines and vice versa. However, since most
2551 of the supported machines have an R4000 (or similar) CPU, R4x00
2552 might be a safe bet. If the resulting kernel does not work,
2553 try to recompile with R3000.
2555 R3000 MIPS Technologies R3000-series processors,
2556 including the 3041, 3051, and 3081.
2558 R6000 MIPS Technologies R6000-series processors,
2559 including the 64474, 64475, 64574 and 64575.
2561 R4300 MIPS Technologies R4300-series processors.
2563 R4x00 MIPS Technologies R4000-series processors other than 4300,
2564 including the 4640, 4650, and 4700.
2566 R5000 MIPS Technologies R5000-series processors other than the
2569 R52xx MIPS Technologies R52xx-series ("Nevada") processors.
2571 R10000 MIPS Technologies R10000-series processors.
2573 SB1 Broadcom SiByte SB1 processor.
2577 MIPS Technologies R6000-series processors, including the 64474,
2578 64475, 64574 and 64575.
2582 MIPS Technologies R4300-series processors.
2586 MIPS Technologies R4000-series processors other than 4300, including
2587 the 4640, 4650, and 4700.
2591 MIPS Technologies R5000-series processors other than the Nevada.
2595 MIPS Technologies R52x0-series ("Nevada") processors.
2599 MIPS Technologies R8000-series processors.
2603 MIPS Technologies R10000-series processors.
2607 Broadcom SiByte SB1 processor.
2609 Discontiguous Memory Support
2611 Say Y to support efficient handling of discontiguous physical memory,
2612 for architectures which are either NUMA (Non-Uniform Memory Access)
2613 or have huge holes in the physical address space for other reasons.
2614 See <file:Documentation/vm/numa> for more.
2616 Mapped kernel support
2617 CONFIG_MAPPED_KERNEL
2618 Change the way a Linux kernel is loaded unto memory on a MIPS64
2619 machine. This is required in order to support text replication and
2620 NUMA. If you need to understand it, read the source code.
2622 Kernel text replication support
2623 CONFIG_REPLICATE_KTEXT
2624 Say Y here to enable replicating the kernel text across multiple
2625 nodes in a NUMA cluster. This trades memory for speed.
2627 Exception handler replication support
2628 CONFIG_REPLICATE_EXHANDLERS
2629 Say Y here to enable replicating the kernel exception handlers
2630 across multiple nodes in a NUMA cluster. This trades memory for
2635 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
2636 Access). This option is for configuring high-end multiprocessor
2637 server machines. If in doubt, say N.
2641 The options selects support for the NEC VR41xx series of processors.
2642 Only choose this option if you have one of these processors as a
2643 kernel built with this option will not run on any other type of
2644 processor or vice versa.
2646 CPU feature configuration
2648 Saying yes here allows you to select support for various features
2649 your CPU may or may not have. Most people should say N here.
2651 ll and sc instructions available
2653 MIPS R4000 series and later provide the Load Linked (ll)
2654 and Store Conditional (sc) instructions. More information is
2655 available at <http://www.go-ecs.com/mips/miptek1.htm>.
2657 Say Y here if your CPU has the ll and sc instructions. Say Y here
2658 for better performance, N if you don't know. You must say Y here
2659 for multiprocessor machines.
2661 lld and scd instructions available
2662 CONFIG_CPU_HAS_LLDSCD
2663 Say Y here if your CPU has the lld and scd instructions, the 64-bit
2664 equivalents of ll and sc. Say Y here for better performance, N if
2665 you don't know. You must say Y here for multiprocessor machines.
2667 Writeback Buffer available
2669 Say N here for slightly better performance. You must say Y here for
2670 machines which require flushing of write buffers in software. Saying
2671 Y is the safe option; N may result in kernel malfunction and crashes.
2673 Use 64-bit ELF format for building
2675 A 64-bit kernel is usually built using the 64-bit ELF binary object
2676 format as it's one that allows arbitrary 64-bit constructs. For
2677 kernels that are loaded within the KSEG compatibility segments the
2678 32-bit ELF format can optionally be used resulting in a somewhat
2679 smaller binary, but this option is not explicitly supported by the
2680 toolchain and since binutils 2.14 it does not even work at all.
2682 Say Y to use the 64-bit format or N to use the 32-bit one.
2686 Support for large 64-bit configurations
2687 CONFIG_MIPS_INSANE_LARGE
2688 MIPS R10000 does support a 44 bit / 16TB address space as opposed to
2689 previous 64-bit processors which only supported 40 bit / 1TB. If you
2690 need processes of more than 1TB virtual address space, say Y here.
2691 This will result in additional memory usage, so it is not
2692 recommended for normal users.
2694 Generate little endian code
2695 CONFIG_CPU_LITTLE_ENDIAN
2696 Some MIPS machines can be configured for either little or big endian
2697 byte order. These modes require different kernels. Say Y if your
2698 machine is little endian, N if it's a big endian machine.
2700 Use power LED as a heartbeat
2702 Use the power-on LED on your machine as a load meter. The exact
2703 behaviour is platform-dependent, but normally the flash frequency is
2704 a hyperbolic function of the 5-minute load average.
2708 Unless you really know what you are doing, you should say Y here.
2709 The reason is that some programs need kernel networking support even
2710 when running on a stand-alone machine that isn't connected to any
2711 other computer. If you are upgrading from an older kernel, you
2712 should consider updating your networking tools too because changes
2713 in the kernel and the tools often go hand in hand. The tools are
2714 contained in the package net-tools, the location and version number
2715 of which are given in <file:Documentation/Changes>.
2717 For a general introduction to Linux networking, it is highly
2718 recommended to read the NET-HOWTO, available from
2719 <http://www.tldp.org/docs.html#howto>.
2723 The Linux Socket Filter is derived from the Berkeley Packet Filter.
2724 If you say Y here, user-space programs can attach a filter to any
2725 socket and thereby tell the kernel that it should allow or disallow
2726 certain types of data to get through the socket. Linux Socket
2727 Filtering works on all socket types except TCP for now. See the
2728 text file <file:Documentation/networking/filter.txt> for more
2731 You need to say Y here if you want to use PPP packet filtering
2732 (see the CONFIG_PPP_FILTER option below).
2736 Network packet filtering (replaces ipchains)
2738 Netfilter is a framework for filtering and mangling network packets
2739 that pass through your Linux box.
2741 The most common use of packet filtering is to run your Linux box as
2742 a firewall protecting a local network from the Internet. The type of
2743 firewall provided by this kernel support is called a "packet
2744 filter", which means that it can reject individual network packets
2745 based on type, source, destination etc. The other kind of firewall,
2746 a "proxy-based" one, is more secure but more intrusive and more
2747 bothersome to set up; it inspects the network traffic much more
2748 closely, modifies it and has knowledge about the higher level
2749 protocols, which a packet filter lacks. Moreover, proxy-based
2750 firewalls often require changes to the programs running on the local
2751 clients. Proxy-based firewalls don't need support by the kernel, but
2752 they are often combined with a packet filter, which only works if
2755 You should also say Y here if you intend to use your Linux box as
2756 the gateway to the Internet for a local network of machines without
2757 globally valid IP addresses. This is called "masquerading": if one
2758 of the computers on your local network wants to send something to
2759 the outside, your box can "masquerade" as that computer, i.e. it
2760 forwards the traffic to the intended outside destination, but
2761 modifies the packets to make it look like they came from the
2762 firewall box itself. It works both ways: if the outside host
2763 replies, the Linux box will silently forward the traffic to the
2764 correct local computer. This way, the computers on your local net
2765 are completely invisible to the outside world, even though they can
2766 reach the outside and can receive replies. It is even possible to
2767 run globally visible servers from within a masqueraded local network
2768 using a mechanism called portforwarding. Masquerading is also often
2769 called NAT (Network Address Translation).
2771 Another use of Netfilter is in transparent proxying: if a machine on
2772 the local network tries to connect to an outside host, your Linux
2773 box can transparently forward the traffic to a local server,
2774 typically a caching proxy server.
2776 Various modules exist for netfilter which replace the previous
2777 masquerading (ipmasqadm), packet filtering (ipchains), transparent
2778 proxying, and portforwarding mechanisms. Please see
2779 <file:Documentation/Changes> under "iptables" for the location of
2782 Make sure to say N to "Fast switching" below if you intend to say Y
2783 here, as Fast switching currently bypasses netfilter.
2785 Chances are that you should say Y here if you compile a kernel which
2786 will run as a router and N for regular hosts. If unsure, say N.
2788 Network packet filtering debugging
2789 CONFIG_NETFILTER_DEBUG
2790 You can say Y here if you want to get additional messages useful in
2791 debugging the netfilter code.
2793 Connection tracking (required for masq/NAT)
2794 CONFIG_IP_NF_CONNTRACK
2795 Connection tracking keeps a record of what packets have passed
2796 through your machine, in order to figure out how they are related
2799 This is required to do Masquerading or other kinds of Network
2800 Address Translation (except for Fast NAT). It can also be used to
2801 enhance packet filtering (see `Connection state match support'
2804 If you want to compile it as a module, say M here and read
2805 <file:Documentation/modules.txt>. If unsure, say `N'.
2807 Amanda protocol support
2809 If you are running the Amanda backup package (http://www.amanda.org/)
2810 on this machine or machines that will be MASQUERADED through this
2811 machine, then you may want to enable this feature. This allows the
2812 connection tracking and natting code to allow the sub-channels that
2813 Amanda requires for communication of the backup data, messages and
2816 If you want to compile it as a module, say M here and read
2817 Documentation/modules.txt. If unsure, say `N'.
2820 IRC Send/Chat protocol support
2822 There is a commonly-used extension to IRC called
2823 Direct Client-to-Client Protocol (DCC). This enables users to send
2824 files to each other, and also chat to each other without the need
2825 of a server. DCC Sending is used anywhere you send files over IRC,
2826 and DCC Chat is most commonly used by Eggdrop bots. If you are
2827 using NAT, this extension will enable you to send files and initiate
2828 chats. Note that you do NOT need this extension to get files or
2829 have others initiate chats, or everything else in IRC.
2831 If you want to compile it as a module, say 'M' here and read
2832 Documentation/modules.txt. If unsure, say 'N'.
2834 TFTP protocol support
2836 TFTP connection tracking helper, this is required depending
2837 on how restrictive your ruleset is.
2838 If you are using a tftp client behind -j SNAT or -j MASQUERADING
2841 If you want to compile it as a module, say M here and read
2842 Documentation/modules.txt. If unsure, say `Y'.
2844 FTP protocol support
2846 Tracking FTP connections is problematic: special helpers are
2847 required for tracking them, and doing masquerading and other forms
2848 of Network Address Translation on them.
2850 If you want to compile it as a module, say M here and read
2851 <file:Documentation/modules.txt>. If unsure, say `Y'.
2853 User space queueing via NETLINK
2855 Netfilter has the ability to queue packets to user space: the
2856 netlink device can be used to access them using this driver.
2858 If you want to compile it as a module, say M here and read
2859 <file:Documentation/modules.txt>. If unsure, say `N'.
2861 IP tables support (required for filtering/masq/NAT)
2862 CONFIG_IP_NF_IPTABLES
2863 iptables is a general, extensible packet identification framework.
2864 The packet filtering and full NAT (masquerading, port forwarding,
2865 etc) subsystems now use this: say `Y' or `M' here if you want to use
2868 If you want to compile it as a module, say M here and read
2869 <file:Documentation/modules.txt>. If unsure, say `N'.
2871 recent match support
2872 CONFIG_IP_NF_MATCH_RECENT
2873 This match is used for creating one or many lists of recently
2874 used addresses and then matching against that/those list(s).
2876 Short options are available by using 'iptables -m recent -h'
2877 Official Website: <http://snowman.net/projects/ipt_recent/>
2879 If you want to compile it as a module, say M here and read
2880 Documentation/modules.txt. If unsure, say `N'.
2883 CONFIG_IP_NF_MATCH_LIMIT
2884 limit matching allows you to control the rate at which a rule can be
2885 matched: mainly useful in combination with the LOG target ("LOG
2886 target support", below) and to avoid some Denial of Service attacks.
2888 If you want to compile it as a module, say M here and read
2889 <file:Documentation/modules.txt>. If unsure, say `N'.
2891 skb->pkt_type packet match support
2892 CONFIG_IP_NF_MATCH_PKTTYPE
2893 This patch allows you to match packet in accrodance
2894 to its "class", eg. BROADCAST, MULTICAST, ...
2897 iptables -A INPUT -m pkttype --pkt-type broadcast -j LOG
2899 If you want to compile it as a module, say M here and read
2900 Documentation/modules.txt. If unsure, say `N'.
2902 MAC address match support
2903 CONFIG_IP_NF_MATCH_MAC
2904 MAC matching allows you to match packets based on the source
2905 Ethernet address of the packet.
2907 If you want to compile it as a module, say M here and read
2908 <file:Documentation/modules.txt>. If unsure, say `N'.
2910 Netfilter MARK match support
2911 CONFIG_IP_NF_MATCH_MARK
2912 Netfilter mark matching allows you to match packets based on the
2913 `nfmark' value in the packet. This can be set by the MARK target
2916 If you want to compile it as a module, say M here and read
2917 <file:Documentation/modules.txt>. If unsure, say `N'.
2919 Multiple port match support
2920 CONFIG_IP_NF_MATCH_MULTIPORT
2921 Multiport matching allows you to match TCP or UDP packets based on
2922 a series of source or destination ports: normally a rule can only
2923 match a single range of ports.
2925 If you want to compile it as a module, say M here and read
2926 <file:Documentation/modules.txt>. If unsure, say `N'.
2929 CONFIG_IP_NF_MATCH_TTL
2930 This adds CONFIG_IP_NF_MATCH_TTL option, which enabled the user
2931 to match packets by their TTL value.
2933 If you want to compile it as a module, say M here and read
2934 Documentation/modules.txt. If unsure, say `N'.
2936 LENGTH match support
2937 CONFIG_IP_NF_MATCH_LENGTH
2938 This option allows you to match the length of a packet against a
2939 specific value or range of values.
2941 If you want to compile it as a module, say M here and read
2942 <file:Documentation/modules.txt>. If unsure, say `N'.
2944 AH/ESP match support
2945 CONFIG_IP_NF_MATCH_AH_ESP
2946 These two match extensions (`ah' and `esp') allow you to match a
2947 range of SPIs inside AH or ESP headers of IPSec packets.
2949 If you want to compile it as a module, say M here and read
2950 Documentation/modules.txt. If unsure, say `N'.
2953 CONFIG_IP_NF_MATCH_DSCP
2954 This option adds a `DSCP' match, which allows you to match against
2955 the IPv4 header DSCP field (DSCP codepoint).
2957 The DSCP codepoint can have any value between 0x0 and 0x4f.
2959 If you want to compile it as a module, say M here and read
2960 Documentation/modules.txt. If unsure, say `N'.
2965 CONFIG_IP_NF_MATCH_ECN
2966 This option adds a `ECN' match, which allows you to match against
2967 the IPv4 and TCP header ECN fields.
2969 If you want to compile it as a module, say M here and read
2970 Documentation/modules.txt. If unsure, say `N'.
2975 CONFIG_IP_NF_MATCH_TOS
2976 TOS matching allows you to match packets based on the Type Of
2977 Service fields of the IP packet.
2979 If you want to compile it as a module, say M here and read
2980 <file:Documentation/modules.txt>. If unsure, say `N'.
2982 conntrack match support
2983 CONFIG_IP_NF_MATCH_CONNTRACK
2984 This is a general conntrack match module, a superset of the state match.
2986 It allows matching on additional conntrack information, which is
2987 useful in complex configurations, such as NAT gateways with multiple
2988 internet links or tunnels.
2990 If you want to compile it as a module, say M here and read
2991 Documentation/modules.txt. If unsure, say `N'.
2994 Connection state match support
2995 CONFIG_IP_NF_MATCH_STATE
2996 Connection state matching allows you to match packets based on their
2997 relationship to a tracked connection (ie. previous packets). This
2998 is a powerful tool for packet classification.
3000 If you want to compile it as a module, say M here and read
3001 <file:Documentation/modules.txt>. If unsure, say `N'.
3003 Unclean match support
3004 CONFIG_IP_NF_MATCH_UNCLEAN
3005 Unclean packet matching matches any strange or invalid packets, by
3006 looking at a series of fields in the IP, TCP, UDP and ICMP headers.
3008 If you want to compile it as a module, say M here and read
3009 <file:Documentation/modules.txt>. If unsure, say `N'.
3012 CONFIG_IP_NF_MATCH_OWNER
3013 Packet owner matching allows you to match locally-generated packets
3014 based on who created them: the user, group, process or session.
3016 If you want to compile it as a module, say M here and read
3017 <file:Documentation/modules.txt>. If unsure, say `N'.
3021 Packet filtering defines a table `filter', which has a series of
3022 rules for simple packet filtering at local input, forwarding and
3023 local output. See the man page for iptables(8).
3025 If you want to compile it as a module, say M here and read
3026 <file:Documentation/modules.txt>. If unsure, say `N'.
3028 REJECT target support
3029 CONFIG_IP_NF_TARGET_REJECT
3030 The REJECT target allows a filtering rule to specify that an ICMP
3031 error should be issued in response to an incoming packet, rather
3032 than silently being dropped.
3034 If you want to compile it as a module, say M here and read
3035 <file:Documentation/modules.txt>. If unsure, say `N'.
3037 MIRROR target support
3038 CONFIG_IP_NF_TARGET_MIRROR
3039 The MIRROR target allows a filtering rule to specify that an
3040 incoming packet should be bounced back to the sender.
3042 If you want to compile it as a module, say M here and read
3043 <file:Documentation/modules.txt>. If unsure, say `N'.
3045 Full NAT (Network Address Translation)
3047 The Full NAT option allows masquerading, port forwarding and other
3048 forms of full Network Address Port Translation. It is controlled by
3049 the `nat' table in iptables: see the man page for iptables(8).
3051 If you want to compile it as a module, say M here and read
3052 <file:Documentation/modules.txt>. If unsure, say `N'.
3054 MASQUERADE target support
3055 CONFIG_IP_NF_TARGET_MASQUERADE
3056 Masquerading is a special case of NAT: all outgoing connections are
3057 changed to seem to come from a particular interface's address, and
3058 if the interface goes down, those connections are lost. This is
3059 only useful for dialup accounts with dynamic IP address (ie. your IP
3060 address will be different on next dialup).
3062 If you want to compile it as a module, say M here and read
3063 <file:Documentation/modules.txt>. If unsure, say `N'.
3065 Basic SNMP-ALG support
3066 CONFIG_IP_NF_NAT_SNMP_BASIC
3068 This module implements an Application Layer Gateway (ALG) for
3069 SNMP payloads. In conjunction with NAT, it allows a network
3070 management system to access multiple private networks with
3071 conflicting addresses. It works by modifying IP addresses
3072 inside SNMP payloads to match IP-layer NAT mapping.
3074 This is the "basic" form of SNMP-ALG, as described in RFC 2962
3076 If you want to compile it as a module, say M here and read
3077 <file:Documentation/modules.txt>. If unsure, say `N'.
3079 REDIRECT target support
3080 CONFIG_IP_NF_TARGET_REDIRECT
3081 REDIRECT is a special case of NAT: all incoming connections are
3082 mapped onto the incoming interface's address, causing the packets to
3083 come to the local machine instead of passing through. This is
3084 useful for transparent proxies.
3086 If you want to compile it as a module, say M here and read
3087 <file:Documentation/modules.txt>. If unsure, say `N'.
3091 This option adds a `mangle' table to iptables: see the man page for
3092 iptables(8). This table is used for various packet alterations
3093 which can effect how the packet is routed.
3095 If you want to compile it as a module, say M here and read
3096 <file:Documentation/modules.txt>. If unsure, say `N'.
3099 CONFIG_IP_NF_TARGET_DSCP
3100 This option adds a `DSCP' target, which allows you to create rules in
3101 the iptables mangle table. The selected packet has the DSCP field set
3102 to the hex value provided on the command line; unlike the TOS target
3103 which will only set the legal values within ip.h.
3105 The DSCP field can be set to any value between 0x0 and 0x4f. It does
3106 take into account that bits 6 and 7 are used by ECN.
3108 If you want to compile it as a module, say M here and read
3109 Documentation/modules.txt. If unsure, say `N'.
3114 CONFIG_IP_NF_TARGET_ECN
3115 This option adds a `ECN' target, which can be used in the iptables mangle
3118 You can use this target to remove the ECN bits from the IPv4 header of
3119 an IP packet. This is particularly useful, if you need to work around
3120 existing ECN blackholes on the internet, but don't want to disable
3121 ECN support in general.
3123 If you want to compile it as a module, say M here and read
3124 Documentation/modules.txt. If unsure, say `N'.
3129 CONFIG_IP_NF_TARGET_TOS
3130 This option adds a `TOS' target, which allows you to create rules in
3131 the `mangle' table which alter the Type Of Service field of an IP
3132 packet prior to routing.
3134 If you want to compile it as a module, say M here and read
3135 <file:Documentation/modules.txt>. If unsure, say `N'.
3138 CONFIG_IP_NF_TARGET_MARK
3139 This option adds a `MARK' target, which allows you to create rules
3140 in the `mangle' table which alter the netfilter mark (nfmark) field
3141 associated with the packet prior to routing. This can change
3142 the routing method (see `Use netfilter MARK value as routing
3143 key') and can also be used by other subsystems to change their
3146 If you want to compile it as a module, say M here and read
3147 <file:Documentation/modules.txt>. If unsure, say `N'.
3149 TCPMSS target support
3150 CONFIG_IP_NF_TARGET_TCPMSS
3151 This option adds a `TCPMSS' target, which allows you to alter the
3152 MSS value of TCP SYN packets, to control the maximum size for that
3153 connection (usually limiting it to your outgoing interface's MTU
3156 This is used to overcome criminally braindead ISPs or servers which
3157 block ICMP Fragmentation Needed packets. The symptoms of this
3158 problem are that everything works fine from your Linux
3159 firewall/router, but machines behind it can never exchange large
3161 1) Web browsers connect, then hang with no data received.
3162 2) Small mail works fine, but large emails hang.
3163 3) ssh works fine, but scp hangs after initial handshaking.
3165 Workaround: activate this option and add a rule to your firewall
3168 iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN \
3169 -j TCPMSS --clamp-mss-to-pmtu
3171 If you want to compile it as a module, say M here and read
3172 <file:Documentation/modules.txt>. If unsure, say `N'.
3174 Helper match support
3175 CONFIG_IP_NF_MATCH_HELPER
3176 Helper matching allows you to match packets in dynamic connections
3177 tracked by a conntrack-helper, ie. ip_conntrack_ftp
3179 If you want to compile it as a module, say M here and read
3180 Documentation/modules.txt. If unsure, say `Y'.
3182 TCPMSS match support
3183 CONFIG_IP_NF_MATCH_TCPMSS
3184 This option adds a `tcpmss' match, which allows you to examine the
3185 MSS value of TCP SYN packets, which control the maximum packet size
3186 for that connection.
3188 If you want to compile it as a module, say M here and read
3189 <file:Documentation/modules.txt>. If unsure, say `N'.
3192 CONFIG_IP_NF_TARGET_ULOG
3193 This option adds a `ULOG' target, which allows you to create rules in
3194 any iptables table. The packet is passed to a userspace logging
3195 daemon using netlink multicast sockets; unlike the LOG target
3196 which can only be viewed through syslog.
3198 The appropriate userspace logging daemon (ulogd) may be obtained from
3199 <http://www.gnumonks.org/projects/ulogd>
3201 If you want to compile it as a module, say M here and read
3202 Documentation/modules.txt. If unsure, say `N'.
3205 CONFIG_IP_NF_TARGET_LOG
3206 This option adds a `LOG' target, which allows you to create rules in
3207 any iptables table which records the packet header to the syslog.
3209 If you want to compile it as a module, say M here and read
3210 <file:Documentation/modules.txt>. If unsure, say `N'.
3212 ipchains (2.2-style) support
3213 CONFIG_IP_NF_COMPAT_IPCHAINS
3214 This option places ipchains (with masquerading and redirection
3215 support) back into the kernel, using the new netfilter
3216 infrastructure. It is not recommended for new installations (see
3217 `Packet filtering'). With this enabled, you should be able to use
3218 the ipchains tool exactly as in 2.2 kernels.
3220 If you want to compile it as a module, say M here and read
3221 <file:Documentation/modules.txt>. If unsure, say `N'.
3223 ipfwadm (2.0-style) support
3224 CONFIG_IP_NF_COMPAT_IPFWADM
3225 This option places ipfwadm (with masquerading and redirection
3226 support) back into the kernel, using the new netfilter
3227 infrastructure. It is not recommended for new installations (see
3228 `Packet filtering'). With this enabled, you should be able to use
3229 the ipfwadm tool exactly as in 2.0 kernels.
3231 If you want to compile it as a module, say M here and read
3232 <file:Documentation/modules.txt>. If unsure, say `N'.
3234 EUI64 address check (EXPERIMENTAL)
3235 CONFIG_IP6_NF_MATCH_EUI64
3236 This module performs checking on the IPv6 source address
3237 Compares the last 64 bits with the EUI64 (delivered
3238 from the MAC address) address
3240 If you want to compile it as a module, say M here and read
3241 Documentation/modules.txt. If unsure, say `N'.
3243 MAC address match support
3244 CONFIG_IP6_NF_MATCH_MAC
3245 mac matching allows you to match packets based on the source
3246 Ethernet address of the packet.
3248 If you want to compile it as a module, say M here and read
3249 <file:Documentation/modules.txt>. If unsure, say `N'.
3251 length match support
3252 CONFIG_IP6_NF_MATCH_LENGTH
3253 This option allows you to match the length of a packet against a
3254 specific value or range of values.
3256 If you want to compile it as a module, say M here and read
3257 Documentation/modules.txt. If unsure, say `N'.
3259 Netfilter MARK match support
3260 CONFIG_IP6_NF_MATCH_MARK
3261 Netfilter mark matching allows you to match packets based on the
3262 `nfmark' value in the packet. This can be set by the MARK target
3265 If you want to compile it as a module, say M here and read
3266 <file:Documentation/modules.txt>. If unsure, say `N'.
3268 Multiple port match support
3269 CONFIG_IP6_NF_MATCH_MULTIPORT
3270 Multiport matching allows you to match TCP or UDP packets based on
3271 a series of source or destination ports: normally a rule can only
3272 match a single range of ports.
3274 If you want to compile it as a module, say M here and read
3275 <file:Documentation/modules.txt>. If unsure, say `N'.
3277 IPV6 queue handler (EXPERIMENTAL)
3280 This option adds a queue handler to the kernel for IPv6
3281 packets which lets us to receive the filtered packets
3282 with QUEUE target using libiptc as we can do with
3285 (C) Fernando Anton 2001
3286 IPv64 Project - Work based in IPv64 draft by Arturo Azcorra.
3287 Universidad Carlos III de Madrid
3288 Universidad Politecnica de Alcala de Henares
3289 email: fanton@it.uc3m.es
3291 If you want to compile it as a module, say M here and read
3292 Documentation/modules.txt. If unsure, say `N'.
3295 CONFIG_IP6_NF_MATCH_OWNER
3296 Packet owner matching allows you to match locally-generated packets
3297 based on who created them: the user, group, process or session.
3299 If you want to compile it as a module, say M here and read
3300 <file:Documentation/modules.txt>. If unsure, say `N'.
3303 CONFIG_IP6_NF_FILTER
3304 Packet filtering defines a table `filter', which has a series of
3305 rules for simple packet filtering at local input, forwarding and
3306 local output. See the man page for iptables(8).
3308 If you want to compile it as a module, say M here and read
3309 <file:Documentation/modules.txt>. If unsure, say `N'.
3312 CONFIG_IP6_NF_MANGLE
3313 This option adds a `mangle' table to iptables: see the man page for
3314 iptables(8). This table is used for various packet alterations
3315 which can effect how the packet is routed.
3317 If you want to compile it as a module, say M here and read
3318 <file:Documentation/modules.txt>. If unsure, say `N'.
3321 CONFIG_IP6_NF_TARGET_MARK
3322 This option adds a `MARK' target, which allows you to create rules
3323 in the `mangle' table which alter the netfilter mark (nfmark) field
3324 associated with the packet packet prior to routing. This can change
3325 the routing method (see `Use netfilter MARK value as routing
3326 key') and can also be used by other subsystems to change their
3329 If you want to compile it as a module, say M here and read
3330 <file:Documentation/modules.txt>. If unsure, say `N'.
3333 CONFIG_IP_NF_ARPTABLES
3334 arptables is a general, extensible packet identification framework.
3335 The ARP packet filtering and mangling (manipulation)subsystems
3336 use this: say Y or M here if you want to use either of those.
3338 If you want to compile it as a module, say M here and read
3339 <file:Documentation/modules.txt>. If unsure, say `N'.
3341 ARP packet filtering
3342 CONFIG_IP_NF_ARPFILTER
3343 ARP packet filtering defines a table `filter', which has a series of
3344 rules for simple ARP packet filtering at local input and
3345 local output. See the man page for arptables(8).
3347 If you want to compile it as a module, say M here and read
3348 <file:Documentation/modules.txt>. If unsure, say `N'.
3350 ARP payload mangling
3351 CONFIG_IP_NF_ARP_MANGLE
3352 Allows altering the ARP packet payload: source and destination
3353 hardware and network addresses.
3355 If you want to compile it as a module, say M here and read
3356 <file:Documentation/modules.txt>. If unsure, say `N'.
3358 TCP Explicit Congestion Notification support
3360 Explicit Congestion Notification (ECN) allows routers to notify
3361 clients about network congestion, resulting in fewer dropped packets
3362 and increased network performance. This option adds ECN support to
3363 the Linux kernel, as well as a sysctl (/proc/sys/net/ipv4/tcp_ecn)
3364 which allows ECN support to be disabled at runtime.
3366 Note that, on the Internet, there are many broken firewalls which
3367 refuse connections from ECN-enabled machines, and it may be a while
3368 before these firewalls are fixed. Until then, to access a site
3369 behind such a firewall (some of which are major sites, at the time
3370 of this writing) you will have to disable this option, either by
3371 saying N now or by using the sysctl.
3375 IPv6 tables support (required for filtering/masq/NAT)
3376 CONFIG_IP6_NF_IPTABLES
3377 ip6tables is a general, extensible packet identification framework.
3378 Currently only the packet filtering and packet mangling subsystem
3379 for IPv6 use this, but connection tracking is going to follow.
3380 Say 'Y' or 'M' here if you want to use either of those.
3382 If you want to compile it as a module, say M here and read
3383 <file:Documentation/modules.txt>. If unsure, say `N'.
3385 IPv6 limit match support
3386 CONFIG_IP6_NF_MATCH_LIMIT
3387 limit matching allows you to control the rate at which a rule can be
3388 matched: mainly useful in combination with the LOG target ("LOG
3389 target support", below) and to avoid some Denial of Service attacks.
3391 If you want to compile it as a module, say M here and read
3392 <file:Documentation/modules.txt>. If unsure, say `N'.
3395 CONFIG_IP6_NF_TARGET_LOG
3396 This option adds a `LOG' target, which allows you to create rules in
3397 any iptables table which records the packet header to the syslog.
3399 If you want to compile it as a module, say M here and read
3400 <file:Documentation/modules.txt>. If unsure, say `N'.
3402 IP: virtual server support
3404 IP Virtual Server support will let you build a high-performance
3405 virtual server based on cluster of two or more real servers. This
3406 option must be enabled for at least one of the clustered computers
3407 that will take care of intercepting incomming connections to a
3408 single IP address and scheduling them to real servers.
3410 Three request dispatching techniques are implemented, they are
3411 virtual server via NAT, virtual server via tunneling and virtual
3412 server via direct routing. The several scheduling algorithms can
3413 be used to choose which server the connection is directed to,
3414 thus load balancing can be achieved among the servers. For more
3415 information and its administration program, please visit the
3417 http://www.linuxvirtualserver.org/
3419 If you want to compile it in kernel, say Y. If you want to compile
3420 it as a module, say M here and read Documentation/modules.txt. If
3423 IP virtual server debugging
3425 Say Y here if you want to get additional messages useful in
3426 debugging the IP virtual server code. You can change the debug
3427 level in /proc/sys/net/ipv4/vs/debug_level
3429 IPVS connection hash table size (the Nth power of 2)
3430 CONFIG_IP_VS_TAB_BITS
3431 The IPVS connection hash table uses the chaining scheme to handle
3432 hash collisions. Using a big IPVS connection hash table will greatly
3433 reduce conflicts when there are hundreds of thousands of connections
3436 Note the table size must be power of 2. The table size will be the
3437 value of 2 to the your input number power. The number to choose is
3438 from 8 to 20, the default number is 12, which means the table size
3439 is 4096. Don't input the number too small, otherwise you will lose
3440 performance on it. You can adapt the table size yourself, according
3441 to your virtual server application. It is good to set the table size
3442 not far less than the number of connections per second multiplying
3443 average lasting time of connection in the table. For example, your
3444 virtual server gets 200 connections per second, the connection lasts
3445 for 200 seconds in average in the connection table, the table size
3446 should be not far less than 200x200, it is good to set the table
3449 Another note that each connection occupies 128 bytes effectively and
3450 each hash entry uses 8 bytes, so you can estimate how much memory is
3451 needed for your box.
3453 IPVS: round-robin scheduling
3455 The robin-robin scheduling algorithm simply directs network
3456 connections to different real servers in a round-robin manner.
3458 If you want to compile it in kernel, say Y. If you want to compile
3459 it as a module, say M here and read Documentation/modules.txt. If
3462 IPVS: weighted round-robin scheduling
3464 The weighted robin-robin scheduling algorithm directs network
3465 connections to different real servers based on server weights
3466 in a round-robin manner. Servers with higher weights receive
3467 new connections first than those with less weights, and servers
3468 with higher weights get more connections than those with less
3469 weights and servers with equal weights get equal connections.
3471 If you want to compile it in kernel, say Y. If you want to compile
3472 it as a module, say M here and read Documentation/modules.txt. If
3475 IPVS: least-connection scheduling
3477 The least-connection scheduling algorithm directs network
3478 connections to the server with the least number of active
3481 If you want to compile it in kernel, say Y. If you want to compile
3482 it as a module, say M here and read Documentation/modules.txt. If
3485 IPVS: weighted least-connection scheduling
3487 The weighted least-connection scheduling algorithm directs network
3488 connections to the server with the least active connections
3489 normalized by the server weight.
3491 If you want to compile it in kernel, say Y. If you want to compile
3492 it as a module, say M here and read Documentation/modules.txt. If
3495 IPVS: locality-based least-connection scheduling
3497 The locality-based least-connection scheduling algorithm is for
3498 destination IP load balancing. It is usually used in cache cluster.
3499 This algorithm usually directs packet destined for an IP address to
3500 its server if the server is alive and under load. If the server is
3501 overloaded (its active connection numbers is larger than its weight)
3502 and there is a server in its half load, then allocate the weighted
3503 least-connection server to this IP address.
3505 If you want to compile it in kernel, say Y. If you want to compile
3506 it as a module, say M here and read Documentation/modules.txt. If
3509 IPVS: locality-based least-connection with replication scheduling
3511 The locality-based least-connection with replication scheduling
3512 algorithm is also for destination IP load balancing. It is
3513 usually used in cache cluster. It differs from the LBLC scheduling
3514 as follows: the load balancer maintains mappings from a target
3515 to a set of server nodes that can serve the target. Requests for
3516 a target are assigned to the least-connection node in the target's
3517 server set. If all the node in the server set are over loaded,
3518 it picks up a least-connection node in the cluster and adds it
3519 in the sever set for the target. If the server set has not been
3520 modified for the specified time, the most loaded node is removed
3521 from the server set, in order to avoid high degree of replication.
3523 If you want to compile it in kernel, say Y. If you want to compile
3524 it as a module, say M here and read Documentation/modules.txt. If
3527 IPVS: destination hashing scheduling
3529 The destination hashing scheduling algorithm assigns network
3530 connections to the servers through looking up a statically assigned
3531 hash table by their destination IP addresses.
3533 If you want to compile it in kernel, say Y. If you want to compile
3534 it as a module, say M here and read Documentation/modules.txt. If
3537 IPVS: source hashing scheduling
3539 The source hashing scheduling algorithm assigns network
3540 connections to the servers through looking up a statically assigned
3541 hash table by their source IP addresses.
3543 If you want to compile it in kernel, say Y. If you want to compile
3544 it as a module, say M here and read Documentation/modules.txt. If
3547 IPVS: shortest expected delay scheduling
3549 The shortest expected delay scheduling algorithm assigns network
3550 connections to the server with the shortest expected delay. The
3551 expected delay that the job will experience is (Ci + 1) / Ui if
3552 sent to the ith server, in which Ci is the number of connections
3553 on the the ith server and Ui is the fixed service rate (weight)
3556 If you want to compile it in kernel, say Y. If you want to compile
3557 it as a module, say M here and read Documentation/modules.txt. If
3560 IPVS: never queue scheduling
3562 The never queue scheduling algorithm adopts a two-speed model.
3563 When there is an idle server available, the job will be sent to
3564 the idle server, instead of waiting for a fast one. When there
3565 is no idle server available, the job will be sent to the server
3566 that minimize its expected delay (The Shortest Expected Delay
3567 scheduling algorithm).
3569 If you want to compile it in kernel, say Y. If you want to compile
3570 it as a module, say M here and read Documentation/modules.txt. If
3573 IPVS: FTP protocol helper
3575 FTP is a protocol that transfers IP address and/or port number in
3576 the payload. In the virtual server via Network Address Translation,
3577 the IP address and port number of real servers cannot be sent to
3578 clients in ftp connections directly, so FTP protocol helper is
3579 required for tracking the connection and mangling it back to that of
3582 If you want to compile it in kernel, say Y. If you want to compile
3583 it as a module, say M here and read Documentation/modules.txt. If
3586 AH/ESP match support (EXPERIMENTAL)
3587 CONFIG_IP6_NF_MATCH_AHESP
3588 This module allows one to match AH and ESP packets.
3590 If you want to compile it as a module, say M here and read
3591 <file:Documentation/modules.txt>. The modules will be called
3592 ip6t_ah.o and ip6t_esp.o.
3596 Routing header match support
3597 CONFIG_IP6_NF_MATCH_RT
3598 rt matching allows you to match packets based on the routing
3599 header of the packet.
3601 If you want to compile it as a module, say M here and read
3602 <file:Documentation/modules.txt>. The module will be called
3607 Hop-by-hop and Dst opts header match support
3608 CONFIG_IP6_NF_MATCH_OPTS
3609 This allows one to match packets based on the hop-by-hop
3610 and destination options headers of a packet.
3612 If you want to compile it as a module, say M here and read
3613 <file:Documentation/modules.txt>. The modules will be called
3614 ip6t_hbh.o and ip6t_dst.o.
3618 Fragmentation header match support
3619 CONFIG_IP6_NF_MATCH_FRAG
3620 frag matching allows you to match packets based on the fragmentation
3621 header of the packet.
3623 If you want to compile it as a module, say M here and read
3624 <file:Documentation/modules.txt>. The module will be called
3630 CONFIG_IP6_NF_MATCH_HL
3631 HL matching allows you to match packets based on the hop
3632 limit of the packet.
3634 If you want to compile it as a module, say M here and read
3635 <file:Documentation/modules.txt>. The module will be called
3640 IPv6 Extension Headers Match (EXPERIMENTAL)
3641 CONFIG_IP6_NF_MATCH_IPV6HEADER
3642 This module allows one to match packets based upon
3643 the ipv6 extension headers.
3645 If you want to compile it as a module, say M here and read
3646 <file:Documentation/modules.txt>. The module will be called
3651 SYN flood protection
3653 Normal TCP/IP networking is open to an attack known as "SYN
3654 flooding". This denial-of-service attack prevents legitimate remote
3655 users from being able to connect to your computer during an ongoing
3656 attack and requires very little work from the attacker, who can
3657 operate from anywhere on the Internet.
3659 SYN cookies provide protection against this type of attack. If you
3660 say Y here, the TCP/IP stack will use a cryptographic challenge
3661 protocol known as "SYN cookies" to enable legitimate users to
3662 continue to connect, even when your machine is under attack. There
3663 is no need for the legitimate users to change their TCP/IP software;
3664 SYN cookies work transparently to them. For technical information
3665 about SYN cookies, check out <http://cr.yp.to/syncookies.html>.
3667 If you are SYN flooded, the source address reported by the kernel is
3668 likely to have been forged by the attacker; it is only reported as
3669 an aid in tracing the packets to their actual source and should not
3670 be taken as absolute truth.
3672 SYN cookies may prevent correct error reporting on clients when the
3673 server is really overloaded. If this happens frequently better turn
3676 If you say Y here, note that SYN cookies aren't enabled by default;
3677 you can enable them by saying Y to "/proc file system support" and
3678 "Sysctl support" below and executing the command
3680 echo 1 >/proc/sys/net/ipv4/tcp_syncookies
3682 at boot time after the /proc file system has been mounted.
3688 CONFIG_ALPHA_GENERIC
3689 This is the system type of your hardware. A "generic" kernel will
3690 run on any supported Alpha system. However, if you configure a
3691 kernel for your specific system, it will be faster and smaller.
3693 To find out what type of Alpha system you have, you may want to
3694 check out the Linux/Alpha FAQ, accessible on the WWW from
3695 <http://www.alphalinux.org/>. In summary:
3697 Alcor/Alpha-XLT AS 600
3698 Alpha-XL XL-233, XL-266
3699 AlphaBook1 Alpha laptop
3700 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
3701 Cabriolet AlphaPC64, AlphaPCI64
3703 EB164 EB164 21164 evaluation board
3704 EB64+ EB64+ 21064 evaluation board
3705 EB66 EB66 21066 evaluation board
3706 EB66+ EB66+ 21066 evaluation board
3707 Jensen DECpc 150, DEC 2000 model 300,
3710 Miata Personal Workstation 433a, 433au, 500a,
3711 500au, 600a, or 600au
3713 Noname AXPpci33, UDB (Multia)
3714 Noritake AS 1000A, AS 600A, AS 800
3716 Rawhide AS 1200, AS 4000, AS 4100
3717 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
3719 Sable AS 2000, AS 2100
3723 Wildfire AlphaServer GS 40/80/160/320
3725 If you don't know what to do, choose "generic".
3727 # Most of the information on these variants is from
3728 # <http://www.alphalinux.org/docs/alpha-howto.html>
3731 For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
3732 slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O
3733 Address, CIA) - a 383 pin plastic PGA). It provides a DRAM
3734 controller (256-bit memory bus) and a PCI interface. It also does
3735 all the work required to support an external Bcache and to maintain
3736 memory coherence when a PCI device DMAs into (or out of) memory.
3740 XL-233 and XL-266-based Alpha systems.
3744 Dec AlphaBook1/Burns Alpha-based laptops.
3748 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based
3750 <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.
3753 CONFIG_ALPHA_CABRIOLET
3754 Cabriolet AlphaPC64, AlphaPCI64 systems. Derived from EB64+ but now
3755 baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA
3756 slots, 4 PCI slots (one pair are on a shared slot), uses plug-in
3757 Bcache SIMMs. Requires power supply with 3.3V output.
3761 Various 21264 systems with the tsunami core logic chipset.
3762 API Networks: 264DP, UP2000(+), CS20;
3763 Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40.
3767 EB164 21164 evaluation board from DEC. Uses 21164 and ALCOR. Has
3768 ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is
3769 shared with an ISA slot) and 2 32-bit PCI slots. Uses plus-in
3770 Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD,
3771 MOUSE (PS2 style), RTC/NVRAM. Boot ROM is Flash. PC-AT-sized
3772 motherboard. Requires power supply with 3.3V output.
3776 Uses 21064 or 21064A and APECs. Has ISA and PCI expansion (3 ISA,
3777 2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
3778 ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI
3779 (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),
3780 SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM. PC-AT size.
3781 Runs from standard PC power supply.
3785 A Digital DS group board. Uses 21066 or 21066A. I/O sub-system is
3786 identical to EB64+. Baby PC-AT size. Runs from standard PC power
3787 supply. The EB66 schematic was published as a marketing poster
3788 advertising the 21066 as "the first microprocessor in the world with
3793 Later variant of the EB66 board.
3797 Apparently an obscure OEM single-board computer based on the
3798 Typhoon/Tsunami chipset family. Information on it is scanty.
3802 DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
3803 of the first-generation Alpha systems. A number of these systems
3804 seem to be available on the second- hand market. The Jensen is a
3805 floor-standing tower system which originally used a 150MHz 21064 It
3806 used programmable logic to interface a 486 EISA I/O bridge to the
3811 A technical overview of this board is available at
3812 <http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html>.
3816 The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a,
3817 or 600au). There is an Installation HOWTO for this hardware at
3818 <http://members.brabant.chello.nl/~s.vandereijk/miata.html>.
3822 AlphaServer 1000-based Alpha systems.
3825 CONFIG_ALPHA_NAUTILUS
3826 Alpha systems based on the AMD 751 & ALI 1543C chipsets.
3830 The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia
3831 UDB). This design was produced by Digital's Technical OEM (TOEM)
3832 group. It uses the 21066 processor running at 166MHz or 233MHz. It
3833 is a baby-AT size, and runs from a standard PC power supply. It has
3834 5 ISA slots and 3 PCI slots (one pair are a shared slot). There are
3835 2 versions, with either PS/2 or large DIN connectors for the
3839 CONFIG_ALPHA_NORITAKE
3840 AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based
3844 CONFIG_ALPHA_RAWHIDE
3845 AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines.
3847 <http://www.alphalinux.org/docs/rawhide/4100_install.shtml>.
3850 CONFIG_ALPHA_RUFFIAN
3851 Samsung APC164UX. There is a page on known problems and workarounds
3852 at <http://www.alphalinux.org/faq/FAQ-11.html>.
3856 Digital AlphaServer 2000 and 2100-based systems.
3860 Alpha 11164-based OEM single-board computer.
3863 CONFIG_ALPHA_WILDFIRE
3864 AlphaServer GS 40/80/160/320 SMP based on the EV67 core.
3866 EV5 CPU daughtercard (model 5/xxx)
3868 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
3870 EV5 CPU(s) (model 5/xxx)
3872 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
3874 EV67 (or later) CPU (speed > 600MHz)?
3876 Is this a machine based on the EV67 core? If in doubt, select N here
3877 and the machine will be treated as an EV6.
3879 Use SRM as bootloader
3881 There are two different types of booting firmware on Alphas: SRM,
3882 which is command line driven, and ARC, which uses menus and arrow
3883 keys. Details about the Linux/Alpha booting process are contained in
3884 the Linux/Alpha FAQ, accessible on the WWW from
3885 <http://www.alphalinux.org/>.
3887 The usual way to load Linux on an Alpha machine is to use MILO
3888 (a bootloader that lets you pass command line parameters to the
3889 kernel just like lilo does for the x86 architecture) which can be
3890 loaded either from ARC or can be installed directly as a permanent
3891 firmware replacement from floppy (which requires changing a certain
3892 jumper on the motherboard). If you want to do either of these, say N
3893 here. If MILO doesn't work on your system (true for Jensen
3894 motherboards), you can bypass it altogether and boot Linux directly
3895 from an SRM console; say Y here in order to do that. Note that you
3896 won't be able to boot from an IDE disk using old versions of SRM.
3900 Legacy kernel start address
3901 CONFIG_ALPHA_LEGACY_START_ADDRESS
3902 The 2.4 kernel changed the kernel start address from 0x310000
3903 to 0x810000 to make room for the Wildfire's larger SRM console.
3905 If you're using aboot 0.7 or later, the bootloader will examine the
3906 ELF headers to determine where to transfer control. Unfortunately,
3907 most older bootloaders -- APB or MILO -- hardcoded the kernel start
3908 address rather than examining the ELF headers, and the result is a
3911 Say Y if you have a broken bootloader. Say N if you do not, or if
3912 you wish to run on Wildfire.
3914 Large VMALLOC support
3915 CONFIG_ALPHA_LARGE_VMALLOC
3916 Process creation and other aspects of virtual memory management can
3917 be streamlined if we restrict the kernel to one PGD for all vmalloc
3918 allocations. This equates to about 8GB.
3920 Under normal circumstances, this is so far and above what is needed
3921 as to be laughable. However, there are certain applications (such
3922 as benchmark-grade in-kernel web serving) that can make use of as
3923 much vmalloc space as is available.
3925 Say N unless you know you need gobs and gobs of vmalloc space.
3927 Non-standard serial port support
3928 CONFIG_SERIAL_NONSTANDARD
3929 Say Y here if you have any non-standard serial boards -- boards
3930 which aren't supported using the standard "dumb" serial driver.
3931 This includes intelligent serial boards such as Cyclades,
3932 Digiboards, etc. These are usually used for systems that need many
3933 serial ports because they serve many terminals or dial-in
3936 Note that the answer to this question won't directly affect the
3937 kernel: saying N will just cause the configurator to skip all
3938 the questions about non-standard serial boards.
3940 Most people can say N here.
3942 Extended dumb serial driver options
3943 CONFIG_SERIAL_EXTENDED
3944 If you wish to use any non-standard features of the standard "dumb"
3945 driver, say Y here. This includes HUB6 support, shared serial
3946 interrupts, special multiport support, support for more than the
3947 four COM 1/2/3/4 boards, etc.
3949 Note that the answer to this question won't directly affect the
3950 kernel: saying N will just cause the configurator to skip all
3951 the questions about serial driver options. If unsure, say N.
3953 Support more than 4 serial ports
3954 CONFIG_SERIAL_MANY_PORTS
3955 Say Y here if you have dumb serial boards other than the four
3956 standard COM 1/2/3/4 ports. This may happen if you have an AST
3957 FourPort, Accent Async, Boca (read the Boca mini-HOWTO, available
3958 from <http://www.tldp.org/docs.html#howto>), or other custom
3959 serial port hardware which acts similar to standard serial port
3960 hardware. If you only use the standard COM 1/2/3/4 ports, you can
3961 say N here to save some memory. You can also say Y if you have an
3962 "intelligent" multiport card such as Cyclades, Digiboards, etc.
3964 Support for sharing serial interrupts
3965 CONFIG_SERIAL_SHARE_IRQ
3966 Some serial boards have hardware support which allows multiple dumb
3967 serial ports on the same board to share a single IRQ. To enable
3968 support for this in the serial driver, say Y here.
3970 Auto-detect IRQ on standard ports (unsafe)
3971 CONFIG_SERIAL_DETECT_IRQ
3972 Say Y here if you want the kernel to try to guess which IRQ
3973 to use for your serial port.
3975 This is considered unsafe; it is far better to configure the IRQ in
3976 a boot script using the setserial command.
3980 Support special multiport boards
3981 CONFIG_SERIAL_MULTIPORT
3982 Some multiport serial ports have special ports which are used to
3983 signal when there are any serial ports on the board which need
3984 servicing. Say Y here to enable the serial driver to take advantage
3985 of those special I/O ports.
3987 SGI IP22 Zilog85C30 serial support
3989 If you want to use your IP22's built-in serial ports under Linux,
3992 SGI Newport Console support
3993 CONFIG_SGI_NEWPORT_CONSOLE
3994 Say Y here if you want the console on the Newport aka XL graphics
3995 card of your Indy. Most people say Y here.
3997 SGI DS1286 RTC support
3999 If you say Y here and create a character special file /dev/rtc with
4000 major number 10 and minor number 135 using mknod ("man mknod"), you
4001 will get access to the real time clock built into your computer.
4002 Every SGI has such a clock built in. It reports status information
4003 via the file /proc/rtc and its behaviour is set by various ioctls on
4006 Dallas DS1742 RTC Support
4008 If you say Y here and create a character special file /dev/rtc with
4009 major number 10 and minor number 135 using mknod ("man mknod"), you
4010 will get access to the real time clock present on various Toshiba
4011 MIPS-based boards. It reports status information via the file
4012 /proc/driver/rtc and its behaviour is set by various ioctls on
4013 /dev/rtc or /dev/misc/rtc if using devfs.
4015 For technical information and application notes, please see the
4016 Dallas Semiconductor website:
4017 <http://www.dalsemi.com/quick_view2.cfm?qv_pk=2768>.
4019 This driver is also available as a module ( = code which can be
4020 inserted in and removed from the running kernel whenever you want).
4021 The module is called ds1742.o. If you want to compile it as a module,
4022 say M here and read <file:Documentation/modules.txt>.
4024 Indy/I2 Hardware Watchdog
4026 Hardwaredriver for the Indy's/I2's watchdog. This is a
4027 watchdog timer that will reboot the machine after a 60 second
4028 timer expired and no process has written to /dev/watchdog during
4031 Support the Bell Technologies HUB6 card
4033 Say Y here to enable support in the dumb serial driver to support
4036 PCMCIA serial device support
4037 CONFIG_PCMCIA_SERIAL_CS
4038 Say Y here to enable support for 16-bit PCMCIA serial devices,
4039 including serial port cards, modems, and the modem functions of
4040 multi-function Ethernet/modem cards. (PCMCIA- or PC-cards are
4041 credit-card size devices often used with laptops.)
4043 This driver is also available as a module ( = code which can be
4044 inserted in and removed from the running kernel whenever you want).
4045 The module will be called serial_cs.o. If you want to compile it as
4046 a module, say M here and read <file:Documentation/modules.txt>.
4050 Enable support for the SyncLink PC Card serial adapter, running
4051 asynchronous and HDLC communications up to 512Kbps. The port is
4052 selectable for RS-232, V.35, RS-449, RS-530, and X.21
4054 This driver may be built as a module ( = code which can be
4055 inserted in and removed from the running kernel whenever you want).
4056 The module will be called synclinkmp.o. If you want to do that, say M
4059 ACP Modem (Mwave) support
4061 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
4062 kernel driver and a user level application. Together these components
4063 support direct attachment to public switched telephone networks (PSTNs)
4064 and support selected world wide countries.
4066 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
4067 600, and 770 that include on board ACP modem hardware.
4069 The modem also supports the standard communications port interface
4070 (ttySx) and is compatible with the Hayes AT Command Set.
4072 The user level application needed to use this driver can be found at
4073 the IBM Linux Technology Center (LTC) web site:
4074 <http://www.ibm.com/linux/ltc/>.
4076 If you own one of the above IBM Thinkpads which has the Mwave chipset
4079 This driver is also available as a module ( = code which can be
4080 inserted in and removed from the running kernel whenever you want).
4081 The module will be called mwave.o. If you want to compile it as
4082 a module, say M here and read Documentation/modules.txt.
4084 /dev/agpgart (AGP Support)
4086 AGP (Accelerated Graphics Port) is a bus system mainly used to
4087 connect graphics cards to the rest of the system.
4089 If you have an AGP system and you say Y here, it will be possible to
4090 use the AGP features of your 3D rendering video card. This code acts
4091 as a sort of "AGP driver" for the motherboard's chipset.
4093 If you need more texture memory than you can get with the AGP GART
4094 (theoretically up to 256 MB, but in practice usually 64 or 128 MB
4095 due to kernel allocation issues), you could use PCI accesses
4096 and have up to a couple gigs of texture space.
4098 Note that this is the only means to have XFree4/GLX use
4099 write-combining with MTRR support on the AGP bus. Without it, OpenGL
4100 direct rendering will be a lot slower but still faster than PIO.
4102 You should say Y here if you use XFree86 3.3.6 or 4.x and want to
4103 use GLX or DRI. If unsure, say N.
4105 This driver is available as a module. If you want to compile it as
4106 a module, say M here and read <file:Documentation/modules.txt>. The
4107 module will be called agpgart.o.
4109 Intel 440LX/BX/GX/815/820/830/840/845/850/860 support
4111 This option gives you AGP support for the GLX component of the
4112 XFree86 4.x on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850 and 860 chipsets.
4114 You should say Y here if you use XFree86 3.3.6 or 4.x and want to
4115 use GLX or DRI. If unsure, say N.
4119 This option gives you AGP support for the Intel 460GX chipset. This
4120 chipset, the first to support Intel Itanium processors, is new and
4121 this option is correspondingly a little experimental.
4123 If you don't have a 460GX based machine (such as BigSur) with an AGP
4124 slot then this option isn't going to do you much good. If you're
4125 dying to do Direct Rendering on IA-64, this is what you're looking for.
4127 Intel I810/I815 DC100/I810e support
4129 This option gives you AGP support for the Xserver on the Intel 810
4130 815 and 830m chipset boards for their on-board integrated graphics. This
4131 is required to do any useful video modes with these boards.
4135 This option gives you AGP support for the GLX component of the
4136 XFree86 4.x on VIA MPV3/Apollo Pro chipsets.
4138 You should say Y here if you use XFree86 3.3.6 or 4.x and want to
4139 use GLX or DRI. If unsure, say N.
4141 AMD Irongate, 761, and 762 support
4143 This option gives you AGP support for the GLX component of the
4144 XFree86 4.x on AMD Irongate, 761, and 762 chipsets.
4146 You should say Y here if you use XFree86 3.3.6 or 4.x and want to
4147 use GLX or DRI. If unsure, say N.
4150 This option gives you AGP support for the GLX component of
4151 XFree86 on an AMD Opteron/Athlon64 using the on-CPU GART.
4153 You should say Y here if you use XFree86 3.3.6 or 4.x and want to
4154 use GLX or DRI. If unsure, say N.
4158 This option gives you AGP support for the GLX component of
4159 XFree86 4.x on Silicon Integrated Systems [SiS] chipsets.
4161 Note that 5591/5592 AGP chipsets are NOT specifically supported;
4162 However, the driver works well on these, too.
4164 You should say Y here if you use XFree86 3.3.6 or 4.x and want to
4165 use GLX or DRI. If unsure, say N.
4167 Serverworks LE/HE support
4169 Say Y here to support the Serverworks AGP card. See
4170 <http://www.serverworks.com/> for product descriptions and images.
4172 NVIDIA chipset support
4174 This option gives you AGP support for the GLX component of the
4175 XFree86 4.x on NVIDIA nForce/nForce2 chipsets.
4177 You should say Y here if you use XFree86 3.3.6 or 4.x and want to
4178 use GLX or DRI. If unsure, say N.
4182 This option gives you AGP support for the GLX component of the
4183 XFree86 4.x on the following ALi chipsets. The supported chipsets
4184 include M1541, M1621, M1631, M1632, M1641,M1647,and M1651.
4185 For the ALi-chipset question, ALi suggests you refer to
4186 <http://www.ali.com.tw/eng/support/index.shtml>.
4188 The M1541 chipset can do AGP 1x and 2x, but note that there is an
4189 acknowledged incompatibility with Matrox G200 cards. Due to
4190 timing issues, this chipset cannot do AGP 2x with the G200.
4191 This is a hardware limitation. AGP 1x seems to be fine, though.
4193 You should say Y here if you use XFree86 3.3.6 or 4.x and want to
4194 use GLX or DRI. If unsure, say N.
4197 This option gives you AGP GART support for the HP ZX1 chipset
4198 for IA64 processors.
4201 This option gives you AGP support for the GLX component of
4202 XFree86 4.x on the ATI RadeonIGP family of chipsets.
4204 You should say Y here if you use XFree86 3.3.6 or 4.x and want to
4205 use GLX or DRI. If unsure, say N.
4207 Support for ISA-bus hardware
4209 Find out whether you have ISA slots on your motherboard. ISA is the
4210 name of a bus system, i.e. the way the CPU talks to the other stuff
4211 inside your box. Other bus systems are PCI, EISA, MicroChannel
4212 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
4213 newer boards don't support it. If you have ISA, say Y, otherwise N.
4215 Support for PCI bus hardware
4217 Find out whether you have a PCI motherboard. PCI is the name of a
4218 bus system, i.e. the way the CPU talks to the other stuff inside
4219 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
4220 VESA. If you have PCI, say Y, otherwise N.
4222 The PCI-HOWTO, available from
4223 <http://www.tldp.org/docs.html#howto>, contains valuable
4224 information about which PCI hardware does work under Linux and which
4228 CONFIG_PCI_INTEGRATOR
4229 Find out whether you have a PCI motherboard. PCI is the name of a
4230 bus system, i.e. the way the CPU talks to the other stuff inside
4231 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
4232 VESA. If you have PCI, say Y, otherwise N.
4234 The PCI-HOWTO, available from
4235 <http://www.tldp.org/docs.html#howto>, contains valuable
4236 information about which PCI hardware does work under Linux and which
4241 Find out whether you have a PCI motherboard. PCI is the name of a
4242 bus system, i.e. the way the CPU talks to the other stuff inside
4243 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
4244 VESA. If you have PCI, say Y, otherwise N.
4246 The PCI-HOWTO, available from
4247 <http://www.tldp.org/docs.html#howto>, contains valuable
4248 information about which PCI hardware does work under Linux and which
4251 # Choice: pci_access
4254 On PCI systems, the BIOS can be used to detect the PCI devices and
4255 determine their configuration. However, some old PCI motherboards
4256 have BIOS bugs and may crash if this is done. Also, some embedded
4257 PCI-based systems don't have any BIOS at all. Linux can also try to
4258 detect the PCI hardware directly without using the BIOS.
4260 With this option, you can specify how Linux should detect the PCI
4261 devices. If you choose "BIOS", the BIOS will be used, if you choose
4262 "Direct", the BIOS won't be used, and if you choose "Any", the
4263 kernel will try the direct access method and falls back to the BIOS
4264 if that doesn't work. If unsure, go with the default, which is
4267 PCI device name database
4269 By default, the kernel contains a database of all known PCI device
4270 names to make the information in /proc/pci, /proc/ioports and
4271 similar files comprehensible to the user. This database increases
4272 size of the kernel image by about 80KB, but it gets freed after the
4273 system boots up, so it doesn't take up kernel memory. Anyway, if you
4274 are building an installation floppy or kernel for an embedded system
4275 where kernel image size really matters, you can disable this feature
4276 and you'll get device ID numbers instead of names.
4278 When in doubt, say Y.
4280 Generic PCI hotplug support
4282 Say Y here if you have a motherboard with a PCI Hotplug controller.
4283 This allows you to add and remove PCI cards while the machine is
4284 powered up and running. The file system pcihpfs must be mounted
4285 in order to interact with any PCI Hotplug controllers.
4287 This code is also available as a module ( = code which can be
4288 inserted in and removed from the running kernel whenever you want).
4289 The module will be called pci_hotplug.o. If you want to compile it
4290 as a module, say M here and read <file:Documentation/modules.txt>.
4292 When in doubt, say N.
4294 Compaq PCI Hotplug driver
4295 CONFIG_HOTPLUG_PCI_COMPAQ
4296 Say Y here if you have a motherboard with a Compaq PCI Hotplug
4299 This code is also available as a module ( = code which can be
4300 inserted in and removed from the running kernel whenever you want).
4301 The module will be called cpqphp.o. If you want to compile it
4302 as a module, say M here and read <file:Documentation/modules.txt>.
4304 When in doubt, say N.
4306 PCI Compaq Hotplug controller NVRAM support
4307 CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM
4308 Say Y here if you have a Compaq server that has a PCI Hotplug
4309 controller. This will allow the PCI Hotplug driver to store the PCI
4310 system configuration options in NVRAM.
4312 When in doubt, say N.
4314 ACPI PCI Hotplug driver
4315 CONFIG_HOTPLUG_PCI_ACPI
4316 Say Y here if you have a system that supports PCI Hotplug using
4319 This code is also available as a module ( = code which can be
4320 inserted in and removed from the running kernel whenever you want).
4321 The module will be called acpiphp.o. If you want to compile it
4322 as a module, say M here and read <file:Documentation/modules.txt>.
4324 CONFIG_HOTPLUG_PCI_SHPC
4325 Say Y here if you have a motherboard with a SHPC PCI Hotplug
4328 This code is also available as a module ( = code which can be
4329 inserted in and removed from the running kernel whenever you want).
4330 The module will be called shpchp.o. If you want to compile it
4331 as a module, say M here and read <file:Documentation/modules.txt>.
4333 When in doubt, say N.
4335 CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE
4336 Say Y here if you want to use the polling mechanism for hot-plug
4337 events for early platform testing.
4339 When in doubt, say N.
4341 CONFIG_HOTPLUG_PCI_SHPC_PHPRM_LEGACY
4342 Say Y here for AMD SHPC. You have to select this option if you are
4343 using this driver on platform with AMD SHPC.
4345 When in doubt, say N.
4347 CONFIG_HOTPLUG_PCI_PCIE
4348 Say Y here if you have a motherboard that supports PCI Express Native
4351 This code is also available as a module ( = code which can be
4352 inserted in and removed from the running kernel whenever you want).
4353 The module will be called pciehp.o. If you want to compile it
4354 as a module, say M here and read <file:Documentation/modules.txt>.
4356 When in doubt, say N.
4358 CONFIG_HOTPLUG_PCI_PCIE_POLL_EVENT_MODE
4359 Say Y here if you want to use the polling mechanism for hot-plug
4360 events for early platform testing.
4362 When in doubt, say N.
4366 MicroChannel Architecture is found in some IBM PS/2 machines and
4367 laptops. It is a bus system similar to PCI or ISA. See
4368 <file:Documentation/mca.txt> (and especially the web page given
4369 there) before attempting to build an MCA bus kernel.
4371 Support for EISA-bus hardware
4373 The Extended Industry Standard Architecture (EISA) bus was
4374 developed as an open alternative to the IBM MicroChannel bus.
4376 The EISA bus provided some of the features of the IBM MicroChannel
4377 bus while maintaining backward compatibility with cards made for
4378 the older ISA bus. The EISA bus saw limited use between 1988 and
4379 1995 when it was made obsolete by the PCI bus.
4381 Say Y here if you are building a kernel for an EISA-based machine.
4385 SGI Visual Workstation support
4387 The SGI Visual Workstation series is an IA32-based workstation
4388 based on SGI systems chips with some legacy PC hardware attached.
4389 Say Y here to create a kernel to run on the SGI 320 or 540.
4390 A kernel compiled for the Visual Workstation will not run on other
4391 PC boards and vice versa.
4392 See <file:Documentation/sgi-visws.txt> for more.
4394 SGI Visual Workstation framebuffer support
4396 SGI Visual Workstation support for framebuffer graphics.
4400 The Intelligent Input/Output (I2O) architecture allows hardware
4401 drivers to be split into two parts: an operating system specific
4402 module called the OSM and an hardware specific module called the
4403 HDM. The OSM can talk to a whole range of HDM's, and ideally the
4404 HDM's are not OS dependent. This allows for the same HDM driver to
4405 be used under different operating systems if the relevant OSM is in
4406 place. In order for this to work, you need to have an I2O interface
4407 adapter card in your computer. This card contains a special I/O
4408 processor (IOP), thus allowing high speeds since the CPU does not
4409 have to deal with I/O.
4411 If you say Y here, you will get a choice of interface adapter
4412 drivers and OSM's with the following questions.
4414 This support is also available as a module ( = code which can be
4415 inserted in and removed from the running kernel whenever you want).
4416 If you want to compile it as a module, say M here and read
4417 <file:Documentation/modules.txt>. You will get modules called
4418 i2o_core.o and i2o_config.o.
4424 Say Y for support of PCI bus I2O interface adapters. Currently this
4425 is the only variety supported, so you should say Y.
4427 This support is also available as a module called i2o_pci.o ( = code
4428 which can be inserted in and removed from the running kernel
4429 whenever you want). If you want to compile it as a module, say M
4430 here and read <file:Documentation/modules.txt>.
4434 Include support for the I2O Block OSM. The Block OSM presents disk
4435 and other structured block devices to the operating system.
4437 This support is also available as a module called i2o_block.o ( =
4438 code which can be inserted in and removed from the running kernel
4439 whenever you want). If you want to compile it as a module, say M
4440 here and read <file:Documentation/modules.txt>.
4444 Include support for the LAN OSM. You will also need to include
4445 support for token ring or FDDI if you wish to use token ring or FDDI
4446 I2O cards with this driver.
4448 This support is also available as a module called i2o_lan.o ( = code
4449 which can be inserted in and removed from the running kernel
4450 whenever you want). If you want to compile it as a module, say M
4451 here and read <file:Documentation/modules.txt>.
4455 Allows direct SCSI access to SCSI devices on a SCSI or FibreChannel
4456 I2O controller. You can use both the SCSI and Block OSM together if
4459 This support is also available as a module called i2o_scsi.o ( =
4460 code which can be inserted in and removed from the running kernel
4461 whenever you want). If you want to compile it as a module, say M
4462 here and read <file:Documentation/modules.txt>.
4466 If you say Y here and to "/proc file system support", you will be
4467 able to read I2O related information from the virtual directory
4470 This support is also available as a module called i2o_proc.o ( =
4471 code which can be inserted in and removed from the running kernel
4472 whenever you want). If you want to compile it as a module, say M
4473 here and read <file:Documentation/modules.txt>.
4475 Plug and Play support
4477 Plug and Play (PnP) is a standard for peripherals which allows those
4478 peripherals to be configured by software, e.g. assign IRQ's or other
4479 parameters. No jumpers on the cards are needed, instead the values
4480 are provided to the cards from the BIOS, from the operating system,
4481 or using a user-space utility.
4483 Say Y here if you would like Linux to configure your Plug and Play
4484 devices. You should then also say Y to "ISA Plug and Play support",
4485 below. Alternatively, you can say N here and configure your PnP
4486 devices using the user space utilities contained in the isapnptools
4489 This support is also available as a module ( = code which can be
4490 inserted in and removed from the running kernel whenever you want).
4491 If you want to compile it as a module, say M here and read
4492 <file:Documentation/modules.txt>.
4494 ISA Plug and Play support
4496 Say Y here if you would like support for ISA Plug and Play devices.
4497 Some information is in <file:Documentation/isapnp.txt>.
4499 This support is also available as a module called isapnp.o ( =
4500 code which can be inserted in and removed from the running kernel
4501 whenever you want). If you want to compile it as a module, say M
4502 here and read <file:Documentation/modules.txt>.
4508 Linux uses the PNPBIOS as defined in "Plug and Play BIOS
4509 Specification Version 1.0A May 5, 1994" to autodetect built-in
4510 mainboard resources (e.g. parallel port resources).
4512 Other features (e.g. change resources, ESCD, event notification,
4513 Docking station information, ISAPNP services) are not used.
4515 Note: ACPI is expected to supersede PNPBIOS some day, currently it
4518 See latest pcmcia-cs (stand-alone package) for a nice "lspnp" tools,
4519 or have a look at /proc/bus/pnp.
4523 Support for hot-pluggable devices
4525 Say Y here if you want to plug devices into your computer while
4526 the system is running, and be able to use them quickly. In many
4527 cases, the devices can likewise be unplugged at any time too.
4529 One well known example of this is PCMCIA- or PC-cards, credit-card
4530 size devices such as network cards, modems or hard drives which are
4531 plugged into slots found on all modern laptop computers. Another
4532 example, used on modern desktops as well as laptops, is USB.
4534 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
4535 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
4536 Then your kernel will automatically call out to a user mode "policy
4537 agent" (/sbin/hotplug) to load modules and set up software needed
4538 to use devices as you hotplug them.
4540 PCMCIA/CardBus support
4542 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
4543 computer. These are credit-card size devices such as network cards,
4544 modems or hard drives often used with laptops computers. There are
4545 actually two varieties of these cards: the older 16 bit PCMCIA cards
4546 and the newer 32 bit CardBus cards. If you want to use CardBus
4547 cards, you need to say Y here and also to "CardBus support" below.
4549 To use your PC-cards, you will need supporting software from David
4550 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
4551 for location). Please also read the PCMCIA-HOWTO, available from
4552 <http://www.tldp.org/docs.html#howto>.
4554 This driver is also available as a module ( = code which can be
4555 inserted in and removed from the running kernel whenever you want).
4556 When compiled this way, there will be modules called pcmcia_core.o
4557 and ds.o. If you want to compile it as a module, say M here and
4558 read <file:Documentation/modules.txt>.
4560 CardBus card and (Yenta) bridge support
4562 CardBus is a bus mastering architecture for PC-cards, which allows
4563 for 32 bit PC-cards (the original PCMCIA standard specifies only
4564 a 16 bit wide bus). Many newer PC-cards are actually CardBus cards.
4566 This option enables support for CardBus PC Cards, as well as support
4567 for CardBus host bridges. Virtually all modern PCMCIA bridges are
4568 CardBus compatible. A "bridge" is the hardware inside your computer
4569 that PCMCIA cards are plugged into.
4571 To use your PC-cards, you will need supporting software from David
4572 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
4577 i82092 compatible bridge support
4579 This provides support for the Intel I82092AA PCI-to-PCMCIA bridge device,
4580 found in some older laptops and more commonly in evaluation boards for the
4583 i82365 compatible host bridge support
4585 Say Y here to include support for ISA-bus PCMCIA host bridges that
4586 are register compatible with the Intel i82365. These are found on
4587 older laptops and ISA-bus card readers for desktop systems. A
4588 "bridge" is the hardware inside your computer that PCMCIA cards are
4589 plugged into. If unsure, say N.
4591 Databook TCIC host bridge support
4593 Say Y here to include support for the Databook TCIC family of PCMCIA
4594 host bridges. These are only found on a handful of old systems.
4595 "Bridge" is the name used for the hardware inside your computer that
4596 PCMCIA cards are plugged into. If unsure, say N.
4598 CONFIG_PCMCIA_SIBYTE
4599 Say Y here to include support for the SiByte SOC's built-in PCMCIA
4600 interface. Only ATA cards and CompactFlash are currently
4605 Inter Process Communication is a suite of library functions and
4606 system calls which let processes (running programs) synchronize and
4607 exchange information. It is generally considered to be a good thing,
4608 and some programs won't run unless you say Y here. In particular, if
4609 you want to run the DOS emulator dosemu under Linux (read the
4610 DOSEMU-HOWTO, available from
4611 <http://www.tldp.org/docs.html#howto>), you'll need to say Y
4614 You can find documentation about IPC with "info ipc" and also in
4615 section 6.4 of the Linux Programmer's Guide, available from
4616 <http://www.tldp.org/docs.html#guide>.
4618 BSD Process Accounting
4619 CONFIG_BSD_PROCESS_ACCT
4620 If you say Y here, a user level program will be able to instruct the
4621 kernel (via a special system call) to write process accounting
4622 information to a file: whenever a process exits, information about
4623 that process will be appended to the file by the kernel. The
4624 information includes things such as creation time, owning user,
4625 command name, memory usage, controlling terminal etc. (the complete
4626 list is in the struct acct in <file:include/linux/acct.h>). It is
4627 up to the user level program to do useful things with this
4628 information. This is generally a good idea, so say Y.
4632 The sysctl interface provides a means of dynamically changing
4633 certain kernel parameters and variables on the fly without requiring
4634 a recompile of the kernel or reboot of the system. The primary
4635 interface consists of a system call, but if you say Y to "/proc
4636 file system support", a tree of modifiable sysctl entries will be
4637 generated beneath the /proc/sys directory. They are explained in the
4638 files in <file:Documentation/sysctl/>. Note that enabling this
4639 option will enlarge the kernel by at least 8 KB.
4641 As it is generally a good thing, you should say Y here unless
4642 building a kernel for install/rescue disks or your system is very
4646 Kernel core (/proc/kcore) format
4648 If you enabled support for /proc file system then the file
4649 /proc/kcore will contain the kernel core image. This can be used
4652 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
4654 You have two choices here: ELF and A.OUT. Selecting ELF will make
4655 /proc/kcore appear in ELF core format as defined by the Executable
4656 and Linking Format specification. Selecting A.OUT will choose the
4657 old "a.out" format which may be necessary for some old versions
4658 of binutils or on some architectures.
4660 This is especially useful if you have compiled the kernel with the
4661 "-g" option to preserve debugging information. It is mainly used
4662 for examining kernel data structures on the live kernel so if you
4663 don't understand what this means or are not a kernel hacker, just
4664 leave it at its default value ELF.
4666 Select a.out format for /proc/kcore
4668 Not necessary unless you're using a very out-of-date binutils
4669 version. You probably want KCORE_ELF.
4671 Kernel support for ELF binaries
4673 ELF (Executable and Linkable Format) is a format for libraries and
4674 executables used across different architectures and operating
4675 systems. Saying Y here will enable your kernel to run ELF binaries
4676 and enlarge it by about 13 KB. ELF support under Linux has now all
4677 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
4678 because it is portable (this does *not* mean that you will be able
4679 to run executables from different architectures or operating systems
4680 however) and makes building run-time libraries very easy. Many new
4681 executables are distributed solely in ELF format. You definitely
4684 Information about ELF is contained in the ELF HOWTO available from
4685 <http://www.tldp.org/docs.html#howto>.
4687 If you find that after upgrading from Linux kernel 1.2 and saying Y
4688 here, you still can't run any ELF binaries (they just crash), then
4689 you'll have to install the newest ELF runtime libraries, including
4690 ld.so (check the file <file:Documentation/Changes> for location and
4693 Kernel support for a.out binaries
4695 A.out (Assembler.OUTput) is a set of formats for libraries and
4696 executables used in the earliest versions of UNIX. Linux used the
4697 a.out formats QMAGIC and ZMAGIC until they were replaced with the
4700 As more and more programs are converted to ELF, the use for a.out
4701 will gradually diminish. If you disable this option it will reduce
4702 your kernel by one page. This is not much and by itself does not
4703 warrant removing support. However its removal is a good idea if you
4704 wish to ensure that absolutely none of your programs will use this
4705 older executable format. If you don't know what to answer at this
4706 point then answer Y. If someone told you "You need a kernel with
4707 QMAGIC support" then you'll have to say Y here. You may answer M to
4708 compile a.out support as a module and later load the module when you
4709 want to use a program or library in a.out format. The module will be
4710 called binfmt_aout.o. Saying M or N here is dangerous though,
4711 because some crucial programs on your system might still be in A.OUT
4714 OSF/1 v4 readv/writev compatibility
4716 Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
4717 with v4 shared libraries freely available from Compaq. If you're
4718 going to use shared libraries from Tru64 version 5.0 or later, say N.
4720 Kernel support for Linux/Intel ELF binaries
4722 Say Y here if you want to be able to execute Linux/Intel ELF
4723 binaries just like native Alpha binaries on your Alpha machine. For
4724 this to work, you need to have the emulator /usr/bin/em86 in place.
4726 You can get the same functionality by saying N here and saying Y to
4727 "Kernel support for MISC binaries".
4729 You may answer M to compile the emulation support as a module and
4730 later load the module when you want to use a Linux/Intel binary. The
4731 module will be called binfmt_em86.o. If unsure, say Y.
4733 Kernel support for SOM binaries
4735 SOM is a binary executable format inherited from HP/UX. Say Y here
4736 to be able to load and execute SOM binaries directly.
4738 Kernel support for MISC binaries
4740 If you say Y here, it will be possible to plug wrapper-driven binary
4741 formats into the kernel. You will like this especially when you use
4742 programs that need an interpreter to run like Java, Python or
4743 Emacs-Lisp. It's also useful if you often run DOS executables under
4744 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
4745 <http://www.tldp.org/docs.html#howto>). Once you have
4746 registered such a binary class with the kernel, you can start one of
4747 those programs simply by typing in its name at a shell prompt; Linux
4748 will automatically feed it to the correct interpreter.
4750 You can do other nice things, too. Read the file
4751 <file:Documentation/binfmt_misc.txt> to learn how to use this
4752 feature, and <file:Documentation/java.txt> for information about how
4753 to include Java support.
4755 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
4756 use this part of the kernel.
4758 You may say M here for module support and later load the module when
4759 you have use for it; the module is called binfmt_misc.o. If you
4760 don't know what to answer at this point, say Y.
4762 Kernel support for JAVA binaries
4764 If you say Y here, the kernel will load and execute Java J-code
4765 binaries directly. Note: this option is obsolete and scheduled for
4766 removal, use CONFIG_BINFMT_MISC instead.
4768 Solaris binary emulation
4770 This is experimental code which will enable you to run (many)
4771 Solaris binaries on your SPARC Linux machine.
4773 This code is also available as a module ( = code which can be
4774 inserted in and removed from the running kernel whenever you want).
4775 The module will be called solaris.o. If you want to compile it as a
4776 module, say M here and read <file:Documentation/modules.txt>.
4778 SUN SME environment monitoring
4780 Kernel support for temperature and fan monitoring on Sun SME
4783 This code is also available as a module ( = code which can be
4784 inserted in and removed from the running kernel whenever you want).
4785 The module will be called envctrl.o. If you want to compile it as a
4786 module, say M here and read <file:Documentation/modules.txt>.
4791 This is the processor type of your CPU. This information is used for
4792 optimizing purposes. In order to compile a kernel that can run on
4793 all x86 CPU types (albeit not optimally fast), you can specify
4796 The kernel will not necessarily run on earlier architectures than
4797 the one you have chosen, e.g. a Pentium optimized kernel will run on
4798 a PPro, but not necessarily on a i486.
4800 Here are the settings recommended for greatest speed:
4801 - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
4802 486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels
4803 will run on a 386 class machine.
4804 - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
4805 SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
4806 - "586" for generic Pentium CPUs, possibly lacking the TSC
4807 (time stamp counter) register.
4808 - "Pentium-Classic" for the Intel Pentium.
4809 - "Pentium-MMX" for the Intel Pentium MMX.
4810 - "Pentium-Pro" for the Intel Pentium Pro/Celeron/Pentium II.
4811 - "Pentium-III" for the Intel Pentium III
4812 and Celerons based on the Coppermine core.
4813 - "Pentium-4" for the Intel Pentium 4.
4814 - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
4815 - "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
4816 - "Elan" for the AMD Elan family (Elan SC400/SC410).
4817 - "Crusoe" for the Transmeta Crusoe series.
4818 - "Winchip-C6" for original IDT Winchip.
4819 - "Winchip-2" for IDT Winchip 2.
4820 - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
4821 - "CyrixIII" for VIA Cyrix III or VIA C3.
4822 - "VIA C3-2 for VIA C3-2 "Nehemiah" (model 9 and above).
4824 If you don't know what to do, choose "386".
4828 Select this for a x486 processor, ether Intel or one of the
4829 compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX,
4830 DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or
4833 586/K5/5x86/6x86/6x86MX
4835 Select this for an x586 or x686 processor such as the AMD K5, the
4836 Intel 5x86 or 6x86, or the Intel 6x86MX. This choice does not
4837 assume the RDTSC instruction.
4841 Select this for a Pentium Classic processor with the RDTSC (Read
4842 Time Stamp Counter) instruction for benchmarking.
4846 Select this for a VIA C3 "Nehemiah". Selecting this enables usage of SSE
4847 and tells gcc to treat the CPU as a 686.
4849 Note, this kernel will not boot on older (pre model 9) C3s.
4853 Saying Y here will allow developers with a C180, C200, C240, C360,
4854 J200, J210, and/or a J2240 to test 64-bit kernels by providing a
4855 wrapper for the 32-bit PDC calls. Since the machines which require
4856 this option do not support over 4G of RAM, this option is targeted
4857 for developers of these machines wishing to test changes on both
4858 32-bit and 64-bit configurations.
4864 Saying Y here will allow you to use Linux in text mode through a
4865 display that complies with the generic VGA standard. Virtually
4866 everyone wants that.
4868 The program SVGATextMode can be used to utilize SVGA video cards to
4869 their full potential in text mode. Download it from
4870 <ftp://ibiblio.org/pub/Linux/utils/console/>.
4874 Distribute interrupts on all CPUs by default
4876 This option gives the kernel permission to distribute IRQs across
4877 multiple CPUs. Saying N here will route all IRQs to the first
4878 CPU. Generally SMP PowerMacs can answer Y. SMP IBM CHRP boxes or
4879 Power3 boxes should say N for now.
4881 Video mode selection support
4883 This enables support for text mode selection on kernel startup. If
4884 you want to take advantage of some high-resolution text mode your
4885 card's BIOS offers, but the traditional Linux utilities like
4886 SVGATextMode don't, you can say Y here and set the mode using the
4887 "vga=" option from your boot loader (lilo or loadlin) or set
4888 "vga=ask" which brings up a video mode menu on kernel startup. (Try
4889 "man bootparam" or see the documentation of your boot loader about
4890 how to pass options to the kernel.)
4892 Read the file <file:Documentation/svga.txt> for more information
4893 about the Video mode selection support. If unsure, say N.
4895 Support for frame buffer devices
4897 The frame buffer device provides an abstraction for the graphics
4898 hardware. It represents the frame buffer of some video hardware and
4899 allows application software to access the graphics hardware through
4900 a well-defined interface, so the software doesn't need to know
4901 anything about the low-level (hardware register) stuff.
4903 Frame buffer devices work identically across the different
4904 architectures supported by Linux and make the implementation of
4905 application programs easier and more portable; at this point, an X
4906 server exists which uses the frame buffer device exclusively.
4907 On several non-X86 architectures, the frame buffer device is the
4908 only way to use the graphics hardware.
4910 The device is accessed through special device nodes, usually located
4911 in the /dev directory, i.e. /dev/fb*.
4913 You need an utility program called fbset to make full use of frame
4914 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
4915 and the Framebuffer-HOWTO at
4916 <http://www.tahallah.demon.co.uk/programming/prog.html> for more
4919 Say Y here and to the driver for your graphics board below if you
4920 are compiling a kernel for a non-x86 architecture.
4922 If you are compiling for the x86 architecture, you can say Y if you
4923 want to play with it, but it is not essential. Please note that
4924 running graphical applications that directly touch the hardware
4925 (e.g. an accelerated X server) and that are not frame buffer
4926 device-aware may cause unexpected results. If unsure, say N.
4930 This is the frame buffer device driver for the Acorn VIDC graphics
4931 hardware found in Acorn RISC PCs and other ARM-based machines. If
4936 This is the frame buffer device driver for the Permedia2 AGP frame
4937 buffer card from ASK, aka `Graphic Blaster Exxtreme'. There is a
4939 <http://www.ask.com.hk/product/Permedia%202/permedia2.htm>.
4941 Enable FIFO disconnect feature
4942 CONFIG_FB_PM2_FIFO_DISCONNECT
4943 Support the Permedia2 FIFOI disconnect feature (see CONFIG_FB_PM2).
4945 Generic Permedia2 PCI board support
4947 Say Y to enable support for Permedia2 AGP frame buffer card from
4948 3Dlabs (aka `Graphic Blaster Exxtreme') on the PCI bus.
4950 Phase5 CVisionPPC/BVisionPPC support
4952 Say Y to enable support for the Amiga Phase 5 CVisionPPC BVisionPPC
4953 framebuffer cards. Phase 5 is no longer with us, alas.
4955 Amiga native chipset support
4957 This is the frame buffer device driver for the builtin graphics
4958 chipset found in Amigas.
4960 The driver is also available as a module ( = code which can be
4961 inserted and removed from the running kernel whenever you want). The
4962 module will be called amifb.o. If you want to compile it as a
4963 module, say M here and read <file:Documentation/modules.txt>.
4965 Amiga OCS chipset support
4967 This enables support for the original Agnus and Denise video chips,
4968 found in the Amiga 1000 and most A500's and A2000's. If you intend
4969 to run Linux on any of these systems, say Y; otherwise say N.
4971 Amiga ECS chipset support
4973 This enables support for the Enhanced Chip Set, found in later
4974 A500's, later A2000's, the A600, the A3000, the A3000T and CDTV. If
4975 you intend to run Linux on any of these systems, say Y; otherwise
4978 Amiga AGA chipset support
4980 This enables support for the Advanced Graphics Architecture (also
4981 known as the AGA or AA) Chip Set, found in the A1200, A4000, A4000T
4982 and CD32. If you intend to run Linux on any of these systems, say Y;
4985 Amiga CyberVision support
4987 This enables support for the Cybervision 64 graphics card from
4988 Phase5. Please note that its use is not all that intuitive (i.e. if
4989 you have any questions, be sure to ask!). Say N unless you have a
4990 Cybervision 64 or plan to get one before you next recompile the
4991 kernel. Please note that this driver DOES NOT support the
4992 Cybervision 64 3D card, as they use incompatible video chips.
4994 CyberPro 20x0 support
4996 This enables support for the Integraphics CyberPro 20x0 and 5000
4997 VGA chips used in the Rebel.com Netwinder and other machines.
4998 Say Y if you have a NetWinder or a graphics card containing this
4999 device, otherwise say N.
5001 Amiga CyberVision3D support
5003 This enables support for the Cybervision 64/3D graphics card from
5004 Phase5. Please note that its use is not all that intuitive (i.e. if
5005 you have any questions, be sure to ask!). Say N unless you have a
5006 Cybervision 64/3D or plan to get one before you next recompile the
5007 kernel. Please note that this driver DOES NOT support the older
5008 Cybervision 64 card, as they use incompatible video chips.
5010 Amiga RetinaZ3 support
5012 This enables support for the Retina Z3 graphics card. Say N unless
5013 you have a Retina Z3 or plan to get one before you next recompile
5016 Cirrus Logic generic driver
5018 This enables support for Cirrus Logic GD542x/543x based boards on
5019 Amiga: SD64, Piccolo, Picasso II/II+, Picasso IV, or EGS Spectrum.
5021 If you have a PCI-based system, this enables support for these
5022 chips: GD-543x, GD-544x, GD-5480.
5024 Please read the file <file:Documentation/fb/clgenfb.txt>.
5026 Say N unless you have such a graphics board or plan to get one
5027 before you next recompile the kernel.
5031 Say Y here if you want to run Linux on an MC680x0-based Apollo
5032 Domain workstation such as the DN3500.
5034 Apollo 3c505 "EtherLink Plus" support
5035 CONFIG_APOLLO_ELPLUS
5036 Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
5037 If you don't have one made for Apollos, you can use one from a PC,
5038 except that your Apollo won't be able to boot from it (because the
5039 code in the ROM will be for a PC).
5041 Atari native chipset support
5043 This is the frame buffer device driver for the builtin graphics
5044 chipset found in Ataris.
5046 Amiga FrameMaster II/Rainbow II support
5048 This is the frame buffer device driver for the Amiga FrameMaster
5049 card from BSC (exhibited 1992 but not shipped as a CBM product).
5051 Open Firmware frame buffer device support
5053 Say Y if you want support with Open Firmware for your graphics
5056 S3 Trio frame buffer device support
5058 If you have a S3 Trio say Y. Say N for S3 Virge.
5060 3Dfx Banshee/Voodoo3 display support
5062 This driver supports graphics boards with the 3Dfx Banshee/Voodoo3
5063 chips. Say Y if you have such a graphics board.
5065 The driver is also available as a module ( = code which can be
5066 inserted and removed from the running kernel whenever you want). The
5067 module will be called tdfxfb.o. If you want to compile it as a
5068 module, say M here and read <file:Documentation/modules.txt>.
5072 This driver supports graphics boards with the nVidia Riva/Geforce
5074 Say Y if you have such a graphics board.
5076 The driver is also available as a module ( = code which can be
5077 inserted and removed from the running kernel whenever you want). The
5078 module will be called rivafb.o. If you want to compile it as a
5079 module, say M here and read <file:Documentation/modules.txt>.
5081 Trident Blade/Image support
5083 This driver is supposed to support graphics boards with the
5084 Trident CyberXXXX/Image/CyberBlade chips mostly found in laptops
5085 but also on some motherboards.Read <file:Documentation/fb/tridentfb.txt>
5087 Say Y if you have such a graphics board.
5089 The driver is also available as a module ( = code which can be
5090 inserted and removed from the running kernel whenever you want). The
5091 module will be called tridentfb.o. If you want to compile it as a
5092 module, say M here and read <file:Documentation/modules.txt>.
5094 ATI Mach64 display support
5096 This driver supports graphics boards with the ATI Mach64 chips.
5097 Say Y if you have such a graphics board.
5099 The driver is also available as a module ( = code which can be
5100 inserted and removed from the running kernel whenever you want). The
5101 module will be called atyfb.o. If you want to compile it as a
5102 module, say M here and read <file:Documentation/modules.txt>.
5104 ATI Rage128 display support
5106 This driver supports graphics boards with the ATI Rage128 chips.
5107 Say Y if you have such a graphics board and read
5108 <file:Documentation/fb/aty128fb.txt>.
5110 The driver is also available as a module ( = code which can be
5111 inserted and removed from the running kernel whenever you want). The
5112 module will be called aty128fb.o. If you want to compile it as a
5113 module, say M here and read <file:Documentation/modules.txt>.
5115 Maxine (Personal DECstation) onboard framebuffer support
5117 Support for the onboard framebuffer (1024x768x8) in the Personal
5118 DECstation series (Personal DECstation 5000/20, /25, /33, /50,
5121 PMAG-AA TURBOchannel framebuffer support
5123 Support for the PMAG-AA TURBOchannel framebuffer card (1280x1024x1)
5124 used mainly in the MIPS-based DECstation series.
5126 PMAG-BA TURBOchannel framebuffer support
5128 Support for the PMAG-BA TURBOchannel framebuffer card (1024x864x8)
5129 used mainly in the MIPS-based DECstation series.
5131 PMAGB-B TURBOchannel framebuffer support
5133 Support for the PMAGB-B TURBOchannel framebuffer card used mainly
5134 in the MIPS-based DECstation series. The card is currently only
5135 supported in 1280x1024x8 mode.
5139 Say Y here if you intend to run this kernel on a FutureTV (nee Nexus
5140 Electronics) StrongARM PCI card.
5142 ANAKIN Vehicle Telematics Platform
5144 The Anakin is a StrongArm based SA110 - 2 DIN Vehicle Telematics Platform.
5145 64MB SDRAM - 4 Mb Flash - Compact Flash Interface - 1 MB VRAM
5147 On board peripherals:
5148 * Front display: 400x234 16 bit TFT touchscreen
5149 * External independent second screen interface
5150 * CAN controller SJA1000
5151 * USB host controller
5152 * 6 channel video codec with hardware overlay
5156 Modules interfaced over the Multi Media Extension slots:
5157 * A communication card
5161 * An audio card ( 4 * 40W, AC97 Codec, I2S)
5163 Altera Excalibur XA10 Dev Board
5165 This enables support for Altera's Excalibur XA10 development board.
5166 If you would like to build your kernel to run on one of these boards
5167 then you must say 'Y' here. Otherwise say 'N'
5169 Link-Up Systems LCD support
5171 This driver supports the L7200 Color LCD.
5172 Say Y if you want graphics support.
5174 NeoMagic display support (EXPERIMENTAL)
5176 This driver supports notebooks with NeoMagic PCI chips.
5177 Say Y if you have such a graphics card.
5179 The driver is also available as a module ( = code which can be
5180 inserted and removed from the running kernel whenever you want). The
5181 module will be called neofb.o. If you want to compile it as a
5182 module, say M here and read Documentation/modules.txt.
5184 PowerMac "control" frame buffer device support
5186 This driver supports a frame buffer for the graphics adapter in the
5187 Power Macintosh 7300 and others.
5189 PowerMac "platinum" frame buffer device support
5191 This driver supports a frame buffer for the "platinum" graphics
5192 adapter in some Power Macintoshes.
5194 PowerMac "valkyrie" frame buffer device support
5196 This driver supports a frame buffer for the "valkyrie" graphics
5197 adapter in some Power Macintoshes.
5199 Chips 65550 display support
5201 This is the frame buffer device driver for the Chips & Technologies
5202 65550 graphics chip in PowerBooks.
5204 TGA/SFB+ frame buffer support
5206 This is the frame buffer device driver for generic TGA and SFB+
5207 graphic cards. These include DEC ZLXp-E1, E2 and E3 PCI cards,
5208 also known as PBXGA-A, B and C, and DEC ZLX-E2 and E3 TURBOchannel
5209 cards, also known as PMAGD-B and C. The DEC ZLX-E1 or PMAGD-A card
5210 is currently unsupported. Due to hardware limitations ZLX-E2 and
5211 E3 cards are only supported for DECstation 5000/1xx and Personal
5212 DECstation 5000/xx systems.
5214 Say Y if you have one of those.
5216 VESA VGA graphics console
5218 This is the frame buffer device driver for generic VESA 2.0
5219 compliant graphic cards. The older VESA 1.2 cards are not supported.
5220 You will get a boot time penguin logo at no additional cost. Please
5221 read <file:Documentation/fb/vesafb.txt>. If unsure, say Y.
5223 VGA 16-color planar support
5224 CONFIG_FBCON_VGA_PLANES
5225 This low level frame buffer console driver enable the kernel to use
5226 the 16-color planar modes of the old VGA cards where the bits of
5227 each pixel are separated into 4 planes.
5229 Only answer Y here if you have a (very old) VGA card that isn't VESA
5232 VGA 16-color graphics console
5234 This is the frame buffer device driver for VGA 16 color graphic
5235 cards. Say Y if you have such a card.
5237 This code is also available as a module. If you want to compile it
5238 as a module ( = code which can be inserted in and removed from the
5239 running kernel whenever you want), say M here and read
5240 <file:Documentation/modules.txt>. The module will be called
5243 Generic STI frame buffer device support
5245 STI refers to the HP "Standard Text Interface" which is a set of
5246 BIOS routines contained in a ROM chip in HP PA-RISC based machines.
5247 Enabling this option will implement the linux framebuffer device and
5248 an fbcon color text console using calls to the STI BIOS routines.
5249 The HP framebuffer device is sometimes planar, using a strange memory
5250 layout, and changing the plane mask to create colored pixels
5251 can require a call to the STI routines, so /dev/fb may not actually
5252 be useful. However, on some systems packed pixel formats are supported.
5253 It is sufficient for basic text console functions, including fonts.
5255 You should probably enable this option, unless you are having
5256 trouble getting video when booting the kernel (make sure it isn't
5257 just that you are running the console on the serial port, though).
5258 Really old HP boxes may not have STI, and must use the PDC BIOS
5259 console or the IODC BIOS.
5261 Select other compiled-in fonts
5263 Say Y here if you would like to use fonts other than the default
5264 your frame buffer console usually use.
5266 Note that the answer to this question won't directly affect the
5267 kernel: saying N will just cause the configurator to skip all
5268 the questions about foreign fonts.
5270 If unsure, say N (the default choices are safe).
5274 This is the "high resolution" font for the VGA frame buffer (the one
5275 provided by the VGA text console 80x25 mode.
5279 Support only 8 pixels wide fonts
5280 CONFIG_FBCON_FONTWIDTH8_ONLY
5281 Answer Y here will make the kernel provide only the 8x8 fonts (these
5282 are the less readable).
5286 Sparc console 8x16 font
5288 This is the high resolution console font for Sun machines. Say Y.
5290 Sparc console 12x22 font (not supported by all drivers)
5291 CONFIG_FONT_SUN12x22
5292 This is the high resolution console font for Sun machines with very
5293 big letters (like the letters used in the SPARC PROM). If the
5294 standard font is unreadable for you, say Y, otherwise say N.
5298 This is the "high resolution" font for the VGA frame buffer (the one
5299 provided by the text console 80x50 (and higher) modes).
5301 Note that this is a poor quality font. The VGA 8x16 font is quite a
5304 Given the resolution provided by the frame buffer device, answer N
5307 Mac console 6x11 font (not supported by all drivers)
5309 Small console font with Macintosh-style high-half glyphs. Some Mac
5310 framebuffer drivers don't support this one at all.
5312 Pearl (old m68k) console 8x8 font
5313 CONFIG_FONT_PEARL_8x8
5314 Small console font with PC-style control-character and high-half
5317 Acorn console 8x8 font
5318 CONFIG_FONT_ACORN_8x8
5319 Small console font with PC-style control characters and high-half
5322 Backward compatibility mode for Xpmac
5323 CONFIG_FB_COMPAT_XPMAC
5324 If you use the Xpmac X server (common with mklinux), you'll need to
5325 say Y here to use X. You should consider changing to XFree86 which
5326 includes a server that supports the frame buffer device directly
5329 Hercules (HGA) mono graphics support
5331 Say Y here if you have a Hercules mono graphics card.
5333 This driver is also available as a module ( = code which can be
5334 inserted and removed from the running kernel whenever you want).
5335 The module will be called hgafb.o. If you want to compile it as
5336 a module, say M here and read <file:Documentation/modules.txt>.
5338 As this card technology is 15 years old, most people will answer N
5341 Epson 1355 framebuffer support
5343 Build in support for the SED1355 Epson Research Embedded RAMDAC
5344 LCD/CRT Controller (since redesignated as the S1D13505) as a
5345 framebuffer. Product specs at
5346 <http://www.erd.epson.com/vdc/html/products.htm>.
5348 Dreamcast Frame Buffer support
5350 Say Y here to enable support for the framebuffer on the Sega
5351 Dreamcast. This driver is also available as a module, dcfb.o.
5353 Register Base Address
5354 CONFIG_E1355_REG_BASE
5355 Epson SED1355/S1D13505 LCD/CRT controller register base address.
5357 <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
5360 Framebuffer Base Address
5361 CONFIG_E1355_FB_BASE
5362 Epson SED1355/S1D13505 LCD/CRT controller memory base address. See
5364 <http://www.erd.epson.com/vdc/html/contents/S1D13505.htm> for
5367 NEC PowerVR 2 display support
5369 Say Y here if you have a PowerVR 2 card in your box. If you plan to
5370 run linux on your Dreamcast, you will have to say Y here.
5371 This driver may or may not work on other PowerVR 2 cards, but is
5372 totally untested. Use at your own risk. If unsure, say N.
5374 This driver is also available as a module ( = code which can be
5375 inserted and removed from the running kernel whenever you want).
5376 The module will be called pvr2fb.o. If you want to compile it as
5377 a module, say M here and read <file:Documentation/modules.txt>.
5379 You can pass several parameters to the driver at boot time or at
5380 module load time. The parameters look like "video=pvr2:XXX", where
5381 the meaning of XXX can be found at the end of the main source file
5382 (<file:drivers/video/pvr2fb.c>). Please see the file
5383 <file:Documentation/fb/pvr2fb.txt>.
5386 CONFIG_FB_PVR2_DEBUG
5387 Say Y here if you wish for the pvr2fb driver to print out debugging
5388 messages. Most people will want to say N here. If unsure, you will
5391 Matrox unified accelerated driver
5393 Say Y here if you have a Matrox Millennium, Millennium II, Mystique,
5394 Mystique 220, Productiva G100, Mystique G200, Millennium G200,
5395 Matrox G400, G450 or G550 card in your box. At this time, support for
5396 the G-series digital output is almost non-existant.
5398 This driver is also available as a module ( = code which can be
5399 inserted and removed from the running kernel whenever you want).
5400 The module will be called matroxfb.o. If you want to compile it as
5401 a module, say M here and read <file:Documentation/modules.txt>.
5403 You can pass several parameters to the driver at boot time or at
5404 module load time. The parameters look like "video=matrox:XXX", and
5405 are described in <file:Documentation/fb/matroxfb.txt>.
5407 Matrox Millennium I/II support
5408 CONFIG_FB_MATROX_MILLENIUM
5409 Say Y here if you have a Matrox Millennium or Matrox Millennium II
5410 video card. If you select "Advanced lowlevel driver options" below,
5411 you should check 4 bpp packed pixel, 8 bpp packed pixel, 16 bpp
5412 packed pixel, 24 bpp packed pixel and 32 bpp packed pixel. You can
5413 also use font widths different from 8.
5415 Matrox Mystique support
5416 CONFIG_FB_MATROX_MYSTIQUE
5417 Say Y here if you have a Matrox Mystique or Matrox Mystique 220
5418 video card. If you select "Advanced lowlevel driver options" below,
5419 you should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp
5420 packed pixel and 32 bpp packed pixel. You can also use font widths
5423 CONFIG_FB_MATROX_G450
5424 Say Y here if you have a Matrox G100, G200, G400, G450 or G550 based
5425 video card. If you select "Advanced lowlevel driver options", you
5426 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
5427 pixel and 32 bpp packed pixel. You can also use font widths
5430 If you need support for G400 secondary head, you must first say Y to
5431 "I2C support" and "I2C bit-banging support" in the character devices
5432 section, and then to "Matrox I2C support" and "G400 second head
5433 support" here in the framebuffer section. G450/G550 secondary head
5434 and digital output are supported without additional modules.
5436 The driver starts in monitor mode. You must use the matroxset tool
5437 (available at <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to
5438 swap primary and secondary head outputs, or to change output mode.
5439 Secondary head driver always start in 640x480 resolution and you
5440 must use fbset to change it.
5442 Do not forget that second head supports only 16 and 32 bpp
5443 packed pixels, so it is a good idea to compile them into the kernel
5444 too. You can use only some font widths, as the driver uses generic
5445 painting procedures (the secondary head does not use acceleration
5448 G450/G550 hardware can display TV picture only from secondary CRTC,
5449 and it performs no scaling, so picture must have 525 or 625 lines.
5451 CONFIG_FB_MATROX_G100A
5452 Say Y here if you have a Matrox G100, G200 or G400 based
5453 video card. If you select "Advanced lowlevel driver options", you
5454 should check 8 bpp packed pixel, 16 bpp packed pixel, 24 bpp packed
5455 pixel and 32 bpp packed pixel. You can also use font widths
5458 If you need support for G400 secondary head, you must first say Y to
5459 "I2C support" and "I2C bit-banging support" in the character devices
5460 section, and then to "Matrox I2C support" and "G400 second head
5461 support" here in the framebuffer section.
5463 CONFIG_FB_MATROX_I2C
5464 This drivers creates I2C buses which are needed for accessing the
5465 DDC (I2C) bus present on all Matroxes, an I2C bus which
5466 interconnects Matrox optional devices, like MGA-TVO on G200 and
5467 G400, and the secondary head DDC bus, present on G400 only.
5469 You can say Y or M here if you want to experiment with monitor
5470 detection code. You must say Y or M here if you want to use either
5471 second head of G400 or MGA-TVO on G200 or G400.
5473 If you compile it as module, it will create a module named
5476 Matrox G400 second head support
5477 CONFIG_FB_MATROX_MAVEN
5478 WARNING !!! This support does not work with G450 !!!
5480 Say Y or M here if you want to use a secondary head (meaning two
5481 monitors in parallel) on G400 or MGA-TVO add-on on G200. Secondary
5482 head is not compatible with accelerated XFree 3.3.x SVGA servers -
5483 secondary head output is blanked while you are in X. With XFree
5484 3.9.17 preview you can use both heads if you use SVGA over fbdev or
5485 the fbdev driver on first head and the fbdev driver on second head.
5487 If you compile it as module, two modules are created,
5488 matroxfb_crtc2.o and matroxfb_maven.o. Matroxfb_maven is needed for
5489 both G200 and G400, matroxfb_crtc2 is needed only by G400. You must
5490 also load i2c-matroxfb to get it to run.
5492 The driver starts in monitor mode and you must use the matroxset
5494 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to switch it to
5495 PAL or NTSC or to swap primary and secondary head outputs.
5496 Secondary head driver also always start in 640x480 resolution, you
5497 must use fbset to change it.
5499 Also do not forget that second head supports only 16 and 32 bpp
5500 packed pixels, so it is a good idea to compile them into the kernel
5501 too. You can use only some font widths, as the driver uses generic
5502 painting procedures (the secondary head does not use acceleration
5505 CONFIG_FB_MATROX_PROC
5506 Say Y or M here if you want to access some informations about driver
5507 state through /proc interface.
5509 You should download matrox_pins tool (available at
5510 <ftp://platan.vc.cvut.cz/pub/linux/matrox-latest/>) to get human
5513 CONFIG_FB_MATROX_MULTIHEAD
5514 Say Y here if you have more than one (supported) Matrox device in
5515 your computer and you want to use all of them for different monitors
5516 ("multihead"). If you have only one device, you should say N because
5517 the driver compiled with Y is larger and a bit slower, especially on
5520 If you said M to "Matrox unified accelerated driver" and N here, you
5521 will still be able to use several Matrox devices simultaneously:
5522 insert several instances of the module matroxfb.o into the kernel
5523 with insmod, supplying the parameter "dev=N" where N is 0, 1, etc.
5524 for the different Matrox devices. This method is slightly faster but
5525 uses 40 KB of kernel memory per Matrox card.
5527 There is no need for enabling 'Matrox multihead support' if you have
5528 only one Matrox card in the box.
5530 3Dfx Voodoo Graphics / Voodoo2 frame buffer support
5532 Say Y here if you have a 3Dfx Voodoo Graphics (Voodoo1/sst1) or
5533 Voodoo2 (cvg) based graphics card.
5535 This driver is also available as a module ( = code which can be
5536 inserted and removed from the running kernel whenever you want).
5537 The module will be called sstfb.o. If you want to compile it as
5538 a module, say M here and read Documentation/modules.txt.
5540 WARNING: Do not use any application that uses the 3D engine
5541 (namely glide) while using this driver.
5542 Please read the file Documentation/fb/README-sstfb.txt for supported
5543 options and other important info support.
5545 MDA text console (dual-headed)
5547 Say Y here if you have an old MDA or monochrome Hercules graphics
5548 adapter in your system acting as a second head ( = video card). You
5549 will then be able to use two monitors with your Linux system. Do not
5550 say Y here if your MDA card is the primary card in your system; the
5551 normal VGA driver will handle it.
5553 This driver is also available as a module ( = code which can be
5554 inserted and removed from the running kernel whenever you want).
5555 The module will be called mdacon.o. If you want to compile it as
5556 a module, say M here and read <file:Documentation/modules.txt>.
5560 SBUS and UPA framebuffers
5562 Say Y if you want support for SBUS or UPA based frame buffer device.
5564 Creator/Creator3D support
5566 This is the frame buffer device driver for the Creator and Creator3D
5569 CGsix (GX,TurboGX) support
5571 This is the frame buffer device driver for the CGsix (GX, TurboGX)
5576 This is the frame buffer device driver for the BWtwo frame buffer.
5580 This is the frame buffer device driver for the CGthree frame buffer.
5582 CGfourteen (SX) support
5583 CONFIG_FB_CGFOURTEEN
5584 This is the frame buffer device driver for the CGfourteen frame
5585 buffer on Desktop SPARCsystems with the SX graphics option.
5587 P9100 (Sparcbook 3 only) support
5589 This is the frame buffer device driver for the P9100 card
5590 supported on Sparcbook 3 machines.
5594 This is the frame buffer device driver for the SBUS-based Sun ZX
5595 (leo) frame buffer cards.
5597 IGA 168x display support
5599 This is the framebuffer device for the INTERGRAPHICS 1680 and
5600 successor frame buffer cards.
5602 TCX (SS4/SS5 only) support
5604 This is the frame buffer device driver for the TCX 24/8bit frame
5607 HD64461 Frame Buffer support
5609 This is the frame buffer device driver for the Hitachi HD64461 LCD
5614 This is the frame buffer device driver for the SiS 300, 315 and 330
5615 series chipsets. Documentation available at the maintainer's site
5616 at <http://www.winischhofer.net/linuxsisvga.shtml>.
5618 SIS 300 series support
5620 This enables support for SiS 300 series chipsets (300/305, 540, 630,
5621 630S, 730S). Documentation available at the maintainer's website at
5622 <http://www.winischhofer.net/linuxsisvga.shtml>.
5624 SIS 315/330 series support
5626 This enables support for SiS 315/330 series chipsets (315, 315PRO,
5627 55x, (M)650, 651, (M)661FX, 661MX, 740, (M)741(GX), (M)760, 330).
5628 Documentation available at the maintainer's website at
5629 <http://www.winischhofer.net/linuxsisvga.shtml>.
5631 IMS Twin Turbo display support
5633 The IMS Twin Turbo is a PCI-based frame buffer card bundled with
5634 many Macintosh and compatible computers.
5637 The TX3912 is a Toshiba RISC processor based on the MIPS 3900 core;
5638 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
5640 Say Y here to enable kernel support for the on-board framebuffer.
5642 Virtual Frame Buffer support (ONLY FOR TESTING!)
5644 This is a `virtual' frame buffer device. It operates on a chunk of
5645 unswappable kernel memory instead of on the memory of a graphics
5646 board. This means you cannot see any output sent to this frame
5647 buffer device, while it does consume precious memory. The main use
5648 of this frame buffer device is testing and debugging the frame
5649 buffer subsystem. Do NOT enable it for normal systems! To protect
5650 the innocent, it has to be enabled explicitly at boot time using the
5651 kernel option `video=vfb:'.
5653 This driver is also available as a module ( = code which can be
5654 inserted and removed from the running kernel whenever you want). The
5655 module will be called vfb.o. If you want to compile it as a module,
5656 say M here and read <file:Documentation/modules.txt>.
5660 Mach64 CT/VT/GT/LT (incl. 3D RAGE) support
5662 Say Y here to support use of ATI's 64-bit Rage boards (or other
5663 boards based on the Mach64 CT, VT, GT, and LT chipsets) as a
5664 framebuffer device. The ATI product support page for these boards
5665 is at <http://support.ati.com/products/pc/mach64/>.
5667 Sony Vaio Picturebook laptop LCD panel support
5668 CONFIG_FB_ATY_CT_VAIO_LCD
5669 Say Y here if you want to use the full width of the Sony Vaio
5670 Picturebook laptops LCD panels (you will get a 128x30 console).
5672 Note that you need to activate this mode using the 'vga=0x301'
5673 option from your boot loader (lilo or loadlin). See the
5674 documentation of your boot loader about how to pass options to the
5679 Say Y here to support use of the ATI Mach64 Graphics Expression
5680 board (or other boards based on the Mach64 GX chipset) as a
5681 framebuffer device. The ATI product support page for these boards
5683 <http://support.ati.com/products/pc/mach64/graphics_xpression.html>.
5685 Mach64 Generic LCD support
5686 CONFIG_FB_ATY_GENERIC_LCD
5687 Enabling this option enables the Atyfb driver to drive LCD panels. It
5688 will autodetect the resulution and format of your display and emulate
5689 other resolutions using the hardware stretcher on the chip.
5690 Say Y here if you have computer with a Rage LT Pro, Rage Mobility M1,
5691 Rage XC or Rage XL chip and a laptop LCD display or any other LCD display
5692 that needs to be digitally driven. It is not necessary to enable this
5693 option if you are using an LCD display with a normal VGA connector,
5694 but it won't hurt if you do.
5696 ATI Radeon display support
5698 Choose this option if you want to use an ATI Radeon graphics card as
5699 a framebuffer device. There are both PCI and AGP versions. You
5700 don't need to choose this to run the Radeon in plain VGA mode.
5701 There is a product page at
5702 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
5706 This is a framebuffer device for the SA-1100 LCD Controller.
5707 See <http://www.linux-fbdev.org/> for information on framebuffer
5710 If you plan to use the LCD display with your SA-1100 system, say
5713 Advanced low level driver options
5714 CONFIG_FBCON_ADVANCED
5715 The frame buffer console uses character drawing routines that are
5716 tailored to the specific organization of pixels in the memory of
5717 your graphics hardware. These are called the low level frame buffer
5718 console drivers. Note that they are used for text console output
5719 only; they are NOT needed for graphical applications.
5721 If you say N here, the needed low level drivers are automatically
5722 enabled, depending on what frame buffer devices you selected above.
5723 This is recommended for most users.
5725 If you say Y here, you have more fine-grained control over which low
5726 level drivers are enabled. You can e.g. leave out low level drivers
5727 for color depths you do not intend to use for text consoles.
5729 Low level frame buffer console drivers can be modules ( = code which
5730 can be inserted and removed from the running kernel whenever you
5731 want). The modules will be called fbcon-*.o. If you want to compile
5732 (some of) them as modules, read <file:Documentation/modules.txt>.
5738 This is the low level frame buffer console driver for monochrome
5739 (2 colors) packed pixels.
5741 2 bpp packed pixels support
5743 This is the low level frame buffer console driver for 2 bits per
5744 pixel (4 colors) packed pixels.
5746 4 bpp packed pixels support
5748 This is the low level frame buffer console driver for 4 bits per
5749 pixel (16 colors) packed pixels.
5751 8 bpp packed pixels support
5753 This is the low level frame buffer console driver for 8 bits per
5754 pixel (256 colors) packed pixels.
5756 16 bpp packed pixels support
5758 This is the low level frame buffer console driver for 15 or 16 bits
5759 per pixel (32K or 64K colors, also known as `hicolor') packed
5762 24 bpp packed pixels support
5764 This is the low level frame buffer console driver for 24 bits per
5765 pixel (16M colors, also known as `truecolor') packed pixels. It is
5766 NOT for `sparse' 32 bits per pixel mode.
5768 32 bpp packed pixels support
5770 This is the low level frame buffer console driver for 32 bits per
5771 pixel (16M colors, also known as `truecolor') sparse packed pixels.
5773 Amiga bitplanes support
5775 This is the low level frame buffer console driver for 1 to 8
5776 bitplanes (2 to 256 colors) on Amiga.
5778 Amiga interleaved bitplanes support
5780 This is the low level frame buffer console driver for 1 to 8
5781 interleaved bitplanes (2 to 256 colors) on Amiga.
5783 Atari interleaved bitplanes (2 planes) support
5784 CONFIG_FBCON_IPLAN2P2
5785 This is the low level frame buffer console driver for 2 interleaved
5786 bitplanes (4 colors) on Atari.
5788 Atari interleaved bitplanes (4 planes) support
5789 CONFIG_FBCON_IPLAN2P4
5790 This is the low level frame buffer console driver for 4 interleaved
5791 bitplanes (16 colors) on Atari.
5793 Atari interleaved bitplanes (8 planes) support
5794 CONFIG_FBCON_IPLAN2P8
5795 This is the low level frame buffer console driver for 8 interleaved
5796 bitplanes (256 colors) on Atari.
5798 Mac variable bpp packed pixels support
5800 This is the low level frame buffer console driver for 1/2/4/8/16/32
5801 bits per pixel packed pixels on Mac. It supports variable font
5802 widths for low resolution screens.
5804 Permedia3 support (EXPERIMENTAL)
5806 This is the frame buffer device driver for the 3DLabs Permedia3
5807 chipset, used in Formac ProFormance III, 3DLabs Oxygen VX1 &
5808 similar boards, 3DLabs Permedia3 Create!, Appian Jeronimo 2000
5809 and maybe other boards.
5811 HGA monochrome support
5813 This is the low level frame buffer console driver for Hercules mono
5816 VGA characters/attributes support
5818 This is the low level frame buffer console driver for VGA text mode;
5819 it is used by frame buffer device drivers that support VGA text
5822 Parallel-port support
5824 If you want to use devices connected to your machine's parallel port
5825 (the connector at the computer with 25 holes), e.g. printer, ZIP
5826 drive, PLIP link (Parallel Line Internet Protocol is mainly used to
5827 create a mini network by connecting the parallel ports of two local
5828 machines) etc., then you need to say Y here; please read
5829 <file:Documentation/parport.txt> and
5830 <file:drivers/parport/BUGS-parport>.
5832 For extensive information about drivers for many devices attaching
5833 to the parallel port see <http://www.torque.net/linux-pp.html> on
5836 It is possible to share a single parallel port among several devices
5837 and it is safe to compile all the corresponding drivers into the
5838 kernel. If you want to compile parallel port support as a module
5839 ( = code which can be inserted in and removed from the running
5840 kernel whenever you want), say M here and read
5841 <file:Documentation/modules.txt>. The module will be called
5842 parport.o. If you have more than one parallel port and want to
5843 specify which port and IRQ to be used by this driver at module load
5844 time, take a look at <file:Documentation/parport.txt>.
5850 You should say Y here if you have a PC-style parallel port. All IBM
5851 PC compatible computers and some Alphas have PC-style parallel
5854 This code is also available as a module. If you want to compile it
5855 as a module ( = code which can be inserted in and removed from the
5856 running kernel whenever you want), say M here and read
5857 <file:Documentation/modules.txt>. The module will be called
5862 Parallel+serial PCI multi-IO card support
5863 CONFIG_PARPORT_SERIAL
5864 This adds support for multi-IO PCI cards that have parallel and
5865 serial ports. You should say Y or M here. If you say M, the module
5866 will be called parport_serial.o.
5868 Use FIFO/DMA if available
5869 CONFIG_PARPORT_PC_FIFO
5870 Many parallel port chipsets provide hardware that can speed up
5871 printing. Say Y here if you want to take advantage of that.
5873 As well as actually having a FIFO, or DMA capability, the kernel
5874 will need to know which IRQ the parallel port has. By default,
5875 parallel port interrupts will not be used, and so neither will the
5876 FIFO. See <file:Documentation/parport.txt> to find out how to
5877 specify which IRQ/DMA to use.
5879 SuperIO chipset support
5880 CONFIG_PARPORT_PC_SUPERIO
5881 Saying Y here enables some probes for Super-IO chipsets in order to
5882 find out things like base addresses, IRQ lines and DMA channels. It
5885 Support for PCMCIA management for PC-style ports
5886 CONFIG_PARPORT_PC_PCMCIA
5887 Say Y here if you need PCMCIA support for your PC-style parallel
5888 ports. If unsure, say N.
5890 This driver is also available as a module ( = code which can be
5891 inserted in and removed from the running kernel whenever you want).
5892 If you want to compile it as a module, say M here and read
5893 <file:Documentation/modules.txt>. The module will be called
5896 Support foreign hardware
5897 CONFIG_PARPORT_OTHER
5898 Say Y here if you want to be able to load driver modules to support
5899 other non-standard types of parallel ports. This causes a
5900 performance loss, so most people say N.
5902 Amiga built-in parallel port support
5903 CONFIG_PARPORT_AMIGA
5904 Say Y here if you need support for the parallel port hardware on
5905 Amiga machines. This code is also available as a module (say M),
5906 called parport_amiga.o. If in doubt, saying N is the safe plan.
5908 Atari built-in parallel port support
5909 CONFIG_PARPORT_ATARI
5910 Say Y here if you need support for the parallel port hardware on
5911 Atari machines. This code is also available as a module (say M),
5912 called parport_atari.o. If in doubt, saying N is the safe plan.
5914 Multiface III parallel port support
5916 Say Y here if you need parallel port support for the MFC3 card.
5917 This code is also available as a module (say M), called
5918 parport_mfc3.o. If in doubt, saying N is the safe plan.
5920 Support IEEE 1284 status readback
5921 CONFIG_PRINTER_READBACK
5922 If you have a device on your parallel port that support this
5923 protocol, this option will allow the device to report its status. It
5926 IEEE 1284 transfer modes
5928 If you have a printer that supports status readback or device ID, or
5929 want to use a device that uses enhanced parallel port transfer modes
5930 such as EPP and ECP, say Y here to enable advanced IEEE 1284
5931 transfer modes. Also say Y if you want device ID information to
5932 appear in /proc/sys/dev/parport/*/autoprobe*. It is safe to say N.
5934 Enable loadable module support
5936 Kernel modules are small pieces of compiled code which can be
5937 inserted in or removed from the running kernel, using the programs
5938 insmod and rmmod. This is described in the file
5939 <file:Documentation/modules.txt>, including the fact that you have
5940 to say "make modules" in order to compile the modules that you chose
5941 during kernel configuration. Modules can be device drivers, file
5942 systems, binary executable formats, and so on. If you think that you
5943 may want to make use of modules with this kernel in the future, then
5944 say Y here. If unsure, say Y.
5946 Set version information on all symbols for modules
5948 Usually, modules have to be recompiled whenever you switch to a new
5949 kernel. Saying Y here makes it possible, and safe, to use the
5950 same modules even after compiling a new kernel; this requires the
5951 program modprobe. All the software needed for module support is in
5952 the modutils package (check the file <file:Documentation/Changes>
5953 for location and latest version). NOTE: if you say Y here but don't
5954 have the program genksyms (which is also contained in the above
5955 mentioned modutils package), then the building of your kernel will
5956 fail. If you are going to use modules that are generated from
5957 non-kernel sources, you would benefit from this option. Otherwise
5958 it's not that important. So, N ought to be a safe bet.
5960 Kernel module loader support
5962 Normally when you have selected some drivers and/or file systems to
5963 be created as loadable modules, you also have the responsibility to
5964 load the corresponding modules (using the programs insmod or
5965 modprobe) before you can use them. If you say Y here however, the
5966 kernel will be able to load modules for itself: when a part of the
5967 kernel needs a module, it runs modprobe with the appropriate
5968 arguments, thereby loading the module if it is available. (This is a
5969 replacement for kerneld.) Say Y here and read about configuring it
5970 in <file:Documentation/kmod.txt>.
5974 Normally, the kernel maintains an internal cache which maps IP
5975 addresses to hardware addresses on the local network, so that
5976 Ethernet/Token Ring/ etc. frames are sent to the proper address on
5977 the physical networking layer. For small networks having a few
5978 hundred directly connected hosts or less, keeping this address
5979 resolution (ARP) cache inside the kernel works well. However,
5980 maintaining an internal ARP cache does not work well for very large
5981 switched networks, and will use a lot of kernel memory if TCP/IP
5982 connections are made to many machines on the network.
5984 If you say Y here, the kernel's internal ARP cache will never grow
5985 to more than 256 entries (the oldest entries are expired in a LIFO
5986 manner) and communication will be attempted with the user space ARP
5987 daemon arpd. Arpd then answers the address resolution request either
5988 from its own cache or by asking the net.
5990 This code is experimental and also obsolete. If you want to use it,
5991 you need to find a version of the daemon arpd on the net somewhere,
5992 and you should also say Y to "Kernel/User network link driver",
5993 below. If unsure, say N.
5997 These are the protocols used on the Internet and on most local
5998 Ethernets. It is highly recommended to say Y here (this will enlarge
5999 your kernel by about 144 KB), since some programs (e.g. the X window
6000 system) use TCP/IP even if your machine is not connected to any
6001 other computer. You will get the so-called loopback device which
6002 allows you to ping yourself (great fun, that!).
6004 For an excellent introduction to Linux networking, please read the
6005 NET-3-HOWTO, available from
6006 <http://www.tldp.org/docs.html#howto>.
6008 This option is also necessary if you want to use the full power of
6009 term (term is a program which gives you almost full Internet
6010 connectivity if you have a regular dial up shell account on some
6011 Internet connected Unix computer; for more information, read
6012 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
6014 If you say Y here and also to "/proc file system support" and
6015 "Sysctl support" below, you can change various aspects of the
6016 behaviour of the TCP/IP code by writing to the (virtual) files in
6017 /proc/sys/net/ipv4/*; the options are explained in the file
6018 <file:Documentation/networking/ip-sysctl.txt>.
6020 Short answer: say Y.
6024 This is code for addressing several networked computers at once,
6025 enlarging your kernel by about 2 KB. You need multicasting if you
6026 intend to participate in the MBONE, a high bandwidth network on top
6027 of the Internet which carries audio and video broadcasts. More
6028 information about the MBONE is on the WWW at
6029 <http://www-itg.lbl.gov/mbone/>. Information about the multicast
6030 capabilities of the various network cards is contained in
6031 <file:Documentation/networking/multicast.txt>. For most people, it's
6035 CONFIG_IP_ADVANCED_ROUTER
6036 If you intend to run your Linux box mostly as a router, i.e. as a
6037 computer that forwards and redistributes network packets, say Y; you
6038 will then be presented with several options that allow more precise
6039 control about the routing process.
6041 The answer to this question won't directly affect the kernel:
6042 answering N will just cause the configurator to skip all the
6043 questions about advanced routing.
6045 Note that your box can only act as a router if you enable IP
6046 forwarding in your kernel; you can do that by saying Y to "/proc
6047 file system support" and "Sysctl support" below and executing the
6050 echo "1" > /proc/sys/net/ipv4/ip_forward
6052 at boot time after the /proc file system has been mounted.
6054 If you turn on IP forwarding, you will also get the rp_filter, which
6055 automatically rejects incoming packets if the routing table entry
6056 for their source address doesn't match the network interface they're
6057 arriving on. This has security advantages because it prevents the
6058 so-called IP spoofing, however it can pose problems if you use
6059 asymmetric routing (packets from you to a host take a different path
6060 than packets from that host to you) or if you operate a non-routing
6061 host which has several IP addresses on different interfaces. To turn
6064 echo 0 > /proc/sys/net/ipv4/conf/<device>/rp_filter
6066 echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
6068 If unsure, say N here.
6071 CONFIG_IP_MULTIPLE_TABLES
6072 Normally, a router decides what to do with a received packet based
6073 solely on the packet's final destination address. If you say Y here,
6074 the Linux router will also be able to take the packet's source
6075 address into account. Furthermore, if you also say Y to "Use TOS
6076 value as routing key" below, the TOS (Type-Of-Service) field of the
6077 packet can be used for routing decisions as well. In addition, if
6078 you say Y here and to "Fast network address translation" below,
6079 the router will also be able to modify source and destination
6080 addresses of forwarded packets.
6082 If you are interested in this, please see the preliminary
6083 documentation at <http://www.compendium.com.ar/policy-routing.txt>
6084 and <ftp://post.tepkom.ru/pub/vol2/Linux/docs/advanced-routing.tex>.
6085 You will need supporting software from
6086 <ftp://ftp.inr.ac.ru/ip-routing/>.
6090 Equal cost multipath
6091 CONFIG_IP_ROUTE_MULTIPATH
6092 Normally, the routing tables specify a single action to be taken in
6093 a deterministic manner for a given packet. If you say Y here
6094 however, it becomes possible to attach several actions to a packet
6095 pattern, in effect specifying several alternative paths to travel
6096 for those packets. The router considers all these paths to be of
6097 equal "cost" and chooses one of them in a non-deterministic fashion
6098 if a matching packet arrives.
6100 Use TOS value as routing key
6102 The header of every IP packet carries a TOS (Type Of Service) value
6103 with which the packet requests a certain treatment, e.g. low
6104 latency (for interactive traffic), high throughput, or high
6105 reliability. If you say Y here, you will be able to specify
6106 different routes for packets with different TOS values.
6108 Use netfilter MARK value as routing key
6109 CONFIG_IP_ROUTE_FWMARK
6110 If you say Y here, you will be able to specify different routes for
6111 packets with different mark values (see iptables(8), MARK target).
6113 Verbose route monitoring
6114 CONFIG_IP_ROUTE_VERBOSE
6115 If you say Y here, which is recommended, then the kernel will print
6116 verbose messages regarding the routing, for example warnings about
6117 received packets which look strange and could be evidence of an
6118 attack or a misconfigured system somewhere. The information is
6119 handled by the klogd daemon which is responsible for kernel messages
6122 Fast network address translation
6124 If you say Y here, your router will be able to modify source and
6125 destination addresses of packets that pass through it, in a manner
6126 you specify. General information about Network Address Translation
6127 can be gotten from the document
6128 <http://www.csn.tu-chemnitz.de/~mha/linux-ip-nat/diplom/nat.html>.
6130 Kernel level IP autoconfiguration
6132 This enables automatic configuration of IP addresses of devices and
6133 of the routing table during kernel boot, based on either information
6134 supplied on the kernel command line or by BOOTP or RARP protocols.
6135 You need to say Y only for diskless machines requiring network
6136 access to boot (in which case you want to say Y to "Root file system
6137 on NFS" as well), because all other machines configure the network
6138 in their startup scripts.
6142 If you want your Linux box to mount its whole root file system (the
6143 one containing the directory /) from some other computer over the
6144 net via NFS and you want the IP address of your computer to be
6145 discovered automatically at boot time using the BOOTP protocol (a
6146 special protocol designed for doing this job), say Y here. In case
6147 the boot ROM of your network card was designed for booting Linux and
6148 does BOOTP itself, providing all necessary information on the kernel
6149 command line, you can say N here. If unsure, say Y. Note that if you
6150 want to use BOOTP, a BOOTP server must be operating on your network.
6151 Read <file:Documentation/nfsroot.txt> for details.
6155 If you want your Linux box to mount its whole root file system (the
6156 one containing the directory /) from some other computer over the
6157 net via NFS and you want the IP address of your computer to be
6158 discovered automatically at boot time using the DHCP protocol (a
6159 special protocol designed for doing this job), say Y here. In case
6160 the boot ROM of your network card was designed for booting Linux and
6161 does DHCP itself, providing all necessary information on the kernel
6162 command line, you can say N here.
6164 If unsure, say Y. Note that if you want to use DHCP, a DHCP server
6165 must be operating on your network. Read
6166 <file:Documentation/nfsroot.txt> for details.
6170 If you want your Linux box to mount its whole root file system (the
6171 one containing the directory /) from some other computer over the
6172 net via NFS and you want the IP address of your computer to be
6173 discovered automatically at boot time using the RARP protocol (an
6174 older protocol which is being obsoleted by BOOTP and DHCP), say Y
6175 here. Note that if you want to use RARP, a RARP server must be
6176 operating on your network. Read <file:Documentation/nfsroot.txt> for
6181 Tunneling means encapsulating data of one protocol type within
6182 another protocol and sending it over a channel that understands the
6183 encapsulating protocol. This particular tunneling driver implements
6184 encapsulation of IP within IP, which sounds kind of pointless, but
6185 can be useful if you want to make your (or some other) machine
6186 appear on a different network than it physically is, or to use
6187 mobile-IP facilities (allowing laptops to seamlessly move between
6188 networks without changing their IP addresses).
6190 Saying Y to this option will produce two modules ( = code which can
6191 be inserted in and removed from the running kernel whenever you
6192 want). Most people won't need this and can say N.
6194 This driver is also available as a module ( = code which can be
6195 inserted in and removed from the running kernel whenever you want).
6196 If you want to compile it as a module, say M here and read
6197 <file:Documentation/modules.txt>. The module will be called
6202 Tunneling means encapsulating data of one protocol type within
6203 another protocol and sending it over a channel that understands the
6204 encapsulating protocol. This particular tunneling driver implements
6205 GRE (Generic Routing Encapsulation) and at this time allows
6206 encapsulating of IPv4 or IPv6 over existing IPv4 infrastructure.
6207 This driver is useful if the other endpoint is a Cisco router: Cisco
6208 likes GRE much better than the other Linux tunneling driver ("IP
6209 tunneling" above). In addition, GRE allows multicast redistribution
6212 This driver is also available as a module ( = code which can be
6213 inserted in and removed from the running kernel whenever you want).
6214 If you want to compile it as a module, say M here and read
6215 <file:Documentation/modules.txt>. The module will be called
6218 Broadcast GRE over IP
6219 CONFIG_NET_IPGRE_BROADCAST
6220 One application of GRE/IP is to construct a broadcast WAN (Wide Area
6221 Network), which looks like a normal Ethernet LAN (Local Area
6222 Network), but can be distributed all over the Internet. If you want
6223 to do that, say Y here and to "IP multicast routing" below.
6225 IP multicast routing
6227 This is used if you want your machine to act as a router for IP
6228 packets that have several destination addresses. It is needed on the
6229 MBONE, a high bandwidth network on top of the Internet which carries
6230 audio and video broadcasts. In order to do that, you would most
6231 likely run the program mrouted. Information about the multicast
6232 capabilities of the various network cards is contained in
6233 <file:Documentation/networking/multicast.txt>. If you haven't heard
6234 about it, you don't need it.
6236 PIM-SM version 1 support
6238 Kernel side support for Sparse Mode PIM (Protocol Independent
6239 Multicast) version 1. This multicast routing protocol is used widely
6240 because Cisco supports it. You need special software to use it
6241 (pimd-v1). Please see <http://netweb.usc.edu/pim/> for more
6242 information about PIM.
6244 Say Y if you want to use PIM-SM v1. Note that you can say N here if
6245 you just want to use Dense Mode PIM.
6247 PIM-SM version 2 support
6249 Kernel side support for Sparse Mode PIM version 2. In order to use
6250 this, you need an experimental routing daemon supporting it (pimd or
6251 gated-5). This routing protocol is not used widely, so say N unless
6252 you want to play with it.
6256 If you say Y here, you will include support for Unix domain sockets;
6257 sockets are the standard Unix mechanism for establishing and
6258 accessing network connections. Many commonly used programs such as
6259 the X Window system and syslog use these sockets even if your
6260 machine is not connected to any network. Unless you are working on
6261 an embedded system or something similar, you therefore definitely
6264 However, the socket support is also available as a module ( = code
6265 which can be inserted in and removed from the running kernel
6266 whenever you want). If you want to compile it as a module, say M
6267 here and read <file:Documentation/modules.txt>. The module will be
6268 called unix.o. If you try building this as a module and you have
6269 said Y to "Kernel module loader support" above, be sure to add
6270 'alias net-pf-1 unix' to your /etc/modules.conf file. Note that
6271 several important services won't work correctly if you say M here
6272 and then neglect to load the module.
6274 Say Y unless you know what you are doing.
6278 This is experimental support for the next version of the Internet
6279 Protocol: IP version 6 (also called IPng "IP next generation").
6280 Features of this new protocol include: expanded address space,
6281 authentication and privacy, and seamless interoperability with the
6282 current version of IP (IP version 4). For general information about
6283 IPv6, see <http://playground.sun.com/pub/ipng/html/ipng-main.html>;
6284 for specific information about IPv6 under Linux read the HOWTO at
6285 <http://www.bieringer.de/linux/IPv6/> and the file net/ipv6/README
6286 in the kernel source.
6288 If you want to use IPv6, please upgrade to the newest net-tools as
6289 given in <file:Documentation/Changes>. You will still be able to do
6290 regular IPv4 networking as well.
6292 This protocol support is also available as a module ( = code which
6293 can be inserted in and removed from the running kernel whenever you
6294 want). The module will be called ipv6.o. If you want to compile it
6295 as a module, say M here and read <file:Documentation/modules.txt>.
6297 It is safe to say N here for now.
6299 The SCTP Protocol (EXPERIMENTAL)
6301 Stream Control Transmission Protocol
6303 From RFC 2960 (http://www.ietf.org/rfc/rfc2960.txt)
6305 "SCTP is a reliable transport protocol operating on top of a
6306 connectionless packet network such as IP. It offers the following
6307 services to its users:
6309 -- acknowledged error-free non-duplicated transfer of user data,
6310 -- data fragmentation to conform to discovered path MTU size,
6311 -- sequenced delivery of user messages within multiple streams,
6312 with an option for order-of-arrival delivery of individual user
6314 -- optional bundling of multiple user messages into a single SCTP
6316 -- network-level fault tolerance through supporting of multi-
6317 homing at either or both ends of an association."
6319 This protocol support is also available as a module ( = code which
6320 can be inserted in and removed from the running kernel whenever you
6321 want). The module will be called sctp. If you want to compile it
6322 as a module, say M here and read <file:Documentation/modules.txt>.
6326 SCTP: Debug messages
6328 If you say Y, this will enable verbose debugging messages.
6330 If unsure, say N. However, if you are running into problems, use
6331 this option to gather detailed trace information
6333 SCTP: Debug object counts
6334 CONFIG_SCTP_DBG_OBJCNT
6335 If you say Y, this will enable debugging support for counting the
6336 type of objects that are currently allocated. This is useful for
6337 identifying memory leaks. If the /proc filesystem is enabled this
6338 debug information can be viewed by
6339 'cat /proc/net/sctp/sctp_dbg_objcnt'
6344 SCTP: HMAC algorithm
6345 CONFIG_SCTP_HMAC_NONE
6346 Choose an HMAC algorithm to be used during association establishment.
6347 It can be one of SHA1, MD5 or NONE. It is advised to use either HMAC-MD5
6349 See configuration for Cryptographic API and enable these algorithms
6350 to make usable by SCTP.
6352 SCTP: SHA1 HMAC algorithm
6353 CONFIG_SCTP_HMAC_SHA1
6354 Enable the use of HMAC-SHA1 during association establishment. It
6355 is advised to use either HMAC-MD5 or HMAC-SHA1.
6356 See configuration for Cryptographic API and enable these algorithms
6357 to make usable by SCTP.
6359 SCTP: MD5 HMAC algorithm
6360 config SCTP_HMAC_MD5
6361 Enable the use of HMAC-MD5 during association establishment. It is
6362 advised to use either HMAC-MD5 or HMAC-SHA1.
6363 See configuration for Cryptographic API and enable these algorithms
6364 to make usable by SCTP.
6366 Kernel httpd acceleration
6368 The kernel httpd acceleration daemon (kHTTPd) is a (limited) web
6369 server built into the kernel. It is limited since it can only serve
6370 files from the file system and cannot deal with executable content
6371 such as CGI scripts. Serving files is sped up if you use kHTTPd.
6372 If kHTTPd is not able to fulfill a request, it can transparently
6373 pass it through to a user space web server such as apache.
6375 Saying "M" here builds the kHTTPd module; this is NOT enough to have
6376 a working kHTTPd. For safety reasons, the module has to be activated
6377 by doing a "echo 1 > /proc/sys/net/khttpd/start" after inserting the
6380 Before using this, read the README in net/khttpd !
6382 The kHTTPd is experimental. Be careful when using it on a production
6383 machine. Also note that kHTTPd doesn't support virtual servers yet.
6387 This is support for the Novell networking protocol, IPX, commonly
6388 used for local networks of Windows machines. You need it if you
6389 want to access Novell NetWare file or print servers using the Linux
6390 Novell client ncpfs (available from
6391 <ftp://platan.vc.cvut.cz/pub/linux/ncpfs/>) or from
6392 within the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO,
6393 available from <http://www.tldp.org/docs.html#howto>). In order
6394 to do the former, you'll also have to say Y to "NCP file system
6397 IPX is similar in scope to IP, while SPX, which runs on top of IPX,
6398 is similar to TCP. There is also experimental support for SPX in
6399 Linux (see "SPX networking", below).
6401 To turn your Linux box into a fully featured NetWare file server and
6402 IPX router, say Y here and fetch either lwared from
6403 <ftp://ibiblio.org/pub/Linux/system/network/daemons/> or
6404 mars_nwe from <ftp://www.compu-art.de/mars_nwe/>. For more
6405 information, read the IPX-HOWTO available from
6406 <http://www.tldp.org/docs.html#howto>.
6408 General information about how to connect Linux, Windows machines and
6409 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
6411 The IPX driver would enlarge your kernel by about 16 KB. This driver
6412 is also available as a module ( = code which can be inserted in and
6413 removed from the running kernel whenever you want). The module will
6414 be called ipx.o. If you want to compile it as a module, say M here
6415 and read <file:Documentation/modules.txt>. Unless you want to
6416 integrate your Linux box with a local Novell network, say N.
6418 Full internal IPX network
6420 Every IPX network has an address that identifies it. Sometimes it is
6421 useful to give an IPX "network" address to your Linux box as well
6422 (for example if your box is acting as a file server for different
6423 IPX networks: it will then be accessible from everywhere using the
6424 same address). The way this is done is to create a virtual internal
6425 "network" inside your box and to assign an IPX address to this
6426 network. Say Y here if you want to do this; read the IPX-HOWTO at
6427 <http://www.tldp.org/docs.html#howto> for details.
6429 The full internal IPX network enables you to allocate sockets on
6430 different virtual nodes of the internal network. This is done by
6431 evaluating the field sipx_node of the socket address given to the
6432 bind call. So applications should always initialize the node field
6433 to 0 when binding a socket on the primary network. In this case the
6434 socket is assigned the default node that has been given to the
6435 kernel when the internal network was created. By enabling the full
6436 internal IPX network the cross-forwarding of packets targeted at
6437 'special' sockets to sockets listening on the primary network is
6438 disabled. This might break existing applications, especially RIP/SAP
6439 daemons. A RIP/SAP daemon that works well with the full internal net
6440 can be found on <ftp://ftp.gwdg.de/pub/linux/misc/ncpfs/>.
6442 If you don't know what you are doing, say N.
6444 #(We're told this will come back someday)
6448 * Orphaned entry retained 20 April 2001 by Petr Vandrovec *
6449 * If you read this note from the configurator, please contact *
6450 * the Configure.help maintainers. *
6451 The Sequenced Packet eXchange protocol is a transport layer protocol
6452 built on top of IPX. It is used in Novell NetWare systems for
6453 client-server applications and is similar to TCP (which runs on top
6456 Note that Novell NetWare file sharing does not use SPX; it uses a
6457 protocol called NCP, for which separate Linux support is available
6458 ("NCP file system support" below for the client side, and the user
6459 space programs lwared or mars_nwe for the server side).
6461 Say Y here if you have use for SPX; read the IPX-HOWTO at
6462 <http://www.tldp.org/docs.html#howto> for details.
6464 This driver is also available as a module ( = code which can be
6465 inserted in and removed from the running kernel whenever you want).
6466 The module will be called af_spx.o. If you want to compile it as a
6467 module, say M here and read <file:Documentation/modules.txt>.
6471 The DECnet networking protocol was used in many products made by
6472 Digital (now Compaq). It provides reliable stream and sequenced
6473 packet communications over which run a variety of services similar
6474 to those which run over TCP/IP.
6476 To find some tools to use with the kernel layer support, please
6477 look at Patrick Caulfield's web site:
6478 <http://linux.dreamtime.org/decnet/>.
6480 More detailed documentation is available in
6481 <file:Documentation/networking/decnet.txt>.
6483 Be sure to say Y to "/proc file system support" and "Sysctl support"
6484 below when using DECnet, since you will need sysctl support to aid
6485 in configuration at run time.
6487 The DECnet code is also available as a module ( = code which can be
6488 inserted in and removed from the running kernel whenever you want).
6489 The module is called decnet.o.
6491 DECnet SIOCFIGCONF support
6492 CONFIG_DECNET_SIOCGIFCONF
6493 This option should only be turned on if you are really sure that
6494 you know what you are doing. It can break other applications which
6495 use this system call and the proper way to get the information
6496 provided by this call is to use rtnetlink.
6500 DECnet router support
6501 CONFIG_DECNET_ROUTER
6502 Add support for turning your DECnet Endnode into a level 1 or 2
6503 router. This is an unfinished option for developers only. If you
6504 do say Y here, then make sure that you also say Y to "Kernel/User
6505 network link driver", "Routing messages" and "Network packet
6506 filtering". The first two are required to allow configuration via
6507 rtnetlink (currently you need Alexey Kuznetsov's iproute2 package
6508 from <ftp://ftp.inr.ac.ru/>). The "Network packet filtering" option
6509 will be required for the forthcoming routing daemon to work.
6511 See <file:Documentation/networking/decnet.txt> for more information.
6513 Use FWMARK value as DECnet routing key
6514 CONFIG_DECNET_ROUTE_FWMARK
6515 If you say Y here, you will be able to specify different routes for
6516 packets with different FWMARK ("firewalling mark") values
6517 (see ipchains(8), "-m" argument).
6519 AppleTalk interfaces support
6520 CONFIG_DEV_APPLETALK
6521 AppleTalk is the protocol that Apple computers can use to communicate
6522 on a network. If your Linux box is connected to such a network, and wish
6523 to do IP over it, or you have a LocalTalk card and wish to use it to
6524 connect to the AppleTalk network, say Y.
6526 AppleTalk protocol support
6528 AppleTalk is the protocol that Apple computers can use to communicate
6529 on a network. If your Linux box is connected to such a network and you
6530 wish to connect to it, say Y. You will need to use the netatalk package
6531 so that your Linux box can act as a print and file server for Macs as
6532 well as access AppleTalk printers. Check out
6533 <http://www.zettabyte.net/netatalk/> on the WWW for details.
6534 EtherTalk is the name used for AppleTalk over Ethernet and the
6535 cheaper and slower LocalTalk is AppleTalk over a proprietary Apple
6536 network using serial links. EtherTalk and LocalTalk are fully
6539 General information about how to connect Linux, Windows machines and
6540 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>. The
6541 NET-3-HOWTO, available from
6542 <http://www.tldp.org/docs.html#howto>, contains valuable
6543 information as well.
6545 This driver is also available as a module ( = code which can be
6546 inserted in and removed from the running kernel whenever you want).
6547 The module is called appletalk.o. If you want to compile it as a
6548 module, say M here and read <file:Documentation/modules.txt>. You
6549 almost certainly want to compile it as a module so you can restart
6550 your AppleTalk stack without rebooting your machine. I hear that
6551 the GNU boycott of Apple is over, so even politically correct people
6552 are allowed to say Y here.
6554 AppleTalk-IP driver support
6556 This allows IP networking for users who only have AppleTalk
6557 networking available. This feature is experimental. With this
6558 driver, you can encapsulate IP inside AppleTalk (e.g. if your Linux
6559 box is stuck on an AppleTalk only network) or decapsulate (e.g. if
6560 you want your Linux box to act as an Internet gateway for a zoo of
6561 AppleTalk connected Macs). Please see the file
6562 <file:Documentation/networking/ipddp.txt> for more information.
6564 If you say Y here, the AppleTalk-IP support will be compiled into
6565 the kernel. In this case, you can either use encapsulation or
6566 decapsulation, but not both. With the following two questions, you
6567 decide which one you want.
6569 If you say M here, the AppleTalk-IP support will be compiled as a
6570 module ( = code which can be inserted in and removed from the
6571 running kernel whenever you want, read
6572 <file:Documentation/modules.txt>). The module is called ipddp.o.
6573 In this case, you will be able to use both encapsulation and
6574 decapsulation simultaneously, by loading two copies of the module
6575 and specifying different values for the module option ipddp_mode.
6577 IP to AppleTalk-IP Encapsulation support
6579 If you say Y here, the AppleTalk-IP code will be able to encapsulate
6580 IP packets inside AppleTalk frames; this is useful if your Linux box
6581 is stuck on an AppleTalk network (which hopefully contains a
6582 decapsulator somewhere). Please see
6583 <file:Documentation/networking/ipddp.txt> for more information. If
6584 you said Y to "AppleTalk-IP driver support" above and you say Y
6585 here, then you cannot say Y to "AppleTalk-IP to IP Decapsulation
6588 AppleTalk-IP to IP Decapsulation support
6590 If you say Y here, the AppleTalk-IP code will be able to decapsulate
6591 AppleTalk-IP frames to IP packets; this is useful if you want your
6592 Linux box to act as an Internet gateway for an AppleTalk network.
6593 Please see <file:Documentation/networking/ipddp.txt> for more
6594 information. If you said Y to "AppleTalk-IP driver support" above
6595 and you say Y here, then you cannot say Y to "IP to AppleTalk-IP
6596 Encapsulation support", above.
6598 Apple/Farallon LocalTalk PC card support
6600 This allows you to use the AppleTalk PC card to connect to LocalTalk
6601 networks. The card is also known as the Farallon PhoneNet PC card.
6602 If you are in doubt, this card is the one with the 65C02 chip on it.
6603 You also need version 1.3.3 or later of the netatalk package.
6604 This driver is experimental, which means that it may not work.
6605 See the file <file:Documentation/networking/ltpc.txt>.
6607 This driver is also available as a module ( = code which can be
6608 inserted in and removed from the running kernel whenever you want).
6609 If you want to compile it as a module, say M here and read
6610 <file:Documentation/modules.txt>. The module will be called
6613 COPS LocalTalk PC card support
6615 This allows you to use COPS AppleTalk cards to connect to LocalTalk
6616 networks. You also need version 1.3.3 or later of the netatalk
6617 package. This driver is experimental, which means that it may not
6618 work. This driver will only work if you choose "AppleTalk DDP"
6619 networking support, above.
6620 Please read the file <file:Documentation/networking/cops.txt>.
6622 This driver is also available as a module ( = code which can be
6623 inserted in and removed from the running kernel whenever you want).
6624 If you want to compile it as a module, say M here and read
6625 <file:Documentation/modules.txt>. The module will be called
6628 Dayna firmware support
6630 Support COPS compatible cards with Dayna style firmware (Dayna
6631 DL2000/ Daynatalk/PC (half length), COPS LT-95, Farallon PhoneNET PC
6632 III, Farallon PhoneNET PC II).
6634 Tangent firmware support
6636 Support COPS compatible cards with Tangent style firmware (Tangent
6637 ATB_II, Novell NL-1000, Daystar Digital LT-200.
6639 Amateur Radio support
6641 If you want to connect your Linux box to an amateur radio, answer Y
6642 here. You want to read <http://www.tapr.org/tapr/html/pkthome.html> and
6643 the AX25-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
6645 Note that the answer to this question won't directly affect the
6646 kernel: saying N will just cause the configurator to skip all
6647 the questions about amateur radio.
6649 Amateur Radio AX.25 Level 2 protocol
6651 This is the protocol used for computer communication over amateur
6652 radio. It is either used by itself for point-to-point links, or to
6653 carry other protocols such as tcp/ip. To use it, you need a device
6654 that connects your Linux box to your amateur radio. You can either
6655 use a low speed TNC (a Terminal Node Controller acts as a kind of
6656 modem connecting your computer's serial port to your radio's
6657 microphone input and speaker output) supporting the KISS protocol or
6658 one of the various SCC cards that are supported by the generic Z8530
6659 or the DMA SCC driver. Another option are the Baycom modem serial
6660 and parallel port hacks or the sound card modem (supported by their
6661 own drivers). If you say Y here, you also have to say Y to one of
6664 Information about where to get supporting software for Linux amateur
6665 radio as well as information about how to configure an AX.25 port is
6666 contained in the AX25-HOWTO, available from
6667 <http://www.tldp.org/docs.html#howto>. You might also want to
6668 check out the file <file:Documentation/networking/ax25.txt> in the
6669 kernel source. More information about digital amateur radio in
6670 general is on the WWW at
6671 <http://www.tapr.org/tapr/html/pkthome.html>.
6673 This driver is also available as a module ( = code which can be
6674 inserted in and removed from the running kernel whenever you want).
6675 The module will be called ax25.o. If you want to compile it as a
6676 module, say M here and read <file:Documentation/modules.txt>.
6678 AX.25 DAMA Slave support
6679 CONFIG_AX25_DAMA_SLAVE
6680 DAMA is a mechanism to prevent collisions when doing AX.25
6681 networking. A DAMA server (called "master") accepts incoming traffic
6682 from clients (called "slaves") and redistributes it to other slaves.
6683 If you say Y here, your Linux box will act as a DAMA slave; this is
6684 transparent in that you don't have to do any special DAMA
6685 configuration. (Linux cannot yet act as a DAMA server.) If unsure,
6688 AX.25 DAMA Master support
6689 CONFIG_AX25_DAMA_MASTER
6690 DAMA is a mechanism to prevent collisions when doing AX.25
6691 networking. A DAMA server (called "master") accepts incoming traffic
6692 from clients (called "slaves") and redistributes it to other
6693 slaves. If you say Y here, your Linux box will act as a DAMA server.
6696 Amateur Radio NET/ROM support
6698 NET/ROM is a network layer protocol on top of AX.25 useful for
6701 A comprehensive listing of all the software for Linux amateur radio
6702 users as well as information about how to configure an AX.25 port is
6703 contained in the AX25-HOWTO, available from
6704 <http://www.tldp.org/docs.html#howto>. You also might want to
6705 check out the file <file:Documentation/networking/ax25.txt>. More
6706 information about digital amateur radio in general is on the WWW at
6707 <http://www.tapr.org/tapr/html/pkthome.html>.
6709 This driver is also available as a module ( = code which can be
6710 inserted in and removed from the running kernel whenever you want).
6711 The module will be called netrom.o. If you want to compile it as a
6712 module, say M here and read <file:Documentation/modules.txt>.
6714 Amateur Radio X.25 PLP (Rose)
6716 The Packet Layer Protocol (PLP) is a way to route packets over X.25
6717 connections in general and amateur radio AX.25 connections in
6718 particular, essentially an alternative to NET/ROM.
6720 A comprehensive listing of all the software for Linux amateur radio
6721 users as well as information about how to configure an AX.25 port is
6722 contained in the AX25-HOWTO, available from
6723 <http://www.tldp.org/docs.html#howto>. You also might want to
6724 check out the file <file:Documentation/networking/ax25.txt>. More
6725 information about digital amateur radio in general is on the WWW at
6726 <http://www.tapr.org/tapr/html/pkthome.html>.
6728 This driver is also available as a module ( = code which can be
6729 inserted in and removed from the running kernel whenever you want).
6730 The module will be called rose.o. If you want to compile it as a
6731 module, say M here and read <file:Documentation/modules.txt>.
6733 Serial port KISS driver for AX.25
6735 KISS is a protocol used for the exchange of data between a computer
6736 and a Terminal Node Controller (a small embedded system commonly
6737 used for networking over AX.25 amateur radio connections; it
6738 connects the computer's serial port with the radio's microphone
6739 input and speaker output).
6741 Although KISS is less advanced than the 6pack protocol, it has
6742 the advantage that it is already supported by most modern TNCs
6743 without the need for a firmware upgrade.
6745 If you want to compile this driver as a module ( = code which can be
6746 inserted in and removed from the running kernel whenever you want),
6747 say M here and read <file:Documentation/modules.txt>. The module
6748 will be called mkiss.o.
6750 Serial port 6PACK driver for AX.25
6752 6pack is a transmission protocol for the data exchange between your
6753 PC and your TNC (the Terminal Node Controller acts as a kind of
6754 modem connecting your computer's serial port to your radio's
6755 microphone input and speaker output). This protocol can be used as
6756 an alternative to KISS for networking over AX.25 amateur radio
6757 connections, but it has some extended functionality.
6759 Note that this driver is still experimental and might cause
6760 problems. For details about the features and the usage of the
6761 driver, read <file:Documentation/networking/6pack.txt>.
6763 If you want to compile this driver as a module ( = code which can be
6764 inserted in and removed from the running kernel whenever you want),
6765 say M here and read <file:Documentation/modules.txt>. The module
6766 will be called 6pack.o.
6770 AX.25 is the protocol used for computer communication over amateur
6771 radio. If you say Y here, you will be able to send and receive AX.25
6772 traffic over Ethernet (also called "BPQ AX.25"), which could be
6773 useful if some other computer on your local network has a direct
6774 amateur radio connection.
6776 If you want to compile the driver as a module ( = code which can be
6777 inserted in and removed from the running kernel whenever you want),
6778 say M here and read <file:Documentation/modules.txt>. The module
6779 will be called bpqether.o.
6781 High-speed (DMA) SCC driver for AX.25
6783 This is a driver for high-speed SCC boards, i.e. those supporting
6784 DMA on one port. You usually use those boards to connect your
6785 computer to an amateur radio modem (such as the WA4DSY 56kbps
6786 modem), in order to send and receive AX.25 packet radio network
6789 Currently, this driver supports Ottawa PI/PI2, Paccomm/Gracilis
6790 PackeTwin, and S5SCC/DMA boards. They are detected automatically.
6791 If you have one of these cards, say Y here and read the AX25-HOWTO,
6792 available from <http://www.tldp.org/docs.html#howto>.
6794 This driver can operate multiple boards simultaneously. If you
6795 compile it as a module (by saying M instead of Y), it will be called
6796 dmascc.o. If you don't pass any parameter to the driver, all
6797 possible I/O addresses are probed. This could irritate other devices
6798 that are currently not in use. You may specify the list of addresses
6799 to be probed by "dmascc=addr1,addr2,..." (when compiled into the
6800 kernel image) or "io=addr1,addr2,..." (when loaded as a module). The
6801 network interfaces will be called dmascc0 and dmascc1 for the board
6802 detected first, dmascc2 and dmascc3 for the second one, and so on.
6804 Before you configure each interface with ifconfig, you MUST set
6805 certain parameters, such as channel access timing, clock mode, and
6806 DMA channel. This is accomplished with a small utility program,
6807 dmascc_cfg, available at
6808 <http://www.nt.tuwien.ac.at/~kkudielk/Linux/>. Please be sure to get
6809 at least version 1.27 of dmascc_cfg, as older versions will not
6810 work with the current driver.
6812 Z8530 SCC driver for AX.25
6814 These cards are used to connect your Linux box to an amateur radio
6815 in order to communicate with other computers. If you want to use
6816 this, read <file:Documentation/networking/z8530drv.txt> and the
6817 AX25-HOWTO, available from
6818 <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
6819 to "Amateur Radio AX.25 Level 2" support.
6821 If you want to compile this as a module ( = code which can be
6822 inserted in and removed from the running kernel whenever you want),
6823 say M here and read <file:Documentation/modules.txt>. The module
6824 will be called scc.o.
6826 Support for TRX that feedback the tx signal to rx
6828 Some transmitters feed the transmitted signal back to the receive
6829 line. Say Y here to foil this by explicitly disabling the receiver
6830 during data transmission. If in doubt, say Y.
6832 Additional delay for PA0HZP OptoSCC compatible boards
6834 Say Y here if you experience problems with the SCC driver not
6835 working properly; please read
6836 <file:Documentation/networking/z8530drv.txt> for details. If unsure,
6839 YAM driver for AX.25
6841 The YAM is a modem for packet radio which connects to the serial
6842 port and includes some of the functions of a Terminal Node
6843 Controller. If you have one of those, say Y here.
6845 If you want to compile the driver as a module ( = code which can be
6846 inserted in and removed from the running kernel whenever you want),
6847 say M here and read <file:Documentation/modules.txt>. The module
6848 will be called yam.o.
6850 BAYCOM picpar and par96 driver for AX.25
6852 This is a driver for Baycom style simple amateur radio modems that
6853 connect to a parallel interface. The driver supports the picpar and
6854 par96 designs. To configure the driver, use the sethdlc utility
6855 available in the standard ax25 utilities package. For information on
6856 the modems, see <http://www.baycom.de/> and the file
6857 <file:Documentation/networking/baycom.txt>.
6859 If you want to compile this driver as a module ( = code which can be
6860 inserted in and removed from the running kernel whenever you want),
6861 say M here and read <file:Documentation/modules.txt>. This is
6862 recommended. The module will be called baycom_par.o.
6864 BAYCOM EPP driver for AX.25
6866 This is a driver for Baycom style simple amateur radio modems that
6867 connect to a parallel interface. The driver supports the EPP
6868 designs. To configure the driver, use the sethdlc utility available
6869 in the standard ax25 utilities package. For information on the
6870 modems, see <http://www.baycom.de/> and the file
6871 <file:Documentation/networking/baycom.txt>.
6873 If you want to compile this driver as a module ( = code which can be
6874 inserted in and removed from the running kernel whenever you want),
6875 say M here and read <file:Documentation/modules.txt>. This is
6876 recommended. The module will be called baycom_par.o.
6878 BAYCOM ser12 full-duplex driver for AX.25
6879 CONFIG_BAYCOM_SER_FDX
6880 This is one of two drivers for Baycom style simple amateur radio
6881 modems that connect to a serial interface. The driver supports the
6882 ser12 design in full-duplex mode. In addition, it allows the
6883 baudrate to be set between 300 and 4800 baud (however not all modems
6884 support all baudrates). This is the preferred driver. The next
6885 driver, "BAYCOM ser12 half-duplex driver for AX.25" is the old
6886 driver and still provided in case this driver does not work with
6887 your serial interface chip. To configure the driver, use the sethdlc
6888 utility available in the standard ax25 utilities package. For
6889 information on the modems, see <http://www.baycom.de/> and
6890 <file:Documentation/networking/baycom.txt>.
6892 If you want to compile this driver as a module ( = code which can be
6893 inserted in and removed from the running kernel whenever you want),
6894 say M here and read <file:Documentation/modules.txt>. This is
6895 recommended. The module will be called baycom_ser_fdx.o.
6897 BAYCOM ser12 half-duplex driver for AX.25
6898 CONFIG_BAYCOM_SER_HDX
6899 This is one of two drivers for Baycom style simple amateur radio
6900 modems that connect to a serial interface. The driver supports the
6901 ser12 design in full-duplex mode. This is the old driver. It is
6902 still provided in case your serial interface chip does not work with
6903 the full-duplex driver. This driver is depreciated. To configure
6904 the driver, use the sethdlc utility available in the standard ax25
6905 utilities package. For information on the modems, see
6906 <http://www.baycom.de/> and
6907 <file:Documentation/networking/baycom.txt>.
6909 If you want to compile this driver as a module ( = code which can be
6910 inserted in and removed from the running kernel whenever you want),
6911 say M here and read <file:Documentation/modules.txt>. This is
6912 recommended. The module will be called baycom_ser_hdx.o.
6914 Sound card modem driver for AX.25
6916 This experimental driver allows a standard Sound Blaster or
6917 WindowsSoundSystem compatible sound card to be used as a packet
6918 radio modem (NOT as a telephone modem!), to send digital traffic
6921 To configure the driver, use the sethdlc, smdiag and smmixer
6922 utilities available in the standard ax25 utilities package. For
6923 information on how to key the transmitter, see
6924 <http://www.ife.ee.ethz.ch/~sailer/pcf/ptt_circ/ptt.html> and
6925 <file:Documentation/networking/soundmodem.txt>.
6927 If you want to compile this driver as a module ( = code which can be
6928 inserted in and removed from the running kernel whenever you want),
6929 say M here and read <file:Documentation/modules.txt>. This is
6930 recommended. The module will be called soundmodem.o.
6932 Sound card modem support for Sound Blaster and compatible cards
6933 CONFIG_SOUNDMODEM_SBC
6934 This option enables the soundmodem driver to use Sound Blaster and
6935 compatible cards. If you have a dual mode card (i.e. a WSS cards
6936 with a Sound Blaster emulation) you should say N here and Y to
6937 "Sound card modem support for WSS and Crystal cards", below, because
6938 this usually results in better performance. This option also
6939 supports SB16/32/64 in full-duplex mode.
6941 Sound card modem support for WSS and Crystal cards
6942 CONFIG_SOUNDMODEM_WSS
6943 This option enables the soundmodem driver to use WindowsSoundSystem
6944 compatible cards. These cards feature a codec chip from either
6945 Analog Devices (such as AD1848, AD1845, AD1812) or Crystal
6946 Semiconductors (such as CS4248, CS423x). This option also supports
6947 the WSS full-duplex operation which currently works with Crystal
6948 CS423x chips. If you don't need full-duplex operation, do not enable
6949 it to save performance.
6951 Sound card modem support for 1200 baud AFSK modulation
6952 CONFIG_SOUNDMODEM_AFSK1200
6953 This option enables the soundmodem driver 1200 baud AFSK modem,
6954 compatible to popular modems using TCM3105 or AM7911. The
6955 demodulator requires about 12% of the CPU power of a Pentium 75 CPU
6958 Sound card modem support for 2400 baud AFSK modulation (7.3728MHz crystal)
6959 CONFIG_SOUNDMODEM_AFSK2400_7
6960 This option enables the soundmodem driver 2400 baud AFSK modem,
6961 compatible to TCM3105 modems (over-)clocked with a 7.3728MHz
6962 crystal. Note that the availability of this driver does _not_ imply
6963 that I recommend building such links. It is only here since users
6964 especially in eastern Europe have asked me to do so. In fact this
6965 modulation scheme has many disadvantages, mainly its incompatibility
6966 with many transceiver designs and the fact that the TCM3105 (if
6967 used) is operated widely outside its specifications.
6969 Sound card modem support for 2400 baud AFSK modulation (8MHz crystal)
6970 CONFIG_SOUNDMODEM_AFSK2400_8
6971 This option enables the soundmodem driver 2400 baud AFSK modem,
6972 compatible to TCM3105 modems (over-)clocked with an 8MHz crystal.
6973 Note that the availability of this driver does _not_ imply that I
6974 recommend building such links. It is only here since users
6975 especially in eastern Europe have asked me to do so. In fact this
6976 modulation scheme has many disadvantages, mainly its incompatibility
6977 with many transceiver designs and the fact that the TCM3105 (if
6978 used) is operated widely outside its specifications.
6980 Sound card modem support for 2666 baud AFSK modulation
6981 CONFIG_SOUNDMODEM_AFSK2666
6982 This option enables the soundmodem driver 2666 baud AFSK modem.
6983 This modem is experimental, and not compatible to anything
6986 Sound card modem support for 4800 baud 8PSK modulation
6987 CONFIG_SOUNDMODEM_PSK4800
6988 This option enables the soundmodem driver 4800 baud 8PSK modem.
6989 This modem is experimental, and not compatible to anything
6992 Sound card modem support for 4800 baud HAPN-1 modulation
6993 CONFIG_SOUNDMODEM_HAPN4800
6994 This option enables the soundmodem driver 4800 baud HAPN-1
6995 compatible modem. This modulation seems to be widely used 'down
6996 under' and in the Netherlands. Here, nobody uses it, so I could not
6997 test if it works. It is compatible to itself, however :-)
6999 Sound card modem support for 9600 baud FSK G3RUH modulation
7000 CONFIG_SOUNDMODEM_FSK9600
7001 This option enables the soundmodem driver 9600 baud FSK modem,
7002 compatible to the G3RUH standard. The demodulator requires about 4%
7003 of the CPU power of a Pentium 75 CPU per channel. You can say Y to
7004 both 1200 baud AFSK and 9600 baud FSK if you want (but obviously you
7005 can only use one protocol at a time, depending on what the other end
7008 CCITT X.25 Packet Layer
7010 X.25 is a set of standardized network protocols, similar in scope to
7011 frame relay; the one physical line from your box to the X.25 network
7012 entry point can carry several logical point-to-point connections
7013 (called "virtual circuits") to other computers connected to the X.25
7014 network. Governments, banks, and other organizations tend to use it
7015 to connect to each other or to form Wide Area Networks (WANs). Many
7016 countries have public X.25 networks. X.25 consists of two
7017 protocols: the higher level Packet Layer Protocol (PLP) (say Y here
7018 if you want that) and the lower level data link layer protocol LAPB
7019 (say Y to "LAPB Data Link Driver" below if you want that).
7021 You can read more about X.25 at <http://www.sangoma.com/x25.htm> and
7022 <http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/cx25.htm>.
7023 Information about X.25 for Linux is contained in the files
7024 <file:Documentation/networking/x25.txt> and
7025 <file:Documentation/networking/x25-iface.txt>.
7027 One connects to an X.25 network either with a dedicated network card
7028 using the X.21 protocol (not yet supported by Linux) or one can do
7029 X.25 over a standard telephone line using an ordinary modem (say Y
7030 to "X.25 async driver" below) or over Ethernet using an ordinary
7031 Ethernet card and either the 802.2 LLC protocol (say Y to "802.2
7032 LLC" below) or LAPB over Ethernet (say Y to "LAPB Data Link Driver"
7033 and "LAPB over Ethernet driver" below).
7035 If you want to compile this driver as a module ( = code which can be
7036 inserted in and removed from the running kernel whenever you want),
7037 say M here and read <file:Documentation/modules.txt>. The module
7038 will be called x25.o. If unsure, say N.
7040 LAPB Data Link Driver
7042 Link Access Procedure, Balanced (LAPB) is the data link layer (i.e.
7043 the lower) part of the X.25 protocol. It offers a reliable
7044 connection service to exchange data frames with one other host, and
7045 it is used to transport higher level protocols (mostly X.25 Packet
7046 Layer, the higher part of X.25, but others are possible as well).
7047 Usually, LAPB is used with specialized X.21 network cards, but Linux
7048 currently supports LAPB only over Ethernet connections. If you want
7049 to use LAPB connections over Ethernet, say Y here and to "LAPB over
7050 Ethernet driver" below. Read
7051 <file:Documentation/networking/lapb-module.txt> for technical
7054 If you want to compile this driver as a module though ( = code which
7055 can be inserted in and removed from the running kernel whenever you
7056 want), say M here and read <file:Documentation/modules.txt>. The
7057 module will be called lapb.o. If unsure, say N.
7061 This is a Logical Link Layer protocol used for X.25 connections over
7062 Ethernet, using ordinary Ethernet cards.
7066 The Frame Diverter allows you to divert packets from the
7067 network, that are not aimed at the interface receiving it (in
7068 promisc. mode). Typically, a Linux box setup as an Ethernet bridge
7069 with the Frames Diverter on, can do some *really* transparent www
7070 caching using a Squid proxy for example.
7072 This is very useful when you don't want to change your router's
7073 config (or if you simply don't have access to it).
7075 The other possible usages of diverting Ethernet Frames are
7077 - reroute smtp traffic to another interface
7078 - traffic-shape certain network streams
7079 - transparently proxy smtp connections
7082 For more informations, please refer to:
7083 <http://diverter.sourceforge.net/>
7084 <http://perso.wanadoo.fr/magpie/EtherDivert.html>
7088 802.1d Ethernet Bridging
7090 If you say Y here, then your Linux box will be able to act as an
7091 Ethernet bridge, which means that the different Ethernet segments it
7092 is connected to will appear as one Ethernet to the participants.
7093 Several such bridges can work together to create even larger
7094 networks of Ethernets using the IEEE 802.1 spanning tree algorithm.
7095 As this is a standard, Linux bridges will cooperate properly with
7096 other third party bridge products.
7098 In order to use the Ethernet bridge, you'll need the bridge
7099 configuration tools; see <file:Documentation/networking/bridge.txt>
7100 for location. Please read the Bridge mini-HOWTO for more
7103 Note that if your box acts as a bridge, it probably contains several
7104 Ethernet devices, but the kernel is not able to recognize more than
7105 one at boot time without help; for details read the Ethernet-HOWTO,
7106 available from in <http://www.tldp.org/docs.html#howto>.
7108 If you want to compile this code as a module ( = code which can be
7109 inserted in and removed from the running kernel whenever you want),
7110 say M here and read <file:Documentation/modules.txt>. The module
7111 will be called bridge.o.
7117 The Packet protocol is used by applications which communicate
7118 directly with network devices without an intermediate network
7119 protocol implemented in the kernel, e.g. tcpdump. If you want them
7122 This driver is also available as a module called af_packet.o ( =
7123 code which can be inserted in and removed from the running kernel
7124 whenever you want). If you want to compile it as a module, say M
7125 here and read <file:Documentation/modules.txt>; if you use modprobe
7126 or kmod, you may also want to add "alias net-pf-17 af_packet" to
7131 Packet socket: mmapped IO
7133 If you say Y here, the Packet protocol driver can use a faster and
7134 more efficient capture method. This feature also allows bigger
7135 receive buffers. To take advantage of this method who have to use
7136 a libpcap library that supports it. For more info see
7137 <file:Documentation/networking/packet_mmap.txt>.
7141 Netlink device emulation
7143 This option will be removed soon. Any programs that want to use
7144 character special nodes like /dev/tap0 or /dev/route (all with major
7145 number 36) need this option, and need to be rewritten soon to use
7146 the real netlink socket.
7147 This is a backward compatibility option, choose Y for now.
7149 This driver is also available as a module ( = code which can be
7150 inserted in and removed from the running kernel whenever you want).
7151 If you want to compile it as a module, say M here and read
7152 <file:Documentation/modules.txt>. The module will be called
7155 Asynchronous Transfer Mode (ATM)
7157 ATM is a high-speed networking technology for Local Area Networks
7158 and Wide Area Networks. It uses a fixed packet size and is
7159 connection oriented, allowing for the negotiation of minimum
7160 bandwidth requirements.
7162 In order to participate in an ATM network, your Linux box needs an
7163 ATM networking card. If you have that, say Y here and to the driver
7164 of your ATM card below.
7166 Note that you need a set of user-space programs to actually make use
7167 of ATM. See the file <file:Documentation/networking/atm.txt> for
7170 Classical IP over ATM
7172 Classical IP over ATM for PVCs and SVCs, supporting InARP and
7173 ATMARP. If you want to communication with other IP hosts on your ATM
7174 network, you will typically either say Y here or to "LAN Emulation
7177 Do NOT send ICMP if no neighbour
7178 CONFIG_ATM_CLIP_NO_ICMP
7179 Normally, an "ICMP host unreachable" message is sent if a neighbour
7180 cannot be reached because there is no VC to it in the kernel's
7181 ATMARP table. This may cause problems when ATMARP table entries are
7182 briefly removed during revalidation. If you say Y here, packets to
7183 such neighbours are silently discarded instead.
7185 RFC1483/2684 Bridged protocols
7187 ATM PVCs can carry ethernet PDUs according to rfc2684 (formerly 1483)
7188 This device will act like an ethernet from the kernels point of view,
7189 with the traffic being carried by ATM PVCs (currently 1 PVC/device).
7190 This is sometimes used over DSL lines. If in doubt, say N.
7192 Per-VC IP filter kludge
7193 CONFIG_ATM_BR2684_IPFILTER
7194 This is an experimental mechanism for users who need to terminating a
7195 large number of IP-only vcc's. Do not enable this unless you are sure
7196 you know what you are doing.
7198 LAN Emulation (LANE) support
7200 LAN Emulation emulates services of existing LANs across an ATM
7201 network. Besides operating as a normal ATM end station client, Linux
7202 LANE client can also act as an proxy client bridging packets between
7203 ELAN and Ethernet segments. You need LANE if you want to try MPOA.
7205 Multi-Protocol Over ATM (MPOA) support
7207 Multi-Protocol Over ATM allows ATM edge devices such as routers,
7208 bridges and ATM attached hosts establish direct ATM VCs across
7209 subnetwork boundaries. These shortcut connections bypass routers
7210 enhancing overall network performance.
7214 ATM over TCP driver. Useful mainly for development and for
7215 experiments. If unsure, say N.
7217 Efficient Networks ENI155P
7219 Driver for the Efficient Networks ENI155p series and SMC ATM
7220 Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
7221 2MB on-board RAM (Efficient calls them "C" and "S", respectively),
7222 and the FPGA and the ASIC Tonga versions of the board are supported.
7223 The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
7226 This driver is also available as a module. If you want to compile
7227 it as a module, say M here and read
7228 <file:Documentation/modules.txt>. The module will be called eni.o.
7230 Enable extended debugging
7231 CONFIG_ATM_ENI_DEBUG
7232 Extended debugging records various events and displays that list
7233 when an inconsistency is detected. This mechanism is faster than
7234 generally using printks, but still has some impact on performance.
7235 Note that extended debugging may create certain race conditions
7236 itself. Enable this ONLY if you suspect problems with the driver.
7238 Fine-tune burst settings
7239 CONFIG_ATM_ENI_TUNE_BURST
7240 In order to obtain good throughput, the ENI NIC can transfer
7241 multiple words of data per PCI bus access cycle. Such a multi-word
7242 transfer is called a burst.
7244 The default settings for the burst sizes are suitable for most PCI
7245 chipsets. However, in some cases, large bursts may overrun buffers
7246 in the PCI chipset and cause data corruption. In such cases, large
7247 bursts must be disabled and only (slower) small bursts can be used.
7248 The burst sizes can be set independently in the send (TX) and
7249 receive (RX) direction.
7251 Note that enabling many different burst sizes in the same direction
7252 may increase the cost of setting up a transfer such that the
7253 resulting throughput is lower than when using only the largest
7254 available burst size.
7256 Also, sometimes larger bursts lead to lower throughput, e.g. on an
7257 Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
7258 when going from 8W to 16W bursts.
7260 Enable 16W TX bursts (discouraged)
7261 CONFIG_ATM_ENI_BURST_TX_16W
7262 Burst sixteen words at once in the send direction. This may work
7263 with recent PCI chipsets, but is known to fail with older chipsets.
7265 Enable 8W TX bursts (recommended)
7266 CONFIG_ATM_ENI_BURST_TX_8W
7267 Burst eight words at once in the send direction. This is the default
7270 Enable 4W TX bursts (optional)
7271 CONFIG_ATM_ENI_BURST_TX_4W
7272 Burst four words at once in the send direction. You may want to try
7273 this if you have disabled 8W bursts. Enabling 4W if 8W is also set
7274 may or may not improve throughput.
7276 Enable 2W TX bursts (optional)
7277 CONFIG_ATM_ENI_BURST_TX_2W
7278 Burst two words at once in the send direction. You may want to try
7279 this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
7280 are also set may or may not improve throughput.
7282 Enable 16W RX bursts (discouraged)
7283 CONFIG_ATM_ENI_BURST_RX_16W
7284 Burst sixteen words at once in the receive direction. This may work
7285 with recent PCI chipsets, but is known to fail with older chipsets.
7287 Enable 8W RX bursts (discouraged)
7288 CONFIG_ATM_ENI_BURST_RX_8W
7289 Burst eight words at once in the receive direction. This may work
7290 with recent PCI chipsets, but is known to fail with older chipsets,
7291 such as the Intel Neptune series.
7293 Enable 4W RX bursts (recommended)
7294 CONFIG_ATM_ENI_BURST_RX_4W
7295 Burst four words at once in the receive direction. This is the
7296 default setting. Enabling 4W if 8W is also set may or may not
7299 Enable 2W RX bursts (optional)
7300 CONFIG_ATM_ENI_BURST_RX_2W
7301 Burst two words at once in the receive direction. You may want to
7302 try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
7303 8W are also set may or may not improve throughput.
7305 ZeitNet ZN1221/ZN1225
7307 Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
7310 This driver is also available as a module. If you want to compile
7311 it as a module, say M here and read
7312 <file:Documentation/modules.txt>. The module will be called zatm.o.
7314 Enable extended debugging
7315 CONFIG_ATM_ZATM_DEBUG
7316 Extended debugging records various events and displays that list
7317 when an inconsistency is detected. This mechanism is faster than
7318 generally using printks, but still has some impact on performance.
7319 Note that extended debugging may create certain race conditions
7320 itself. Enable this ONLY if you suspect problems with the driver.
7322 Fujitsu FireStream (FS50/FS155)
7323 CONFIG_ATM_FIRESTREAM
7324 Driver for the Fujitsu FireStream 155 (MB86697) and
7325 FireStream 50 (MB86695) ATM PCI chips.
7327 This driver is also available as a module. If you want to compile
7328 it as a module, say M here and read
7329 <file:Documentation/modules.txt>. The module will be called
7332 Enable usec resolution timestamps
7333 CONFIG_ATM_ZATM_EXACT_TS
7334 The uPD98401 SAR chip supports a high-resolution timer (approx. 30
7335 MHz) that is used for very accurate reception timestamps. Because
7336 that timer overflows after 140 seconds, and also to avoid timer
7337 drift, time measurements need to be periodically synchronized with
7338 the normal system time. Enabling this feature will add some general
7339 overhead for timer synchronization and also per-packet overhead for
7342 IDT 77201/11 (NICStAR) (ForeRunnerLE)
7344 The NICStAR chipset family is used in a large number of ATM NICs for
7345 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
7346 series. Say Y if you have one of those.
7348 This driver is also available as a module. If you want to compile
7349 it as a module, say M here and read
7350 <file:Documentation/modules.txt>. The module will be called
7353 Use suni PHY driver (155Mbps)
7354 CONFIG_ATM_NICSTAR_USE_SUNI
7355 Support for the S-UNI and compatible PHYsical layer chips. These are
7356 found in most 155Mbps NICStAR based ATM cards, namely in the
7357 ForeRunner LE155 cards. This driver provides detection of cable~
7358 removal and reinsertion and provides some statistics. This driver
7359 doesn't have removal capability when compiled as a module, so if you
7360 need that capability don't include S-UNI support (it's not needed to
7361 make the card work).
7363 Use IDT77015 PHY driver (25Mbps)
7364 CONFIG_ATM_NICSTAR_USE_IDT77105
7365 Support for the PHYsical layer chip in ForeRunner LE25 cards. In
7366 addition to cable removal/reinsertion detection, this driver allows
7367 you to control the loopback mode of the chip via a dedicated IOCTL.
7368 This driver is required for proper handling of temporary carrier
7369 loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
7371 IDT 77252 (NICStAR II)
7373 Driver for the IDT 77252 ATM PCI chips.
7375 This driver is also available as a module. If you want to compile
7376 it as a module, say M here and read
7377 <file:Documentation/modules.txt>. The module will be called idt77252.o
7379 Enable debugging messages
7380 CONFIG_ATM_IDT77252_DEBUG
7381 Somewhat useful debugging messages are available. The choice of
7382 messages is controlled by a bitmap. This may be specified as a
7383 module argument. See the file <file:drivers/atm/idt77252.h> for
7384 the meanings of the bits in the mask.
7386 When active, these messages can have a significant impact on the
7387 speed of the driver, and the size of your syslog files! When
7388 inactive, they will have only a modest impact on performance.
7390 Receive ALL cells in raw queue
7391 CONFIG_ATM_IDT77252_RCV_ALL
7392 Enable receiving of all cells on the ATM link, that do not match
7393 an open connection in the raw cell queue of the driver. Useful
7394 for debugging or special applications only, so the safe answer is N.
7396 Madge Ambassador (Collage PCI 155 Server)
7397 CONFIG_ATM_AMBASSADOR
7398 This is a driver for ATMizer based ATM card produced by Madge
7399 Networks Ltd. Say Y (or M to compile as a module named ambassador.o)
7400 here if you have one of these cards.
7402 Enable debugging messages
7403 CONFIG_ATM_AMBASSADOR_DEBUG
7404 Somewhat useful debugging messages are available. The choice of
7405 messages is controlled by a bitmap. This may be specified as a
7406 module argument (kernel command line argument as well?), changed
7407 dynamically using an ioctl (not yet) or changed by sending the
7408 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
7409 <file:drivers/atm/ambassador.h> for the meanings of the bits in the
7412 When active, these messages can have a significant impact on the
7413 speed of the driver, and the size of your syslog files! When
7414 inactive, they will have only a modest impact on performance.
7416 Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)
7418 This is a driver for the Horizon chipset ATM adapter cards once
7419 produced by Madge Networks Ltd. Say Y (or M to compile as a module
7420 named horizon.o) here if you have one of these cards.
7422 Enable debugging messages
7423 CONFIG_ATM_HORIZON_DEBUG
7424 Somewhat useful debugging messages are available. The choice of
7425 messages is controlled by a bitmap. This may be specified as a
7426 module argument (kernel command line argument as well?), changed
7427 dynamically using an ioctl (not yet) or changed by sending the
7428 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
7429 <file:drivers/atm/horizon.h> for the meanings of the bits in the
7432 When active, these messages can have a significant impact on the
7433 speed of the driver, and the size of your syslog files! When
7434 inactive, they will have only a modest impact on performance.
7436 Interphase ATM PCI x575/x525/x531
7438 This is a driver for the Interphase (i)ChipSAR adapter cards
7439 which include a variety of variants in term of the size of the
7440 control memory (128K-1KVC, 512K-4KVC), the size of the packet
7441 memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
7442 UTP155, UTP25, DS3 and E3). Go to:
7443 <http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
7444 for more info about the cards. Say Y (or M to compile as a module
7445 named iphase.o) here if you have one of these cards.
7447 See the file <file:Documentation/networking/iphase.txt> for further
7450 Enable debugging messages
7452 Somewhat useful debugging messages are available. The choice of
7453 messages is controlled by a bitmap. This may be specified as a
7454 module argument (kernel command line argument as well?), changed
7455 dynamically using an ioctl (Get the debug utility, iadbg, from
7456 <ftp://ftp.iphase.com/pub/atm/pci/>).
7458 See the file <file:drivers/atm/iphase.h> for the meanings of the
7461 When active, these messages can have a significant impact on the
7462 speed of the driver, and the size of your syslog files! When
7463 inactive, they will have only a modest impact on performance.
7465 Efficient Networks Speedstream 3010
7467 Supports ATM cards based on the Efficient Networks "Lanai"
7468 chipset such as the Speedstream 3010 and the ENI-25p. The
7469 Speedstream 3060 is currently not supported since we don't
7470 have the code to drive the on-board Alcatel DSL chipset (yet).
7472 Linux telephony support
7474 Say Y here if you have a telephony card, which for example allows
7475 you to use a regular phone for voice-over-IP applications.
7477 Note: this has nothing to do with modems. You do not need to say Y
7478 here in order to be able to use a modem under Linux.
7480 This support is also available as a module. If you want to compile
7481 it as a module, say M here and read
7482 <file:Documentation/modules.txt>. The module will be called
7485 Compaq Smart Array support
7486 CONFIG_BLK_CPQ_CISS_DA
7487 This is the driver for Compaq Smart Array 5xxx controllers.
7488 Everyone using these boards should say Y here.
7489 See <file:Documentation/cciss.txt> for the current list of
7490 boards supported by this driver, and for further information
7491 on the use of this driver.
7493 This driver is also available as a module ( = code which can be
7494 inserted in and removed from the running kernel whenever you want).
7495 If you want to compile it as a module, say M here and read
7496 <file:Documentation/modules.txt>. The module will be called
7499 SCSI tape drive support for Smart Array 5xxx
7500 CONFIG_CISS_SCSI_TAPE
7501 When enabled (Y), this option allows SCSI tape drives and SCSI medium
7502 changers (tape robots) to be accessed via a Compaq 5xxx array
7503 controller. (See <file:Documentation/cciss.txt> for more details.)
7505 "SCSI support" and "SCSI tape support" must also be enabled for this
7508 When this option is disabled (N), the SCSI portion of the driver
7511 Enable monitor thread
7512 CONFIG_CISS_MONITOR_THREAD
7513 Intended for use with multipath configurations (see the md driver).
7514 This option allows a per-adapter monitoring thread to periodically
7515 poll the adapter to detect failure modes in which the processor
7516 is unable to receive interrupts from the adapter, thus enabling
7517 fail-over to an alternate adapter in such situations. See
7518 <file:Documentation/cciss.txt> for more details.
7520 QuickNet Internet LineJack/PhoneJack support
7522 Say M if you have a telephony card manufactured by Quicknet
7523 Technologies, Inc. These include the Internet PhoneJACK and
7524 Internet LineJACK Telephony Cards. You will get a module called
7527 For the ISA versions of these products, you can configure the
7528 cards using the isapnp tools (pnpdump/isapnp) or you can use the
7529 isapnp support. Please read <file:Documentation/telephony/ixj.txt>.
7531 For more information on these cards, see Quicknet's web site at:
7532 <http://www.quicknet.net/>.
7534 If you do not have any Quicknet telephony cards, you can safely
7537 QuickNet Internet LineJack/PhoneJack PCMCIA support
7538 CONFIG_PHONE_IXJ_PCMCIA
7539 Say Y here to configure in PCMCIA service support for the Quicknet
7540 cards manufactured by Quicknet Technologies, Inc. This builds an
7541 additional support module for the PCMCIA version of the card.
7543 FORE Systems 200E-series
7544 CONFIG_ATM_FORE200E_MAYBE
7545 This is a driver for the FORE Systems 200E-series ATM adapter
7546 cards. It simultaneously supports PCA-200E and SBA-200E models
7547 on PCI and SBUS hosts. Say Y (or M to compile as a module
7548 named fore_200e.o) here if you have one of these ATM adapters.
7550 Note that the driver will actually be compiled only if you
7551 additionally enable the support for PCA-200E and/or SBA-200E
7554 See the file <file:Documentation/networking/fore200e.txt> for
7557 Enable PCA-200E card support on PCI-based hosts
7558 CONFIG_ATM_FORE200E_PCA
7559 Say Y here if you want your PCA-200E cards to be probed.
7561 Use default PCA-200E firmware
7562 CONFIG_ATM_FORE200E_PCA_DEFAULT_FW
7563 Use the default PCA-200E firmware data shipped with the driver.
7565 Normal users do not have to deal with the firmware stuff, so
7566 they should say Y here.
7568 Pathname of user-supplied binary firmware
7569 CONFIG_ATM_FORE200E_PCA_FW
7570 This defines the pathname of an alternative PCA-200E binary
7571 firmware image supplied by the user. This pathname may be
7572 absolute or relative to the drivers/atm directory.
7574 The driver comes with an adequate firmware image, so normal users do
7575 not have to supply an alternative one. They just say Y to "Use
7576 default PCA-200E firmware" instead.
7578 Enable SBA-200E card support on SBUS-based hosts
7579 CONFIG_ATM_FORE200E_SBA
7580 Say Y here if you want your SBA-200E cards to be probed.
7582 Use default SBA-200E firmware
7583 CONFIG_ATM_FORE200E_SBA_DEFAULT_FW
7584 Use the default SBA-200E firmware data shipped with the driver.
7586 Normal users do not have to deal with the firmware stuff, so
7587 they should say Y here.
7589 Pathname of user-supplied binary firmware
7590 CONFIG_ATM_FORE200E_SBA_FW
7591 This defines the pathname of an alternative SBA-200E binary
7592 firmware image supplied by the user. This pathname may be
7593 absolute or relative to the drivers/atm directory.
7595 The driver comes with an adequate firmware image, so normal users do
7596 not have to supply an alternative one. They just say Y to "Use
7597 default SBA-200E firmware", above.
7599 CONFIG_ATM_FORE200E_USE_TASKLET
7600 This defers work to be done by the interrupt handler to a
7601 tasklet instead of handling everything at interrupt time. This
7602 may improve the responsiveness of the host.
7604 Maximum number of tx retries
7605 CONFIG_ATM_FORE200E_TX_RETRY
7606 Specifies the number of times the driver attempts to transmit
7607 a message before giving up, if the transmit queue of the ATM card
7608 is transiently saturated.
7610 Saturation of the transmit queue may occur only under extreme
7611 conditions, e.g. when a fast host continuously submits very small
7612 frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
7614 Note that under common conditions, it is unlikely that you encounter
7615 a saturation of the transmit queue, so the retry mechanism never
7618 Debugging level (0-3)
7619 CONFIG_ATM_FORE200E_DEBUG
7620 Specifies the level of debugging messages issued by the driver.
7621 The verbosity of the driver increases with the value of this
7624 When active, these messages can have a significant impact on
7625 the performances of the driver, and the size of your syslog files!
7626 Keep the debugging level to 0 during normal operations.
7628 ForeRunner HE Series
7630 This is a driver for the Marconi ForeRunner HE-series ATM adapter
7631 cards. It simultaneously supports the 155 and 622 versions.
7633 Use S/UNI PHY driver
7634 Support for the S/UNI-Ultra and S/UNI-622 found in the ForeRunner
7635 HE cards. This driver provides carrier detection some statistics.
7639 Support PPP (Point to Point Protocol) encapsulated in ATM frames.
7640 This implementation does not yet comply with section 8 of RFC2364,
7641 which can lead to bad results idf the ATM peer loses state and
7642 changes its encapsulation unilaterally.
7644 Fusion MPT device support
7646 LSI Logic Fusion(TM) Message Passing Technology (MPT) device support
7647 provides high performance SCSI host initiator, and LAN [1] interface
7648 services to a host system. The Fusion architecture is capable of
7649 duplexing these protocols on high-speed Fibre Channel
7650 (up to 2 GHz x 2 ports = 4 GHz) and parallel SCSI (up to Ultra-320)
7653 [1] LAN is not supported on parallel SCSI medium.
7655 These drivers require a Fusion MPT compatible PCI adapter installed
7656 in the host system. MPT adapters contain specialized I/O processors
7657 to handle I/O workload, and more importantly to offload this work
7658 from the host CPU(s).
7660 If you have Fusion MPT hardware and want to use it, you can say
7661 Y or M here to add MPT (base + ScsiHost) drivers.
7662 <Y> = build lib (fusion.o), and link [static] into the kernel [2]
7664 <M> = compiled as [dynamic] modules [3] named: (mptbase.o,
7667 [2] In order enable capability to boot the linux kernel
7668 natively from a Fusion MPT target device, you MUST
7669 answer Y here! (currently requires CONFIG_BLK_DEV_SD)
7670 [3] This support is also available as a module ( = code
7671 which can be inserted in and removed from the running
7672 kernel whenever you want). If you want to compile as
7673 modules, say M here and read
7674 <file:Documentation/modules.txt>.
7678 If you say Y or M here you will get a choice of these
7679 additional protocol and support module options: Module Name:
7680 <M> Enhanced SCSI error reporting (isense.o)
7681 <M> Fusion MPT misc device (ioctl) driver (mptctl.o)
7682 <M> Fusion MPT LAN driver (mptlan.o)
7685 Fusion MPT is trademark of LSI Logic Corporation, and its
7686 architecture is based on LSI Logic's Message Passing Interface (MPI)
7689 Maximum number of scatter gather entries
7690 CONFIG_FUSION_MAX_SGE
7691 This option allows you to specify the maximum number of scatter-
7692 gather entries per I/O. The driver defaults to 40, a reasonable number
7693 for most systems. However, the user may increase this up to 128.
7694 Increasing this parameter will require significantly more memory
7695 on a per controller instance. Increasing the parameter is not
7696 necessary (or recommended) unless the user will be running
7697 large I/O's via the raw interface.
7699 Fusion MPT enhanced SCSI error reporting [optional] module
7700 CONFIG_FUSION_ISENSE
7701 The isense module (roughly stands for Interpret SENSE data) is
7702 completely optional. It simply provides extra English readable
7703 strings in SCSI Error Report(s) that might be generated from the
7704 Fusion MPT SCSI Host driver, for example when a target device
7705 returns a SCSI check condition on a I/O. Without this module
7706 loaded you might see:
7708 SCSI Error Report =-=-= (ioc0,scsi5:0)
7709 SCSI_Status=02h (CHECK_CONDITION)
7710 Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00
7711 SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
7712 SenseKey=2h (NOT READY); FRU=02h
7715 Where otherwise, if this module had been loaded, you would see:
7717 SCSI Error Report =-=-= (ioc0,scsi5:0)
7718 SCSI_Status=02h (CHECK_CONDITION)
7719 Original_CDB[]: 2A 00 00 00 00 41 00 00 02 00 - "WRITE(10)"
7720 SenseData[12h]: 70 00 02 00 00 00 00 0A 00 00 00 00 04 02 02 00 00 00
7721 SenseKey=2h (NOT READY); FRU=02h
7722 ASC/ASCQ=29h/00h "LOGICAL UNIT NOT READY, INITIALIZING CMD. REQUIRED"
7724 Say M for "Enhanced SCSI error reporting" to compile this optional module,
7725 creating a driver named: isense.o.
7727 NOTE: Support for building this feature into the kernel is not
7728 available, due to kernel size considerations.
7730 Fusion MPT misc device (ioctl) driver [optional] module
7732 The Fusion MPT misc device driver provides specialized control
7733 of MPT adapters via system ioctl calls. Use of ioctl calls to
7734 the MPT driver requires that you create and use a misc device
7736 mknod /dev/mptctl c 10 220
7738 One use of this ioctl interface is to perform an upgrade (reflash)
7739 of the MPT adapter firmware. Refer to readme file(s) distributed
7740 with the Fusion MPT linux driver for additional details.
7742 If enabled by saying M to this, a driver named: mptctl.o
7745 If unsure whether you really want or need this, say N.
7747 Fusion MPT LAN driver [optional]
7749 This module supports LAN IP traffic over Fibre Channel port(s)
7750 on Fusion MPT compatible hardware (LSIFC9xx chips).
7751 The physical interface used is defined in RFC 2625.
7752 Please refer to that document for details.
7754 Installing this driver requires the knowledge to configure and
7755 activate a new network interface, "fc0", using standard Linux tools.
7757 If enabled by saying M to this, a driver named: mptlan.o
7760 If unsure whether you really want or need this, say N.
7762 NOTES: This feature is NOT available nor supported for linux-2.2.x
7763 kernels. You must be building a linux-2.3.x or linux-2.4.x kernel
7764 in order to configure this option.
7765 Support for building this feature into the linux kernel is not
7770 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
7771 any other SCSI device under Linux, say Y and make sure that you know
7772 the name of your SCSI host adapter (the card inside your computer
7773 that "speaks" the SCSI protocol, also called SCSI controller),
7774 because you will be asked for it.
7776 You also need to say Y here if you want support for the parallel
7777 port version of the 100 MB IOMEGA ZIP drive.
7779 This driver is also available as a module ( = code which can be
7780 inserted in and removed from the running kernel whenever you want).
7781 The module will be called scsi_mod.o. If you want to compile it as
7782 a module, say M here and read <file:Documentation/modules.txt> and
7783 <file:Documentation/scsi.txt>. However, do not compile this as a
7784 module if your root file system (the one containing the directory /)
7785 is located on a SCSI device.
7789 If you want to use a SCSI hard disk or the SCSI or parallel port
7790 version of the IOMEGA ZIP drive under Linux, say Y and read the
7791 SCSI-HOWTO, the Disk-HOWTO and the Multi-Disk-HOWTO, available from
7792 <http://www.tldp.org/docs.html#howto>. This is NOT for SCSI
7795 This driver is also available as a module ( = code which can be
7796 inserted in and removed from the running kernel whenever you want).
7797 The module will be called sd_mod.o. If you want to compile it as a
7798 module, say M here and read <file:Documentation/modules.txt> and
7799 <file:Documentation/scsi.txt>. Do not compile this driver as a
7800 module if your root file system (the one containing the directory /)
7801 is located on a SCSI disk. In this case, do not compile the driver
7802 for your SCSI host adapter (below) as a module either.
7804 Maximum number of SCSI disks that can be loaded as modules
7805 CONFIG_SD_EXTRA_DEVS
7806 This controls the amount of additional space allocated in tables for
7807 drivers that are loaded as modules after the kernel is booted. In
7808 the event that the SCSI core itself was loaded as a module, this
7809 value is the number of additional disks that can be loaded after the
7810 first host driver is loaded.
7812 Admittedly this isn't pretty, but there are tons of race conditions
7813 involved with resizing the internal arrays on the fly. Someday this
7814 flag will go away, and everything will work automatically.
7816 If you don't understand what's going on, go with the default.
7818 Maximum number of SCSI tapes that can be loaded as modules
7819 CONFIG_ST_EXTRA_DEVS
7820 This controls the amount of additional space allocated in tables for
7821 drivers that are loaded as modules after the kernel is booted. In
7822 the event that the SCSI core itself was loaded as a module, this
7823 value is the number of additional tapes that can be loaded after the
7824 first host driver is loaded.
7826 Admittedly this isn't pretty, but there are tons of race conditions
7827 involved with resizing the internal arrays on the fly. Someday this
7828 flag will go away, and everything will work automatically.
7830 If you don't understand what's going on, go with the default.
7834 If you want to use a SCSI tape drive under Linux, say Y and read the
7835 SCSI-HOWTO, available from
7836 <http://www.tldp.org/docs.html#howto>, and
7837 <file:drivers/scsi/README.st> in the kernel source. This is NOT for
7840 This driver is also available as a module ( = code which can be
7841 inserted in and removed from the running kernel whenever you want).
7842 The module will be called st.o. If you want to compile it as a
7843 module, say M here and read <file:Documentation/modules.txt> and
7844 <file:Documentation/scsi.txt>.
7846 OnStream SC-x0 SCSI tape support
7848 The OnStream SC-x0 SCSI tape drives can not be driven by the
7849 standard st driver, but instead need this special osst driver and
7850 use the /dev/osstX char device nodes (major 206). Via usb-storage
7851 and ide-scsi, you may be able to drive the USB-x0 and DI-x0 drives
7852 as well. Note that there is also a second generation of OnStream
7853 tape drives (ADR-x0) that supports the standard SCSI-2 commands for
7854 tapes (QIC-157) and can be driven by the standard driver st.
7855 For more information, you may have a look at the SCSI-HOWTO
7856 <http://www.tldp.org/docs.html#howto> and
7857 <file:drivers/scsi/README.osst> in the kernel source.
7858 More info on the OnStream driver may be found on
7859 <http://linux1.onstream.nl/test/>
7860 Please also have a look at the standard st docu, as most of it
7861 applies to osst as well.
7863 This driver is also available as a module ( = code which can be
7864 inserted in and removed from the running kernel whenever you want).
7865 The module will be called osst.o. If you want to compile it as a
7866 module, say M here and read <file:Documentation/modules.txt> and
7867 <file:Documentation/scsi.txt>.
7871 If you want to use a SCSI CD-ROM under Linux, say Y and read the
7872 SCSI-HOWTO and the CD-ROM-HOWTO at
7873 <http://www.tldp.org/docs.html#howto>. Also make sure to say Y
7874 or M to "ISO 9660 CD-ROM file system support" later.
7876 This driver is also available as a module ( = code which can be
7877 inserted in and removed from the running kernel whenever you want).
7878 The module will be called sr_mod.o. If you want to compile it as a
7879 module, say M here and read <file:Documentation/modules.txt> and
7880 <file:Documentation/scsi.txt>.
7882 Maximum number of CD-ROM devices that can be loaded as modules
7883 CONFIG_SR_EXTRA_DEVS
7884 This controls the amount of additional space allocated in tables for
7885 drivers that are loaded as modules after the kernel is booted. In
7886 the event that the SCSI core itself was loaded as a module, this
7887 value is the number of additional CD-ROMs that can be loaded after
7888 the first host driver is loaded.
7890 Admittedly this isn't pretty, but there are tons of race conditions
7891 involved with resizing the internal arrays on the fly. Someday this
7892 flag will go away, and everything will work automatically.
7894 If you don't understand what's going on, go with the default.
7896 Enable vendor-specific extensions (for SCSI CD-ROM)
7897 CONFIG_BLK_DEV_SR_VENDOR
7898 This enables the usage of vendor specific SCSI commands. This is
7899 required to support multisession CDs with old NEC/TOSHIBA cdrom
7900 drives (and HP Writers). If you have such a drive and get the first
7901 session only, try saying Y here; everybody else says N.
7903 SCSI generic support
7905 If you want to use SCSI scanners, synthesizers or CD-writers or just
7906 about anything having "SCSI" in its name other than hard disks,
7907 CD-ROMs or tapes, say Y here. These won't be supported by the kernel
7908 directly, so you need some additional software which knows how to
7909 talk to these devices using the SCSI protocol:
7911 For scanners, look at SANE (<http://www.mostang.com/sane/>). For CD
7912 writer software look at Cdrtools
7913 (<http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html>)
7914 and for burning a "disk at once": CDRDAO
7915 (<http://cdrdao.sourceforge.net/>). Cdparanoia is a high
7916 quality digital reader of audio CDs (<http://www.xiph.org/paranoia/>).
7917 For other devices, it's possible that you'll have to write the
7918 driver software yourself. Please read the file
7919 <file:Documentation/scsi-generic.txt> for more information.
7921 If you want to compile this as a module ( = code which can be
7922 inserted in and removed from the running kernel whenever you want),
7923 say M here and read <file:Documentation/modules.txt> and
7924 <file:Documentation/scsi.txt>. The module will be called sg.o. If unsure,
7927 Probe all LUNs on each SCSI device
7928 CONFIG_SCSI_MULTI_LUN
7929 If you have a SCSI device that supports more than one LUN (Logical
7930 Unit Number), e.g. a CD jukebox, and only one LUN is detected, you
7931 can say Y here to force the SCSI driver to probe for multiple LUNs.
7932 A SCSI device with multiple LUNs acts logically like multiple SCSI
7933 devices. The vast majority of SCSI devices have only one LUN, and
7934 so most people can say N here and should in fact do so, because it
7937 Verbose SCSI error reporting (kernel size +=12K)
7938 CONFIG_SCSI_CONSTANTS
7939 The error messages regarding your SCSI hardware will be easier to
7940 understand if you say Y here; it will enlarge your kernel by about
7941 12 KB. If in doubt, say Y.
7943 SCSI logging facility
7945 This turns on a logging facility that can be used to debug a number
7946 of SCSI related problems.
7948 If you say Y here, no logging output will appear by default, but you
7949 can enable logging by saying Y to "/proc file system support" and
7950 "Sysctl support" below and executing the command
7952 echo "scsi log token [level]" > /proc/scsi/scsi
7954 at boot time after the /proc file system has been mounted.
7956 There are a number of things that can be used for 'token' (you can
7957 find them in the source: <file:drivers/scsi/scsi.c>), and this
7958 allows you to select the types of information you want, and the
7959 level allows you to select the level of verbosity.
7961 If you say N here, it may be harder to track down some types of SCSI
7962 problems. If you say Y here your kernel will be somewhat larger, but
7963 there should be no noticeable performance impact as long as you have
7966 QDIO base support for IBM S/390 and zSeries
7968 This driver provides the Queued Direct I/O base support for the
7969 IBM S/390 (G5 and G6) and eServer zSeries (z800, z900 and z990).
7971 For details please refer to the documentation provided by IBM at
7972 <http://www10.software.ibm.com/developerworks/opensource/linux390>
7974 This driver is also available as a module ( = code which can be
7975 inserted in and removed from the running kernel whenever you want).
7976 The module will be called qdio.o. If you want to compile it as a
7977 module, say M here and read <file:Documentation/modules.txt>.
7981 Performance statistics for QDIO base support
7982 CONFIG_QDIO_PERF_STATS
7983 Say Y here to get performance statistics in /proc/qdio_perf
7987 IBM S/390 and zSeries OSA-Express and HiperSockets device driver
7989 This driver supports the IBM S/390 and zSeries OSA Express adapters
7990 in QDIO mode (all media types), HiperSockets interfaces and VM GuestLAN
7991 interfaces in QDIO and HIPER mode.
7993 For details please refer to the documentation provided by IBM at
7994 <http://www10.software.ibm.com/developerworks/opensource/linux390>
7996 This driver is also available as a module (code which can be
7997 inserted in and removed from the running kernel whenever you
7998 want). If you want to compile it as a module, say 'M' here and
7999 read file Documentation/modules.txt.
8001 IPv6 support for qeth
8003 If CONFIG_QETH is switched on, this option will include IPv6
8004 support in the qeth device driver.
8006 IEEE 802.1q VLAN support for qeth
8008 If CONFIG_QETH is switched on, this option will include IEEE
8009 802.1q VLAN support in the qeth device driver.
8011 Performance statistics for the qeth drivers
8012 CONFIG_QETH_PERF_STATS
8013 When switched on, this option will add a file in the proc-fs
8014 (/proc/qeth_perf_stats) containing performance statistics. It
8015 may slightly impact performance, so this is only recommended for
8016 internal tuning of the device driver.
8018 SGI WD93C93 SCSI Driver
8020 Say Y here to support the on-board WD93C93 SCSI controller found (a)
8021 on the Indigo2 and other MIPS-based SGI machines, and (b) on ARCS
8024 DEC NCR53C94 SCSI Driver
8026 Say Y here to support the NCR53C94 SCSI controller chips on IOASIC
8027 based TURBOchannel DECstations and TURBOchannel PMAZ-A cards.
8029 AdvanSys SCSI support
8030 CONFIG_SCSI_ADVANSYS
8031 This is a driver for all SCSI host adapters manufactured by
8032 AdvanSys. It is documented in the kernel source in
8033 <file:drivers/scsi/advansys.c>.
8035 This driver is also available as a module ( = code which can be
8036 inserted in and removed from the running kernel whenever you want).
8037 If you want to compile it as a module, say M here and read
8038 <file:Documentation/modules.txt>. The module will be called
8041 Adaptec AHA152X/2825 support
8043 This is a driver for the AHA-1510, AHA-1520, AHA-1522, and AHA-2825
8044 SCSI host adapters. It also works for the AVA-1505, but the IRQ etc.
8045 must be manually specified in this case.
8047 It is explained in section 3.3 of the SCSI-HOWTO, available from
8048 <http://www.tldp.org/docs.html#howto>. You might also want to
8049 read the file <file:drivers/scsi/README.aha152x>.
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 will be called aha152x.o. If you want to compile it as a
8054 module, say M here and read <file:Documentation/modules.txt>.
8056 Adaptec AHA1542 support
8058 This is support for a SCSI host adapter. It is explained in section
8059 3.4 of the SCSI-HOWTO, available from
8060 <http://www.tldp.org/docs.html#howto>. Note that Trantor was
8061 purchased by Adaptec, and some former Trantor products are being
8062 sold under the Adaptec name. If it doesn't work out of the box, you
8063 may have to change some settings in <file:drivers/scsi/aha1542.h>.
8065 If you want to compile this as a module ( = code which can be
8066 inserted in and removed from the running kernel whenever you want),
8067 say M here and read <file:Documentation/modules.txt>. The module
8068 will be called aha1542.o.
8070 Adaptec AHA1740 support
8072 This is support for a SCSI host adapter. It is explained in section
8073 3.5 of the SCSI-HOWTO, available from
8074 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
8075 of the box, you may have to change some settings in
8076 <file:drivers/scsi/aha1740.h>.
8078 This driver is also available as a module ( = code which can be
8079 inserted in and removed from the running kernel whenever you want).
8080 The module will be called aha1740.o. If you want to compile it as a
8081 module, say M here and read <file:Documentation/modules.txt>.
8083 Adaptec AIC7xxx support
8085 This driver supports all of Adaptec's Fast through Ultra 160 PCI
8086 based SCSI controllers as well as the aic7770 based EISA and VLB
8087 SCSI controllers (the 274x and 284x series). For AAA and ARO based
8088 configurations, only SCSI functionality is provided.
8090 If you want to compile the driver as a module ( = code which can be
8091 inserted in and removed from the running kernel whenever you want),
8092 say M here and read <file:Documentation/modules.txt>. The module
8093 will be called aic7xxx.o.
8095 Maximum number of TCQ commands per device
8096 CONFIG_AIC7XXX_CMDS_PER_DEVICE
8097 Specify the number of commands you would like to allocate per SCSI
8098 device when Tagged Command Queueing (TCQ) is enabled on that device.
8100 This is an upper bound value for the number of tagged transactions
8101 to be used for any device. The aic7xxx driver will automatically
8102 vary this number based on device behavior. For devices with a
8103 fixed maximum, the driver will eventually lock to this maximum
8104 and display a console message indicating this value.
8106 Due to resource allocation issues in the Linux SCSI mid-layer, using
8107 a high number of commands per device may result in memory allocation
8108 failures when many devices are attached to the system. For this reason,
8109 the default is set to 32. Higher values may result in higer performance
8110 on some devices. The upper bound is 253. 0 disables tagged queueing.
8112 Per device tag depth can be controlled via the kernel command line
8113 "tag_info" option. See drivers/scsi/aic7xxx/README.aic7xxx
8118 Initial bus reset delay in milli-seconds
8119 CONFIG_AIC7XXX_RESET_DELAY_MS
8120 The number of milliseconds to delay after an initial bus reset.
8121 The bus settle delay following all error recovery actions is
8122 dictated by the SCSI layer and is not affected by this value.
8124 Default: 15000 (15 seconds)
8126 Probe for EISA and VL AIC7XXX Adapters
8127 CONFIG_AIC7XXX_PROBE_EISA_VL
8128 Probe for EISA and VLB Aic7xxx controllers. In many newer systems,
8129 the invasive probes necessary to detect these controllers can cause
8130 other devices to fail. For this reason, the non-PCI probe code is
8131 disabled by default. The current value of this option can be "toggled"
8132 via the no_probe kernel command line option.
8134 CONFIG_AIC7XXX_BUILD_FIRMWARE
8135 This option should only be enabled if you are modifying the firmware
8136 source to the aic7xxx driver and wish to have the generated firmware
8137 include files updated during a normal kernel build. The assembler
8138 for the firmware requires lex and yacc or their equivalents, as well
8139 as the db v1 library. You may have to install additional packages
8140 or modify the assembler Makefile or the files it includes if your
8141 build environment is different than that of the author.
8143 Compile in Debugging Code
8144 CONFIG_AIC7XXX_DEBUG_ENABLE
8145 Compile in aic7xxx debugging code that can be useful in diagnosing
8148 Debug code enable mask (2048 for all debugging)
8149 CONFIG_AIC7XXX_DEBUG_MASK
8150 Bit mask of debug options that is only valid if the
8151 CONFIG_AIC7XXX_DEBUG_ENABLE option is enabled. The bits in this mask
8152 are defined in the drivers/scsi/aic7xxx/aic7xxx.h - search for the
8153 variable ahc_debug in that file to find them.
8157 Decode registers during diagnostics
8158 CONFIG_AIC7XXX_REG_PRETTY_PRINT
8159 Compile in register value tables for the output of expanded register
8160 contents in diagnostics. This make it much easier to understand debug
8161 output without having to refer to a data book and/or the aic7xxx.reg file.
8163 Old Adaptec AIC7xxx support
8164 CONFIG_SCSI_AIC7XXX_OLD
8165 WARNING This driver is an older aic7xxx driver and is no longer
8166 under active development. Adaptec, Inc. is writing a new driver to
8167 take the place of this one, and it is recommended that whenever
8168 possible, people should use the new Adaptec written driver instead
8169 of this one. This driver will eventually be phased out entirely.
8171 This is support for the various aic7xxx based Adaptec SCSI
8172 controllers. These include the 274x EISA cards; 284x VLB cards;
8173 2902, 2910, 293x, 294x, 394x, 3985 and several other PCI and
8174 motherboard based SCSI controllers from Adaptec. It does not support
8175 the AAA-13x RAID controllers from Adaptec, nor will it likely ever
8176 support them. It does not support the 2920 cards from Adaptec that
8177 use the Future Domain SCSI controller chip. For those cards, you
8178 need the "Future Domain 16xx SCSI support" driver.
8180 In general, if the controller is based on an Adaptec SCSI controller
8181 chip from the aic777x series or the aic78xx series, this driver
8182 should work. The only exception is the 7810 which is specifically
8183 not supported (that's the RAID controller chip on the AAA-13x
8186 Note that the AHA2920 SCSI host adapter is *not* supported by this
8187 driver; choose "Future Domain 16xx SCSI support" instead if you have
8190 Information on the configuration options for this controller can be
8191 found by checking the help file for each of the available
8192 configuration options. You should read
8193 <file:drivers/scsi/aic7xxx_old/README.aic7xxx> at a minimum before
8194 contacting the maintainer with any questions. The SCSI-HOWTO,
8195 available from <http://www.tldp.org/docs.html#howto>, can also
8198 If you want to compile this driver as a module ( = code which can be
8199 inserted in and removed from the running kernel whenever you want),
8200 say M here and read <file:Documentation/modules.txt>. The module
8201 will be called aic7xxx_old.o.
8203 Enable tagged command queueing (TCQ) by default
8204 CONFIG_AIC7XXX_OLD_TCQ_ON_BY_DEFAULT
8205 This option causes the aic7xxx driver to attempt to use Tagged
8206 Command Queueing (TCQ) on all devices that claim to support it.
8208 TCQ is a feature of SCSI-2 which improves performance: the host
8209 adapter can send several SCSI commands to a device's queue even if
8210 previous commands haven't finished yet. Because the device is
8211 intelligent, it can optimize its operations (like head positioning)
8212 based on its own request queue. Not all devices implement this
8215 If you say Y here, you can still turn off TCQ on troublesome devices
8216 with the use of the tag_info boot parameter. See the file
8217 <file:drivers/scsi/README.aic7xxx> for more information on that and
8218 other aic7xxx setup commands. If this option is turned off, you may
8219 still enable TCQ on known good devices by use of the tag_info boot
8222 If you are unsure about your devices then it is safest to say N
8225 However, TCQ can increase performance on some hard drives by as much
8226 as 50% or more, so it is recommended that if you say N here, you
8227 should at least read the <file:drivers/scsi/README.aic7xxx> file so
8228 you will know how to enable this option manually should your drives
8229 prove to be safe in regards to TCQ.
8231 Conversely, certain drives are known to lock up or cause bus resets
8232 when TCQ is enabled on them. If you have a Western Digital
8233 Enterprise SCSI drive for instance, then don't even bother to enable
8234 TCQ on it as the drive will become unreliable, and it will actually
8237 Default number of TCQ commands per device
8238 CONFIG_AIC7XXX_OLD_CMDS_PER_DEVICE
8239 Specify the number of commands you would like to allocate per SCSI
8240 device when Tagged Command Queueing (TCQ) is enabled on that device.
8242 Reasonable figures are in the range of 8 to 24 commands per device,
8243 but depending on hardware could be increased or decreased from that
8244 figure. If the number is too high for any particular device, the
8245 driver will automatically compensate usually after only 10 minutes
8246 of uptime. It will not hinder performance if some of your devices
8247 eventually have their command depth reduced, but is a waste of
8248 memory if all of your devices end up reducing this number down to a
8249 more reasonable figure.
8251 NOTE: Certain very broken drives are known to lock up when given
8252 more commands than they like to deal with. Quantum Fireball drives
8253 are the most common in this category. For the Quantum Fireball
8254 drives it is suggested to use no more than 8 commands per device.
8258 Collect statistics to report in /proc
8259 CONFIG_AIC7XXX_OLD_PROC_STATS
8260 This option tells the driver to keep track of how many commands have
8261 been sent to each particular device and report that information to
8262 the user via the /proc/scsi/aic7xxx/n file, where n is the number of
8263 the aic7xxx controller you want the information on. This adds a
8264 small amount of overhead to each and every SCSI command the aic7xxx
8265 driver handles, so if you aren't really interested in this
8266 information, it is best to leave it disabled. This will only work if
8267 you also say Y to "/proc file system support", below.
8272 This driver supports all of Adaptec's Ultra 320 PCI-X based SCSI controllers.
8274 CONFIG_AIC79XX_CMDS_PER_DEVICE 32
8275 Specify the number of commands you would like to allocate per SCSI
8276 device when Tagged Command Queueing (TCQ) is enabled on that device.
8278 This is an upper bound value for the number of tagged transactions
8279 to be used for any device. The aic7xxx driver will automatically
8280 vary this number based on device behavior. For devices with a
8281 fixed maximum, the driver will eventually lock to this maximum
8282 and display a console message indicating this value.
8284 Due to resource allocation issues in the Linux SCSI mid-layer, using
8285 a high number of commands per device may result in memory allocation
8286 failures when many devices are attached to the system. For this reason,
8287 the default is set to 32. Higher values may result in higer performance
8288 on some devices. The upper bound is 253.
8290 Per device tag depth can be controlled via the kernel command line
8291 "tag_info" option. See drivers/scsi/aic7xxx/README.aic79xx
8296 CONFIG_AIC79XX_RESET_DELAY_MS 15000
8297 The number of milliseconds to delay after an initial bus reset.
8298 The bus settle delay following all error recovery actions is
8299 dictated by the SCSI layer and is not affected by this value.
8301 Default: 15000 (15 seconds)
8303 CONFIG_AIC79XX_BUILD_FIRMWARE
8304 This option should only be enabled if you are modifying the firmware
8305 source to the aic7xxx driver and wish to have the generated firmware
8306 include files updated during a normal kernel build. The assembler
8307 for the firmware requires lex and yacc or their equivalents, as well
8308 as the db v1 library. You may have to install additional packages
8309 or modify the assembler Makefile or the files it includes if your
8310 build environment is different than that of the author.
8312 CONFIG_AIC79XX_ENABLE_RD_STRM
8313 Read Streaming is a U320 protocol option that should enhance performance.
8314 Early U320 drive firmware actually performs slower with read streaming
8315 enabled so it is disabled by default. Read Streaming can be configured
8316 in much the same way as tagged queueing using the "rd_strm" command line
8317 option. See drivers/scsi/aic7xxx/README.aic79xx for details.
8319 CONFIG_AIC79XX_DEBUG_ENABLE
8320 Compile in aic79xx debugging code that can be useful in diagnosing
8323 CONFIG_AIC79XX_DEBUG_MASK
8324 Bit mask of debug options that is only valid if the
8325 CONFIG_AIC79XX_DEBUG_ENABLE option is enabled. The bits in this mask
8326 are defined in the drivers/scsi/aic7xxx/aic79xx.h - search for the
8327 variable ahd_debug in that file to find them.
8331 CONFIG_AIC79XX_REG_PRETTY_PRINT
8332 Compile in register value tables for the output of expanded register
8333 contents in diagnostics. This make it much easier to understand debug
8334 output without having to refer to a data book and/or the aic7xxx.reg file.
8336 Adaptec I2O RAID support
8338 This driver supports all of Adaptec's I2O based RAID controllers as
8339 well as the DPT SmartRaid V cards. This is an Adaptec maintained
8340 driver by Deanna Bonds. See <file:drivers/scsi/README.dpti>.
8342 This driver is also available as a module ( = code which can be
8343 inserted in and removed from the running kernel whenever you want).
8344 If you want to compile it as a module, say M here and read
8345 <file:Documentation/modules.txt>. The module will be called
8348 IBM ServeRAID support
8350 This is support for the IBM ServeRAID hardware RAID controllers.
8351 See <http://www.developer.ibm.com/welcome/netfinity/serveraid.html>
8352 for more information. If this driver does not work correctly
8353 without modification please contact the author by email at
8354 ipslinux@us.ibm.com.
8356 You can build this driver as a module ( = code which can be
8357 inserted in and removed from the running kernel whenever you want),
8358 but only a single instance may be loaded. If you want to compile it
8359 as a module, say M here and read <file:Documentation/modules.txt>.
8360 The module will be called ips.o.
8362 BusLogic SCSI support
8363 CONFIG_SCSI_BUSLOGIC
8364 This is support for BusLogic MultiMaster and FlashPoint SCSI Host
8365 Adapters. Consult the SCSI-HOWTO, available from
8366 <http://www.tldp.org/docs.html#howto>, and the files
8367 <file:drivers/scsi/README.BusLogic> and
8368 <file:drivers/scsi/README.FlashPoint> for more information. If this
8369 driver does not work correctly without modification, please contact
8370 the author, Leonard N. Zubkoff, by email to lnz@dandelion.com.
8372 You can also build this driver as a module ( = code which can be
8373 inserted in and removed from the running kernel whenever you want),
8374 but only a single instance may be loaded. If you want to compile it
8375 as a module, say M here and read <file:Documentation/modules.txt>.
8376 The module will be called BusLogic.o.
8378 Omit BusLogic SCSI FlashPoint support
8379 CONFIG_SCSI_OMIT_FLASHPOINT
8380 This option allows you to omit the FlashPoint support from the
8381 BusLogic SCSI driver. The FlashPoint SCCB Manager code is
8382 substantial, so users of MultiMaster Host Adapters may wish to omit
8385 Compaq Fibre Channel 64-bit/66Mhz HBA support
8387 Say Y here to compile in support for the Compaq StorageWorks Fibre
8388 Channel 64-bit/66Mhz Host Bus Adapter.
8390 If you want to compile the driver as a module ( = code which can be
8391 inserted in and removed from the running kernel whenever you want),
8392 say M here and read <file:Documentation/modules.txt>. The module
8393 will be called cpqfc.o.
8395 DMX3191D SCSI support
8396 CONFIG_SCSI_DMX3191D
8397 This is support for Domex DMX3191D SCSI Host Adapters.
8399 This driver is also available as a module ( = code which can be
8400 inserted in and removed from the running kernel whenever you want).
8401 The module will be called dmx3191d.o. If you want to compile it as
8402 a module, say M here and read <file:Documentation/modules.txt>.
8404 DTC3180/3280 SCSI support
8406 This is support for DTC 3180/3280 SCSI Host Adapters. Please read
8407 the SCSI-HOWTO, available from
8408 <http://www.tldp.org/docs.html#howto>, and the file
8409 <file:drivers/scsi/README.dtc3x80>.
8411 This driver is also available as a module ( = code which can be
8412 inserted in and removed from the running kernel whenever you want).
8413 The module will be called dtc.o. If you want to compile it as a
8414 module, say M here and read <file:Documentation/modules.txt>.
8416 EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti, Alphatronix) support
8417 CONFIG_SCSI_EATA_DMA
8418 This is support for the EATA-DMA protocol compliant SCSI Host
8419 Adapters like the SmartCache III/IV, SmartRAID controller families
8420 and the DPT PM2011B and PM2012B controllers.
8422 Note that this driver is obsolete; if you have one of the above
8423 SCSI Host Adapters, you should normally say N here and Y to "EATA
8424 ISA/EISA/PCI support", below. Please read the SCSI-HOWTO, available
8425 from <http://www.tldp.org/docs.html#howto>.
8427 This driver is also available as a module ( = code which can be
8428 inserted in and removed from the running kernel whenever you want).
8429 The module will be called eata_dma.o. If you want to compile it as
8430 a module, say M here and read <file:Documentation/modules.txt>.
8432 EATA-PIO (old DPT PM2001, PM2012A) support
8433 CONFIG_SCSI_EATA_PIO
8434 This driver supports all EATA-PIO protocol compliant SCSI Host
8435 Adapters like the DPT PM2001 and the PM2012A. EATA-DMA compliant
8436 host adapters could also use this driver but are discouraged from
8437 doing so, since this driver only supports hard disks and lacks
8438 numerous features. You might want to have a look at the SCSI-HOWTO,
8439 available from <http://www.tldp.org/docs.html#howto>.
8441 If you want to compile this as a module ( = code which can be
8442 inserted in and removed from the running kernel whenever you want),
8443 say M here and read <file:Documentation/modules.txt>. The module
8444 will be called eata_pio.o.
8446 UltraStor 14F/34F support
8448 This is support for the UltraStor 14F and 34F SCSI-2 host adapters.
8449 The source at <file:drivers/scsi/u14-34f.c> contains some
8450 information about this hardware. If the driver doesn't work out of
8451 the box, you may have to change some settings in
8452 <file: drivers/scsi/u14-34f.c>. Read the SCSI-HOWTO, available from
8453 <http://www.tldp.org/docs.html#howto>. Note that there is also
8454 another driver for the same hardware: "UltraStor SCSI support",
8455 below. You should say Y to both only if you want 24F support as
8458 This driver is also available as a module ( = code which can be
8459 inserted in and removed from the running kernel whenever you want).
8460 The module will be called u14-34f.o. If you want to compile it as a
8461 module, say M here and read <file:Documentation/modules.txt>.
8463 enable elevator sorting
8464 CONFIG_SCSI_U14_34F_LINKED_COMMANDS
8465 This option enables elevator sorting for all probed SCSI disks and
8466 CD-ROMs. It definitely reduces the average seek distance when doing
8467 random seeks, but this does not necessarily result in a noticeable
8468 performance improvement: your mileage may vary...
8470 The safe answer is N.
8472 maximum number of queued commands
8473 CONFIG_SCSI_U14_34F_MAX_TAGS
8474 This specifies how many SCSI commands can be maximally queued for
8475 each probed SCSI device. You should reduce the default value of 8
8476 only if you have disks with buggy or limited tagged command support.
8477 Minimum is 2 and maximum is 14. This value is also the window size
8478 used by the elevator sorting option above. The effective value used
8479 by the driver for each probed SCSI device is reported at boot time.
8481 Future Domain 16xx SCSI/AHA-2920A support
8482 CONFIG_SCSI_FUTURE_DOMAIN
8483 This is support for Future Domain's 16-bit SCSI host adapters
8484 (TMC-1660/1680, TMC-1650/1670, TMC-3260, TMC-1610M/MER/MEX) and
8485 other adapters based on the Future Domain chipsets (Quantum
8486 ISA-200S, ISA-250MG; Adaptec AHA-2920A; and at least one IBM board).
8487 It is explained in section 3.7 of the SCSI-HOWTO, available from
8488 <http://www.tldp.org/docs.html#howto>.
8490 NOTE: Newer Adaptec AHA-2920C boards use the Adaptec AIC-7850 chip
8491 and should use the aic7xxx driver ("Adaptec AIC7xxx chipset SCSI
8492 controller support"). This Future Domain driver works with the older
8493 Adaptec AHA-2920A boards with a Future Domain chip on them.
8495 This driver is also available as a module ( = code which can be
8496 inserted in and removed from the running kernel whenever you want).
8497 The module will be called fdomain.o. If you want to compile it as a
8498 module, say M here and read <file:Documentation/modules.txt>.
8500 Future Domain MCS-600/700 SCSI support
8502 This is support for Future Domain MCS 600/700 MCA SCSI adapters.
8503 Some PS/2 computers are equipped with IBM Fast SCSI Adapter/A which
8504 is identical to the MCS 700 and hence also supported by this driver.
8505 This driver also supports the Reply SB16/SCSI card (the SCSI part).
8506 It supports multiple adapters in the same system.
8508 This driver is also available as a module ( = code which can be
8509 inserted in and removed from the running kernel whenever you want).
8510 The module will be called fd_mcs.o. If you want to compile it as a
8511 module, say M here and read <file:Documentation/modules.txt>.
8513 Generic NCR5380/53c400 SCSI support
8514 CONFIG_SCSI_GENERIC_NCR5380
8515 This is the generic NCR family of SCSI controllers, not to be
8516 confused with the NCR 53c7 or 8xx controllers. It is explained in
8517 section 3.8 of the SCSI-HOWTO, available from
8518 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
8519 of the box, you may have to change some settings in
8520 <file:drivers/scsi/g_NCR5380.h>.
8522 This driver is also available as a module ( = code which can be
8523 inserted in and removed from the running kernel whenever you want).
8524 The module will be called g_NCR5380.o. If you want to compile it as
8525 a module, say M here and read <file:Documentation/modules.txt>.
8527 Enable NCR53c400 extensions
8528 CONFIG_SCSI_GENERIC_NCR53C400
8529 This enables certain optimizations for the NCR53c400 SCSI cards.
8530 You might as well try it out. Note that this driver will only probe
8531 for the Trantor T130B in its default configuration; you might have
8532 to pass a command line option to the kernel at boot time if it does
8533 not detect your card. See the file
8534 <file:drivers/scsi/README.g_NCR5380> for details.
8537 NCR5380/53c400 mapping method (use Port for T130B)
8538 CONFIG_SCSI_G_NCR5380_PORT
8539 The NCR5380 and NCR53c400 SCSI controllers come in two varieties:
8540 port or memory mapped. You should know what you have. The most
8541 common card, Trantor T130B, uses port mapped mode.
8543 NCR Dual 700 MCA SCSI support
8544 CONFIG_SCSI_NCR_D700
8545 This is a driver for the MicroChannel Dual 700 card produced by
8546 NCR and commonly used in 345x/35xx/4100 class machines. It always
8547 tries to negotiate sync and uses tag command queueing.
8549 Unless you have an NCR manufactured machine, the chances are that
8550 you do not have this SCSI card, so say N.
8552 If you want to compile the driver as a module ( = code which can be
8553 inserted in and removed from the running kernel whenever you want),
8554 say M here and read <file:Documentation/modules.txt>. The module
8555 will be called NCR_D700.o.
8557 HP LASI SCSI support for 53c700/710
8559 This is a driver for the lasi baseboard in some parisc machines
8560 which is based on the 53c700 chip. Will also support LASI subsystems
8561 based on the 710 chip using 700 emulation mode.
8563 Unless you know you have a 53c700 or 53c710 based lasi, say N here
8565 NCR53c7,8xx SCSI support
8566 CONFIG_SCSI_NCR53C7xx
8567 This is a driver for the 53c7 and 8xx NCR family of SCSI
8568 controllers, not to be confused with the NCR 5380 controllers. It
8569 is explained in section 3.8 of the SCSI-HOWTO, available from
8570 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
8571 of the box, you may have to change some settings in
8572 <file:drivers/scsi/53c7,8xx.h>. Please read
8573 <file:drivers/scsi/README.ncr53c7xx> for the available boot time
8574 command line options.
8576 Note: there is another driver for the 53c8xx family of controllers
8577 ("NCR53C8XX SCSI support" below). If you want to use them both, you
8578 need to say M to both and build them as modules, but only one may be
8579 active at a time. If you have a 53c8xx board, it's better to use the
8582 This driver is also available as a module ( = code which can be
8583 inserted in and removed from the running kernel whenever you want).
8584 The module will be called 53c7,8xx.o. If you want to compile it as
8585 a module, say M here and read <file:Documentation/modules.txt>.
8587 Always negotiate synchronous transfers
8588 CONFIG_SCSI_NCR53C7xx_sync
8589 In general, this is good; however, it is a bit dangerous since there
8590 are some broken SCSI devices out there. Take your chances. Safe bet
8593 Allow FAST-SCSI [10MHz]
8594 CONFIG_SCSI_NCR53C7xx_FAST
8595 This will enable 10MHz FAST-SCSI transfers with your host
8596 adapter. Some systems have problems with that speed, so it's safest
8600 CONFIG_SCSI_NCR53C7xx_DISCONNECT
8601 This enables the disconnect/reconnect feature of the NCR SCSI
8602 controller. When you say Y here, a slow SCSI device will not lock
8603 the SCSI bus while processing a request, allowing simultaneous use
8604 of e.g. a SCSI hard disk and SCSI tape or CD-ROM drive, and
8605 providing much better performance when using slow and fast SCSI
8606 devices at the same time. Some devices, however, do not operate
8607 properly with this option enabled, and will cause your SCSI system
8608 to hang, which might cause a system crash. The safe answer
8609 therefore is to say N.
8611 SYM53C8XX Version 2 SCSI support
8612 CONFIG_SCSI_SYM53C8XX_2
8613 This driver supports the whole NCR53C8XX/SYM53C8XX family of
8614 PCI-SCSI controllers. It also supports the subset of LSI53C10XX
8615 Ultra-160 controllers that are based on the SYM53C8XX SCRIPTS
8616 language. It does not support LSI53C10XX Ultra-320 PCI-X SCSI
8619 If your system has problems using this new major version of the
8620 SYM53C8XX driver, you may switch back to driver version 1.
8622 Please read <file:drivers/scsi/sym53c8xx_2/Documentation.txt> for more
8625 If you want to compile the driver as a module ( = code which can be
8626 inserted in and removed from the running kernel whenever you want),
8627 say M here and read <file:Documentation/modules.txt>. The module
8628 will be called sym53c8xx_2.o.
8630 PCI DMA addressing mode
8631 CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE
8632 This option only applies to PCI-SCSI chip that are PCI DAC capable
8633 (875A, 895A, 896, 1010-33, 1010-66, 1000).
8635 When set to 0, only PCI 32 bit DMA addressing (SAC) will be performed.
8636 When set to 1, 40 bit DMA addressing (with upper 24 bits of address
8637 set to zero) is supported. The addressable range is here 1 TB.
8638 When set to 2, full 64 bits of address for DMA are supported, but only
8639 16 segments of 4 GB can be addressed. The addressable range is so
8642 The safest value is 0 (32 bit DMA addressing) that is guessed to still
8643 fit most of real machines.
8645 The preferred value 1 (40 bit DMA addressing) should make happy
8646 properly engineered PCI DAC capable host bridges. You may configure
8647 this option for Intel platforms with more than 4 GB of memory.
8649 The still experimental value 2 (64 bit DMA addressing with 16 x 4GB
8650 segments limitation) can be used on systems that require PCI address
8651 bits past bit 39 to be set for the addressing of memory using PCI
8655 CONFIG_SCSI_SYM53C8XX_IOMAPPED
8656 If you say Y here, the driver will preferently use normal IO rather than
8659 maximum number of queued commands
8660 CONFIG_SCSI_SYM53C8XX_MAX_TAGS
8661 This option allows you to specify the maximum number of commands
8662 that can be queued to any device, when tagged command queuing is
8663 possible. The driver supports up to 256 queued commands per device.
8664 This value is used as a compiled-in hard limit.
8666 default tagged command queue depth
8667 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS
8668 This is the default value of the command queue depth the driver will
8669 announce to the generic SCSI layer for devices that support tagged
8670 command queueing. This value can be changed from the boot command line.
8671 This is a soft limit that cannot exceed CONFIG_SCSI_SYM53C8XX_MAX_TAGS.
8673 NCR53C8XX SCSI support
8674 CONFIG_SCSI_NCR53C8XX
8675 This is the BSD ncr driver adapted to Linux for the NCR53C8XX family
8676 of PCI-SCSI controllers. This driver supports parity checking,
8677 tagged command queuing and fast synchronous data transfers up to 80
8678 MB/s with wide FAST-40 LVD devices and controllers.
8680 Recent versions of the 53C8XX chips are better supported by the
8681 option "SYM53C8XX SCSI support", below.
8683 Note: there is yet another driver for the 53c8xx family of
8684 controllers ("NCR53c7,8xx SCSI support" above). If you want to use
8685 them both, you need to say M to both and build them as modules, but
8686 only one may be active at a time. If you have a 53c8xx board, you
8687 probably do not want to use the "NCR53c7,8xx SCSI support".
8689 Please read <file:drivers/scsi/README.ncr53c8xx> for more
8692 If you want to compile the driver as a module ( = code which can be
8693 inserted in and removed from the running kernel whenever you want),
8694 say M here and read <file:Documentation/modules.txt>. The module
8695 will be called ncr53c8xx.o.
8697 SYM53C8XX Version 1 SCSI support
8698 CONFIG_SCSI_SYM53C8XX
8699 This driver supports all the features of recent 53C8XX chips (used
8700 in PCI SCSI controllers), notably the hardware phase mismatch
8701 feature of the SYM53C896.
8703 Older versions of the 53C8XX chips are not supported by this
8704 driver. If your system uses either a 810 rev. < 16, a 815, or a 825
8705 rev. < 16 PCI SCSI processor, you must use the generic NCR53C8XX
8706 driver ("NCR53C8XX SCSI support" above) or configure both the
8707 NCR53C8XX and this SYM53C8XX drivers either as module or linked to
8710 When both drivers are linked into the kernel, the SYM53C8XX driver
8711 is called first at initialization and you can use the 'excl=ioaddr'
8712 driver boot option to exclude attachment of adapters by the
8713 SYM53C8XX driver. For example, entering
8714 'sym53c8xx=excl:0xb400,excl=0xc000' at the lilo prompt prevents
8715 adapters at io address 0xb400 and 0xc000 from being attached by the
8716 SYM53C8XX driver, thus allowing the NCR53C8XX driver to attach them.
8717 The 'excl' option is also supported by the NCR53C8XX driver.
8719 Please read <file:drivers/scsi/README.ncr53c8xx> for more
8722 If you want to compile the driver as a module ( = code which can be
8723 inserted in and removed from the running kernel whenever you want),
8724 say M here and read <file:Documentation/modules.txt>. The module
8725 will be called sym53c8xx.o.
8727 Synchronous transfer frequency in MHz
8728 CONFIG_SCSI_NCR53C8XX_SYNC
8729 The SCSI Parallel Interface-2 Standard defines 5 classes of transfer
8730 rates: FAST-5, FAST-10, FAST-20, FAST-40 and FAST-80. The numbers
8731 are respectively the maximum data transfer rates in mega-transfers
8732 per second for each class. For example, a FAST-20 Wide 16 device is
8733 able to transfer data at 20 million 16 bit packets per second for a
8734 total rate of 40 MB/s.
8736 You may specify 0 if you want to only use asynchronous data
8737 transfers. This is the safest and slowest option. Otherwise, specify
8738 a value between 5 and 80, depending on the capability of your SCSI
8739 controller. The higher the number, the faster the data transfer.
8740 Note that 80 should normally be ok since the driver decreases the
8741 value automatically according to the controller's capabilities.
8743 Your answer to this question is ignored for controllers with NVRAM,
8744 since the driver will get this information from the user set-up. It
8745 also can be overridden using a boot setup option, as follows
8746 (example): 'ncr53c8xx=sync:12' will allow the driver to negotiate
8747 for FAST-20 synchronous data transfer (20 mega-transfers per
8750 The normal answer therefore is not to go with the default but to
8751 select the maximum value 80 allowing the driver to use the maximum
8752 value supported by each controller. If this causes problems with
8753 your SCSI devices, you should come back and decrease the value.
8755 There is no safe option other than using good cabling, right
8756 terminations and SCSI conformant devices.
8759 CONFIG_SCSI_NCR53C8XX_IOMAPPED
8760 If you say Y here, the driver will use normal IO, as opposed to
8761 memory mapped IO. Memory mapped IO has less latency than normal IO
8762 and works for most Intel-based hardware. Under Linux/Alpha only
8763 normal IO is currently supported by the driver and so, this option
8764 has no effect on those systems.
8766 The normal answer therefore is N; try Y only if you encounter SCSI
8769 Not allow targets to disconnect
8770 CONFIG_SCSI_NCR53C8XX_NO_DISCONNECT
8771 This option is only provided for safety if you suspect some SCSI
8772 device of yours to not support properly the target-disconnect
8773 feature. In that case, you would say Y here. In general however, to
8774 not allow targets to disconnect is not reasonable if there is more
8775 than 1 device on a SCSI bus. The normal answer therefore is N.
8777 Default tagged command queue depth
8778 CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS
8779 "Tagged command queuing" is a feature of SCSI-2 which improves
8780 performance: the host adapter can send several SCSI commands to a
8781 device's queue even if previous commands haven't finished yet.
8782 Because the device is intelligent, it can optimize its operations
8783 (like head positioning) based on its own request queue. Some SCSI
8784 devices don't implement this properly; if you want to disable this
8785 feature, enter 0 or 1 here (it doesn't matter which).
8787 The default value is 8 and should be supported by most hard disks.
8788 This value can be overridden from the boot command line using the
8789 'tags' option as follows (example):
8790 'ncr53c8xx=tags:4/t2t3q16/t0u2q10' will set default queue depth to
8791 4, set queue depth to 16 for target 2 and target 3 on controller 0
8792 and set queue depth to 10 for target 0 / lun 2 on controller 1.
8794 The normal answer therefore is to go with the default 8 and to use
8795 a boot command line option for devices that need to use a different
8796 command queue depth.
8798 There is no safe option other than using good SCSI devices.
8800 Maximum number of queued commands
8801 CONFIG_SCSI_NCR53C8XX_MAX_TAGS
8802 This option allows you to specify the maximum number of commands
8803 that can be queued to any device, when tagged command queuing is
8804 possible. The default value is 32. Minimum is 2, maximum is 64.
8805 Modern hard disks are able to support 64 tags and even more, but
8806 do not seem to be faster when more than 32 tags are being used.
8808 So, the normal answer here is to go with the default value 32 unless
8809 you are using very large hard disks with large cache (>= 1 MB) that
8810 are able to take advantage of more than 32 tagged commands.
8812 There is no safe option and the default answer is recommended.
8814 Assume boards are SYMBIOS compatible
8815 CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT
8816 This option allows you to enable some features depending on GPIO
8817 wiring. These General Purpose Input/Output pins can be used for
8818 vendor specific features or implementation of the standard SYMBIOS
8819 features. Genuine SYMBIOS controllers use GPIO0 in output for
8820 controller LED and GPIO3 bit as a flag indicating
8821 singled-ended/differential interface. The Tekram DC-390U/F boards
8822 uses a different GPIO wiring.
8824 Your answer to this question is ignored if all your controllers have
8825 NVRAM, since the driver is able to detect the board type from the
8828 If all the controllers in your system are genuine SYMBIOS boards or
8829 use BIOS and drivers from SYMBIOS, you would want to say Y here,
8830 otherwise N. N is the safe answer.
8832 Enable traffic profiling
8833 CONFIG_SCSI_NCR53C8XX_PROFILE
8834 This option allows you to enable profiling information gathering.
8835 These statistics are not very accurate due to the low frequency
8836 of the kernel clock (100 Hz on i386) and have performance impact
8837 on systems that use very fast devices.
8839 The normal answer therefore is N.
8841 Include support for the NCR PQS/PDS SCSI card
8842 CONFIG_SCSI_NCR53C8XX_PQS_PDS
8843 Say Y here if you have a special SCSI adapter produced by NCR
8844 corporation called a PCI Quad SCSI or PCI Dual SCSI. You do not need
8845 this if you do not have one of these adapters. However, since this
8846 device is detected as a specific PCI device, this option is quite
8849 The common answer here is N, but answering Y is safe.
8851 Workbit NinjaSCSI-32Bi/UDE support
8853 This is support for the Workbit NinjaSCSI-32Bi/UDE PCI/Cardbus
8854 SCSI host adapter. Please read the SCSI-HOWTO, available from
8855 <http://www.linuxdoc.org/docs.html#howto>.
8857 If you want to compile this as a module ( = code which can be
8858 inserted in and removed from the running kernel whenever you want),
8859 say M here and read <file:Documentation/modules.txt>. The module
8860 will be called nsp32.o.
8864 This is support for the IBM SCSI adapter found in many of the PS/2
8865 series computers. These machines have an MCA bus, so you need to
8866 answer Y to "MCA support" as well and read
8867 <file:Documentation/mca.txt>.
8869 If the adapter isn't found during boot (a common problem for models
8870 56, 57, 76, and 77) you'll need to use the 'ibmmcascsi=<pun>' kernel
8871 option, where <pun> is the id of the SCSI subsystem (usually 7, but
8872 if that doesn't work check your reference diskette). Owners of
8873 model 95 with a LED-matrix-display can in addition activate some
8874 activity info like under OS/2, but more informative, by setting
8875 'ibmmcascsi=display' as an additional kernel parameter. Try "man
8876 bootparam" or see the documentation of your boot loader about how to
8877 pass options to the kernel.
8879 If you want to compile this driver as a module ( = code which can be
8880 inserted in and removed from the running kernel whenever you want),
8881 say M here and read <file:Documentation/modules.txt>. The module
8882 will be called ibmmca.o.
8885 CONFIG_IBMMCA_SCSI_ORDER_STANDARD
8886 In the PC-world and in most modern SCSI-BIOS-setups, SCSI-hard disks
8887 are assigned to the drive letters, starting with the lowest SCSI-id
8888 (physical number -- pun) to be drive C:, as seen from DOS and
8889 similar operating systems. When looking into papers describing the
8890 ANSI-SCSI-standard, this assignment of drives appears to be wrong.
8891 The SCSI-standard follows a hardware-hierarchy which says that id 7
8892 has the highest priority and id 0 the lowest. Therefore, the host
8893 adapters are still today everywhere placed as SCSI-id 7 by default.
8894 In the SCSI-standard, the drive letters express the priority of the
8895 disk. C: should be the hard disk, or a partition on it, with the
8896 highest priority. This must therefore be the disk with the highest
8897 SCSI-id (e.g. 6) and not the one with the lowest! IBM-BIOS kept the
8898 original definition of the SCSI-standard as also industrial- and
8899 process-control-machines, like VME-CPUs running under realtime-OSes
8900 (e.g. LynxOS, OS9) do.
8902 If you like to run Linux on your MCA-machine with the same
8903 assignment of hard disks as seen from e.g. DOS or OS/2 on your
8904 machine, which is in addition conformant to the SCSI-standard, you
8905 must say Y here. This is also necessary for MCA-Linux users who want
8906 to keep downward compatibility to older releases of the
8907 IBM-MCA-SCSI-driver (older than driver-release 2.00 and older than
8910 If you like to have the lowest SCSI-id assigned as drive C:, as
8911 modern SCSI-BIOSes do, which does not conform to the standard, but
8912 is widespread and common in the PC-world of today, you must say N
8913 here. If unsure, say Y.
8915 Reset SCSI-devices at boot time
8916 CONFIG_IBMMCA_SCSI_DEV_RESET
8917 By default, SCSI-devices are reset when the machine is powered on.
8918 However, some devices exist, like special-control-devices,
8919 SCSI-CNC-machines, SCSI-printer or scanners of older type, that do
8920 not reset when switched on. If you say Y here, each device connected
8921 to your SCSI-bus will be issued a reset-command after it has been
8922 probed, while the kernel is booting. This may cause problems with
8923 more modern devices, like hard disks, which do not appreciate these
8924 reset commands, and can cause your system to hang. So say Y only if
8925 you know that one of your older devices needs it; N is the safe
8928 NCR MCA 53C9x SCSI support
8929 CONFIG_SCSI_MCA_53C9X
8930 Some MicroChannel machines, notably the NCR 35xx line, use a SCSI
8931 controller based on the NCR 53C94. This driver will allow use of
8932 the controller on the 3550, and very possibly others.
8934 If you want to compile this as a module (= code which can be
8935 inserted and removed from the running kernel whenever you want), say
8936 M here and read <file:Documentation/modules.txt>. The module will
8937 be called mca_53c9x.o.
8939 Always IN2000 SCSI support
8941 This is support for an ISA bus SCSI host adapter. You'll find more
8942 information in <file:drivers/scsi/README.in2000>. If it doesn't work
8943 out of the box, you may have to change the jumpers for IRQ or
8946 If you want to compile this as a module ( = code which can be
8947 inserted in and removed from the running kernel whenever you want),
8948 say M here and read <file:Documentation/modules.txt>. The module
8949 will be called in2000.o.
8951 Initio 91XXU(W) SCSI support
8953 This is support for the Initio 91XXU(W) SCSI host adapter. Please
8954 read the SCSI-HOWTO, available from
8955 <http://www.tldp.org/docs.html#howto>.
8957 If you want to compile this as a module ( = code which can be
8958 inserted in and removed from the running kernel whenever you want),
8959 say M here and read <file:Documentation/modules.txt>. The module
8960 will be called initio.o.
8964 This is support for a SCSI host adapter. It is explained in section
8965 3.10 of the SCSI-HOWTO, available from
8966 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
8967 of the box, you may have to change some settings in
8968 <file:drivers/scsi/pas16.h>.
8970 This driver 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 pas16.o. If you want to compile it as a
8973 module, say M here and read <file:Documentation/modules.txt>.
8975 Initio INI-A100U2W SCSI support
8977 This is support for the Initio INI-A100U2W SCSI host adapter.
8978 Please read the SCSI-HOWTO, available from
8979 <http://www.tldp.org/docs.html#howto>.
8981 If you want to compile this as a module ( = code which can be
8982 inserted in and removed from the running kernel whenever you want),
8983 say M here and read <file:Documentation/modules.txt>. The module
8984 will be called a100u2w.o.
8988 This is support for the PCI2000I EIDE interface card which acts as a
8989 SCSI host adapter. Please read the SCSI-HOWTO, available from
8990 <http://www.tldp.org/docs.html#howto>.
8992 This driver is also available as a module called pci2000.o ( = code
8993 which can be inserted in and removed from the running kernel
8994 whenever you want). If you want to compile it as a module, say M
8995 here and read <file:Documentation/modules.txt>.
8998 CONFIG_SCSI_PCI2220I
8999 This is support for the PCI2220i EIDE interface card which acts as a
9000 SCSI host adapter. Please read the SCSI-HOWTO, available from
9001 <http://www.tldp.org/docs.html#howto>.
9003 This driver is also available as a module called pci2220i.o ( = code
9004 which can be inserted in and removed from the running kernel
9005 whenever you want). If you want to compile it as a module, say M
9006 here and read <file:Documentation/modules.txt>.
9010 This is support for the PSI240i EIDE interface card which acts as a
9011 SCSI host adapter. Please read the SCSI-HOWTO, available from
9012 <http://www.tldp.org/docs.html#howto>.
9014 This driver is also available as a module called psi240i.o ( = code
9015 which can be inserted in and removed from the running kernel
9016 whenever you want). If you want to compile it as a module, say M
9017 here and read <file:Documentation/modules.txt>.
9019 Qlogic FAS SCSI support
9020 CONFIG_SCSI_QLOGIC_FAS
9021 This is a driver for the ISA, VLB, and PCMCIA versions of the Qlogic
9022 FastSCSI! cards as well as any other card based on the FASXX chip
9023 (including the Control Concepts SCSI/IDE/SIO/PIO/FDC cards).
9025 This driver does NOT support the PCI versions of these cards. The
9026 PCI versions are supported by the Qlogic ISP driver ("Qlogic ISP
9027 SCSI support"), below.
9029 Information about this driver is contained in
9030 <file:drivers/scsi/README.qlogicfas>. You should also read the
9031 SCSI-HOWTO, available from
9032 <http://www.tldp.org/docs.html#howto>.
9034 This driver is also available as a module ( = code which can be
9035 inserted in and removed from the running kernel whenever you want).
9036 The module will be called qlogicfas.o. If you want to compile it as
9037 a module, say M here and read <file:Documentation/modules.txt>.
9039 Qlogic ISP SCSI support
9040 CONFIG_SCSI_QLOGIC_ISP
9041 This driver works for all QLogic PCI SCSI host adapters (IQ-PCI,
9042 IQ-PCI-10, IQ_PCI-D) except for the PCI-basic card. (This latter
9043 card is supported by the "AM53/79C974 PCI SCSI" driver.)
9045 If you say Y here, make sure to choose "BIOS" at the question "PCI
9048 Please read the file <file:drivers/scsi/README.qlogicisp>. You
9049 should also read the SCSI-HOWTO, available from
9050 <http://www.tldp.org/docs.html#howto>.
9052 This driver is also available as a module ( = code which can be
9053 inserted in and removed from the running kernel whenever you want).
9054 The module will be called qlogicisp.o. If you want to compile it as
9055 a module, say M here and read <file:Documentation/modules.txt>.
9057 Qlogic ISP FC SCSI support
9058 CONFIG_SCSI_QLOGIC_FC
9059 This is a driver for the QLogic ISP2100 SCSI-FCP host adapter.
9061 This driver is also available as a module ( = code which can be
9062 inserted in and removed from the running kernel whenever you want).
9063 The module will be called qlogicfc.o. If you want to compile it as
9064 a module, say M here and read <file:Documentation/modules.txt>.
9066 Include loadable firmware in driver
9067 CONFIG_SCSI_QLOGIC_FC_FIRMWARE
9068 Say Y to include ISP2100 Fabric Initiator/Target Firmware, with
9069 expanded LUN addressing and FcTape (FCP-2) support, in the
9070 Qlogic QLA 1280 driver. This is required on some platforms.
9072 Qlogic QLA 1280 SCSI support
9073 CONFIG_SCSI_QLOGIC_1280
9074 Say Y if you have a QLogic ISP1x80/1x160 SCSI host adapter.
9076 This driver is also available as a module ( = code which can be
9077 inserted in and removed from the running kernel whenever you want).
9078 The module will be called qla1280.o. If you want to compile it as
9079 a module, say M here and read <file:Documentation/modules.txt>.
9081 Seagate ST-02 and Future Domain TMC-8xx SCSI support
9083 These are 8-bit SCSI controllers; the ST-01 is also supported by
9084 this driver. It is explained in section 3.9 of the SCSI-HOWTO,
9085 available from <http://www.tldp.org/docs.html#howto>. If it
9086 doesn't work out of the box, you may have to change some settings in
9087 <file:drivers/scsi/seagate.h>.
9089 This driver is also available as a module ( = code which can be
9090 inserted in and removed from the running kernel whenever you want).
9091 The module will be called seagate.o. If you want to compile it as a
9092 module, say M here and read <file:Documentation/modules.txt>.
9094 Trantor T128/T128F/T228 SCSI support
9096 This is support for a SCSI host adapter. It is explained in section
9097 3.11 of the SCSI-HOWTO, available from
9098 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
9099 of the box, you may have to change some settings in
9100 <file:drivers/scsi/t128.h>. Note that Trantor was purchased by
9101 Adaptec, and some former Trantor products are being sold under the
9104 This driver is also available as a module ( = code which can be
9105 inserted in and removed from the running kernel whenever you want).
9106 The module will be called t128.o. If you want to compile it as a
9107 module, say M here and read <file:Documentation/modules.txt>.
9109 UltraStor SCSI support
9110 CONFIG_SCSI_ULTRASTOR
9111 This is support for the UltraStor 14F, 24F and 34F SCSI-2 host
9112 adapter family. This driver is explained in section 3.12 of the
9113 SCSI-HOWTO, available from
9114 <http://www.tldp.org/docs.html#howto>. If it doesn't work out
9115 of the box, you may have to change some settings in
9116 <file:drivers/scsi/ultrastor.h>.
9118 Note that there is also another driver for the same hardware:
9119 "UltraStor 14F/34F support", above.
9121 If you want to compile this as a module ( = code which can be
9122 inserted in and removed from the running kernel whenever you want),
9123 say M here and read <file:Documentation/modules.txt>. The module
9124 will be called ultrastor.o.
9126 7000FASST SCSI support
9127 CONFIG_SCSI_7000FASST
9128 This driver supports the Western Digital 7000 SCSI host adapter
9129 family. Some information is in the source:
9130 <file:drivers/scsi/wd7000.c>.
9132 This driver is also available as a module ( = code which can be
9133 inserted in and removed from the running kernel whenever you want).
9134 The module will be called wd7000.o. If you want to compile it as a
9135 module, say M here and read <file:Documentation/modules.txt>.
9139 This driver supports the ACARD 870U/W SCSI host adapter.
9141 This driver is also available as a module ( = code which can be
9142 inserted in and removed from the running kernel whenever you want).
9143 The module will be called atp870u.o. If you want to compile it as a
9144 module, say M here and read <file:Documentation/modules.txt>.
9146 EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards) support
9148 This driver supports all EATA/DMA-compliant SCSI host adapters. DPT
9149 ISA and all EISA I/O addresses are probed looking for the "EATA"
9150 signature. If you chose "BIOS" at the question "PCI access mode",
9151 the addresses of all the PCI SCSI controllers reported by the PCI
9152 subsystem are probed as well.
9154 You want to read the start of <file:drivers/scsi/eata.c> and the
9155 SCSI-HOWTO, available from
9156 <http://www.tldp.org/docs.html#howto>.
9158 Note that there is also another driver for the same hardware
9159 available: "EATA-DMA [Obsolete] (DPT, NEC, AT&T, SNI, AST, Olivetti,
9160 Alphatronix) support". You should say Y to only one of them.
9162 If you want to compile this as a module ( = code which can be
9163 inserted in and removed from the running kernel whenever you want),
9164 say M here and read <file:Documentation/modules.txt>. The module
9165 will be called eata.o.
9167 enable tagged command queueing
9168 CONFIG_SCSI_EATA_TAGGED_QUEUE
9169 This is a feature of SCSI-2 which improves performance: the host
9170 adapter can send several SCSI commands to a device's queue even if
9171 previous commands haven't finished yet. Most EATA adapters negotiate
9172 this feature automatically with the device, even if your answer is
9173 N. The safe answer is N.
9175 enable elevator sorting
9176 CONFIG_SCSI_EATA_LINKED_COMMANDS
9177 This option enables elevator sorting for all probed SCSI disks and
9178 CD-ROMs. It definitely reduces the average seek distance when doing
9179 random seeks, but this does not necessarily result in a noticeable
9180 performance improvement: your mileage may vary...
9181 The safe answer is N.
9183 maximum number of queued commands
9184 CONFIG_SCSI_EATA_MAX_TAGS
9185 This specifies how many SCSI commands can be maximally queued for
9186 each probed SCSI device. You should reduce the default value of 16
9187 only if you have disks with buggy or limited tagged command support.
9188 Minimum is 2 and maximum is 62. This value is also the window size
9189 used by the elevator sorting option above. The effective value used
9190 by the driver for each probed SCSI device is reported at boot time.
9192 NCR53c406a SCSI support
9193 CONFIG_SCSI_NCR53C406A
9194 This is support for the NCR53c406a SCSI host adapter. For user
9195 configurable parameters, check out <file:drivers/scsi/NCR53c406a.c>
9196 in the kernel source. Also read the SCSI-HOWTO, available from
9197 <http://www.tldp.org/docs.html#howto>.
9199 If you want to compile this driver as a module ( = code which can be
9200 inserted in and removed from the running kernel whenever you want),
9201 say M here and read <file:Documentation/modules.txt>. The module
9202 will be called NCR53c406.o.
9204 Symbios 53c416 SCSI support
9205 CONFIG_SCSI_SYM53C416
9206 This is support for the sym53c416 SCSI host adapter, the SCSI
9207 adapter that comes with some HP scanners. This driver requires that
9208 the sym53c416 is configured first using some sort of PnP
9209 configuration program (e.g. isapnp) or by a PnP aware BIOS. If you
9210 are using isapnp then you need to compile this driver as a module
9211 and then load it using insmod after isapnp has run. The parameters
9212 of the configured card(s) should be passed to the driver. The format
9215 insmod sym53c416 sym53c416=<base>,<irq> [sym53c416_1=<base>,<irq>]
9217 There is support for up to four adapters. If you want to compile
9218 this driver as a module ( = code which can be inserted in and
9219 removed from the running kernel whenever you want), say M here and
9220 read <file:Documentation/modules.txt>. The module will be called
9223 Simple 53c710 SCSI support (Compaq, NCR machines)
9225 This is a simple driver for NCR53c710 based SCSI host adapters.
9227 More complex drivers for this chip are available ("NCR53c7,8xx SCSI
9228 support", above), but they require that the scsi chip be able to do
9229 DMA block moves between memory and on-chip registers, which can
9230 cause problems under certain conditions. This driver is designed to
9231 avoid these problems and is intended to work with any Intel machines
9232 using 53c710 chips, including various Compaq and NCR machines.
9234 Please read the comments at the top of the file
9235 <file:drivers/scsi/sim710.c> for more information.
9237 If you want to compile this driver as a module ( = code which can be
9238 inserted in and removed from the running kernel whenever you want),
9239 say M here and read <file:Documentation/modules.txt>. The module
9240 will be called sim710.o.
9242 Tekram DC390(T) and Am53/79C974 SCSI support
9244 This driver supports PCI SCSI host adapters based on the Am53C974A
9245 chip, e.g. Tekram DC390(T), DawiControl 2974 and some onboard
9246 PCscsi/PCnet (Am53/79C974) solutions.
9248 Documentation can be found in <file:drivers/scsi/README.tmscsim>.
9250 Note that this driver does NOT support Tekram DC390W/U/F, which are
9251 based on NCR/Symbios chips. Use "NCR53C8XX SCSI support" for those.
9252 Also note that there is another generic Am53C974 driver,
9253 "AM53/79C974 PCI SCSI support" below. You can pick either one.
9255 If you want to compile this driver as a module ( = code which can be
9256 inserted in and removed from the running kernel whenever you want),
9257 say M here and read <file:Documentation/modules.txt>. The module
9258 will be called tmscsim.o.
9260 Omit support for other Am53/79C974 based SCSI adapters
9261 CONFIG_SCSI_DC390T_NOGENSUPP
9262 If you say N here, the DC390(T) SCSI driver relies on the DC390
9263 EEPROM to get initial values for its settings, such as speed,
9264 termination, etc. If it can't find this EEPROM, it will use
9265 defaults or the user supplied boot/module parameters. For details
9266 on driver configuration see <file:drivers/scsi/README.tmscsim>.
9268 If you say Y here and if no EEPROM is found, the driver gives up and
9269 thus only supports Tekram DC390(T) adapters. This can be useful if
9270 you have a DC390(T) and another Am53C974 based adapter, which, for
9271 some reason, you want to drive with the other AM53C974 driver.
9275 AM53/79C974 PCI SCSI support
9276 CONFIG_SCSI_AM53C974
9277 This is support for the AM53/79C974 SCSI host adapters. Please read
9278 <file:drivers/scsi/README.AM53C974> for details. Also, the
9279 SCSI-HOWTO, available from
9280 <http://www.tldp.org/docs.html#howto>, is for you.
9282 Note that there is another driver for AM53C974 based adapters:
9283 "Tekram DC390(T) and Am53/79C974 (PCscsi) SCSI support", above. You
9284 can pick either one.
9286 If you want to compile this driver as a module ( = code which can be
9287 inserted in and removed from the running kernel whenever you want),
9288 say M here and read <file:Documentation/modules.txt>. The module
9289 will be called AM53C974.o.
9291 AMI MegaRAID support (old driver)
9292 CONFIG_SCSI_MEGARAID
9293 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490,
9294 467, 471 and 493 SCSI host adapters.
9296 This is the old and very heavily tested driver but lacks features
9299 If you want to compile this driver as a module ( = code which can be
9300 inserted in and removed from the running kernel whenever you want),
9301 say M here and read <file:Documentation/modules.txt>. The module
9302 will be called megaraid.o.
9304 AMI MegaRAID support (new driver)
9305 CONFIG_SCSI_MEGARAID2
9306 This driver supports the AMI MegaRAID 418, 428, 438, 466, 762, 490,
9307 467, 471, 493 and new Ultra320(518, 520, 531, 532) SCSI host adapters.
9309 This is the newer less tested but more featureful driver.
9311 If you want to compile this driver as a module ( = code which can be
9312 inserted in and removed from the running kernel whenever you want),
9313 say M here and read <file:Documentation/modules.txt>. The module
9314 will be called megaraid2.o.
9317 This driver family supports Serial ATA host controllers
9322 CONFIG_SCSI_SATA_AHCI
9323 This option enables support for AHCI Serial ATA.
9327 CONFIG_SCSI_SATA_SVW
9328 This option enables support for Broadcom/Serverworks/Apple K2
9333 CONFIG_SCSI_ATA_PIIX
9334 This option enables support for ICH5 Serial ATA.
9339 This option enables support for NVIDIA Serial ATA.
9343 CONFIG_SCSI_SATA_PROMISE
9344 This option enables support for Promise Serial ATA TX2/TX4.
9348 CONFIG_SCSI_SATA_QSTOR
9349 This option enables support for Pacific Digital Serial ATA QStor.
9353 CONFIG_SCSI_SATA_SX4
9354 This option enables support for Promise Serial ATA SX4.
9358 CONFIG_SCSI_SATA_SIL
9359 This option enables support for Silicon Image Serial ATA.
9363 CONFIG_SCSI_SATA_SIS
9364 This option enables support for SiS Serial ATA 964/180.
9368 CONFIG_SCSI_SATA_ULI
9369 This option enables support for ULi Electronics SATA.
9373 CONFIG_SCSI_SATA_VIA
9374 This option enables support for VIA Serial ATA.
9378 CONFIG_SCSI_SATA_VITESSE
9379 This option enables support for Vitesse VSC7174 Serial ATA.
9383 Intel/ICP (former GDT SCSI Disk Array) RAID Controller support
9385 Formerly called GDT SCSI Disk Array Controller Support.
9387 This is a driver for RAID/SCSI Disk Array Controllers (EISA/ISA/PCI)
9388 manufactured by Intel/ICP vortex (an Intel Company). It is documented
9389 in the kernel source in <file:drivers/scsi/gdth.c> and
9390 <file:drivers/scsi/gdth.h.>
9392 If you want to compile the driver as a module ( = code which can be
9393 inserted in and removed from the running kernel whenever you want),
9394 say M here and read <file:Documentation/modules.txt>. The module
9395 will be called gdth.o.
9397 IOMEGA parallel port (ppa - older drives)
9399 This driver supports older versions of IOMEGA's parallel port ZIP
9400 drive (a 100 MB removable media device).
9402 Note that you can say N here if you have the SCSI version of the ZIP
9403 drive: it will be supported automatically if you said Y to the
9404 generic "SCSI disk support", above.
9406 If you have the ZIP Plus drive or a more recent parallel port ZIP
9407 drive (if the supplied cable with the drive is labeled "AutoDetect")
9408 then you should say N here and Y to "IOMEGA parallel port (imm -
9409 newer drives)", below.
9411 For more information about this driver and how to use it you should
9412 read the file <file:drivers/scsi/README.ppa>. You should also read
9413 the SCSI-HOWTO, which is available from
9414 <http://www.tldp.org/docs.html#howto>. If you use this driver,
9415 you will still be able to use the parallel port for other tasks,
9416 such as a printer; it is safe to compile both drivers into the
9419 This driver is also available as a module which can be inserted in
9420 and removed from the running kernel whenever you want. To compile
9421 this driver as a module, say M here and read
9422 <file:Documentation/modules.txt>. The module will be called ppa.o.
9424 IOMEGA parallel port (imm - newer drives)
9426 This driver supports newer versions of IOMEGA's parallel port ZIP
9427 drive (a 100 MB removable media device).
9429 Note that you can say N here if you have the SCSI version of the ZIP
9430 drive: it will be supported automatically if you said Y to the
9431 generic "SCSI disk support", above.
9433 If you have the ZIP Plus drive or a more recent parallel port ZIP
9434 drive (if the supplied cable with the drive is labeled "AutoDetect")
9435 then you should say Y here; if you have an older ZIP drive, say N
9436 here and Y to "IOMEGA Parallel Port (ppa - older drives)", above.
9438 For more information about this driver and how to use it you should
9439 read the file <file:drivers/scsi/README.ppa>. You should also read
9440 the SCSI-HOWTO, which is available from
9441 <http://www.tldp.org/docs.html#howto>. If you use this driver,
9442 you will still be able to use the parallel port for other tasks,
9443 such as a printer; it is safe to compile both drivers into the
9446 This driver is also available as a module which can be inserted in
9447 and removed from the running kernel whenever you want. To compile
9448 this driver as a module, say M here and read
9449 <file:Documentation/modules.txt>. The module will be called imm.o.
9451 Force the Iomega ZIP drivers to use EPP-16
9452 CONFIG_SCSI_IZIP_EPP16
9453 EPP (Enhanced Parallel Port) is a standard for parallel ports which
9454 allows them to act as expansion buses that can handle up to 64
9457 Some parallel port chipsets are slower than their motherboard, and
9458 so we have to control the state of the chipset's FIFO queue every
9459 now and then to avoid data loss. This will be done if you say Y
9462 Generally, saying Y is the safe option and slows things down a bit.
9464 Assume slow parallel port control register
9465 CONFIG_SCSI_IZIP_SLOW_CTR
9466 Some parallel ports are known to have excessive delays between
9467 changing the parallel port control register and good data being
9468 available on the parallel port data/status register. This option
9469 forces a small delay (1.0 usec to be exact) after changing the
9470 control register to let things settle out. Enabling this option may
9471 result in a big drop in performance but some very old parallel ports
9472 (found in 386 vintage machines) will not work properly.
9474 Generally, saying N is fine.
9476 SCSI debugging host simulator
9478 This is a host adapter simulator that can be programmed to simulate
9479 a large number of conditions that could occur on a real bus. The
9480 advantage is that many hard to reproduce problems can be tested in a
9481 controlled environment where there is reduced risk of losing
9482 important data. This is primarily of use to people trying to debug
9483 the middle and upper layers of the SCSI subsystem. If unsure, say N.
9485 If you want to compile the driver as a module ( = code which can be
9486 inserted in and removed from the running kernel whenever you want),
9487 say M here and read <file:Documentation/modules.txt>. The module
9488 will be called scsi_debug.o.
9490 Fibre Channel and FC4 SCSI support
9492 Fibre Channel is a high speed serial protocol mainly used to
9493 connect large storage devices to the computer; it is compatible with
9494 and intended to replace SCSI.
9496 This is an experimental support for storage arrays connected to your
9497 computer using optical fibre cables and the "X3.269-199X Fibre
9498 Channel Protocol for SCSI" specification. If you want to use this,
9499 you need to say Y here and to "SCSI support" as well as to the
9500 drivers for the storage array itself and for the interface adapter
9501 such as SOC or SOC+. This subsystem could even serve for IP
9502 networking, with some code extensions.
9508 Serial Optical Channel is an interface card with one or two Fibre
9509 Optic ports, each of which can be connected to a disk array. Note
9510 that if you have older firmware in the card, you'll need the
9511 microcode from the Solaris driver to make it work.
9513 This support is also available as a module called soc.o ( = code
9514 which can be inserted in and removed from the running kernel
9515 whenever you want). If you want to compile it as a module, say M
9516 here and read <file:Documentation/modules.txt>.
9518 Sun SOC+ (aka SOCAL)
9520 Serial Optical Channel Plus is an interface card with up to two
9521 Fibre Optic ports. This card supports FC Arbitrated Loop (usually
9522 A5000 or internal FC disks in E[3-6]000 machines through the
9523 Interface Board). You'll probably need the microcode from the
9524 Solaris driver to make it work.
9526 This support is also available as a module called socal.o ( = code
9527 which can be inserted in and removed from the running kernel
9528 whenever you want). If you want to compile it as a module, say M
9529 here and read <file:Documentation/modules.txt>.
9531 SparcSTORAGE Array 100 and 200 series
9533 If you never bought a disk array made by Sun, go with N.
9535 This support is also available as a module called pluto.o ( = code
9536 which can be inserted in and removed from the running kernel
9537 whenever you want). If you want to compile it as a module, say M
9538 here and read <file:Documentation/modules.txt>.
9540 Sun Enterprise Network Array (A5000 and EX500)
9542 This driver drives FC-AL disks connected through a Fibre Channel
9543 card using the drivers/fc4 layer (currently only SOCAL). The most
9544 common is either A5000 array or internal disks in E[3-6]000
9547 This support is also available as a module called fcal.o ( = code
9548 which can be inserted in and removed from the running kernel
9549 whenever you want). If you want to compile it as a module, say M
9550 here and read <file:Documentation/modules.txt>. If unsure, say N.
9552 Acorn SCSI card (aka30) support
9553 CONFIG_SCSI_ACORNSCSI_3
9554 This enables support for the Acorn SCSI card (aka30). If you have an
9555 Acorn system with one of these, say Y. If unsure, say N.
9557 Support SCSI 2 Tagged queueing
9558 CONFIG_SCSI_ACORNSCSI_TAGGED_QUEUE
9559 Say Y here to enable tagged queuing support on the Acorn SCSI card.
9561 This is a feature of SCSI-2 which improves performance: the host
9562 adapter can send several SCSI commands to a device's queue even if
9563 previous commands haven't finished yet. Some SCSI devices don't
9564 implement this properly, so the safe answer is N.
9566 Support SCSI 2 Synchronous Transfers
9567 CONFIG_SCSI_ACORNSCSI_SYNC
9568 Say Y here to enable synchronous transfer negotiation with all
9569 targets on the Acorn SCSI card.
9571 In general, this improves performance; however some SCSI devices
9572 don't implement it properly, so the safe answer is N.
9575 CONFIG_SCSI_ARXESCSI
9576 Around 1991, Arxe Systems Limited released a high density floppy
9577 disc interface for the Acorn Archimedes range, to allow the use of
9578 HD discs from the then new A5000 on earlier models. This interface
9579 was either sold on its own or with an integral SCSI controller.
9580 Technical details on this NCR53c94-based device are available at
9581 <http://www.cryton.demon.co.uk/acornbits/scsi_arxe.html>
9582 Say Y here to compile in support for the SCSI controller.
9586 This enables support for the Oak SCSI card. If you have an Acorn
9587 system with one of these, say Y. If unsure, say N.
9589 Cumana SCSI I support
9590 CONFIG_SCSI_CUMANA_1
9591 This enables support for the Cumana SCSI I card. If you have an
9592 Acorn system with one of these, say Y. If unsure, say N.
9594 Cumana SCSI II support
9595 CONFIG_SCSI_CUMANA_2
9596 This enables support for the Cumana SCSI II card. If you have an
9597 Acorn system with one of these, say Y. If unsure, say N.
9601 This enables support for the EcoSCSI card -- a small card that sits
9602 in the Econet socket. If you have an Acorn system with one of these,
9603 say Y. If unsure, say N.
9606 CONFIG_SCSI_EESOXSCSI
9607 This enables support for the EESOX SCSI card. If you have an Acorn
9608 system with one of these, say Y, otherwise say N.
9610 PowerTec SCSI support
9611 CONFIG_SCSI_POWERTECSCSI
9612 This enables support for the Powertec SCSI card on Acorn systems. If
9613 you have one of these, say Y. If unsure, say N.
9615 IEEE 1394 (FireWire) support
9617 IEEE 1394 describes a high performance serial bus, which is also
9618 known as FireWire(tm) or i.Link(tm) and is used for connecting all
9619 sorts of devices (most notably digital video cameras) to your
9622 If you have FireWire hardware and want to use it, say Y here. This
9623 is the core support only, you will also need to select a driver for
9624 your IEEE 1394 adapter.
9626 If you want to compile this as a module ( = code which can be
9627 inserted in and removed from the running kernel whenever you want),
9628 say M here and read <file:Documentation/modules.txt>. The module
9629 will be called ieee1394.o.
9631 Texas Instruments PCILynx support
9632 CONFIG_IEEE1394_PCILYNX
9633 Say Y here if you have an IEEE-1394 controller with the Texas
9634 Instruments PCILynx chip. Note: this driver is written for revision
9635 2 of this chip and may not work with revision 0.
9637 If you want to compile this as a module ( = code which can be
9638 inserted in and removed from the running kernel whenever you want),
9639 say M here and read <file:Documentation/modules.txt>. The module
9640 will be called pcilynx.o.
9642 Use local RAM on PCILynx board
9643 CONFIG_IEEE1394_PCILYNX_LOCALRAM
9644 This option makes the PCILynx driver use local RAM available on some
9645 PCILynx setups for Packet Control Lists. Local RAM is random access
9646 memory which resides on the PCILynx board as opposed to on your
9647 computer's motherboard. Local RAM may speed up command processing
9648 because no PCI transfers are necessary during use of the Packet
9651 Note that there are no known PCILynx systems providing local RAM
9652 except for the evaluation boards by Texas Instruments and that the
9653 PCILynx does not reliably report missing RAM. This means that it is
9654 dangerous to say Y here if you are not absolutely sure that your
9655 board provides 64KB of local RAM.
9659 Support for non-IEEE1394 local ports
9660 CONFIG_IEEE1394_PCILYNX_PORTS
9661 This option enables driver code to access the RAM, ROM and AUX ports
9662 of the PCILynx through character devices in /dev. If you don't know
9663 what this is about then you won't need it.
9667 #Adaptec AIC-5800 IEEE 1394 support
9668 #CONFIG_IEEE1394_AIC5800
9669 # Say Y here if you have a IEEE 1394 controller using the Adaptec
9670 # AIC-5800 chip. All Adaptec host adapters (89xx series) use this
9671 # chip, as well as miro's DV boards.
9673 # If you want to compile this as a module ( = code which can be
9674 # inserted in and removed from the running kernel whenever you want),
9675 # say M here and read <file:Documentation/modules.txt>. The module
9676 # will be called aic5800.o.
9678 OHCI-1394 (Open Host Controller Interface) support
9679 CONFIG_IEEE1394_OHCI1394
9680 Enable this driver if you have an IEEE 1394 controller based on the
9681 OHCI-1394 specification. The current driver is only tested with OHCI
9682 chipsets made by Texas Instruments and NEC. Most third-party vendors
9683 use one of these chipsets. It should work with any OHCI-1394
9684 compliant card, however.
9686 If you want to compile this as a module ( = code which can be
9687 inserted in and removed from the running kernel whenever you want),
9688 say M here and read <file:Documentation/modules.txt>. The module
9689 will be called ohci1394.o.
9691 OHCI-1394 Video support
9692 CONFIG_IEEE1394_VIDEO1394
9693 This option enables video device usage for OHCI-1394 cards. Enable
9694 this option only if you have an IEEE 1394 video device connected to
9697 SBP-2 support (Harddisks etc.)
9698 CONFIG_IEEE1394_SBP2
9699 This option enables you to use SBP-2 devices connected to your IEEE
9700 1394 bus. SBP-2 devices include harddrives and DVD devices.
9702 Raw IEEE 1394 I/O support
9703 CONFIG_IEEE1394_RAWIO
9704 Say Y here if you want support for the raw device. This is generally
9705 a good idea, so you should say Y here. The raw device enables
9706 direct communication of user programs with the IEEE 1394 bus and
9707 thus with the attached peripherals.
9709 If you want to compile this as a module ( = code which can be
9710 inserted in and removed from the running kernel whenever you want),
9711 say M here and read <file:Documentation/modules.txt>. The module
9712 will be called raw1394.o.
9714 Excessive debugging output
9715 CONFIG_IEEE1394_VERBOSEDEBUG
9716 If you say Y here, you will get very verbose debugging logs from the
9717 subsystem which includes a dump of the header of every sent and
9718 received packet. This can amount to a high amount of data collected
9719 in a very short time which is usually also saved to disk by the
9720 system logging daemons.
9722 Say Y if you really want or need the debugging output, everyone else
9725 CONFIG_IEEE1394_OUI_DB
9726 If you say Y here, then an OUI list (vendor unique ID's) will be
9727 compiled into the ieee1394 module. This doesn't really do much
9728 except being able to display the vendor of a hardware node. The
9729 downside is that it adds about 300k to the size of the module,
9730 or kernel (depending on whether you compile ieee1394 as a
9731 module, or static in the kernel).
9733 This option is not needed for userspace programs like gscanbus
9734 to show this information.
9736 Network device support
9738 You can say N here if you don't intend to connect your Linux box to
9739 any other computer at all or if all your connections will be over a
9740 telephone line with a modem either via UUCP (UUCP is a protocol to
9741 forward mail and news between unix hosts over telephone lines; read
9742 the UUCP-HOWTO, available from
9743 <http://www.tldp.org/docs.html#howto>) or dialing up a shell
9744 account or a BBS, even using term (term is a program which gives you
9745 almost full Internet connectivity if you have a regular dial up
9746 shell account on some Internet connected Unix computer. Read
9747 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
9749 You'll have to say Y if your computer contains a network card that
9750 you want to use under Linux (make sure you know its name because you
9751 will be asked for it and read the Ethernet-HOWTO (especially if you
9752 plan to use more than one network card under Linux)) or if you want
9753 to use SLIP (Serial Line Internet Protocol is the protocol used to
9754 send Internet traffic over telephone lines or null modem cables) or
9755 CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
9756 and newer replacement for SLIP) or PLIP (Parallel Line Internet
9757 Protocol is mainly used to create a mini network by connecting the
9758 parallel ports of two local machines) or AX.25/KISS (protocol for
9759 sending Internet traffic over amateur radio links).
9761 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
9762 Olaf Kirch's excellent and free book "Network Administrator's
9763 Guide", to be found in <http://www.tldp.org/docs.html#guide>. If
9766 Dummy net driver support
9768 This is essentially a bit-bucket device (i.e. traffic you send to
9769 this device is consigned into oblivion) with a configurable IP
9770 address. It is most commonly used in order to make your currently
9771 inactive SLIP address seem like a real address for local programs.
9772 If you use SLIP or PPP, you might want to say Y here. Since this
9773 thing often comes in handy, the default is Y. It won't enlarge your
9774 kernel either. What a deal. Read about it in the Network
9775 Administrator's Guide, available from
9776 <http://www.tldp.org/docs.html#guide>.
9778 If you want to compile this as a module ( = code which can be
9779 inserted in and removed from the running kernel whenever you want),
9780 say M here and read <file:Documentation/modules.txt>. The module
9781 will be called dummy.o. If you want to use more than one dummy
9782 device at a time, you need to compile this driver as a module.
9783 Instead of 'dummy', the devices will then be called 'dummy0',
9786 Bonding driver support
9788 Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
9789 Channels together. This is called 'Etherchannel' by Cisco,
9790 'Trunking' by Sun, and 'Bonding' in Linux.
9792 If you have two Ethernet connections to some other computer, you can
9793 make them behave like one double speed connection using this driver.
9794 Naturally, this has to be supported at the other end as well, either
9795 with a similar Bonding Linux driver, a Cisco 5500 switch or a
9796 SunTrunking SunSoft driver.
9798 This is similar to the EQL driver, but it merges Ethernet segments
9799 instead of serial lines.
9801 If you want to compile this as a module ( = code which can be
9802 inserted in and removed from the running kernel whenever you want),
9803 say M here and read <file:Documentation/modules.txt>. The module
9804 will be called bonding.o.
9806 SLIP (serial line) support
9808 Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
9809 connect to your Internet service provider or to connect to some
9810 other local Unix box or if you want to configure your Linux box as a
9811 Slip/CSlip server for other people to dial in. SLIP (Serial Line
9812 Internet Protocol) is a protocol used to send Internet traffic over
9813 serial connections such as telephone lines or null modem cables;
9814 nowadays, the protocol PPP is more commonly used for this same
9817 Normally, your access provider has to support SLIP in order for you
9818 to be able to use it, but there is now a SLIP emulator called SLiRP
9819 around (available from
9820 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
9821 allows you to use SLIP over a regular dial up shell connection. If
9822 you plan to use SLiRP, make sure to say Y to CSLIP, below. The
9823 NET-3-HOWTO, available from
9824 <http://www.tldp.org/docs.html#howto>, explains how to
9825 configure SLIP. Note that you don't need this option if you just
9826 want to run term (term is a program which gives you almost full
9827 Internet connectivity if you have a regular dial up shell account on
9828 some Internet connected Unix computer. Read
9829 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
9830 support will enlarge your kernel by about 4 KB. If unsure, say N.
9832 If you want to compile this as a module ( = code which can be
9833 inserted in and removed from the running kernel whenever you want),
9834 say M here and read <file:Documentation/modules.txt> as well as
9835 <file:Documentation/networking/net-modules.txt>. The module will be
9838 CSLIP compressed headers
9839 CONFIG_SLIP_COMPRESSED
9840 This protocol is faster than SLIP because it uses compression on the
9841 TCP/IP headers (not on the data itself), but it has to be supported
9842 on both ends. Ask your access provider if you are not sure and
9843 answer Y, just in case. You will still be able to use plain SLIP. If
9844 you plan to use SLiRP, the SLIP emulator (available from
9845 <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
9846 allows you to use SLIP over a regular dial up shell connection, you
9847 definitely want to say Y here. The NET-3-HOWTO, available from
9848 <http://www.tldp.org/docs.html#howto>, explains how to configure
9849 CSLIP. This won't enlarge your kernel.
9851 Keepalive and linefill
9853 Adds additional capabilities to the SLIP driver to support the
9854 RELCOM line fill and keepalive monitoring. Ideal on poor quality
9857 Six bit SLIP encapsulation
9858 CONFIG_SLIP_MODE_SLIP6
9859 Just occasionally you may need to run IP over hostile serial
9860 networks that don't pass all control characters or are only seven
9861 bit. Saying Y here adds an extra mode you can use with SLIP:
9862 "slip6". In this mode, SLIP will only send normal ASCII symbols over
9863 the serial device. Naturally, this has to be supported at the other
9864 end of the link as well. It's good enough, for example, to run IP
9865 over the async ports of a Camtec JNT Pad. If unsure, say N.
9867 PPP (point-to-point protocol) support
9869 PPP (Point to Point Protocol) is a newer and better SLIP. It serves
9870 the same purpose: sending Internet traffic over telephone (and other
9871 serial) lines. Ask your access provider if they support it, because
9872 otherwise you can't use it; most Internet access providers these
9873 days support PPP rather than SLIP.
9875 To use PPP, you need an additional program called pppd as described
9876 in the PPP-HOWTO, available at
9877 <http://www.tldp.org/docs.html#howto>. Make sure that you have
9878 the version of pppd recommended in <file:Documentation/Changes>.
9879 The PPP option enlarges your kernel by about 16 KB.
9881 There are actually two versions of PPP: the traditional PPP for
9882 asynchronous lines, such as regular analog phone lines, and
9883 synchronous PPP which can be used over digital ISDN lines for
9884 example. If you want to use PPP over phone lines or other
9885 asynchronous serial lines, you need to say Y (or M) here and also to
9886 the next option, "PPP support for async serial ports". For PPP over
9887 synchronous lines, you should say Y (or M) here and to "Support
9888 synchronous PPP", below.
9890 This driver is also available as a module ( = code which can be
9891 inserted in and removed from the running kernel whenever you want).
9892 If you said Y to "Version information on all symbols" above, then
9893 you cannot compile the PPP driver into the kernel; you can then only
9894 compile it as a module. The module will be called ppp_generic.o.
9895 If you want to compile it as a module, say M here and read
9896 <file:Documentation/modules.txt> as well as
9897 <file:Documentation/networking/net-modules.txt>.
9899 PPP multilink support
9900 CONFIG_PPP_MULTILINK
9901 PPP multilink is a protocol (defined in RFC 1990) which allows you
9902 to combine several (logical or physical) lines into one logical PPP
9903 connection, so that you can utilize your full bandwidth.
9905 This has to be supported at the other end as well and you need a
9906 version of the pppd daemon which understands the multilink protocol.
9912 Say Y here if you want to be able to filter the packets passing over
9913 PPP interfaces. This allows you to control which packets count as
9914 activity (i.e. which packets will reset the idle timer or bring up
9915 a demand-dialled link) and which packets are to be dropped entirely.
9916 You need to say Y here if you wish to use the pass-filter and
9917 active-filter options to pppd.
9921 PPP support for async serial ports
9923 Say Y (or M) here if you want to be able to use PPP over standard
9924 asynchronous serial ports, such as COM1 or COM2 on a PC. If you use
9925 a modem (not a synchronous or ISDN modem) to contact your ISP, you
9928 If you want to compile the driver as a module ( = code which can be
9929 inserted in and removed from the running kernel whenever you want),
9930 say M here and read <file:Documentation/modules.txt>. The module
9931 will be called ppp_async.o.
9935 PPP support for sync tty ports
9937 Say Y (or M) here if you want to be able to use PPP over synchronous
9938 (HDLC) tty devices, such as the SyncLink adapter. These devices
9939 are often used for high-speed leased lines like T1/E1.
9941 If you want to compile the driver as a module ( = code which can be
9942 inserted in and removed from the running kernel whenever you want),
9943 say M here and read <file:Documentation/modules.txt>. The module
9944 will be called ppp_synctty.o.
9946 PPP Deflate compression
9948 Support for the Deflate compression method for PPP, which uses the
9949 Deflate algorithm (the same algorithm that gzip uses) to compress
9950 each PPP packet before it is sent over the wire. The machine at the
9951 other end of the PPP link (usually your ISP) has to support the
9952 Deflate compression method as well for this to be useful. Even if
9953 they don't support it, it is safe to say Y here.
9955 If you want to compile the driver as a module ( = code which can be
9956 inserted in and removed from the running kernel whenever you want),
9957 say M here and read <file:Documentation/modules.txt>. The module
9958 will be called ppp_deflate.o.
9960 PPP BSD-Compress compression
9962 Support for the BSD-Compress compression method for PPP, which uses
9963 the LZW compression method to compress each PPP packet before it is
9964 sent over the wire. The machine at the other end of the PPP link
9965 (usually your ISP) has to support the BSD-Compress compression
9966 method as well for this to be useful. Even if they don't support it,
9967 it is safe to say Y here.
9969 The PPP Deflate compression method ("PPP Deflate compression",
9970 above) is preferable to BSD-Compress, because it compresses better
9973 Note that the BSD compression code will always be compiled as a
9974 module; it is called bsd_comp.o and will show up in the directory
9975 modules once you have said "make modules". If unsure, say N.
9979 Support for PPP over Ethernet.
9981 This driver requires a ppp release >= 2.4.2.
9983 Wireless LAN (non-hamradio)
9985 Support for wireless LANs and everything having to do with radio,
9986 but not with amateur radio or FM broadcasting.
9988 Saying Y here also enables the Wireless Extensions (creates
9989 /proc/net/wireless and enables ifconfig access). The Wireless
9990 Extension is a generic API allowing a driver to expose to the user
9991 space configuration and statistics specific to common Wireless LANs.
9992 The beauty of it is that a single set of tool can support all the
9993 variations of Wireless LANs, regardless of their type (as long as
9994 the driver supports Wireless Extension). Another advantage is that
9995 these parameters may be changed on the fly without restarting the
9996 driver (or Linux). If you wish to use Wireless Extensions with
9997 wireless PCMCIA (PC-) cards, you need to say Y here; you can fetch
9999 <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
10001 Some user-level drivers for scarab devices which don't require
10002 special kernel support are available from
10003 <ftp://shadow.cabi.net/pub/Linux/>.
10005 STRIP (Metricom Starmode radio IP)
10007 Say Y if you have a Metricom radio and intend to use Starmode Radio
10008 IP. STRIP is a radio protocol developed for the MosquitoNet project
10009 (on the WWW at <http://mosquitonet.stanford.edu/>) to send Internet
10010 traffic using Metricom radios. Metricom radios are small, battery
10011 powered, 100kbit/sec packet radio transceivers, about the size and
10012 weight of a cellular telephone. (You may also have heard them called
10013 "Metricom modems" but we avoid the term "modem" because it misleads
10014 many people into thinking that you can plug a Metricom modem into a
10015 phone line and use it as a modem.)
10017 You can use STRIP on any Linux machine with a serial port, although
10018 it is obviously most useful for people with laptop computers. If you
10019 think you might get a Metricom radio in the future, there is no harm
10020 in saying Y to STRIP now, except that it makes the kernel a bit
10023 You can also compile this as a module ( = code which can be inserted
10024 in and removed from the running kernel whenever you want), say M
10025 here and read <file:Documentation/modules.txt>. The module will be
10028 AT&T WaveLAN & DEC RoamAbout DS support
10030 The Lucent WaveLAN (formerly NCR and AT&T; or DEC RoamAbout DS) is
10031 a Radio LAN (wireless Ethernet-like Local Area Network) using the
10032 radio frequencies 900 MHz and 2.4 GHz.
10034 This driver support the ISA version of the WaveLAN card. A separate
10035 driver for the PCMCIA (PC-card) hardware is available in David
10036 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
10039 If you want to use an ISA WaveLAN card under Linux, say Y and read
10040 the Ethernet-HOWTO, available from
10041 <http://www.tldp.org/docs.html#howto>. Some more specific
10042 information is contained in
10043 <file:Documentation/networking/wavelan.txt> and in the source code
10044 <file:drivers/net/wavelan.p.h>.
10046 You will also need the wireless tools package available from
10047 <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
10048 Please read the man pages contained therein.
10050 This driver is also available as a module ( = code which can be
10051 inserted in and removed from the running kernel whenever you want).
10052 The module will be called wavelan.o. If you want to compile it as a
10053 module, say M here and read <file:Documentation/modules.txt> as well
10054 as <file:Documentation/networking/net-modules.txt>.
10056 Aironet Arlan 655 & IC2200 DS support
10058 Aironet makes Arlan, a class of wireless LAN adapters. These use the
10059 www.Telxon.com chip, which is also used on several similar cards.
10060 This driver is tested on the 655 and IC2200 series cards. Look at
10061 <http://www.ylenurme.ee/~elmer/655/> for the latest information.
10063 The driver is built as two modules, arlan and arlan-proc. The latter
10064 is the /proc interface and is not needed most of time.
10066 On some computers the card ends up in non-valid state after some
10067 time. Use a ping-reset script to clear it.
10069 Aironet 4500/4800 series adapters
10071 www.aironet.com (recently bought by Cisco) makes these 802.11 DS
10072 adapters. Driver by Elmer Joandi (elmer@ylenurme.ee).
10074 Say Y here if you have such an adapter, and then say Y below to
10075 the option that applies to your particular type of card (PCI, ISA,
10078 This driver is also available as a module ( = code which can be
10079 inserted in and removed from the running kernel whenever you want).
10080 The module will be called aironet4500_core.o. If you want to
10081 compile it as a module, say M here and read
10082 <file:Documentation/modules.txt> as well as
10083 <file:Documentation/networking/net-modules.txt>.
10085 quick config parameters:
10086 SSID=tsunami - "The Password"
10087 adhoc=1 there are no Access Points around
10088 master=1 Adhoc master (the one who creates network
10090 slave=1 Adhoc slave (btw, it is still forming own net
10091 sometimes, and has problems with firmware...
10092 change IbssJoinNetTimeout from /proc...)
10093 channel=1..? meaningful in adhoc mode
10095 If you have problems with screwing up card, both_bap_lock=1 is a
10096 conservative value (performance hit 15%).
10098 All other parameters can be set via the proc interface.
10100 Aironet 4500/4800 ISA/PCI/PNP/365 support
10101 CONFIG_AIRONET4500_NONCS
10102 If you have an ISA, PCI or PCMCIA Aironet 4500/4800 wireless LAN
10103 card, say Y here, and then also to the options below that apply
10106 This driver is also available as a module ( = code which can be
10107 inserted in and removed from the running kernel whenever you want).
10108 The module will be called aironet4500_card.o. If you want to
10109 compile it as a module, say M here and read
10110 <file:Documentation/modules.txt>.
10112 Aironet 4500/4800 PNP support
10113 CONFIG_AIRONET4500_PNP
10114 If you have an ISA Aironet 4500/4800 card which you want to use in
10115 PnP (Plug and Play) mode, say Y here. This is the recommended mode
10116 for ISA cards. Remember however to enable the PnP jumper on the
10117 board if you say Y here.
10119 Aironet 4500/4800 PCI support
10120 CONFIG_AIRONET4500_PCI
10121 If you have an PCI Aironet 4500/4800 card, say Y here.
10123 Aironet 4500/4800 ISA broken support
10124 CONFIG_AIRONET4500_ISA
10125 If you have an ISA Aironet 4500/4800 card which you want to run in
10126 non-PnP mode, say Y here. This is not recommended and does not work
10127 correctly at this point. Say N.
10129 Aironet 4500/4800 I365 broken support
10130 CONFIG_AIRONET4500_I365
10131 If you have a PCMCIA Aironet 4500/4800 card which you want to use
10132 without the standard PCMCIA cardservices provided by the pcmcia-cs
10133 package, say Y here. This is not recommended, so say N.
10135 Aironet 4500/4800 PCMCIA support
10136 CONFIG_AIRONET4500_CS
10137 Say Y here if you have a PCMCIA Aironet 4500/4800 card which you
10138 want to use with the standard PCMCIA cardservices provided by the
10141 This driver is also available as a module ( = code which can be
10142 inserted in and removed from the running kernel whenever you want).
10143 The module will be called aironet4500_cs.o. If you want to
10144 compile it as a module, say M here and read
10145 <file:Documentation/modules.txt>.
10147 Intersil 802.11(a/b/g) Prism GT/Duette/Indigo support
10149 Enable PCI and Cardbus support for the following chipset based cards:
10151 ISL3880 - Prism GT 802.11 b/g
10152 ISL3877 - Prism Indigo 802.11 a
10153 ISL3890 - Prism Duette 802.11 a/b/g
10155 For a complete list of supported cards visit <http://prism54.org>.
10156 Here is the latest confirmed list of supported cards:
10158 3com OfficeConnect 11g Cardbus Card aka 3CRWE154G72
10159 Allnet ALL0271 PCI Card
10160 Compex WL54G Cardbus Card
10161 Corega CG-WLCB54GT Cardbus Card
10162 D-Link Air Plus Xtreme G A1 Cardbus Card aka DWL-g650
10163 I-O Data WN-G54/CB Cardbus Card
10164 Kobishi XG-300 aka Z-Com Cardbus Card
10165 Netgear WG511 Cardbus Card
10166 Ovislink WL-5400PCI PCI Card
10167 Peabird WLG-PCI PCI Card
10168 Sitecom WL-100i Cardbus Card
10169 Sitecom WL-110i PCI Card
10170 SMC2802W - EZ Connect g 2.4GHz 54 Mbps Wireless PCI Card
10171 SMC2835W - EZ Connect g 2.4GHz 54 Mbps Wireless Cardbus Card
10172 Z-Com XG-900 PCI Card
10173 Zyxel G-100 Cardbus Card
10175 If you enable this, you require a firmware file as well.
10176 You will need to copy this to /usr/lib/hotplug/firmware/isl3890.
10177 You can get this non-GPL'd firmware file from the Prism54 project page:
10178 <http://prism54.org>.
10179 You will also need the /etc/hotplug/firmware.agent script from
10180 a current hotplug package.
10183 Note: You need a motherboard with DMA support to use any of these cards
10185 If you want to compile the driver as a module ( = code which can be
10186 inserted in and removed from the running kernel whenever you want),
10187 say M here and read <file:Documentation/modules.txt>. The module
10188 will be called prism54.o.
10190 Aironet 4500/4800 PROC interface
10191 CONFIG_AIRONET4500_PROC
10192 If you say Y here (and to the "/proc file system" below), you will
10193 be able to configure your Aironet card via the
10194 /proc/sys/aironet4500 interface.
10196 Additional info: look in <file:drivers/net/aironet4500_rid.c>.
10198 This driver is also available as a module ( = code which can be
10199 inserted in and removed from the running kernel whenever you want).
10200 The module will be called aironet4500_proc.o. If you want to
10201 compile it as a module, say M here and read
10202 <file:Documentation/modules.txt>.
10204 NOTE: the proc interface uses a lot of memory, so it is recommended
10205 to compile it as a module and remove the module after
10208 LAPB over Ethernet driver
10210 This is a driver for a pseudo device (typically called /dev/lapb0)
10211 which allows you to open an LAPB point-to-point connection to some
10212 other computer on your Ethernet network. In order to do this, you
10213 need to say Y or M to the driver for your Ethernet card as well as
10214 to "LAPB Data Link Driver".
10216 If you want to compile this driver as a module ( = code which can be
10217 inserted in and removed from the running kernel whenever you want),
10218 say M here and read <file:Documentation/modules.txt>. The module
10219 will be called lapbether.o. If unsure, say N.
10223 This is a driver for sending and receiving X.25 frames over regular
10224 asynchronous serial lines such as telephone lines equipped with
10225 ordinary modems. Experts should note that this driver doesn't
10226 currently comply with the asynchronous HDLS framing protocols in
10227 CCITT recommendation X.25.
10229 If you want to compile this driver as a module ( = code which can be
10230 inserted in and removed from the running kernel whenever you want),
10231 say M here and read <file:Documentation/modules.txt>. The module
10232 will be called x25_asy.o. If unsure, say N.
10234 PCMCIA network device support
10236 Say Y if you would like to include support for any PCMCIA or CardBus
10237 network adapters, then say Y to the driver for your particular card
10238 below. PCMCIA- or PC-cards are credit-card size devices often used
10239 with laptops computers; CardBus is the newer and faster version of
10242 To use your PC-cards, you will need supporting software from David
10243 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
10244 for location). You also want to check out the PCMCIA-HOWTO,
10245 available from <http://www.tldp.org/docs.html#howto>.
10249 3Com 3c589 PCMCIA support
10250 CONFIG_PCMCIA_3C589
10251 Say Y here if you intend to attach a 3Com 3c589 or compatible PCMCIA
10252 (PC-card) Ethernet card to your computer.
10254 This driver is also available as a module ( = code which can be
10255 inserted in and removed from the running kernel whenever you want).
10256 The module will be called 3c589_cs.o. If you want to compile it as
10257 a module, say M here and read <file:Documentation/modules.txt>. If
10260 3Com 3c574 PCMCIA support
10261 CONFIG_PCMCIA_3C574
10262 Say Y here if you intend to attach a 3Com 3c574 or compatible PCMCIA
10263 (PC-card) Fast Ethernet card to your computer.
10265 This driver is also available as a module ( = code which can be
10266 inserted in and removed from the running kernel whenever you want).
10267 The module will be called 3c574_cs.o. If you want to compile it as
10268 a module, say M here and read <file:Documentation/modules.txt>. If
10271 Fujitsu FMV-J18x PCMCIA support
10272 CONFIG_PCMCIA_FMVJ18X
10273 Say Y here if you intend to attach a Fujitsu FMV-J18x or compatible
10274 PCMCIA (PC-card) Ethernet card to your computer.
10276 This driver is also available as a module ( = code which can be
10277 inserted in and removed from the running kernel whenever you want).
10278 The module will be called fmvj18x_cs.o. If you want to compile it
10279 as a module, say M here and read <file:Documentation/modules.txt>.
10282 NE2000 compatible PCMCIA support
10283 CONFIG_PCMCIA_PCNET
10284 Say Y here if you intend to attach an NE2000 compatible PCMCIA
10285 (PC-card) Ethernet or Fast Ethernet card to your computer.
10287 This driver is also available as a module ( = code which can be
10288 inserted in and removed from the running kernel whenever you want).
10289 The module will be called pcnet_cs.o. If you want to compile it as
10290 a module, say M here and read <file:Documentation/modules.txt>. If
10293 Asix AX88190 PCMCIA support
10294 CONFIG_PCMCIA_AXNET
10295 Say Y here if you intend to attach an Asix AX88190-based PCMCIA
10296 (PC-card) Fast Ethernet card to your computer. These cards are
10297 nearly NE2000 compatible but need a separate driver due to a few
10300 This driver is also available as a module ( = code which can be
10301 inserted in and removed from the running kernel whenever you want).
10302 The module will be called axnet_cs.o. If you want to compile it as
10303 a module, say M here and read <file:Documentation/modules.txt>. If
10306 New Media PCMCIA support
10307 CONFIG_PCMCIA_NMCLAN
10308 Say Y here if you intend to attach a New Media Ethernet or LiveWire
10309 PCMCIA (PC-card) Ethernet card to your computer.
10311 This driver is also available as a module ( = code which can be
10312 inserted in and removed from the running kernel whenever you want).
10313 The module will be called nmclan_cs.o. If you want to compile it as
10314 a module, say M here and read <file:Documentation/modules.txt>. If
10317 SMC 91Cxx PCMCIA support
10318 CONFIG_PCMCIA_SMC91C92
10319 Say Y here if you intend to attach an SMC 91Cxx compatible PCMCIA
10320 (PC-card) Ethernet or Fast Ethernet card to your computer.
10322 This driver is also available as a module ( = code which can be
10323 inserted in and removed from the running kernel whenever you want).
10324 The module will be called smc91c92_cs.o. If you want to compile it
10325 as a module, say M here and read <file:Documentation/modules.txt>.
10328 Xircom 16-bit PCMCIA support
10329 CONFIG_PCMCIA_XIRC2PS
10330 Say Y here if you intend to attach a Xircom 16-bit PCMCIA (PC-card)
10331 Ethernet or Fast Ethernet card to your computer.
10333 This driver is also available as a module ( = code which can be
10334 inserted in and removed from the running kernel whenever you want).
10335 The module will be called xirc2ps_cs.o. If you want to compile it
10336 as a module, say M here and read <file:Documentation/modules.txt>.
10339 COM20020 ARCnet PCMCIA support
10340 CONFIG_ARCNET_COM20020_CS
10341 Say Y here if you intend to attach this type of ARCnet PCMCIA card
10344 This driver is also available as a module ( = code which can be
10345 inserted in and removed from the running kernel whenever you want).
10346 The module will be called com20020_cs.o. If you want to compile it
10347 as a module, say M here and read <file:Documentation/modules.txt>.
10350 IBM PCMCIA Token Ring adapter support
10351 CONFIG_PCMCIA_IBMTR
10352 Say Y here if you intend to attach this type of Token Ring PCMCIA
10353 card to your computer. You then also need to say Y to "Token Ring
10356 This driver is also available as a module ( = code which can be
10357 inserted in and removed from the running kernel whenever you want).
10358 The module will be called ibmtr_cs.o. If you want to compile it as
10359 a module, say M here and read <file:Documentation/modules.txt>.
10361 Xircom Tulip-like CardBus support (old driver)
10362 CONFIG_PCMCIA_XIRTULIP
10363 This driver is for the Digital "Tulip" Ethernet CardBus adapters.
10364 It should work with most DEC 21*4*-based chips/ethercards, as well
10365 as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and
10368 This driver is also available as a module ( = code which can be
10369 inserted in and removed from the running kernel whenever you want).
10370 The module will be called xircom_tulip_cb.o. If you want to compile
10371 it as a module, say M here and read
10372 <file:Documentation/modules.txt>. If unsure, say N.
10374 Xircom CardBus support (new driver)
10375 CONFIG_PCMCIA_XIRCOM
10376 This driver is for the Digital "Tulip" Ethernet CardBus adapters.
10377 It should work with most DEC 21*4*-based chips/ethercards, as well
10378 as with work-alike chips from Lite-On (PNIC) and Macronix (MXIC) and
10381 This driver is also available as a module ( = code which can be
10382 inserted in and removed from the running kernel whenever you want).
10383 The module will be called xircom_cb.o. If you want to compile
10384 it as a module, say M here and read
10385 <file:Documentation/modules.txt>. If unsure, say N.
10387 PCMCIA Wireless LAN
10388 CONFIG_NET_PCMCIA_RADIO
10389 Say Y here if you would like to use a PCMCIA (PC-card) device to
10390 connect to a wireless local area network. Then say Y to the driver
10391 for your particular card below.
10393 To use your PC-cards, you will need supporting software from David
10394 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
10395 for location). You also want to check out the PCMCIA-HOWTO,
10396 available from <http://www.tldp.org/docs.html#howto>.
10398 Hermes chipset 802.11b support (Orinoco/Prism2/Symbol cards)
10400 A driver for 802.11b wireless cards based based on the "Hermes" or
10401 Intersil HFA384x (Prism 2) MAC controller. This includes the vast
10402 majority of the PCMCIA 802.11b cards (which are nearly all rebadges)
10403 - except for the Cisco/Aironet cards. Cards supported include the
10404 Apple Airport (not a PCMCIA card), WavelanIEEE/Orinoco,
10405 Cabletron/EnteraSys Roamabout, ELSA AirLancer, MELCO Buffalo, Avaya,
10406 IBM High Rate Wireless, Farralon Syyline, Samsung MagicLAN, Netgear
10407 MA401, LinkSys WPC-11, D-Link DWL-650, 3Com AirConnect, Intel
10408 PRO/Wireless, and Symbol Spectrum24 High Rate amongst others.
10410 This option includes the guts of the driver, but in order to
10411 actually use a card you will also need to enable support for PCMCIA
10412 Hermes cards, PLX9052 based PCI adaptors or the Apple Airport below.
10414 You will also very likely also need the Wireless Tools in order to
10415 configure your card and that /etc/pcmcia/wireless.opts works :
10416 <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>
10418 If you want to compile the driver as a module ( = code which can be
10419 inserted in and removed from the running kernel whenever you want),
10420 say M here and read <file:Documentation/modules.txt>. The module
10421 will be called hermes.o.
10423 Hermes 802.11b in PLX9052 based PCI adaptor support
10425 Enable support for PCMCIA cards supported by the "Hermes" (aka
10426 orinoco_cs) driver when used in PLX9052 based PCI adaptors. These
10427 adaptors are not a full PCMCIA controller but act as a more limited
10428 PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that
10429 802.11b PCMCIA cards can be used in desktop machines. The Netgear
10430 MA301 is such an adaptor.
10432 Support for these adaptors is so far still incomplete and buggy.
10433 You have been warned.
10435 Hermes 802.11b in TMD7160/NCP130 based PCI adaptor support
10437 Enable support for PCMCIA cards supported by the "Hermes" (aka
10438 orinoco) driver when used in TMD7160 based PCI adaptors. These
10439 adaptors are not a full PCMCIA controller but act as a more limited
10440 PCI <-> PCMCIA bridge. Several vendors sell such adaptors so that
10441 802.11b PCMCIA cards can be used in desktop machines.
10443 Support for these adaptors is so far still incomplete and buggy.
10444 You have been warned.
10446 Prism 2.5 PCI 802.11b adaptor support
10448 Enable support for PCI and mini-PCI 802.11b wireless NICs based on
10449 the Prism 2.5 chipset. These are true PCI cards, not the 802.11b
10450 PCMCIA cards bundled with PCI<->PCMCIA adaptors which are also
10451 common. Some of the built-in wireless adaptors in laptops are of
10454 Hermes support (Orinoco/WavelanIEEE/PrismII/Symbol 802.11b cards)
10455 CONFIG_PCMCIA_HERMES
10456 A driver for "Hermes" chipset based PCMCIA wireless adaptors, such
10457 as the Lucent WavelanIEEE/Orinoco cards and their OEM (Cabletron/
10458 EnteraSys RoamAbout 802.11, ELSA Airlancer, Melco Buffalo and
10459 others). It should also be usable on various Prism II based cards
10460 such as the Linksys, D-Link and Farallon Skyline. It should also
10461 work on Symbol cards such as the 3Com AirConnect and Ericsson WLAN.
10463 To use your PC-cards, you will need supporting software from David
10464 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
10465 for location). You also want to check out the PCMCIA-HOWTO,
10466 available from <http://www.tldp.org/docs.html#howto>.
10468 You will also very likely also need the Wireless Tools in order to
10469 configure your card and that /etc/pcmcia/wireless.opts works:
10470 <http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html>.
10472 If you want to compile the driver as a module ( = code which can be
10473 inserted in and removed from the running kernel whenever you want),
10474 say M here and read <file:Documentation/modules.txt>. The module
10475 will be called orinoco_cs.o.
10477 Cisco/Aironet 34X/35X/4500/4800 ISA and PCI cards
10479 This is the standard Linux driver to support Cisco/Aironet ISA and
10480 PCI 802.11 wireless cards.
10481 It supports the new 802.11b cards from Cisco (Cisco 34X, Cisco 35X
10482 - with or without encryption) as well as card before the Cisco
10483 acquisition (Aironet 4500, Aironet 4800, Aironet 4800B).
10485 This driver support both the standard Linux Wireless Extensions
10486 and Cisco proprietary API, so both the Linux Wireless Tools and the
10487 Cisco Linux utilities can be used to configure the card.
10489 The driver can be compiled as a module and will be named "airo.o".
10491 Cisco/Aironet 34X/35X/4500/4800 PCMCIA cards
10493 This is the standard Linux driver to support Cisco/Aironet PCMCIA
10494 802.11 wireless cards. This driver is the same as the Aironet
10495 driver part of the Linux Pcmcia package.
10496 It supports the new 802.11b cards from Cisco (Cisco 34X, Cisco 35X
10497 - with or without encryption) as well as card before the Cisco
10498 acquisition (Aironet 4500, Aironet 4800, Aironet 4800B). It also
10499 supports OEM of Cisco such as the DELL TrueMobile 4800 and Xircom
10502 This driver support both the standard Linux Wireless Extensions
10503 and Cisco proprietary API, so both the Linux Wireless Tools and the
10504 Cisco Linux utilities can be used to configure the card.
10506 To use your PC-cards, you will need supporting software from David
10507 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
10508 for location). You also want to check out the PCMCIA-HOWTO,
10509 available from <http://www.tldp.org/docs.html#howto>.
10511 If you want to compile the driver as a module ( = code which can be
10512 inserted in and removed from the running kernel whenever you want),
10513 say M here and read <file:Documentation/modules.txt>. The module
10514 will be called airo_cs.o.
10516 Atmel at76c502/at76c504 PCMCIA cards
10517 CONFIG_PCMCIA_ATMEL
10518 A driver for PCMCIA 802.11 wireless cards based on the
10519 Atmel fast-vnet chips. This driver supports standard
10520 Linux wireless extensions.
10522 Many cards based on this chipset do not have flash memory
10523 and need their firmware loaded at start-up. If yours is
10524 one of these, you will need to provide a firmware image
10525 to be loaded into the card by the driver. The Atmel
10526 firmware package can be downloaded from
10527 http://www.thekelleys.org.uk/atmel/atmel_firmware.tar.gz
10529 Aviator/Raytheon 2.4MHz wireless support
10530 CONFIG_PCMCIA_RAYCS
10531 Say Y here if you intend to attach an Aviator/Raytheon PCMCIA
10532 (PC-card) wireless Ethernet networking card to your computer.
10533 Please read the file <file:Documentation/networking/ray_cs.txt> for
10536 This driver is also available as a module ( = code which can be
10537 inserted in and removed from the running kernel whenever you want).
10538 The module will be called ray_cs.o. If you want to compile it as a
10539 module, say M here and read <file:Documentation/modules.txt>. If
10542 Apple Airport support (built-in)
10543 CONFIG_APPLE_AIRPORT
10544 Say Y here to support the Airport 802.11b wireless Ethernet hardware
10545 built into the Macintosh iBook and other recent PowerPC-based
10546 Macintosh machines. This is essentially a Lucent Orinoco card with
10547 a non-standard interface
10549 Xircom Netwave AirSurfer wireless support
10550 CONFIG_PCMCIA_NETWAVE
10551 Say Y here if you intend to attach this type of PCMCIA (PC-card)
10552 wireless Ethernet networking card to your computer.
10554 This driver is also available as a module ( = code which can be
10555 inserted in and removed from the running kernel whenever you want).
10556 The module will be called netwave_cs.o. If you want to compile it
10557 as a module, say M here and read <file:Documentation/modules.txt>.
10560 AT&T/Lucent Wavelan wireless support
10561 CONFIG_PCMCIA_WAVELAN
10562 Say Y here if you intend to attach an AT&T/Lucent Wavelan PCMCIA
10563 (PC-card) wireless Ethernet networking card to your computer. This
10564 driver is for the non-IEEE-802.11 Wavelan cards.
10566 This driver is also available as a module ( = code which can be
10567 inserted in and removed from the running kernel whenever you want).
10568 The module will be called wavelan_cs.o. If you want to compile it
10569 as a module, say M here and read <file:Documentation/modules.txt>.
10572 PLIP (parallel port) support
10574 PLIP (Parallel Line Internet Protocol) is used to create a
10575 reasonably fast mini network consisting of two (or, rarely, more)
10576 local machines. A PLIP link from a Linux box is a popular means to
10577 install a Linux distribution on a machine which doesn't have a
10578 CD-ROM drive (a minimal system has to be transferred with floppies
10579 first). The kernels on both machines need to have this PLIP option
10580 enabled for this to work.
10582 The PLIP driver has two modes, mode 0 and mode 1. The parallel
10583 ports (the connectors at the computers with 25 holes) are connected
10584 with "null printer" or "Turbo Laplink" cables which can transmit 4
10585 bits at a time (mode 0) or with special PLIP cables, to be used on
10586 bidirectional parallel ports only, which can transmit 8 bits at a
10587 time (mode 1); you can find the wiring of these cables in
10588 <file:Documentation/networking/PLIP.txt>. The cables can be up to
10589 15m long. Mode 0 works also if one of the machines runs DOS/Windows
10590 and has some PLIP software installed, e.g. the Crynwr PLIP packet
10591 driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
10592 and winsock or NCSA's telnet.
10594 If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
10595 as the NET-3-HOWTO, both available from
10596 <http://www.tldp.org/docs.html#howto>. Note that the PLIP
10597 protocol has been changed and this PLIP driver won't work together
10598 with the PLIP support in Linux versions 1.0.x. This option enlarges
10599 your kernel by about 8 KB.
10601 If you want to compile this as a module ( = code which can be
10602 inserted in and removed from the running kernel whenever you want),
10603 say M here and read <file:Documentation/modules.txt> as well as
10604 <file:Documentation/networking/net-modules.txt>. The module will be
10605 called plip.o. If unsure, say Y or M, in case you buy a laptop
10608 EQL (serial line load balancing) support
10610 If you have two serial connections to some other computer (this
10611 usually requires two modems and two telephone lines) and you use
10612 SLIP (the protocol for sending Internet traffic over telephone
10613 lines) or PPP (a better SLIP) on them, you can make them behave like
10614 one double speed connection using this driver. Naturally, this has
10615 to be supported at the other end as well, either with a similar EQL
10616 Linux driver or with a Livingston Portmaster 2e.
10618 Say Y if you want this and read
10619 <file:Documentation/networking/eql.txt>. You may also want to read
10620 section 6.2 of the NET-3-HOWTO, available from
10621 <http://www.tldp.org/docs.html#howto>.
10623 This driver is also available as a module ( = code which can be
10624 inserted in and removed from the running kernel whenever you want).
10625 The module will be called eql.o. If you want to compile it as a
10626 module, say M here and read <file:Documentation/modules.txt>. If
10629 Universal TUN/TAP device driver support
10631 TUN/TAP provides packet reception and transmission for user space
10632 programs. It can be viewed as a simple Point-to-Point or Ethernet
10633 device, which instead of receiving packets from a physical media,
10634 receives them from user space program and instead of sending packets
10635 via physical media writes them to the user space program.
10637 When a program opens /dev/net/tun, driver creates and registers
10638 corresponding net device tunX or tapX. After a program closed above
10639 devices, driver will automatically delete tunXX or tapXX device and
10640 all routes corresponding to it.
10642 Please read <file:Documentation/networking/tuntap.txt> for more
10645 This driver is also available as a module ( = code which can be
10646 inserted in and removed from the running kernel whenever you want).
10647 The module will be called tun.o. If you want to compile it as a
10648 module, say M here and read <file:Documentation/modules.txt>.
10650 If you don't know what to use this for, you don't need it.
10652 Ethertap network tap (OBSOLETE)
10654 If you say Y here (and have said Y to "Kernel/User network link
10655 driver", above) and create a character special file /dev/tap0 with
10656 major number 36 and minor number 16 using mknod ("man mknod"), you
10657 will be able to have a user space program read and write raw
10658 Ethernet frames from/to that special file. tap0 can be configured
10659 with ifconfig and route like any other Ethernet device but it is not
10660 connected to any physical LAN; everything written by the user to
10661 /dev/tap0 is treated by the kernel as if it had come in from a LAN
10662 to the device tap0; everything the kernel wants to send out over the
10663 device tap0 can instead be read by the user from /dev/tap0: the user
10664 mode program replaces the LAN that would be attached to an ordinary
10665 Ethernet device. Please read the file
10666 <file:Documentation/networking/ethertap.txt> for more information.
10668 This driver is also available as a module ( = code which can be
10669 inserted in and removed from the running kernel whenever you want).
10670 The module will be called ethertap.o. If you want to compile it as a
10671 module, say M here and read <file:Documentation/modules.txt>.
10673 If you don't know what to use this for, you don't need it.
10675 Sealevel Systems 4021 support
10676 CONFIG_SEALEVEL_4021
10677 This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
10679 This driver can only be compiled as a module ( = code which can be
10680 inserted in and removed from the running kernel whenever you want).
10681 If you want to do that, say M here. The module will be called
10684 TMPTX3912/PR31700 serial port support
10685 CONFIG_SERIAL_TX3912
10686 The TX3912 is a Toshiba RISC processor based o the MIPS 3900 core;
10687 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
10688 Say Y here to enable kernel support for the on-board serial port.
10690 Console on TMPTX3912/PR31700 serial port
10691 CONFIG_SERIAL_TX3912_CONSOLE
10692 The TX3912 is a Toshiba RISC processor based o the MIPS 3900 core;
10693 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
10694 Say Y here to direct console I/O to the on-board serial port.
10696 Enable Au1000 serial console
10697 CONFIG_AU1000_SERIAL_CONSOLE
10698 If you have an Alchemy AU1000 processor (MIPS based) and you want
10699 to use a console on a serial port, say Y. Otherwise, say N.
10701 Enable Au1000 UART Support
10703 If you have an Alchemy AU1000 processor (MIPS based) and you want
10704 to use serial ports, say Y. Otherwise, say N.
10706 SyncLink HDLC/SYNCPPP support
10707 CONFIG_SYNCLINK_SYNCPPP
10708 Enables HDLC/SYNCPPP support for the SyncLink WAN driver.
10709 Normally the SyncLink WAN driver works with the main PPP
10710 driver (ppp.c) and pppd program. HDLC/SYNCPPP support allows use
10711 of the Cisco HDLC/PPP driver (syncppp.c).
10712 The SyncLink WAN driver (in character devices) must also be enabled.
10714 If you want to compile the driver as a module ( = code which can be
10715 inserted in and removed from the running kernel whenever you want),
10716 say M here and read <file:Documentation/modules.txt>. The module
10717 will be called syncppp.o.
10719 FarSync T-Series X.21 (and V.35/V.24) cards
10721 This driver supports the FarSync T-Series X.21 (and V.35/V.24) cards
10722 from FarSite Communications Ltd.
10723 Synchronous communication is supported on all ports at speeds up to
10724 8Mb/s (128K on V.24) using synchronous PPP, Cisco HDLC, raw HDLC,
10725 Frame Relay or X.25/LAPB.
10727 If you want to compile this driver as a module ( = code which can be
10728 inserted in and removed from the running kernel whenever you want)
10729 say M here and read <file:Documentation/modules.txt>.
10730 The module will be called farsync.o and if you want the module to be
10731 automatically loaded when the interface is referenced then you
10732 should add "alias hdlcX farsync" to /etc/modules.conf for each
10733 interface, where X is 0, 1, 2, ...
10735 Frame Relay (DLCI) support
10737 This is support for the frame relay protocol; frame relay is a fast
10738 low-cost way to connect to a remote Internet access provider or to
10739 form a private wide area network. The one physical line from your
10740 box to the local "switch" (i.e. the entry point to the frame relay
10741 network, usually at the phone company) can carry several logical
10742 point-to-point connections to other computers connected to the frame
10743 relay network. For a general explanation of the protocol, check out
10744 <http://www.frforum.com/> on the WWW. To use frame relay, you need
10745 supporting hardware (called FRAD) and certain programs from the
10746 net-tools package as explained in
10747 <file:Documentation/networking/framerelay.txt>.
10749 This driver is also available as a module ( = code which can be
10750 inserted in and removed from the running kernel whenever you want).
10751 The module will be called dlci.o. If you want to compile it as a
10752 module, say M here and read <file:Documentation/modules.txt>.
10756 This is the maximal number of logical point-to-point frame relay
10757 connections (the identifiers of which are called DCLIs) that
10758 the driver can handle. The default is probably fine.
10760 Max DLCI per device
10762 You can specify here how many logical point-to-point frame relay
10763 connections (the identifiers of which are called DCLIs) should be
10764 handled by each of your hardware frame relay access devices. Go with
10767 SDLA (Sangoma S502/S508) support
10769 Say Y here if you need a driver for the Sangoma S502A, S502E, and
10770 S508 Frame Relay Access Devices. These are multi-protocol cards, but
10771 only frame relay is supported by the driver at this time. Please
10772 read <file:Documentation/framerelay.txt>.
10774 This driver is also available as a module ( = code which can be
10775 inserted in and removed from the running kernel whenever you want).
10776 The module will be called sdla.o. If you want to compile it as a
10777 module, say M here and read <file:Documentation/modules.txt>.
10779 Acorn Econet/AUN protocols
10781 Econet is a fairly old and slow networking protocol mainly used by
10782 Acorn computers to access file and print servers. It uses native
10783 Econet network cards. AUN is an implementation of the higher level
10784 parts of Econet that runs over ordinary Ethernet connections, on
10785 top of the UDP packet protocol, which in turn runs on top of the
10786 Internet protocol IP.
10788 If you say Y here, you can choose with the next two options whether
10789 to send Econet/AUN traffic over a UDP Ethernet connection or over
10790 a native Econet network card.
10792 This driver is also available as a module ( = code which can be
10793 inserted in and removed from the running kernel whenever you want).
10794 The module will be called econet.o. If you want to compile it as a
10795 module, say M here and read <file:Documentation/modules.txt>.
10798 CONFIG_ECONET_AUNUDP
10799 Say Y here if you want to send Econet/AUN traffic over a UDP
10800 connection (UDP is a packet based protocol that runs on top of the
10801 Internet protocol IP) using an ordinary Ethernet network card.
10804 CONFIG_ECONET_NATIVE
10805 Say Y here if you have a native Econet network card installed in
10810 Wide Area Networks (WANs), such as X.25, frame relay and leased
10811 lines, are used to interconnect Local Area Networks (LANs) over vast
10812 distances with data transfer rates significantly higher than those
10813 achievable with commonly used asynchronous modem connections.
10814 Usually, a quite expensive external device called a `WAN router' is
10815 needed to connect to a WAN.
10817 As an alternative, WAN routing can be built into the Linux kernel.
10818 With relatively inexpensive WAN interface cards available on the
10819 market, a perfectly usable router can be built for less than half
10820 the price of an external router. If you have one of those cards and
10821 wish to use your Linux box as a WAN router, say Y here and also to
10822 the WAN driver for your card, below. You will then need the
10823 wan-tools package which is available from <ftp://ftp.sangoma.com/>.
10824 Read <file:Documentation/networking/wan-router.txt> for more
10827 The WAN routing support is also available as a module called
10828 wanrouter.o ( = code which can be inserted in and removed from the
10829 running kernel whenever you want). If you want to compile it as a
10830 module, say M here and read <file:Documentation/modules.txt>.
10834 Fast switching (read help!)
10835 CONFIG_NET_FASTROUTE
10836 Saying Y here enables direct NIC-to-NIC (NIC = Network Interface
10837 Card) data transfers on the local network, which is fast.
10839 IMPORTANT NOTE: This option is NOT COMPATIBLE with "Network packet
10840 filtering" (CONFIG_NETFILTER). Say N here if you say Y there.
10842 However, it will work with all options in the "Advanced router"
10843 section (except for "Use TOS value as routing key" and
10844 "Use FWMARK value as routing key").
10846 At the moment, few devices support fast switching (tulip is one of
10847 them, a modified 8390 driver can be found at
10848 <ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz>).
10852 Forwarding between high speed interfaces
10853 CONFIG_NET_HW_FLOWCONTROL
10854 This option enables NIC (Network Interface Card) hardware throttling
10855 during periods of extremal congestion. At the moment only a couple
10856 of device drivers support it (really only one -- tulip, a modified
10857 8390 driver can be found at
10858 <ftp://ftp.inr.ac.ru/ip-routing/fastroute/fastroute-8390.tar.gz>).
10860 Really, this option is applicable to any machine attached to a fast
10861 enough network, and even a 10 Mb NIC is able to kill a not very slow
10862 box, such as a 120MHz Pentium.
10864 However, do not say Y here if you did not experience any serious
10867 QoS and/or fair queueing
10869 When the kernel has several packets to send out over a network
10870 device, it has to decide which ones to send first, which ones to
10871 delay, and which ones to drop. This is the job of the packet
10872 scheduler, and several different algorithms for how to do this
10873 "fairly" have been proposed.
10875 If you say N here, you will get the standard packet scheduler, which
10876 is a FIFO (first come, first served). If you say Y here, you will be
10877 able to choose from among several alternative algorithms which can
10878 then be attached to different network devices. This is useful for
10879 example if some of your network devices are real time devices that
10880 need a certain minimum data flow rate, or if you need to limit the
10881 maximum data flow rate for traffic which matches specified criteria.
10882 This code is considered to be experimental.
10884 To administer these schedulers, you'll need the user-level utilities
10885 from the package iproute2+tc at <ftp://ftp.inr.ac.ru/ip-routing/>.
10886 That package also contains some documentation; for more, check out
10887 <http://snafu.freedom.org/linux2.2/iproute-notes.html>.
10889 This Quality of Service (QoS) support will enable you to use
10890 Differentiated Services (diffserv) and Resource Reservation Protocol
10891 (RSVP) on your Linux router if you also say Y to "QoS support",
10892 "Packet classifier API" and to some classifiers below. Documentation
10893 and software is at <http://icawww1.epfl.ch/linux-diffserv/>.
10895 If you say Y here and to "/proc file system" below, you will be able
10896 to read status information about packet schedulers from the file
10899 The available schedulers are listed in the following questions; you
10900 can say Y to as many as you like. If unsure, say N now.
10902 CBQ packet scheduler
10904 Say Y here if you want to use the Class-Based Queueing (CBQ) packet
10905 scheduling algorithm for some of your network devices. This
10906 algorithm classifies the waiting packets into a tree-like hierarchy
10907 of classes; the leaves of this tree are in turn scheduled by
10908 separate algorithms (called "disciplines" in this context).
10910 See the top of <file:net/sched/sch_cbq.c> for references about the
10913 CBQ is a commonly used scheduler, so if you're unsure, you should
10914 say Y here. Then say Y to all the queueing algorithms below that you
10915 want to use as CBQ disciplines. Then say Y to "Packet classifier
10916 API" and say Y to all the classifiers you want to use; a classifier
10917 is a routine that allows you to sort your outgoing traffic into
10918 classes based on a certain criterion.
10920 This code is also available as a module called sch_cbq.o ( = code
10921 which can be inserted in and removed from the running kernel
10922 whenever you want). If you want to compile it as a module, say M
10923 here and read <file:Documentation/modules.txt>.
10926 Say Y here if you want to use the Hierarchical Token Buckets (HTB)
10927 packet scheduling algorithm for some of your network devices. See
10928 URL <http://luxik.cdi.cz/~devik/qos/htb/> for complete manual and
10931 HTB is very similar to the CBQ regarding its goals however is has
10932 different properties and different algorithm.
10934 This code is also available as a module called sch_htb.o ( = code
10935 which can be inserted in and removed from the running kernel
10936 whenever you want). If you want to compile it as a module, say M
10937 here and read <file:Documentation/modules.txt>.
10939 CONFIG_NET_SCH_HFSC
10940 Say Y here if you want to use the Hierarchical Fair Service Curve
10941 (HFSC) packet scheduling algorithm for some of your network devices.
10943 This code is also available as a module called sch_hfsc.o ( = code
10944 which can be inserted in and removed from the running kernel
10945 whenever you want). If you want to compile it as a module, say M
10946 here and read <file:Documentation/modules.txt>.
10948 CSZ packet scheduler
10950 Say Y here if you want to use the Clark-Shenker-Zhang (CSZ) packet
10951 scheduling algorithm for some of your network devices. At the
10952 moment, this is the only algorithm that can guarantee service for
10953 real-time applications (see the top of <file:net/sched/sch_csz.c>
10954 for details and references about the algorithm).
10956 Note: this scheduler is currently broken.
10958 This code is also available as a module called sch_csz.o ( = code
10959 which can be inserted in and removed from the running kernel
10960 whenever you want). If you want to compile it as a module, say M
10961 here and read <file:Documentation/modules.txt>.
10963 ATM pseudo-scheduler
10965 Say Y here if you want to use the ATM pseudo-scheduler. This
10966 provides a framework for invoking classifiers (aka "filters"), which
10967 in turn select classes of this queuing discipline. Each class maps
10968 the flow(s) it is handling to a given virtual circuit (see the top of
10969 <file:net/sched/sch_atm.c>).
10971 This code is also available as a module called sch_atm.o ( = code
10972 which can be inserted in and removed from the running kernel
10973 whenever you want). If you want to compile it as a module, say M
10974 here and read <file:Documentation/modules.txt>.
10976 The simplest PRIO pseudo-scheduler
10977 CONFIG_NET_SCH_PRIO
10978 Say Y here if you want to use an n-band priority queue packet
10979 "scheduler" for some of your network devices or as a leaf discipline
10980 for the CBQ scheduling algorithm. If unsure, say Y.
10982 This code is also available as a module called sch_prio.o ( = code
10983 which can be inserted in and removed from the running kernel
10984 whenever you want). If you want to compile it as a module, say M
10985 here and read <file:Documentation/modules.txt>.
10987 Diffserv field marker
10988 CONFIG_NET_SCH_DSMARK
10989 Say Y if you want to schedule packets according to the
10990 Differentiated Services architecture proposed in RFC 2475.
10991 Technical information on this method, with pointers to associated
10992 RFCs, is available at <http://www.gta.ufrj.br/diffserv/>.
10994 This code is also available as a module called sch_dsmark.o ( = code
10995 which can be inserted in and removed from the running kernel
10996 whenever you want). If you want to compile it as a module, say M
10997 here and read <file:Documentation/modules.txt>.
11000 CONFIG_NET_SCH_GRED
11001 Say Y here if you want to use the Generic Random Early Detection
11002 (RED) packet scheduling algorithm for some of your network devices
11003 (see the top of <file:net/sched/sch_red.c> for details and
11004 references about the algorithm).
11006 This code is also available as a module called sch_gred.o ( = code
11007 which can be inserted in and removed from the running kernel
11008 whenever you want). If you want to compile it as a module, say M
11009 here and read <file:Documentation/modules.txt>.
11013 Say Y here if you want to use the Random Early Detection (RED)
11014 packet scheduling algorithm for some of your network devices (see
11015 the top of <file:net/sched/sch_red.c> for details and references
11016 about the algorithm).
11018 This code is also available as a module called sch_red.o ( = code
11019 which can be inserted in and removed from the running kernel
11020 whenever you want). If you want to compile it as a module, say M
11021 here and read <file:Documentation/modules.txt>.
11025 Say Y here if you want to use the Stochastic Fairness Queueing (SFQ)
11026 packet scheduling algorithm for some of your network devices or as a
11027 leaf discipline for the CBQ scheduling algorithm (see the top of
11028 <file:net/sched/sch_sfq.c> for details and references about the SFQ
11031 This code is also available as a module called sch_sfq.o ( = code
11032 which can be inserted in and removed from the running kernel
11033 whenever you want). If you want to compile it as a module, say M
11034 here and read <file:Documentation/modules.txt>.
11037 CONFIG_NET_SCH_TEQL
11038 Say Y here if you want to use the True Link Equalizer (TLE) packet
11039 scheduling algorithm for some of your network devices or as a leaf
11040 discipline for the CBQ scheduling algorithm. This queueing
11041 discipline allows the combination of several physical devices into
11042 one virtual device. (see the top of <file:net/sched/sch_teql.c> for
11045 This code is also available as a module called sch_teql.o ( = code
11046 which can be inserted in and removed from the running kernel
11047 whenever you want). If you want to compile it as a module, say M
11048 here and read <file:Documentation/modules.txt>.
11052 Say Y here if you want to use the Simple Token Bucket Filter (TBF)
11053 packet scheduling algorithm for some of your network devices or as a
11054 leaf discipline for the CBQ scheduling algorithm (see the top of
11055 <file:net/sched/sch_tbf.c> for a description of the TBF algorithm).
11057 This code is also available as a module called sch_tbf.o ( = code
11058 which can be inserted in and removed from the running kernel
11059 whenever you want). If you want to compile it as a module, say M
11060 here and read <file:Documentation/modules.txt>.
11062 CONFIG_NET_SCH_NETEM
11063 Say Y if you want to emulate network delay, loss, and packet
11064 re-ordering. This is often useful to simulate networks when
11065 testing applications or protocols.
11067 To compile this driver as a module, choose M here: the module
11068 will be called sch_netem.
11073 CONFIG_NET_SCH_INGRESS
11074 If you say Y here, you will be able to police incoming bandwidth
11075 and drop packets when this bandwidth exceeds your desired rate.
11078 This code is also available as a module called cls_ingress.o
11079 ( = code which can be inserted in and removed from the running
11080 kernel whenever you want). If you want to compile it as a module,
11081 say M here and read <file:Documentation/modules.txt>.
11085 Say Y here if you want to include Quality Of Service scheduling
11086 features, which means that you will be able to request certain
11087 rate-of-flow limits for your network devices.
11089 This Quality of Service (QoS) support will enable you to use
11090 Differentiated Services (diffserv) and Resource Reservation Protocol
11091 (RSVP) on your Linux router if you also say Y to "Packet classifier
11092 API" and to some classifiers below. Documentation and software is at
11093 <http://icawww1.epfl.ch/linux-diffserv/>.
11095 Note that the answer to this question won't directly affect the
11096 kernel: saying N will just cause the configurator to skip all
11097 the questions about QoS support.
11100 CONFIG_NET_ESTIMATOR
11101 In order for Quality of Service scheduling to work, the current
11102 rate-of-flow for a network device has to be estimated; if you say Y
11103 here, the kernel will do just that.
11105 Packet classifier API
11107 The CBQ scheduling algorithm requires that network packets which are
11108 scheduled to be sent out over a network device be classified
11109 according to some criterion. If you say Y here, you will get a
11110 choice of several different packet classifiers with the following
11113 This will enable you to use Differentiated Services (diffserv) and
11114 Resource Reservation Protocol (RSVP) on your Linux router.
11115 Documentation and software is at
11116 <http://icawww1.epfl.ch/linux-diffserv/>.
11118 Traffic policing (needed for in/egress)
11119 CONFIG_NET_CLS_POLICE
11120 Say Y to support traffic policing (bandwidth limits). Needed for
11121 ingress and egress rate limiting.
11123 TC index classifier
11124 CONFIG_NET_CLS_TCINDEX
11125 If you say Y here, you will be able to classify outgoing packets
11126 according to the tc_index field of the skb. You will want this
11127 feature if you want to implement Differentiated Services using
11128 sch_dsmark. If unsure, say Y.
11130 This code is also available as a module called cls_tcindex.o
11131 ( = code which can be inserted in and removed from the running
11132 kernel whenever you want). If you want to compile it as a module,
11133 say M here and read <file:Documentation/modules.txt>.
11135 Routing tables based classifier
11136 CONFIG_NET_CLS_ROUTE4
11137 If you say Y here, you will be able to classify outgoing packets
11138 according to the route table entry they matched. If unsure, say Y.
11140 This code is also available as a module called cls_route.o ( = code
11141 which can be inserted in and removed from the running kernel
11142 whenever you want). If you want to compile it as a module, say M
11143 here and read <file:Documentation/modules.txt>.
11145 Firewall based classifier
11147 If you say Y here, you will be able to classify outgoing packets
11148 according to firewall criteria you specified.
11150 This code is also available as a module called cls_fw.o ( = code
11151 which can be inserted in and removed from the running kernel
11152 whenever you want). If you want to compile it as a module, say M
11153 here and read <file:Documentation/modules.txt>.
11157 If you say Y here, you will be able to classify outgoing packets
11158 according to their destination address. If unsure, say Y.
11160 This code is also available as a module called cls_u32.o ( = code
11161 which can be inserted in and removed from the running kernel
11162 whenever you want). If you want to compile it as a module, say M
11163 here and read <file:Documentation/modules.txt>.
11165 Special RSVP classifier
11166 CONFIG_NET_CLS_RSVP
11167 The Resource Reservation Protocol (RSVP) permits end systems to
11168 request a minimum and maximum data flow rate for a connection; this
11169 is important for real time data such as streaming sound or video.
11171 Say Y here if you want to be able to classify outgoing packets based
11172 on their RSVP requests.
11174 This code is also available as a module called cls_rsvp.o ( = code
11175 which can be inserted in and removed from the running kernel
11176 whenever you want). If you want to compile it as a module, say M
11177 here and read <file:Documentation/modules.txt>.
11179 Special RSVP classifier for IPv6
11180 CONFIG_NET_CLS_RSVP6
11181 The Resource Reservation Protocol (RSVP) permits end systems to
11182 request a minimum and maximum data flow rate for a connection; this
11183 is important for real time data such as streaming sound or video.
11185 Say Y here if you want to be able to classify outgoing packets based
11186 on their RSVP requests and you are using the new Internet Protocol
11187 IPv6 as opposed to the older and more common IPv4.
11189 This code is also available as a module called cls_rsvp6.o ( = code
11190 which can be inserted in and removed from the running kernel
11191 whenever you want). If you want to compile it as a module, say M
11192 here and read <file:Documentation/modules.txt>.
11194 Network code profiler
11196 If you say Y here and to "/proc file system support" below, some
11197 obscure and undocumented information about the network code's
11198 performance will be written to /proc/net/profile. If you don't know
11199 what it is about, you don't need it: say N.
11201 Network packet generator
11203 This module will inject preconfigured packets, at a configurable
11204 rate, out of a given interface. It is used for network interface
11205 stress testing and performance analysis. If you don't understand
11206 what was just said, you don't need it: say N.
11208 Documentation on how to use the packet generator can be found
11209 at <file:Documentation/networking/pktgen.txt>.
11211 This code is also available as a module called pktgen.o ( = code
11212 which can be inserted in and removed from the running kernel
11213 whenever you want). If you want to compile it as a module, say M
11214 here and read <file:Documentation/modules.txt>.
11216 Wan interfaces support
11218 Wide Area Networks (WANs), such as X.25, frame relay and leased
11219 lines, are used to interconnect Local Area Networks (LANs) over vast
11220 distances with data transfer rates significantly higher than those
11221 achievable with commonly used asynchronous modem connections.
11222 Usually, a quite expensive external device called a `WAN router' is
11223 needed to connect to a WAN.
11225 As an alternative, a relatively inexpensive WAN interface card can
11226 allow your Linux box to directly connect to a WAN. If you have one
11227 of those cards and wish to use it under Linux, say Y here and also
11228 to the WAN driver for your card, below.
11232 Comtrol Hostess SV-11 support
11233 CONFIG_HOSTESS_SV11
11234 This is a network card for low speed synchronous serial links, at
11235 up to 256Kbps. It supports both PPP and Cisco HDLC.
11237 At this point, the driver can only be compiled as a module.
11239 If you want to compile the driver as a module ( = code which can be
11240 inserted in and removed from the running kernel whenever you want),
11241 say M here and read <file:Documentation/modules.txt>. The module
11242 will be called hostess_sv11.o.
11244 COSA/SRP sync serial board support
11246 This is a driver for COSA and SRP synchronous serial boards. These
11247 boards allow to connect synchronous serial devices (for example
11248 base-band modems, or any other device with the X.21, V.24, V.35 or
11249 V.36 interface) to your Linux box. The cards can work as the
11250 character device, synchronous PPP network device, or the Cisco HDLC
11253 To actually use the COSA or SRP board, you will need user-space
11254 utilities for downloading the firmware to the cards and to set them
11255 up. Look at the <http://www.fi.muni.cz/~kas/cosa/> for more
11256 information about the cards (including the pointer to the user-space
11257 utilities). You can also read the comment at the top of the
11258 <file:drivers/net/wan/cosa.c> for details about the cards and the driver
11261 The driver will be compiled as a module ( = code which can be
11262 inserted in and removed from the running kernel whenever you want).
11263 The module will be called cosa.o. For general information about
11264 modules read <file:Documentation/modules.txt>.
11266 Etinc PCISYNC serial board support
11268 This is a driver for Etinc PCISYNC boards based on the Infineon
11269 (ex. Siemens) DSCC4 chipset. It is supposed to work with the four
11270 ports card. Take a look at <http://www.cogenit.fr/dscc4/>
11271 for further informations about the driver and his configuration.
11273 The driver will be compiled as a module ( = code which can be
11274 inserted in and removed from the running kernel whenever you want).
11275 The module will be called dscc4.o. For general information about
11276 modules read <file:Documentation/modules.txt>.
11279 CONFIG_DSCC4_PCISYNC
11280 Due to Etinc's design choice for its PCISYNC cards, some operations
11281 are only allowed on specific ports of the DSCC4. This option is the
11282 only way for the driver to know that it shouldn't return a success
11283 code for these operations.
11285 Please say Y if your card is an Etinc's PCISYNC.
11288 CONFIG_DSCC4_PCI_RST
11289 Various DSCC4 bug forbid any reliable software reset of the asic.
11290 As a replacement, some vendors provide a way to assert the PCI #RST
11291 pin of DSCC4 through the GPIO port of the card. If you choose Y, the
11292 driver will make use of this feature before module removal (i.e. rmmod).
11293 This feature is known to exist on Commtech's cards.
11294 Contact your manufacturer for details.
11296 Say Y if yout card supports this feature.
11298 LanMedia Corp. serial boards (SSI/V.35, T1/E1, HSSI, T3)
11300 This is a driver for the following Lan Media family of serial
11303 LMC 1000 board allows you to connect synchronous serial devices (for
11304 example base-band modems, or any other device with the X.21, V.24,
11305 V.35 or V.36 interface) to your Linux box.
11307 LMC 1200 with on board DSU board allows you to connect your Linux
11308 box directly to a T1 or E1 circuit.
11310 LMC 5200 board provides a HSSI interface capable of running up to
11311 52 mbits per second.
11313 LMC 5245 board connects directly to a T3 circuit saving the
11314 additional external hardware.
11316 To change setting such as syncPPP vs cisco HDLC or clock source you
11317 will need lmcctl. It is available at <ftp://ftp.lanmedia.com/>.
11319 This code is also available as a module called lmc.o ( = code
11320 which can be inserted in and removed from the running kernel
11321 whenever you want). If you want to compile it as a module, say M
11322 here and read <file:Documentation/modules.txt>.
11324 Fibre Channel driver support
11326 Fibre Channel is a high speed serial protocol mainly used to connect
11327 large storage devices to the computer; it is compatible with and
11328 intended to replace SCSI.
11330 If you intend to use Fibre Channel, you need to have a Fibre channel
11331 adaptor card in your computer; say Y here and to the driver for your
11332 adaptor below. You also should have said Y to "SCSI support" and
11333 "SCSI generic support".
11335 Interphase 5526 Tachyon chipset based adaptor support
11337 Say Y here if you have a Fibre Channel adaptor of this kind.
11339 The driver is also available as a module ( = code which can be
11340 inserted in and removed from the running kernel whenever you want).
11341 The module will be called iph5526.o. For general information about
11342 modules read <file:Documentation/modules.txt>.
11344 Red Creek Hardware VPN
11346 This is a driver for hardware which provides a Virtual Private
11347 Network (VPN). Say Y if you have it.
11349 This code is also available as a module called rcpci.o ( = code
11350 which can be inserted in and removed from the running kernel
11351 whenever you want). If you want to compile it as a module, say M
11352 here and read <file:Documentation/modules.txt>.
11354 Granch SBNI12 Leased Line adapter driver
11356 This is a driver for ISA SBNI12-xx cards which are low cost
11357 alternatives to leased line modems. Say Y if you want to insert
11358 the driver into the kernel or say M to compile it as a module (the
11359 module will be called sbni.o).
11361 You can find more information and last versions of drivers and
11362 utilities at <http://www.granch.ru/>. If you have any question you
11363 can send email to sbni@granch.ru.
11367 SBNI multiple-line feature support
11368 CONFIG_SBNI_MULTILINE
11369 Schedule traffic for some parallel lines, via SBNI12 adapters.
11370 If you have two computers connected with two parallel lines it's
11371 possible to increase transfer rate nearly twice. You should have
11372 a program named 'sbniconfig' to configure adapters.
11377 CONFIG_WAN_ROUTER_DRIVERS
11378 If you have a WAN interface card and you want your Linux box to act
11379 as a WAN router, thereby connecting you Local Area Network to the
11380 outside world over the WAN connection, say Y here and then to the
11381 driver for your card below. In addition, you need to say Y to "Wan
11384 You will need the wan-tools package which is available from
11385 <ftp://ftp.sangoma.com/>. Read
11386 <file:Documentation/networking/wan-router.txt> for more information.
11388 Note that the answer to this question won't directly affect the
11389 kernel: saying N will just cause the configurator to skip all
11390 the questions about WAN router drivers. If unsure, say N.
11392 Sangoma WANPIPE(tm) multiprotocol cards
11393 CONFIG_VENDOR_SANGOMA
11394 WANPIPE from Sangoma Technologies Inc. (<http://www.sangoma.com/>)
11395 is a family of intelligent multiprotocol WAN adapters with data
11396 transfer rates up to 4Mbps. They are also known as Synchronous
11397 Data Link Adapters (SDLA) and are designated as S514-PCI or
11398 S508-ISA. These cards support
11400 - X.25, Frame Relay, PPP, Cisco HDLC protocols.
11402 - API support for protocols like HDLC (LAPB),
11403 HDLC Streaming, X.25, Frame Relay and BiSync.
11405 - Ethernet Bridging over Frame Relay protocol.
11409 - Async PPP (Modem Dialup)
11411 If you have one or more of these cards, say M to this option; you
11412 may then also want to read the file
11413 <file:Documentation/networking/wanpipe.txt>. The next questions
11414 will ask you about the protocols you want the driver to support.
11416 The driver will be compiled as a module ( = code which can be
11417 inserted in and removed from the running kernel whenever you want).
11418 The module will be called wanpipe.o. For general information about
11419 modules read <file:Documentation/modules.txt>.
11421 WANPIPE X.25 support
11423 Say Y to this option if you are planning to connect a WANPIPE card
11424 to an X.25 network. Note, this feature also includes the X.25 API
11425 support used to develop custom applications over the X.25 protocol.
11426 If you say N, the X.25 support will not be included in the driver.
11427 The X.25 option is supported on S514-PCI and S508-ISA cards.
11429 WANPIPE Frame Relay support
11431 Say Y to this option if you are planning to connect a WANPIPE card
11432 to a frame relay network, or use frame relay API to develop
11433 custom applications over the Frame Relay protocol.
11434 This feature also contains the Ethernet Bridging over Frame Relay,
11435 where a WANPIPE frame relay link can be directly connected to the
11436 Linux kernel bridge. If you say N, the frame relay support will
11437 not be included in the driver. The Frame Relay option is
11438 supported on S514-PCI and S508-ISA cards.
11440 WANPIPE PPP support
11442 Say Y to this option if you are planning to connect a WANPIPE card
11443 to a leased line using Point-to-Point protocol (PPP). If you say N,
11444 the PPP support will not be included in the driver. The PPP option
11445 is supported on S514-PCI/S508-ISA cards.
11447 WANPIPE Multi-Port PPP support
11448 CONFIG_WANPIPE_MULTPPP
11449 Say Y to this option if you are planning to connect a WANPIPE card
11450 to a leased line using Point-to-Point protocol (PPP). Note, the
11451 MultiPort PPP uses the Linux Kernel SyncPPP protocol over the
11452 Sangoma HDLC Streaming adapter. In this case each Sangoma adapter
11453 port can support an independent PPP connection. For example, a
11454 single Quad-Port PCI adapter can support up to four independent
11455 PPP links. If you say N,the PPP support will not be included in the
11456 driver. The PPP option is supported on S514-PCI/S508-ISA cards.
11458 WANPIPE Cisco HDLC support
11459 CONFIG_WANPIPE_CHDLC
11460 Say Y to this option if you are planning to connect a WANPIPE card
11461 to a leased line using the Cisco HDLC protocol. This now supports
11462 Dual Port Cisco HDLC on the S514-PCI/S508-ISA cards.
11463 This support also allows user to build applications using the
11464 HDLC streaming API.
11466 CHDLC Streaming driver also supports MULTILINK PPP
11467 support that can bind multiple WANPIPE T1 cards into
11468 a single logical channel.
11470 If you say N, the Cisco HDLC support and
11471 HDLC streaming API and MULTILINK PPP will not be
11472 included in the driver.
11474 MultiGate (COMX) synchronous serial board support
11476 Say Y if you want to use any board from the MultiGate (COMX) family.
11477 These boards are synchronous serial adapters for the PC,
11478 manufactured by ITConsult-Pro Co, Hungary.
11480 Read <file:Documentation/networking/comx.txt> for help on
11481 configuring and using COMX interfaces. Further info on these cards
11482 can be found at <http://www.itc.hu/> or <info@itc.hu>.
11484 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
11487 Support for COMX/CMX/HiCOMX boards
11488 CONFIG_COMX_HW_COMX
11489 Hardware driver for the 'CMX', 'COMX' and 'HiCOMX' boards from the
11490 MultiGate family. Say Y if you have one of these.
11492 You will need additional firmware to use these cards, which are
11493 downloadable from <ftp://ftp.itc.hu/>.
11495 If you want to compile this as a module, say M and read
11496 <file:Documentation/modules.txt>. The module will be called
11499 Support for LoCOMX board
11500 CONFIG_COMX_HW_LOCOMX
11501 Hardware driver for the 'LoCOMX' board from the MultiGate family.
11502 Say Y if you have a board like this.
11504 If you want to compile this as a module, say M and read
11505 <file:Documentation/modules.txt>. The module will be called
11508 Support for MixCOM board
11509 CONFIG_COMX_HW_MIXCOM
11510 Hardware driver for the 'MixCOM' board from the MultiGate family.
11511 Say Y if you have a board like this.
11513 If you want to use the watchdog device on this card, you should
11514 select it in the Watchdog Cards section of the Character Devices
11515 configuration. The ISDN interface of this card is Teles 16.3
11516 compatible, you should enable it in the ISDN configuration menu. The
11517 driver for the flash ROM of this card is available separately on
11518 <ftp://ftp.itc.hu/>.
11520 If you want to compile this as a module, say M and read
11521 <file:Documentation/modules.txt>. The module will be called
11524 i810 TCO timer/watchdog support
11526 Hardware driver for the TCO timer built into the Intel i810 and i815
11527 chipset family. The TCO (Total Cost of Ownership) timer is a
11528 watchdog timer that will reboot the machine after its second
11529 expiration. The expiration time can be configured by command
11530 argument "i810_margin=<n>" where <n> is the counter initial value.
11531 It is decremented every 0.6 secs, the default is 50 which gives a
11532 timeout of 30 seconds and one minute until reset.
11534 On some motherboards the driver may fail to reset the chipset's
11535 NO_REBOOT flag which prevents the watchdog from rebooting the
11536 machine. If this is the case you will get a kernel message like
11537 "i810tco init: failed to reset NO_REBOOT flag".
11539 If you want to compile this as a module, say M and read
11540 <file:Documentation/modules.txt>. The module will be called
11543 SliceCOM/PciCOM board support
11544 CONFIG_COMX_HW_MUNICH
11545 Hardware driver for the 'SliceCOM' (channelized E1) and 'PciCOM'
11546 boards (X21) from the MultiGate family.
11548 This driver is also available as a module ( = code which can be
11549 inserted in and removed from the running kernel whenever you want).
11550 The module will be called comx-hw-munich.o. If you want to compile it
11551 as a module, say M here and read <file:Documentation/modules.txt>.
11553 Read linux/Documentation/networking/slicecom.txt for help on
11554 configuring and using SliceCOM interfaces. Further info on these cards
11555 can be found at <http://www.itc.hu> or <info@itc.hu>.
11557 Support for HDLC and syncPPP protocols on MultiGate boards
11558 CONFIG_COMX_PROTO_PPP
11559 Cisco-HDLC and synchronous PPP protocol driver for all MultiGate
11560 boards. Say Y if you want to use either protocol on your MultiGate
11563 If you want to compile this as a module, say M and read
11564 <file:Documentation/modules.txt>. The module will be called
11567 Support for LAPB protocol on MultiGate boards
11568 CONFIG_COMX_PROTO_LAPB
11569 LAPB protocol driver for all MultiGate boards. Say Y if you
11570 want to use this protocol on your MultiGate boards.
11572 If you want to compile this as a module, say M and read
11573 <file:Documentation/modules.txt>. The module will be called
11576 Support for Frame Relay on MultiGate boards
11577 CONFIG_COMX_PROTO_FR
11578 Frame Relay protocol driver for all MultiGate boards. Say Y if you
11579 want to use this protocol on your MultiGate boards.
11581 If you want to compile this as a module, say M and read
11582 <file:Documentation/modules.txt>. The module will be called
11585 Cyclom 2X(tm) multiprotocol cards
11586 CONFIG_CYCLADES_SYNC
11587 Cyclom 2X from Cyclades Corporation (<http://www.cyclades.com/> and
11588 <http://www.cyclades.com.br/>) is an intelligent multiprotocol WAN
11589 adapter with data transfer rates up to 512 Kbps. These cards support
11590 the X.25 and SNA related protocols. If you have one or more of these
11591 cards, say Y to this option. The next questions will ask you about
11592 the protocols you want the driver to support (for now only X.25 is
11595 While no documentation is available at this time please grab the
11596 wanconfig tarball in
11597 <http://www.conectiva.com.br/~acme/cycsyn-devel/> (with minor changes
11598 to make it compile with the current wanrouter include files; efforts
11599 are being made to use the original package available at
11600 <ftp://ftp.sangoma.com/>).
11602 Feel free to contact me or the cycsyn-devel mailing list at
11603 acme@conectiva.com.br and cycsyn-devel@bazar.conectiva.com.br for
11604 additional details, I hope to have documentation available as soon
11605 as possible. (Cyclades Brazil is writing the Documentation).
11607 The driver will be compiled as a module ( = code which can be
11608 inserted in and removed from the running kernel whenever you want).
11609 The module will be called cyclomx.o. For general information about
11610 modules read <file:Documentation/modules.txt>.
11612 Cyclom 2X X.25 support
11614 Say Y to this option if you are planning to connect a Cyclom 2X card
11615 to an X.25 network.
11617 If you say N, the X.25 support will not be included in the driver
11618 (saves about 11 KB of kernel memory).
11620 Generic HDLC driver
11622 Say Y to this option if your Linux box contains a WAN card supported
11623 by this driver and you are planning to connect the box to a WAN
11624 ( = Wide Area Network). You will need supporting software from
11625 <http://hq.pm.waw.pl/hdlc/>.
11626 Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame
11627 Relay, synchronous Point-to-Point Protocol (PPP) and X.25.
11629 If you want to compile the driver as a module ( = code which can be
11630 inserted in and removed from the running kernel whenever you want),
11631 say M here and read <file:Documentation/modules.txt>. The module
11632 will be called hdlc.o.
11634 If unsure, say N here.
11638 Say Y to this option if you want generic HDLC driver to support
11639 raw HDLC over WAN (Wide Area Network) connections.
11641 If unsure, say N here.
11643 Raw HDLC Ethernet device support
11644 CONFIG_HDLC_RAW_ETH
11645 Say Y to this option if you want generic HDLC driver to support
11646 raw HDLC Ethernet device emulation over WAN (Wide Area Network)
11648 You will need it for Ethernet over HDLC bridges.
11650 If unsure, say N here.
11654 Say Y to this option if you want generic HDLC driver to support
11655 Cisco HDLC over WAN (Wide Area Network) connections.
11657 If unsure, say N here.
11659 Frame-Relay HDLC support
11661 Say Y to this option if you want generic HDLC driver to support
11662 Frame-Relay protocol over WAN (Wide Area Network) connections.
11664 If unsure, say N here.
11666 Synchronous Point-to-Point Protocol (PPP) support
11668 Say Y to this option if you want generic HDLC driver to support
11669 PPP over WAN (Wide Area Network) connections.
11671 If unsure, say N here.
11673 CCITT X.25 over HDLC support
11675 Say Y to this option if you want generic HDLC driver to support
11676 X.25 protocol over WAN (Wide Area Network) connections.
11678 If unsure, say N here.
11680 Cyclades-PC300 support
11682 This is a driver for the Cyclades-PC300 synchronous communication
11683 boards. These boards provide synchronous serial interfaces to your
11684 Linux box (interfaces currently available are RS-232/V.35, X.21 and
11685 T1/E1). If you wish to support Multilink PPP, please select the
11686 option below this one and read the file README.mlppp provided by PC300
11689 If you want to compile this as a module ( = code which can be
11690 inserted in and removed from the running kernel whenever you want),
11691 say M here and read Documentation/modules.txt. The module will be
11694 If you haven't heard about it, it's safe to say N.
11696 Cyclades-PC300 Sync TTY (to MLPPP) support
11698 Say 'Y' to this option if you are planning to use Multilink PPP over the
11699 PC300 synchronous communication boards.
11702 This driver is for PCI200SYN cards made by Goramo sp. j.
11703 If you have such a card, say Y or M here and see
11704 <http://hq.pm.waw.pl/pub/hdlc/>
11706 If you want to compile the driver as a module ( = code which can be
11707 inserted in and removed from the running kernel whenever you want),
11708 say M here and read <file:Documentation/modules.txt>. The module
11709 will be called pci200syn.o.
11711 If unsure, say N here.
11713 SDL RISCom/N2 support
11715 This driver is for RISCom/N2 single or dual channel ISA cards
11716 made by SDL Communications Inc. If you have such a card,
11717 say Y here and see <http://hq.pm.waw.pl/pub/hdlc/>.
11719 Note that N2csu and N2dds cards are not supported by this driver.
11721 If you want to compile the driver as a module ( = code which can be
11722 inserted in and removed from the running kernel whenever you want),
11723 say M here and read <file:Documentation/modules.txt>. The module
11724 will be called n2.o.
11726 If unsure, say N here.
11730 This driver is for C101 SuperSync ISA cards made by Moxa
11731 Technologies Co., Ltd. If you have such a card,
11732 say Y here and see <http://hq.pm.waw.pl/pub/hdlc/>
11734 If you want to compile the driver as a module ( = code which can be
11735 inserted in and removed from the running kernel whenever you want),
11736 say M here and read <file:Documentation/modules.txt>. The module
11737 will be called c101.o.
11739 If unsure, say N here.
11741 Ethernet (10 or 100Mbit)
11742 CONFIG_NET_ETHERNET
11743 Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
11744 type of Local Area Network (LAN) in universities and companies.
11746 Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
11747 coaxial cable, linking computers in a chain), 10BASE-T or twisted
11748 pair (10 Mbps over twisted pair cable, linking computers to central
11749 hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
11750 100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
11751 100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
11752 cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
11753 [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
11754 Ethernet (1 Gbps over optical fiber or short copper links).
11756 If your Linux machine will be connected to an Ethernet and you have
11757 an Ethernet network interface card (NIC) installed in your computer,
11758 say Y here and read the Ethernet-HOWTO, available from
11759 <http://www.tldp.org/docs.html#howto>. You will then also have
11760 to say Y to the driver for your particular NIC.
11762 Note that the answer to this question won't directly affect the
11763 kernel: saying N will just cause the configurator to skip all
11764 the questions about Ethernet network cards. If unsure, say N.
11766 Western Digital/SMC cards
11767 CONFIG_NET_VENDOR_SMC
11768 If you have a network (Ethernet) card belonging to this class, say Y
11769 and read the Ethernet-HOWTO, available from
11770 <http://www.tldp.org/docs.html#howto>.
11772 Note that the answer to this question doesn't directly affect the
11773 kernel: saying N will just cause the configurator to skip all
11774 the questions about Western Digital cards. If you say Y, you will be
11775 asked for your specific card in the following questions.
11779 If you have a network (Ethernet) card of this type, say Y and read
11780 the Ethernet-HOWTO, available from
11781 <http://www.tldp.org/docs.html#howto>.
11783 This driver is also available as a module ( = code which can be
11784 inserted in and removed from the running kernel whenever you want).
11785 The module will be called wd.o. If you want to compile it as a
11786 module, say M here and read <file:Documentation/modules.txt> as well
11787 as <file:Documentation/networking/net-modules.txt>.
11789 SMC Ultra MCA support
11791 If you have a network (Ethernet) card of this type and are running
11792 an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
11793 available from <http://www.tldp.org/docs.html#howto>.
11795 This driver is also available as a module ( = code which can be
11796 inserted in and removed from the running kernel whenever you want).
11797 The module will be called smc-mca.o. If you want to compile it as a
11798 module, say M here and read <file:Documentation/modules.txt> as well
11799 as <file:Documentation/networking/net-modules.txt>.
11803 If you have a network (Ethernet) card of this type, say Y and read
11804 the Ethernet-HOWTO, available from
11805 <http://www.tldp.org/docs.html#howto>.
11807 Important: There have been many reports that, with some motherboards
11808 mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
11809 such as some BusLogic models) causes corruption problems with many
11810 operating systems. The Linux smc-ultra driver has a work-around for
11811 this but keep it in mind if you have such a SCSI card and have
11814 This driver is also available as a module ( = code which can be
11815 inserted in and removed from the running kernel whenever you want).
11816 The module will be called smc-ultra.o. If you want to compile it as
11817 a module, say M here and read <file:Documentation/modules.txt> as
11818 well as <file:Documentation/networking/net-modules.txt>.
11820 SMC Ultra32 EISA support
11822 If you have a network (Ethernet) card of this type, say Y and read
11823 the Ethernet-HOWTO, available from
11824 <http://www.tldp.org/docs.html#howto>.
11826 This driver is also available as a module ( = code which can be
11827 inserted in and removed from the running kernel whenever you want).
11828 The module will be called smc-ultra32.o. If you want to compile it
11829 as a module, say M here and read <file:Documentation/modules.txt> as
11830 well as <file:Documentation/networking/net-modules.txt>.
11834 This is support for the SMC9xxx based Ethernet cards. Choose this
11835 option if you have a DELL laptop with the docking station, or
11836 another SMC9192/9194 based chipset. Say Y if you want it compiled
11837 into the kernel, and read the file
11838 <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
11839 available from <http://www.tldp.org/docs.html#howto>.
11841 This driver is also available as a module ( = code which can be
11842 inserted in and removed from the running kernel whenever you want).
11843 The module will be called smc9194.o. If you want to compile it as a
11844 module, say M here and read <file:Documentation/modules.txt> as well
11845 as <file:Documentation/networking/net-modules.txt>.
11847 PCI NE2000 and clones support
11849 This driver is for NE2000 compatible PCI cards. It will not work
11850 with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
11851 support" below). If you have a PCI NE2000 network (Ethernet) card,
11852 say Y and read the Ethernet-HOWTO, available from
11853 <http://www.tldp.org/docs.html#howto>.
11855 This driver also works for the following NE2000 clone cards:
11856 RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2
11857 NetVin NV5000SC Via 86C926 SureCom NE34 Winbond
11858 Holtek HT80232 Holtek HT80229
11860 This driver is also available as a module ( = code which can be
11861 inserted in and removed from the running kernel whenever you want).
11862 The module will be called ne2k-pci.o. If you want to compile it as
11863 a module, say M here and read <file:Documentation/modules.txt> as
11864 well as <file:Documentation/networking/net-modules.txt>.
11866 Racal-Interlan (Micom) NI cards
11867 CONFIG_NET_VENDOR_RACAL
11868 If you have a network (Ethernet) card belonging to this class, such
11869 as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
11870 available from <http://www.tldp.org/docs.html#howto>.
11872 Note that the answer to this question doesn't directly affect the
11873 kernel: saying N will just cause the configurator to skip all
11874 the questions about NI cards. If you say Y, you will be asked for
11875 your specific card in the following questions.
11879 If you have a network (Ethernet) card of this type, say Y and read
11880 the Ethernet-HOWTO, available from
11881 <http://www.tldp.org/docs.html#howto>. Note that this is still
11884 This driver is also available as a module ( = code which can be
11885 inserted in and removed from the running kernel whenever you want).
11886 The module will be called ni5010.o. If you want to compile it as a
11887 module, say M here and read <file:Documentation/modules.txt> as well
11888 as <file:Documentation/networking/net-modules.txt>.
11892 If you have a network (Ethernet) card of this type, say Y and read
11893 the Ethernet-HOWTO, available from
11894 <http://www.tldp.org/docs.html#howto>.
11896 This driver is also available as a module ( = code which can be
11897 inserted in and removed from the running kernel whenever you want).
11898 The module will be called ni52.o. If you want to compile it as a
11899 module, say M here and read <file:Documentation/modules.txt> as well
11900 as <file:Documentation/networking/net-modules.txt>.
11904 If you have a network (Ethernet) card of this type, say Y and read
11905 the Ethernet-HOWTO, available from
11906 <http://www.tldp.org/docs.html#howto>.
11908 This driver is also available as a module ( = code which can be
11909 inserted in and removed from the running kernel whenever you want).
11910 The module will be called ni65.o. If you want to compile it as a
11911 module, say M here and read <file:Documentation/modules.txt> as well
11912 as <file:Documentation/networking/net-modules.txt>.
11914 RealTek RTL-8139C+ 10/100 PCI Fast Ethernet Adapter support
11916 This is a driver for the Fast Ethernet PCI network cards based on
11917 the RTL8139C+ chips. If you have one of those, say Y and read
11918 the Ethernet-HOWTO, available from
11919 <http://www.tldp.org/docs.html#howto>.
11921 If you want to compile this driver as a module ( = code which can be
11922 inserted in and removed from the running kernel whenever you want),
11923 say M here and read Documentation/modules.txt. This is recommended.
11924 The module will be called 8139cp.o.
11926 RealTek RTL-8139 PCI Fast Ethernet Adapter support
11928 This is a driver for the Fast Ethernet PCI network cards based on
11929 the RTL8139 chips. If you have one of those, say Y and read
11930 <file:Documentation/networking/8139too.txt> as well as the
11931 Ethernet-HOWTO, available from
11932 <http://www.tldp.org/docs.html#howto>.
11934 If you want to compile this driver as a module ( = code which can be
11935 inserted in and removed from the running kernel whenever you want),
11936 say M here and read <file:Documentation/modules.txt>. This is
11937 recommended. The module will be called 8139too.o.
11939 Use PIO instead of MMIO
11941 This instructs the driver to use programmed I/O ports (PIO) instead
11942 of PCI shared memory (MMIO). This can possibly solve some problems
11943 in case your mainboard has memory consistency issues. If unsure,
11946 Support for uncommon RTL-8139 rev. K (automatic channel equalization)
11947 CONFIG_8139TOO_TUNE_TWISTER
11948 This implements a function which might come in handy in case you
11949 are using low quality on long cabling. It is required for RealTek
11950 RTL-8139 revision K boards, and totally unused otherwise. It tries
11951 to match the transceiver to the cable characteristics. This is
11952 experimental since hardly documented by the manufacturer.
11955 Support for older RTL-8129/8130 boards
11956 CONFIG_8139TOO_8129
11957 This enables support for the older and uncommon RTL-8129 and
11958 RTL-8130 chips, which support MII via an external transceiver,
11959 instead of an internal one. Disabling this option will save some
11960 memory by making the code size smaller. If unsure, say Y.
11962 Use older RX-reset method
11963 CONFIG_8139_OLD_RX_RESET
11964 The 8139too driver was recently updated to contain a more rapid
11965 reset sequence, in the face of severe receive errors. This "new"
11966 RX-reset method should be adequate for all boards. But if you
11967 experience problems, you can enable this option to restore the
11968 old RX-reset behavior. If unsure, say N.
11970 SiS 900/7016 PCI Fast Ethernet Adapter support
11972 This is a driver for the Fast Ethernet PCI network cards based on
11973 the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
11974 SiS 630 and SiS 540 chipsets. If you have one of those, say Y and
11975 read the Ethernet-HOWTO, available at
11976 <http://www.tldp.org/docs.html#howto>. Please read
11977 <file:Documentation/networking/sis900.txt> and comments at the
11978 beginning of <file:drivers/net/sis900.c> for more information.
11980 This driver also supports AMD 79C901 HomePNA so that you can use
11981 your phone line as a network cable.
11983 If you want to compile this driver as a module ( = code which can be
11984 inserted in and removed from the running kernel whenever you want),
11985 say M here and read <file:Documentation/modules.txt>. This is
11986 recommended. The module will be called sis900.o.
11988 Packet Engines Yellowfin Gigabit-NIC / Symbios 53c885 support
11990 Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
11991 adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
11992 used by the Beowulf Linux cluster project. See
11993 <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
11994 information about this driver in particular and Beowulf in general.
11996 If you want to compile this driver as a module ( = code which can be
11997 inserted in and removed from the running kernel whenever you want),
11998 say M here and read <file:Documentation/modules.txt>. This is
11999 recommended. The module will be called yellowfin.o.
12001 Realtek 8169 Gigabit Ethernet support
12003 Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
12005 If you want to compile this driver as a module ( = code which can be
12006 inserted in and removed from the running kernel whenever you want),
12007 say M here and read <file:Documentation/modules.txt>. This is
12008 recommended. The module will be called r8169.o.
12010 General Instruments Surfboard 1000
12012 This is a driver for the General Instrument (also known as
12013 NextLevel) SURFboard 1000 internal
12014 cable modem. This is an ISA card which is used by a number of cable
12015 TV companies to provide cable modem access. It's a one-way
12016 downstream-only cable modem, meaning that your upstream net link is
12017 provided by your regular phone modem.
12019 At present this driver only compiles as a module, so say M here if
12020 you have this card. The module will be called sb1000.o. Then read
12021 <file:Documentation/networking/README.sb1000> for information on how
12022 to use this module, as it needs special ppp scripts for establishing
12023 a connection. Further documentation and the necessary scripts can be
12026 <http://www.jacksonville.net/~fventuri/>
12027 <http://home.adelphia.net/~siglercm/sb1000.html>
12028 <http://linuxpower.cx/~cable/>
12030 If you don't have this card, of course say N.
12032 Adaptec Starfire support
12033 CONFIG_ADAPTEC_STARFIRE
12034 Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
12035 adapter. The DuraLAN chip is used on the 64 bit PCI boards from
12036 Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
12039 If you want to compile this driver as a module ( = code which can be
12040 inserted in and removed from the running kernel whenever you want),
12041 say M here and read <file:Documentation/modules.txt>. This is
12042 recommended. The module will be called starfire.o.
12044 Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support
12046 Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
12047 GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
12048 adapter. The driver allows for using the Jumbo Frame option (9000
12049 bytes/frame) however it requires that your switches can handle this
12050 as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
12053 If you want to compile this driver as a module ( = code which can be
12054 inserted in and removed from the running kernel whenever you want),
12055 say M here and read <file:Documentation/modules.txt>. This is
12056 recommended. The module will be called acenic.o.
12058 Omit support for old Tigon I based AceNICs
12059 CONFIG_ACENIC_OMIT_TIGON_I
12060 Say Y here if you only have Tigon II based AceNICs and want to leave
12061 out support for the older Tigon I based cards which are no longer
12062 being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
12063 version)). This will reduce the size of the driver object by
12064 app. 100KB. If you are not sure whether your card is a Tigon I or a
12065 Tigon II, say N here.
12067 The safe and default value for this is N.
12069 Marvell Yukon / SysKonnect SK-98xx and SK-95xx Gigabit Ethernet Adapter family support
12071 Say Y here if you have a Marvell Yukon or SysKonnect SK-98xx/SK-95xx
12072 compliant Gigabit Ethernet Adapter. The following adapters are supported
12074 - 3Com 3C940 Gigabit LOM Ethernet Adapter
12075 - 3Com 3C941 Gigabit LOM Ethernet Adapter
12076 - Allied Telesyn AT-2970LX Gigabit Ethernet Adapter
12077 - Allied Telesyn AT-2970LX/2SC Gigabit Ethernet Adapter
12078 - Allied Telesyn AT-2970SX Gigabit Ethernet Adapter
12079 - Allied Telesyn AT-2970SX/2SC Gigabit Ethernet Adapter
12080 - Allied Telesyn AT-2970TX Gigabit Ethernet Adapter
12081 - Allied Telesyn AT-2970TX/2TX Gigabit Ethernet Adapter
12082 - Allied Telesyn AT-2971SX Gigabit Ethernet Adapter
12083 - Allied Telesyn AT-2971T Gigabit Ethernet Adapter
12084 - DGE-530T Gigabit Ethernet Adapter
12085 - EG1032 v2 Instant Gigabit Network Adapter
12086 - EG1064 v2 Instant Gigabit Network Adapter
12087 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Abit)
12088 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Albatron)
12089 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Asus)
12090 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (ECS)
12091 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Epox)
12092 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Foxconn)
12093 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Gigabyte)
12094 - Marvell 88E8001 Gigabit LOM Ethernet Adapter (Iwill)
12095 - Marvell RDK-8001 Adapter
12096 - Marvell RDK-8002 Adapter
12097 - Marvell RDK-8003 Adapter
12098 - Marvell RDK-8004 Adapter
12099 - Marvell RDK-8006 Adapter
12100 - Marvell RDK-8007 Adapter
12101 - Marvell RDK-8008 Adapter
12102 - Marvell RDK-8009 Adapter
12103 - Marvell RDK-8010 Adapter
12104 - Marvell RDK-8011 Adapter
12105 - Marvell RDK-8012 Adapter
12106 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (32 bit)
12107 - Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (64 bit)
12108 - N-Way PCI-Bus Giga-Card 1000/100/10Mbps(L)
12109 - SK-9521 10/100/1000Base-T Adapter
12110 - SK-9521 V2.0 10/100/1000Base-T Adapter
12111 - SK-9821 Gigabit Ethernet Server Adapter (SK-NET GE-T)
12112 - SK-9821 V2.0 Gigabit Ethernet 10/100/1000Base-T Adapter
12113 - SK-9822 Gigabit Ethernet Server Adapter (SK-NET GE-T dual link)
12114 - SK-9841 Gigabit Ethernet Server Adapter (SK-NET GE-LX)
12115 - SK-9841 V2.0 Gigabit Ethernet 1000Base-LX Adapter
12116 - SK-9842 Gigabit Ethernet Server Adapter (SK-NET GE-LX dual link)
12117 - SK-9843 Gigabit Ethernet Server Adapter (SK-NET GE-SX)
12118 - SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
12119 - SK-9844 Gigabit Ethernet Server Adapter (SK-NET GE-SX dual link)
12120 - SK-9851 V2.0 Gigabit Ethernet 1000Base-SX Adapter
12121 - SK-9861 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition)
12122 - SK-9861 V2.0 Gigabit Ethernet 1000Base-SX Adapter
12123 - SK-9862 Gigabit Ethernet Server Adapter (SK-NET GE-SX Volition dual link)
12124 - SK-9871 Gigabit Ethernet Server Adapter (SK-NET GE-ZX)
12125 - SK-9871 V2.0 Gigabit Ethernet 1000Base-ZX Adapter
12126 - SK-9872 Gigabit Ethernet Server Adapter (SK-NET GE-ZX dual link)
12127 - SMC EZ Card 1000 (SMC9452TXV.2)
12129 The adapters support Jumbo Frames.
12130 The dual link adapters support link-failover and dual port features.
12131 Both Marvell Yukon and SysKonnect SK-98xx/SK-95xx adapters support
12132 the scatter-gather functionality with sendfile(). Please refer to
12133 Documentation/networking/sk98lin.txt for more information about
12134 optional driver parameters.
12135 Questions concerning this driver may be addressed to:
12136 linux@syskonnect.de
12138 If you want to compile this driver as a module ( = code which can be
12139 inserted in and removed from the running kernel whenever you want),
12140 say M here and read Documentation/modules.txt. This is recommended.
12141 The module will be called sk98lin.o.
12146 Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also
12147 <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
12149 This chip is also used by Apple under the name GMAC in all their recent
12150 machines starting with the first iBook. This includes all AGP capable
12151 Apple machines except some early G4s and iMacs that still used a
12152 Tulip chip. This driver obsoletes the GMAC driver for these machines.
12154 If you want to compile the driver as a module ( = code which can be
12155 inserted in and removed from the running kernel whenever you want),
12156 say M here and read <file:Documentation/modules.txt>. The module
12157 will be called sungem.o.
12159 Broadcom Tigon3 support
12161 This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
12163 If you want to compile this driver as a module ( = code which can be
12164 inserted in and removed from the running kernel whenever you want),
12165 say M here and read <file:Documentation/modules.txt>. This is
12166 recommended. The module will be called tg3.o.
12168 MV-64340 Ethernet support
12170 This driver supports the Marvell Discovery II MV64340 device
12171 as an Ethernet controller. Say Y here and select Port 0,1,2
12172 as needed. Otherwise, say N.
12175 CONFIG_MV64340_ETH_0
12176 Enable port 0 on the MV64340 Ethernet controller.
12179 CONFIG_MV64340_ETH_1
12180 Enable port 1 on the MV64340 Ethernet controller.
12183 CONFIG_MV64340_ETH_2
12184 Enable port 2 on the MV64340 Ethernet controller.
12186 MyriCOM Gigabit Ethernet support
12188 This driver supports MyriCOM Sbus gigabit Ethernet cards.
12190 If you want to compile this driver as a module ( = code which can be
12191 inserted in and removed from the running kernel whenever you want),
12192 say M here and read <file:Documentation/modules.txt>. This is
12193 recommended. The module will be called myri_sbus.o.
12195 D-Link 2000-based Gigabit Ethernet support
12197 This driver supports D-Link 2000-based gigabit ethernet cards, which
12199 D-Link DGE-550T Gigabit Ethernet Adapter.
12200 D-Link DL2000-based Gigabit Ethernet Adapter.
12202 If you want to compile this driver as a module ( = code which can be
12203 inserted in and removed from the running kernel whenever you want),
12204 say M here and read <file:Documentation/modules.txt>. This is
12205 recommended. The module will be called dl2k.o.
12207 EtherExpress Pro/100 support (e100, Alternate Intel driver)
12209 This driver supports Intel(R) PRO/100 family of adapters.
12210 To verify that your adapter is supported, find the board ID number
12211 on the adapter. Look for a label that has a barcode and a number
12212 in the format 123456-001 (six digits hyphen three digits).
12214 Use the above information and the Adapter & Driver ID Guide at:
12216 http://support.intel.com/support/network/adapter/pro100/21397.htm
12218 to identify the adapter.
12220 For the latest Intel PRO/100 network driver for Linux, see:
12222 http://appsr.intel.com/scripts-df/support_intel.asp
12224 More specific information on configuring the driver is in
12225 <file:Documentation/networking/e100.txt>.
12227 This driver is also available as a module ( = code which can be
12228 inserted in and removed from the running kernel whenever you want).
12229 The module will be called e100.o. If you want to compile it as a
12230 module, say M here and read <file:Documentation/modules.txt> as well
12231 as <file:Documentation/networking/net-modules.txt>.
12233 Intel(R) PRO/1000 Gigabit Ethernet support
12235 This driver supports Intel(R) PRO/1000 gigabit ethernet family of
12236 adapters. For more information on how to identify your adapter, go to the
12237 Adapter & Driver ID Guide at:
12239 <http://support.intel.com/support/network/adapter/pro100/21397.htm>
12241 For general information and support, go to the Intel support
12244 <http://support.intel.com>
12246 More specific information on configuring the driver is in
12247 <file:Documentation/networking/e1000.txt>.
12249 This driver is also available as a module ( = code which can be
12250 inserted in and removed from the running kernel whenever you want).
12251 The module will be called e1000.o. If you want to compile it as a
12252 module, say M here and read <file:Documentation/modules.txt> as well
12253 as <file:Documentation/networking/net-modules.txt>.
12256 NAPI is a new driver API designed to reduce CPU and interrupt load
12257 when the driver is receiving lots of packets from the card. It is
12258 still somewhat experimental and thus not yet enabled by default.
12260 If your estimated Rx load is 10kpps or more, or if the card will be
12261 deployed on potentially unfriendly networks (e.g. in a firewall),
12264 See <file:Documentation/networking/NAPI_HOWTO.txt> for more
12267 If in doubt, say N.
12269 AMD LANCE and PCnet (AT1500 and NE2100) support
12271 If you have a network (Ethernet) card of this type, say Y and read
12272 the Ethernet-HOWTO, available from
12273 <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
12276 If you want to compile this driver as a module ( = code which can be
12277 inserted in and removed from the running kernel whenever you want),
12278 say M here and read <file:Documentation/modules.txt>. This is
12279 recommended. The module will be called lance.o.
12282 CONFIG_SGI_IOC3_ETH
12283 If you have a network (Ethernet) card of this type, say Y and read
12284 the Ethernet-HOWTO, available from
12285 <http://www.tldp.org/docs.html#howto>.
12287 National Semiconductor DP83902AV support
12289 Support for cards based on the National Semiconductor DP83902AV
12290 ST-NIC Serial Network Interface Controller for Twisted Pair. This
12291 is a 10Mbit/sec Ethernet controller. Product overview and specs at
12292 <http://www.national.com/pf/DP/DP83902A.html>.
12297 CONFIG_NET_VENDOR_3COM
12298 If you have a network (Ethernet) card belonging to this class, say Y
12299 and read the Ethernet-HOWTO, available from
12300 <http://www.tldp.org/docs.html#howto>.
12302 Note that the answer to this question doesn't directly affect the
12303 kernel: saying N will just cause the configurator to skip all
12304 the questions about 3COM cards. If you say Y, you will be asked for
12305 your specific card in the following questions.
12307 3c501 "EtherLink" support
12309 If you have a network (Ethernet) card of this type, say Y and read
12310 the Ethernet-HOWTO, available from
12311 <http://www.tldp.org/docs.html#howto>. Also, consider buying a
12312 new card, since the 3c501 is slow, broken, and obsolete: you will
12313 have problems. Some people suggest to ping ("man ping") a nearby
12314 machine every minute ("man cron") when using this card.
12316 This driver is also available as a module ( = code which can be
12317 inserted in and removed from the running kernel whenever you want).
12318 The module will be called 3c501.o. If you want to compile it as a
12319 module, say M here and read <file:Documentation/modules.txt> as well
12320 as <file:Documentation/networking/net-modules.txt>.
12322 3c503 "EtherLink II" support
12324 If you have a network (Ethernet) card of this type, say Y and read
12325 the Ethernet-HOWTO, available from
12326 <http://www.tldp.org/docs.html#howto>.
12328 This driver is also available as a module ( = code which can be
12329 inserted in and removed from the running kernel whenever you want).
12330 The module will be called 3c503.o. If you want to compile it as a
12331 module, say M here and read <file:Documentation/modules.txt> as well
12332 as <file:Documentation/networking/net-modules.txt>.
12334 3c505 "EtherLink Plus" support
12336 Information about this network (Ethernet) card can be found in
12337 <file:Documentation/networking/3c505.txt>. If you have a card of
12338 this type, say Y and read the Ethernet-HOWTO, available from
12339 <http://www.tldp.org/docs.html#howto>.
12341 If you want to compile this as a module ( = code which can be
12342 inserted in and removed from the running kernel whenever you want),
12343 say M here and read <file:Documentation/modules.txt> as well as
12344 <file:Documentation/networking/net-modules.txt>. The module will be
12347 3c507 (EtherLink 16) support
12349 If you have a network (Ethernet) card of this type, say Y and read
12350 the Ethernet-HOWTO, available from
12351 <http://www.tldp.org/docs.html#howto>.
12353 This driver is also available as a module ( = code which can be
12354 inserted in and removed from the running kernel whenever you want).
12355 The module will be called 3c507.o. If you want to compile it as a
12356 module, say M here and read <file:Documentation/modules.txt> as well
12357 as <file:Documentation/networking/net-modules.txt>.
12359 3c523 "EtherlinkMC" support
12361 If you have a network (Ethernet) card of this type, say Y and read
12362 the Ethernet-HOWTO, available from
12363 <http://www.tldp.org/docs.html#howto>.
12365 This driver is also available as a module ( = code which can be
12366 inserted in and removed from the running kernel whenever you want).
12367 The module will be called 3c523.o. If you want to compile it as a
12368 module, say M here and read <file:Documentation/modules.txt> as well
12369 as <file:Documentation/networking/net-modules.txt>.
12371 3c527 "EtherLink/MC 32" support
12373 If you have a network (Ethernet) card of this type, say Y and read
12374 the Ethernet-HOWTO, available from
12375 <http://www.tldp.org/docs.html#howto>.
12377 This driver is also available as a module ( = code which can be
12378 inserted in and removed from the running kernel whenever you want).
12379 The module will be called 3c527.o. If you want to compile it as a
12380 module, say M here and read <file:Documentation/modules.txt> as well
12381 as <file:Documentation/networking/net-modules.txt>.
12383 3c509/3c529 (MCA)/3c579 "EtherLink III" support
12385 If you have a network (Ethernet) card belonging to the 3Com
12386 EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
12387 from <http://www.tldp.org/docs.html#howto>.
12389 If your card is not working you may need to use the DOS
12390 setup disk to disable Plug & Play mode, and to select the default
12393 If you want to compile this as a module ( = code which can be
12394 inserted in and removed from the running kernel whenever you want),
12395 say M here and read <file:Documentation/modules.txt> as well as
12396 <file:Documentation/networking/net-modules.txt>. The module will be
12399 3c515 ISA Fast EtherLink
12401 If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
12402 network card, say Y and read the Ethernet-HOWTO, available from
12403 <http://www.tldp.org/docs.html#howto>.
12405 If you want to compile this as a module ( = code which can be
12406 inserted in and removed from the running kernel whenever you want),
12407 say M here and read <file:Documentation/modules.txt> as well as
12408 <file:Documentation/networking/net-modules.txt>. The module will be
12411 3c590/3c900 series (592/595/597) "Vortex/Boomerang/Cyclone" support
12413 This option enables driver support for a large number of 10mbps and
12414 10/100mbps EISA, PCI and PCMCIA 3Com network cards:
12416 "Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
12417 "Boomerang" (EtherLink XL 3c900 or 3c905) PCI
12418 "Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus
12419 "Tornado" (3c905) PCI
12420 "Hurricane" (3c555/3cSOHO) PCI
12422 If you have such a card, say Y and read the Ethernet-HOWTO,
12423 available from <http://www.tldp.org/docs.html#howto>. More
12424 specific information is in
12425 <file:Documentation/networking/vortex.txt> and in the comments at
12426 the beginning of <file:drivers/net/3c59x.c>.
12428 If you want to compile the driver as a module ( = code which can be
12429 inserted in and removed from the running kernel whenever you want),
12430 say M here and read <file:Documentation/modules.txt>. The module
12431 will be called 3c59x.o.
12433 3cr990 series "Typhoon" support
12435 This option enables driver support for the 3cr990 series of cards:
12437 3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
12438 3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
12439 3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
12441 If you have a network (Ethernet) card of this type, say Y and read
12442 the Ethernet-HOWTO, available from
12443 <http://www.linuxdoc.org/docs.html#howto>.
12445 This driver is also available as a module ( = code which can be
12446 inserted in and removed from the running kernel whenever you want).
12447 The module will be called typhoon.o. If you want to compile it as a
12448 module, say M here and read <file:Documentation/modules.txt> as well
12449 as <file:Documentation/networking/net-modules.txt>.
12453 If your network (Ethernet) card hasn't been mentioned yet and its
12454 bus system (that's the way the cards talks to the other components
12455 of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
12456 Make sure you know the name of your card. Read the Ethernet-HOWTO,
12457 available from <http://www.tldp.org/docs.html#howto>.
12461 Note that the answer to this question doesn't directly affect the
12462 kernel: saying N will just cause the configurator to skip all
12463 the remaining ISA network card questions. If you say Y, you will be
12464 asked for your specific card in the following questions.
12466 Generic ARCnet support
12468 If you have a network card of this type, say Y and check out the
12469 (arguably) beautiful poetry in
12470 <file:Documentation/networking/arcnet.txt>.
12472 You need both this driver, and the driver for the particular ARCnet
12473 chipset of your card. If you don't know, then it's probably a
12474 COM90xx type card, so say Y (or M) to "ARCnet COM90xx chipset
12477 You might also want to have a look at the Ethernet-HOWTO, available
12478 from <http://www.tldp.org/docs.html#howto>(even though ARCnet
12479 is not really Ethernet).
12481 This driver is also available as a module ( = code which can be
12482 inserted in and removed from the running kernel whenever you want).
12483 The module will be called arcnet.o. If you want to compile it as a
12484 module, say M here and read <file:Documentation/modules.txt> as well
12485 as <file:Documentation/networking/net-modules.txt>.
12487 Enable old ARCNet packet format (RFC 1051)
12489 This allows you to use RFC1051 with your ARCnet card via the virtual
12490 arc0s device. You only need arc0s if you want to talk to ARCnet
12491 software complying with the "old" standard, specifically, the DOS
12492 arcnet.com packet driver, Amigas running AmiTCP, and some variants
12493 of NetBSD. You do not need to say Y here to communicate with
12494 industry-standard RFC1201 implementations, like the arcether.com
12495 packet driver or most DOS/Windows ODI drivers. RFC1201 is included
12496 automatically as the arc0 device. Please read the ARCnet
12497 documentation in <file:Documentation/networking/arcnet.txt> for more
12498 information about using arc0e and arc0s.
12500 If you want to compile the driver as a module ( = code which can be
12501 inserted in and removed from the running kernel whenever you want),
12502 say M here and read <file:Documentation/modules.txt>. The module
12503 will be called rfc1051.o.
12505 Enable standard ARCNet packet format (RFC 1201)
12507 This allows you to use RFC1201 with your ARCnet card via the virtual
12508 arc0 device. You need to say Y here to communicate with
12509 industry-standard RFC1201 implementations, like the arcether.com
12510 packet driver or most DOS/Windows ODI drivers. Please read the
12511 ARCnet documentation in <file:Documentation/networking/arcnet.txt>
12512 for more information about using arc0.
12514 If you want to compile the driver as a module ( = code which can be
12515 inserted in and removed from the running kernel whenever you want),
12516 say M here and read <file:Documentation/modules.txt>. The module
12517 will be called rfc1201.o.
12519 Enable raw mode packet interface
12521 ARCnet "raw mode" packet encapsulation, no soft headers. Unlikely
12522 to work unless talking to a copy of the same Linux arcnet driver,
12523 but perhaps marginally faster in that case.
12525 If you want to compile the driver as a module ( = code which can be
12526 inserted in and removed from the running kernel whenever you want),
12527 say M here and read <file:Documentation/modules.txt>. The module
12528 will be called arc-rawmode.o.
12530 ARCnet COM90xx (normal) chipset driver
12531 CONFIG_ARCNET_COM90xx
12532 This is the chipset driver for the standard COM90xx cards. If you
12533 have always used the old ARCnet driver without knowing what type of
12534 card you had, this is probably the one for you.
12536 This driver is also available as a module ( = code which can be
12537 inserted in and removed from the running kernel whenever you want).
12538 The module will be called com90xx.o. If you want to compile it as a
12539 module, say M here and read <file:Documentation/modules.txt> as well
12540 as <file:Documentation/networking/net-modules.txt>.
12542 ARCnet COM90xx (IO mapped) chipset driver
12543 CONFIG_ARCNET_COM90xxIO
12544 This is the chipset driver for the COM90xx cards, using them in
12545 IO-mapped mode instead of memory-mapped mode. This is slower than
12546 the normal driver. Only use it if your card doesn't support shared
12549 This driver is also available as a module ( = code which can be
12550 inserted in and removed from the running kernel whenever you want).
12551 The module will be called com90io.o. If you want to compile it as a
12552 module, say M here and read <file:Documentation/modules.txt> as well
12553 as <file:Documentation/networking/net-modules.txt>.
12555 ARCnet COM90xx (RIM I) chipset driver
12556 CONFIG_ARCNET_RIM_I
12557 This is yet another chipset driver for the COM90xx cards, but this
12558 time only using memory-mapped mode, and no IO ports at all. This
12559 driver is completely untested, so if you have one of these cards,
12560 please mail dwmw2@infradead.org, especially if it works!
12562 This driver is also available as a module ( = code which can be
12563 inserted in and removed from the running kernel whenever you
12564 want). The module will be called arc-rimi.o. If you want to compile
12565 it as a module, say M here and read <file:Documentation/modules.txt>
12566 as well as <file:Documentation/networking/net-modules.txt>.
12568 ARCnet COM20020 chipset driver
12569 CONFIG_ARCNET_COM20020
12570 This is the driver for the new COM20020 chipset. It supports such
12571 things as promiscuous mode, so packet sniffing is possible, and
12572 extra diagnostic information.
12574 This driver is also available as a module ( = code which can be
12575 inserted in and removed from the running kernel whenever you want).
12576 The module will be called com20020.o. If you want to compile it as
12577 a module, say M here and read <file:Documentation/modules.txt> as
12578 well as <file:Documentation/networking/net-modules.txt>.
12580 Cabletron E21xx support
12582 If you have a network (Ethernet) card of this type, say Y and read
12583 the Ethernet-HOWTO, available from
12584 <http://www.tldp.org/docs.html#howto>.
12586 This driver is also available as a module ( = code which can be
12587 inserted in and removed from the running kernel whenever you want).
12588 The module will be called e2100.o. If you want to compile it as a
12589 module, say M here and read <file:Documentation/modules.txt> as well
12590 as <file:Documentation/networking/net-modules.txt>.
12592 Broadcom 4400 ethernet support (EXPERIMENTAL)
12594 If you have a network (Ethernet) controller of this type, say Y and
12595 read the Ethernet-HOWTO, available from
12596 <http://www.tldp.org/docs.html#howto>.
12598 If you want to compile this as a module ( = code which can be
12599 inserted in and removed from the running kernel whenever you want),
12600 say M here and read <file:Documentation/modules.txt> as well as
12601 <file:Documentation/networking/net-modules.txt>. The module will be
12604 nForce Ethernet support (EXPERIMENTAL)
12606 If you have a network (Ethernet) controller of this type, say Y and
12607 read the Ethernet-HOWTO, available from
12608 <http://www.tldp.org/docs.html#howto>.
12610 To compile this driver as a module, choose M here and read
12611 <file:Documentation/networking/net-modules.txt>. The module will be
12612 called forcedeth.o.
12614 CS89x0 support (Daynaport CS and LC cards)
12616 Support for CS89x0 chipset based Ethernet cards. If you have a
12617 network (Ethernet) card of this type, say Y and read the
12618 Ethernet-HOWTO, available from
12619 <http://www.tldp.org/docs.html#howto> as well as
12620 <file:Documentation/networking/cs89x0.txt>.
12622 If you want to compile this as a module ( = code which can be
12623 inserted in and removed from the running kernel whenever you want),
12624 say M here and read <file:Documentation/modules.txt> as well as
12625 <file:Documentation/networking/net-modules.txt>. The module will be
12628 DEPCA, DE10x, DE200, DE201, DE202, DE422 support
12630 If you have a network (Ethernet) card of this type, say Y and read
12631 the Ethernet-HOWTO, available from
12632 <http://www.tldp.org/docs.html#howto> as well as
12633 <file:drivers/net/depca.c>.
12635 If you want to compile this as a module ( = code which can be
12636 inserted in and removed from the running kernel whenever you want),
12637 say M here and read <file:Documentation/modules.txt> as well as
12638 <file:Documentation/networking/net-modules.txt>. The module will be
12642 EtherWORKS 3 (DE203, DE204, DE205) support
12644 This driver supports the DE203, DE204 and DE205 network (Ethernet)
12645 cards. If this is for you, say Y and read
12646 <file:Documentation/networking/ewrk3.txt> in the kernel source as
12647 well as the Ethernet-HOWTO, available from
12648 <http://www.tldp.org/docs.html#howto>.
12650 If you want to compile this as a module ( = code which can be
12651 inserted in and removed from the running kernel whenever you want),
12652 say M here and read <file:Documentation/modules.txt> as well as
12653 <file:Documentation/networking/net-modules.txt>. The module will be
12658 This is a driver for the SEEQ 8005 network (Ethernet) card. If this
12659 is for you, read the Ethernet-HOWTO, available from
12660 <http://www.tldp.org/docs.html#howto>.
12662 If you want to compile this as a module ( = code which can be
12663 inserted in and removed from the running kernel whenever you want),
12664 say M here and read <file:Documentation/modules.txt> as well as
12665 <file:Documentation/networking/net-modules.txt>. The module will be
12668 AT1700/1720 support
12670 If you have a network (Ethernet) card of this type, say Y and read
12671 the Ethernet-HOWTO, available from
12672 <http://www.tldp.org/docs.html#howto>.
12674 This driver is also available as a module ( = code which can be
12675 inserted in and removed from the running kernel whenever you want).
12676 If you want to compile it as a module, say M here and read
12677 <file:Documentation/modules.txt> as well as
12678 <file:Documentation/networking/net-modules.txt>. The module will be
12681 FMV-181/182/183/184 support
12683 If you have a Fujitsu FMV-181/182/183/184 network (Ethernet) card,
12684 say Y and read the Ethernet-HOWTO, available from
12685 <http://www.tldp.org/docs.html#howto>.
12687 If you use an FMV-183 or FMV-184 and it is not working, you may need
12688 to disable Plug & Play mode of the card.
12690 This driver is also available as a module ( = code which can be
12691 inserted in and removed from the running kernel whenever you want).
12692 The module will be called fmv18x.o. If you want to compile it as a
12693 module, say M here and read <file:Documentation/modules.txt> as well
12694 as <file:Documentation/networking/net-modules.txt>.
12696 EtherExpressPro and EtherExpress 10 (i82595) support
12697 CONFIG_EEXPRESS_PRO
12698 If you have a network (Ethernet) card of this type, say Y. This
12699 driver supports intel i82595{FX,TX} based boards. Note however
12700 that the EtherExpress PRO/100 Ethernet card has its own separate
12701 driver. Please read the Ethernet-HOWTO, available from
12702 <http://www.tldp.org/docs.html#howto>.
12704 This driver is also available as a module ( = code which can be
12705 inserted in and removed from the running kernel whenever you want).
12706 The module will be called eepro.o. If you want to compile it as a
12707 module, say M here and read <file:Documentation/modules.txt> as well
12708 as <file:Documentation/networking/net-modules.txt>.
12710 EtherExpress 16 support
12712 If you have an EtherExpress16 network (Ethernet) card, say Y and
12713 read the Ethernet-HOWTO, available from
12714 <http://www.tldp.org/docs.html#howto>. Note that the Intel
12715 EtherExpress16 card used to be regarded as a very poor choice
12716 because the driver was very unreliable. We now have a new driver
12717 that should do better.
12719 If you want to compile this driver as a module ( = code which can be
12720 inserted in and removed from the running kernel whenever you want),
12721 say M here and read <file:Documentation/modules.txt> as well as
12722 <file:Documentation/networking/net-modules.txt>. The module will be
12725 Packet Engines Hamachi GNIC-II support
12727 If you have a Gigabit Ethernet card of this type, say Y and read
12728 the Ethernet-HOWTO, available from
12729 <http://www.tldp.org/docs.html#howto>.
12731 If you want to compile this as a module ( = code which can be
12732 inserted in and removed from the running kernel whenever you want),
12733 say M here and read <file:Documentation/modules.txt> as well as
12734 <file:Documentation/networking/net-modules.txt>. The module will be
12737 HP PCLAN+ (27247B and 27252A) support
12739 If you have a network (Ethernet) card of this type, say Y and read
12740 the Ethernet-HOWTO, available from
12741 <http://www.tldp.org/docs.html#howto>.
12743 This driver is also available as a module ( = code which can be
12744 inserted in and removed from the running kernel whenever you want).
12745 The module will be called hp-plus.o. If you want to compile it as a
12746 module, say M here and read <file:Documentation/modules.txt> as well
12747 as <file:Documentation/networking/net-modules.txt>.
12749 HP PCLAN (27245 and other 27xxx series) support
12751 If you have a network (Ethernet) card of this type, say Y and read
12752 the Ethernet-HOWTO, available from
12753 <http://www.tldp.org/docs.html#howto>.
12755 This driver is also available as a module ( = code which can be
12756 inserted in and removed from the running kernel whenever you want).
12757 The module will be called hp.o. If you want to compile it as a
12758 module, say M here and read <file:Documentation/modules.txt> as well
12759 as <file:Documentation/networking/net-modules.txt>.
12761 HP 10/100VG PCLAN (ISA, EISA, PCI) support
12763 If you have a network (Ethernet) card of this type, say Y and read
12764 the Ethernet-HOWTO, available from
12765 <http://www.tldp.org/docs.html#howto>.
12767 If you want to compile this as a module ( = code which can be
12768 inserted in and removed from the running kernel whenever you want),
12769 say M here and read <file:Documentation/modules.txt> as well as
12770 <file:Documentation/networking/net-modules.txt>. The module will be
12773 NE2000/NE1000 support
12775 If you have a network (Ethernet) card of this type, say Y and read
12776 the Ethernet-HOWTO, available from
12777 <http://www.tldp.org/docs.html#howto>. Many Ethernet cards
12778 without a specific driver are compatible with NE2000.
12780 If you have a PCI NE2000 card however, say N here and Y to "PCI
12781 NE2000 support", above. If you have a NE2000 card and are running on
12782 an MCA system (a bus system used on some IBM PS/2 computers and
12783 laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
12786 This driver is also available as a module ( = code which can be
12787 inserted in and removed from the running kernel whenever you want).
12788 The module will be called ne.o. If you want to compile it as a
12789 module, say M here and read <file:Documentation/modules.txt> as well
12790 as <file:Documentation/networking/net-modules.txt>.
12792 National Semiconductor DP8381x series PCI Ethernet support
12794 This driver is for the National Semiconductor DP83810 series,
12795 which is used in cards from PureData, NetGear, Linksys
12796 and others, including the 83815 chip.
12797 More specific information and updates are available from
12798 <http://www.scyld.com/network/natsemi.html>.
12800 If you want to compile the driver as a module ( = code which can be
12801 inserted in and removed from the running kernel whenever you want),
12802 say M here and read <file:Documentation/modules.txt>. The module
12803 will be called natsemi.o.
12805 NatSemi workaround for high errors
12806 CONFIG_NATSEMI_CABLE_MAGIC
12807 Some systems see lots of errors with NatSemi ethernet controllers
12808 on certain cables. If you are seeing lots of errors, try turning
12809 this option on. Some boards have incorrect values for supporting
12810 resistors that can cause this change to break. If you turn this
12811 option on and your network suddenly stops working, turn this
12816 If you have a network (Ethernet) card of this type, say Y and read
12817 the Ethernet-HOWTO, available from
12818 <http://www.tldp.org/docs.html#howto>.
12820 NE/2 (ne2000 MCA version) support
12822 If you have a network (Ethernet) card of this type, say Y and read
12823 the Ethernet-HOWTO, available from
12824 <http://www.tldp.org/docs.html#howto>.
12826 This driver is also available as a module ( = code which can be
12827 inserted in and removed from the running kernel whenever you want).
12828 The module will be called ne2.o. If you want to compile it as a
12829 module, say M here and read <file:Documentation/modules.txt> as well
12830 as <file:Documentation/networking/net-modules.txt>.
12834 These are Micro Channel Ethernet adapters. You need to say Y to "MCA
12835 support" in order to use this driver. Supported cards are the SKnet
12836 Junior MC2 and the SKnet MC2(+). The driver automatically
12837 distinguishes between the two cards. Note that using multiple boards
12838 of different type hasn't been tested with this driver. Say Y if you
12839 have one of these Ethernet adapters.
12841 This driver is also available as a module ( = code which can be
12842 inserted in and removed from the running kernel whenever you want).
12843 The module is called sk_mca.o. If you want to compile it as a
12844 module, say M here and read <file:Documentation/modules.txt> as well
12845 as <file:Documentation/networking/net-modules.txt>.
12847 IBM LAN Adapter/A support
12849 This is a Micro Channel Ethernet adapter. You need to set
12850 CONFIG_MCA to use this driver. It is both available as an in-kernel
12851 driver and as a module ( = code which can be inserted in and removed
12852 from the running kernel whenever you want). If you want to compile
12853 it as a module, say M here and read <file:Documentation/modules.txt>
12854 as well as <file:Documentation/networking/net-modules.txt>. The only
12855 currently supported card is the IBM LAN Adapter/A for Ethernet. It
12856 will both support 16K and 32K memory windows, however a 32K window
12857 gives a better security against packet losses. Usage of multiple
12858 boards with this driver should be possible, but has not been tested
12859 up to now due to lack of hardware.
12861 If you want to compile the driver as a module ( = code which can be
12862 inserted in and removed from the running kernel whenever you want),
12863 say M here and read <file:Documentation/modules.txt>. The module
12864 will be called ibmlana.o.
12866 EISA, VLB, PCI and on board controllers
12868 This is another class of network cards which attach directly to the
12869 bus. If you have one of those, say Y and read the Ethernet-HOWTO,
12870 available from <http://www.tldp.org/docs.html#howto>.
12872 Note that the answer to this question doesn't directly affect the
12873 kernel: saying N will just cause the configurator to skip all
12874 the questions about this class of network cards. If you say Y, you
12875 will be asked for your specific card in the following questions. If
12876 you are unsure, say Y.
12878 AMD PCnet32 (VLB and PCI) support
12880 If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
12881 answer Y here and read the Ethernet-HOWTO, available from
12882 <http://www.tldp.org/docs.html#howto>.
12884 This driver is also available as a module ( = code which can be
12885 inserted in and removed from the running kernel whenever you want).
12886 The module will be called pcnet32.o. If you want to compile it as a
12887 module, say M here and read <file:Documentation/modules.txt> as well
12888 as <file:Documentation/networking/net-modules.txt>.
12890 AMD 8111 (new PCI lance) support
12892 If you have an AMD 8111-based PCI lance ethernet card,
12893 answer Y here and read the Ethernet-HOWTO, available from
12894 <http://www.tldp.org/docs.html#howto>.
12896 This driver is also available as a module ( = code which can be
12897 inserted in and removed from the running kernel whenever you want).
12898 The module will be called amd8111e.o. If you want to compile it as a
12899 module, say M here and read <file:Documentation/modules.txt> as well
12900 as <file:Documentation/networking/net-modules.txt>.
12902 Ansel Communications EISA 3200 support
12904 If you have a network (Ethernet) card of this type, say Y and read
12905 the Ethernet-HOWTO, available from
12906 <http://www.tldp.org/docs.html#howto>.
12908 This driver is also available as a module ( = code which can be
12909 inserted in and removed from the running kernel whenever you want).
12910 The module will be called ac3200.o. If you want to compile it as a
12911 module, say M here and read <file:Documentation/modules.txt> as well
12912 as <file:Documentation/networking/net-modules.txt>.
12914 Mylex EISA LNE390A/LNE390B support
12916 If you have a network (Ethernet) card of this type, say Y and read
12917 the Ethernet-HOWTO, available from
12918 <http://www.tldp.org/docs.html#howto>.
12920 This driver is also available as a module ( = code which can be
12921 inserted in and removed from the running kernel whenever you want).
12922 The module will be called lne390.o. If you want to compile it as a
12923 module, say M here and read <file:Documentation/modules.txt> as well
12924 as <file:Documentation/networking/net-modules.txt>.
12926 Novell/Eagle/Microdyne NE3210 EISA support
12928 If you have a network (Ethernet) card of this type, say Y and read
12929 the Ethernet-HOWTO, available from
12930 <http://www.tldp.org/docs.html#howto>. Note that this driver
12931 will NOT WORK for NE3200 cards as they are completely different.
12933 This driver is also available as a module ( = code which can be
12934 inserted in and removed from the running kernel whenever you want).
12935 The module will be called ne3210.o. If you want to compile it as a
12936 module, say M here and read <file:Documentation/modules.txt> as well
12937 as <file:Documentation/networking/net-modules.txt>.
12939 Apricot Xen-II on board Ethernet
12941 If you have a network (Ethernet) controller of this type, say Y and
12942 read the Ethernet-HOWTO, available from
12943 <http://www.tldp.org/docs.html#howto>.
12945 If you want to compile this as a module ( = code which can be
12946 inserted in and removed from the running kernel whenever you want),
12947 say M here and read <file:Documentation/modules.txt> as well as
12948 <file:Documentation/networking/net-modules.txt>. The module will be
12951 Generic DECchip & DIGITAL EtherWORKS PCI/EISA
12953 This is support for the DIGITAL series of PCI/EISA Ethernet cards.
12954 These include the DE425, DE434, DE435, DE450 and DE500 models. If
12955 you have a network card of this type, say Y and read the
12956 Ethernet-HOWTO, available from
12957 <http://www.tldp.org/docs.html#howto>. More specific
12958 information is contained in
12959 <file:Documentation/networking/de4x5.txt>.
12961 This driver is also available as a module ( = code which can be
12962 inserted in and removed from the running kernel whenever you want).
12963 The module will be called de4x5.o. If you want to compile it as a
12964 module, say M here and read <file:Documentation/modules.txt> as well
12965 as <file:Documentation/networking/net-modules.txt>.
12967 DECchip Tulip (dc21x4x) PCI support
12969 This driver is developed for the SMC EtherPower series Ethernet
12970 cards and also works with cards based on the DECchip
12971 21040/21041/21140 (Tulip series) chips. Some LinkSys PCI cards are
12972 of this type. (If your card is NOT SMC EtherPower 10/100 PCI
12973 (smc9332dst), you can also try the driver for "Generic DECchip"
12974 cards, above. However, most people with a network card of this type
12975 will say Y here.) Do read the Ethernet-HOWTO, available from
12976 <http://www.tldp.org/docs.html#howto>. More specific
12977 information is contained in
12978 <file:Documentation/networking/tulip.txt>.
12980 This driver is also available as a module ( = code which can be
12981 inserted in and removed from the running kernel whenever you want).
12982 The module will be called tulip.o. If you want to compile it as a
12983 module, say M here and read <file:Documentation/modules.txt> as well
12984 as <file:Documentation/networking/net-modules.txt>.
12986 Use PCI shared memory for NIC registers
12988 Use PCI shared memory for the NIC registers, rather than going through
12989 the Tulip's PIO (programmed I/O ports). Faster, but could produce
12990 obscure bugs if your mainboard has memory controller timing issues.
12991 If in doubt, say N.
12993 Digi Intl. RightSwitch SE-X support
12995 This is support for the Digi International RightSwitch series of
12996 PCI/EISA Ethernet switch cards. These include the SE-4 and the SE-6
12997 models. If you have a network card of this type, say Y and read the
12998 Ethernet-HOWTO, available from
12999 <http://www.tldp.org/docs.html#howto>. More specific
13000 information is contained in <file:Documentation/networking/dgrs.txt>.
13002 This driver is also available as a module ( = code which can be
13003 inserted in and removed from the running kernel whenever you want).
13004 The module will be called dgrs.o. If you want to compile it as a
13005 module, say M here and read <file:Documentation/modules.txt> as well
13006 as <file:Documentation/networking/net-modules.txt>.
13008 EtherExpress Pro/100 support
13010 If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
13011 card, say Y and read the Ethernet-HOWTO, available from
13012 <http://www.tldp.org/docs.html#howto>.
13014 This driver is also available as a module ( = code which can be
13015 inserted in and removed from the running kernel whenever you want).
13016 The module will be called eepro100.o. If you want to compile it as
13017 a module, say M here and read <file:Documentation/modules.txt> as
13018 well as <file:Documentation/networking/net-modules.txt>.
13020 Use PIO instead of MMIO
13021 CONFIG_EEPRO100_PIO
13022 This instructs the driver to use programmed I/O ports (PIO) instead
13023 of PCI shared memory (MMIO). This can possibly solve some problems
13024 in case your mainboard has memory consistency issues. If unsure,
13027 Enable Power Management
13029 Many Intel EtherExpress PRO/100 PCI network cards are capable
13030 of providing power management capabilities. To make use of these
13031 capabilities, say Y.
13033 WARNING: This option is intended for kernel developers and testers.
13034 It is still very experimental, with some people reporting complete
13037 It is recommended to say N here.
13039 Myson MTD-8xx PCI Ethernet support
13041 Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
13042 cards. Specifications and data at
13043 <http://www.myson.com.hk/mtd/datasheet/>.
13045 If you want to compile the driver as a module ( = code which can be
13046 inserted in and removed from the running kernel whenever you want),
13047 say M here and read <file:Documentation/modules.txt>. The module
13048 will be called fealnx.o.
13050 LP486E on board Ethernet
13052 Say Y here to support the 82596-based on-board Ethernet controller
13053 for the Panther motherboard, which is one of the two shipped in the
13054 Intel Professional Workstation.
13056 If you want to compile the driver as a module ( = code which can be
13057 inserted in and removed from the running kernel whenever you want),
13058 say M here and read <file:Documentation/modules.txt>. The module
13059 will be called lp486e.o.
13061 ICL EtherTeam 16i/32 support
13063 If you have a network (Ethernet) card of this type, say Y and read
13064 the Ethernet-HOWTO, available from
13065 <http://www.tldp.org/docs.html#howto>.
13067 This driver is also available as a module ( = code which can be
13068 inserted in and removed from the running kernel whenever you want).
13069 The module will be called eth16i.o. If you want to compile it as a
13070 module, say M here and read <file:Documentation/modules.txt> as well
13071 as <file:Documentation/networking/net-modules.txt>.
13073 TI ThunderLAN support
13075 If you have a PCI Ethernet network card based on the ThunderLAN chip
13076 which is supported by this driver, say Y and read the
13077 Ethernet-HOWTO, available from
13078 <http://www.tldp.org/docs.html#howto>.
13080 Devices currently supported by this driver are Compaq Netelligent,
13081 Compaq NetFlex and Olicom cards. Please read the file
13082 <file:Documentation/networking/tlan.txt> for more details.
13084 This driver is also available as a module ( = code which can be
13085 inserted in and removed from the running kernel whenever you want).
13086 The module will be called tlan.o. If you want to compile it as a
13087 module, say M here and read <file:Documentation/modules.txt> as well
13088 as <file:Documentation/networking/net-modules.txt>.
13090 Please email feedback to torben.mathiasen@compaq.com.
13094 If you have a VIA "rhine" based network card (Rhine-I (3043) or
13095 Rhine-2 (VT86c100A)), say Y here.
13097 This driver is also available as a module ( = code which can be
13098 inserted in and removed from the running kernel whenever you want).
13099 The module will be called via-rhine.o. If you want to compile it as
13100 a module, say M here and read <file:Documentation/modules.txt> as
13101 well as <file:Documentation/networking/net-modules.txt>.
13103 VIA Rhine MMIO support (EXPERIMENTAL)
13104 CONFIG_VIA_RHINE_MMIO
13105 This instructs the driver to use PCI shared memory (MMIO) instead of
13106 programmed I/O ports (PIO). Enabling this gives an improvement in
13107 processing time in parts of the driver.
13109 It is not known if this works reliably on all "rhine" based cards,
13110 but it has been tested successfully on some DFE-530TX adapters.
13114 Davicom DM910x/DM980x support
13116 This driver is for DM9102(A)/DM9132/DM9801 compatible PCI cards from
13117 Davicom (<http://www.davicom.com.tw/>). If you have such a network
13118 (Ethernet) card, say Y. Some information is contained in the file
13119 <file:Documentation/networking/dmfe.txt>.
13121 This driver is also available as a module ( = code which can be
13122 inserted in and removed from the running kernel whenever you want).
13123 The module will be called dmfe.o. If you want to compile it as a
13124 module, say M here and read <file:Documentation/modules.txt> as well
13125 as <file:Documentation/networking/net-modules.txt>.
13127 Racal-Interlan EISA ES3210 support
13129 If you have a network (Ethernet) card of this type, say Y and read
13130 the Ethernet-HOWTO, available from
13131 <http://www.tldp.org/docs.html#howto>.
13133 This driver is also available as a module ( = code which can be
13134 inserted in and removed from the running kernel whenever you want).
13135 The module will be called es3210.o. If you want to compile it as a
13136 module, say M here and read <file:Documentation/modules.txt> as well
13137 as <file:Documentation/networking/net-modules.txt>.
13141 This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
13142 which is based on the SMC83c17x (EPIC/100).
13143 More specific information and updates are available from
13144 <http://www.scyld.com/network/epic100.html>.
13146 If you want to compile the driver as a module ( = code which can be
13147 inserted in and removed from the running kernel whenever you want),
13148 say M here and read <file:Documentation/modules.txt>. The module
13149 will be called epic100.o.
13151 DEC LANCE Ethernet controller support
13153 This driver is for the series of Ethernet controllers produced by
13154 DEC (now Compaq) based on the AMD Lance chipset, including the
13155 DEPCA series. (This chipset is better known via the NE2100 cards.)
13157 SGI Seeq Ethernet controller support
13159 Say Y here if you have an Seeq based Ethernet network card. This is
13160 used in many Silicon Graphics machines.
13162 Sundance Alta PCI Ethernet support
13164 This driver is for the Sundance "Alta" chip.
13165 More specific information and updates are available from
13166 <http://www.scyld.com/network/sundance.html>.
13168 If you want to compile the driver as a module ( = code which can be
13169 inserted in and removed from the running kernel whenever you want),
13170 say M here and read <file:Documentation/modules.txt>. The module
13171 will be called sundance.o.
13173 Sundance Alta memory-mapped I/O support
13174 CONFIG_SUNDANCE_MMIO
13175 Enable memory-mapped I/O for interaction with Sundance NIC registers.
13176 Do NOT enable this by default, PIO (enabled when MMIO is disabled)
13177 is known to solve bugs on certain chips.
13181 Sun3/Sun3x on-board LANCE support
13183 Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
13184 featured an AMD Lance 10Mbit Ethernet controller on board; say Y
13185 here to compile in the Linux driver for this and enable Ethernet.
13186 General Linux information on the Sun 3 and 3x series (now
13187 discontinued) is at
13188 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
13190 If you're not building a kernel for a Sun 3, say N.
13192 Sun3 on-board Intel 82586 support
13194 This driver enables support for the on-board Intel 82586 based
13195 Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note
13196 that this driver does not support 82586-based adapters on additional
13199 Winbond W89c840 PCI Ethernet support
13201 This driver is for the Winbond W89c840 chip. It also works with
13202 the TX9882 chip on the Compex RL100-ATX board.
13203 More specific information and updates are available from
13204 <http://www.scyld.com/network/drivers.html>.
13206 Zenith Z-Note support
13208 The Zenith Z-Note notebook computer has a built-in network
13209 (Ethernet) card, and this is the Linux driver for it. Note that the
13210 IBM Thinkpad 300 is compatible with the Z-Note and is also supported
13211 by this driver. Read the Ethernet-HOWTO, available from
13212 <http://www.tldp.org/docs.html#howto>.
13214 Philips SAA9730 Ethernet support
13216 The SAA9730 is a combined multimedia and peripheral controller used
13217 in thin clients, Internet access terminals, and diskless
13219 See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
13221 Pocket and portable adapters
13223 Cute little network (Ethernet) devices which attach to the parallel
13224 port ("pocket adapters"), commonly used with laptops. If you have
13225 one of those, say Y and read the Ethernet-HOWTO, available from
13226 <http://www.tldp.org/docs.html#howto>.
13228 If you want to plug a network (or some other) card into the PCMCIA
13229 (or PC-card) slot of your laptop instead (PCMCIA is the standard for
13230 credit card size extension cards used by all modern laptops), you
13231 need the pcmcia-cs package (location contained in the file
13232 <file:Documentation/Changes>) and you can say N here.
13234 Laptop users should read the Linux Laptop home page at
13235 <http://www.cs.utexas.edu/users/kharker/linux-laptop/>.
13237 Note that the answer to this question doesn't directly affect the
13238 kernel: saying N will just cause the configurator to skip all
13239 the questions about this class of network devices. If you say Y, you
13240 will be asked for your specific device in the following questions.
13242 AT-LAN-TEC/RealTek pocket adapter support
13244 This is a network (Ethernet) device which attaches to your parallel
13245 port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
13246 available from <http://www.tldp.org/docs.html#howto>, if you
13247 want to use this. If you intend to use this driver, you should have
13248 said N to the "Parallel printer support", because the two drivers
13249 don't like each other.
13251 If you want to compile this driver as a module however ( = code
13252 which can be inserted in and removed from the running kernel
13253 whenever you want), say M here and read
13254 <file:Documentation/modules.txt>. The module will be called atp.o.
13256 D-Link DE600 pocket adapter support
13258 This is a network (Ethernet) device which attaches to your parallel
13259 port. Read <file:Documentation/networking/DLINK.txt> as well as the
13260 Ethernet-HOWTO, available from
13261 <http://www.tldp.org/docs.html#howto>, if you want to use
13262 this. It is possible to have several devices share a single parallel
13263 port and it is safe to compile the corresponding drivers into the
13266 If you want to compile this driver as a module however ( = code
13267 which can be inserted in and removed from the running kernel
13268 whenever you want), say M here and read
13269 <file:Documentation/modules.txt>.
13270 The module will be called de600.o.
13272 D-Link DE620 pocket adapter support
13274 This is a network (Ethernet) device which attaches to your parallel
13275 port. Read <file:Documentation/networking/DLINK.txt> as well as the
13276 Ethernet-HOWTO, available from
13277 <http://www.tldp.org/docs.html#howto>, if you want to use
13278 this. It is possible to have several devices share a single parallel
13279 port and it is safe to compile the corresponding drivers into the
13282 If you want to compile this driver as a module however ( = code
13283 which can be inserted in and removed from the running kernel
13284 whenever you want), say M here and read
13285 <file:Documentation/modules.txt>.
13286 The module will be called de620.o.
13288 Token Ring driver support
13290 Token Ring is IBM's way of communication on a local network; the
13291 rest of the world uses Ethernet. To participate on a Token Ring
13292 network, you need a special Token ring network card. If you are
13293 connected to such a Token Ring network and want to use your Token
13294 Ring card under Linux, say Y here and to the driver for your
13295 particular card below and read the Token-Ring mini-HOWTO, available
13296 from <http://www.tldp.org/docs.html#howto>. Most people can
13299 IBM Tropic chipset based adapter support
13301 This is support for all IBM Token Ring cards that don't use DMA. If
13302 you have such a beast, say Y and read the Token-Ring mini-HOWTO,
13303 available from <http://www.tldp.org/docs.html#howto>.
13305 Warning: this driver will almost definitely fail if more than one
13306 active Token Ring card is present.
13308 This driver is also available as a module ( = code which can be
13309 inserted in and removed from the running kernel whenever you want).
13310 The module will be called ibmtr.o. If you want to compile it as a
13311 module, say M here and read <file:Documentation/modules.txt>.
13313 IBM Olympic chipset PCI adapter support
13315 This is support for all non-Lanstreamer IBM PCI Token Ring Cards.
13316 Specifically this is all IBM PCI, PCI Wake On Lan, PCI II, PCI II
13317 Wake On Lan, and PCI 100/16/4 adapters.
13319 If you have such an adapter, say Y and read the Token-Ring
13320 mini-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
13322 This driver is also available as a module ( = code which can be
13323 inserted in and removed from the running kernel whenever you want).
13324 The module will be called olympic.o. If you want to compile it
13325 as a module, say M here and read <file:Documentation/modules.txt>.
13327 Also read <file:Documentation/networking/olympic.txt> or check the
13328 Linux Token Ring Project site for the latest information at
13329 <http://www.linuxtr.net/>.
13331 IBM Lanstreamer chipset PCI adapter support
13333 This is support for IBM Lanstreamer PCI Token Ring Cards.
13335 If you have such an adapter, say Y and read the Token-Ring
13336 mini-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
13338 This driver is also available as a modules ( = code which can be
13339 inserted in and removed from the running kernel whenever you want).
13340 The modules will be called lanstreamer.o. If you want to compile it
13341 as a module, say M here and read <file:Documentation/modules.txt>.
13343 Generic TMS380 Token Ring ISA/PCI/MCA/EISA adapter support
13345 This driver provides generic support for token ring adapters
13346 based on the Texas Instruments TMS380 series chipsets. This
13347 includes the SysKonnect TR4/16(+) ISA (SK-4190), SysKonnect
13348 TR4/16(+) PCI (SK-4590), SysKonnect TR4/16 PCI (SK-4591),
13349 Compaq 4/16 PCI, Thomas-Conrad TC4048 4/16 PCI, and several
13350 Madge adapters. If you say Y here, you will be asked to select
13351 which cards to support below. If you're using modules, each
13352 class of card will be supported by a separate module.
13354 If you have such an adapter and would like to use it, say Y and
13355 read the Token-Ring mini-HOWTO, available from
13356 <http://www.tldp.org/docs.html#howto>.
13358 Also read the file <file:Documentation/networking/tms380tr.txt> or
13359 check <http://www.auk.cx/tms380tr/>.
13361 This driver is also available as a module ( = code which can be
13362 inserted in and removed from the running kernel whenever you want).
13363 The module will be called tms380tr.o. If you want to compile it
13364 as a module, say M here and read <file:Documentation/modules.txt>.
13366 Generic TMS380 PCI support
13368 This tms380 module supports generic TMS380-based PCI cards.
13370 These cards are known to work:
13371 - Compaq 4/16 TR PCI
13372 - SysKonnect TR4/16 PCI (SK-4590/SK-4591)
13373 - Thomas-Conrad TC4048 PCI 4/16
13374 - 3Com Token Link Velocity
13376 This driver is available as a module ( = code which can be
13377 inserted in and removed from the running kernel whenever you want).
13378 The module will be called tmspci.o. If you want to compile it
13379 as a module, say M here and read <file:Documentation/modules.txt>.
13381 Generic TMS380 ISA support
13383 This tms380 module supports generic TMS380-based ISA cards.
13385 These cards are known to work:
13386 - SysKonnect TR4/16 ISA (SK-4190)
13388 This driver is available as a module ( = code which can be
13389 inserted in and removed from the running kernel whenever you want).
13390 The module will be called tmsisa.o. If you want to compile it
13391 as a module, say M here and read <file:Documentation/modules.txt>.
13393 Madge Smart 16/4 PCI Mk2 support
13395 This tms380 module supports the Madge Smart 16/4 PCI Mk2
13398 This driver is available as a module ( = code which can be
13399 inserted in and removed from the running kernel whenever you want).
13400 The module will be called abyss.o. If you want to compile it
13401 as a module, say M here and read <file:Documentation/modules.txt>.
13403 Madge Smart 16/4 Ringnode MicroChannel
13405 This tms380 module supports the Madge Smart 16/4 MC16 and MC32
13406 MicroChannel adapters.
13408 This driver is available as a module ( = code which can be
13409 inserted in and removed from the running kernel whenever you want).
13410 The module will be called madgemc.o. If you want to compile it
13411 as a module, say M here and read <file:Documentation/modules.txt>.
13413 SMC ISA/MCA Token Ring adapter support
13415 This is support for the ISA and MCA SMC Token Ring cards,
13416 specifically SMC TokenCard Elite (8115T) and SMC TokenCard Elite/A
13417 (8115T/A) adapters.
13419 If you have such an adapter and would like to use it, say Y or M and
13420 read the Token-Ring mini-HOWTO, available from
13421 <http://www.tldp.org/docs.html#howto> and the file
13422 <file:Documentation/networking/smctr.txt>.
13424 This driver is also available as a module ( = code which can be
13425 inserted in and removed from the running kernel whenever you want).
13426 The module will be called smctr.o. If you want to compile it
13427 as a module, say M here and read <file:Documentation/modules.txt>.
13429 3COM 3C359 Token Link Velocity XL PCI adapter support
13431 This is support for the 3Com PCI Velocity XL cards, specifically
13432 the 3Com 3C359, please note this is not for the 3C339 cards, you
13433 should use the tms380 driver instead.
13435 If you have such an adapter, say Y and read the Token-Ring
13436 mini-HOWTO, available from <http://www.tldp.org/docs.html#howto>.
13438 This driver is also available as a module ( = code which can be
13439 inserted in and removed from the running kernel whenever you want).
13440 The module will will be called 3c359.o. If you want to compile it
13441 as a module, say M here and read Documentation/modules.txt.
13443 Also read the file <file:Documentation/networking/3c359.txt> or check the
13444 Linux Token Ring Project site for the latest information at
13445 <http://www.linuxtr.net>
13447 Sun Happy Meal 10/100baseT support
13449 This driver supports the "hme" interface present on most Ultra
13450 systems and as an option on older Sbus systems. This driver supports
13451 both PCI and Sbus devices. This driver also supports the "qfe" quad
13452 100baseT device available in both PCI and Sbus configurations.
13454 This support is also available as a module called sunhme.o ( = code
13455 which can be inserted in and removed from the running kernel
13456 whenever you want). If you want to compile it as a module, say M
13457 here and read <file:Documentation/modules.txt>.
13461 This driver supports the "le" interface present on all 32-bit Sparc
13462 systems, on some older Ultra systems and as an Sbus option. These
13463 cards are based on the AMD Lance chipset, which is better known
13464 via the NE2100 cards.
13466 This support is also available as a module called sunlance.o ( =
13467 code which can be inserted in and removed from the running kernel
13468 whenever you want). If you want to compile it as a module, say M
13469 here and read <file:Documentation/modules.txt>.
13471 Sun BigMAC 10/100baseT support
13473 This driver supports the "be" interface available as an Sbus option.
13474 This is Sun's older 100baseT Ethernet device.
13476 This support is also available as a module called sunbmac.o ( = code
13477 which can be inserted in and removed from the running kernel
13478 whenever you want). If you want to compile it as a module, say M
13479 here and read <file:Documentation/modules.txt>.
13481 Sun QuadEthernet support
13483 This driver supports the "qe" 10baseT Ethernet device, available as
13484 an Sbus option. Note that this is not the same as Quad FastEthernet
13485 "qfe" which is supported by the Happy Meal driver instead.
13487 This support is also available as a module called sunqe.o ( = code
13488 which can be inserted in and removed from the running kernel
13489 whenever you want). If you want to compile it as a module, say M
13490 here and read <file:Documentation/modules.txt>.
13494 The traffic shaper is a virtual network device that allows you to
13495 limit the rate of outgoing data flow over some other network device.
13496 The traffic that you want to slow down can then be routed through
13497 these virtual devices. See
13498 <file:Documentation/networking/shaper.txt> for more information.
13500 An alternative to this traffic shaper is the experimental
13501 Class-Based Queueing (CBQ) scheduling support which you get if you
13502 say Y to "QoS and/or fair queueing" above.
13504 To set up and configure shaper devices, you need the shapecfg
13505 program, available from <ftp://shadow.cabi.net/pub/Linux/> in the
13508 This driver is also available as a module ( = code which can be
13509 inserted in and removed from the running kernel whenever you want).
13510 The module will be called shaper.o. If you want to compile it as a
13511 module, say M here and read <file:Documentation/modules.txt>. If
13514 FDDI driver support
13516 Fiber Distributed Data Interface is a high speed local area network
13517 design; essentially a replacement for high speed Ethernet. FDDI can
13518 run over copper or fiber. If you are connected to such a network and
13519 want a driver for the FDDI card in your computer, say Y here (and
13520 then also Y to the driver for your FDDI card, below). Most people
13523 Digital DEFTA/DEFEA/DEFPA adapter support
13525 This is support for the DIGITAL series of TURBOchannel (DEFTA), EISA
13526 (DEFEA) and PCI (DEFPA) controllers which can connect you to a local
13529 If you want to compile the driver as a module ( = code which can be
13530 inserted in and removed from the running kernel whenever you want),
13531 say M here and read <file:Documentation/modules.txt>. The module
13532 will be called defxx.o.
13534 SysKonnect FDDI PCI support
13536 Say Y here if you have a SysKonnect FDDI PCI adapter.
13537 The following adapters are supported by this driver:
13538 - SK-5521 (SK-NET FDDI-UP)
13539 - SK-5522 (SK-NET FDDI-UP DAS)
13540 - SK-5541 (SK-NET FDDI-FP)
13541 - SK-5543 (SK-NET FDDI-LP)
13542 - SK-5544 (SK-NET FDDI-LP DAS)
13543 - SK-5821 (SK-NET FDDI-UP64)
13544 - SK-5822 (SK-NET FDDI-UP64 DAS)
13545 - SK-5841 (SK-NET FDDI-FP64)
13546 - SK-5843 (SK-NET FDDI-LP64)
13547 - SK-5844 (SK-NET FDDI-LP64 DAS)
13548 - Netelligent 100 FDDI DAS Fibre SC
13549 - Netelligent 100 FDDI SAS Fibre SC
13550 - Netelligent 100 FDDI DAS UTP
13551 - Netelligent 100 FDDI SAS UTP
13552 - Netelligent 100 FDDI SAS Fibre MIC
13554 Read <file:Documentation/networking/skfp.txt> for information about
13557 Questions concerning this driver can be addressed to:
13558 linux@syskonnect.de
13560 If you want to compile this driver as a module ( = code which can be
13561 inserted in and removed from the running kernel whenever you want),
13562 say M here and read <file:Documentation/modules.txt>. This is
13563 recommended. The module will be called skfp.o.
13565 HIgh Performance Parallel Interface (HIPPI) support
13567 HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
13568 1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
13569 can run over copper (25m) or fiber (300m on multi-mode or 10km on
13570 single-mode). HIPPI networks are commonly used for clusters and to
13571 connect to super computers. If you are connected to a HIPPI network
13572 and have a HIPPI network card in your computer that you want to use
13573 under Linux, say Y here (you must also remember to enable the driver
13574 for your HIPPI card below). Most people will say N here.
13576 IBM PowerPC Virtual Ethernet driver support
13578 This driver supports virtual ethernet adapters on newer IBM iSeries
13579 and pSeries systems.
13581 If you want to compile the driver as a module ( = code which can be
13582 inserted in and removed from the running kernel whenever you want),
13583 say M here and read <file:Documentation/modules.txt>. The module
13584 will be called ibmveth.o.
13586 Essential RoadRunner HIPPI PCI adapter support
13588 Say Y here if this is your PCI HIPPI network card.
13590 This driver is also available as a module ( = code which can be
13591 inserted in and removed from the running kernel whenever you want).
13592 The module will be called rrunner.o. If you want to compile it as a
13593 module, say M here and read <file:Documentation/modules.txt>. If
13596 Use large TX/RX rings
13597 CONFIG_ROADRUNNER_LARGE_RINGS
13598 If you say Y here, the RoadRunner driver will preallocate up to 2 MB
13599 of additional memory to allow for fastest operation, both for
13600 transmitting and receiving. This memory cannot be used by any other
13601 kernel code or by user space programs. Say Y here only if you have
13604 Acorn Ether1 support
13606 If you have an Acorn system with one of these (AKA25) network cards,
13607 you should say Y to this option if you wish to use it with Linux.
13609 Acorn/ANT Ether3 support
13611 If you have an Acorn system with one of these network cards, you
13612 should say Y to this option if you wish to use it with Linux.
13614 I-Cubed EtherH support
13616 If you have an Acorn system with one of these network cards, you
13617 should say Y to this option if you wish to use it with Linux.
13619 EBSA-110 Ethernet interface (AM79C961A)
13620 CONFIG_ARM_AM79C961A
13621 If you wish to compile a kernel for the EBSA-110, then you should
13622 always answer Y to this.
13624 Support Thumb instructions
13626 Say Y if you want to have kernel support for ARM Thumb instructions,
13627 fault handlers, and system calls.
13629 The Thumb instruction set is a compressed form of the standard ARM
13630 instruction set resulting in smaller binaries at the expense of
13631 slightly less efficient code.
13633 If you don't know what this all is, saying Y is a safe choice.
13635 Support CD-ROM drives that are not SCSI or IDE/ATAPI
13636 CONFIG_CD_NO_IDESCSI
13637 If you have a CD-ROM drive that is neither SCSI nor IDE/ATAPI, say Y
13638 here, otherwise N. Read the CD-ROM-HOWTO, available from
13639 <http://www.tldp.org/docs.html#howto>.
13641 Note that the answer to this question doesn't directly affect the
13642 kernel: saying N will just cause the configurator to skip all
13643 the questions about these CD-ROM drives. If you are unsure what you
13644 have, say Y and find out whether you have one of the following
13647 For each of these drivers, a file Documentation/cdrom/{driver_name}
13648 exists. Especially in cases where you do not know exactly which kind
13649 of drive you have you should read there. Most of these drivers use a
13650 file drivers/cdrom/{driver_name}.h where you can define your
13651 interface parameters and switch some internal goodies.
13653 All these CD-ROM drivers are also usable as a module ( = code which
13654 can be inserted in and removed from the running kernel whenever you
13655 want). If you want to compile them as module, say M instead of Y and
13656 read <file:Documentation/modules.txt>.
13658 If you want to use any of these CD-ROM drivers, you also have to
13659 answer Y or M to "ISO 9660 CD-ROM file system support" below (this
13660 answer will get "defaulted" for you if you enable any of the Linux
13663 Sony CDU31A/CDU33A CD-ROM support
13665 These CD-ROM drives have a spring-pop-out caddyless drawer, and a
13666 rectangular green LED centered beneath it. NOTE: these CD-ROM
13667 drives will not be auto detected by the kernel at boot time; you
13668 have to provide the interface address as an option to the kernel at
13669 boot time as described in <file:Documentation/cdrom/cdu31a> or fill
13670 in your parameters into <file:drivers/cdrom/cdu31a.c>. Try "man
13671 bootparam" or see the documentation of your boot loader (lilo or
13672 loadlin) about how to pass options to the kernel.
13674 If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
13675 file system support" below, because that's the file system used on
13678 This driver is also available as a module ( = code which can be
13679 inserted in and removed from the running kernel whenever you want).
13680 The module will be called cdu31a.o. If you want to compile it as a
13681 module, say M here and read <file:Documentation/modules.txt>.
13683 Standard Mitsumi [no XA/Multisession] CD-ROM support
13685 This is the older of the two drivers for the older Mitsumi models
13686 LU-005, FX-001 and FX-001D. This is not the right driver for the
13687 FX-001DE and the triple or quad speed models (all these are
13688 IDE/ATAPI models). Please also the file
13689 <file:Documentation/cdrom/mcd>.
13691 With the old LU-005 model, the whole drive chassis slides out for cd
13692 insertion. The FX-xxx models use a motorized tray type mechanism.
13693 Note that this driver does not support XA or MultiSession CDs
13694 (PhotoCDs). There is a new driver (next question) which can do
13695 this. If you want that one, say N here.
13697 If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
13698 file system support" below, because that's the file system used on
13701 This driver is also available as a module ( = code which can be
13702 inserted in and removed from the running kernel whenever you want).
13703 The module will be called mcd.o. If you want to compile it as a
13704 module, say M here and read <file:Documentation/modules.txt>.
13706 IRQ channel for Mitsumi CD-ROM
13708 This allows you to specify the default value of the IRQ used by the
13709 driver. This setting can be overridden by passing the "mcd="
13710 parameter to the kernel at boot time (or at module load time if you
13711 said M to "Standard Mitsumi CD-ROM support").
13713 I/O base address for Mitsumi CD-ROM
13715 This allows you to specify the default value of the I/O base address
13716 used by the driver. This setting can be overridden by passing the
13717 "mcd=" parameter to the kernel at boot time (or at module load time
13718 if you said M to "Standard Mitsumi CD-ROM support").
13720 Mitsumi [XA/MultiSession] CD-ROM support
13722 Use this driver if you want to be able to read XA or MultiSession
13723 CDs (PhotoCDs) as well as ordinary CDs with your Mitsumi LU-005,
13724 FX-001 or FX-001D CD-ROM drive. In addition, this driver uses much
13725 less kernel memory than the old one, if that is a concern. This
13726 driver is able to support more than one drive, but each drive needs
13727 a separate interface card. Please read the file
13728 <file:Documentation/cdrom/mcdx>.
13730 If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
13731 file system support" below, because that's the file system used on
13734 This driver is also available as a module ( = code which can be
13735 inserted in and removed from the running kernel whenever you want).
13736 The module will be called mcdx.o. If you want to compile it as a
13737 module, say M here and read <file:Documentation/modules.txt>.
13739 Matsushita/Panasonic/Creative, Longshine, TEAC CD-ROM support
13741 This driver supports most of the drives which use the Panasonic or
13742 Sound Blaster interface. Please read the file
13743 <file:Documentation/cdrom/sbpcd>.
13745 The Matsushita CR-521, CR-522, CR-523, CR-562, CR-563 drives
13746 (sometimes labeled "Creative"), the Creative Labs CD200, the
13747 Longshine LCS-7260, the "IBM External ISA CD-ROM" (in fact a CR-56x
13748 model), the TEAC CD-55A fall under this category. Some other
13749 "electrically compatible" drives (Vertos, Genoa, some Funai models)
13750 are currently not supported; for the Sanyo H94A drive currently a
13751 separate driver (asked later) is responsible. Most drives have a
13752 uniquely shaped faceplate, with a caddyless motorized drawer, but
13753 without external brand markings. The older CR-52x drives have a
13754 caddy and manual loading/eject, but still no external markings. The
13755 driver is able to do an extended auto-probing for interface
13756 addresses and drive types; this can help to find facts in cases you
13757 are not sure, but can consume some time during the boot process if
13758 none of the supported drives gets found. Once your drive got found,
13759 you should enter the reported parameters into
13760 <file:drivers/cdrom/sbpcd.h> and set "DISTRIBUTION 0" there.
13762 This driver can support up to four CD-ROM controller cards, and each
13763 card can support up to four CD-ROM drives; if you say Y here, you
13764 will be asked how many controller cards you have. If compiled as a
13765 module, only one controller card (but with up to four drives) is
13768 If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
13769 file system support" below, because that's the file system used on
13772 This driver is also available as a module ( = code which can be
13773 inserted in and removed from the running kernel whenever you want).
13774 The module will be called sbpcd.o. If you want to compile it as a
13775 module, say M here and read <file:Documentation/modules.txt>.
13777 Matsushita/Panasonic, ... second CD-ROM controller support
13779 Say Y here only if you have two CD-ROM controller cards of this type
13780 (usually only if you have more than four drives). You should enter
13781 the parameters for the second, third and fourth interface card into
13782 <file:drivers/cdrom/sbpcd.h> before compiling the new kernel. Read
13783 the file <file:Documentation/cdrom/sbpcd>.
13785 Matsushita/Panasonic, ... third CD-ROM controller support
13787 Say Y here only if you have three CD-ROM controller cards of this
13788 type (usually only if you have more than six drives). You should
13789 enter the parameters for the second, third and fourth interface card
13790 into <file:include/linux/sbpcd.h> before compiling the new kernel.
13791 Read the file <file:Documentation/cdrom/sbpcd>.
13793 Matsushita/Panasonic, ... fourth CD-ROM controller support
13795 Say Y here only if you have four CD-ROM controller cards of this
13796 type (usually only if you have more than eight drives). You should
13797 enter the parameters for the second, third and fourth interface card
13798 into <file:include/linux/sbpcd.h> before compiling the new kernel.
13799 Read the file <file:Documentation/cdrom/sbpcd>.
13801 Aztech/Orchid/Okano/Wearnes/TXC/CyDROM CD-ROM support
13803 This is your driver if you have an Aztech CDA268-01A, Orchid
13804 CD-3110, Okano or Wearnes CDD110, Conrad TXC, or CyCD-ROM CR520 or
13805 CR540 CD-ROM drive. This driver -- just like all these CD-ROM
13806 drivers -- is NOT for CD-ROM drives with IDE/ATAPI interfaces, such
13807 as Aztech CDA269-031SE. Please read the file
13808 <file:Documentation/cdrom/aztcd>.
13810 If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
13811 file system support" below, because that's the file system used on
13814 This driver is also available as a module ( = code which can be
13815 inserted in and removed from the running kernel whenever you want).
13816 The module will be called aztcd.o. If you want to compile it as a
13817 module, say M here and read <file:Documentation/modules.txt>.
13819 Sony CDU535 CD-ROM support
13821 This is the driver for the older Sony CDU-535 and CDU-531 CD-ROM
13822 drives. Please read the file <file:Documentation/cdrom/sonycd535>.
13824 If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
13825 file system support" below, because that's the file system used on
13828 This driver is also available as a module ( = code which can be
13829 inserted in and removed from the running kernel whenever you want).
13830 The module will be called sonycd535.o. If you want to compile it as
13831 a module, say M here and read <file:Documentation/modules.txt>.
13833 Goldstar R420 CD-ROM support
13835 If this is your CD-ROM drive, say Y here. As described in the file
13836 <file:Documentation/cdrom/gscd>, you might have to change a setting
13837 in the file <file:drivers/cdrom/gscd.h> before compiling the
13838 kernel. Please read the file <file:Documentation/cdrom/gscd>.
13840 If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
13841 file system support" below, because that's the file system used on
13844 This driver is also available as a module ( = code which can be
13845 inserted in and removed from the running kernel whenever you want).
13846 The module will be called gscd.o. If you want to compile it as a
13847 module, say M here and read <file:Documentation/modules.txt>.
13849 Philips/LMS CM206 CD-ROM support
13851 If you have a Philips/LMS CD-ROM drive cm206 in combination with a
13852 cm260 host adapter card, say Y here. Please also read the file
13853 <file:Documentation/cdrom/cm206>.
13855 If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
13856 file system support" below, because that's the file system used on
13859 This driver is also available as a module ( = code which can be
13860 inserted in and removed from the running kernel whenever you want).
13861 The module will be called cm206.o. If you want to compile it as a
13862 module, say M here and read <file:Documentation/modules.txt>.
13864 Optics Storage DOLPHIN 8000AT CD-ROM support
13866 This is the driver for the 'DOLPHIN' drive with a 34-pin Sony
13867 compatible interface. It also works with the Lasermate CR328A. If
13868 you have one of those, say Y. This driver does not work for the
13869 Optics Storage 8001 drive; use the IDE-ATAPI CD-ROM driver for that
13870 one. Please read the file <file:Documentation/cdrom/optcd>.
13872 If you say Y here, you should also say Y or M to "ISO 9660 CD-ROM
13873 file system support" below, because that's the file system used on
13876 This driver is also available as a module ( = code which can be
13877 inserted in and removed from the running kernel whenever you want).
13878 The module will be called optcd.o. If you want to compile it as a
13879 module, say M here and read <file:Documentation/modules.txt>.
13881 Sanyo CDR-H94A CD-ROM support
13883 If this is your CD-ROM drive, say Y here and read the file
13884 <file:Documentation/cdrom/sjcd>. You should then also say Y or M to
13885 "ISO 9660 CD-ROM file system support" below, because that's the
13886 file system used on CD-ROMs.
13888 This driver is also available as a module ( = code which can be
13889 inserted in and removed from the running kernel whenever you want).
13890 The module will be called sjcd.o. If you want to compile it as a
13891 module, say M here and read <file:Documentation/modules.txt>.
13893 ISP16/MAD16/Mozart soft configurable cdrom interface support
13895 These are sound cards with built-in cdrom interfaces using the OPTi
13896 82C928 or 82C929 chips. Say Y here to have them detected and
13897 possibly configured at boot time. In addition, You'll have to say Y
13898 to a driver for the particular cdrom drive you have attached to the
13899 card. Read <file:Documentation/cdrom/isp16> for details.
13901 This driver is also available as a module ( = code which can be
13902 inserted in and removed from the running kernel whenever you want).
13903 The module will be called isp16.o. If you want to compile it as a
13904 module, say M here and read <file:Documentation/modules.txt>.
13906 iSeries Virtual I/O CD Support
13908 If you are running Linux on an IBM iSeries system and you want to
13909 read a CD drive owned by OS/400, say Y here.
13913 If you say Y here, you will be able to set per user limits for disk
13914 usage (also called disk quotas). Currently, it works only for the
13915 ext2 file system. You need additional software in order to use quota
13916 support (you can download sources from
13917 <http://www.sf.net/projects/linuxquota/>). For further details, read
13918 the Quota mini-HOWTO, available from
13919 <http://www.tldp.org/docs.html#howto>. Probably the quota
13920 support is only useful for multi user systems. If unsure, say N.
13922 VFS v0 quota format support
13924 This quota format allows using quotas with 32-bit UIDs/GIDs. If you
13925 need this functionality say Y here. Note that you will need latest
13926 quota utilities for new quota format with this kernel.
13928 Memory Technology Device (MTD) support
13930 Memory Technology Devices are flash, RAM and similar chips, often
13931 used for solid state file systems on embedded devices. This option
13932 will provide the generic support for MTD drivers to register
13933 themselves with the kernel and for potential users of MTD devices
13934 to enumerate the devices which are present and obtain a handle on
13935 them. It will also allow you to select individual drivers for
13936 particular hardware and users of MTD devices. If unsure, say N.
13938 This driver is also available as a module ( = code which can be
13939 inserted in and removed from the running kernel whenever you want).
13940 If you want to compile it as a module, say M here and read
13941 <file:Documentation/modules.txt>. The module will be called
13944 MTD debugging support
13946 This turns on low-level debugging for the entire MTD sub-system.
13947 Normally, you should say 'N'.
13949 MTD partitioning support
13950 CONFIG_MTD_PARTITIONS
13951 If you have a device which needs to divide its flash chip(s) up
13952 into multiple 'partitions', each of which appears to the user as
13953 a separate MTD device, you require this option to be enabled. If
13956 This driver is also available as a module ( = code which can be
13957 inserted in and removed from the running kernel whenever you want).
13958 If you want to compile it as a module, say M here and read
13959 <file:Documentation/modules.txt>. The module will be called
13962 Note, however, that you don't need this option for the DiskOnChip
13963 devices. Partitioning on NFTL 'devices' is a different - that's the
13964 'normal' form of partitioning used on a block device.
13966 RedBoot partition table parsing
13967 CONFIG_MTD_REDBOOT_PARTS
13968 RedBoot is a ROM monitor and bootloader which deals with multiple
13969 'images' in flash devices by putting a table in the last erase block
13970 of the device, similar to a partition table, which gives the
13971 offsets, lengths and names of all the images stored in the flash.
13973 If you need code which can detect and parse this table, and register
13974 MTD 'partitions' corresponding to each image in the table, enable
13977 You will still need the parsing functions to be called by the driver
13978 for your particular device. It won't happen automatically. The
13979 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
13982 This driver is also available as a module ( = code which can be
13983 inserted in and removed from the running kernel whenever you want).
13984 If you want to compile it as a module, say M here and read
13985 <file:Documentation/modules.txt>. The module will be called
13988 CONFIG_MTD_CMDLINE_PARTS
13989 Allow generic configuration of the MTD paritition tables via the kernel
13990 command line. Multiple flash resources are supported for hardware where
13991 different kinds of flash memory are available.
13993 You will still need the parsing functions to be called by the driver
13994 for your particular device. It won't happen automatically. The
13995 SA1100 map driver (CONFIG_MTD_SA1100) has an option for this, for
13998 The format for the command line is as follows:
14000 mtdparts=<mtddef>[;<mtddef]
14001 <mtddef> := <mtd-id>:<partdef>[,<partdef>]
14002 <partdef> := <size>[@offset][<name>][ro]
14003 <mtd-id> := unique id used in mapping driver/device
14004 <size> := standard linux memsize OR "-" to denote all
14008 Due to the way Linux handles the command line, no spaces are
14009 allowed in the partition definition, including mtd id's and partition
14014 1 flash resource (mtd-id "sa1100"), with 1 single writable partition:
14017 Same flash, but 2 named partitions, the first one being read-only:
14018 mtdparts=sa1100:256k(ARMboot)ro,-(root)
14020 If unsure, say 'N'.
14022 MTD concatenating support
14024 Support for concatenating several MTD devices into a single
14025 (virtual) one. This allows you to have -for example- a JFFS(2)
14026 file system spanning multiple physical flash chips. If unsure,
14029 If compiled as a module, it will be called mtdconcat.o.
14031 ARM Firmware Suite flash layout / partition parsing
14032 CONFIG_MTD_AFS_PARTS
14033 The ARM Firmware Suite allows the user to divide flash devices into
14034 multiple 'images'. Each such image has a header containing its name
14035 and offset/size etc.
14037 If you need code which can detect and parse these tables, and
14038 register MTD 'partitions' corresponding to each image detected,
14039 enable this option.
14041 You will still need the parsing functions to be called by the driver
14042 for your particular device. It won't happen automatically. The
14043 'armflash' map driver (CONFIG_MTD_ARMFLASH) does this, for example.
14045 MTD debugging verbosity (0 = quiet, 3 = noisy)
14046 CONFIG_MTD_DEBUG_VERBOSE
14047 Determines the verbosity level of the MTD debugging messages.
14049 Direct chardevice access to MTD devices
14051 This provides a character device for each MTD device present in
14052 the system, allowing the user to read and write directly to the
14053 memory chips, and also use ioctl() to obtain information about
14054 the device, or to erase parts of it.
14056 This driver is also available as a module ( = code which can be
14057 inserted in and removed from the running kernel whenever you want).
14058 If you want to compile it as a module, say M here and read
14059 <file:Documentation/modules.txt>. The module will be called
14062 Caching block device access to MTD devices
14064 Although most flash chips have an erase size too large to be useful
14065 as block devices, it is possible to use MTD devices which are based
14066 on RAM chips in this manner. This block device is a user of MTD
14067 devices performing that function.
14069 At the moment, it is also required for the Journalling Flash File
14070 System(s) to obtain a handle on the MTD device when it's mounted
14071 (although JFFS and JFFS2 don't actually use any of the functionality
14072 of the mtdblock device).
14074 Later, it may be extended to perform read/erase/modify/write cycles
14075 on flash chips to emulate a smaller block size. Needless to say,
14076 this is very unsafe, but could be useful for file systems which are
14077 almost never written to.
14079 You do not need this option for use with the DiskOnChip devices. For
14080 those, enable NFTL support (CONFIG_NFTL) instead.
14082 This driver is also available as a module ( = code which can be
14083 inserted in and removed from the running kernel whenever you want).
14084 If you want to compile it as a module, say M here and read
14085 <file:Documentation/modules.txt>. The module will be called
14088 Readonly block device access to MTD devices
14089 CONFIG_MTD_BLOCK_RO
14090 This allows you to mount read-only file systems (such as cramfs)
14091 from an MTD device, without the overhead (and danger) of the caching
14094 You do not need this option for use with the DiskOnChip devices. For
14095 those, enable NFTL support (CONFIG_NFTL) instead.
14097 This driver is also available as a module ( = code which can be
14098 inserted in and removed from the running kernel whenever you want).
14099 If you want to compile it as a module, say M here and read
14100 <file:Documentation/modules.txt>. The module will be called
14103 FTL (Flash Translation Layer) support
14105 This provides support for the original Flash Translation Layer which
14106 is part of the PCMCIA specification. It uses a kind of pseudo-
14107 file system on a flash device to emulate a block device with
14108 512-byte sectors, on top of which you put a 'normal' file system.
14110 You may find that the algorithms used in this code are patented
14111 unless you live in the Free World where software patents aren't
14112 legal - in the USA you are only permitted to use this on PCMCIA
14113 hardware, although under the terms of the GPL you're obviously
14114 permitted to copy, modify and distribute the code as you wish. Just
14117 This driver is also available as a module ( = code which can be
14118 inserted in and removed from the running kernel whenever you want).
14119 If you want to compile it as a module, say M here and read
14120 <file:Documentation/modules.txt>. The module will be called
14123 NFTL (NAND Flash Translation Layer) support
14125 This provides support for the NAND Flash Translation Layer which is
14126 used on M-Systems' DiskOnChip devices. It uses a kind of pseudo-
14127 file system on a flash device to emulate a block device with
14128 512-byte sectors, on top of which you put a 'normal' file system.
14130 You may find that the algorithms used in this code are patented
14131 unless you live in the Free World where software patents aren't
14132 legal - in the USA you are only permitted to use this on DiskOnChip
14133 hardware, although under the terms of the GPL you're obviously
14134 permitted to copy, modify and distribute the code as you wish. Just
14137 This driver is also available as a module ( = code which can be
14138 inserted in and removed from the running kernel whenever you want).
14139 If you want to compile it as a module, say M here and read
14140 <file:Documentation/modules.txt>. The module will be called
14143 Write support for NFTL (EXPERIMENTAL)
14145 If you're lucky, this will actually work. Don't whinge if it
14146 doesn't. Send mail to the MTD mailing list
14147 <linux-mtd@lists.infradead.org> if you want to help to make it more
14150 Detect flash chips by Common Flash Interface (CFI) probe
14152 The Common Flash Interface specification was developed by Intel,
14153 AMD and other flash manufactures that provides a universal method
14154 for probing the capabilities of flash devices. If you wish to
14155 support any device that is CFI-compliant, you need to enable this
14156 option. Visit <http://www.amd.com/products/nvd/overview/cfi.html>
14157 for more information on CFI.
14159 This driver is also available as a module ( = code which can be
14160 inserted in and removed from the running kernel whenever you want).
14161 If you want to compile it as a module, say M here and read
14162 <file:Documentation/modules.txt>. The module will be called
14165 CFI Advanced configuration options
14166 CONFIG_MTD_CFI_ADV_OPTIONS
14167 If you need to specify a specific endianness for access to flash
14168 chips, or if you wish to reduce the size of the kernel by including
14169 support for only specific arrangements of flash chips, say 'Y'. This
14170 option does not directly affect the code, but will enable other
14171 configuration options which allow you to do so.
14173 If unsure, say 'N'.
14175 Specific CFI Flash geometry selection
14176 CONFIG_MTD_CFI_GEOMETRY
14177 This option does not affect the code directly, but will enable
14178 some other configuration options which would allow you to reduce
14179 the size of the kernel by including support for only certain
14180 arrangements of CFI chips. If unsure, say 'N' and all options
14181 which are supported by the current code will be enabled.
14183 Support 8-bit buswidth
14185 If you wish to support CFI devices on a physical bus which is
14186 8 bits wide, say 'Y'.
14188 Support 16-bit buswidth
14190 If you wish to support CFI devices on a physical bus which is
14191 16 bits wide, say 'Y'.
14193 Support 32-bit buswidth
14195 If you wish to support CFI devices on a physical bus which is
14196 32 bits wide, say 'Y'.
14199 If you wish to support CFI devices on a physical bus which is
14200 64 bits wide, say 'Y'.
14202 Support 1-chip flash interleave
14204 If your flash chips are not interleaved - i.e. you only have one
14205 flash chip addressed by each bus cycle, then say 'Y'.
14207 Support 2-chip flash interleave
14209 If your flash chips are interleaved in pairs - i.e. you have two
14210 flash chips addressed by each bus cycle, then say 'Y'.
14212 Support 4-chip flash interleave
14214 If your flash chips are interleaved in fours - i.e. you have four
14215 flash chips addressed by each bus cycle, then say 'Y'.
14218 If your flash chips are interleaved in eights - i.e. you have eight
14219 flash chips addressed by each bus cycle, then say 'Y'.
14221 # Choice: mtd_data_swap
14222 Flash cmd/query data swapping
14223 CONFIG_MTD_CFI_NOSWAP
14224 This option defines the way in which the CPU attempts to arrange
14225 data bits when writing the 'magic' commands to the chips. Saying
14226 'NO', which is the default when CONFIG_MTD_CFI_ADV_OPTIONS isn't
14227 enabled, means that the CPU will not do any swapping; the chips
14228 are expected to be wired to the CPU in 'host-endian' form.
14229 Specific arrangements are possible with the BIG_ENDIAN_BYTE and
14230 LITTLE_ENDIAN_BYTE, if the bytes are reversed.
14232 If you have a LART, on which the data (and address) lines were
14233 connected in a fashion which ensured that the nets were as short
14234 as possible, resulting in a bit-shuffling which seems utterly
14235 random to the untrained eye, you need the LART_ENDIAN_BYTE option.
14237 Yes, there really exists something sicker than PDP-endian :)
14239 CFI support for Intel/Sharp Extended Command Set chips
14240 CONFIG_MTD_CFI_INTELEXT
14241 The Common Flash Interface defines a number of different command
14242 sets which a CFI-compliant chip may claim to implement. This code
14243 provides support for one of those command sets, used on Intel
14244 StrataFlash and other parts.
14246 CFI support for AMD/Fujitsu Standard Command Set chips
14247 CONFIG_MTD_CFI_AMDSTD
14248 The Common Flash Interface defines a number of different command
14249 sets which a CFI-compliant chip may claim to implement. This code
14250 provides support for one of those command sets, used on chips
14251 chips including the AMD Am29LV320.
14253 CFI support for Intel/Sharp Standard Commands
14254 CONFIG_MTD_CFI_INTELSTD
14255 The Common Flash Interface defines a number of different command
14256 sets which a CFI-compliant chip may claim to implement. This code
14257 provides support for one of those command sets.
14259 pre-CFI Sharp chip support
14261 This option enables support for flash chips using Sharp-compatible
14262 commands, including some which are not CFI-compatible and hence
14263 cannot be used with the CONFIG_MTD_CFI_INTELxxx options.
14265 This driver is also available as a module ( = code which can be
14266 inserted in and removed from the running kernel whenever you want).
14267 If you want to compile it as a module, say M here and read
14268 <file:Documentation/modules.txt>. The module will be called
14271 AMD compatible flash chip support (non-CFI)
14273 This option enables support for flash chips using AMD-compatible
14274 commands, including some which are not CFI-compatible and hence
14275 cannot be used with the CONFIG_MTD_CFI_AMDSTD option.
14277 It also works on AMD compatible chips that do conform to CFI.
14279 This driver is also available as a module ( = code which can be
14280 inserted in and removed from the running kernel whenever you want).
14281 If you want to compile it as a module, say M here and read
14282 <file:Documentation/modules.txt>. The module will be called
14285 CONFIG_MTD_CFI_STAA
14286 The Common Flash Interface defines a number of different command
14287 sets which a CFI-compliant chip may claim to implement. This code
14288 provides support for one of those command sets.
14290 Support for RAM chips in bus mapping
14292 This option enables basic support for RAM chips accessed through
14293 a bus mapping driver.
14295 This driver is also available as a module ( = code which can be
14296 inserted in and removed from the running kernel whenever you want).
14297 If you want to compile it as a module, say M here and read
14298 <file:Documentation/modules.txt>. The module will be called
14301 Support for ROM chips in bus mapping
14303 This option enables basic support for ROM chips accessed through
14304 a bus mapping driver.
14306 This driver is also available as a module ( = code which can be
14307 inserted in and removed from the running kernel whenever you want).
14308 If you want to compile it as a module, say M here and read
14309 <file:Documentation/modules.txt>. The module will be called
14312 JEDEC device support
14314 Enable older older JEDEC flash interface devices for self
14315 programming flash. It is commonly used in older AMD chips. It is
14316 only called JEDEC because the JEDEC association
14317 <http://www.jedec.org/> distributes the identification codes for the
14318 chips. WARNING!!!! This code does not compile and is incomplete as
14319 are the specific JEDEC devices drivers.
14321 This driver is also available as a module ( = code which can be
14322 inserted in and removed from the running kernel whenever you want).
14323 If you want to compile it as a module, say M here and read
14324 <file:Documentation/modules.txt>. The module will be called
14327 CFI Flash device mapped on StrongARM SA11x0
14329 This enables access to the flash chips on most platforms based on
14330 the SA1100 and SA1110, including the Assabet and the Compaq iPAQ.
14331 If you have such a board, say 'Y'.
14333 Support for Compaq bootldr partition tables on SA11x0
14334 CONFIG_MTD_SA1100_REDBOOT_PARTITIONS
14335 Enabling this option will cause the kernel to look for a RedBoot
14336 FIS (Flash Image System) table in the last erase block of the flash
14337 chips detected. If you are using RedBoot on your SA11x0-based board
14338 and want Linux to present 'partitions' matching the images which
14339 RedBoot has listed, say 'Y'.
14341 Support for Compaq bootldr partition tables on SA11x0
14342 CONFIG_MTD_SA1100_BOOTLDR_PARTITIONS
14343 Enabling this option will cause the kernel to look for a Compaq
14344 bootldr partition table on the flash chips detected. If you are
14345 using the Compaq bootldr on your SA11x0-based board and want Linux
14346 to present 'partitions' matching the images which the bootldr has
14349 Flash chip mapping in physical memory
14351 This provides a 'mapping' driver which allows the CFI probe and
14352 command set driver code to communicate with flash chips which
14353 are mapped physically into the CPU's memory. You will need to
14354 configure the physical address and size of the flash chips on
14355 your particular board as well as the bus width.
14357 This driver is also available as a module ( = code which can be
14358 inserted in and removed from the running kernel whenever you want).
14359 If you want to compile it as a module, say M here and read
14360 <file:Documentation/modules.txt>. The module will be called
14363 Physical start location of flash chip mapping
14364 CONFIG_MTD_PHYSMAP_START
14365 This is the physical memory location at which the flash chips
14366 are mapped on your particular target board. Refer to the
14367 memory map which should hopefully be in the documentation for
14370 Physical length of flash chip mapping
14371 CONFIG_MTD_PHYSMAP_LEN
14372 This is the total length of the mapping of the flash chips on
14373 your particular board. If there is space, or aliases, in the
14374 physical memory map between the chips, this could be larger
14375 than the total amount of flash present. Refer to the memory
14376 map which should hopefully be in the documentation for your
14379 Buswidth of flash in bytes
14380 CONFIG_MTD_PHYSMAP_BUSWIDTH
14381 This is the total width of the data bus of the flash devices
14382 in octets. For example, if you have a data bus width of 32
14383 bits, you would set the bus width octet value to 4. This is
14384 used internally by the CFI drivers.
14386 Flash chip mapping on Sun Microsystems boardsets
14387 CONFIG_MTD_SUN_UFLASH
14388 This provides a 'mapping' driver which supports the way in
14389 which user-programmable flash chips are connected on various
14390 Sun Microsystems boardsets. This driver will require CFI support
14391 in the kernel, so if you did not enable CFI previously, do that now.
14393 Flash chip mapping on Nora
14395 If you had to ask, you don't have one. Say 'N'.
14397 Flash chip mapping on Photron PNC-2000
14399 PNC-2000 is the name of Network Camera product from PHOTRON
14400 Ltd. in Japan. It uses CFI-compliant flash.
14402 Flash chip mapping on RPXlite or CLLF PPC board
14404 The RPXLite PowerPC board has CFI-compliant chips mapped in
14405 a strange sparse mapping. This 'mapping' driver supports that
14406 arrangement, allowing the CFI probe and command set driver code
14407 to communicate with the chips on the RPXLite board. More at
14408 <http://www.embeddedplanet.com/rpx_lite_specification_sheet.htm>.
14410 Flash chip mapping on AMD SC520 CDP board
14411 CONFIG_MTD_SC520CDP
14412 The SC520 CDP board has two banks of CFI-compliant chips and one
14413 Dual-in-line JEDEC chip. This 'mapping' driver supports that
14414 arrangement, implementing three MTD devices.
14416 This driver is also available as a module ( = code which can be
14417 inserted in and removed from the running kernel whenever you want).
14418 If you want to compile it as a module, say M here and read
14419 <file:Documentation/modules.txt>. The module will be called
14422 Flash chip mapping on Arcom Control Systems SBC-MediaGX
14424 This provides a driver for the on-board flash of Arcom Control
14425 Systems' SBC-GXn family of boards, formerly known as SBC-MediaGX.
14426 By default the flash is split into 3 partitions which are accessed
14427 as separate MTD devices. This board utilizes Intel StrataFlash.
14429 <http://www.arcomcontrols.com/products/icp/pc104/processors/>.
14431 CFI Flash device mapped on D-Box2
14433 This enables access routines for the flash chips on the Nokia/Sagem
14434 D-Box 2 board. If you have one of these boards and would like to use
14435 the flash chips on it, say 'Y'.
14437 CFI Flash devices mapped on IBM Redwood
14439 This enables access routines for the flash chips on the IBM
14440 Redwood board. If you have one of these boards and would like to
14441 use the flash chips on it, say 'Y'.
14443 If compiled as a module, it will be called redwood.o.
14445 CFI Flash device mapped on the XScale IQ80310 board
14447 This enables access routines for the flash chips on the Intel XScale
14448 IQ80310 evaluation board. If you have one of these boards and would
14449 like to use the flash chips on it, say 'Y'.
14451 CFI Flash device mapped on AMD NetSc520
14452 CONFIG_MTD_NETSC520
14453 This enables access routines for the flash chips on the AMD NetSc520
14454 demonstration board. If you have one of these boards and would like
14455 to use the flash chips on it, say 'Y'.
14457 Flash chip mapping on Arcom Control Systems ELAN-104NC
14458 CONFIG_MTD_ELAN_104NC
14459 This provides a driver for the on-board flash of the Arcom Control
14460 System's ELAN-104NC development board. By default the flash
14461 is split into 3 partitions which are accessed as separate MTD
14462 devices. This board utilizes Intel StrataFlash. More info at
14463 <http://www.arcomcontrols.com/products/icp/pc104/processors/>.
14465 Flash chip mapping on Compaq iPAQ/Bitsy
14467 This provides a driver for the on-board flash found in Compaq's
14468 iPAQ Palm PC and their research prototype the Itsy. iPAQ info at
14469 <http://www5.compaq.com/products/handhelds/pocketpc/> and the
14470 Itsy <http://www.research.digital.com/wrl/projects/Itsy/index.html>.
14472 Flash chip mapping on Compaq iPAQ/Bitsy
14474 This provides a driver for the flash accessed using Intel's
14475 21285 bridge used with Intel's StrongARM processors. More info at
14476 <http://developer.intel.com/design/bridge/quicklist/dsc-21285.htm>.
14478 Flash chip mapping on ITE QED-4N-S01B, Globespan IVR or custom board
14479 CONFIG_MTD_CSTM_MIPS_IXX
14480 This provides a mapping driver for the Integrated Tecnology Express,
14481 Inc (ITE) QED-4N-S01B eval board and the Globespan IVR Reference
14482 Board. It provides the necessary addressing, length, buswidth, vpp
14483 code and addition setup of the flash device for these boards. In
14484 addition, this mapping driver can be used for other boards via
14485 setting of the CONFIG_MTD_CSTM_MIPS_IXX_START/LEN/BUSWIDTH
14486 parameters. This mapping will provide one mtd device using one
14487 partition. The start address can be offset from the beginning of
14488 flash and the len can be less than the total flash device size to
14489 allow a window into the flash. Both CFI and JEDEC probes are
14492 Physical start location of flash chip mapping
14493 CONFIG_MTD_CSTM_MIPS_IXX_START
14494 This is the physical memory location that the MTD driver will
14495 use for the flash chips on your particular target board.
14496 Refer to the memory map which should hopefully be in the
14497 documentation for your board.
14499 Physical length of flash chip mapping
14500 CONFIG_MTD_CSTM_MIPS_IXX_LEN
14501 This is the total length that the MTD driver will use for the
14502 flash chips on your particular board. Refer to the memory
14503 map which should hopefully be in the documentation for your
14506 Physical bus width of flash mapping in bytes
14507 CONFIG_MTD_CSTM_MIPS_IXX_BUSWIDTH
14508 This is the total bus width of the mapping of the flash chips
14509 on your particular board.
14511 JEDEC Flash device mapped on Mixcom piggyback card
14513 This supports the paging arrangement for access to flash chips
14514 on the MixCOM piggyback card, allowing the flash chip drivers
14515 to get on with their job of driving the flash chips without
14516 having to know about the paging. If you have one of these boards,
14517 you probably want to enable this mapping driver. More info is at
14518 <http://www.itc.hu/>.
14520 JEDEC Flash device mapped on Octagon 5066 SBC
14522 This provides a 'mapping' driver which supports the way in which
14523 the flash chips are connected in the Octagon-5066 Single Board
14524 Computer. More information on the board is available at
14525 <http://www.octagonsystems.com/Products/5066/5066.html>.
14527 This driver is also available as a module ( = code which can be
14528 inserted in and removed from the running kernel whenever you want).
14529 If you want to compile it as a module, say M here and read
14530 <file:Documentation/modules.txt>. The module will be called
14533 JEDEC Flash device mapped on Tempustech VMAX SBC301
14535 This provides a 'mapping' driver which supports the way in which
14536 the flash chips are connected in the Tempustech VMAX SBC301 Single
14537 Board Computer. More information on the board is available at
14538 <http://www.tempustech.com/tt301.htm>.
14540 This driver is also available as a module ( = code which can be
14541 inserted in and removed from the running kernel whenever you want).
14542 If you want to compile it as a module, say M here and read
14543 <file:Documentation/modules.txt>. The module will be called
14546 Support for NAND flash devices
14548 This enables support for accessing all type of NAND flash
14551 This driver is also available as a module ( = code which can be
14552 inserted in and removed from the running kernel whenever you want).
14553 If you want to compile it as a module, say M here and read
14554 <file:Documentation/modules.txt>. The module will be called
14557 Support for software ECC algorithm
14558 CONFIG_MTD_NAND_ECC
14559 This enables software-based ECC for use with NAND flash chips. It
14560 can detect and correct 1 bit errors per 256 byte blocks. This
14561 should be used to increase the reliability of the data stored and
14562 read on the device.
14564 Support for verify read after write
14565 CONFIG_MTD_NAND_VERIFY_WRITE
14566 This adds an extra check when data is written to the flash. The
14567 NAND flash device internally checks only bits transitioning
14568 from 1 to 0. There is a rare possibility that even though the
14569 device thinks the write was successful, a bit could have been
14570 flipped accidentally due to device wear, gamma rays, whatever.
14571 Enable this if you are really paranoid.
14573 Support for the SPIA board
14574 CONFIG_MTD_NAND_SPIA
14575 If you had to ask, you don't have one. Say 'N'.
14577 SmartMediaCard on autronix autcpu12 board
14578 CONFIG_MTD_NAND_AUTCPU12
14579 This enables the driver for the autronix autcpu12 board to
14580 access the SmartMediaCard.
14582 If compiled as a module, it will be called autcpu12.o.
14584 Support for Cirrus Logic EBD7312 evaluation board
14585 CONFIG_MTD_NAND_EDB7312
14586 This enables the driver for the Cirrus Logic EBD7312 evaluation
14587 board to access the onboard NAND Flash.
14589 If compiled as a module, it will be called edb7312.o.
14591 M-Systems Disk-On-Chip 1000 support
14593 This provides an MTD device driver for the M-Systems DiskOnChip
14594 1000 devices, which are obsolete so you probably want to say 'N'.
14596 This driver is also available as a module ( = code which can be
14597 inserted in and removed from the running kernel whenever you want).
14598 If you want to compile it as a module, say M here and read
14599 <file:Documentation/modules.txt>. The module will be called
14602 M-Systems Disk-On-Chip 2000 and Millennium support
14604 This provides an MTD device driver for the M-Systems DiskOnChip
14605 2000 and Millennium devices. Originally designed for the DiskOnChip
14606 2000, it also now includes support for the DiskOnChip Millennium.
14607 If you have problems with this driver and the DiskOnChip Millennium,
14608 you may wish to try the alternative Millennium driver below. To use
14609 the alternative driver, you will need to undefine DOC_SINGLE_DRIVER
14610 in the <file:drivers/mtd/devices/docprobe.c> source code.
14612 If you use this device, you probably also want to enable the NFTL
14613 'NAND Flash Translation Layer' option below, which is used to
14614 emulate a block device by using a kind of file system on the flash
14617 This driver is also available as a module ( = code which can be
14618 inserted in and removed from the running kernel whenever you want).
14619 If you want to compile it as a module, say M here and read
14620 <file:Documentation/modules.txt>. The module will be called
14623 Alternative Disk-On-Chip Millennium support
14625 This provides an alternative MTD device driver for the M-Systems
14626 DiskOnChip Millennium devices. Use this if you have problems with
14627 the combined DiskOnChip 2000 and Millennium driver above. To get
14628 the DiskOnChip probe code to load and use this driver instead of
14629 the other one, you will need to undefine DOC_SINGLE_DRIVER near
14630 the beginning of <file:drivers/mtd/devices/docprobe.c>.
14632 If you use this device, you probably also want to enable the NFTL
14633 'NAND Flash Translation Layer' option below, which is used to
14634 emulate a block device by using a kind of file system on the flash
14637 This driver is also available as a module ( = code which can be
14638 inserted in and removed from the running kernel whenever you want).
14639 If you want to compile it as a module, say M here and read
14640 <file:Documentation/modules.txt>. The module will be called
14643 Probe for DiskOnChip devices
14644 CONFIG_MTD_DOCPROBE
14645 This isn't a real config option, it's derived.
14647 Advanced detection options for DiskOnChip
14648 CONFIG_MTD_DOCPROBE_ADVANCED
14649 This option allows you to specify nonstandard address at which to
14650 probe for a DiskOnChip, or to change the detection options. You
14651 are unlikely to need any of this unless you are using LinuxBIOS.
14654 Probe for 0x55 0xAA BIOS Extension Signature
14655 CONFIG_MTD_DOCPROBE_55AA
14656 Check for the 0x55 0xAA signature of a DiskOnChip, and do not
14657 continue with probing if it is absent. The signature will always be
14658 present for a DiskOnChip 2000 or a normal DiskOnChip Millennium.
14659 Only if you have overwritten the first block of a DiskOnChip
14660 Millennium will it be absent. Enable this option if you are using
14661 LinuxBIOS or if you need to recover a DiskOnChip Millennium on which
14662 you have managed to wipe the first block.
14664 Physical address of DiskOnChip
14665 CONFIG_MTD_DOCPROBE_ADDRESS
14666 By default, the probe for DiskOnChip devices will look for a
14667 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
14668 This option allows you to specify a single address at which to probe
14669 for the device, which is useful if you have other devices in that
14670 range which get upset when they are probed.
14672 (Note that on PowerPC, the normal probe will only check at
14675 Normally, you should leave this set to zero, to allow the probe at
14676 the normal addresses.
14678 Probe high addresses
14679 CONFIG_MTD_DOCPROBE_HIGH
14680 By default, the probe for DiskOnChip devices will look for a
14681 DiskOnChip at every multiple of 0x2000 between 0xC8000 and 0xEE000.
14682 This option changes to make it probe between 0xFFFC8000 and
14683 0xFFFEE000. Unless you are using LinuxBIOS, this is unlikely to be
14684 useful to you. Say 'N'.
14686 Ramix PMC551 PCI Mezzanine ram card support
14688 This provides a MTD device driver for the Ramix PMC551 RAM PCI card
14689 from Ramix Inc. <http://www.ramix.com/products/memory/pmc551.html>.
14690 These devices come in memory configurations from 32M - 1G. If you
14691 have one, you probably want to enable this.
14693 If this driver is compiled as a module you get the ability to select
14694 the size of the aperture window pointing into the devices memory.
14695 What this means is that if you have a 1G card, normally the kernel
14696 will use a 1G memory map as its view of the device. As a module,
14697 you can select a 1M window into the memory and the driver will
14698 "slide" the window around the PMC551's memory. This was
14699 particularly useful on the 2.2 kernels on PPC architectures as there
14700 was limited kernel space to deal with.
14702 This driver is also available as a module ( = code which can be
14703 inserted in and removed from the running kernel whenever you want).
14704 If you want to compile it as a module, say M here and read
14705 <file:Documentation/modules.txt>. The module will be called
14708 PMC551 256M DRAM Bugfix
14709 CONFIG_MTD_PMC551_BUGFIX
14710 Some of Ramix's PMC551 boards with 256M configurations have invalid
14711 column and row mux values. This option will fix them, but will
14712 break other memory configurations. If unsure say N.
14715 CONFIG_MTD_PMC551_DEBUG
14716 This option makes the PMC551 more verbose during its operation and
14717 is only really useful if you are developing on this driver or
14718 suspect a possible hardware or driver bug. If unsure say N.
14720 Use extra onboard system memory as MTD device
14722 If your CPU cannot cache all of the physical memory in your machine,
14723 you can still use it for storage or swap by using this driver to
14724 present it to the system as a Memory Technology Device.
14726 This driver is also available as a module ( = code which can be
14727 inserted in and removed from the running kernel whenever you want).
14728 If you want to compile it as a module, say M here and read
14729 <file:Documentation/modules.txt>. The module will be called
14732 DEC MS02-NV NVRAM module support
14734 This is an MTD driver for the DEC's MS02-NV (54-20948-01) battery
14735 backed-up NVRAM module. The module was originally meant as an NFS
14736 accelerator. Say Y here if you have a DECstation 5000/2x0 or a
14737 DECsystem 5900 equipped with such a module.
14739 If you want to compile this driver as a module ( = code which can be
14740 inserted in and removed from the running kernel whenever you want),
14741 say M here and read <file:Documentation/modules.txt>. The module will
14742 be called ms02-nv.o.
14744 Debugging RAM test driver
14746 This enables a test MTD device driver which uses vmalloc() to
14747 provide storage. You probably want to say 'N' unless you're
14750 This driver is also available as a module ( = code which can be
14751 inserted in and removed from the running kernel whenever you want).
14752 If you want to compile it as a module, say M here and read
14753 <file:Documentation/modules.txt>. The module will be called
14756 MTDRAM erase block size in KB
14757 CONFIG_MTDRAM_ERASE_SIZE
14758 This allows you to configure the size of the erase blocks in the
14759 device emulated by the MTDRAM driver. If the MTDRAM driver is built
14760 as a module, it is also possible to specify this as a parameter when
14761 loading the module.
14763 MTDRAM device size in KB
14764 CONFIG_MTDRAM_TOTAL_SIZE
14765 This allows you to configure the total size of the MTD device
14766 emulated by the MTDRAM driver. If the MTDRAM driver is built
14767 as a module, it is also possible to specify this as a parameter when
14768 loading the module.
14770 SRAM Hexadecimal Absolute position or 0
14771 CONFIG_MTDRAM_ABS_POS
14772 If you have system RAM accessible by the CPU but not used by Linux
14773 in normal operation, you can give the physical address at which the
14774 available RAM starts, and the MTDRAM driver will use it instead of
14775 allocating space from Linux's available memory. Otherwise, leave
14776 this set to zero. Most people will want to leave this as zero.
14778 CFI Flash device mapping on the Flaga Digital Module
14779 CONFIG_MTD_CFI_FLAGADM
14780 Mapping for the Flaga digital module. If you don´t have one, ignore
14783 Momenco Ocelot boot flash device
14785 This enables access routines for the boot flash device and for the
14786 NVRAM on the Momenco Ocelot board. If you have one of these boards
14787 and would like access to either of these, say 'Y'.
14789 Support for absent chips in bus mapping
14791 This option enables support for a dummy probing driver used to
14792 allocated placeholder MTD devices on systems that have socketed
14793 or removable media. Use of this driver as a fallback chip probe
14794 preserves the expected registration order of MTD device nodes on
14795 the system regardless of media presence. Device nodes created
14796 with this driver will return -ENODEV upon access.
14798 This driver is also available as a module ( = code which can be
14799 inserted in and removed from the running kernel whenever you want).
14800 If you want to compile it as a module, say M here and read
14801 <file:Documentation/modules.txt>. The module will be called
14804 MTD emulation using block device
14806 This driver allows a block device to appear as an MTD. It would
14807 generally be used in the following cases:
14809 Using Compact Flash as an MTD, these usually present themselves to
14810 the system as an ATA drive.
14811 Testing MTD users (eg JFFS2) on large media and media that might
14812 be removed during a write (using the floppy drive).
14814 This driver is also available as a module ( = code which can be
14815 inserted in and removed from the running kernel whenever you want).
14816 If you want to compile it as a module, say M here and read
14817 <file:Documentation/modules.txt>. The module will be called
14820 Cirrus CDB89712 evaluation board mappings
14821 CONFIG_MTD_CDB89712
14822 This enables access to the flash or ROM chips on the CDB89712 board.
14823 (This board has 8 MB of Intel Strataflash, a 128 byte boot ROM, and 48 KB of
14824 internal SRAM. This driver provides MTD devices for all three components.)
14825 If you have such a board, say 'Y'.
14827 Detect non-CFI AMD/JEDEC-compatible flash chips
14828 CONFIG_MTD_JEDECPROBE
14829 This option enables JEDEC-style probing of flash chips which are not
14830 compatible with the Common Flash Interface, but will use the common
14831 CFI-targetted flash drivers for any chips which are identified which
14832 are in fact compatible in all but the probe method. This actually
14833 covers most AMD/Fujitsu-compatible chips, and will shortly cover also
14834 non-CFI Intel chips (that code is in MTD CVS and should shortly be sent
14835 for inclusion in Linus' tree)
14837 This driver is also available as a module ( = code which can be
14838 inserted in and removed from the running kernel whenever you want).
14839 If you want to compile it as a module, say M here and read
14840 <file:Documentation/modules.txt>. The module will be called
14843 BIOS flash chip on Intel L440GX boards
14845 Support for treating the BIOS flash chip on Intel L440GX motherboards
14846 as an MTD device - with this you can reprogram your BIOS.
14850 This driver is also available as a module ( = code which can be
14851 inserted in and removed from the running kernel whenever you want).
14852 If you want to compile it as a module, say M here and read
14853 <file:Documentation/modules.txt>. The module will be called
14856 28F160xx flash driver for LART
14858 This enables the flash driver for LART. Please note that you do
14859 not need any mapping/chip driver for LART. This one does it all
14860 for you, so go disable all of those if you enabled some of them (:
14862 Older (theoretically obsoleted now) drivers for non-CFI chips
14863 CONFIG_MTD_OBSOLETE_CHIPS
14864 This option does not enable any code directly, but will allow you to
14865 select some other chip drivers which are now considered obsolete,
14866 because the generic CONFIG_JEDEC_PROBE code above should now detect
14867 the chips which are supported by these drivers, and allow the generic
14868 CFI-compatible drivers to drive the chips. Say 'N' here unless you have
14869 already tried the CONFIG_JEDEC_PROBE method and reported its failure
14870 to the MTD mailing list at <linux-mtd@lists.infradead.org>
14872 CFI Flash device mapped on Hitachi SolutionEngine
14873 CONFIG_MTD_SOLUTIONENGINE
14874 This enables access to the flash chips on the Hitachi SolutionEngine and
14875 similar boards. Say 'Y' if you are building a kernel for such a board.
14877 CFI Flash device mapped on TQM8XXL PPC board
14879 The TQM8xxL PowerPC board has up to two banks of CFI-compliant
14880 chips, currently uses AMD one. This 'mapping' driver supports
14881 that arrangement, allowing the CFI probe and command set driver
14882 code to communicate with the chips on the TQM8xxL board. More at
14883 <http://www.denx.de/embedded-ppc-en.html>.
14887 This is an option about which you will never be asked a question.
14888 Therefore, I conclude that you do not exist - go away.
14890 There is a grue here.
14892 Physical memory size
14894 This sets the default memory size assumed by your SH kernel. It can
14895 be overridden as normal by the 'mem=' argument on the kernel command
14896 line. If unsure, consult your board specifications or just leave it
14897 as 0x00400000 which was the default value before this became
14900 Cache and PCI noncoherent
14901 CONFIG_SH_PCIDMA_NONCOHERENT
14902 Enable this option if your platform does not have a CPU cache which
14903 remains coherent with PCI DMA. It is safest to say 'Y', although you
14904 will see better performance if you can say 'N', because the PCI DMA
14905 code will not have to flush the CPU's caches. If you have a PCI host
14906 bridge integrated with your SH CPU, refer carefully to the chip specs
14907 to see if you can say 'N' here. Otherwise, leave it as 'Y'.
14909 USB (Universal Serial Bus) support
14911 Universal Serial Bus (USB) is a specification for a serial bus
14912 subsystem which offers higher speeds and more features than the
14913 traditional PC serial port. The bus supplies power to peripherals
14914 and allows for hot swapping. Up to 127 USB peripherals can be
14915 connected to a single USB port in a tree structure. The USB port is
14916 the root of the tree, the peripherals are the leaves and the inner
14917 nodes are special USB devices called hubs. Many newer PC's have USB
14918 ports and newer peripherals such as scanners, keyboards, mice,
14919 modems, and printers support the USB protocol and can be connected
14920 to the PC via those ports.
14922 Say Y here if your computer has a USB port and you want to use USB
14923 devices. You then need to say Y to at least one of "UHCI support"
14924 or "OHCI support" below (the type of interface that the USB hardware
14925 in your computer provides to the operating system) and then choose
14926 from among the drivers for USB peripherals. You may want to check
14927 out the information provided in <file:Documentation/usb/> and
14928 especially the links given in <file:Documentation/usb/usb-help.txt>.
14930 This code is also available as a module ( = code which can be
14931 inserted in and removed from the running kernel whenever you want).
14932 The module will be called usbcore.o. If you want to compile it as a
14933 module, say M here and read <file:Documentation/modules.txt>.
14935 USB verbose debug messages
14937 Say Y here if you want the USB core & hub drivers to produce a bunch
14938 of debug messages to the system log. Select this if you are having a
14939 problem with USB support and want to see more of what is going on.
14941 USB long timeout for slow-responding devices (some MGE Ellipse UPSes)
14942 CONFIG_USB_LONG_TIMEOUT
14943 This option makes the standard time out a bit longer. Basically,
14944 some devices are just slow to respond, so this makes usb more
14945 patient. There should be no harm in selecting this, but it is
14946 needed for some MGE Ellipse UPSes.
14948 If you have an MGE Ellipse UPS, or you see timeouts in HID
14949 transactions, say Y; otherwise say N.
14951 EHCI (USB 2.0) support
14952 CONFIG_USB_EHCI_HCD
14953 The Enhanced Host Controller Interface (EHCI) is standard for USB 2.0
14954 "high speed" (480 Mbit/sec, 60 Mbyte/sec) host controller hardware.
14955 If your USB host controller supports USB 2.0, you will likely want to
14956 configure this Host Controller Driver. At this writing, the primary
14957 implementation of EHCI is a chip from NEC, widely available in add-on
14958 PCI cards, but implementations are in the works from other vendors
14959 including Intel and Philips. Motherboard support is appearing.
14961 EHCI controllers are packaged with "companion" host controllers (OHCI
14962 or UHCI) to handle USB 1.1 devices connected to root hub ports. Ports
14963 will connect to EHCI if it the device is high speed, otherwise they
14964 connect to a companion controller. If you configure EHCI, you should
14965 probably configure the OHCI (for NEC and some other vendors) USB Host
14966 Controller Driver too.
14968 You may want to read <file:Documentation/usb/ehci.txt>.
14970 This code is also available as a module ( = code which can be
14971 inserted in and removed from the running kernel whenever you want).
14972 The module will be called ehci-hcd.o. If you want to compile it as a
14973 module, say M here and read <file:Documentation/modules.txt>.
14975 UHCI (Intel PIIX4, VIA, ...) support
14977 The Universal Host Controller Interface is a standard by Intel for
14978 accessing the USB hardware in the PC (which is also called the USB
14979 host controller). If your USB host controller conforms to this
14980 standard, you may want to say Y, but see below. All recent boards
14981 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
14982 i810, i820) conform to this standard. Also all VIA PCI chipsets
14983 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
14986 Currently there exist two drivers for UHCI host controllers: this
14987 one and the so-called JE driver, which you can get from
14988 "UHCI alternate (JE) support", below. You need only one.
14990 This code is also available as a module ( = code which can be
14991 inserted in and removed from the running kernel whenever you want).
14992 The module will be called usb-uhci.o. If you want to compile it as a
14993 module, say M here and read <file:Documentation/modules.txt>.
14995 UHCI (Intel PIIX4, VIA, ...) alternate (JE) support
14996 CONFIG_USB_UHCI_ALT
14997 The Universal Host Controller Interface is a standard by Intel for
14998 accessing the USB hardware in the PC (which is also called the USB
14999 host controller). If your USB host controller conforms to this
15000 standard, you may want to say Y, but see below. All recent boards
15001 with Intel PCI chipsets (like intel 430TX, 440FX, 440LX, 440BX,
15002 i810, i820) conform to this standard. Also all VIA PCI chipsets
15003 (like VIA VP2, VP3, MVP3, Apollo Pro, Apollo Pro II or Apollo Pro
15004 133). If unsure, say Y.
15006 Currently there exist two drivers for UHCI host controllers: this
15007 so-called JE driver, and the one you get from "UHCI support", above.
15010 This code is also available as a module ( = code which can be
15011 inserted in and removed from the running kernel whenever you want).
15012 The module will be called uhci.o. If you want to compile it as a
15013 module, say M here and read <file:Documentation/modules.txt>.
15015 OHCI (Compaq, iMacs, OPTi, SiS, ALi, ...) support
15017 The Open Host Controller Interface is a standard by
15018 Compaq/Microsoft/National for accessing the USB PC hardware (also
15019 called USB host controller). If your USB host controller conforms to
15020 this standard, say Y. The USB host controllers on most non-Intel
15021 architectures and on several x86 compatibles with non-Intel chipsets
15022 -- like SiS (aktual 610, 610 and so on) or ALi (ALi IV, ALi V,
15023 Aladdin Pro..) -- conform to this standard.
15025 You may want to read <file:Documentation/usb/ohci.txt>.
15027 This code is also available as a module ( = code which can be
15028 inserted in and removed from the running kernel whenever you want).
15029 The module will be called usb-ohci.o. If you want to compile it
15030 as a module, say M here and read <file:Documentation/modules.txt>.
15032 SL811HS (x86, StrongARM) support
15034 Embedded Open Host Controller SL811HS from CYPRESS SEMICONDUCTOR INC.
15037 Board USB1104 in i386 architecture with PC/104-bus.
15038 <http://www.ssv-embedded.de>
15039 <file:Documentation/usb/hc_sl811.txt>
15041 StrongARM is currently not testet and not for PC/104-bus!
15042 StrongARM need a special hardware with Chip Select directly from CPU.
15043 See also SL811HS_ALT.
15045 SL811HS_ALT (x86, StrongARM) support
15046 CONFIG_USB_SL811HS_ALT
15047 Embedded Open Host Controller SL811HS from CYPRESS SEMICONDUCTOR INC.
15048 Alternate with isochornous mode and better interrupt handling.
15051 USB Human Interface Device (full HID) support
15053 Say Y here if you want full HID support to connect keyboards,
15054 mice, joysticks, graphic tablets, or any other HID based devices
15055 to your computer via USB. You also need to select HID Input layer
15056 support (below) if you want to use keyboards, mice, joysticks and
15059 You can't use this driver and the HIDBP (Boot Protocol) keyboard
15060 and mouse drivers at the same time. More information is available:
15061 <file:Documentation/input/input.txt>.
15065 This code is also available as a module ( = code which can be
15066 inserted in and removed from the running kernel whenever you want).
15067 The module will be called hid.o. If you want to compile it as a
15068 module, say M here and read <file:Documentation/modules.txt>.
15070 USB HID Input layer support
15071 CONFIG_USB_HIDINPUT
15072 Say Y here if you want to use a USB keyboard, mouse or joystick,
15073 or any other HID input device. You also need Input layer support,
15074 (CONFIG_INPUT) which you select under "Input core support".
15078 /dev/usb/hiddev raw HID device support
15080 Say Y here if you want to support HID devices (from the USB
15081 specification standpoint) that aren't strictly user interface
15082 devices, like monitor controls and Uninterruptable Power Supplies.
15084 This module supports these devices separately using a separate
15085 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
15086 This driver requires CONFIG_USB_HID.
15090 USB HIDBP Keyboard (basic) support
15092 Say Y here only if you are absolutely sure that you don't want
15093 to use the generic HID driver for your USB keyboard and prefer
15094 to use the keyboard in its limited Boot Protocol mode instead.
15096 This is almost certainly not what you want.
15098 This code is also available as a module ( = code which can be
15099 inserted in and removed from the running kernel whenever you want).
15100 The module will be called usbkbd.o. If you want to compile it as a
15101 module, say M here and read <file:Documentation/modules.txt>.
15103 If even remotely unsure, say N.
15105 USB HIDBP Mouse (basic) support
15107 Say Y here only if you are absolutely sure that you don't want
15108 to use the generic HID driver for your USB mouse and prefer
15109 to use the mouse in its limited Boot Protocol mode instead.
15111 This is almost certainly not what you want.
15113 This code is also available as a module ( = code which can be
15114 inserted in and removed from the running kernel whenever you want).
15115 The module will be called usbmouse.o. If you want to compile it as
15116 a module, say M here and read <file:Documentation/modules.txt>.
15118 If even remotely unsure, say N.
15120 Wacom Intuos/Graphire tablet support
15122 Say Y here if you want to use the USB version of the Wacom Intuos
15123 or Graphire tablet. Make sure to say Y to "Mouse support"
15124 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
15125 (CONFIG_INPUT_EVDEV) as well.
15127 This driver is also available as a module ( = code which can be
15128 inserted in and removed from the running kernel whenever you want).
15129 The module will be called wacom.o. If you want to compile it as a
15130 module, say M here and read <file:Documentation/modules.txt>.
15132 Griffin Technology PowerMate support
15133 CONFIG_USB_POWERMATE
15134 Say Y here if you want to use the Griffin Technology, Inc. USB
15135 PowerMate device. This device is an aluminum dial which can
15136 measure clockwise and anticlockwise rotation. The dial also
15137 acts as a pushbutton. The base contains an LED which can be
15138 instructed to pulse or to switch to a particular intensity.
15140 You can download userspace tools from http://sowerbutts.com/powermate/
15142 This driver is also available as a module ( = code which can be
15143 inserted in and removed from the running kernel whenever you want).
15144 The module will be called powermate.o. If you want to compile it as a
15145 module, say M here and read <file:Documentation/modules.txt>.
15147 Aiptek HyperPen tablet support
15149 Say Y here if you want to use the USB version of the Aiptek HyperPen
15150 Digital Tablet (models 4000U, 5000U, 6000U, 8000U, and 12000U.)
15151 Make sure to say Y to "Mouse support" (CONFIG_INPUT_MOUSEDEV) and/or
15152 "Event interface support" (CONFIG_INPUT_EVDEV) as well.
15154 This driver is also available as a module ( = code which can be
15155 inserted in and removed from the running kernel whenever you want).
15156 The module will be called aiptek.o. If you want to compile it as a
15157 module, say M here and read <file:Documentation/modules.txt>.
15159 Use input layer for ADB devices
15160 CONFIG_INPUT_ADBHID
15161 Say Y here if you want to have ADB (Apple Desktop Bus) HID devices
15162 such as keyboards, mice, joysticks, or graphic tablets handled by
15163 the input layer. If you say Y here, make sure to say Y to the
15164 corresponding drivers "Keyboard support" (CONFIG_INPUT_KEYBDEV),
15165 "Mouse Support" (CONFIG_INPUT_MOUSEDEV) and "Event interface
15166 support" (CONFIG_INPUT_EVDEV) as well.
15168 If you say N here, you still have the option of using the old ADB
15169 keyboard and mouse drivers.
15173 HP OB600 C/CT Pop-Up Mouse
15175 Only add this driver if you have an Omnibook 600C or 600CT laptop.
15176 This driver has no probe routine and must assume ports 0x238-23b
15177 belong to the Pop-Up mouse. Depends on CONFIG_INPUT_MOUSEDEV.
15179 Best is to use a module and load the obmouse driver at runtime.
15180 Say M here and read <file:Documentation/modules.txt>.
15185 Say Y here if you want to enable any of the following options for
15186 USB Human Interface Device (HID) support.
15188 Say Y here if you want to enable any of the USB HID options in the
15189 USB support section which require Input core support.
15194 CONFIG_INPUT_KEYBDEV
15195 Say Y here if you want your USB HID keyboard (or an ADB keyboard
15196 handled by the input layer) to be able to serve as a system
15199 This driver is also available as a module ( = code which can be
15200 inserted in and removed from the running kernel whenever you want).
15201 The module will be called keybdev.o. If you want to compile it as a
15202 module, say M here and read <file:Documentation/modules.txt>.
15205 CONFIG_INPUT_MOUSEDEV
15206 Say Y here if you want your USB HID mouse (or ADB mouse handled by
15207 the input layer) to be accessible as char devices 13:32+ -
15208 /dev/input/mouseX and 13:63 - /dev/input/mice as an emulated ImPS/2
15209 mouse. That way, all user space programs will be able to use your
15214 This driver is also available as a module ( = code which can be
15215 inserted in and removed from the running kernel whenever you want).
15216 The module will be called mousedev.o. If you want to compile it as
15217 a module, say M here and read <file:Documentation/modules.txt>.
15219 Horizontal screen resolution
15220 CONFIG_INPUT_MOUSEDEV_SCREEN_X
15221 If you're using a digitizer, or a graphic tablet, and want to use
15222 it as a mouse then the mousedev driver needs to know the X window
15223 screen resolution you are using to correctly scale the data. If
15224 you're not using a digitizer, this value is ignored.
15226 Vertical screen resolution
15227 CONFIG_INPUT_MOUSEDEV_SCREEN_Y
15228 If you're using a digitizer, or a graphic tablet, and want to use
15229 it as a mouse then the mousedev driver needs to know the X window
15230 screen resolution you are using to correctly scale the data. If
15231 you're not using a digitizer, this value is ignored.
15234 CONFIG_INPUT_JOYDEV
15235 Say Y here if you want your USB HID joystick or gamepad to be
15236 accessible as char device 13:0+ - /dev/input/jsX device.
15238 This driver is also available as a module ( = code which can be
15239 inserted in and removed from the running kernel whenever you want).
15240 The module will be called joydev.o. If you want to compile it as a
15241 module, say M here and read <file:Documentation/modules.txt>.
15243 Dummy keyboard driver
15247 Not all systems have keyboards. Some don't even have a keyboard
15248 port. However, some of those systems have video support and can
15249 use the virtual terminal support for display. However, the virtual
15250 terminal code expects a keyboard of some kind. This driver keeps
15251 the virtual terminal code happy by providing it a "keyboard", albeit
15254 If you want to use the virtual terminal support but your system
15255 does not support a keyboard, define CONFIG_DUMMY_KEYB along with
15258 This can also be selected lonesome without any VT support (i.e. no
15259 monitor or keyboard attached) - just define CONFIG_DUMMY_KEYB.
15261 Event interface support
15263 Say Y here if you want your USB or ADB HID device events be
15264 accessible under char device 13:64+ - /dev/input/eventX in a generic
15265 way. This is the future ...
15267 CONFIG_INPUT_UINPUT
15268 Say Y here if you want to support user level drivers for input
15269 subsystem accessible under char device 10:223 - /dev/input/uinput.
15271 This driver is also available as a module ( = code which can be
15272 inserted in and removed from the running kernel whenever you want).
15273 The module will be called uinput.o. If you want to compile it as a
15274 module, say M here and read <file:Documentation/modules.txt>.
15276 USB Scanner support
15278 Say Y here if you want to connect a USB scanner to your computer's
15279 USB port. Please read <file:Documentation/usb/scanner.txt> for more
15282 This code is also available as a module ( = code which can be
15283 inserted in and removed from the running kernel whenever you want).
15284 The module will be called scanner.o. If you want to compile it as
15285 a module, say M here and read <file:Documentation/modules.txt>.
15287 HP 5300C scanner support
15289 Say Y here if you want to connect a HP5300C scanner to your
15290 computer's USB port.
15292 This code is also available as a module ( = code which can be
15293 inserted in and removed from the running kernel whenever you want).
15294 The module will be called hp5300.o. If you want to compile it as
15295 a module, say M here and read <file:Documentation/modules.txt>.
15299 Say Y here if you want to connect USB audio equipment such as
15300 speakers to your computer's USB port.
15302 This code is also available as a module ( = code which can be
15303 inserted in and removed from the running kernel whenever you want).
15304 The module will be called audio.o. If you want to compile it as a
15305 module, say M here and read <file:Documentation/modules.txt>.
15307 EMI 2|6 USB Audio interface support
15309 This driver loads firmware to Emagic EMI 2|6 low latency USB
15312 After firmware load the device is handled with standard linux
15315 This code is also available as a module ( = code which can be
15316 inserted in and removed from the running kernel whenever you want).
15317 The module will be called audio.o. If you want to compile it as a
15318 module, say M here and read <file:Documentation/modules.txt>.
15320 USB Modem (CDC ACM) support
15322 This driver supports USB modems and ISDN adapters which support the
15323 Communication Device Class Abstract Control Model interface.
15324 Please read <file:Documentation/usb/acm.txt> for details.
15326 This code is also available as a module ( = code which can be
15327 inserted in and removed from the running kernel whenever you want).
15328 The module will be called acm.o. If you want to compile it as a
15329 module, say M here and read <file:Documentation/modules.txt>.
15331 USB serial converter support
15333 Say Y here if you have a USB device that provides normal serial
15334 ports, or acts like a serial device, and you want to connect it to
15337 Please read <file:Documentation/usb/usb-serial.txt> for more
15338 information on the specifics of the different devices that are
15339 supported, and on how to use them.
15341 This code is also available as a module ( = code which can be
15342 inserted in and removed from the running kernel whenever you want).
15343 The module will be called usbserial.o. If you want to compile it
15344 as a module, say M here and read <file:Documentation/modules.txt>.
15346 USB Generic Serial Driver
15347 CONFIG_USB_SERIAL_GENERIC
15348 Say Y here if you want to use the generic USB serial driver. Please
15349 read <file:Documentation/usb/usb-serial.txt> for more information on
15350 using this driver. It is recommended that the "USB Serial converter
15351 support" be compiled as a module for this driver to be used
15354 USB ConnectTech WhiteHEAT Serial Driver
15355 CONFIG_USB_SERIAL_WHITEHEAT
15356 Say Y here if you want to use a ConnectTech WhiteHEAT 4 port
15357 USB to serial converter device.
15359 This code is also available as a module ( = code which can be
15360 inserted in and removed from the running kernel whenever you want).
15361 The module will be called whiteheat.o. If you want to compile it as
15362 a module, say M here and read <file:Documentation/modules.txt>.
15364 USB Handspring Visor Driver
15365 CONFIG_USB_SERIAL_VISOR
15366 Say Y here if you want to connect to your HandSpring Visor, Palm
15367 m500 or m505 through its USB docking station. See
15368 <http://usbvisor.sourceforge.net/> for more information on using this
15371 This code is also available as a module ( = code which can be
15372 inserted in and removed from the running kernel whenever you want).
15373 The module will be called visor.o. If you want to compile it as a
15374 module, say M here and read <file:Documentation/modules.txt>.
15376 USB PocketPC PDA Driver
15377 CONFIG_USB_SERIAL_IPAQ
15378 Say Y here if you want to connect to your Compaq iPAQ, HP Jornada,
15379 or any other PDA running Windows CE 3.0 or PocketPC 2002 using a USB
15380 cradle/cable. For information on using the driver,
15381 read <file:Documentation/usb/usb-serial.txt>.
15383 This code is also available as a module ( = code which can be
15384 inserted in and removed from the running kernel whenever you want).
15385 The module will be called ipaq.o. If you want to compile it as a
15386 module, say M here and read <file:Documentation/modules.txt>.
15388 USB IR Dongle Serial Driver
15389 CONFIG_USB_SERIAL_IR
15390 Say Y here if you want to enable simple serial support for USB IrDA
15391 devices. This is useful if you do not want to use the full IrDA
15394 This code is also available as a module ( = code which can be
15395 inserted in and removed from the running kernel whenever you want).
15396 The module will be called ir-usb.o. If you want to compile it as a
15397 module, say M here and read <file:Documentation/modules.txt>.
15399 USB Belkin and Paracom Single Port Serial Driver
15400 CONFIG_USB_SERIAL_BELKIN
15401 Say Y here if you want to use a Belkin USB Serial single port
15402 adaptor (F5U103 is one of the model numbers) or the Peracom single
15403 port USB to serial adapter.
15405 This code is also available as a module ( = code which can be
15406 inserted in and removed from the running kernel whenever you want).
15407 The module will be called belkin_sa.o. If you want to compile it as
15408 a module, say M here and read <file:Documentation/modules.txt>.
15410 USB FTDI Single Port Serial Driver
15411 CONFIG_USB_SERIAL_FTDI_SIO
15412 Say Y here if you want to use a FTDI SIO single port USB to serial
15413 converter device. The implementation I have is called the USC-1000.
15414 This driver has also be tested with the 245 and 232 devices.
15416 See <http://ftdi-usb-sio.sourceforge.net/> for more
15417 information on this driver and the device.
15419 This code is also available as a module ( = code which can be
15420 inserted in and removed from the running kernel whenever you want).
15421 The module will be called ftdi_sio.o. If you want to compile it as
15422 a module, say M here and read <file:Documentation/modules.txt>.
15424 USB Keyspan PDA Single Port Serial Driver
15425 CONFIG_USB_SERIAL_KEYSPAN_PDA
15426 Say Y here if you want to use a Keyspan PDA single port USB to
15427 serial converter device. This driver makes use of firmware
15428 developed from scratch by Brian Warner.
15430 This code is also available as a module ( = code which can be
15431 inserted in and removed from the running kernel whenever you want).
15432 The module will be called keyspan_pda.o. If you want to compile it
15433 as a module, say M here and read <file:Documentation/modules.txt>.
15435 USB Xircom / Entregra Single Port Serial Driver
15436 CONFIG_USB_SERIAL_XIRCOM
15437 Say Y here if you want to use a Xircom or Entregra single port USB to
15438 serial converter device. This driver makes use of firmware
15439 developed from scratch by Brian Warner.
15441 This code is also available as a module ( = code which can be
15442 inserted in and removed from the running kernel whenever you want).
15443 The module will be called keyspan_pda.o. If you want to compile it
15444 as a module, say M here and read <file:Documentation/modules.txt>.
15446 USB Keyspan USA-xxx Serial Driver
15447 CONFIG_USB_SERIAL_KEYSPAN
15448 Say Y here if you want to use Keyspan USB to serial converter
15449 devices. This driver makes use of Keyspan's official firmware
15450 and was developed with their support. You must also include
15451 firmware to support your particular device(s).
15453 See <http://misc.nu/hugh/keyspan.html> for more information.
15455 This code is also available as a module ( = code which can be
15456 inserted in and removed from the running kernel whenever you want).
15457 The module will be called keyspan.o. If you want to compile it as a
15458 module, say M here and read <file:Documentation/modules.txt>.
15460 USB Keyspan USA-28 Firmware
15461 CONFIG_USB_SERIAL_KEYSPAN_USA28
15462 Say Y here to include firmware for the USA-28 converter.
15464 USB Keyspan USA-28X Firmware
15465 CONFIG_USB_SERIAL_KEYSPAN_USA28X
15466 Say Y here to include firmware for the USA-28X converter.
15467 Be sure you have a USA-28X, there are also 28XA and 28XB
15468 models, the label underneath has the actual part number.
15470 USB Keyspan USA-28XA Firmware
15471 CONFIG_USB_SERIAL_KEYSPAN_USA28XA
15472 Say Y here to include firmware for the USA-28XA converter.
15473 Be sure you have a USA-28XA, there are also 28X and 28XB
15474 models, the label underneath has the actual part number.
15476 USB Keyspan USA-28XB Firmware
15477 CONFIG_USB_SERIAL_KEYSPAN_USA28XB
15478 Say Y here to include firmware for the USA-28XB converter.
15479 Be sure you have a USA-28XB, there are also 28X and 28XA
15480 models, the label underneath has the actual part number.
15482 USB Keyspan USA-19 Firmware
15483 CONFIG_USB_SERIAL_KEYSPAN_USA19
15484 Say Y here to include firmware for the USA-19 converter.
15486 USB Keyspan USA-18X Firmware
15487 CONFIG_USB_SERIAL_KEYSPAN_USA18X
15488 Say Y here to include firmware for the USA-18X converter.
15490 USB Keyspan USA-19W Firmware
15491 CONFIG_USB_SERIAL_KEYSPAN_USA19W
15492 Say Y here to include firmware for the USA-19W converter.
15494 USB Keyspan USA-19QW Firmware
15495 CONFIG_USB_SERIAL_KEYSPAN_USA19QW
15496 Say Y here to include firmware for the USA-19QW converter.
15498 USB Keyspan USA-19QI Firmware
15499 CONFIG_USB_SERIAL_KEYSPAN_USA19QI
15500 Say Y here to include firmware for the USA-19QI converter.
15502 USB Keyspan USA-49W Firmware
15503 CONFIG_USB_SERIAL_KEYSPAN_USA49W
15504 Say Y here to include firmware for the USA-49W converter.
15506 CONFIG_USB_SERIAL_KEYSPAN_USA49WLC
15507 Say Y here to include firmware for the USA-49WLC converter.
15509 USB ZyXEL omni.net LCD Plus Driver
15510 CONFIG_USB_SERIAL_OMNINET
15511 Say Y here if you want to use a ZyXEL omni.net LCD ISDN TA.
15513 This code is also available as a module ( = code which can be
15514 inserted in and removed from the running kernel whenever you want).
15515 The module will be called omninet.o. If you want to compile it as a
15516 module, say M here and read <file:Documentation/modules.txt>.
15518 USB Digi International AccelePort USB Serial Driver
15519 CONFIG_USB_SERIAL_DIGI_ACCELEPORT
15520 Say Y here if you want to use Digi AccelePort USB 2 or 4 devices,
15521 2 port (plus parallel port) and 4 port USB serial converters. The
15522 parallel port on the USB 2 appears as a third serial port on Linux.
15523 The Digi Acceleport USB 8 is not yet supported by this driver.
15525 This driver works under SMP with the usb-uhci driver. It does not
15526 work under SMP with the uhci driver.
15528 This code is also available as a module ( = code which can be
15529 inserted in and removed from the running kernel whenever you want).
15530 The module will be called digi_acceleport.o. If you want to compile
15531 it as a module, say M here and read
15532 <file:Documentation/modules.txt>.
15534 USB Empeg empeg-car Mark I/II Driver
15535 CONFIG_USB_SERIAL_EMPEG
15536 Say Y here if you want to connect to your Empeg empeg-car Mark I/II
15537 mp3 player via USB. The driver uses a single ttyUSB{0,1,2,...}
15538 device node. See <file:Documentation/usb/usb-serial.txt> for more
15539 tidbits of information.
15541 This code is also available as a module ( = code which can be
15542 inserted in and removed from the running kernel whenever you want).
15543 The module will be called empeg.o. If you want to compile it as a
15544 module, say M here and read <file:Documentation/modules.txt>.
15546 USB MCT Single Port Serial Driver
15547 CONFIG_USB_SERIAL_MCT_U232
15548 Say Y here if you want to use a USB Serial single port adapter from
15549 Magic Control Technology Corp. (U232 is one of the model numbers).
15551 This driver also works with Sitecom U232-P25 and D-Link DU-H3SP USB
15554 This code is also available as a module ( = code which can be
15555 inserted in and removed from the running kernel whenever you want).
15556 The module will be called mct_u232.o. If you want to compile it as
15557 a module, say M here and read <file:Documentation/modules.txt>.
15559 USB Prolific 2303 Single Port Serial Driver
15560 CONFIG_USB_SERIAL_PL2303
15561 Say Y here if you want to use the PL2303 USB Serial single port
15562 adapter from Prolific.
15564 This code is also available as a module ( = code which can be
15565 inserted in and removed from the running kernel whenever you want).
15566 The module will be called pl2303.o. If you want to compile it as
15567 a module, say M here and read <file:Documentation/modules.txt>.
15569 USB KOBIL chipcard reader
15570 CONFIG_USB_SERIAL_KOBIL_SCT
15571 Say Y here if you want to use one of the following KOBIL USB chipcard
15572 readers: TWIN, KAAN Standard Plus, SecOVID Reader Plus, B1 PRO, KAAN PRO
15574 Note that you need a current CT-API.
15575 This code is also available as a module ( = code which can be
15576 inserted in and removed from the running kernel whenever you want).
15577 The module will be called kobil_sct.o. If you want to compile it as
15578 a module, say M here and read <file:Documentation/modules.txt>.
15580 USB REINER SCT cyberJack pinpad/e-com chipcard reader
15581 CONFIG_USB_SERIAL_CYBERJACK
15582 Say Y here if you want to use a cyberJack pinpad/e-com USB chipcard
15583 reader. This is an interface to ISO 7816 compatible contactbased
15584 chipcards, e.g. GSM SIMs.
15586 This code is also available as a module ( = code which can be
15587 inserted in and removed from the running kernel whenever you want).
15588 The module will be called cyberjack.o. If you want to compile it as
15589 a module, say M here and read <file:Documentation/modules.txt>.
15593 USB Edgeport Serial Driver
15594 CONFIG_USB_SERIAL_EDGEPORT
15595 Say Y here if you want to use any of the following devices from
15596 Inside Out Networks (Digi):
15614 This code is also available as a module ( = code which can be
15615 inserted in and removed from the running kernel whenever you want).
15616 The module will be called io_edgeport.o. If you want to compile it
15617 as a module, say M here and read <file:Documentation/modules.txt>.
15619 USB PalmConnect (and other KL5KUSB105-based) Single Port Serial Driver
15620 CONFIG_USB_SERIAL_KLSI
15621 Say Y here if you want to use a KL5KUSB105 - based single port
15622 serial adapter. The most widely known -- and currently the only
15623 tested -- device in this category is the PalmConnect USB Serial
15624 adapter sold by Palm Inc. for use with their Palm III and Palm V
15627 Please read <file:Documentation/usb/usb-serial.txt> for more
15630 This code is also available as a module ( = code which can be
15631 inserted in and removed from the running kernel whenever you want).
15632 The module will be called kl5kusb105.o. If you want to compile it as
15633 a module, say M here and read <file:Documentation/modules.txt>.
15635 USB Serial Converter verbose debug
15636 CONFIG_USB_SERIAL_DEBUG
15637 Say Y here if you want verbose debug messages from the USB Serial
15638 Drivers sent to the kernel debug log.
15640 USB Printer support
15642 Say Y here if you want to connect a USB printer to your computer's
15645 This code is also available as a module ( = code which can be
15646 inserted in and removed from the running kernel whenever you want).
15647 The module will be called printer.o. If you want to compile it as a
15648 module, say M here and read <file:Documentation/modules.txt>.
15650 USB IBM (Xirlink) C-It Camera support
15652 Say Y here if you want to connect a IBM "C-It" camera, also known as
15653 "Xirlink PC Camera" to your computer's USB port. For more
15654 information, read <file:Documentation/usb/ibmcam.txt>.
15656 This driver uses the Video For Linux API. You must enable
15657 (Y or M in config) Video For Linux (under Character Devices)
15658 to use this driver. Information on this API and pointers to
15659 "v4l" programs may be found on the WWW at
15660 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
15662 This code is also available as a module ( = code which can be
15663 inserted in and removed from the running kernel whenever you want).
15664 The module will be called ibmcam.o. If you want to compile it as a
15665 module, say M here and read <file:Documentation/modules.txt>. This
15666 camera has several configuration options which can be specified when
15667 you load the module. Read <file:Documentation/usb/ibmcam.txt> to
15670 CONFIG_USB_KONICAWC
15671 Say Y here if you want support for webcams based on a Konica
15672 chipset. This is known to work with the Intel YC76 webcam.
15674 This driver uses the Video For Linux API. You must enable
15675 (Y or M in config) Video For Linux (under Character Devices)
15676 to use this driver. Information on this API and pointers to
15677 "v4l" programs may be found on the WWW at
15678 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
15680 This code is also available as a module ( = code which can be
15681 inserted in and removed from the running kernel whenever you want).
15682 The module will be called konicawc.o. If you want to compile it as
15683 a module, say M here and read <file:Documentation/modules.txt>.
15685 USB OV511 Camera support
15687 Say Y here if you want to connect this type of camera to your
15688 computer's USB port. See <file:Documentation/usb/ov511.txt> for more
15689 information and for a list of supported cameras.
15691 This driver uses the Video For Linux API. You must say Y or M to
15692 "Video For Linux" (under Character Devices) to use this driver.
15693 Information on this API and pointers to "v4l" programs may be found
15694 on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
15696 This code is also available as a module ( = code which can be
15697 inserted in and removed from the running kernel whenever you want).
15698 The module will be called ov511.o. If you want to compile it as a
15699 module, say M here and read <file:Documentation/modules.txt>.
15701 USB W996[87]CF Camera support
15703 Say Y here if you want support for cameras based on
15704 Winbond W9967CF/W9968CF JPEG USB Dual Mode Camera Chips.
15706 This driver has an optional plugin, which is distributed as a
15707 separate module only (released under GPL). It contains code that
15708 allows you to use higher resolutions and framerates, and cannot
15709 be included in the official Linux kernel for performance purposes.
15710 At the moment the driver needs a third-party module for the CMOS
15711 sensors, which is available on internet: it is recommended to read
15712 <file:Documentation/usb/w9968cf.txt> for more informations and for
15713 a list of supported cameras.
15715 This driver uses the Video For Linux and the I2C APIs.
15716 You must say Y or M to both "Video For Linux" and "I2C Support"
15717 to use this driver. Information on this API and pointers to "v4l"
15718 programs may be found on the WWW at
15719 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
15721 This code is also available as a module ( = code which can be
15722 inserted in and removed from the running kernel whenever you want).
15723 The module will be called w9968cf.o. If you want to compile it as a
15724 module, say M here and read <file:Documentation/modules.txt>.
15726 USB Communication Class Ethernet device support
15727 CONFIG_USB_CDCETHER
15728 This driver supports devices conforming to the Communication Device
15729 Class Ethernet Control Model. This is used in some cable modems.
15730 For more details on the specification, get the Communication Device
15731 Class specification from <http://www.usb.org/>.
15733 This driver should work with the following devices:
15734 * Ericsson PipeRider (all variants)
15735 * Motorola (DM100 and SB4100)
15736 * Broadcom Cable Modem (reference design)
15737 * Toshiba PCX1100U and possibly other cable modems
15738 * Sharp Zaurus SL-5000D
15740 The device creates a network device (ethX, where X depends on what
15741 other networking devices you have in use), as for a normal PCI
15742 or ISA based ethernet network card.
15744 This code is also available as a module ( = code which can be
15745 inserted in and removed from the running kernel whenever you want).
15746 The module will be called CDCEther.o. If you want to compile it as
15747 a module, say M here and read <file:Documentation/modules.txt>.
15749 NetChip 1080-based USB Host-to-Host Link
15751 The NetChip 1080 is a USB 1.1 host controller. NetChip has a web
15752 site with technical information at <http://www.netchip.com/>.
15754 Philips webcam support
15756 Say Y or M here if you want to use one of these Philips USB webcams:
15757 PCA645, PCA646, PCVC675, PCVC680, PCVC690, PCVC730, PCVC740, or
15758 the Askey VC010. The PCA635, PCVC665 and PCVC720 are not supported
15759 by this driver and never will be.
15761 This driver has an optional plugin, which is distributed as a binary
15762 module only. It contains code that allow you to use higher
15763 resolutions and framerates but may not be distributed as source.
15764 But even without this plugin you can these cams for most
15767 See <file:Documentation/usb/philips.txt> for more information and
15768 installation instructions.
15770 The built-in microphone is enabled by selecting USB Audio support.
15772 This driver uses the Video For Linux API. You must say Y or M to
15773 "Video For Linux" (under Character Devices) to use this driver.
15774 Information on this API and pointers to "v4l" programs may be found
15775 on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
15777 This code is also available as a module ( = code which can be
15778 inserted in and removed from the running kernel whenever you want).
15779 The module will be called pwc.o. If you want to compile it as a
15780 module, say M here and read <file:Documentation/modules.txt>.
15782 USB SE401 Camera support
15784 Say Y here if you want to connect this type of camera to your
15785 computer's USB port. See <file:Documentation/usb/se401.txt> for more
15786 information and for a list of supported cameras.
15788 This driver uses the Video For Linux API. You must say Y or M to
15789 "Video For Linux" (under Multimedia Devices) to use this driver.
15790 Information on this API and pointers to "v4l" programs may be found
15791 on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
15793 This code is also available as a module ( = code which can be
15794 inserted in and removed from the running kernel whenever you want).
15795 The module will be called se401.o. If you want to compile it as a
15796 module, say M here and read <file:Documentation/modules.txt>.
15798 USB STV680 (Pencam) Camera support
15800 Say Y here if you want to connect this type of camera to your
15801 computer's USB port. This includes the Pencam line of cameras.
15802 See <file:Documentation/usb/stv680.txt> for more information and for
15803 a list of supported cameras.
15805 This driver uses the Video For Linux API. You must say Y or M to
15806 "Video For Linux" (under Multimedia Devices) to use this driver.
15807 Information on this API and pointers to "v4l" programs may be found
15808 on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
15810 This code is also available as a module ( = code which can be
15811 inserted in and removed from the running kernel whenever you want).
15812 The module will be called stv680.o. If you want to compile it as a
15813 module, say M here and read <file:Documentation/modules.txt>.
15817 Say Y here if you have 3com homeconnect camera (vicam).
15819 This driver uses the Video For Linux API. You must say Y or M to
15820 "Video For Linux" (under Multimedia Devices) to use this driver.
15821 Information on this API and pointers to "v4l" programs may be found
15822 on the WWW at <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
15824 This code is also available as a module ( = code which can be
15825 inserted in and removed from the running kernel whenever you want).
15826 The module will be called vicam.o. If you want to compile it as a
15827 module, say M here and read <file:Documentation/modules.txt>.
15830 Pegasus/Pegasus II based USB-Ethernet device support
15832 Say Y here if you know you have Pegasus or Pegasus-II based adapter.
15833 If in doubt then look at linux/drivers/usb/pegasus.h for the complete
15834 list of supported devices.
15835 If your particular adapter is not in the list and you are _sure_ it
15836 is Pegasus or Pegasus-II based then send me (petkan@users.sourceforge.net)
15837 vendor and device IDs.
15839 This code is also available as a module ( = code which can be
15840 inserted in and removed from the running kernel whenever you want).
15841 The module will be called pegasus.o. If you want to compile it as a
15842 module, say M here and read <file:Documentation/modules.txt>.
15844 Realtek RTL8150 based USB-Ethernet device support
15846 Say Y here if you have RTL8150 based usb-ethernet adapter.
15847 Send me (petkan@users.sourceforge.net) any comments you may have.
15848 You can also check for updates at <http://pegasus2.sourceforge.net/>
15850 This code is also available as a module ( = code which can be
15851 inserted in and removed from the running kernel whenever you want).
15852 The module will be called rtl8150.o. If you want to compile it as a
15853 module, say M here and read <file:Documentation/modules.txt>.
15855 USB KLSI KL5USB101-based Ethernet device support
15857 Say Y here if you want to use one of the following 10Mbps only
15858 USB Ethernet adapters based on the KLSI KL5KUSB101B chipset:
15862 ASANTE USB To Ethernet Adapter
15863 AOX Endpoints USB Ethernet
15865 D-Link DSB-650C and DU-E10
15866 Entrega / Portgear E45
15868 Jaton USB Ethernet Device Adapter
15869 Kingston Technology USB Ethernet Adapter
15871 Mobility USB-Ethernet Adapter
15873 Peracom Enet and Enet2
15874 Portsmith Express Ethernet Adapter
15875 Shark Pocket Adapter
15877 Sony Vaio port extender
15879 This driver is likely to work with most 10Mbps only USB Ethernet
15880 adapters, including some "no brand" devices. It does NOT work on
15881 SmartBridges smartNIC or on Belkin F5U111 devices - you should use
15882 the CATC NetMate driver for those. If you are not sure which one
15883 you need, select both, and the correct one should be selected for
15886 This driver makes the adapter appear as a normal Ethernet interface,
15887 typically on eth0, if it is the only ethernet device, or perhaps on
15888 eth1, if you have a PCI or ISA ethernet card installed.
15890 This code is also available as a module ( = code which can be
15891 inserted in and removed from the running kernel whenever you want).
15892 The module will be called kaweth.o. If you want to compile it as a
15893 module, say M here and read <file:Documentation/modules.txt>.
15895 USB CATC NetMate-based Ethernet device support
15897 Say Y if you want to use one of the following 10Mbps USB Ethernet
15898 device based on the EL1210A chip. Supported devices are:
15903 smartBridges smartNIC
15905 This driver makes the adapter appear as a normal Ethernet interface,
15906 typically on eth0, if it is the only ethernet device, or perhaps on
15907 eth1, if you have a PCI or ISA ethernet card installed.
15909 This code is also available as a module ( = code which can be
15910 inserted in and removed from the running kernel whenever you want).
15911 The module will be called catc.o. If you want to compile it as a
15912 module, say M here and read <file:Documentation/modules.txt>.
15914 USB Kodak DC-2xx Camera support
15916 Say Y here if you want to connect this type of still camera to your
15917 computer's USB port. See <file:Documentation/usb/dc2xx.txt> for
15918 more information; some non-Kodak cameras may also work with this
15919 driver, given application support (such as <http://www.gphoto.org/>).
15921 This code is also available as a module ( = code which can be
15922 inserted in and removed from the running kernel whenever you want).
15923 The module will be called dc2xx.o. If you want to compile it as a
15924 module, say M here and read <file:Documentation/modules.txt>.
15926 USB Mustek MDC800 Digital Camera support
15928 Say Y here if you want to connect this type of still camera to
15929 your computer's USB port. This driver can be used with gphoto 0.4.3
15930 and higher (look at <http://www.gphoto.org/>).
15931 To use it create a device node with "mknod /dev/mustek c 180 32" and
15932 configure it in your software.
15934 This code is also available as a module ( = code which can be
15935 inserted in and removed from the running kernel whenever you want).
15936 The module will be called mdc800.o. If you want to compile it as a
15937 module, say M here and read <file:Documentation/modules.txt>.
15939 USB Mass Storage support
15941 Say Y here if you want to connect USB mass storage devices to your
15942 computer's USB port.
15944 This code is also available as a module ( = code which can be
15945 inserted in and removed from the running kernel whenever you want).
15946 The module will be called usb-storage.o. If you want to compile it
15947 as a module, say M here and read <file:Documentation/modules.txt>.
15949 USB Mass Storage verbose debug
15950 CONFIG_USB_STORAGE_DEBUG
15951 Say Y here in order to have the USB Mass Storage code generate
15952 verbose debugging messages.
15954 ISD-200 USB/ATA Bridge support
15955 CONFIG_USB_STORAGE_ISD200
15956 Say Y here if you want to use USB Mass Store devices based
15957 on the In-Systems Design ISD-200 USB/ATA bridge.
15959 Some of the products that use this chip are:
15961 - Archos Jukebox 6000
15962 - ISD SmartCable for Storage
15963 - Taiwan Skymaster CD530U/DEL-0241 IDE bridge
15964 - Sony CRX10U CD-R/RW drive
15965 - CyQ've CQ8060A CDRW drive
15966 - Planex eXtreme Drive RX-25HU USB-IDE cable (not model RX-25U)
15968 USS720 parport driver
15970 This driver is for USB parallel port adapters that use the Lucent
15971 Technologies USS-720 chip. These cables are plugged into your USB
15972 port and provide USB compatibility to peripherals designed with
15973 parallel port interfaces.
15975 The chip has two modes: automatic mode and manual mode. In automatic
15976 mode, it looks to the computer like a standard USB printer. Only
15977 printers may be connected to the USS-720 in this mode. The generic
15978 USB printer driver ("USB Printer support", above) may be used in
15979 that mode, and you can say N here if you want to use the chip only
15982 Manual mode is not limited to printers, any parallel port
15983 device should work. This driver utilizes manual mode.
15984 Note however that some operations are three orders of magnitude
15985 slower than on a PCI/ISA Parallel Port, so timing critical
15986 applications might not work.
15988 Say Y here if you own an USS-720 USB->Parport cable and intend to
15989 connect anything other than a printer to it.
15991 This code is also available as a module ( = code which can be
15992 inserted in and removed from the running kernel whenever you want).
15993 The module will be called uss720.o. If you want to compile it as a
15994 module, say M here and read <file:Documentation/modules.txt>.
15996 USB device file system
15997 CONFIG_USB_DEVICEFS
15998 If you say Y here (and to "/proc file system support" in the "File
15999 systems section, above), you will get a file /proc/bus/usb/devices
16000 which lists the devices currently connected to your USB bus or
16001 busses, a file /proc/bus/usb/drivers which lists the USB kernel
16002 client drivers currently loaded, and for every connected device a
16003 file named "/proc/bus/usb/xxx/yyy", where xxx is the bus number and
16004 yyy the device number; the latter files can be used by user space
16005 programs to talk directly to the device. These files are "virtual",
16006 meaning they are generated on the fly and not stored on the hard
16009 You may need to mount the usbdevfs file system to see the files, use
16010 mount -t usbdevfs none /proc/bus/usb
16012 For the format of the various /proc/bus/usb/ files, please read
16013 <file:Documentation/usb/proc_usb_info.txt>.
16015 Please note that this code is completely unrelated to devfs, the
16016 "/dev file system support".
16018 Most users want to say Y here.
16020 Enforce USB bandwidth allocation
16021 CONFIG_USB_BANDWIDTH
16022 If you say Y here, the USB subsystem enforces USB bandwidth
16023 allocation and will prevent some device opens from succeeding
16024 if they would cause USB bandwidth usage to go above 90% of
16027 If you say N here, these conditions will cause warning messages
16028 about USB bandwidth usage to be logged and some devices or
16029 drivers may not work correctly.
16033 A Digital Audio Broadcasting (DAB) Receiver for USB and Linux
16034 brought to you by the DAB-Team (<http://dab.in.tum.de/>). This
16035 driver can be taken as an example for URB-based bulk, control, and
16036 isochronous transactions. URB's are explained in
16037 <file:Documentation/usb/URB.txt>.
16039 This code is also available as a module ( = code which can be
16040 inserted in and removed from the running kernel whenever you want).
16041 The module will be called dabusb.o. If you want to compile it as a
16042 module, say M here and read <file:Documentation/modules.txt>.
16044 Host-to-Host USB networking
16046 This driver supports network links over USB with USB "Network"
16047 or "data transfer" cables, often used to network laptops to PCs.
16048 Such cables have chips from suppliers such as Belkin/eTEK, GeneSys
16049 (GeneLink), NetChip and Prolific. Intelligent USB devices could also
16050 use this approach to provide Internet access, using standard USB
16051 cabling. You can find these chips also on some motherboards with
16054 These links will have names like "usb0", "usb1", etc. They act
16055 like two-node Ethernets, so you can use 802.1d Ethernet Bridging
16056 (CONFIG_BRIDGE) to simplify your network routing.
16058 This code is also available as a kernel module (code which can be
16059 inserted in and removed from the running kernel whenever you want).
16060 The module will be called usbnet.o. If you want to compile it as a
16061 module, say M here and read <file:Documentation/modules.txt>.
16063 Freecom USB/ATAPI Bridge support
16064 CONFIG_USB_STORAGE_FREECOM
16065 Support for the Freecom USB to IDE/ATAPI adaptor.
16066 Freecom has a web page at <http://www.freecom.de/>.
16068 Microtech CompactFlash/SmartMedia reader
16069 CONFIG_USB_STORAGE_DPCM
16070 Say Y here to support the Microtech ZiO! CompactFlash/SmartMedia
16071 reader, details at <http://www.microtechint.com/zio/index.html>.
16072 This driver treats the flash card as a removable storage device.
16074 SanDisk SDDR-09 (and other SmartMedia) support
16075 CONFIG_USB_STORAGE_SDDR09
16076 Say Y here to include additional code to support the Sandisk SDDR-09
16077 SmartMedia reader in the USB Mass Storage driver.
16079 SanDisk SDDR-55 SmartMedia support
16080 CONFIG_USB_STORAGE_SDDR55
16081 Say Y here to include additional code to support the Sandisk SDDR-55
16082 SmartMedia reader in the USB Mass Storage driver.
16084 USB Diamond Rio500 support
16086 Say Y here if you want to connect a USB Rio500 mp3 player to your
16087 computer's USB port. Please read <file:Documentation/usb/rio.txt>
16088 for more information.
16090 This code is also available as a module ( = code which can be
16091 inserted in and removed from the running kernel whenever you want).
16092 The module will be called rio500.o. If you want to compile it as
16093 a module, say M here and read <file:Documenatation/modules.txt>.
16095 Auerswald device support
16096 CONFIG_USB_AUERSWALD
16097 Say Y here if you want to connect an Auerswald USB ISDN Device
16098 to your computer's USB port.
16100 This code is also available as a module ( = code which can be
16101 inserted in and removed from the running kernel whenever you want).
16102 The module will be called auerswald.o. If you want to compile it as
16103 a module, say M here and read <file:Documenatation/modules.txt>
16105 USB Auerswald ISDN modem support
16106 CONFIG_USB_AUERISDN
16107 Say Y here if you want to enable the ISDN modem option
16108 of your Auerswald ISDN devices.
16110 This code is also available as a module ( = code which can be
16111 inserted in and removed from the running kernel whenever you want).
16112 The module will be called auerswald.o. If you want to compile it as
16113 a module, say M here and read <file:Documenatation/modules.txt>
16116 If you own a Texas Instruments graphing calculator and use a
16117 TI-GRAPH LINK USB cable (aka SilverLink), then you might be
16118 interested in this driver.
16120 If you enable this driver, you will be able to communicate with
16121 your calculator through a set of device nodes under /dev.
16123 This code is also available as a module ( = code which can be
16124 inserted in and removed from the running kernel whenever you want).
16125 The module will be called tiglusb.o. If you want to compile it as a
16126 module, say M here and read Documentation/modules.txt.
16128 If you don't know what the SilverLink cable is or what a Texas
16129 Instruments graphing calculator is, then you probably don't need this
16134 Texas Instruments parallel link cable support
16136 If you own a Texas Instruments graphing calculator and use a
16137 parallel link cable, then you might be interested in this driver.
16139 If you enable this driver, you will be able to communicate with
16140 your calculator through a set of device nodes under /dev. The
16141 main advantage of this driver is that you don't have to be root
16142 to use this precise link cable (depending on the permissions on
16143 the device nodes, though).
16145 This code is also available as a module ( = code which can be
16146 inserted in and removed from the running kernel whenever you want).
16147 The module will be called tipar.o. If you want to compile it as a
16148 module, say M here and read <file:Documentation/modules.txt>
16150 If you don't know what a parallel link cable is or what a Texas
16151 Instruments graphing calculator is, then you probably don't need this
16156 Tieman Voyager USB Braille display support
16157 CONFIG_USB_BRLVOYAGER
16158 Say Y here if you want to use the Voyager USB Braille display from
16159 Tieman. See <file:Documentation/usb/brlvger.txt> for more
16162 This code is also available as a module ( = code which can be
16163 inserted in and removed from the running kernel whenever you want).
16164 The module will be called brlvger.o. If you want to compile it as
16165 a module, say M here and read <file:Documentation/modules.txt>.
16169 Say Y here if you want to connect an USBLCD to your computer's
16170 USB port. The USBLCD is a small USB interface board for
16171 alphanumeric LCD modules. See <http://www.usblcd.de> for more
16174 This code is also available as a module ( = code which can be
16175 inserted in and removed from the running kernel whenever you want).
16176 The module will be called usblcd.o. If you want to compile it as
16177 a module, say M here and read <file:Documentation/modules.txt>.
16179 D-Link DSB-R100 FM radio support
16181 Say Y here if you want to connect this type of radio to your
16182 computer's USB port. Note that the audio is not digital, and
16183 you must connect the line out connector to a sound card or a
16186 This driver uses the Video For Linux API. You must enable
16187 (Y or M in config) Video For Linux (under Character Devices)
16188 to use this driver. Information on this API and pointers to
16189 "v4l" programs may be found on the WWW at
16190 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
16192 This code is also available as a module ( = code which can be
16193 inserted in and removed from the running kernel whenever you want).
16194 The module will be called dsbr100.o. If you want to compile it as a
16195 module, say M here and read <file:Documentation/modules.txt>.
16197 Alcatel Speedtouch USB support
16198 CONFIG_USB_SPEEDTOUCH
16199 Say Y here if you have an Alcatel SpeedTouch USB or SpeedTouch 330
16200 modem. In order to use your modem you will need to install some user
16201 space tools, see <http://www.linux-usb.org/SpeedTouch/> for details.
16203 This code is also available as a module ( = code which can be
16204 inserted in and removed from the running kernel whenever you want).
16205 The module will be called speedtch.o. If you want to compile it as
16206 a module, say M here and read <file:Documentation/modules.txt>.
16209 USB is a master/slave protocol, organized with one master
16210 host (such as a PC) controlling up to 127 peripheral devices.
16211 The USB hardware is asymmetric, which makes it easier to set up:
16212 you can't connect two "to-the-host" connectors to each other.
16214 Linux can run in the host, or in the peripheral. In both cases
16215 you need a low level bus controller driver, and some software
16216 talking to it. Peripheral controllers are often discrete silicon,
16217 or are integrated with the CPU in a microcontroller. The more
16218 familiar host side controllers have names like like "EHCI", "OHCI",
16219 or "UHCI", and are usually integrated into southbridges on PC
16222 Enable this configuration option if you want to run Linux inside
16223 a USB peripheral device. Configure one hardware driver for your
16224 peripheral/device side bus controller, and a "gadget driver" for
16225 your peripheral protocol. (If you use modular gadget drivers,
16226 you may configure more than one.)
16228 If in doubt, say "N" and don't enable these drivers; most people
16229 don't have this kind of hardware (except maybe inside Linux PDAs).
16232 NetChip 2280 is a PCI based USB peripheral controller which
16233 supports both full and high speed USB 2.0 data transfers.
16235 It has six configurable endpoints, as well as endpoint zero
16236 (for control transfers) and several endpoints with dedicated
16239 Say "y" to link the driver statically, or "m" to build a
16240 dynamically linked module called "net2280" and force all
16241 gadget drivers to also be dynamically linked.
16244 Gadget Zero is a two-configuration device. It either sinks and
16245 sources bulk data; or it loops back a configurable number of
16246 transfers. It also implements control requests, for "chapter 9"
16247 conformance. The driver needs only two bulk-capable endpoints, so
16248 it can work on top of most device-side usb controllers. It's
16249 useful for testing, and is also a working example showing how
16250 USB "gadget drivers" can be written.
16252 Make this be the first driver you try using on top of any new
16253 USB peripheral controller driver. Then you can use host-side
16254 test software, like the "usbtest" driver, to put your hardware
16255 and its driver through a basic set of functional tests.
16257 Gadget Zero also works with the host-side "usb-skeleton" driver,
16258 and with many kinds of host-side test software. You may need
16259 to tweak product and vendor IDs before host software knows about
16260 this device, and arrange to select an appropriate configuration.
16262 Say "y" to link the driver statically, or "m" to build a
16263 dynamically linked module called "g_zero".
16266 This driver implements Ethernet style communication, in either
16269 - The "Communication Device Class" (CDC) Ethernet Control Model.
16270 That protocol is often avoided with pure Ethernet adapters, in
16271 favor of simpler vendor-specific hardware, but is widely
16272 supported by firmware for smart network devices.
16274 - On hardware can't implement that protocol, a simpler approach
16275 is used, placing fewer demands on USB.
16277 Within the USB device, this gadget driver exposes a network device
16278 "usbX", where X depends on what other networking devices you have.
16279 Treat it like a two-node Ethernet link: host, and gadget.
16281 The Linux-USB host-side "usbnet" driver interoperates with this
16282 driver, so that deep I/O queues can be supported. On 2.4 kernels,
16283 use "CDCEther" instead, if you're using the CDC option. That CDC
16284 mode should also interoperate with standard CDC Ethernet class
16285 drivers on other host operating systems.
16287 Say "y" to link the driver statically, or "m" to build a
16288 dynamically linked module called "g_ether".
16290 CONFIG_USB_ETH_RNDIS
16291 Microsoft Windows XP bundles the "Remote NDIS" (RNDIS) protocol,
16292 and Microsoft provides redistributable binary RNDIS drivers for
16293 older versions of Windows.
16295 If you say "y" here, the Ethernet gadget driver will try to provide
16296 a second device configuration, supporting RNDIS to talk to such
16297 Microsoft USB hosts.
16299 CONFIG_USB_FILE_STORAGE
16300 The File-backed Storage Gadget acts as a USB Mass Storage
16301 disk drive. As its storage repository it can use a regular
16302 file or a block device (in much the same way as the "loop"
16303 device driver), specified as a module parameter.
16305 CONFIG_USB_FILE_STORAGE_TEST
16306 Say "y" to generate the larger testing version of the
16307 File-backed Storage Gadget, useful for probing the
16308 behavior of USB Mass Storage hosts. Not needed for
16311 Always do synchronous disk IO for UBD
16312 CONFIG_BLK_DEV_UBD_SYNC
16313 The User-Mode Linux port includes a driver called UBD which will let
16314 you access arbitrary files on the host computer as block devices.
16315 Writes to such a block device are not immediately written to the
16316 host's disk; this may cause problems if, for example, the User-Mode
16317 Linux 'Virtual Machine' uses a journalling file system and the host
16320 Synchronous operation (i.e. always writing data to the host's disk
16321 immediately) is configurable on a per-UBD basis by using a special
16322 kernel command line option. Alternatively, you can say Y here to
16323 turn on synchronous operation by default for all block.
16325 If you're running a journalling file system (like reiserfs, for
16326 example) in your virtual machine, you will want to say Y here. If
16327 you care for the safety of the data in your virtual machine, Y is a
16328 wise choice too. In all other cases (for example, if you're just
16329 playing around with User-Mode Linux) you can choose N.
16331 Enable ptrace proxy
16333 This option enables a debugging interface which allows gdb to debug
16334 the kernel without needing to actually attach to kernel threads.
16335 If you want to do kernel debugging, say Y here; otherwise say N.
16339 The user mode linux management console is a low-level interface to
16340 the kernel, somewhat like the i386 SysRq interface. Since there is
16341 a full-blown operating system running under every user mode linux
16342 instance, there is much greater flexibility possible than with the
16345 If you answer 'Y' to this option, to use this feature, you need the
16346 mconsole client (called uml_mconsole) which is present in CVS in
16347 2.4.5-9um and later (path /tools/mconsole), and is also in the
16348 distribution RPM package in 2.4.6 and later.
16350 It is safe to say 'Y' here.
16352 Enable kernel debugging symbols
16354 When this is enabled, the User-Mode Linux binary will include
16355 debugging symbols. This enlarges the binary by a few megabytes,
16356 but aids in tracking down kernel problems in UML. It is required
16357 if you intend to do any kernel development.
16359 If you're truly short on disk space or don't expect to report any
16360 bugs back to the UML developers, say N, otherwise say Y.
16362 Enable gcov support
16364 This option allows developers to retrieve coverage data from a UML
16367 See <http://user-mode-linux.sourceforge.net/gcov.html> for more
16370 If you're involved in UML kernel development and want to use gcov,
16371 say Y. If you're unsure, say N.
16373 Enable gprof support
16375 This allows profiling of a User-Mode Linux kernel with the gprof
16378 See <http://user-mode-linux.sourceforge.net/gprof.html> for more
16381 If you're involved in UML kernel development and want to use gprof,
16382 say Y. If you're unsure, say N.
16386 While the User-Mode Linux port uses its own root file system for
16387 booting and normal file access, this module lets the UML user
16388 access files stored on the host. It does not require any
16389 network connection between the Host and UML. An example use of
16392 mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
16394 where /tmp/fromhost is an empty directory inside UML and
16395 /tmp/umlshare is a directory on the host with files the UML user
16398 For more information, see
16399 <http://user-mode-linux.sourceforge.net/hostfs.html>.
16401 If you'd like to be able to work with files stored on the host,
16402 say Y or M here; otherwise say N.
16404 Example IO Memory driver
16406 The User-Mode Linux port can provide support for IO Memory
16407 emulation with this option. This allows a host file to be
16408 specified as an I/O region on the kernel command line. That file
16409 will be mapped into UML's kernel address space where a driver can
16410 locate it and do whatever it wants with the memory, including
16411 providing an interface to it for UML processes to use.
16413 For more information, see
16414 <http://user-mode-linux.sourceforge.net/iomem.html>.
16416 If you'd like to be able to provide a simulated IO port space for
16417 User-Mode Linux processes, say Y. If unsure, say N.
16419 Virtual Serial Line
16421 The User-Mode Linux environment allows you to create virtual serial
16422 lines on the UML that are usually made to show up on the host as
16425 See <http://user-mode-linux.sourceforge.net/input.html> for more
16426 information and command line examples of how to use this facility.
16428 Unless you have a specific reason for disabling this, say Y.
16430 Virtual network device
16432 While the User-Mode port cannot directly talk to any physical
16433 hardware devices, this choice and the following transport options
16434 provide one or more virtual network devices through which the UML
16435 kernels can talk to each other, the host, and with the host's help,
16436 machines on the outside world.
16438 For more information, including explanations of the networking and
16439 sample configurations, see
16440 <http://user-mode-linux.sourceforge.net/networking.html>.
16442 If you'd like to be able to enable networking in the User-Mode
16443 linux environment, say Y; otherwise say N. Note that you must
16444 enable at least one of the following transport options to actually
16445 make use of UML networking.
16448 CONFIG_UML_NET_DAEMON
16449 This User-Mode Linux network transport allows one or more running
16450 UMLs on a single host to communicate with each other, but not to
16453 To use this form of networking, you'll need to run the UML
16454 networking daemon on the host.
16456 For more information, see
16457 <http://user-mode-linux.sourceforge.net/networking.html> That site
16458 has examples of the UML command line to use to enable Daemon
16461 If you'd like to set up a network with other UMLs on a single host,
16462 say Y. If you need a network between UMLs on multiple physical
16463 hosts, choose the Multicast Transport. To set up a network with
16464 the host and/or other IP machines, say Y to the Ethertap or Slip
16465 transports. You'll need at least one of them, but may choose
16466 more than one without conflict. If you don't need UML networking,
16470 CONFIG_UML_NET_ETHERTAP
16471 The Ethertap User-Mode Linux network transport allows a single
16472 running UML to exchange packets with its host over one of the
16473 host's Ethertap devices, such as /dev/tap0. Additional running
16474 UMLs can use additional Ethertap devices, one per running UML.
16475 While the UML believes it's on a (multi-device, broadcast) virtual
16476 Ethernet network, it's in fact communicating over a point-to-point
16477 link with the host.
16479 To use this, your host kernel must have support for Ethertap
16480 devices. Also, if your host kernel is 2.4.x, it must have
16481 CONFIG_NETLINK_DEV configured as Y or M.
16483 For more information, see
16484 <http://user-mode-linux.sourceforge.net/networking.html> That site
16485 has examples of the UML command line to use to enable Ethertap
16488 If you'd like to set up an IP network with the host and/or the
16489 outside world, say Y to this, the Daemon Transport and/or the
16490 Slip Transport. You'll need at least one of them, but may choose
16491 more than one without conflict. If you don't need UML networking,
16495 CONFIG_UML_NET_TUNTAP
16496 The UML TUN/TAP network transport allows a UML instance to exchange
16497 packets with the host over a TUN/TAP device. This option will only
16498 work with a 2.4 host, unless you've applied the TUN/TAP patch to
16499 your 2.2 host kernel.
16501 To use this transport, your host kernel must have support for TUN/TAP
16502 devices, either built-in or as a module.
16504 Multicast transport
16505 CONFIG_UML_NET_MCAST
16506 This Multicast User-Mode Linux network transport allows multiple
16507 UMLs (even ones running on different host machines!) to talk to
16508 each other over a virtual ethernet network. However, it requires
16509 at least one UML with one of the other transports to act as a
16510 bridge if any of them need to be able to talk to their hosts or any
16513 To use this, your host kernel(s) must support IP Multicasting.
16515 For more information, see
16516 <http://user-mode-linux.sourceforge.net/networking.html> That site
16517 has examples of the UML command line to use to enable Multicast
16518 networking, and notes about the security of this approach.
16520 If you need UMLs on multiple physical hosts to communicate as if
16521 they shared an Ethernet network, say Y. If you need to communicate
16522 with other IP machines, make sure you select one of the other
16523 transports (possibly in addition to Multicast; they're not
16524 exclusive). If you don't need to network UMLs say N to each of
16528 CONFIG_UML_NET_SLIP
16529 The Slip User-Mode Linux network transport allows a running UML to
16530 network with its host over a point-to-point link. Unlike Ethertap,
16531 which can carry any Ethernet frame (and hence even non-IP packets),
16532 the Slip transport can only carry IP packets.
16534 To use this, your host must support Slip devices.
16536 For more information, see
16537 <http://user-mode-linux.sourceforge.net/networking.html>. That site
16538 has examples of the UML command line to use to enable Slip
16539 networking, and details of a few quirks with it.
16541 The Ethertap Transport is preferred over Slip because of its
16542 limitation. If you prefer Slip, however, say Y here. Otherwise
16543 choose the Multicast transport (to network multiple UMLs on
16544 multiple hosts), Ethertap (to network with the host and the
16545 outside world), and/or the Daemon transport (to network multiple
16546 UMLs on a single host). You may choose more than one without
16547 conflict. If you don't need UML networking, say N.
16549 Microtek USB scanner support
16550 CONFIG_USB_MICROTEK
16551 Say Y here if you want support for the Microtek X6USB and
16552 possibly the Phantom 336CX, Phantom C6 and ScanMaker V6U(S)L.
16553 Support for anything but the X6 is experimental.
16554 Please report failures and successes.
16555 The scanner will appear as a scsi generic device to the rest
16556 of the system. Scsi support is required for this driver to compile
16557 and work. SANE 1.0.4 or newer is needed to make use of your scanner.
16558 This driver can be compiled as a module.
16560 HP53xx and Minolta Dual Scanner support
16561 CONFIG_USB_HPUSBSCSI
16562 Say Y here if you want support for the HP 53xx series of scanners
16563 and the Minolta Scan Dual. This driver is experimental.
16564 The scanner will be accessible as a SCSI device.
16566 USB Bluetooth support
16567 CONFIG_USB_BLUETOOTH
16568 Say Y here if you want to connect a USB Bluetooth device to your
16569 computer's USB port. You will need the Bluetooth stack (available
16570 at <http://developer.axis.com/software>) to fully use the device.
16572 This code is also available as a module ( = code which can be
16573 inserted in and removed from the running kernel whenever you want).
16574 The module will be called bluetooth.o. If you want to compile it as
16575 a module, say M here and read <file:Documentation/modules.txt>.
16579 Say Y here if you want to connect a USB MIDI device to your
16580 computer's USB port. This driver is for devices that comply with
16581 'Universal Serial Bus Device Class Definition for MIDI Device'.
16583 The following devices are known to work:
16584 * Steinberg USB2MIDI
16593 This code is also available as a module ( = code which can be
16594 inserted in and removed from the running kernel whenever you want).
16595 The module will be called usb-midi.o. If you want to compile it as a
16596 module, say M here and read <file:Documentation/modules.txt>.
16600 Minix is a simple operating system used in many classes about OS's.
16601 The minix file system (method to organize files on a hard disk
16602 partition or a floppy disk) was the original file system for Linux,
16603 but has been superseded by the second extended file system ext2fs.
16604 You don't want to use the minix file system on your hard disk
16605 because of certain built-in restrictions, but it is sometimes found
16606 on older Linux floppy disks. This option will enlarge your kernel
16607 by about 28 KB. If unsure, say N.
16609 If you want to compile this as a module ( = code which can be
16610 inserted in and removed from the running kernel whenever you want),
16611 say M here and read <file:Documentation/modules.txt>. The module
16612 will be called minix.o. Note that the file system of your root
16613 partition (the one containing the directory /) cannot be compiled as
16618 Stores not just filenames but the files themselves in a balanced
16619 tree. Uses journalling.
16621 Balanced trees are more efficient than traditional file system
16622 architectural foundations.
16624 In general, ReiserFS is as fast as ext2, but is very efficient with
16625 large directories and small files. It is much faster for writes,
16626 and slightly slower for reads than ext2. It is much faster than
16627 ext3. It will be obsoleted by Reiser4 in not too long, so keep
16628 an eye on our website for when Reiser4 ships.
16630 Mount with the notail option if performance matters more to you than
16631 saving space (the design flaw underlying this is fixed in reiser4).
16633 Read <http://www.namesys.com> to learn more about reiserfs.
16635 Enable extra Reiserfs consistency checks
16636 CONFIG_REISERFS_CHECK
16637 If you set this to Y, then ReiserFS will perform every check it can
16638 possibly imagine of its internal consistency throughout its
16639 operation. It will also go substantially slower. More than once we
16640 have forgotten that this was on, and then gone despondent over the
16641 latest benchmarks.:-) Use of this option allows our team to go all
16642 out in checking for consistency when debugging without fear of its
16643 effect on end users. If you are on the verge of sending in a bug
16644 report, say Y and you might get a useful error message. Almost
16645 everyone should say N.
16647 Publish some reiserfs-specific info under /proc/fs/reiserfs
16648 CONFIG_REISERFS_PROC_INFO
16649 Create under /proc/fs/reiserfs a hierarchy of files, displaying
16650 various ReiserFS statistics and internal data at the expense of making
16651 your kernel or module slightly larger (+8 KB). This also increases the
16652 amount of kernel memory required for each mount by 440 bytes.
16653 It isn't useful to average persons, and you probably can't measure the
16654 performance cost of it. If you are fine-tuning reiserfs, say Y,
16657 Second extended fs support
16659 This is the de facto standard Linux file system (method to organize
16660 files on a storage device) for hard disks.
16662 You want to say Y here, unless you intend to use Linux exclusively
16663 from inside a DOS partition using the UMSDOS file system. The
16664 advantage of the latter is that you can get away without
16665 repartitioning your hard drive (which often implies backing
16666 everything up and restoring afterwards); the disadvantage is that
16667 Linux becomes susceptible to DOS viruses and that UMSDOS is somewhat
16668 slower than ext2fs. Even if you want to run Linux in this fashion,
16669 it might be a good idea to have ext2fs around: it enables you to
16670 read more floppy disks and facilitates the transition to a *real*
16671 Linux partition later. Another (rare) case which doesn't require
16672 ext2fs is a diskless Linux box which mounts all files over the
16673 network using NFS (in this case it's sufficient to say Y to "NFS
16674 file system support" below). Saying Y here will enlarge your kernel
16677 The Ext2fs-Undeletion mini-HOWTO, available from
16678 <http://www.tldp.org/docs.html#howto>, gives information about
16679 how to retrieve deleted files on ext2fs file systems.
16681 To change the behaviour of ext2 file systems, you can use the tune2fs
16682 utility ("man tune2fs"). To modify attributes of files and
16683 directories on ext2 file systems, use chattr ("man chattr").
16685 Ext2fs partitions can be read from within DOS using the ext2tool
16686 command line tool package (available from
16687 <ftp://ibiblio.org/pub/Linux/system/filesystems/ext2/>) and from
16688 within Windows NT using the ext2nt command line tool package from
16689 <ftp://ibiblio.org/pub/Linux/utils/dos/>. Explore2fs is a
16690 graphical explorer for ext2fs partitions which runs on Windows 95
16691 and Windows NT and includes experimental write support; it is
16693 <http://jnewbigin-pc.it.swin.edu.au/Linux/Explore2fs.htm>.
16695 If you want to compile this file system as a module ( = code which
16696 can be inserted in and removed from the running kernel whenever you
16697 want), say M here and read <file:Documentation/modules.txt>. The
16698 module will be called ext2.o. Be aware however that the file system
16699 of your root partition (the one containing the directory /) cannot
16700 be compiled as a module, and so this could be dangerous. Most
16701 everyone wants to say Y here.
16703 Ext3 journalling file system support (EXPERIMENTAL)
16705 This is the journalling version of the Second extended file system
16706 (often called ext3), the de facto standard Linux file system
16707 (method to organize files on a storage device) for hard disks.
16709 The journalling code included in this driver means you do not have
16710 to run e2fsck (file system checker) on your file systems after a
16711 crash. The journal keeps track of any changes that were being made
16712 at the time the system crashed, and can ensure that your file system
16713 is consistent without the need for a lengthy check.
16715 Other than adding the journal to the file system, the on-disk format
16716 of ext3 is identical to ext2. It is possible to freely switch
16717 between using the ext3 driver and the ext2 driver, as long as the
16718 file system has been cleanly unmounted, or e2fsck is run on the file
16721 To add a journal on an existing ext2 file system or change the
16722 behaviour of ext3 file systems, you can use the tune2fs utility ("man
16723 tune2fs"). To modify attributes of files and directories on ext3
16724 file systems, use chattr ("man chattr"). You need to be using
16725 e2fsprogs version 1.20 or later in order to create ext3 journals
16726 (available at <http://sourceforge.net/projects/e2fsprogs/>).
16728 If you want to compile this file system as a module ( = code which
16729 can be inserted in and removed from the running kernel whenever you
16730 want), say M here and read <file:Documentation/modules.txt>. The
16731 module will be called ext3.o. Be aware however that the file system
16732 of your root partition (the one containing the directory /) cannot
16733 be compiled as a module, and so this may be dangerous.
16735 Journal Block Device support (JBD for ext3) (EXPERIMENTAL)
16737 This is a generic journalling layer for block devices. It is
16738 currently used by the ext3 file system, but it could also be used to
16739 add journal support to other file systems or block devices such as
16742 If you are using the ext3 file system, you need to say Y here. If
16743 you are not using ext3 then you will probably want to say N.
16745 If you want to compile this device as a module ( = code which can be
16746 inserted in and removed from the running kernel whenever you want),
16747 say M here and read <file:Documentation/modules.txt>. The module
16748 will be called jbd.o. If you are compiling ext3 into the kernel,
16749 you cannot compile this code as a module.
16751 JBD (ext3) debugging support
16753 If you are using the ext3 journalling file system (or potentially any
16754 other file system/device using JBD), this option allows you to
16755 enable debugging output while the system is running, in order to
16756 help track down any problems you are having. By default the
16757 debugging output will be turned off.
16759 If you select Y here, then you will be able to turn on debugging
16760 with "echo N > /proc/sys/fs/jbd-debug", where N is a number between
16761 1 and 5, the higher the number, the more debugging output is
16762 generated. To turn debugging off again, do
16763 "echo 0 > /proc/sys/fs/jbd-debug".
16765 Buffer Head tracing (DEBUG)
16766 CONFIG_BUFFER_DEBUG
16767 If you are a kernel developer working with file systems or in the
16768 block device layer, this buffer head tracing may help you to track
16769 down bugs in your code. This enables some debugging macros
16770 (BUFFER_TRACE, etc.) which allow you to track the state of a buffer
16771 through various layers of code. The debugging code is used
16772 primarily by ext3 and JBD code.
16774 Because this option adds considerably to the size of each buffer,
16775 most people will want to say N here.
16777 BeOS filesystem support (BeFS) (read only)
16779 The BeOS File System (BeFS) is the native file system of Be, Inc's
16780 BeOS. Notable features include support for arbitrary attributes
16781 on files and directories, and database-like indices on selected
16782 attributes. (Also note that this driver doesn't make those features
16783 available at this time). It is a 64 bit filesystem, so it supports
16784 extremely large volumes and files.
16786 If you use this filesystem, you should also say Y to at least one
16787 of the NLS (native language support) options below.
16789 If you don't know what this is about, say N.
16791 If you want to compile this as a module ( = code which can be
16792 inserted in and removed from the running kernel whenever you want),
16793 say M here and read Documentation/modules.txt. The module will be
16798 If you say Y here, you can use the 'debug' mount option to enable
16799 debugging output from the driver. This is unlike previous versions
16800 of the driver, where enabling this option would turn on debugging
16801 output automatically.
16804 mount -t befs /dev/hda2 /mnt -o debug
16806 BFS file system support
16808 Boot File System (BFS) is a file system used under SCO UnixWare to
16809 allow the bootloader access to the kernel image and other important
16810 files during the boot process. It is usually mounted under /stand
16811 and corresponds to the slice marked as "STAND" in the UnixWare
16812 partition. You should say Y if you want to read or write the files
16813 on your /stand slice from within Linux. You then also need to say Y
16814 to "UnixWare slices support", below. More information about the BFS
16815 file system is contained in the file
16816 <file:Documentation/filesystems/bfs.txt>.
16818 If you don't know what this is about, say N.
16820 If you want to compile this as a module ( = code which can be
16821 inserted in and removed from the running kernel whenever you want),
16822 say M here and read <file:Documentation/modules.txt>. The module
16823 will be called bfs.o. Note that the file system of your root
16824 partition (the one containing the directory /) cannot be compiled as
16827 Compressed ROM file system support
16829 Saying Y here includes support for CramFs (Compressed ROM File
16830 System). CramFs is designed to be a simple, small, and compressed
16831 file system for ROM based embedded systems. CramFs is read-only,
16832 limited to 256MB file systems (with 16MB files), and doesn't support
16833 16/32 bits uid/gid, hard links and timestamps.
16835 See <file:Documentation/filesystems/cramfs.txt> and
16836 <file:fs/cramfs/README> for further information.
16838 If you want to compile this as a module ( = code which can be
16839 inserted in and removed from the running kernel whenever you want),
16840 say M here and read <file:Documentation/modules.txt>. The module
16841 will be called cramfs.o. Note that the root file system (the one
16842 containing the directory /) cannot be compiled as a module.
16846 CMS file system support
16848 Read only support for CMS minidisk file systems found on IBM
16849 mainframe systems. Only the basic format is supported so far. If
16850 you don't know what CMS is you probably don't want to know any more.
16852 # When the 2.5 version of configure.help goes away, the part of this that
16853 # duplicates Documentation/filesystems/tmpfs.txt can drop out.
16854 Virtual memory file system support
16856 Tmpfs is a file system which keeps all files in virtual memory.
16857 Everything in tmpfs is temporary in the sense that no files will be
16858 created on your hard drive. If you reboot, everything in tmpfs will
16861 In contrast to RAM disks, which get allocated a fixed amount of
16862 physical RAM, tmpfs grows and shrinks to accommodate the files it
16863 contains and is able to swap unneeded pages out to swap space.
16865 Everything is "virtual" in the sense that no files will be created
16866 on your hard drive; if you reboot, everything in tmpfs will be
16869 You should mount the file system somewhere to be able to use
16870 POSIX shared memory. Adding the following line to /etc/fstab should
16871 take care of things:
16873 tmpfs /dev/shm tmpfs defaults 0 0
16875 Remember to create the directory that you intend to mount tmpfs on
16876 if necessary (/dev/shm is automagically created if you use devfs).
16878 You can set limits for the number of blocks and inodes used by the
16879 file system with the mount options "size", "nr_blocks" and
16880 "nr_inodes". These parameters accept a suffix k, m or g for kilo,
16881 mega and giga and can be changed on remount.
16883 The initial permissions of the root directory can be set with the
16884 mount option "mode".
16886 See <file:Documentation/filesystems/tmpfs.txt> for details.
16888 Simple RAM-based file system support
16890 Ramfs is a file system which keeps all files in RAM. It allows
16891 read and write access.
16893 It is more of an programming example than a usable file system. If
16894 you need a file system which lives in RAM with limit checking use
16897 If you want to compile this as a module ( = code which can be
16898 inserted in and removed from the running kernel whenever you want),
16899 say M here and read <file:Documentation/modules.txt>. The module
16900 will be called ramfs.o.
16902 ISO 9660 CD-ROM file system support
16904 This is the standard file system used on CD-ROMs. It was previously
16905 known as "High Sierra File System" and is called "hsfs" on other
16906 Unix systems. The so-called Rock-Ridge extensions which allow for
16907 long Unix filenames and symbolic links are also supported by this
16908 driver. If you have a CD-ROM drive and want to do more with it than
16909 just listen to audio CDs and watch its LEDs, say Y (and read
16910 <file:Documentation/filesystems/isofs.txt> and the CD-ROM-HOWTO,
16911 available from <http://www.tldp.org/docs.html#howto>), thereby
16912 enlarging your kernel by about 27 KB; otherwise say N.
16914 If you want to compile this as a module ( = code which can be
16915 inserted in and removed from the running kernel whenever you want),
16916 say M here and read <file:Documentation/modules.txt>. The module
16917 will be called isofs.o.
16919 Microsoft Joliet CD-ROM extensions
16921 Joliet is a Microsoft extension for the ISO 9660 CD-ROM file system
16922 which allows for long filenames in unicode format (unicode is the
16923 new 16 bit character code, successor to ASCII, which encodes the
16924 characters of almost all languages of the world; see
16925 <http://www.unicode.org/> for more information). Say Y here if you
16926 want to be able to read Joliet CD-ROMs under Linux.
16928 Transparent decompression extension
16930 This is a Linux-specific extension to RockRidge which lets you store
16931 data in compressed form on a CD-ROM and have it transparently
16932 decompressed when the CD-ROM is accessed. See
16933 <http://www.kernel.org/pub/linux/utils/fs/zisofs/> for the tools
16934 necessary to create such a filesystem. Say Y here if you want to be
16935 able to read such compressed CD-ROMs.
16937 UDF file system support (read-only)
16939 This is the new file system used on some CD-ROMs and DVDs. Say Y if
16940 you intend to mount DVD discs or CDRW's written in packet mode, or
16941 if written to by other UDF utilities, such as DirectCD. This UDF
16942 file system support is read-only. If you want to write to UDF
16943 file systems on some media, you need to say Y to "UDF read-write
16944 support" below in addition. Please read
16945 <file:Documentation/filesystems/udf.txt>.
16947 This file system support is also available as a module ( = code
16948 which can be inserted in and removed from the running kernel
16949 whenever you want). The module is called udf.o. If you want to
16950 compile it as a module, say M here and read
16951 <file:Documentation/modules.txt>.
16955 UDF write support (DANGEROUS)
16957 Say Y if you want to test write support for UDF file systems.
16958 Due to lack of support for writing to CDR/CDRW's, this option
16959 is only supported for hard discs, DVD-RAM, and loopback files.
16963 If you want to use one of the FAT-based file systems (the MS-DOS,
16964 VFAT (Windows 95) and UMSDOS (used to run Linux on top of an
16965 ordinary DOS partition) file systems), then you must say Y or M here
16966 to include FAT support. You will then be able to mount partitions or
16967 diskettes with FAT-based file systems and transparently access the
16968 files on them, i.e. MSDOS files will look and behave just like all
16971 This FAT support is not a file system in itself, it only provides
16972 the foundation for the other file systems. You will have to say Y or
16973 M to at least one of "MSDOS fs support" or "VFAT fs support" in
16974 order to make use of it.
16976 Another way to read and write MSDOS floppies and hard drive
16977 partitions from within Linux (but not transparently) is with the
16978 mtools ("man mtools") program suite. You don't need to say Y here in
16981 If you need to move large files on floppies between a DOS and a
16982 Linux box, say Y here, mount the floppy under Linux with an MSDOS
16983 file system and use GNU tar's M option. GNU tar is a program
16984 available for Unix and DOS ("man tar" or "info tar").
16986 It is now also becoming possible to read and write compressed FAT
16987 file systems; read <file:Documentation/filesystems/fat_cvf.txt> for
16990 The FAT support will enlarge your kernel by about 37 KB. If unsure,
16993 If you want to compile this as a module however ( = code which can
16994 be inserted in and removed from the running kernel whenever you
16995 want), say M here and read <file:Documentation/modules.txt>. The
16996 module will be called fat.o. Note that if you compile the FAT
16997 support as a module, you cannot compile any of the FAT-based file
16998 systems into the kernel -- they will have to be modules as well.
16999 The file system of your root partition (the one containing the
17000 directory /) cannot be a module, so don't say M here if you intend
17001 to use UMSDOS as your root file system.
17005 This allows you to mount MSDOS partitions of your hard drive (unless
17006 they are compressed; to access compressed MSDOS partitions under
17007 Linux, you can either use the DOS emulator DOSEMU, described in the
17008 DOSEMU-HOWTO, available from
17009 <http://www.tldp.org/docs.html#howto>, or try dmsdosfs in
17010 <ftp://ibiblio.org/pub/Linux/system/filesystems/dosfs/>. If you
17011 intend to use dosemu with a non-compressed MSDOS partition, say Y
17012 here) and MSDOS floppies. This means that file access becomes
17013 transparent, i.e. the MSDOS files look and behave just like all
17016 If you want to use UMSDOS, the Unix-like file system on top of a
17017 DOS file system, which allows you to run Linux from within a DOS
17018 partition without repartitioning, you'll have to say Y or M here.
17020 If you have Windows 95 or Windows NT installed on your MSDOS
17021 partitions, you should use the VFAT file system (say Y to "VFAT fs
17022 support" below), or you will not be able to see the long filenames
17023 generated by Windows 95 / Windows NT.
17025 This option will enlarge your kernel by about 7 KB. If unsure,
17026 answer Y. This will only work if you said Y to "DOS FAT fs support"
17027 as well. If you want to compile this as a module however ( = code
17028 which can be inserted in and removed from the running kernel
17029 whenever you want), say M here and read
17030 <file:Documentation/modules.txt>.
17031 The module will be called msdos.o.
17033 VFAT (Windows-95) fs support
17035 This option provides support for normal Windows file systems with
17036 long filenames. That includes non-compressed FAT-based file systems
17037 used by Windows 95, Windows 98, Windows NT 4.0, and the Unix
17038 programs from the mtools package.
17040 You cannot use the VFAT file system for your Linux root partition
17041 (the one containing the directory /); use UMSDOS instead if you
17042 want to run Linux from within a DOS partition (i.e. say Y to
17043 "Unix like fs on top of std MSDOS fs", below).
17045 The VFAT support enlarges your kernel by about 10 KB and it only
17046 works if you said Y to the "DOS FAT fs support" above. Please read
17047 the file <file:Documentation/filesystems/vfat.txt> for details. If
17050 If you want to compile this as a module ( = code which can be
17051 inserted in and removed from the running kernel whenever you want),
17052 say M here and read <file:Documentation/modules.txt>. The module
17053 will be called vfat.o.
17055 Unix-like file system on top of standard MSDOS fs
17057 Say Y here if you want to run Linux from within an existing DOS
17058 partition of your hard drive. The advantage of this is that you can
17059 get away without repartitioning your hard drive (which often implies
17060 backing everything up and restoring afterwards) and hence you're
17061 able to quickly try out Linux or show it to your friends; the
17062 disadvantage is that Linux becomes susceptible to DOS viruses and
17063 that UMSDOS is somewhat slower than ext2fs. Another use of UMSDOS
17064 is to write files with long unix filenames to MSDOS floppies; it
17065 also allows Unix-style soft-links and owner/permissions of files on
17066 MSDOS floppies. You will need a program called umssync in order to
17067 make use of UMSDOS; read
17068 <file:Documentation/filesystems/umsdos.txt>.
17070 To get utilities for initializing/checking UMSDOS file system, or
17071 latest patches and/or information, visit the UMSDOS home page at
17072 <http://www.voyager.hr/~mnalis/umsdos/>.
17074 This option enlarges your kernel by about 28 KB and it only works if
17075 you said Y to both "DOS FAT fs support" and "MSDOS fs support"
17076 above. If you want to compile this as a module ( = code which can
17077 be inserted in and removed from the running kernel whenever you
17078 want), say M here and read <file:Documentation/modules.txt>. The
17079 module will be called umsdos.o. Note that the file system of your
17080 root partition (the one containing the directory /) cannot be a
17081 module, so saying M could be dangerous. If unsure, say N.
17083 /proc file system support
17085 This is a virtual file system providing information about the status
17086 of the system. "Virtual" means that it doesn't take up any space on
17087 your hard disk: the files are created on the fly by the kernel when
17088 you try to access them. Also, you cannot read the files with older
17089 version of the program less: you need to use more or cat.
17091 It's totally cool; for example, "cat /proc/interrupts" gives
17092 information about what the different IRQs are used for at the moment
17093 (there is a small number of Interrupt ReQuest lines in your computer
17094 that are used by the attached devices to gain the CPU's attention --
17095 often a source of trouble if two devices are mistakenly configured
17096 to use the same IRQ). The program procinfo to display some
17097 information about your system gathered from the /proc file system.
17099 Before you can use the /proc file system, it has to be mounted,
17100 meaning it has to be given a location in the directory hierarchy.
17101 That location should be /proc. A command such as "mount -t proc proc
17102 /proc" or the equivalent line in /etc/fstab does the job.
17104 The /proc file system is explained in the file
17105 <file:Documentation/filesystems/proc.txt> and on the proc(5) manpage
17108 This option will enlarge your kernel by about 67 KB. Several
17109 programs depend on this, so everyone should say Y here.
17111 Support for PReP Residual Data
17112 CONFIG_PREP_RESIDUAL
17113 Some PReP systems have residual data passed to the kernel by the
17114 firmware. This allows detection of memory size, devices present and
17115 other useful pieces of information. Sometimes this information is
17116 not present or incorrect.
17118 Unless you expect to boot on a PReP system, there is no need to
17121 PReP residual data available in /proc/residual
17122 CONFIG_PROC_PREPRESIDUAL
17123 Enabling this option will create a /proc/residual file which allows
17124 you to get at the residual data on PReP systems. You will need a tool
17125 (lsresidual) to parse it. If you aren't on a PReP system, you don't
17128 /dev file system support
17130 This is support for devfs, a virtual file system (like /proc) which
17131 provides the file system interface to device drivers, normally found
17132 in /dev. Devfs does not depend on major and minor number
17133 allocations. Device drivers register entries in /dev which then
17134 appear automatically, which means that the system administrator does
17135 not have to create character and block special device files in the
17136 /dev directory using the mknod command (or MAKEDEV script) anymore.
17138 This is work in progress. If you want to use this, you *must* read
17139 the material in <file:Documentation/filesystems/devfs/>, especially
17140 the file README there.
17144 Automatically mount devfs at boot time
17146 This option appears if you have CONFIG_DEVFS_FS enabled. Setting
17147 this to 'Y' will make the kernel automatically mount devfs onto /dev
17148 when the system is booted, before the init thread is started.
17149 You can override this with the "devfs=nomount" boot option.
17155 If you say Y here, then the /dev file system code will generate
17156 debugging messages. See the file
17157 <file:Documentation/filesystems/devfs/boot-options> for more
17162 NFS file system support
17164 If you are connected to some other (usually local) Unix computer
17165 (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing
17166 on that computer (the NFS server) using the Network File Sharing
17167 protocol, say Y. "Mounting files" means that the client can access
17168 the files with usual UNIX commands as if they were sitting on the
17169 client's hard disk. For this to work, the server must run the
17170 programs nfsd and mountd (but does not need to have NFS file system
17171 support enabled in its kernel). NFS is explained in the Network
17172 Administrator's Guide, available from
17173 <http://www.tldp.org/docs.html#guide>, on its man page: "man
17174 nfs", and in the NFS-HOWTO.
17176 A superior but less widely used alternative to NFS is provided by
17177 the Coda file system; see "Coda file system support" below.
17179 If you say Y here, you should have said Y to TCP/IP networking also.
17180 This option would enlarge your kernel by about 27 KB.
17182 This file system is also available as a module ( = code which can be
17183 inserted in and removed from the running kernel whenever you want).
17184 The module is called nfs.o. If you want to compile it as a module,
17185 say M here and read <file:Documentation/modules.txt>.
17187 If you are configuring a diskless machine which will mount its root
17188 file system over NFS at boot time, say Y here and to "Kernel
17189 level IP autoconfiguration" above and to "Root file system on NFS"
17190 below. You cannot compile this driver as a module in this case.
17191 There are two packages designed for booting diskless machines over
17192 the net: netboot, available from
17193 <http://ftp1.sourceforge.net/netboot/>, and Etherboot,
17194 available from <http://ftp1.sourceforge.net/etherboot/>.
17196 If you don't know what all this is about, say N.
17198 Provide NFSv3 client support
17200 Say Y here if you want your NFS client to be able to speak the newer
17201 version 3 of the NFS protocol.
17205 Allow direct I/O on files in NFS
17206 CONFIG_NFS_DIRECTIO
17207 There are important applications whose performance or correctness
17208 depends on uncached access to file data. Database clusters (multiple
17209 copies of the same instance running on separate hosts) implement their
17210 own cache coherency protocol that subsumes the NFS cache protocols.
17211 Applications that process datasets considerably larger than the client's
17212 memory do not always benefit from a local cache. A streaming video
17213 server, for instance, has no need to cache the contents of a file.
17215 This option enables applications to perform direct I/O on files in NFS
17216 file systems using the O_DIRECT open() flag. When O_DIRECT is set for
17217 files, their data is not cached in the system's page cache. Direct
17218 read and write operations are aligned to block boundaries. Data is
17219 moved to and from user-level application buffers directly.
17221 Unless your program is designed to use O_DIRECT properly, you are much
17222 better off allowing the NFS client to manage caching for you. Misusing
17223 O_DIRECT can cause poor server performance or network storms. This
17224 kernel build option defaults OFF to avoid exposing system administrators
17225 unwittingly to a potentially hazardous feature.
17229 Root file system on NFS
17231 If you want your Linux box to mount its whole root file system (the
17232 one containing the directory /) from some other computer over the
17233 net via NFS (presumably because your box doesn't have a hard disk),
17234 say Y. Read <file:Documentation/nfsroot.txt> for details. It is
17235 likely that in this case, you also want to say Y to "Kernel level IP
17236 autoconfiguration" so that your box can discover its network address
17239 Most people say N here.
17243 If you want your Linux box to act as an NFS *server*, so that other
17244 computers on your local network which support NFS can access certain
17245 directories on your box transparently, you have two options: you can
17246 use the self-contained user space program nfsd, in which case you
17247 should say N here, or you can say Y and use the kernel based NFS
17248 server. The advantage of the kernel based solution is that it is
17251 In either case, you will need support software; the respective
17252 locations are given in the file <file:Documentation/Changes> in the
17255 If you say Y here, you will get support for version 2 of the NFS
17256 protocol (NFSv2). If you also want NFSv3, say Y to the next question
17259 Please read the NFS-HOWTO, available from
17260 <http://www.tldp.org/docs.html#howto>.
17262 The NFS server is also available as a module ( = code which can be
17263 inserted in and removed from the running kernel whenever you want).
17264 The module is called nfsd.o. If you want to compile it as a module,
17265 say M here and read <file:Documentation/modules.txt>. If unsure,
17268 Provide NFSv3 server support
17270 If you would like to include the NFSv3 server as well as the NFSv2
17271 server, say Y here. If unsure, say Y.
17273 Provide NFS over TCP server support
17275 If you want your NFS server to support TCP connections, say Y here.
17276 TCP connections usually perform better than the default UDP when
17277 the network is lossy or congested. If unsure, say Y.
17279 OS/2 HPFS file system support
17281 OS/2 is IBM's operating system for PC's, the same as Warp, and HPFS
17282 is the file system used for organizing files on OS/2 hard disk
17283 partitions. Say Y if you want to be able to read files from and
17284 write files to an OS/2 HPFS partition on your hard drive. OS/2
17285 floppies however are in regular MSDOS format, so you don't need this
17286 option in order to be able to read them. Read
17287 <file:Documentation/filesystems/hpfs.txt>.
17289 This file system is also available as a module ( = code which can be
17290 inserted in and removed from the running kernel whenever you want).
17291 The module is called hpfs.o. If you want to compile it as a module,
17292 say M here and read <file:Documentation/modules.txt>. If unsure,
17295 NTFS file system support (read-only)
17297 NTFS is the file system of Microsoft Windows NT. Say Y if you want
17298 to get read access to files on NTFS partitions of your hard drive.
17299 The Linux NTFS driver supports most of the mount options of the VFAT
17300 driver, see <file:Documentation/filesystems/ntfs.txt>. Saying Y here
17301 will give you read-only access to NTFS partitions.
17303 This code is also available as a module ( = code which can be
17304 inserted in and removed from the running kernel whenever you want).
17305 The module will be called ntfs.o. If you want to compile it as a
17306 module, say M here and read <file:Documentation/modules.txt>.
17308 NTFS write support (DANGEROUS)
17310 If you say Y here, you will (maybe) be able to write to NTFS file
17311 systems as well as read from them. The read-write support in NTFS
17312 is far from being complete and is not well tested. If you say Y
17313 here, back up your NTFS volume first, since it will probably get
17314 damaged. Also, download the Linux-NTFS project distribution from
17315 Sourceforge at <http://linux-ntfs.sf.net/> and always run the
17316 included ntfsfix utility after writing to an NTFS partition from
17317 Linux to fix some of the damage done by the driver. You should run
17318 ntfsfix _after_ unmounting the partition in Linux but _before_
17319 rebooting into Windows. When Windows next boots, chkdsk will be
17320 run automatically to fix the remaining damage.
17321 Please note that write support is limited to Windows NT4 and
17326 System V/Xenix/V7/Coherent file system support
17328 SCO, Xenix and Coherent are commercial Unix systems for Intel
17329 machines, and Version 7 was used on the DEC PDP-11. Saying Y
17330 here would allow you to read from their floppies and hard disk
17333 If you have floppies or hard disk partitions like that, it is likely
17334 that they contain binaries from those other Unix systems; in order
17335 to run these binaries, you will want to install linux-abi which is a
17336 a set of kernel modules that lets you run SCO, Xenix, Wyse,
17337 UnixWare, Dell Unix and System V programs under Linux. It is
17338 available via FTP (user: ftp) from
17339 <ftp://ftp.openlinux.org/pub/people/hch/linux-abi/>).
17340 NOTE: that will work only for binaries from Intel-based systems;
17341 PDP ones will have to wait until somebody ports Linux to -11 ;-)
17343 If you only intend to mount files from some other Unix over the
17344 network using NFS, you don't need the System V file system support
17345 (but you need NFS file system support obviously).
17347 Note that this option is generally not needed for floppies, since a
17348 good portable way to transport files and directories between unixes
17349 (and even other operating systems) is given by the tar program ("man
17350 tar" or preferably "info tar"). Note also that this option has
17351 nothing whatsoever to do with the option "System V IPC". Read about
17352 the System V file system in
17353 <file:Documentation/filesystems/sysv-fs.txt>.
17354 Saying Y here will enlarge your kernel by about 27 KB.
17356 If you want to compile this as a module ( = code which can be
17357 inserted in and removed from the running kernel whenever you want),
17358 say M here and read <file:Documentation/modules.txt>. The module
17359 will be called sysv.o.
17361 If you haven't heard about all of this before, it's safe to say N.
17363 Amiga FFS file system support
17365 The Fast File System (FFS) is the common file system used on hard
17366 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
17367 if you want to be able to read and write files from and to an Amiga
17368 FFS partition on your hard drive. Amiga floppies however cannot be
17369 read with this driver due to an incompatibility of the floppy
17370 controller used in an Amiga and the standard floppy controller in
17371 PCs and workstations. Read <file:Documentation/filesystems/affs.txt>
17372 and <file:fs/affs/Changes>.
17374 With this driver you can also mount disk files used by Bernd
17375 Schmidt's Un*X Amiga Emulator
17376 (<http://www.freiburg.linux.de/~uae/>).
17377 If you want to do this, you will also need to say Y or M to "Loop
17378 device support", above.
17380 This file system is also available as a module ( = code which can be
17381 inserted in and removed from the running kernel whenever you want).
17382 The module is called affs.o. If you want to compile it as a module,
17383 say M here and read <file:Documentation/modules.txt>. If unsure,
17386 Apple HFS file system support
17388 If you say Y here, you will be able to mount Macintosh-formatted
17389 floppy disks and hard drive partitions with full read-write access.
17390 Please read <file:fs/hfs/HFS.txt> to learn about the available mount
17393 This file system support is also available as a module ( = code
17394 which can be inserted in and removed from the running kernel
17395 whenever you want). The module is called hfs.o. If you want to
17396 compile it as a module, say M here and read
17397 <file:Documentation/modules.txt>.
17399 Apple HFS+ (Extended HFS) file system support
17401 If you say Y here, you will be able to mount extended format
17402 Macintosh-formatted hard drive partitions with full read-write access.
17404 This file system is often called HFS+ and was introduced with
17405 MacOS 8. It includes all Mac specific filesystem data such as
17406 data forks and creator codes, but it also has several UNIX
17407 style features such as file ownership and permissions.
17409 This file system is also available as a module ( = code which can
17410 be inserted in and removed from the running kernel whenever you
17411 want). The module is called hfsplus.o. If you want to compile it
17412 as a module, say M here and read Documentation/modules.txt.
17414 ROM file system support
17416 This is a very small read-only file system mainly intended for
17417 initial ram disks of installation disks, but it could be used for
17418 other read-only media as well. Read
17419 <file:Documentation/filesystems/romfs.txt> for details.
17421 This file system support is also available as a module ( = code
17422 which can be inserted in and removed from the running kernel
17423 whenever you want). The module is called romfs.o. If you want to
17424 compile it as a module, say M here and read
17425 <file:Documentation/modules.txt>. Note that the file system of your
17426 root partition (the one containing the directory /) cannot be a
17429 If you don't know whether you need it, then you don't need it:
17432 QNX4 file system support (read only)
17434 This is the file system used by the real-time operating systems
17435 QNX 4 and QNX 6 (the latter is also called QNX RTP).
17436 Further information is available at <http://www.qnx.com/>.
17437 Say Y if you intend to mount QNX hard disks or floppies.
17438 Unless you say Y to "QNX4FS read-write support" below, you will
17439 only be able to read these file systems.
17441 This file system support is also available as a module ( = code
17442 which can be inserted in and removed from the running kernel
17443 whenever you want). The module is called qnx4.o. If you want to
17444 compile it as a module, say M here and read
17445 <file:Documentation/modules.txt>.
17447 If you don't know whether you need it, then you don't need it:
17450 QNX4FS write support (DANGEROUS)
17452 Say Y if you want to test write support for QNX4 file systems.
17454 It's currently broken, so for now:
17457 Kernel automounter support
17459 The automounter is a tool to automatically mount remote file systems
17460 on demand. This implementation is partially kernel-based to reduce
17461 overhead in the already-mounted case; this is unlike the BSD
17462 automounter (amd), which is a pure user space daemon.
17464 To use the automounter you need the user-space tools from the autofs
17465 package; you can find the location in <file:Documentation/Changes>.
17466 You also want to answer Y to "NFS file system support", below.
17468 If you want to use the newer version of the automounter with more
17469 features, say N here and say Y to "Kernel automounter v4 support",
17472 If you want to compile this as a module ( = code which can be
17473 inserted in and removed from the running kernel whenever you want),
17474 say M here and read <file:Documentation/modules.txt>. The module
17475 will be called autofs.o.
17477 If you are not a part of a fairly large, distributed network, you
17478 probably do not need an automounter, and can say N here.
17480 Kernel automounter version 4 support (also supports v3)
17482 The automounter is a tool to automatically mount remote file systems
17483 on demand. This implementation is partially kernel-based to reduce
17484 overhead in the already-mounted case; this is unlike the BSD
17485 automounter (amd), which is a pure user space daemon.
17487 To use the automounter you need the user-space tools from
17488 <ftp://ftp.kernel.org/pub/linux/daemons/autofs/v4/>; you also
17489 want to answer Y to "NFS file system support", below.
17491 If you want to compile this as a module ( = code which can be
17492 inserted in and removed from the running kernel whenever you want),
17493 say M here and read <file:Documentation/modules.txt>. The module
17494 will be called autofs4.o. You will need to add "alias autofs
17495 autofs4" to your modules configuration file.
17497 If you are not a part of a fairly large, distributed network or
17498 don't have a laptop which needs to dynamically reconfigure to the
17499 local network, you probably do not need an automounter, and can say
17502 EFS file system support (read-only)
17504 EFS is an older file system used for non-ISO9660 CD-ROMs and hard
17505 disk partitions by SGI's IRIX operating system (IRIX 6.0 and newer
17506 uses the XFS file system for hard disk partitions however).
17508 This implementation only offers read-only access. If you don't know
17509 what all this is about, it's safe to say N. For more information
17510 about EFS see its home page at <http://aeschi.ch.eu.org/efs/>.
17512 If you want to compile the EFS file system support as a module ( =
17513 code which can be inserted in and removed from the running kernel
17514 whenever you want), say M here and read
17515 <file:Documentation/modules.txt>. The module will be called efs.o.
17517 Journalling Flash File System (JFFS) support
17519 JFFS is the Journalling Flash File System developed by Axis
17520 Communications in Sweden, aimed at providing a crash/powerdown-safe
17521 file system for disk-less embedded devices. Further information is
17522 available at (<http://developer.axis.com/software/jffs/>).
17524 JFFS debugging verbosity (0 = quiet, 3 = noisy)
17525 CONFIG_JFFS_FS_VERBOSE
17526 Determines the verbosity level of the JFFS debugging messages.
17528 Journalling Flash File System v2 (JFFS2) support
17530 JFFS2 is the second generation of the Journalling Flash File System
17531 for use on diskless embedded devices. It provides improved wear
17532 levelling, compression and support for hard links. You cannot use
17533 this on normal block devices, only on 'MTD' devices.
17535 Further information should be made available soon at
17536 <http://sources.redhat.com/jffs2/>.
17538 JFFS2 debugging verbosity (0 = quiet, 2 = noisy)
17539 CONFIG_JFFS2_FS_DEBUG
17540 This controls the amount of debugging messages produced by the JFFS2
17541 code. Set it to zero for use in production systems. For evaluation,
17542 testing and debugging, it's advisable to set it to one. This will
17543 enable a few assertions and will print debugging messages at the
17544 KERN_DEBUG loglevel, where they won't normally be visible. Level 2
17545 is unlikely to be useful - it enables extra debugging in certain
17546 areas which at one point needed debugging, but when the bugs were
17547 located and fixed, the detailed messages were relegated to level 2.
17549 If reporting bugs, please try to have available a full dump of the
17550 messages at debug level 1 while the misbehaviour was occurring.
17552 JFFS stats available in /proc filesystem
17553 CONFIG_JFFS_PROC_FS
17554 Enabling this option will cause statistics from mounted JFFS file systems
17555 to be made available to the user in the /proc/fs/jffs/ directory.
17557 UFS file system support (read-only)
17559 BSD and derivate versions of Unix (such as SunOS, FreeBSD, NetBSD,
17560 OpenBSD and NeXTstep) use a file system called UFS. Some System V
17561 Unixes can create and mount hard disk partitions and diskettes using
17562 this file system as well. Saying Y here will allow you to read from
17563 these partitions; if you also want to write to them, say Y to the
17564 experimental "UFS file system write support", below. Please read the
17565 file <file:Documentation/filesystems/ufs.txt> for more information.
17567 If you only intend to mount files from some other Unix over the
17568 network using NFS, you don't need the UFS file system support (but
17569 you need NFS file system support obviously).
17571 Note that this option is generally not needed for floppies, since a
17572 good portable way to transport files and directories between unixes
17573 (and even other operating systems) is given by the tar program ("man
17574 tar" or preferably "info tar").
17576 When accessing NeXTstep files, you may need to convert them from the
17577 NeXT character set to the Latin1 character set; use the program
17578 recode ("info recode") for this purpose.
17580 If you want to compile the UFS file system support as a module ( =
17581 code which can be inserted in and removed from the running kernel
17582 whenever you want), say M here and read
17583 <file:Documentation/modules.txt>. The module will be called ufs.o.
17585 If you haven't heard about all of this before, it's safe to say N.
17587 UFS file system write support (DANGEROUS)
17588 CONFIG_UFS_FS_WRITE
17589 Say Y here if you want to try writing to UFS partitions. This is
17590 experimental, so you should back up your UFS partitions beforehand.
17592 XFS filesystem support
17594 XFS is a high performance journaling filesystem which originated
17595 on the SGI IRIX platform. It is completely multi-threaded, can
17596 support large files and large filesystems, extended attributes,
17597 variable block sizes, is extent based, and makes extensive use of
17598 Btrees (directories, extents, free space) to aid both performance
17601 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
17602 for complete details. This implementation is on-disk compatible
17603 with the IRIX version of XFS.
17605 If you want to compile this file system as a module ( = code which
17606 can be inserted in and removed from the running kernel whenever you
17607 want), say M here and read <file:Documentation/modules.txt>. The
17608 module will be called xfs.o. Be aware, however, that if the file
17609 system of your root partition is compiled as a module, you'll need
17610 to use an initial ramdisk (initrd) to boot.
17614 If you say Y here, you will be able to set limits for disk usage on
17615 a per user and/or per group basis under XFS. XFS considers quota
17616 information as filesystem metadata and uses journaling to provide a
17617 higher level guarantee of consistency. The on-disk data format for
17618 quota is also compatible with the IRIX version of XFS, allowing a
17619 filesystem to be migrated between Linux and IRIX without any need
17622 If unsure, say N. More comprehensive documentation can be found in
17623 README.quota in the xfsprogs package. XFS quota can be used either
17624 with or without the generic quota support enabled (CONFIG_QUOTA) -
17625 they are completely independent subsystems.
17627 Realtime support (EXPERIMENTAL)
17629 If you say Y here you will be able to mount and use XFS filesystems
17630 which contain a realtime subvolume. The realtime subvolume is a
17631 separate area of disk space where only file data is stored. The
17632 realtime subvolume is designed to provide very deterministic
17633 data rates suitable for media streaming applications.
17635 See the xfs man page in section 5 for a bit more information.
17637 This feature is unsupported at this time, is not yet fully
17638 functional, and may cause serious problems.
17642 Tracing support (EXPERIMENTAL)
17644 Say Y here to get an XFS build with activity tracing enabled.
17645 Enabling this option will attach historical information to XFS
17646 inodes, buffers, certain locks, the log, the IO path, and a
17647 few other key areas within XFS. These traces can be examined
17648 using a kernel debugger.
17650 Say N unless you are an XFS developer.
17652 Debugging support (EXPERIMENTAL)
17654 Say Y here to get an XFS build with many debugging features,
17655 including ASSERT checks, function wrappers around macros,
17656 and extra sanity-checking functions in various code paths.
17658 Note that the resulting code will be HUGE and SLOW, and probably
17659 not useful unless you are debugging a particular problem.
17661 Say N unless you are an XFS developer, or play one on TV.
17663 Advanced partition selection
17664 CONFIG_PARTITION_ADVANCED
17665 Say Y here if you would like to use hard disks under Linux which
17666 were partitioned under an operating system running on a different
17667 architecture than your Linux system.
17669 Note that the answer to this question won't directly affect the
17670 kernel: saying N will just cause the configurator to skip all
17671 the questions about foreign partitioning schemes.
17675 Acorn partition support
17676 CONFIG_ACORN_PARTITION
17677 Support hard disks partitioned under Acorn operating systems.
17679 Native filecore partition support
17680 CONFIG_ACORN_PARTITION_ADFS
17681 The Acorn Disc Filing System is the standard file system of the
17682 RiscOS operating system which runs on Acorn's ARM-based Risc PC
17683 systems and the Acorn Archimedes range of machines. If you say
17684 `Y' here, Linux will support disk partitions created under ADFS.
17686 PowerTec partition support
17687 CONFIG_ACORN_PARTITION_POWERTEC
17688 Support reading partition tables created on Acorn machines using
17689 the PowerTec SCSI drive.
17691 RISCiX partition support
17692 CONFIG_ACORN_PARTITION_RISCIX
17693 Once upon a time, there was a native Unix port for the Acorn series
17694 of machines called RISCiX. If you say 'Y' here, Linux will be able
17695 to read disks partitioned under RISCiX.
17697 ICS partition support
17698 CONFIG_ACORN_PARTITION_ICS
17699 Say Y here if you would like to use hard disks under Linux which
17700 were partitioned using the ICS interface on Acorn machines.
17702 Alpha OSF partition support
17703 CONFIG_OSF_PARTITION
17704 Say Y here if you would like to use hard disks under Linux which
17705 were partitioned on an Alpha machine.
17707 Macintosh partition map support
17708 CONFIG_MAC_PARTITION
17709 Say Y here if you would like to use hard disks under Linux which
17710 were partitioned on a Macintosh.
17712 Windows Logical Disk Manager (Dynamic Disk) support (EXPERIMENTAL)
17713 CONFIG_LDM_PARTITION
17714 Say Y here if you would like to use hard disks under Linux which
17715 were partitioned using Windows 2000's or XP's Logical Disk Manager.
17716 They are also known as "Dynamic Disks".
17718 Windows 2000 introduced the concept of Dynamic Disks to get around
17719 the limitations of the PC's partitioning scheme. The Logical Disk
17720 Manager allows the user to repartition a disk and create spanned,
17721 mirrored, striped or RAID volumes, all without the need for
17724 Normal partitions are now called Basic Disks under Windows 2000 and
17727 Technical documentation to accompany this driver is available from:
17728 <http://linux-ntfs.sf.net/ldm/>.
17732 Windows LDM extra logging
17734 Say Y here if you would like LDM to log verbosely. This could be
17735 helpful if the driver doesn't work as expected and you'd like to
17740 PC BIOS (MSDOS partition tables) support
17741 CONFIG_MSDOS_PARTITION
17742 Say Y here if you would like to use hard disks under Linux which
17743 were partitioned on an x86 PC (not necessarily by DOS).
17745 Amiga partition table support
17746 CONFIG_AMIGA_PARTITION
17747 Say Y here if you would like to use hard disks under Linux which
17748 were partitioned under AmigaOS.
17750 Atari partition table support
17751 CONFIG_ATARI_PARTITION
17752 Say Y here if you would like to use hard disks under Linux which
17753 were partitioned under the Atari OS.
17755 BSD disklabel (FreeBSD partition tables) support
17756 CONFIG_BSD_DISKLABEL
17757 FreeBSD uses its own hard disk partition scheme on your PC. It
17758 requires only one entry in the primary partition table of your disk
17759 and manages it similarly to DOS extended partitions, putting in its
17760 first sector a new partition table in BSD disklabel format. Saying Y
17761 here allows you to read these disklabels and further mount FreeBSD
17762 partitions from within Linux if you have also said Y to "UFS
17763 file system support", above. If you don't know what all this is
17766 Minix subpartition support
17767 CONFIG_MINIX_SUBPARTITION
17768 Minix 2.0.0/2.0.2 subpartition table support for Linux.
17769 Say Y here if you want to mount and use Minix 2.0.0/2.0.2
17772 Sun partition table support
17773 CONFIG_SUN_PARTITION
17774 Like most systems, SunOS uses its own hard disk partition table
17775 format, incompatible with all others. Saying Y here allows you to
17776 read these partition tables and further mount SunOS partitions from
17777 within Linux if you have also said Y to "UFS file system support",
17778 above. This is mainly used to carry data from a SPARC under SunOS to
17779 your Linux box via a removable medium like magneto-optical or ZIP
17780 drives; note however that a good portable way to transport files and
17781 directories between unixes (and even other operating systems) is
17782 given by the tar program ("man tar" or preferably "info tar"). If
17783 you don't know what all this is about, say N.
17785 Solaris (x86) partition table support
17786 CONFIG_SOLARIS_X86_PARTITION
17787 Like most systems, Solaris x86 uses its own hard disk partition
17788 table format, incompatible with all others. Saying Y here allows you
17789 to read these partition tables and further mount Solaris x86
17790 partitions from within Linux if you have also said Y to "UFS
17791 file system support", above.
17793 SGI partition support
17794 CONFIG_SGI_PARTITION
17795 Say Y here if you would like to be able to read the hard disk
17796 partition table format used by SGI machines.
17798 Intel EFI GUID partition support
17799 CONFIG_EFI_PARTITION
17800 Say Y here if you would like to use hard disks under Linux which
17801 were partitioned using EFI GPT. Presently only useful on the
17804 Ultrix partition table support
17805 CONFIG_ULTRIX_PARTITION
17806 Say Y here if you would like to be able to read the hard disk
17807 partition table format used by DEC (now Compaq) Ultrix machines.
17810 IBM disk label and partition support
17811 CONFIG_IBM_PARTITION
17812 You have to say Y here if you would like to be able to read volume
17813 labels of IBM DASD disks. These can be ECKD DASD disks with
17814 compatible disk layout (cdl) and standard Linux disk layout (ldl),
17815 FBA DASD disks and CMS reserved minidisks.
17816 Otherwise, say N and you will not be able to access these disks.
17818 ADFS file system support
17820 The Acorn Disc Filing System is the standard file system of the
17821 RiscOS operating system which runs on Acorn's ARM-based Risc PC
17822 systems and the Acorn Archimedes range of machines. If you say Y
17823 here, Linux will be able to read from ADFS partitions on hard drives
17824 and from ADFS-formatted floppy discs. If you also want to be able to
17825 write to those devices, say Y to "ADFS write support" below.
17827 The ADFS partition should be the first partition (i.e.,
17828 /dev/[hs]d?1) on each of your drives. Please read the file
17829 <file:Documentation/filesystems/adfs.txt> for further details.
17831 This code is also available as a module called adfs.o ( = code which
17832 can be inserted in and removed from the running kernel whenever you
17833 want). If you want to compile it as a module, say M here and read
17834 <file:Documentation/modules.txt>.
17838 ADFS write support (DANGEROUS)
17840 If you say Y here, you will be able to write to ADFS partitions on
17841 hard drives and ADFS-formatted floppy disks. This is experimental
17842 codes, so if you're unsure, say N.
17844 JFS filesystem support
17846 This is a port of IBM's Journalling Filesystem . More information is
17847 available in the file Documentation/filesystems/jfs.txt.
17849 If you do not intend to use the JFS filesystem, say N.
17853 If you are experiencing any problems with the JFS filesystem, say
17854 Y here. This will result in additional debugging messages to be
17855 written to the system log. Under normal circumstances, this
17856 results in very little overhead.
17859 CONFIG_JFS_STATISTICS
17860 Enabling this option will cause statistics from the JFS file system
17861 to be made available to the user in the /proc/fs/jfs/ directory.
17863 /dev/pts file system for Unix98 PTYs
17865 You should say Y here if you said Y to "Unix98 PTY support" above.
17866 You'll then get a virtual file system which can be mounted on
17867 /dev/pts with "mount -t devpts". This, together with the pseudo
17868 terminal master multiplexer /dev/ptmx, is used for pseudo terminal
17869 support as described in The Open Group's Unix98 standard: in order
17870 to acquire a pseudo terminal, a process opens /dev/ptmx; the number
17871 of the pseudo terminal is then made available to the process and the
17872 pseudo terminal slave can be accessed as /dev/pts/<number>. What was
17873 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
17875 The GNU C library glibc 2.1 contains the requisite support for this
17876 mode of operation; you also need client programs that use the Unix98
17877 API. Please read <file:Documentation/Changes> for more information
17878 about the Unix98 pty devices.
17880 Note that the experimental "/dev file system support"
17881 (CONFIG_DEVFS_FS) is a more general facility.
17883 FreeVxFS file system support (VERITAS VxFS(TM) compatible)
17885 FreeVxFS is a file system driver that support the VERITAS VxFS(TM)
17886 file system format. VERITAS VxFS(TM) is the standard file system
17887 of SCO UnixWare (and possibly others) and optionally available
17888 for Sunsoft Solaris, HP-UX and many other operating systems.
17889 Currently only readonly access is supported.
17891 NOTE: the file system type as used by mount(1), mount(2) and
17892 fstab(5) is 'vxfs' as it describes the file system format, not
17895 This file system is also available as a module ( = code which can be
17896 inserted in and removed from the running kernel whenever you want).
17897 The module is called freevxfs.o. If you want to compile it as a
17898 module, say M here and read <file:Documentation/modules.txt>. If
17901 UnixWare slices support
17902 CONFIG_UNIXWARE_DISKLABEL
17903 Like some systems, UnixWare uses its own slice table inside a
17904 partition (VTOC - Virtual Table of Contents). Its format is
17905 incompatible with all other OSes. Saying Y here allows you to read
17906 VTOC and further mount UnixWare partitions read-only from within
17907 Linux if you have also said Y to "UFS file system support" or
17908 "System V and Coherent file system support", above.
17910 This is mainly used to carry data from a UnixWare box to your
17911 Linux box via a removable medium like magneto-optical, ZIP or
17912 removable IDE drives. Note, however, that a good portable way to
17913 transport files and directories between unixes (and even other
17914 operating systems) is given by the tar program ("man tar" or
17915 preferably "info tar").
17917 If you don't know what all this is about, say N.
17919 SMB file system support (to mount Windows shares etc.)
17921 SMB (Server Message Block) is the protocol Windows for Workgroups
17922 (WfW), Windows 95/98, Windows NT and OS/2 Lan Manager use to share
17923 files and printers over local networks. Saying Y here allows you to
17924 mount their file systems (often called "shares" in this context) and
17925 access them just like any other Unix directory. Currently, this
17926 works only if the Windows machines use TCP/IP as the underlying
17927 transport protocol, and not NetBEUI. For details, read
17928 <file:Documentation/filesystems/smbfs.txt> and the SMB-HOWTO,
17929 available from <http://www.tldp.org/docs.html#howto>.
17931 Note: if you just want your box to act as an SMB *server* and make
17932 files and printing services available to Windows clients (which need
17933 to have a TCP/IP stack), you don't need to say Y here; you can use
17934 the program SAMBA (available from <ftp://ftp.samba.org/pub/samba/>)
17937 General information about how to connect Linux, Windows machines and
17938 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
17940 If you want to compile the SMB support as a module ( = code which
17941 can be inserted in and removed from the running kernel whenever you
17942 want), say M here and read <file:Documentation/modules.txt>. The
17943 module will be called smbfs.o. Most people say N, however.
17946 CONFIG_SMB_NLS_DEFAULT
17947 Enabling this will make smbfs use nls translations by default. You
17948 need to specify the local charset (CONFIG_NLS_DEFAULT) in the nls
17949 settings and you need to give the default nls for the SMB server as
17950 CONFIG_SMB_NLS_REMOTE.
17952 The nls settings can be changed at mount time, if your smbmount
17953 supports that, using the codepage and iocharset parameters.
17955 smbmount from samba 2.2.0 or later supports this.
17957 Default Remote NLS Option
17958 CONFIG_SMB_NLS_REMOTE
17959 This setting allows you to specify a default value for which
17960 codepage the server uses. If this field is left blank no
17961 translations will be done by default. The local codepage/charset
17962 default to CONFIG_NLS_DEFAULT.
17964 The nls settings can be changed at mount time, if your smbmount
17965 supports that, using the codepage and iocharset parameters.
17967 smbmount from samba 2.2.0 or later supports this.
17969 Enable Unix Extensions
17971 Enabling this will make smbfs use the CIFS Unix Extensions if
17972 supported by the server. These extensions allows use of unix user
17973 ids, permissions, file modes, symlinks, etc that normally do not
17976 Samba 3.0 servers supports these extensions.
17978 If you don't know what all this is about, it is safe to say Y.
17980 Coda file system support (advanced network fs)
17982 Coda is an advanced network file system, similar to NFS in that it
17983 enables you to mount file systems of a remote server and access them
17984 with regular Unix commands as if they were sitting on your hard
17985 disk. Coda has several advantages over NFS: support for
17986 disconnected operation (e.g. for laptops), read/write server
17987 replication, security model for authentication and encryption,
17988 persistent client caches and write back caching.
17990 If you say Y here, your Linux box will be able to act as a Coda
17991 *client*. You will need user level code as well, both for the
17992 client and server. Servers are currently user level, i.e. they need
17993 no kernel support. Please read
17994 <file:Documentation/filesystems/coda.txt> and check out the Coda
17995 home page <http://www.coda.cs.cmu.edu/>.
17997 If you want to compile the coda client support as a module ( = code
17998 which can be inserted in and removed from the running kernel
17999 whenever you want), say M here and read
18000 <file:Documentation/modules.txt>. The module will be called coda.o.
18002 InterMezzo file system support (replicating fs)
18003 CONFIG_INTERMEZZO_FS
18004 InterMezzo is a networked file system with disconnected operation
18005 and kernel level write back caching. It is most often used for
18006 replicating potentially large trees or keeping laptop/desktop copies
18009 If you say Y or M your kernel or module will provide InterMezzo
18010 support. You will also need a file server daemon, which you can get
18011 from <http://www.inter-mezzo.org/>.
18013 NCP file system support (to mount NetWare volumes)
18015 NCP (NetWare Core Protocol) is a protocol that runs over IPX and is
18016 used by Novell NetWare clients to talk to file servers. It is to
18017 IPX what NFS is to TCP/IP, if that helps. Saying Y here allows you
18018 to mount NetWare file server volumes and to access them just like
18019 any other Unix directory. For details, please read the file
18020 <file:Documentation/filesystems/ncpfs.txt> in the kernel source and
18021 the IPX-HOWTO from <http://www.tldp.org/docs.html#howto>.
18023 You do not have to say Y here if you want your Linux box to act as a
18024 file *server* for Novell NetWare clients.
18026 General information about how to connect Linux, Windows machines and
18027 Macs is on the WWW at <http://www.eats.com/linux_mac_win.html>.
18029 If you want to compile this as a module ( = code which can be
18030 inserted in and removed from the running kernel whenever you want),
18031 say M here and read <file:Documentation/modules.txt>. The module
18032 will be called ncpfs.o. Say N unless you are connected to a Novell
18036 CONFIG_NCPFS_PACKET_SIGNING
18037 NCP allows packets to be signed for stronger security. If you want
18038 security, say Y. Normal users can leave it off. To be able to use
18039 packet signing you must use ncpfs > 2.0.12.
18041 Proprietary file locking
18042 CONFIG_NCPFS_IOCTL_LOCKING
18043 Allows locking of records on remote volumes. Say N unless you have
18044 special applications which are able to utilize this locking scheme.
18046 Clear remove/delete inhibit when needed
18047 CONFIG_NCPFS_STRONG
18048 Allows manipulation of files flagged as Delete or Rename Inhibit.
18049 To use this feature you must mount volumes with the ncpmount
18050 parameter "-s" (ncpfs-2.0.12 and newer). Say Y unless you are not
18051 mounting volumes with -f 444.
18053 Use NFS namespace if available
18054 CONFIG_NCPFS_NFS_NS
18055 Allows you to utilize NFS namespace on NetWare servers. It brings
18056 you case sensitive filenames. Say Y. You can disable it at
18057 mount-time with the `-N nfs' parameter of ncpmount.
18059 Use LONG (OS/2) namespace if available
18060 CONFIG_NCPFS_OS2_NS
18061 Allows you to utilize OS2/LONG namespace on NetWare servers.
18062 Filenames in this namespace are limited to 255 characters, they are
18063 case insensitive, and case in names is preserved. Say Y. You can
18064 disable it at mount time with the -N os2 parameter of ncpmount.
18066 Lowercase DOS filenames on LONG namespace volume
18067 CONFIG_NCPFS_SMALLDOS
18068 If you say Y here, every filename on a NetWare server volume using
18069 the OS2/LONG namespace and created under DOS or on a volume using
18070 DOS namespace will be converted to lowercase characters.
18071 Saying N here will give you these filenames in uppercase.
18073 This is only a cosmetic option since the OS2/LONG namespace is case
18074 insensitive. The only major reason for this option is backward
18075 compatibility when moving from DOS to OS2/LONG namespace support.
18076 Long filenames (created by Win95) will not be affected.
18078 This option does not solve the problem that filenames appear
18079 differently under Linux and under Windows, since Windows does an
18080 additional conversions on the client side. You can achieve similar
18081 effects by saying Y to "Allow using of Native Language Support"
18084 Use Native Language Support
18086 Allows you to use codepages and I/O charsets for file name
18087 translation between the server file system and input/output. This
18088 may be useful, if you want to access the server with other operating
18089 systems, e.g. Windows 95. See also NLS for more Information.
18091 To select codepages and I/O charsets use ncpfs-2.2.0.13 or newer.
18093 Symbolic links and mode permission bits
18094 CONFIG_NCPFS_EXTRAS
18095 This enables the use of symbolic links and an execute permission
18096 bit on NCPFS. The file server need not have long name space or NFS
18097 name space loaded for these to work.
18099 To use the new attributes, it is recommended to use the flags
18100 '-f 600 -d 755' on the ncpmount command line.
18104 The default NLS used when mounting file system. Note, that this is
18105 the NLS used by your console, not the NLS used by a specific file
18106 system (if different) to store data (filenames) on a disk.
18107 Currently, the valid values are:
18108 big5, cp437, cp737, cp775, cp850, cp852, cp855, cp857, cp860, cp861,
18109 cp862, cp863, cp864, cp865, cp866, cp869, cp874, cp932, cp936,
18110 cp949, cp950, cp1250, cp1251, cp1255, euc-jp, euc-kr, gb2312, iso8859-1,
18111 iso8859-2, iso8859-3, iso8859-4, iso8859-5, iso8859-6, iso8859-7,
18112 iso8859-8, iso8859-9, iso8859-13, iso8859-14, iso8859-15,
18113 koi8-r, koi8-ru, koi8-u, sjis, tis-620, utf8.
18114 If you specify a wrong value, it will use the built-in NLS;
18115 compatible with iso8859-1.
18117 If unsure, specify it as "iso8859-1".
18119 Codepage 437 (United States, Canada)
18120 CONFIG_NLS_CODEPAGE_437
18121 The Microsoft FAT file system family can deal with filenames in
18122 native language character sets. These character sets are stored
18123 in so-called DOS codepages. You need to include the appropriate
18124 codepage if you want to be able to read/write these filenames on
18125 DOS/Windows partitions correctly. This does apply to the filenames
18126 only, not to the file contents. You can include several codepages;
18127 say Y here if you want to include the DOS codepage that is used in
18128 the United States and parts of Canada. This is recommended.
18130 Codepage 737 (Greek)
18131 CONFIG_NLS_CODEPAGE_737
18132 The Microsoft FAT file system family can deal with filenames in
18133 native language character sets. These character sets are stored
18134 in so-called DOS codepages. You need to include the appropriate
18135 codepage if you want to be able to read/write these filenames on
18136 DOS/Windows partitions correctly. This does apply to the filenames
18137 only, not to the file contents. You can include several codepages;
18138 say Y here if you want to include the DOS codepage that is used for
18139 Greek. If unsure, say N.
18141 Codepage 775 (Baltic Rim)
18142 CONFIG_NLS_CODEPAGE_775
18143 The Microsoft FAT file system family can deal with filenames in
18144 native language character sets. These character sets are stored
18145 in so-called DOS codepages. You need to include the appropriate
18146 codepage if you want to be able to read/write these filenames on
18147 DOS/Windows partitions correctly. This does apply to the filenames
18148 only, not to the file contents. You can include several codepages;
18149 say Y here if you want to include the DOS codepage that is used
18150 for the Baltic Rim Languages (Latvian and Lithuanian). If unsure,
18153 Codepage 850 (Europe)
18154 CONFIG_NLS_CODEPAGE_850
18155 The Microsoft FAT file system family can deal with filenames in
18156 native language character sets. These character sets are stored in
18157 so-called DOS codepages. You need to include the appropriate
18158 codepage if you want to be able to read/write these filenames on
18159 DOS/Windows partitions correctly. This does apply to the filenames
18160 only, not to the file contents. You can include several codepages;
18161 say Y here if you want to include the DOS codepage that is used for
18162 much of Europe -- United Kingdom, Germany, Spain, Italy, and [add
18163 more countries here]. It has some characters useful to many European
18164 languages that are not part of the US codepage 437.
18168 Codepage 852 (Central/Eastern Europe)
18169 CONFIG_NLS_CODEPAGE_852
18170 The Microsoft FAT file system family can deal with filenames in
18171 native language character sets. These character sets are stored in
18172 so-called DOS codepages. You need to include the appropriate
18173 codepage if you want to be able to read/write these filenames on
18174 DOS/Windows partitions correctly. This does apply to the filenames
18175 only, not to the file contents. You can include several codepages;
18176 say Y here if you want to include the Latin 2 codepage used by DOS
18177 for much of Central and Eastern Europe. It has all the required
18178 characters for these languages: Albanian, Croatian, Czech, English,
18179 Finnish, Hungarian, Irish, German, Polish, Rumanian, Serbian (Latin
18180 transcription), Slovak, Slovenian, and Serbian.
18182 Codepage 855 (Cyrillic)
18183 CONFIG_NLS_CODEPAGE_855
18184 The Microsoft FAT file system family can deal with filenames in
18185 native language character sets. These character sets are stored in
18186 so-called DOS codepages. You need to include the appropriate
18187 codepage if you want to be able to read/write these filenames on
18188 DOS/Windows partitions correctly. This does apply to the filenames
18189 only, not to the file contents. You can include several codepages;
18190 say Y here if you want to include the DOS codepage for Cyrillic.
18192 Codepage 857 (Turkish)
18193 CONFIG_NLS_CODEPAGE_857
18194 The Microsoft FAT file system family can deal with filenames in
18195 native language character sets. These character sets are stored in
18196 so-called DOS codepages. You need to include the appropriate
18197 codepage if you want to be able to read/write these filenames on
18198 DOS/Windows partitions correctly. This does apply to the filenames
18199 only, not to the file contents. You can include several codepages;
18200 say Y here if you want to include the DOS codepage for Turkish.
18202 Codepage 860 (Portuguese)
18203 CONFIG_NLS_CODEPAGE_860
18204 The Microsoft FAT file system family can deal with filenames in
18205 native language character sets. These character sets are stored in
18206 so-called DOS codepages. You need to include the appropriate
18207 codepage if you want to be able to read/write these filenames on
18208 DOS/Windows partitions correctly. This does apply to the filenames
18209 only, not to the file contents. You can include several codepages;
18210 say Y here if you want to include the DOS codepage for Portuguese.
18212 Codepage 861 (Icelandic)
18213 CONFIG_NLS_CODEPAGE_861
18214 The Microsoft FAT file system family can deal with filenames in
18215 native language character sets. These character sets are stored in
18216 so-called DOS codepages. You need to include the appropriate
18217 codepage if you want to be able to read/write these filenames on
18218 DOS/Windows partitions correctly. This does apply to the filenames
18219 only, not to the file contents. You can include several codepages;
18220 say Y here if you want to include the DOS codepage for Icelandic.
18222 Codepage 862 (Hebrew)
18223 CONFIG_NLS_CODEPAGE_862
18224 The Microsoft FAT file system family can deal with filenames in
18225 native language character sets. These character sets are stored in
18226 so-called DOS codepages. You need to include the appropriate
18227 codepage if you want to be able to read/write these filenames on
18228 DOS/Windows partitions correctly. This does apply to the filenames
18229 only, not to the file contents. You can include several codepages;
18230 say Y here if you want to include the DOS codepage for Hebrew.
18232 Codepage 863 (Canadian French)
18233 CONFIG_NLS_CODEPAGE_863
18234 The Microsoft FAT file system family can deal with filenames in
18235 native language character sets. These character sets are stored in
18236 so-called DOS codepages. You need to include the appropriate
18237 codepage if you want to be able to read/write these filenames on
18238 DOS/Windows partitions correctly. This does apply to the filenames
18239 only, not to the file contents. You can include several codepages;
18240 say Y here if you want to include the DOS codepage for Canadian
18243 Codepage 864 (Arabic)
18244 CONFIG_NLS_CODEPAGE_864
18245 The Microsoft FAT file system family can deal with filenames in
18246 native language character sets. These character sets are stored in
18247 so-called DOS codepages. You need to include the appropriate
18248 codepage if you want to be able to read/write these filenames on
18249 DOS/Windows partitions correctly. This does apply to the filenames
18250 only, not to the file contents. You can include several codepages;
18251 say Y here if you want to include the DOS codepage for Arabic.
18253 Codepage 865 (Norwegian, Danish)
18254 CONFIG_NLS_CODEPAGE_865
18255 The Microsoft FAT file system family can deal with filenames in
18256 native language character sets. These character sets are stored in
18257 so-called DOS codepages. You need to include the appropriate
18258 codepage if you want to be able to read/write these filenames on
18259 DOS/Windows partitions correctly. This does apply to the filenames
18260 only, not to the file contents. You can include several codepages;
18261 say Y here if you want to include the DOS codepage for the Nordic
18262 European countries.
18264 Codepage 866 (Cyrillic/Russian)
18265 CONFIG_NLS_CODEPAGE_866
18266 The Microsoft FAT file system family can deal with filenames in
18267 native language character sets. These character sets are stored in
18268 so-called DOS codepages. You need to include the appropriate
18269 codepage if you want to be able to read/write these filenames on
18270 DOS/Windows partitions correctly. This does apply to the filenames
18271 only, not to the file contents. You can include several codepages;
18272 say Y here if you want to include the DOS codepage for
18275 Codepage 869 (Greek)
18276 CONFIG_NLS_CODEPAGE_869
18277 The Microsoft FAT file system family can deal with filenames in
18278 native language character sets. These character sets are stored in
18279 so-called DOS codepages. You need to include the appropriate
18280 codepage if you want to be able to read/write these filenames on
18281 DOS/Windows partitions correctly. This does apply to the filenames
18282 only, not to the file contents. You can include several codepages;
18283 say Y here if you want to include the DOS codepage for Greek.
18285 Thai charset (CP874, TIS-620)
18286 CONFIG_NLS_CODEPAGE_874
18287 The Microsoft FAT file system family can deal with filenames in
18288 native language character sets. These character sets are stored in
18289 so-called DOS codepages. You need to include the appropriate
18290 codepage if you want to be able to read/write these filenames on
18291 DOS/Windows partitions correctly. This does apply to the filenames
18292 only, not to the file contents. You can include several codepages;
18293 say Y here if you want to include the DOS codepage for Thai.
18295 Windows CP1251 (Bulgarian, Belarusian)
18296 CONFIG_NLS_CODEPAGE_1251
18297 The Microsoft FAT file system family can deal with filenames in
18298 native language character sets. These character sets are stored in
18299 so-called DOS codepages. You need to include the appropriate
18300 codepage if you want to be able to read/write these filenames on
18301 DOS/Windows partitions correctly. This does apply to the filenames
18302 only, not to the file contents. You can include several codepages;
18303 say Y here if you want to include the DOS codepage for Russian and
18304 Bulgarian and Belarusian.
18306 Japanese charsets (Shift-JIS, EUC-JP)
18307 CONFIG_NLS_CODEPAGE_932
18308 The Microsoft FAT file system family can deal with filenames in
18309 native language character sets. These character sets are stored in
18310 so-called DOS codepages. You need to include the appropriate
18311 codepage if you want to be able to read/write these filenames on
18312 DOS/Windows partitions correctly. This does apply to the filenames
18313 only, not to the file contents. You can include several codepages;
18314 say Y here if you want to include the DOS codepage for Shift-JIS
18315 or EUC-JP. To use EUC-JP, you can use 'euc-jp' as mount option or
18316 NLS Default value during kernel configuration, instead of 'cp932'.
18318 Simplified Chinese charset (CP936, GB2312)
18319 CONFIG_NLS_CODEPAGE_936
18320 The Microsoft FAT file system family can deal with filenames in
18321 native language character sets. These character sets are stored in
18322 so-called DOS codepages. You need to include the appropriate
18323 codepage if you want to be able to read/write these filenames on
18324 DOS/Windows partitions correctly. This does apply to the filenames
18325 only, not to the file contents. You can include several codepages;
18326 say Y here if you want to include the DOS codepage for Simplified
18329 Korean charset (CP949, EUC-KR)
18330 CONFIG_NLS_CODEPAGE_949
18331 The Microsoft FAT file system family can deal with filenames in
18332 native language character sets. These character sets are stored in
18333 so-called DOS codepages. You need to include the appropriate
18334 codepage if you want to be able to read/write these filenames on
18335 DOS/Windows partitions correctly. This does apply to the filenames
18336 only, not to the file contents. You can include several codepages;
18337 say Y here if you want to include the DOS codepage for UHC.
18339 Traditional Chinese charset (Big5)
18340 CONFIG_NLS_CODEPAGE_950
18341 The Microsoft FAT file system family can deal with filenames in
18342 native language character sets. These character sets are stored in
18343 so-called DOS codepages. You need to include the appropriate
18344 codepage if you want to be able to read/write these filenames on
18345 DOS/Windows partitions correctly. This does apply to the filenames
18346 only, not to the file contents. You can include several codepages;
18347 say Y here if you want to include the DOS codepage for Traditional
18350 Central European (Codepage 1250)
18351 CONFIG_NLS_CODEPAGE_1250
18352 If you want to display filenames with native language characters
18353 from the Microsoft FAT file system family or from JOLIET CDROMs
18354 correctly on the screen, you need to include the appropriate
18355 input/output character sets. Say Y here for the Windows CP-1250
18356 character set, which works for most Latin-written Slavic and Central
18357 European languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
18360 NLS ISO 8859-1 (Latin 1; Western European Languages)
18361 CONFIG_NLS_ISO8859_1
18362 If you want to display filenames with native language characters
18363 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18364 correctly on the screen, you need to include the appropriate
18365 input/output character sets. Say Y here for the Latin 1 character
18366 set, which covers most West European languages such as Albanian,
18367 Catalan, Danish, Dutch, English, Faeroese, Finnish, French, German,
18368 Galician, Irish, Icelandic, Italian, Norwegian, Portuguese, Spanish,
18369 and Swedish. It is also the default for the US. If unsure, say Y.
18371 NLS ISO 8859-2 (Latin 2; Slavic/Central European Languages)
18372 CONFIG_NLS_ISO8859_2
18373 If you want to display filenames with native language characters
18374 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18375 correctly on the screen, you need to include the appropriate
18376 input/output character sets. Say Y here for the Latin 2 character
18377 set, which works for most Latin-written Slavic and Central European
18378 languages: Czech, German, Hungarian, Polish, Rumanian, Croatian,
18381 NLS ISO 8859-3 (Latin 3; Esperanto, Galician, Maltese, Turkish)
18382 CONFIG_NLS_ISO8859_3
18383 If you want to display filenames with native language characters
18384 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18385 correctly on the screen, you need to include the appropriate
18386 input/output character sets. Say Y here for the Latin 3 character
18387 set, which is popular with authors of Esperanto, Galician, Maltese,
18390 NLS ISO 8859-4 (Latin 4; old Baltic charset)
18391 CONFIG_NLS_ISO8859_4
18392 If you want to display filenames with native language characters
18393 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18394 correctly on the screen, you need to include the appropriate
18395 input/output character sets. Say Y here for the Latin 4 character
18396 set which introduces letters for Estonian, Latvian, and
18397 Lithuanian. It is an incomplete predecessor of Latin 7.
18399 NLS ISO 8859-5 (Cyrillic)
18400 CONFIG_NLS_ISO8859_5
18401 If you want to display filenames with native language characters
18402 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18403 correctly on the screen, you need to include the appropriate
18404 input/output character sets. Say Y here for ISO8859-5, a Cyrillic
18405 character set with which you can type Bulgarian, Belarusian,
18406 Macedonian, Russian, Serbian, and Ukrainian. Note that the charset
18407 KOI8-R is preferred in Russia.
18409 NLS ISO 8859-6 (Arabic)
18410 CONFIG_NLS_ISO8859_6
18411 If you want to display filenames with native language characters
18412 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18413 correctly on the screen, you need to include the appropriate
18414 input/output character sets. Say Y here for ISO8859-6, the Arabic
18417 NLS ISO 8859-7 (Modern Greek)
18418 CONFIG_NLS_ISO8859_7
18419 If you want to display filenames with native language characters
18420 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18421 correctly on the screen, you need to include the appropriate
18422 input/output character sets. Say Y here for ISO8859-7, the Modern
18423 Greek character set.
18425 Hebrew charsets (ISO-8859-8, CP1255)
18426 CONFIG_NLS_ISO8859_8
18427 If you want to display filenames with native language characters
18428 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18429 correctly on the screen, you need to include the appropriate
18430 input/output character sets. Say Y here for ISO8859-8, the Hebrew
18433 NLS ISO 8859-9 (Latin 5; Turkish)
18434 CONFIG_NLS_ISO8859_9
18435 If you want to display filenames with native language characters
18436 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18437 correctly on the screen, you need to include the appropriate
18438 input/output character sets. Say Y here for the Latin 5 character
18439 set, and it replaces the rarely needed Icelandic letters in Latin 1
18440 with the Turkish ones. Useful in Turkey.
18442 NLS ISO 8859-10 (Latin 6; Nordic)
18443 CONFIG_NLS_ISO8859_10
18444 If you want to display filenames with native language characters
18445 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18446 correctly on the screen, you need to include the appropriate
18447 input/output character sets. Say Y here for the Latin 6 character
18448 set, which adds the last Inuit (Greenlandic) and Sami (Lappish)
18449 letters that were missing in Latin 4 to cover the entire Nordic
18452 NLS ISO 8859-13 (Latin 7; Baltic)
18453 CONFIG_NLS_ISO8859_13
18454 If you want to display filenames with native language characters
18455 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18456 correctly on the screen, you need to include the appropriate
18457 input/output character sets. Say Y here for the Latin 7 character
18458 set, which supports modern Baltic languages including Latvian
18461 NLS ISO 8859-14 (Latin 8; Celtic)
18462 CONFIG_NLS_ISO8859_14
18463 If you want to display filenames with native language characters
18464 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18465 correctly on the screen, you need to include the appropriate
18466 input/output character sets. Say Y here for the Latin 8 character
18467 set, which adds the last accented vowels for Welsh (aka Cymraeg)
18468 (and Manx Gaelic) that were missing in Latin 1.
18469 <http://linux.speech.cymru.org/> has further information.
18471 NLS ISO 8859-15 (Latin 9; Western European languages with Euro)
18472 CONFIG_NLS_ISO8859_15
18473 If you want to display filenames with native language characters
18474 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18475 correctly on the screen, you need to include the appropriate
18476 input/output character sets. Say Y here for the Latin 9 character
18477 set, which covers most West European languages such as Albanian,
18478 Catalan, Danish, Dutch, English, Estonian, Faeroese, Finnish,
18479 French, German, Galician, Irish, Icelandic, Italian, Norwegian,
18480 Portuguese, Spanish, and Swedish. Latin 9 is an update to
18481 Latin 1 (ISO 8859-1) that removes a handful of rarely used
18482 characters and instead adds support for Estonian, corrects the
18483 support for French and Finnish, and adds the new Euro character.
18486 NLS KOI8-R (Russian)
18488 If you want to display filenames with native language characters
18489 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18490 correctly on the screen, you need to include the appropriate
18491 input/output character sets. Say Y here for the preferred Russian
18494 NLS KOI8-U/RU (Ukrainian, Belarusian)
18496 If you want to display filenames with native language characters
18497 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18498 correctly on the screen, you need to include the appropriate
18499 input/output character sets. Say Y here for the preferred Ukrainian
18500 (koi8-u) and Belarusian (koi8-ru) character sets.
18504 If you want to display filenames with native language characters
18505 from the Microsoft FAT file system family or from JOLIET CD-ROMs
18506 correctly on the screen, you need to include the appropriate
18507 input/output character sets. Say Y here for the UTF-8 encoding of
18508 the Unicode/ISO9646 universal character set.
18512 If you say Y here, you will get support for terminal devices with
18513 display and keyboard devices. These are called "virtual" because you
18514 can run several virtual terminals (also called virtual consoles) on
18515 one physical terminal. This is rather useful, for example one
18516 virtual terminal can collect system messages and warnings, another
18517 one can be used for a text-mode user session, and a third could run
18518 an X session, all in parallel. Switching between virtual terminals
18519 is done with certain key combinations, usually Alt-<function key>.
18521 The setterm command ("man setterm") can be used to change the
18522 properties (such as colors or beeping) of a virtual terminal. The
18523 man page console_codes(4) ("man console_codes") contains the special
18524 character sequences that can be used to change those properties
18525 directly. The fonts used on virtual terminals can be changed with
18526 the setfont ("man setfont") command and the key bindings are defined
18527 with the loadkeys ("man loadkeys") command.
18529 You need at least one virtual terminal device in order to make use
18530 of your keyboard and monitor. Therefore, only people configuring an
18531 embedded system would want to say N here in order to save some
18532 memory; the only way to log into such a system is then via a serial
18533 or network connection.
18535 If unsure, say Y, or else you won't be able to do much with your new
18536 shiny Linux system :-)
18538 Support for console on virtual terminal
18540 The system console is the device which receives all kernel messages
18541 and warnings and which allows logins in single user mode. If you
18542 answer Y here, a virtual terminal (the device used to interact with
18543 a physical terminal) can be used as system console. This is the most
18544 common mode of operations, so you should say Y here unless you want
18545 the kernel messages be output only to a serial port (in which case
18546 you should say Y to "Console on serial port", below).
18548 If you do say Y here, by default the currently visible virtual
18549 terminal (/dev/tty0) will be used as system console. You can change
18550 that with a kernel command line option such as "console=tty3" which
18551 would use the third virtual terminal as system console. (Try "man
18552 bootparam" or see the documentation of your boot loader (lilo or
18553 loadlin) about how to pass options to the kernel at boot time.)
18559 The STI console is the builtin display/keyboard on HP-PARISC
18560 machines. Say Y here to build support for it into your kernel.
18561 The alternative is to use your primary serial port as a console.
18563 Use MDIO for PHY configuration
18565 On some boards the hardware configuration of the ethernet PHY can be
18566 used without any software interaction over the MDIO interface, so
18567 all MII code can be omitted. Say N here if unsure or if you don't
18568 need link status reports.
18572 Enable Ethernet support via the Fast Ethernet Controller (FCC) on
18573 the Motorola MPC8260.
18577 Use MPC8260 fast Ethernet controller 1 to drive Ethernet (default).
18581 Use MPC8260 fast Ethernet controller 2 to drive Ethernet.
18585 Use MPC8260 fast Ethernet controller 3 to drive Ethernet.
18589 Enable Ethernet support via the Motorola MPC8xx serial
18590 communications controller.
18592 # Choice: scc_ethernet
18595 Use MPC8xx serial communications controller 1 to drive Ethernet
18600 Use MPC8xx serial communications controller 2 to drive Ethernet.
18604 Use MPC8xx serial communications controller 3 to drive Ethernet.
18606 Use Big CPM Ethernet Buffers
18607 CONFIG_ENET_BIG_BUFFERS
18608 Allocate large buffers for MPC8xx Ethernet. Increases throughput
18609 and decreases the likelihood of dropped packets, but costs memory.
18611 Apple Desktop Bus (ADB) support
18613 Apple Desktop Bus (ADB) support is for support of devices which
18614 are connected to an ADB port. ADB devices tend to have 4 pins.
18615 If you have an Apple Macintosh prior to the iMac, or a
18616 "Blue and White G3", you probably want to say Y here. Otherwise
18619 Support for CUDA based PowerMacs
18621 This provides support for CUDA based Power Macintosh systems. This
18622 includes most OldWorld PowerMacs, the first generation iMacs, the
18623 Blue&White G3 and the Yikes G4 (PCI Graphics). All later models
18624 should use CONFIG_ADB_PMU instead.
18628 Support for PMU-based PowerMacs
18630 This provides support for PMU based Power Macintosh systems. This
18631 includes all PowerBooks and all AGP-based machines.
18635 Include MacIO ADB driver
18637 Say Y here to include direct support for the ADB controller in the
18638 Hydra chip used on PowerPC Macintoshes of the CHRP type. (The Hydra
18639 also includes a MESH II SCSI controller, DBDMA controller, VIA chip,
18640 OpenPIC controller and two RS422/Geoports.)
18642 Support for ADB keyboard (old driver)
18643 CONFIG_ADB_KEYBOARD
18644 This option allows you to use an ADB keyboard attached to your
18645 machine. Note that this disables any other (ie. PS/2) keyboard
18646 support, even if your machine is physically capable of using both at
18649 If you use an ADB keyboard (4 pin connector), say Y here.
18650 If you use a PS/2 keyboard (6 pin connector), say N here.
18652 HIL keyboard support
18654 The "Human Interface Loop" is a older, 8-channel USB-like controller
18655 used in Hewlett Packard PA-RISC based machines. There are a few
18656 cases where it is seen on PC/MAC architectures as well, usually also
18657 manufactured by HP. This driver is based off MACH and BSD drivers,
18658 and implements support for a keyboard attached to the HIL port.
18659 Full support for the USB-like functions and non-keyboard channels of
18660 the HIL is not provided for in this driver. There are vestiges of
18661 mouse support in the driver, but it is probably not working. The
18662 necessary hardware documentation to fully support the HIL controller
18663 and interface it to the linux-input API is lacking.
18665 Enable this option if you intend to use a HIL keyboard.
18667 HP System Device Controller support
18669 This option enables supports for the the "System Device Controller",
18670 an i8042 carrying microcode to manage a few miscellanous devices
18671 on some Hewlett Packard systems. The SDC itself contains a 10ms
18672 resolution timer/clock capable of delivering interrupts on periodic
18673 and one-shot basis. The SDC may also be connected to a battery-backed
18674 real-time clock, a basic audio waveform generator, and an HP-HIL
18675 Master Link Controller serving up to seven input devices.
18677 By itself this option is rather useless, but enabling it will
18678 enable selection of drivers for the abovementioned devices.
18679 It is, however, incompatible with the old, reliable HIL keyboard
18680 driver, and the new HIL driver is experimental, so if you plan to
18681 use a HIL keyboard as your primary keyboard, you may wish to
18682 keep using that driver until the new HIL drivers have had more
18685 Include IOP (IIfx/Quadra 9x0) ADB driver
18687 The I/O Processor (IOP) is an Apple custom IC designed to provide
18688 intelligent support for I/O controllers. It is described at
18689 <http://www.angelfire.com/ca2/dev68k/iopdesc.html> to enable direct
18690 support for it, say 'Y' here.
18692 Mac II style Apple Desktop Bus support
18694 Say Y here if want your kernel to support Macintosh systems that use
18695 the Mac II style ADB. This includes the II, IIx, IIcx, SE/30, IIci,
18696 Quadra 610, Quadra 650, Quadra 700, Quadra 800, Centris 610 and
18699 Mac IIsi style Apple Desktop Bus support
18701 Say Y here if want your kernel to support Macintosh systems that use
18702 the Mac IIsi style ADB. This includes the IIsi, IIvi, IIvx, Classic
18703 II, LC, LC II, LC III, Performa 460, and the Performa 600.
18705 Apple 68K PowerBook Power Management and Desktop Bus support
18707 Say Y here if want your kernel to support the m68k based Powerbooks.
18708 This includes the PowerBook 140, PowerBook 145, PowerBook 150,
18709 PowerBook 160, PowerBook 165, PowerBook 165c, PowerBook 170,
18710 PowerBook 180, PowerBook, 180c, PowerBook 190cs, PowerBook 520,
18711 PowerBook Duo 210, PowerBook Duo 230, PowerBook Duo 250,
18712 PowerBook Duo 270c, PowerBook Duo 280 and PowerBook Duo 280c.
18714 Macintosh IIfx/Quadra 900/Quadra 950 floppy support
18715 CONFIG_BLK_DEV_SWIM_IOP
18716 Say Y here to support the SWIM (Super Woz Integrated Machine) IOP
18717 floppy controller on the Macintosh IIfx and Quadra 900/950.
18719 Macintosh NS8390 based Ethernet support
18721 If you want to include a driver to support Nubus or LC-PDS
18722 Ethernet cards using an NS8390 chipset or its equivalent, say Y
18723 and read the Ethernet-HOWTO, available from
18724 <http://www.tldp.org/docs.html#howto>.
18726 Macintosh CS89x0 based Ethernet support
18728 Support for CS89x0 chipset based Ethernet cards. If you have a
18729 Nubus or LC-PDS network (Ethernet) card of this type, say Y and
18730 read the Ethernet-HOWTO, available from
18731 <http://www.tldp.org/docs.html#howto>.
18733 If you want to compile this as a module ( = code which can be
18734 inserted in and removed from the running kernel whenever you want),
18735 say M here and read <file:Documentation/modules.txt> as well as
18736 <file:Documentation/networking/net-modules.txt>. This module will
18737 be called mac89x0.o.
18739 Macintosh onboard AMD 79C940 MACE based Ethernet support
18741 Support for the onboard AMD 79C940 MACE Ethernet controller used in
18742 the 660AV and 840AV Macintosh. If you have one of these Macintoshes
18743 say Y and read the Ethernet-HOWTO, available from
18744 <http://www.tldp.org/docs.html#howto>.
18746 Macintosh SONIC based Ethernet support (onboard, NuBus, LC, CS)
18748 Support for NatSemi SONIC based Ethernet devices. This includes
18749 the onboard Ethernet in many Quadras as well as some LC-PDS,
18750 a few Nubus and all known Comm Slot Ethernet cards. If you have
18751 one of these say Y and read the Ethernet-HOWTO, available from
18752 <http://www.tldp.org/docs.html#howto>.
18754 If you want to compile this as a module ( = code which can be
18755 inserted in and removed from the running kernel whenever you want),
18756 say M here and read <file:Documentation/modules.txt> as well as
18757 <file:Documentation/networking/net-modules.txt>. This module will
18758 be called macsonic.o.
18760 Macintosh NCR5380 SCSI support
18762 This is the NCR 5380 SCSI controller included on most of the 68030
18763 based Macintoshes. If you have one of these say Y and read the
18764 SCSI-HOWTO, available from
18765 <http://www.tldp.org/docs.html#howto>.
18767 Macintosh NCR53c9[46] SCSI support
18768 CONFIG_SCSI_MAC_ESP
18769 This is the NCR 53c9x SCSI controller found on most of the 68040
18770 based Macintoshes. If you have one of these say Y and read the
18771 SCSI-HOWTO, available from
18772 <http://www.tldp.org/docs.html#howto>.
18774 This driver is also available as a module ( = code which can be
18775 inserted in and removed from the running kernel whenever you want).
18776 The module will be called mac_esp.o. If you want to compile it as
18777 a module, say M here and read <file:Documentation/modules.txt>.
18779 Standard/generic (8250/16550 and compatible UARTs) serial support
18781 This selects whether you want to include the driver for the standard
18782 serial ports. The standard answer is Y. People who might say N
18783 here are those that are setting up dedicated Ethernet WWW/FTP
18784 servers, or users that have one of the various bus mice instead of a
18785 serial mouse and don't intend to use their machine's standard serial
18786 port for anything. (Note that the Cyclades and Stallion multi
18787 serial port drivers do not need this driver built in for them to
18790 If you want to compile this driver as a module, say M here and read
18791 <file:Documentation/modules.txt>. The module will be called
18793 [WARNING: Do not compile this driver as a module if you are using
18794 non-standard serial ports, since the configuration information will
18795 be lost when the driver is unloaded. This limitation may be lifted
18798 BTW1: If you have a mouseman serial mouse which is not recognized by
18799 the X window system, try running gpm first.
18801 BTW2: If you intend to use a software modem (also called Winmodem)
18802 under Linux, forget it. These modems are crippled and require
18803 proprietary drivers which are only available under Windows.
18805 Most people will say Y or M here, so that they can use serial mice,
18806 modems and similar devices connecting to the standard serial ports.
18808 Support for console on serial port
18809 CONFIG_SERIAL_CONSOLE
18810 If you say Y here, it will be possible to use a serial port as the
18811 system console (the system console is the device which receives all
18812 kernel messages and warnings and which allows logins in single user
18813 mode). This could be useful if some terminal or printer is connected
18814 to that serial port.
18816 Even if you say Y here, the currently visible virtual console
18817 (/dev/tty0) will still be used as the system console by default, but
18818 you can alter that using a kernel command line option such as
18819 "console=ttyS1". (Try "man bootparam" or see the documentation of
18820 your boot loader (lilo or loadlin) about how to pass options to the
18821 kernel at boot time.)
18823 If you don't have a VGA card installed and you say Y here, the
18824 kernel will automatically use the first serial line, /dev/ttyS0, as
18829 Support for serial port described by EFI HCDP table
18831 If you wish to make the serial console port described by the EFI
18832 HCDP table available for use as serial console or general
18833 purpose port, say Y here. See
18834 <http://www.dig64.org/specifications/DIG64_HCDPv10a_01.pdf>.
18836 Support for PowerMac serial ports
18838 If you have Macintosh style serial ports (8 pin mini-DIN), say Y
18839 here. If you also have regular serial ports and enable the driver
18840 for them, you can't currently use the serial console feature.
18842 Comtrol Rocketport support
18844 This is a driver for the Comtrol Rocketport cards which provide
18845 multiple serial ports. You would need something like this to connect
18846 more than two modems to your Linux box, for instance in order to
18847 become a dial-in server.
18849 If you want to compile this driver as a module, say M here and read
18850 <file:Documentation/modules.txt>. The module will be called
18853 Digiboard Intelligent async support
18855 This is a driver for Digi International's Xx, Xeve, and Xem series
18856 of cards which provide multiple serial ports. You would need
18857 something like this to connect more than two modems to your Linux
18858 box, for instance in order to become a dial-in server. This driver
18859 supports the original PC (ISA) boards as well as PCI, and EISA. If
18860 you have a card like this, say Y here and read the file
18861 <file:Documentation/digiepca.txt>.
18863 NOTE: There is another, separate driver for the Digiboard PC boards:
18864 "Digiboard PC/Xx Support" below. You should (and can) only select
18865 one of the two drivers.
18867 If you want to compile this driver as a module, say M here and read
18868 <file:Documentation/modules.txt>. The module will be called epca.o.
18870 Digiboard PC/Xx Support
18872 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
18873 that give you many serial ports. You would need something like this
18874 to connect more than two modems to your Linux box, for instance in
18875 order to become a dial-in server. If you have a card like that, say
18876 Y here and read the file <file:Documentation/digiboard.txt>.
18878 If you want to compile this driver as a module, say M here and read
18879 <file:Documentation/modules.txt>. The module will be called pcxx.o.
18881 SDL RISCom/8 card support
18883 This is a driver for the SDL Communications RISCom/8 multiport card,
18884 which gives you many serial ports. You would need something like
18885 this to connect more than two modems to your Linux box, for instance
18886 in order to become a dial-in server. If you have a card like that,
18887 say Y here and read the file <file:Documentation/riscom8.txt>.
18889 Also it's possible to say M here and compile this driver as kernel
18890 loadable module; the module will be called riscom8.o.
18892 Computone IntelliPort Plus serial support
18894 This driver supports the entire family of Intelliport II/Plus
18895 controllers with the exception of the MicroChannel controllers and
18896 products previous to the Intelliport II. These are multiport cards,
18897 which give you many serial ports. You would need something like this
18898 to connect more than two modems to your Linux box, for instance in
18899 order to become a dial-in server. If you have a card like that, say
18900 Y here and read <file:Documentation/computone.txt>.
18902 If you want to compile this as a module ( = code which can be
18903 inserted in and removed from the running kernel whenever you want),
18904 say M here and read <file:Documentation/modules.txt>. You will get
18905 two modules called ip2.o and ip2main.o.
18907 Specialix IO8+ card support
18909 This is a driver for the Specialix IO8+ multiport card (both the
18910 ISA and the PCI version) which gives you many serial ports. You
18911 would need something like this to connect more than two modems to
18912 your Linux box, for instance in order to become a dial-in server.
18914 If you have a card like that, say Y here and read the file
18915 <file:Documentation/specialix.txt>. Also it's possible to say M here
18916 and compile this driver as kernel loadable module which will be
18917 called specialix.o.
18919 Specialix DTR/RTS pin is RTS
18920 CONFIG_SPECIALIX_RTSCTS
18921 The Specialix IO8+ card can only support either RTS or DTR. If you
18922 say N here, the driver will use the pin as "DTR" when the tty is in
18923 software handshake mode. If you say Y here or hardware handshake is
18924 on, it will always be RTS. Read the file
18925 <file:Documentation/specialix.txt> for more information.
18927 Specialix RIO system support
18929 This is a driver for the Specialix RIO, a smart serial card which
18930 drives an outboard box that can support up to 128 ports. Product
18931 information is at <http://www.sphinxcst.co.uk/perle/multi.htm>.
18932 There are both ISA and PCI versions.
18934 Support really old RIO/PCI cards
18936 Older RIO PCI cards need some initialization-time configuration to
18937 determine the IRQ and some control addresses. If you have a RIO and
18938 this doesn't seem to work, try setting this to Y.
18940 Cyclades async mux support
18942 This is a driver for a card that gives you many serial ports. You
18943 would need something like this to connect more than two modems to
18944 your Linux box, for instance in order to become a dial-in server.
18945 For information about the Cyclades-Z card, read
18946 <file:drivers/char/README.cycladesZ>.
18948 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
18951 If you want to compile this as a module ( = code which can be
18952 inserted in and removed from the running kernel whenever you want),
18953 say M here and read <file:Documentation/modules.txt>. The module
18954 will be called cyclades.o.
18956 If you haven't heard about it, it's safe to say N.
18958 Cyclades-Z interrupt mode operation
18960 The Cyclades-Z family of multiport cards allows 2 (two) driver op
18961 modes: polling and interrupt. In polling mode, the driver will check
18962 the status of the Cyclades-Z ports every certain amount of time
18963 (which is called polling cycle and is configurable). In interrupt
18964 mode, it will use an interrupt line (IRQ) in order to check the
18965 status of the Cyclades-Z ports. The default op mode is polling. If
18968 Stallion multiport serial support
18970 Stallion cards give you many serial ports. You would need something
18971 like this to connect more than two modems to your Linux box, for
18972 instance in order to become a dial-in server. If you say Y here,
18973 you will be asked for your specific card model in the next
18974 questions. Make sure to read <file:Documentation/stallion.txt> in
18975 this case. If you have never heard about all this, it's safe to
18978 Stallion EasyIO or EC8/32 support
18980 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
18981 card, then this is for you; say Y. Make sure to read
18982 <file:Documentation/stallion.txt>.
18984 If you want to compile this as a module ( = code which can be
18985 inserted in and removed from the running kernel whenever you want),
18986 say M here and read <file:Documentation/modules.txt>. The module
18987 will be called stallion.o.
18989 Stallion EC8/64, ONboard, Brumby support
18991 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
18992 serial multiport card, say Y here. Make sure to read
18993 <file:Documentation/stallion.txt>.
18995 To compile it as a module ( = code which can be inserted in and
18996 removed from the running kernel whenever you want), say M here and
18997 read <file:Documentation/modules.txt>. The module will be called
19000 PDC software console support
19002 Saying Y here will enable the software based PDC console to be
19003 used as the system console. This is useful for machines in
19004 which the hardware based console has not been written yet. The
19005 following steps must be competed to use the PDC console:
19007 1. create the device entry (mknod /dev/ttyB0 c 60 0)
19008 2. Edit the /etc/inittab to start a getty listening on /dev/ttyB0
19009 3. Add device ttyB0 to /etc/securetty (if you want to log on as
19010 root on this console.)
19011 4. Change the kernel command console parameter to: console=ttyB0
19013 Microgate SyncLink adapter support
19015 Provides support for the SyncLink ISA and PCI multiprotocol serial
19016 adapters. These adapters support asynchronous and HDLC bit
19017 synchronous communication up to 10Mbps (PCI adapter).
19019 This driver can only be built as a module ( = code which can be
19020 inserted in and removed from the running kernel whenever you want).
19021 The module will be called synclink.o. If you want to do that, say M
19025 Enable support for the SyncLink Multiport (2 or 4 ports)
19026 serial adapter, running asynchronous and HDLC communications up
19027 to 2.048Mbps. Each ports is independently selectable for
19028 RS-232, V.35, RS-449, RS-530, and X.21
19030 This driver may be built as a module ( = code which can be
19031 inserted in and removed from the running kernel whenever you want).
19032 The module will be called synclinkmp.o. If you want to do that, say M
19035 Synchronous HDLC line discipline support
19037 Allows synchronous HDLC communications with tty device drivers that
19038 support synchronous HDLC such as the Microgate SyncLink adapter.
19040 This driver can only be built as a module ( = code which can be
19041 inserted in and removed from the running kernel whenever you want).
19042 The module will be called n_hdlc.o. If you want to do that, say M
19045 Specialix SX (and SI) card support
19047 This is a driver for the SX and SI multiport serial cards.
19048 Please read the file <file:Documentation/sx.txt> for details.
19050 This driver can only be built as a module ( = code which can be
19051 inserted in and removed from the running kernel whenever you want).
19052 The module will be called sx.o. If you want to do that, say M here.
19054 Hayes ESP serial port support
19056 This is a driver which supports Hayes ESP serial ports. Both single
19057 port cards and multiport cards are supported. Make sure to read
19058 <file:Documentation/hayes-esp.txt>.
19060 To compile this driver as a module ( = code which can be inserted in
19061 and removed from the running kernel whenever you want), say M here
19062 and read <file:Documentation/modules.txt>. The module will be
19063 called esp.o. If unsure, say N.
19065 Moxa Intellio support
19066 CONFIG_MOXA_INTELLIO
19067 Say Y here if you have a Moxa Intellio multiport serial card.
19069 This driver can also be built as a module ( = code which can be
19070 inserted in and removed from the running kernel whenever you want).
19071 The module will be called moxa.o. If you want to do that, say M
19074 Moxa SmartIO support
19075 CONFIG_MOXA_SMARTIO
19076 Say Y here if you have a Moxa SmartIO multiport serial card.
19078 This driver can also be built as a module ( = code which can be
19079 inserted in and removed from the running kernel whenever you want).
19080 The module will be called mxser.o. If you want to do that, say M
19083 Multi-Tech multiport card support
19085 This is a driver for the Multi-Tech cards which provide several
19086 serial ports. The driver is experimental and can currently only be
19087 built as a module ( = code which can be inserted in and removed from
19088 the running kernel whenever you want). Please read
19089 <file:Documentation/modules.txt>. The module will be called
19094 A pseudo terminal (PTY) is a software device consisting of two
19095 halves: a master and a slave. The slave device behaves identical to
19096 a physical terminal; the master device is used by a process to
19097 read data from and write data to the slave, thereby emulating a
19098 terminal. Typical programs for the master side are telnet servers
19101 Linux has traditionally used the BSD-like names /dev/ptyxx for
19102 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
19103 has a number of problems. The GNU C library glibc 2.1 and later,
19104 however, supports the Unix98 naming standard: in order to acquire a
19105 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
19106 terminal is then made available to the process and the pseudo
19107 terminal slave can be accessed as /dev/pts/<number>. What was
19108 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
19110 The entries in /dev/pts/ are created on the fly by a virtual
19111 file system; therefore, if you say Y here you should say Y to
19112 "/dev/pts file system for Unix98 PTYs" as well.
19114 If you want to say Y here, you need to have the C library glibc 2.1
19115 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
19116 Read the instructions in <file:Documentation/Changes> pertaining to
19117 pseudo terminals. It's safe to say N.
19119 Maximum number of Unix98 PTYs in use (0-2048)
19120 CONFIG_UNIX98_PTY_COUNT
19121 The maximum number of Unix98 PTYs that can be used at any one time.
19122 The default is 256, and should be enough for desktop systems. Server
19123 machines which support incoming telnet/rlogin/ssh connections and/or
19124 serve several X terminals may want to increase this: every incoming
19125 connection and every xterm uses up one PTY.
19127 When not in use, each additional set of 256 PTYs occupy
19128 approximately 8 KB of kernel memory on 32-bit architectures.
19130 Parallel printer support
19132 If you intend to attach a printer to the parallel port of your Linux
19133 box (as opposed to using a serial printer; if the connector at the
19134 printer has 9 or 25 holes ["female"], then it's serial), say Y.
19135 Also read the Printing-HOWTO, available from
19136 <http://www.tldp.org/docs.html#howto>.
19138 It is possible to share one parallel port among several devices
19139 (e.g. printer and ZIP drive) and it is safe to compile the
19140 corresponding drivers into the kernel. If you want to compile this
19141 driver as a module however ( = code which can be inserted in and
19142 removed from the running kernel whenever you want), say M here and
19143 read <file:Documentation/modules.txt> and
19144 <file:Documentation/parport.txt>. The module will be called lp.o.
19146 If you have several parallel ports, you can specify which ports to
19147 use with the "lp" kernel command line option. (Try "man bootparam"
19148 or see the documentation of your boot loader (lilo or loadlin) about
19149 how to pass options to the kernel at boot time.) The syntax of the
19150 "lp" command line option can be found in <file:drivers/char/lp.c>.
19152 If you have more than 8 printers, you need to increase the LP_NO
19153 macro in lp.c and the PARPORT_MAX macro in parport.h.
19155 Support for console on line printer
19157 If you want kernel messages to be printed out as they occur, you
19158 can have a console on the printer. This option adds support for
19159 doing that; to actually get it to happen you need to pass the
19160 option "console=lp0" to the kernel at boot time.
19162 If the printer is out of paper (or off, or unplugged, or too
19163 busy..) the kernel will stall until the printer is ready again.
19164 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
19165 can make the kernel continue when this happens,
19166 but it'll lose the kernel messages.
19170 Support for user-space parallel port device drivers
19172 Saying Y to this adds support for /dev/parport device nodes. This
19173 is needed for programs that want portable access to the parallel
19174 port, for instance deviceid (which displays Plug-and-Play device
19177 This is the parallel port equivalent of SCSI generic support (sg).
19178 It is safe to say N to this -- it is not needed for normal printing
19179 or parallel port CD-ROM/disk support.
19181 This support is also available as a module. If you want to compile
19182 it as a module, say M here and read
19183 <file:Documentation/modules.txt>. The module will be called
19188 Cobalt Networks support
19190 Support for Cobalt Networks x86-based servers.
19192 Gen III (3000 series) system support
19193 CONFIG_COBALT_GEN_III
19194 This option enables support for the 3000 series of Cobalt Networks
19195 systems. This includes the RaQ 3, RaQ 4, and Qube 3 product lines.
19197 This platform uses an AMD K6-2 processor, an ALI M1541/1533 chipset,
19198 an optional NCR 53c875 SCSI controller, and two Intel 82559ER or
19199 National Semiconductor DP83815 NICs.
19201 Getting this option wrong will likely result in a kernel that does
19202 not boot. Selecting support for more than 1 system series will add
19203 bloat to your kernel, but will not cause anything bad to happen.
19205 If you have a Cobalt Networks System, but aren't sure what kind,
19208 Gen V (5000 series) system support
19209 CONFIG_COBALT_GEN_V
19210 This option enables support for the 5000 series of Cobalt Networks
19211 systems. This includes the RaQ XTR product line.
19213 This platform uses Intel Pentium III Coppermine FCPGA CPUs, the
19214 ServerWorks LE chipset (with registered ECC DIMMs only!), two
19215 HighPoint HPT370 IDE controllers, and two National Semiconductor
19218 Getting this option wrong will likely result in a kernel that does
19219 not boot. Selecting support for more than 1 system series will add
19220 bloat to your kernel, but will not cause anything bad to happen.
19222 If you have a Cobalt Networks System, but aren't sure what kind,
19225 Create legacy /proc files
19226 CONFIG_COBALT_OLDPROC
19227 This option forces some Cobalt Networks drivers to support legacy
19228 files in /proc. Older versions of these drivers exported files
19229 directly in /proc, as opposed to the newer /proc/cobalt. If you say
19230 N to this option, the old filenames will no longer be exported.
19231 Regardless of your selection here, files in /proc/cobalt will be
19232 exported. Of course, you have to include support for /proc fs, too.
19234 It is safe to say Y here.
19236 Front panel LCD support
19238 This enables support for the Cobalt Networks front panel. This is
19239 for the LCD panel and buttons. The primary method for connection is
19240 via the parallel port (IO base 0x370), but newer systems use an
19243 If you have a Cobalt Networks system, you should say Y here.
19245 Software controlled LED support
19247 This enables support for the software-controlled LEDs on Cobalt
19248 Networks systems. This includes the fault light and front panel
19249 LEDs on the RaQ XTR, the lightbar on the Qube 3, and others.
19251 If you have a Cobalt Networks system, you should say Y here.
19253 Silicon serial number support
19254 CONFIG_COBALT_SERNUM
19255 This enables support for the on-board serial number on Cobalt
19256 Networks systems. This is a universally-unique 64-bit serial
19257 number. Some systems use a Dallas DS2401 chip, others have an I2C
19260 If you select Y here, the files /proc/cobalt/hostid and
19261 /proc/cobalt/serialnumber will be created. The hostid file contains
19262 a 32 bit integer generated from the serial number, in binary form.
19263 The serialnumber file contains the hexadecimal representation of the
19264 serial number, in ASCII.
19266 If you have a Cobalt Networks system, you should say Y here.
19268 Chipset watchdog timer support
19270 This enables support for the watchdog timer built into Cobalt
19271 chipsets. The timer wakes up periodically, to make find out if
19272 system has hung, or disabled interrupts too long. The result of
19273 detecting a hang is a hard reboot.
19275 If you have a Cobalt Networks system, you should say Y here.
19277 Thermal sensor support
19278 CONFIG_COBALT_THERMAL
19279 This enables support for the thermal sensor(s) built into Cobalt
19280 Networks systems. This driver exports /proc/cobalt/thermal_sensors.
19282 If you have a Cobalt Networks system, you should say Y here.
19284 Fan tachometer support
19286 This enables support for the fan tachometers built into some Cobalt
19287 Networks systems. This driver exports /proc/cobalt/faninfo. Some
19288 Cobalt software depends on this feature, and enabling it does not
19291 If you have a Cobalt Networks system, you should say Y here, unless
19292 you are absolutely sure.
19294 Disk drive ruler support
19295 CONFIG_COBALT_RULER
19296 This enables support for the cobalt hard drive ruler, found on some
19297 Cobalt systems, including the RaQ XTR. This is the device that
19298 enables swapping of drives. It is not needed for basic disk
19299 operation. Enabling this on a system with no ruler will have no
19302 If you have a Cobalt Networks system, you should say Y here,
19303 unless you are absolutely sure.
19306 CONFIG_SOUND_IT8172
19307 Say Y here to support the on-board sound generator on the Integrated
19308 Technology Express, Inc. ITE8172 SBC. Vendor page at
19309 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
19310 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
19314 I2C (pronounce: I-square-C) is a slow serial bus protocol used in
19315 many micro controller applications and developed by Philips. SMBus,
19316 or System Management Bus is a subset of the I2C protocol. More
19317 information is contained in the directory <file:Documentation/i2c/>,
19318 especially in the file called "summary" there.
19320 Both I2C and SMBus are supported here. You will need this for
19321 hardware sensors support, and also for Video For Linux support.
19322 Specifically, if you want to use a BT848 based frame grabber/overlay
19323 boards under Linux, say Y here and also to "I2C bit-banging
19324 interfaces", below.
19326 If you want I2C support, you should say Y here and also to the
19327 specific driver for your bus adapter(s) below. If you say Y to
19328 "/proc file system" below, you will then get a /proc interface which
19329 is documented in <file:Documentation/i2c/proc-interface>.
19331 This I2C support is also available as a module. If you want to
19332 compile it as a module, say M here and read
19333 <file:Documentation/modules.txt>.
19334 The module will be called i2c-core.o.
19336 UltraSPARC-III bootbus i2c controller driver
19338 The BBC devices on the UltraSPARC III have two I2C controllers. The
19339 first I2C controller connects mainly to configuration PROMs (NVRAM,
19340 CPU configuration, DIMM types, etc.). The second I2C controller
19341 connects to environmental control devices such as fans and
19342 temperature sensors. The second controller also connects to the
19343 smartcard reader, if present. Say Y to enable support for these.
19345 I2C bit-banging interfaces
19347 This allows you to use a range of I2C adapters called bit-banging
19348 adapters. Say Y if you own an I2C adapter belonging to this class
19349 and then say Y to the specific driver for you adapter below.
19351 This support is also available as a module. If you want to compile
19352 it as a module, say M here and read
19353 <file:Documentation/modules.txt>.
19354 The module will be called i2c-algo-bit.o.
19356 Philips style parallel port adapter
19357 CONFIG_I2C_PHILIPSPAR
19358 This supports parallel-port I2C adapters made by Philips. Say Y if
19359 you own such an adapter.
19361 This driver is also available as a module. If you want to compile
19362 it as a module, say M here and read
19363 <file:Documentation/modules.txt>.
19364 The module will be called i2c-philips-par.o.
19366 Note that if you want support for different parallel port devices,
19367 life will be much easier if you compile them all as modules.
19371 This supports parallel-port I2C adapters called ELV. Say Y if you
19372 own such an adapter.
19374 This driver is also available as a module. If you want to compile
19375 it as a module, say M here and read
19376 <file:Documentation/modules.txt>.
19377 The module will be called i2c-elv.o.
19379 Velleman K8000 adapter
19380 CONFIG_I2C_VELLEMAN
19381 This supports the Velleman K8000 parallel-port I2C adapter. Say Y
19382 if you own such an adapter.
19384 This driver is also available as a module. If you want to compile
19385 it as a module, say M here and read
19386 <file:Documentation/modules.txt>.
19387 The module will be called i2c-velleman.o.
19389 I2C PCF 8584 interfaces
19391 This allows you to use a range of I2C adapters called PCF adapters.
19392 Say Y if you own an I2C adapter belonging to this class and then say
19393 Y to the specific driver for you adapter below.
19395 This support is also available as a module. If you want to compile
19396 it as a module, say M here and read
19397 <file:Documentation/modules.txt>.
19398 The module will be called i2c-algo-pcf.o.
19402 This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
19405 This driver is also available as a module. If you want to compile
19406 it as a module, say M here and read
19407 <file:Documentation/modules.txt>.
19408 The module will be called i2c-elektor.o.
19411 CONFIG_ITE_I2C_ALGO
19412 This supports the use the ITE8172 I2C interface found on some MIPS
19413 systems. Say Y if you have one of these. You should also say Y for
19414 the ITE I2C peripheral driver support below.
19416 This support is also available as a module. If you want to compile
19417 it as a modules, say M here and read
19418 <file:Documentation/modules.txt>.
19419 The module will be called i2c-algo-ite.o.
19422 CONFIG_ITE_I2C_ADAP
19423 This supports the ITE8172 I2C peripheral found on some MIPS
19424 systems. Say Y if you have one of these. You should also say Y for
19425 the ITE I2C driver algorithm support above.
19427 This support is also available as a module. If you want to compile
19428 it as a module, say M here and read
19429 <file:Documentation/modules.txt>.
19430 The module will be called i2c-adap-ite.o.
19432 SiByte I2C Algorithm
19433 CONFIG_I2C_ALGO_SIBYTE
19434 Supports the SiByte SOC on-chip I2C interfaces (2 channels).
19436 MAX1617 Temperature Sensor
19438 This builds a simple polling driver for the Maxim 1617 temperature
19439 sensor. Currently the device is only supported on a SiByte I2C
19440 adapter, and the driver prints status updates to the system log.
19443 CONFIG_I2C_ALGO_SGI
19444 Supports the SGI interfaces like the ones found on SGI Indy VINO
19447 I2C device interface
19449 Say Y here to use i2c-* device files, usually found in the /dev
19450 directory on your system. They make it possible to have user-space
19451 programs use the I2C bus. Information on how to do this is
19452 contained in the file <file:Documentation/i2c/dev-interface>.
19454 This code is also available as a module. If you want to compile
19455 it as a module, say M here and read
19456 <file:Documentation/modules.txt>.
19457 The module will be called i2c-dev.o.
19459 I2C /proc interface (required for hardware sensors)
19461 This provides support for i2c device entries in the /proc filesystem.
19462 The entries will be found in /proc/sys/dev/sensors.
19464 This code is also available as a module. If you want to compile
19465 it as a module, say M here and read <file:Documentation/modules.txt>.
19466 The module will be called i2c-proc.o.
19468 Powermac Keywest I2C interface
19470 This supports the use of the I2C interface in the combo-I/O
19471 chip on recent Apple machines. Say Y if you have such a machine.
19473 This driver is also available as a module. If you want to compile
19474 it as a module, say M here and read Documentation/modules.txt.
19475 The module will be called i2c-keywest.o.
19479 Say Y here if your machine has a bus mouse as opposed to a serial
19480 mouse. Most people have a regular serial MouseSystem or
19481 Microsoft mouse (made by Logitech) that plugs into a COM port
19482 (rectangular with 9 or 25 pins). These people say N here.
19484 If you have a laptop, you either have to check the documentation or
19485 experiment a bit to find out whether the trackball is a serial mouse
19486 or not; it's best to say Y here for you.
19488 This is the generic bus mouse driver code. If you have a bus mouse,
19489 you will have to say Y here and also to the specific driver for your
19492 This code is also available as a module ( = code which can be
19493 inserted in and removed from the running kernel whenever you want).
19494 The module will be called busmouse.o. If you want to compile it as a
19495 module, say M here and read <file:Documentation/modules.txt>.
19497 Mouse Support (not serial and bus mice)
19499 This is for machines with a mouse which is neither a serial nor a
19500 bus mouse. Examples are PS/2 mice (such as the track balls on some
19501 laptops) and some digitizer pads. Most people have a regular serial
19502 MouseSystem or Microsoft mouse (made by Logitech) that plugs into a
19503 COM port (rectangular with 9 or 25 pins). These people say N here.
19504 If you have something else, read the Busmouse-HOWTO, available from
19505 <http://www.tldp.org/docs.html#howto>. This HOWTO contains
19506 information about all non-serial mice, not just bus mice.
19508 If you have a laptop, you either have to check the documentation or
19509 experiment a bit to find out whether the trackball is a serial mouse
19510 or not; it's best to say Y here for you.
19512 Note that the answer to this question won't directly affect the
19513 kernel: saying N will just cause the configurator to skip all
19514 the questions about non-serial mice. If unsure, say Y.
19516 Logitech busmouse support
19517 CONFIG_LOGIBUSMOUSE
19518 Logitech mouse connected to a proprietary interface card. It's
19519 generally a round connector with 9 pins. Note that the newer mice
19520 made by Logitech don't use the Logitech protocol anymore; for those,
19521 you don't need this option. You want to read the Busmouse-HOWTO,
19522 available from <http://www.tldp.org/docs.html#howto>.
19524 If you want to compile this as a module ( = code which can be
19525 inserted in and removed from the running kernel whenever you want),
19526 say M here and read <file:Documentation/modules.txt>. The module
19527 will be called busmouse.o. If you are unsure, say N and read the
19528 HOWTO nevertheless: it will tell you what you have.
19530 PS/2 mouse (aka "auxiliary device") support
19532 The PS/2 mouse connects to a special mouse port that looks much like
19533 the keyboard port (small circular connector with 6 pins). This way,
19534 the mouse does not use any serial ports. This port can also be used
19535 for other input devices like light pens, tablets, keypads. Compaq,
19536 AST and IBM all use this as their mouse port on currently shipping
19537 machines. The trackballs of some laptops are PS/2 mice also. In
19538 particular, the C&T 82C710 mouse on TI Travelmates is a PS/2 mouse.
19540 Although PS/2 mice are not technically bus mice, they are explained
19541 in detail in the Busmouse-HOWTO, available from
19542 <http://www.tldp.org/docs.html#howto>.
19544 When using a PS/2 mouse, you can get problems if you want to use the
19545 mouse both on the Linux console and under X. Using the "-R" option
19546 of the Linux mouse managing program gpm (available from
19547 <ftp://gnu.systemy.it/pub/gpm/>) solves this problem, or you can get
19548 the "mconv2" utility from <ftp://ibiblio.org/pub/Linux/system/mouse/>.
19550 C&T 82C710 mouse port support (as on TI Travelmate)
19551 CONFIG_82C710_MOUSE
19552 This is a certain kind of PS/2 mouse used on the TI Travelmate. If
19553 you are unsure, try first to say N here and come back if the mouse
19554 doesn't work. Read the Busmouse-HOWTO, available from
19555 <http://www.tldp.org/docs.html#howto>.
19557 PC110 digitizer pad support
19559 This drives the digitizer pad on the IBM PC110 palmtop. It can turn
19560 the digitizer pad into a PS/2 mouse emulation with tap gestures or
19561 into an absolute pad.
19563 If you want to compile this as a module ( = code which can be
19564 inserted in and removed from the running kernel whenever you want),
19565 say M here and read <file:Documentation/modules.txt>. The module
19566 will be called pc110pad.o.
19568 Microsoft busmouse support
19570 These animals (also called Inport mice) are connected to an
19571 expansion board using a round connector with 9 pins. If this is what
19572 you have, say Y and read the Busmouse-HOWTO, available from
19573 <http://www.tldp.org/docs.html#howto>.
19575 If you are unsure, say N and read the HOWTO nevertheless: it will
19576 tell you what you have. Also be aware that several vendors talk
19577 about 'Microsoft busmouse' and actually mean PS/2 busmouse -- so
19578 count the pins on the connector.
19580 If you want to compile this as a module ( = code which can be
19581 inserted in and removed from the running kernel whenever you want),
19582 say M here and read <file:Documentation/modules.txt>. The module
19583 will be called msbusmouse.o.
19585 Apple Desktop Bus mouse support
19587 Say Y here if you have this type of bus mouse (4 pin connector) as
19588 is common on Macintoshes. You may want to read the Busmouse-HOWTO,
19589 available from <http://www.tldp.org/docs.html#howto>.
19591 If you want to compile this as a module ( = code which can be
19592 inserted in and removed from the running kernel whenever you want),
19593 say M here and read <file:Documentation/modules.txt>. The module
19594 will be called adbmouse.o.
19596 ATIXL busmouse support
19597 CONFIG_ATIXL_BUSMOUSE
19598 This is a rare type of busmouse that is connected to the back of an
19599 ATI video card. Say Y if you have one of those. Note however that
19600 most mice by ATI are actually Microsoft busmice; you should say Y to
19601 "Microsoft busmouse support" above if you have one of those. Read
19602 the Busmouse-HOWTO, available from
19603 <http://www.tldp.org/docs.html#howto>.
19605 If you want to compile this as a module ( = code which can be
19606 inserted in and removed from the running kernel whenever you want),
19607 say M here and read <file:Documentation/modules.txt>. The module
19608 will be called atixlmouse.o.
19610 If you are unsure, say N and read the HOWTO nevertheless: it will
19611 tell you what you have.
19613 QIC-02 tape support
19615 If you have a non-SCSI tape drive like that, say Y. Or, if you want
19616 to compile this driver as a module ( = code which can be inserted in
19617 and removed from the running kernel whenever you want), say M here
19618 and read <file:Documentation/modules.txt>. The module will be called
19621 iSeries Virtual Tape Support
19623 If you are running Linux on an iSeries system and you want Linux
19624 to read and/or write a tape drive owned by OS/400, say Y here.
19626 Do you want runtime configuration for QIC-02
19627 CONFIG_QIC02_DYNCONF
19628 You can either configure this driver once and for all by editing a
19629 header file (<file:include/linux/tpqic02.h>), in which case you
19630 should say N, or you can fetch a program via anonymous FTP which is
19631 able to configure this driver during runtime. The program to do
19632 this is called 'qic02conf' and it is part of the
19633 tpqic02-support-X.Y.tar.gz support package.
19635 If you want to use the qic02conf program, say Y.
19637 Floppy tape drive (QIC-80/40/3010/3020/TR-1/TR-2/TR-3) support
19639 If you have a tape drive that is connected to your floppy
19640 controller, say Y here.
19642 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
19643 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
19644 controller of their own. These drives (and their companion
19645 controllers) are also supported if you say Y here.
19647 If you have a special controller (such as the CMS FC-10, FC-20,
19648 Mountain Mach-II, or any controller that is based on the Intel 82078
19649 FDC like the high speed controllers by Seagate and Exabyte and
19650 Iomega's "Ditto Dash") you must configure it by selecting the
19651 appropriate entries from the "Floppy tape controllers" sub-menu
19652 below and possibly modify the default values for the IRQ and DMA
19653 channel and the IO base in ftape's configuration menu.
19655 If you want to use your floppy tape drive on a PCI-bus based system,
19656 please read the file <file:drivers/char/ftape/README.PCI>.
19658 The ftape kernel driver is also available as a runtime loadable
19659 module ( = code which can be inserted in and removed from the
19660 running kernel whenever you want). If you want to compile it as a
19661 module, say M here and read <file:Documentation/modules.txt>. The
19662 module will be called ftape.o.
19664 Note that the Ftape-HOWTO is out of date (sorry) and documents the
19665 older version 2.08 of this software but still contains useful
19666 information. There is a web page with more recent documentation at
19667 <http://www.instmath.rwth-aachen.de/~heine/ftape/>. This page
19668 always contains the latest release of the ftape driver and useful
19669 information (backup software, ftape related patches and
19670 documentation, FAQ). Note that the file system interface has
19671 changed quite a bit compared to previous versions of ftape. Please
19672 read <file:Documentation/ftape.txt>.
19674 VFS interface for ftape
19676 Normally, you want to say Y or M. DON'T say N here or you
19677 WON'T BE ABLE TO USE YOUR FLOPPY TAPE DRIVE.
19679 The ftape module itself no longer contains the routines necessary
19680 to interface with the kernel VFS layer (i.e. to actually write data
19681 to and read data from the tape drive). Instead the file system
19682 interface (i.e. the hardware independent part of the driver) has
19683 been moved to a separate module.
19685 If you say M zftape will be compiled as a runtime loadable
19686 module ( = code which can be inserted in and removed from the
19687 running kernel whenever you want). In this case you should read
19688 <file:Documentation/modules.txt>. The module will be called
19691 Regardless of whether you say Y or M here, an additional runtime
19692 loadable module called `zft-compressor.o' which contains code to
19693 support user transparent on-the-fly compression based on Ross
19694 William's lzrw3 algorithm will be produced. If you have enabled the
19695 kernel module loader (i.e. have said Y to "Kernel module loader
19696 support", above) then `zft-compressor.o' will be loaded
19697 automatically by zftape when needed.
19699 Despite its name, zftape does NOT use compression by default. The
19700 file <file:Documentation/ftape.txt> contains a short description of
19701 the most important changes in the file system interface compared to
19702 previous versions of ftape. The ftape home page
19703 <http://www.instmath.rwth-aachen.de/~heine/ftape/> contains
19704 further information.
19706 IMPORTANT NOTE: zftape can read archives created by previous
19707 versions of ftape and provide file mark support (i.e. fast skipping
19708 between tape archives) but previous version of ftape will lack file
19709 mark support when reading archives produced by zftape.
19711 Default block size for zftape
19712 CONFIG_ZFT_DFLT_BLK_SZ
19713 If unsure leave this at its default value, i.e. 10240. Note that
19714 you specify only the default block size here. The block size can be
19715 changed at run time using the MTSETBLK tape operation with the
19716 MTIOCTOP ioctl (i.e. with "mt -f /dev/qft0 setblk #BLKSZ" from the
19717 shell command line).
19719 The probably most striking difference between zftape and previous
19720 versions of ftape is the fact that all data must be written or read
19721 in multiples of a fixed block size. The block size defaults to
19722 10240 which is what GNU tar uses. The values for the block size
19723 should be either 1 or multiples of 1024 up to a maximum value of
19724 63488 (i.e. 62 K). If you specify `1' then zftape's builtin
19725 compression will be disabled.
19727 Reasonable values are `10240' (GNU tar's default block size),
19728 `5120' (afio's default block size), `32768' (default block size some
19729 backup programs assume for SCSI tape drives) or `1' (no restriction
19730 on block size, but disables builtin compression).
19732 Number of DMA buffers
19733 CONFIG_FT_NR_BUFFERS
19734 Please leave this at `3' unless you REALLY know what you are doing.
19735 It is not necessary to change this value. Values below 3 make the
19736 proper use of ftape impossible, values greater than 3 are a waste of
19737 memory. You can change the amount of DMA memory used by ftape at
19738 runtime with "mt -f /dev/qft0 setdrvbuffer #NUMBUFFERS". Each buffer
19739 wastes 32 KB of memory. Please note that this memory cannot be
19742 Enable procfs status report (+2kb)
19744 Optional. Saying Y will result in creation of a directory
19745 `/proc/ftape' under the /proc file system. The files can be viewed
19746 with your favorite pager (i.e. use "more /proc/ftape/history" or
19747 "less /proc/ftape/history" or simply "cat /proc/ftape/history"). The
19748 file will contain some status information about the inserted
19749 cartridge, the kernel driver, your tape drive, the floppy disk
19750 controller and the error history for the most recent use of the
19751 kernel driver. Saying Y will enlarge the size of the ftape driver
19752 by approximately 2 KB.
19754 WARNING: When compiling ftape as a module (i.e. saying M to "Floppy
19755 tape drive") it is dangerous to use ftape's /proc file system
19756 interface. Accessing `/proc/ftape' while the module is unloaded will
19757 result in a kernel Oops. This cannot be fixed from inside ftape.
19760 Controlling the amount of debugging output of ftape
19761 CONFIG_FT_NORMAL_DEBUG
19762 This option controls the amount of debugging output the ftape driver
19763 is ABLE to produce; it does not increase or diminish the debugging
19764 level itself. If unsure, leave this at its default setting,
19765 i.e. choose "Normal".
19767 Ftape can print lots of debugging messages to the system console
19768 resp. kernel log files. Reducing the amount of possible debugging
19769 output reduces the size of the kernel module by some KB, so it might
19770 be a good idea to use "None" for emergency boot floppies.
19772 If you want to save memory then the following strategy is
19773 recommended: leave this option at its default setting "Normal" until
19774 you know that the driver works as expected, afterwards reconfigure
19775 the kernel, this time specifying "Reduced" or "None" and recompile
19776 and install the kernel as usual. Note that choosing "Excessive"
19777 debugging output does not increase the amount of debugging output
19778 printed to the console but only makes it possible to produce
19779 "Excessive" debugging output.
19781 Please read <file:Documentation/ftape.txt> for a short description
19782 how to control the amount of debugging output.
19785 CONFIG_FT_FULL_DEBUG
19786 Extremely verbose output for driver debugging purposes.
19790 Reduced tape driver debugging output.
19793 CONFIG_FT_NO_TRACE_AT_ALL
19794 Suppress all debugging output from the tape drive.
19796 # Choice: ftcontroller
19797 The floppy drive controller for ftape
19799 Only change this setting if you have a special controller. If you
19800 didn't plug any add-on card into your computer system but just
19801 plugged the floppy tape cable into the already existing floppy drive
19802 controller then you don't want to change the default setting,
19803 i.e. choose "Standard".
19805 Choose "MACH-2" if you have a Mountain Mach-2 controller.
19806 Choose "FC-10/FC-20" if you have a Colorado FC-10 or FC-20
19808 Choose "Alt/82078" if you have another controller that is located at
19809 an IO base address different from the standard floppy drive
19810 controller's base address of `0x3f0', or uses an IRQ (interrupt)
19811 channel different from `6', or a DMA channel different from
19812 `2'. This is necessary for any controller card that is based on
19813 Intel's 82078 FDC such as Seagate's, Exabyte's and Iomega's "high
19814 speed" controllers.
19816 If you choose something other than "Standard" then please make
19817 sure that the settings for the IO base address and the IRQ and DMA
19818 channel in the configuration menus below are correct. Use the manual
19819 of your tape drive to determine the correct settings!
19821 If you are already successfully using your tape drive with another
19822 operating system then you definitely should use the same settings
19823 for the IO base, the IRQ and DMA channel that have proven to work
19824 with that other OS.
19826 Note that this menu lets you specify only the default setting for
19827 the hardware setup. The hardware configuration can be changed at
19828 boot time (when ftape is compiled into the kernel, i.e. if you
19829 have said Y to "Floppy tape drive") or module load time (i.e. if you
19830 have said M to "Floppy tape drive").
19832 Please read also the file <file:Documentation/ftape.txt> which
19833 contains a short description of the parameters that can be set at
19834 boot or load time. If you want to use your floppy tape drive on a
19835 PCI-bus based system, please read the file
19836 <file:drivers/char/ftape/README.PCI>.
19838 IO base for the floppy disk controller used with Ftape
19840 You don't need to specify a value if the following default
19841 settings for the base IO address are correct:
19842 <<< MACH-2 : 0x1E0 >>>
19843 <<< FC-10/FC-20: 0x180 >>>
19844 <<< Secondary : 0x370 >>>
19845 Secondary refers to a secondary FDC controller like the "high speed"
19846 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
19847 Please make sure that the setting for the IO base address
19848 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
19849 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
19850 successfully using the tape drive with another operating system then
19851 you definitely should use the same settings for the IO base that has
19852 proven to work with that other OS.
19854 Note that this menu lets you specify only the default setting for
19855 the IO base. The hardware configuration can be changed at boot time
19856 (when ftape is compiled into the kernel, i.e. if you specified Y to
19857 "Floppy tape drive") or module load time (i.e. if you have said M to
19858 "Floppy tape drive").
19860 Please read also the file <file:Documentation/ftape.txt> which
19861 contains a short description of the parameters that can be set at
19864 IRQ channel for the floppy disk controller used with Ftape
19866 You don't need to specify a value if the following default
19867 settings for the interrupt channel are correct:
19869 <<< FC-10/FC-20: 9 >>>
19870 <<< Secondary : 6 >>>
19871 Secondary refers to secondary a FDC controller like the "high speed"
19872 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
19873 Please make sure that the setting for the IO base address
19874 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
19875 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
19876 successfully using the tape drive with another operating system then
19877 you definitely should use the same settings for the IO base that has
19878 proven to work with that other OS.
19880 Note that this menu lets you specify only the default setting for
19881 the IRQ channel. The hardware configuration can be changed at boot
19882 time (when ftape is compiled into the kernel, i.e. if you said Y to
19883 "Floppy tape drive") or module load time (i.e. if you said M to
19884 "Floppy tape drive").
19886 Please read also the file <file:Documentation/ftape.txt> which
19887 contains a short description of the parameters that can be set at
19890 DMA channel for the floppy disk controller used with Ftape
19892 You don't need to specify a value if the following default
19893 settings for the DMA channel are correct:
19895 <<< FC-10/FC-20: 3 >>>
19896 <<< Secondary : 2 >>>
19897 Secondary refers to a secondary FDC controller like the "high speed"
19898 controllers delivered by Seagate or Exabyte or Iomega's Ditto Dash.
19899 Please make sure that the setting for the IO base address
19900 specified here is correct. USE THE MANUAL OF YOUR TAPE DRIVE OR
19901 CONTROLLER CARD TO DETERMINE THE CORRECT SETTING. If you are already
19902 successfully using the tape drive with another operating system then
19903 you definitely should use the same settings for the IO base that has
19904 proven to work with that other OS.
19906 Note that this menu lets you specify only the default setting for
19907 the DMA channel. The hardware configuration can be changed at boot
19908 time (when ftape is compiled into the kernel, i.e. if you said Y to
19909 "Floppy tape drive") or module load time (i.e. if you said M to
19910 "Floppy tape drive").
19912 Please read also the file <file:Documentation/ftape.txt> which
19913 contains a short description of the parameters that can be set at
19916 FDC FIFO Threshold before requesting DMA service
19918 Set the FIFO threshold of the FDC. If this is higher the DMA
19919 controller may serve the FDC after a higher latency time. If this is
19920 lower, fewer DMA transfers occur leading to less bus contention.
19921 You may try to tune this if ftape annoys you with "reduced data
19922 rate because of excessive overrun errors" messages. However, this
19923 doesn't seem to have too much effect.
19925 If unsure, don't touch the initial value, i.e. leave it at "8".
19927 FDC maximum data rate
19928 CONFIG_FT_FDC_MAX_RATE
19929 With some motherboard/FDC combinations ftape will not be able to
19930 run your FDC/tape drive combination at the highest available
19931 speed. If this is the case you'll encounter "reduced data rate
19932 because of excessive overrun errors" messages and lots of retries
19933 before ftape finally decides to reduce the data rate.
19935 In this case it might be desirable to tell ftape beforehand that
19936 it need not try to run the tape drive at the highest available
19937 speed. If unsure, leave this disabled, i.e. leave it at 2000
19940 Direct Rendering Manager (XFree86 DRI support)
19942 Kernel-level support for the Direct Rendering Infrastructure (DRI)
19943 introduced in XFree86 4.0. If you say Y here, you need to select
19944 the module that's right for your graphics card from the list below.
19945 These modules provide support for synchronization, security, and
19946 DMA transfers. Please see <http://dri.sourceforge.net/> for more
19947 details. You should also select and configure AGP
19948 (/dev/agpgart) support.
19950 Build drivers for new (XFree 4.1) DRM
19952 If you set this option, the new DRM version needed by XFree86 4.1
19953 will be used. Otherwise, the old DRM version will be used,
19954 appropriate for XFree86 4.0.
19956 3dfx Banshee/Voodoo3+
19958 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
19959 graphics card. If M is selected, the module will be called tdfx.o.
19963 Choose this option if you have a 3dlabs GMX 2000 graphics card.
19964 If M is selected, the module will be called gamma.o.
19968 Choose this option if you have an ATI Rage 128 graphics card. If M
19969 is selected, the module will be called r128.o. AGP support for
19970 this card is strongly suggested (unless you have a PCI version).
19974 Choose this option if you have an ATI Radeon graphics card. There
19975 are both PCI and AGP versions. You don't need to choose this to
19976 run the Radeon in plain VGA mode. There is a product page at
19977 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
19978 If M is selected, the module will be called radeon.o.
19982 Choose this option if you have an Intel I810 graphics card. If M is
19983 selected, the module will be called i810.o. AGP support is required
19984 for this driver to work.
19986 Intel 830M, 845G, 852GM, 855GM, 865G
19988 Choose this option if you have a system that has Intel 830M, 845G,
19989 852GM, 855GM or 865G integrated graphics. If M is selected, the
19990 module will be called i830.o. AGP support is required for this driver
19993 Matrox G200/G400/G450
19995 Choose this option if you have a Matrox G200, G400 or G450 graphics
19996 card. If M is selected, the module will be called mga.o. AGP
19997 support is required for this driver to work.
19999 3dfx Banshee/Voodoo3+
20001 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
20002 graphics card. If M is selected, the module will be called tdfx.o.
20006 Choose this option if you have a 3dlabs GMX 2000 graphics card.
20007 If M is selected, the module will be called gamma.o.
20011 Choose this option if you have an ATI Rage 128 graphics card. If M
20012 is selected, the module will be called r128.o. AGP support for
20013 this card is strongly suggested (unless you have a PCI version).
20016 CONFIG_DRM40_RADEON
20017 Choose this option if you have an ATI Radeon graphics card. There
20018 are both PCI and AGP versions. You don't need to choose this to
20019 run the Radeon in plain VGA mode. There is a product page at
20020 <http://www.ati.com/na/pages/products/pc/radeon32/index.html>.
20021 If M is selected, the module will be called radeon.o.
20025 Choose this option if you have an Intel I810 graphics card. If M is
20026 selected, the module will be called i810.o. AGP support is required
20027 for this driver to work.
20029 Matrox G200/G400/G450
20031 Choose this option if you have a Matrox G200, G400 or G450 graphics
20032 card. If M is selected, the module will be called mga.o. AGP
20033 support is required for this driver to work.
20035 Creator/Creator3D/Elite3D
20037 Choose this option if you have one of Sun's Creator3D-based graphics
20038 and frame buffer cards. Product page at
20039 <http://www.sun.com/desktop/products/Graphics/creator3d.html>.
20041 MTRR (Memory Type Range Register) support
20043 On Intel P6 family processors (Pentium Pro, Pentium II and later)
20044 the Memory Type Range Registers (MTRRs) may be used to control
20045 processor access to memory ranges. This is most useful if you have
20046 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
20047 allows bus write transfers to be combined into a larger transfer
20048 before bursting over the PCI/AGP bus. This can increase performance
20049 of image write operations 2.5 times or more. Saying Y here creates a
20050 /proc/mtrr file which may be used to manipulate your processor's
20051 MTRRs. Typically the X server should use this.
20053 This code has a reasonably generic interface so that similar
20054 control registers on other processors can be easily supported
20057 The Cyrix 6x86, 6x86MX and M II processors have Address Range
20058 Registers (ARRs) which provide a similar functionality to MTRRs. For
20059 these, the ARRs are used to emulate the MTRRs.
20060 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
20061 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
20062 write-combining. All of these processors are supported by this code
20063 and it makes sense to say Y here if you have one of them.
20065 Saying Y here also fixes a problem with buggy SMP BIOSes which only
20066 set the MTRRs for the boot CPU and not for the secondary CPUs. This
20067 can lead to all sorts of problems, so it's good to say Y here.
20069 You can safely say Y even if your machine doesn't have MTRRs, you'll
20070 just add about 9 KB to your kernel.
20072 See <file:Documentation/mtrr.txt> for more information.
20074 CPU clock frequency of your DEC Alpha
20075 CONFIG_FT_ALPHA_CLOCK
20076 On some DEC Alpha machines the CPU clock frequency cannot be
20077 determined automatically, so you need to specify it here ONLY if
20078 running a DEC Alpha, otherwise this setting has no effect.
20080 Double Talk PC internal speech card support
20082 This driver is for the DoubleTalk PC, a speech synthesizer
20083 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
20084 called the `internal DoubleTalk'. If you want to compile this as a
20085 module ( = code which can be inserted in and removed from the
20086 running kernel whenever you want), say M here and read
20087 <file:Documentation/modules.txt>. The module will be called dtlk.o.
20089 Siemens R3964 serial protocol support
20091 This driver allows synchronous communication with devices using the
20092 Siemens R3964 packet protocol. Unless you are dealing with special
20093 hardware like PLCs, you are unlikely to need this.
20095 To compile this driver as a module ( = code which can be inserted in
20096 and removed from the running kernel whenever you want), say M here
20097 and read <file:Documentation/modules.txt>. The module will be called
20102 Applicom intelligent fieldbus card support
20104 This driver provides the kernel-side support for the intelligent
20105 fieldbus cards made by Applicom International. More information
20106 about these cards can be found on the WWW at the address
20107 <http://www.applicom-int.com/>, or by email from David Woodhouse
20108 <dwmw2@infradead.org>.
20110 To compile this driver as a module ( = code which can be inserted in
20111 and removed from the running kernel whenever you want), say M here
20112 and read <file:Documentation/modules.txt>. The module will be called
20117 Sony Vaio Programmable I/O Control Device support
20119 This driver enables access to the Sony Programmable I/O Control
20120 Device which can be found in many (all ?) Sony Vaio laptops.
20122 If you have one of those laptops, read
20123 <file:Documentation/sonypi.txt>, and say Y or M here.
20125 If you want to compile the driver as a module ( = code which can be
20126 inserted in and removed from the running kernel whenever you want),
20127 say M here and read <file:Documentation/modules.txt>. The module
20128 will be called sonypi.o.
20130 Intel Random Number Generator support
20132 This driver provides kernel-side support for the Random Number
20133 Generator hardware found on Intel i8xx-based motherboards.
20135 Both a character driver, used to read() entropy data, and a timer
20136 function which automatically adds entropy directly into the
20137 kernel pool, are exported by this driver.
20139 To compile this driver as a module ( = code which can be inserted in
20140 and removed from the running kernel whenever you want), say M here
20141 and read <file:Documentation/modules.txt>. The module will be called
20146 Intel/AMD/VIA HW Random Number Generator support
20148 This driver provides kernel-side support for the
20149 Random Number Generator hardware found on Intel i8xx-based motherboards,
20150 AMD 76x-based motherboards, and Via Nehemiah CPUs.
20152 Provides a character driver, used to read() entropy data.
20154 To compile this driver as a module ( = code which can be inserted in
20155 and removed from the running kernel whenever you want), say M here
20156 and read <file:Documentation/modules.txt>. The module will be called
20161 Power Management support
20163 "Power Management" means that parts of your computer are shut
20164 off or put into a power conserving "sleep" mode if they are not
20165 being used. There are two competing standards for doing this: APM
20166 and ACPI. If you want to use either one, say Y here and then also
20167 to the requisite support below.
20169 Power Management is most important for battery powered laptop
20170 computers; if you have a laptop, check out the Linux Laptop home
20172 <http://www.cs.utexas.edu/users/kharker/linux-laptop/> and the
20173 Battery Powered Linux mini-HOWTO, available from
20174 <http://www.tldp.org/docs.html#howto>.
20176 Note that, even if you say N here, Linux on the x86 architecture
20177 will issue the hlt instruction if nothing is to be done, thereby
20178 sending the processor to sleep and saving power.
20182 ACPI/OSPM support for Linux is currently under development. As such,
20183 this support is preliminary and EXPERIMENTAL. Configuring ACPI
20184 support enables kernel interfaces that allow higher level software
20185 (OSPM) to manipulate ACPI defined hardware and software interfaces,
20186 including the evaluation of ACPI control methods. If unsure, choose
20187 N here. Note, this option will enlarge your kernel by about 120K.
20189 This support requires an ACPI compliant platform (hardware/firmware).
20190 If both ACPI and Advanced Power Management (APM) support are
20191 configured, whichever is loaded first shall be used.
20193 This code DOES NOT currently provide a complete OSPM implementation
20194 -- it has not yet reached APM's level of functionality. When fully
20195 implemented, Linux ACPI/OSPM will provide a more robust functional
20196 replacement for legacy configuration and power management
20197 interfaces, including the Plug-and-Play BIOS specification (PnP
20198 BIOS), the Multi-Processor Specification (MPS), and the Advanced
20199 Power Management specification (APM).
20201 Linux support for ACPI/OSPM is based on Intel Corporation's ACPI
20202 Component Architecture (ACPI CA). The latest ACPI CA source code,
20203 documentation, debug builds, and implementation status information
20204 can be downloaded from:
20205 <http://developer.intel.com/technology/iapc/acpi/downloads.htm>.
20207 The ACPI Sourceforge project may also be of interest:
20208 <http://sf.net/projects/acpi/>
20210 Note that "acpi=off" can be used to disable all ACPI code in the kernel.
20212 ACPI kernel configuration manager
20213 CONFIG_ACPI_KERNEL_CONFIG
20214 If you say `Y' here, Linux's ACPI support will use the
20215 hardware-level system descriptions found on IA64 machines.
20217 ACPI Debug Statements
20219 The ACPI driver can optionally report errors with a great deal
20220 of verbosity. Saying Y enables these statements. This will increase
20221 your kernel size by around 50K.
20225 This driver registers for events based on buttons, such as the
20226 power, sleep, and lid switch. In the future, a daemon will read
20227 /proc/acpi/event and perform user-defined actions such as shutting
20228 down the system. Until then, you can cat it, and see output when
20229 a button is pressed.
20231 CONFIG_ACPI_BATTERY
20232 This driver adds support for battery information through
20233 /proc/acpi/battery. If you have a mobile system with a battery,
20237 This driver adds support for ACPI fan devices, allowing user-mode
20238 applications to perform basic fan control (on, off, status).
20240 CONFIG_ACPI_PROCESSOR
20241 This driver installs ACPI as the idle handler for Linux, and uses
20242 ACPI C2 and C3 processor states to save power, on systems that
20247 This driver adds support for the AC Adapter object, which indicates
20248 whether a system is on AC, or not. Typically, only laptops have
20249 this object, since desktops are always on AC.
20251 ACPI Embedded Controller
20253 This driver is required on some systems for the proper operation of
20254 the battery and thermal drivers. If you are compiling for a laptop,
20258 CONFIG_ACPI_THERMAL
20259 This driver handles overheating conditions on laptops. It is HIGHLY
20260 recommended, as your laptop CPU may be damaged without it.
20262 ACPI ASUS/Medion Laptop Extras
20264 This driver provides support for extra features of ACPI-compatible
20265 ASUS laptops. As some of Medion laptops are made by ASUS, it may also
20266 support some Medion laptops (such as 9675 for example). It makes all
20267 the extra buttons generate standard ACPI events that go through
20268 /proc/acpi/events, and (on some models) adds support for changing the
20269 display brightness and output, switching the LCD backlight on and off,
20270 and most importantly, allows you to blink those fancy LEDs intended
20271 for reporting mail and wireless status.
20273 Note: the display switching code is currently considered EXPERIMENTAL,
20274 toying with these values may even lock your machine.
20276 All settings are changed via /proc/acpi/asus directory entries. Owner
20277 and group for these entries can be set with asus_uid and asus_gid
20280 More information and a userspace daemon for handling the extra buttons
20281 at <http://sourceforge.net/projects/acpi4asus/>.
20283 If you have an ACPI-compatible ASUS laptop, say Y or M here. This
20284 driver is still under development, so if your laptop is unsupported or
20285 something works not quite as expected, please use the mailing list
20286 available on the above page (acpi4asus-user@lists.sourceforge.net)
20288 ACPI Toshiba Laptop Extras
20289 CONFIG_ACPI_TOSHIBA
20290 This driver adds support for access to certain system settings
20291 on "legacy free" Toshiba laptops. These laptops can be recognized by
20292 their lack of a BIOS setup menu and APM support.
20294 On these machines, all system configuration is handled through the
20295 ACPI. This driver is required for access to controls not covered
20296 by the general ACPI drivers, such as LCD brightness, video output,
20299 This driver differs from the non-ACPI Toshiba laptop driver (located
20300 under "Processor type and features") in several aspects.
20301 Configuration is accessed by reading and writing text files in the
20302 /proc tree instead of by program interface to /dev. Furthermore, no
20303 power management functions are exposed, as those are handled by the
20304 general ACPI drivers.
20306 More information about this driver is available at
20307 <http://memebeam.org/toys/ToshibaAcpiDriver>.
20309 If you have a legacy free Toshiba laptop (such as the Libretto L1
20312 Advanced Power Management BIOS support
20314 APM is a BIOS specification for saving power using several different
20315 techniques. This is mostly useful for battery powered laptops with
20316 APM compliant BIOSes. If you say Y here, the system time will be
20317 reset after a RESUME operation, the /proc/apm device will provide
20318 battery status information, and user-space programs will receive
20319 notification of APM "events" (e.g. battery status change).
20321 If you select "Y" here, you can disable actual use of the APM
20322 BIOS by passing the "apm=off" option to the kernel at boot time.
20324 Note that the APM support is almost completely disabled for
20325 machines with more than one CPU.
20327 In order to use APM, you will need supporting software. For location
20328 and more information, read <file:Documentation/pm.txt> and the
20329 Battery Powered Linux mini-HOWTO, available from
20330 <http://www.tldp.org/docs.html#howto>.
20332 This driver does not spin down disk drives (see the hdparm(8)
20333 manpage ("man 8 hdparm") for that), and it doesn't turn off
20334 VESA-compliant "green" monitors.
20336 This driver does not support the TI 4000M TravelMate and the ACER
20337 486/DX4/75 because they don't have compliant BIOSes. Many "green"
20338 desktop machines also don't have compliant BIOSes, and this driver
20339 may cause those machines to panic during the boot phase.
20341 Generally, if you don't have a battery in your machine, there isn't
20342 much point in using this driver and you should say N. If you get
20343 random kernel OOPSes or reboots that don't seem to be related to
20344 anything, try disabling/enabling this option (or disabling/enabling
20347 Some other things you should try when experiencing seemingly random,
20350 1) make sure that you have enough swap space and that it is
20352 2) pass the "no-hlt" option to the kernel
20353 3) switch on floating point emulation in the kernel and pass
20354 the "no387" option to the kernel
20355 4) pass the "floppy=nodma" option to the kernel
20356 5) pass the "mem=4M" option to the kernel (thereby disabling
20357 all but the first 4 MB of RAM)
20358 6) make sure that the CPU is not over clocked.
20359 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
20360 8) disable the cache from your BIOS settings
20361 9) install a fan for the video card or exchange video RAM
20362 10) install a better fan for the CPU
20363 11) exchange RAM chips
20364 12) exchange the motherboard.
20366 To compile this driver as a module ( = code which can be inserted in
20367 and removed from the running kernel whenever you want), say M here
20368 and read <file:Documentation/modules.txt>. The module will be called
20371 Ignore USER SUSPEND
20372 CONFIG_APM_IGNORE_USER_SUSPEND
20373 This option will ignore USER SUSPEND requests. On machines with a
20374 compliant APM BIOS, you want to say N. However, on the NEC Versa M
20375 series notebooks, it is necessary to say Y because of a BIOS bug.
20377 Enable APM at boot time
20378 CONFIG_APM_DO_ENABLE
20379 Enable APM features at boot time. From page 36 of the APM BIOS
20380 specification: "When disabled, the APM BIOS does not automatically
20381 power manage devices, enter the Standby State, enter the Suspend
20382 State, or take power saving steps in response to CPU Idle calls."
20383 This driver will make CPU Idle calls when Linux is idle (unless this
20384 feature is turned off -- see "Do CPU IDLE calls", below). This
20385 should always save battery power, but more complicated APM features
20386 will be dependent on your BIOS implementation. You may need to turn
20387 this option off if your computer hangs at boot time when using APM
20388 support, or if it beeps continuously instead of suspending. Turn
20389 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
20390 T400CDT. This is off by default since most machines do fine without
20393 Make CPU Idle calls when idle
20394 CONFIG_APM_CPU_IDLE
20395 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
20396 On some machines, this can activate improved power savings, such as
20397 a slowed CPU clock rate, when the machine is idle. These idle calls
20398 are made after the idle loop has run for some length of time (e.g.,
20399 333 mS). On some machines, this will cause a hang at boot time or
20400 whenever the CPU becomes idle. (On machines with more than one CPU,
20401 this option does nothing.)
20403 Enable console blanking using APM
20404 CONFIG_APM_DISPLAY_BLANK
20405 Enable console blanking using the APM. Some laptops can use this to
20406 turn off the LCD backlight when the screen blanker of the Linux
20407 virtual console blanks the screen. Note that this is only used by
20408 the virtual console screen blanker, and won't turn off the backlight
20409 when using the X Window system. This also doesn't have anything to
20410 do with your VESA-compliant power-saving monitor. Further, this
20411 option doesn't work for all laptops -- it might not turn off your
20412 backlight at all, or it might print a lot of errors to the console,
20413 especially if you are using gpm.
20415 RTC stores time in GMT
20416 CONFIG_APM_RTC_IS_GMT
20417 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
20418 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
20421 It is in fact recommended to store GMT in your RTC, because then you
20422 don't have to worry about daylight savings time changes. The only
20423 reason not to use GMT in your RTC is if you also run a broken OS
20424 that doesn't understand GMT.
20426 Allow interrupts during APM BIOS calls
20427 CONFIG_APM_ALLOW_INTS
20428 Normally we disable external interrupts while we are making calls to
20429 the APM BIOS as a measure to lessen the effects of a badly behaving
20430 BIOS implementation. The BIOS should reenable interrupts if it
20431 needs to. Unfortunately, some BIOSes do not -- especially those in
20432 many of the newer IBM Thinkpads. If you experience hangs when you
20433 suspend, try setting this to Y. Otherwise, say N.
20435 Use real mode APM BIOS call to power off
20436 CONFIG_APM_REAL_MODE_POWER_OFF
20437 Use real mode APM BIOS calls to switch off the computer. This is
20438 a work-around for a number of buggy BIOSes. Switch this option on if
20439 your computer crashes instead of powering off properly.
20441 Watchdog Timer Support
20443 If you say Y here (and to one of the following options) and create a
20444 character special file /dev/watchdog with major number 10 and minor
20445 number 130 using mknod ("man mknod"), you will get a watchdog, i.e.:
20446 subsequently opening the file and then failing to write to it for
20447 longer than 1 minute will result in rebooting the machine. This
20448 could be useful for a networked machine that needs to come back
20449 online as fast as possible after a lock-up. There's both a watchdog
20450 implementation entirely in software (which can sometimes fail to
20451 reboot the machine) and a driver for hardware watchdog boards, which
20452 are more robust and can also keep track of the temperature inside
20453 your computer. For details, read <file:Documentation/watchdog.txt>
20454 in the kernel source.
20456 The watchdog is usually used together with the watchdog daemon
20457 which is available from
20458 <ftp://ibiblio.org/pub/Linux/system/daemons/watchdog/>. This daemon can
20459 also monitor NFS connections and can reboot the machine when the process
20464 Disable watchdog shutdown on close
20465 CONFIG_WATCHDOG_NOWAYOUT
20466 The default watchdog behaviour (which you get if you say N here) is
20467 to stop the timer if the process managing it closes the file
20468 /dev/watchdog. It's always remotely possible that this process might
20469 get killed. If you say Y here, the watchdog cannot be stopped once
20470 it has been started.
20474 If you have a WDT500P or WDT501P watchdog board, say Y here,
20475 otherwise N. It is not possible to probe for this board, which means
20476 that you have to inform the kernel about the IO port and IRQ using
20477 the "wdt=" kernel option (try "man bootparam" or see the
20478 documentation of your boot loader (lilo or loadlin) about how to
20479 pass options to the kernel at boot time).
20481 If you want to compile this as a module ( = code which can be
20482 inserted in and removed from the running kernel whenever you want),
20483 say M here and read <file:Documentation/modules.txt>. The module
20484 will be called wdt.o.
20486 WDT PCI Watchdog timer
20488 If you have a PCI WDT500/501 watchdog board, say Y here, otherwise
20489 N. It is not possible to probe for this board, which means that you
20490 have to inform the kernel about the IO port and IRQ using the "wdt="
20491 kernel option (try "man bootparam" or see the documentation of your
20492 boot loader (lilo or loadlin) about how to pass options to the
20493 kernel at boot time).
20495 If you want to compile this as a module ( = code which can be
20496 inserted in and removed from the running kernel whenever you want),
20497 say M here and read <file:Documentation/modules.txt>. The module
20498 will be called wdt_pci.o.
20502 Saying Y here and creating a character special file /dev/temperature
20503 with major number 10 and minor number 131 ("man mknod") will give
20504 you a thermometer inside your computer: reading from
20505 /dev/temperature yields one byte, the temperature in degrees
20506 Fahrenheit. This works only if you have a WDT501P watchdog board
20511 Enable the Fan Tachometer on the WDT501. Only do this if you have a
20512 fan tachometer actually set up.
20515 CONFIG_SOFT_WATCHDOG
20516 A software monitoring watchdog. This will fail to reboot your system
20517 from some situations that the hardware watchdog will recover
20518 from. Equally it's a lot cheaper to install.
20520 This driver is also available as a module ( = code which can be
20521 inserted in and removed from the running kernel whenever you want).
20522 If you want to compile it as a module, say M here and read
20523 <file:Documentation/modules.txt>. The module will be called
20526 Berkshire Products PC Watchdog
20528 This is the driver for the Berkshire Products PC Watchdog card.
20529 This card simply watches your kernel to make sure it doesn't freeze,
20530 and if it does, it reboots your computer after a certain amount of
20531 time. This driver is like the WDT501 driver but for different
20532 hardware. Please read <file:Documentation/pcwd-watchdog.txt>. The PC
20533 watchdog cards can be ordered from <http://www.berkprod.com/>.
20535 This driver is also available as a module ( = code which can be
20536 inserted in and removed from the running kernel whenever you want).
20537 The module is called pcwd.o. If you want to compile it as a module,
20538 say M here and read <file:Documentation/modules.txt>.
20540 Most people will say N.
20542 Acquire SBC Watchdog Timer
20544 This is the driver for the hardware watchdog on the PSC-6x86 Single
20545 Board Computer produced by Acquire Inc (and others). This watchdog
20546 simply watches your kernel to make sure it doesn't freeze, and if
20547 it does, it reboots your computer after a certain amount of time.
20549 This driver is like the WDT501 driver but for different hardware.
20550 This driver is also available as a module ( = code which can be
20551 inserted in and removed from the running kernel whenever you want).
20552 The module is called pscwdt.o. If you want to compile it as a
20553 module, say M here and read <file:Documentation/modules.txt>. Most
20556 Advantech SBC Watchdog Timer
20557 CONFIG_ADVANTECH_WDT
20558 If you are configuring a Linux kernel for the Advantech single-board
20559 computer, say `Y' here to support its built-in watchdog timer
20560 feature. See the help for CONFIG_WATCHDOG for discussion.
20562 ALi M7101 Watchdog Timer
20563 CONFIG_ALIM7101_WDT
20564 This is the driver for the hardware watchdog on the ALi M7101 PMU
20565 as used in the x86 Cobalt servers.
20567 This driver is also available as a module ( = code which can be
20568 inserted in and removed from the running kernel whenever you want).
20569 The module is called alim7101_wdt.o. If you want to compile it as a
20570 module, say M here and read <file:Documentation/modules.txt>. Most
20573 IB700 SBC Watchdog Timer
20575 This is the driver for the hardware watchdog on the IB700 Single
20576 Board Computer produced by TMC Technology (www.tmc-uk.com). This watchdog
20577 simply watches your kernel to make sure it doesn't freeze, and if
20578 it does, it reboots your computer after a certain amount of time.
20580 This driver is like the WDT501 driver but for slightly different hardware.
20582 This driver is also available as a module ( = code which can be
20583 inserted in and removed from the running kernel whenever you want).
20584 The module is called ib700wdt.o. If you want to compile it as a
20585 module, say M here and read Documentation/modules.txt. Most people
20590 This is a driver for the Mixcom hardware watchdog cards. This
20591 watchdog simply watches your kernel to make sure it doesn't freeze,
20592 and if it does, it reboots your computer after a certain amount of
20595 This driver is also available as a module ( = code which can be
20596 inserted in and removed from the running kernel whenever you want).
20597 The module is called mixcomwd.o. If you want to compile it as a
20598 module, say M here and read <file:Documentation/modules.txt>. Most
20603 If you are using a ZF Micro MachZ processor, say Y here, otherwise
20604 N. This is the driver for the watchdog timer builtin on that
20605 processor using ZF-Logic interface. This watchdog simply watches
20606 your kernel to make sure it doesn't freeze, and if it does, it
20607 reboots your computer after a certain amount of time.
20609 This driver is also available as a module ( = code which can be
20610 inserted in and removed from the running kernel whenever you want).
20611 The module is called machzwd.o. If you want to compile it as a
20612 module, say M here and read <file:Documentation/modules.txt>.
20615 This is a driver for National Semiconductor PC87307/PC97307 hardware
20616 watchdog cards as found on the SC1200. This watchdog is mainly used
20617 for power management purposes and can be used to power down the device
20618 during inactivity periods (includes interrupt activity monitoring).
20620 This driver is also available as a module ( = code which can be
20621 inserted in and removed from the running kernel whenever you want).
20622 The module is called sc1200wdt.o. If you want to compile it as a
20623 module, say M here and read <file:Documentation/modules.txt>. Most
20628 This driver adds watchdog support for the integrated watchdog in the
20629 SuperH 3, 4 and 5 processors. If you have one of these processors, say
20630 Y, otherwise say N.
20632 This driver is also available as a module ( = code which can be
20633 inserted in and removed from the running kernel whenever you want).
20634 The module is called shwdt.o. If you want to compile it as a module,
20635 say M here and read Documentation/modules.txt.
20637 Wafer 5823 Watchdog
20639 This is a driver for the hardware watchdog on the ICP Wafer 5823
20640 Single Board Computer (and probably other similar models).
20642 This driver is also available as a module ( = code which can be
20643 inserted in and removed from the running kernel whenever you want).
20644 If you want to compile it as a module, say M here and read
20645 <file:Documentation/modules.txt>. The module will be called
20648 Machine Check Exception
20650 Machine Check Exception support allows the processor to notify the
20651 kernel if it detects a problem (e.g. overheating, component failure).
20652 The action the kernel takes depends on the severity of the problem,
20653 ranging from a warning message on the console, to halting the machine.
20654 You can safely select this on machines that do not support this feature.
20656 For pentium machines the mce support defaults to off as the mainboard
20657 support is not always present. You must activate it as a boot option.
20659 Toshiba Laptop support
20661 This adds a driver to safely access the System Management Mode of
20662 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
20663 not work on models with a Phoenix BIOS. The System Management Mode
20664 is used to set the BIOS and power saving options on Toshiba portables.
20666 For information on utilities to make use of this driver see the
20667 Toshiba Linux utilities web site at:
20668 <http://www.buzzard.org.uk/toshiba/>.
20670 This driver is also available as a module ( = code which can be
20671 inserted in and removed from the running kernel whenever you want).
20672 If you want to compile it as a module, say M here and read
20673 <file:Documentation/modules.txt>. The module will be called
20676 Say Y if you intend to run this kernel on a Toshiba portable.
20679 Dell laptop support
20681 This adds a driver to safely access the System Management Mode
20682 of the CPU on the Dell Inspiron and Latitude laptops. The System
20683 Management Mode is used to read cpu temperature, cooling fan
20684 status and Fn-keys status on Dell laptops. It can also be used
20685 to switch the fans on and off.
20687 The driver has been developed and tested on an Inspiron 8000
20688 but it should work on any Dell Inspiron or Latitude laptop.
20689 You can force loading on unsupported models by passing the
20690 parameter `force=1' to the module. Use at your own risk.
20692 This driver is also available as a module ( = code which can be
20693 inserted in and removed from the running kernel whenever you want).
20694 If you want to compile it as a module, say M here and read
20695 <file:Documentation/modules.txt>. The module will be called
20698 For more information on this driver and for utilities that make
20699 use of the module see the I8K Linux Utilities web site at:
20700 <http://www.debian.org/~dz/i8k/>.
20702 Say Y if you intend to run this kernel on a Dell laptop.
20705 /dev/cpu/microcode - Intel IA32 CPU microcode support
20707 If you say Y here and also to "/dev file system support" in the
20708 'File systems' section, you will be able to update the microcode on
20709 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
20710 Pentium III, Pentium 4, Xeon etc. You will obviously need the
20711 actual microcode binary data itself which is not shipped with the
20714 For latest news and information on obtaining all the required
20715 ingredients for this driver, check:
20716 <http://www.urbanmyth.org/microcode/>.
20718 This driver is also available as a module ( = code which can be
20719 inserted in and removed from the running kernel whenever you want).
20720 The module will be called microcode.o. If you want to compile it as
20721 a module, say M here and read <file:Documentation/modules.txt>. If
20722 you use modprobe or kmod you may also want to add the line
20723 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
20725 /dev/cpu/*/msr - Model-specific register support
20727 This device gives privileged processes access to the x86
20728 Model-Specific Registers (MSRs). It is a character device with
20729 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
20730 MSR accesses are directed to a specific CPU on multi-processor
20733 This driver is also available as a module ( = code which can be
20734 inserted in and removed from the running kernel whenever you want).
20735 If you want to compile it as a module, say M here and read
20736 <file:Documentation/modules.txt>. The module will be called
20739 /dev/cpu/*/cpuid - CPU information support
20741 This device gives processes access to the x86 CPUID instruction to
20742 be executed on a specific processor. It is a character device
20743 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
20746 This driver is also available as a module ( = code which can be
20747 inserted in and removed from the running kernel whenever you want).
20748 If you want to compile it as a module, say M here and read
20749 <file:Documentation/modules.txt>. The module will be called
20752 x86 BIOS Enhanced Disk Drive support
20754 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
20755 Services real mode BIOS calls to determine which disk
20756 BIOS tries boot from. This information is then exported via /proc.
20758 This option is experimental, but believed to be safe,
20759 and most disk controller BIOS vendors do not yet implement this feature.
20761 SBC-60XX Watchdog Timer
20763 This driver can be used with the watchdog timer found on some
20764 single board computers, namely the 6010 PII based computer.
20765 It may well work with other cards. It reads port 0x443 to enable
20766 and re-set the watchdog timer, and reads port 0x45 to disable
20767 the watchdog. If you have a card that behave in similar ways,
20768 you can probably make this driver work with your card as well.
20770 You can compile this driver directly into the kernel, or use
20771 it as a module. The module will be called sbc60xxwdt.o.
20773 Eurotech CPU-1220/1410 Watchdog Timer
20774 CONFIG_EUROTECH_WDT
20775 Enable support for the watchdog timer on the Eurotech CPU-1220 and
20776 CPU-1410 cards. These are PC/104 SBCs. Spec sheets and product
20777 information are at <http://www.eurotech.it/>.
20779 W83877F Watchdog Timer
20781 This is the driver for the hardware watchdog on the W83877F chipset
20782 as used in EMACS PC-104 motherboards (and may work on others). This
20783 watchdog simply watches your kernel to make sure it doesn't freeze,
20784 and if it does, it reboots your computer after a certain amount of
20787 You can compile this driver directly into the kernel, or use
20788 it as a module. The module will be called w83877f_wdt.o.
20790 SC520 (AMD Elan) Watchdog Timer
20792 This is the driver for the hardware watchdog built in to the
20793 AMD "Elan" SC520 microcomputer commonly used in embedded systems.
20794 This watchdog simply watches your kernel to make sure it doesn't
20795 freeze, and if it does, it reboots your computer after a certain
20798 You can compile this driver directly into the kernel, or use
20799 it as a module. The module will be called sc520_wdt.o.
20801 Enhanced Real Time Clock Support
20803 If you say Y here and create a character special file /dev/rtc with
20804 major number 10 and minor number 135 using mknod ("man mknod"), you
20805 will get access to the real time clock (or hardware clock) built
20806 into your computer.
20808 Every PC has such a clock built in. It can be used to generate
20809 signals from as low as 1Hz up to 8192Hz, and can also be used
20810 as a 24 hour alarm. It reports status information via the file
20811 /proc/driver/rtc and its behaviour is set by various ioctls on
20814 If you run Linux on a multiprocessor machine and said Y to
20815 "Symmetric Multi Processing" above, you should say Y here to read
20816 and set the RTC in an SMP compatible fashion.
20818 If you think you have a use for such a device (such as periodic data
20819 sampling), then say Y here, and read <file:Documentation/rtc.txt>
20822 This driver is also available as a module ( = code which can be
20823 inserted in and removed from the running kernel whenever you want).
20824 The module is called rtc.o. If you want to compile it as a module,
20825 say M here and read <file:Documentation/modules.txt>.
20827 Generic MIPS RTC Support
20830 If your machine is a MIPS machine, this option provides a simple,
20831 generic RTC driver for /dev/rtc device. It only implements two IOCTL
20832 operations of the standard PC RTC driver: RTC_RD_TIME and RTC_SET_TIME.
20833 It is sufficient to run hwclock program.
20835 You should say Y here if there is no machine-specific RTC driver for your
20836 MIPS machine but you do want a simple RTC driver for your RTC device.
20838 Generic Real Time Clock Support
20840 If you say Y here and create a character special file /dev/rtc with
20841 major number 10 and minor number 135 using mknod ("man mknod"), you
20842 will get access to the real time clock (or hardware clock) built
20843 into your computer.
20845 In 2.4 and later kernels this is the only way to set and get rtc
20846 time on m68k systems so it is highly recommended.
20848 It reports status information via the file /proc/driver/rtc and its
20849 behaviour is set by various ioctls on /dev/rtc. If you enable the
20850 "extended RTC operation" below it will also provide an emulation
20851 for RTC_UIE which is required by some programs and may improve
20852 precision in some cases.
20854 This driver is also available as a module ( = code which can be
20855 inserted in and removed from the running kernel whenever you want).
20856 The module is called genrtc.o. If you want to compile it as a module,
20857 say M here and read <file:Documentation/modules.txt>. To load the
20858 module automatically add 'alias char-major-10-135 genrtc' to your
20861 Extended RTC operation
20863 Provides an emulation for RTC_UIE which is required by some programs
20864 and may improve precision of the generic RTC support in some cases.
20866 Tadpole ANA H8 Support
20868 The Hitachi H8/337 is a microcontroller used to deal with the power
20869 and thermal environment. If you say Y here, you will be able to
20870 communicate with it via a character special device.
20876 If you say Y here and create a character special file /dev/nvram
20877 with major number 10 and minor number 144 using mknod ("man mknod"),
20878 you get read and write access to the extra bytes of non-volatile
20879 memory in the real time clock (RTC), which is contained in every PC
20880 and most Ataris. The actual number of bytes varies, depending on the
20881 nvram in the system, but is usually 114 (128-14 for the RTC).
20883 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
20884 on Ataris. /dev/nvram may be used to view settings there, or to
20885 change them (with some utility). It could also be used to frequently
20886 save a few bits of very important data that may not be lost over
20887 power-off and for which writing to disk is too insecure. Note
20888 however that most NVRAM space in a PC belongs to the BIOS and you
20889 should NEVER idly tamper with it. See Ralf Brown's interrupt list
20890 for a guide to the use of CMOS bytes by your BIOS.
20892 On Atari machines, /dev/nvram is always configured and does not need
20895 This driver is also available as a module ( = code which can be
20896 inserted in and removed from the running kernel whenever you want).
20897 The module will be called nvram.o. If you want to compile it as a
20898 module, say M here and read <file:Documentation/modules.txt>.
20902 If you have a joystick, 6dof controller, gamepad, steering wheel,
20903 weapon control system or something like that you can say Y here to
20904 enable generic support for these controllers. You will also need to
20905 say Y or M to at least one of the hardware specific drivers. This
20906 will make the controllers available as /dev/input/jsX devices.
20907 Please read the file <file:Documentation/input/joystick.txt> which
20908 contains more information and the location of the joystick package
20912 CONFIG_INPUT_GAMEPORT
20913 Gameport support is for the standard 15-pin PC gameport. If you
20914 have a joystick, gamepad, gameport card, a soundcard with a gameport
20915 or anything else that uses the gameport, say Y or M here and also to
20916 at least one of the hardware specific drivers.
20917 Please read the file <file:Documentation/input/joystick.txt> which
20918 contains more information and the location of the joystick package
20919 that you'll need if you use the gameport with a joystick.
20921 This driver is also available as a module ( = code which can be
20922 inserted in and removed from the running kernel whenever you want).
20923 The module will be called gameport.o. If you want to compile it as
20924 a module, say M here and read <file:Documentation/modules.txt>.
20926 Classic ISA/PnP gameports
20928 Say Y here if you have an ISA or PnP gameport.
20929 For more information on how to use the driver please read
20930 <file:Documentation/input/joystick.txt>.
20932 This driver is also available as a module ( = code which can be
20933 inserted in and removed from the running kernel whenever you want).
20934 The module will be called ns558.o. If you want to compile it as a
20935 module, say M here and read <file:Documentation/modules.txt>.
20937 PDPI Lightning 4 gamecard
20938 CONFIG_INPUT_LIGHTNING
20939 Say Y here if you have a PDPI Lightning 4 gamecard. For more
20940 information on how to use the driver please read
20941 <file:Documentation/input/joystick.txt>.
20943 This driver is also available as a module ( = code which can be
20944 inserted in and removed from the running kernel whenever you want).
20945 The module will be called lightning.o. If you want to compile it as
20946 a module, say M here and read <file:Documentation/modules.txt>.
20948 Crystal SoundFusion gameports
20949 CONFIG_INPUT_CS461X
20950 Say Y here if you have a Cirrus CS461x aka "Crystal SoundFusion"
20951 PCI audio accelerator. A product page for the CS4614 is at
20952 <http://www.cirrus.com/design/products/overview/index.cfm?ProductID=40>.
20954 This driver is also available as a module ( = code which can be
20955 inserted in and removed from the running kernel whenever you want).
20956 The module will be called cs461x.o. If you want to compile it as a
20957 module, say M here and read <file:Documentation/modules.txt>.
20959 Aureal Vortex, Trident 4DWave, and ALi 5451 gameports
20960 CONFIG_INPUT_PCIGAME
20961 Say Y here if you have a Trident 4DWave DX/NX or Aureal Vortex 1/2
20962 card or an ALi 5451 chip on your motherboard. For more information
20963 on how to use the driver please read
20964 <file:Documentation/input/joystick.txt>.
20966 This driver is also available as a module ( = code which can be
20967 inserted in and removed from the running kernel whenever you want).
20968 The module will be called pcigame.o. If you want to compile it as a
20969 module, say M here and read <file:Documentation/modules.txt>.
20971 SoundBlaster Live! gameports
20972 CONFIG_INPUT_EMU10K1
20973 Say Y here if you have a SoundBlaster Live! card and want to use
20974 its gameport. For more information on how to use the driver
20975 please read <file:Documentation/input/joystick.txt>.
20977 This driver is also available as a module ( = code which can be
20978 inserted in and removed from the running kernel whenever you want).
20979 The module will be called emu10k1-gp.o. If you want to compile it as
20980 a module, say M here and read <file:Documentation/modules.txt>.
20982 Classic PC analog joysticks and gamepads
20983 CONFIG_INPUT_ANALOG
20984 Say Y here if you have a controller that connects to the PC
20985 gameport. This supports many different types, including joysticks
20986 with throttle control, with rudders, or with extensions like
20987 additional hats and buttons compatible with CH Flightstick Pro,
20988 ThrustMaster FCS, 6 and 8 button gamepads, or Saitek Cyborg
20989 joysticks. For more information on how to use the driver please
20990 read <file:Documentation/input/joystick.txt>.
20992 This driver is also available as a module ( = code which can be
20993 inserted in and removed from the running kernel whenever you want).
20994 The module will be called analog.o. If you want to compile it as a
20995 module, say M here and read <file:Documentation/modules.txt>.
20997 Assassin 3D and MadCatz Panther devices
20999 Say Y here if you have an FPGaming or MadCatz controller using the
21000 A3D protocol over the PC gameport. For more information on how to
21001 use the driver please read <file:Documentation/input/joystick.txt>.
21003 This driver is also available as a module ( = code which can be
21004 inserted in and removed from the running kernel whenever you want).
21005 The module will be called a3d.o. If you want to compile it as a
21006 module, say M here and read <file:Documentation/modules.txt>.
21008 Logitech ADI digital joysticks and gamepads
21010 Say Y here if you have a Logitech controller using the ADI
21011 protocol over the PC gameport. For more information on how to use
21012 the driver please read <file:Documentation/input/joystick.txt>.
21014 This driver is also available as a module ( = code which can be
21015 inserted in and removed from the running kernel whenever you want).
21016 The module will be called adi.o. If you want to compile it as a
21017 module, say M here and read <file:Documentation/modules.txt>.
21019 Creative Labs Blaster Cobra gamepad
21021 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
21022 For more information on how to use the driver please read
21023 <file:Documentation/input/joystick.txt>.
21025 This driver is also available as a module ( = code which can be
21026 inserted in and removed from the running kernel whenever you want).
21027 The module will be called cobra.o. If you want to compile it as a
21028 module, say M here and read <file:Documentation/modules.txt>.
21030 Genius Flight2000 Digital joysticks and gamepads
21032 Say Y here if you have a Genius Flight2000 or MaxFighter digitally
21033 communicating joystick or gamepad. For more information on how to
21034 use the driver please read <file:Documentation/input/joystick.txt>.
21036 This driver is also available as a module ( = code which can be
21037 inserted in and removed from the running kernel whenever you want).
21038 The module will be called gf2k.o. If you want to compile it as a
21039 module, say M here and read <file:Documentation/modules.txt>.
21041 Gravis GrIP joysticks and gamepads
21043 Say Y here if you have a Gravis controller using the GrIP protocol
21044 over the PC gameport. For more information on how to use the driver
21045 please read <file:Documentation/input/joystick.txt>.
21047 This driver is also available as a module ( = code which can be
21048 inserted in and removed from the running kernel whenever you want).
21049 The module will be called grip.o. If you want to compile it as a
21050 module, say M here and read <file:Documentation/modules.txt>.
21052 InterAct digital joysticks and gamepads
21053 CONFIG_INPUT_INTERACT
21054 Say Y hereif you have an InterAct gameport or joystick
21055 communicating digitally over the gameport. For more information on
21056 how to use the driver please read <file:Documentation/input/joystick.txt>.
21058 This driver is also available as a module ( = code which can be
21059 inserted in and removed from the running kernel whenever you want).
21060 The module will be called interact.o. If you want to compile it as
21061 a module, say M here and read <file:Documentation/modules.txt>.
21063 ThrustMaster DirectConnect joysticks and gamepads
21065 Say Y here if you have a ThrustMaster controller using the
21066 DirectConnect (BSP) protocol over the PC gameport. For more
21067 information on how to use the driver please read
21068 <file:Documentation/input/joystick.txt>.
21070 This driver is also available as a module ( = code which can be
21071 inserted in and removed from the running kernel whenever you want).
21072 The module will be called tmdc.o. If you want to compile it as a
21073 module, say M here and read <file:Documentation/modules.txt>.
21075 Microsoft SideWinder digital joysticks and gamepads
21076 CONFIG_INPUT_SIDEWINDER
21077 Say Y here if you have a Microsoft controller using the Digital
21078 Overdrive protocol over PC gameport. For more information on how to
21079 use the driver please read <file:Documentation/input/joystick.txt>.
21081 This driver is also available as a module ( = code which can be
21082 inserted in and removed from the running kernel whenever you want).
21083 The module will be called sidewinder.o. If you want to compile it
21084 as a module, say M here and read <file:Documentation/modules.txt>.
21086 Serial port device support
21088 Say Y here and to the Serial port input line discipline option if
21089 you plan to use a joystick that communicates over the serial (COM)
21090 port. For more information on how to use the driver please read
21091 <file:Documentation/input/joystick.txt>.
21093 This driver is also available as a module ( = code which can be
21094 inserted in and removed from the running kernel whenever you want).
21095 The module will be called sidewinder.o. If you want to compile it
21096 as a module, say M here and read <file:Documentation/modules.txt>.
21098 Serial port input line discipline
21099 CONFIG_INPUT_SERPORT
21100 Say Y here if you plan to use a joystick that communicates over the
21101 serial (COM) port. For more information on how to use the driver
21102 please read <file:Documentation/input/joystick.txt>.
21104 This driver is also available as a module ( = code which can be
21105 inserted in and removed from the running kernel whenever you want).
21106 The module will be called serport.o. If you want to compile it as a
21107 module, say M here and read <file:Documentation/modules.txt>.
21109 Logitech WingMan Warrior joystick
21110 CONFIG_INPUT_WARRIOR
21111 Say Y here if you have a Logitech WingMan Warrior joystick connected
21112 to your computer's serial port. For more information on how to use
21113 the driver please read <file:Documentation/input/joystick.txt>.
21115 This driver is also available as a module ( = code which can be
21116 inserted in and removed from the running kernel whenever you want).
21117 The module will be called warrior.o. If you want to compile it as a
21118 module, say M here and read <file:Documentation/modules.txt>.
21120 LogiCad3d Magellan/SpaceMouse 6dof controller
21121 CONFIG_INPUT_MAGELLAN
21122 Say Y here if you have a Magellan or Space Mouse 6DOF controller
21123 connected to your computer's serial port. For more information on
21124 how to use the driver please read <file:Documentation/input/joystick.txt>.
21126 This driver is also available as a module ( = code which can be
21127 inserted in and removed from the running kernel whenever you want).
21128 The module will be called magellan.o. If you want to compile it as
21129 a module, say M here and read <file:Documentation/modules.txt>.
21131 SpaceTec SpaceOrb/Avenger 6dof controller
21132 CONFIG_INPUT_SPACEORB
21133 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
21134 controller connected to your computer's serial port. For more
21135 information on how to use the driver please read
21136 <file:Documentation/input/joystick.txt>.
21138 This driver is also available as a module ( = code which can be
21139 inserted in and removed from the running kernel whenever you want).
21140 The module will be called spaceorb.o. If you want to compile it as
21141 a module, say M here and read <file:Documentation/modules.txt>.
21143 SpaceTec SpaceBall 4000 FLX 6dof controller
21144 CONFIG_INPUT_SPACEBALL
21145 Say Y here if you have a SpaceTec SpaceBall 4000 FLX controller
21146 connected to your computer's serial port. For more information on
21147 how to use the driver please read <file:Documentation/input/joystick.txt>.
21149 This driver is also available as a module ( = code which can be
21150 inserted in and removed from the running kernel whenever you want).
21151 The module will be called spaceball.o. If you want to compile it as
21152 a module, say M here and read <file:Documentation/modules.txt>.
21154 Gravis Stinger gamepad
21155 CONFIG_INPUT_STINGER
21156 Say Y here if you have a Gravis Stinger connected to one of your
21157 serial ports. For more information on how to use the driver please
21158 read <file:Documentation/input/joystick.txt>.
21160 This driver is also available as a module ( = code which can be
21161 inserted in and removed from the running kernel whenever you want).
21162 The module will be called stinger.o. If you want to compile it as a
21163 module, say M here and read <file:Documentation/modules.txt>.
21165 I-Force joysticks/wheels
21166 CONFIG_INPUT_IFORCE_232
21167 Say Y here if you have an I-Force joystick or steering wheel
21168 connected to your serial (COM) port. For more information on how
21169 to use the driver please read <file:Documentation/input/joystick.txt>.
21171 This driver is also available as a module ( = code which can be
21172 inserted in and removed from the running kernel whenever you want).
21173 The module will be called iforce.o. If you want to compile it as a
21174 module, say M here and read <file:Documentation/modules.txt>.
21176 I-Force joysticks/wheels
21177 CONFIG_INPUT_IFORCE_USB
21178 Say Y here if you have an I-Force joystick or steering wheel
21179 connected to your USB port. For more information on how to use the
21180 driver please read <file:Documentation/input/joystick.txt>.
21182 This driver is also available as a module ( = code which can be
21183 inserted in and removed from the running kernel whenever you want).
21184 The module will be called iforce.o. If you want to compile it as a
21185 module, say M here and read <file:Documentation/modules.txt>.
21187 Multisystem, Sega Genesis, Saturn joysticks and gamepads
21189 Say Y here if you have a Sega Master System gamepad, Sega Genesis
21190 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
21191 Commodore, Amstrad CPC joystick connected to your parallel port.
21192 For more information on how to use the driver please read
21193 <file:Documentation/input/joystick.txt> and
21194 <file:Documentation/input/joystick-parport.txt>.
21196 This driver is also available as a module ( = code which can be
21197 inserted in and removed from the running kernel whenever you want).
21198 The module will be called db9.o. If you want to compile it as a
21199 module, say M here and read <file:Documentation/modules.txt>.
21201 Multisystem, NES, SNES, N64, PSX joysticks and gamepads
21202 CONFIG_INPUT_GAMECON
21203 Say Y here if you have a Nintendo Entertainment System gamepad,
21204 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
21205 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
21206 Commodore, Amstrad CPC joystick connected to your parallel port.
21207 For more information on how to use the driver please read
21208 <file:Documentation/input/joystick.txt> and
21209 <file:Documentation/input/joystick-parport.txt>.
21211 This driver is also available as a module ( = code which can be
21212 inserted in and removed from the running kernel whenever you want).
21213 The module will be called gamecon.o. If you want to compile it as a
21214 module, say M here and read <file:Documentation/modules.txt>.
21216 Multisystem joysticks via TurboGraFX device
21217 CONFIG_INPUT_TURBOGRAFX
21218 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
21219 and want to use it with Multisystem -- Atari, Amiga, Commodore,
21220 Amstrad CPC joystick. For more information on how to use the driver
21221 please read <file:Documentation/input/joystick.txt> and
21222 <file:Documentation/input/joystick-parport.txt>.
21224 This driver is also available as a module ( = code which can be
21225 inserted in and removed from the running kernel whenever you want).
21226 The module will be called turbografx.o. If you want to compile it
21227 as a module, say M here and read <file:Documentation/modules.txt>.
21230 CONFIG_INPUT_AMIJOY
21231 Say Y here if you have an Amiga with a digital joystick connected
21232 to it. For more information on how to use the driver please read
21233 <file:Documentation/input/joystick.txt>.
21235 This driver is also available as a module ( = code which can be
21236 inserted in and removed from the running kernel whenever you want).
21237 The module will be called joy-amiga.o. If you want to compile it as
21238 a module, say M here and read <file:Documentation/modules.txt>.
21240 Atomwide serial port support
21241 CONFIG_ATOMWIDE_SERIAL
21242 If you have an Atomwide Serial card for an Acorn system, say Y to
21243 this option. The driver can handle 1, 2, or 3 port cards.
21246 Dual serial port support
21247 CONFIG_DUALSP_SERIAL
21248 If you have the Serial Port's dual serial card for an Acorn system,
21249 say Y to this option. If unsure, say N.
21253 If you say Y here and create a character device node /dev/nwbutton
21254 with major and minor numbers 10 and 158 ("man mknod"), then every
21255 time the orange button is pressed a number of times, the number of
21256 times the button was pressed will be written to that device.
21258 This is most useful for applications, as yet unwritten, which
21259 perform actions based on how many times the button is pressed in a
21262 Do not hold the button down for too long, as the driver does not
21263 alter the behaviour of the hardware reset circuitry attached to the
21264 button; it will still execute a hard reset if the button is held
21265 down for longer than approximately five seconds.
21267 This driver is also available as a module ( = code which can be
21268 inserted in and removed from the running kernel whenever you want).
21269 If you want to compile it as a module, say M here and read
21270 <file:Documentation/modules.txt>. The module will be called
21273 Most people will answer Y to this question and "Reboot Using Button"
21274 below to be able to initiate a system shutdown from the button.
21276 Reboot Using Button
21277 CONFIG_NWBUTTON_REBOOT
21278 If you say Y here, then you will be able to initiate a system
21279 shutdown and reboot by pressing the orange button a number of times.
21280 The number of presses to initiate the shutdown is two by default,
21281 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
21282 in nwbutton.h and recompiling the driver or, if you compile the
21283 driver as a module, you can specify the number of presses at load
21284 time with "insmod button reboot_count=<something>".
21288 If you have a sound card in your computer, i.e. if it can say more
21289 than an occasional beep, say Y. Be sure to have all the information
21290 about your sound card and its configuration down (I/O port,
21291 interrupt and DMA channel), because you will be asked for it.
21293 You want to read the Sound-HOWTO, available from
21294 <http://www.tldp.org/docs.html#howto>. General information about
21295 the modular sound system is contained in the files
21296 <file:Documentation/sound/Introduction>. The file
21297 <file:Documentation/sound/README.OSS> contains some slightly
21298 outdated but still useful information as well.
21300 If you have a PnP sound card and you want to configure it at boot
21301 time using the ISA PnP tools (read
21302 <http://www.roestock.demon.co.uk/isapnptools/>), then you need to
21303 compile the sound card support as a module ( = code which can be
21304 inserted in and removed from the running kernel whenever you want)
21305 and load that module after the PnP configuration is finished. To do
21306 this, say M here and read <file:Documentation/modules.txt> as well
21307 as <file:Documentation/sound/README.modules>; the module will be
21308 called soundcore.o.
21310 I'm told that even without a sound card, you can make your computer
21311 say more than an occasional beep, by programming the PC speaker.
21312 Kernel patches and supporting utilities to do that are in the pcsp
21313 package, available at <ftp://ftp.infradead.org/pub/pcsp/>.
21317 OSS is the Open Sound System suite of sound card drivers. They make
21318 sound programming easier since they provide a common API. Say Y or
21319 M here (the module will be called sound.o) if you haven't found a
21320 driver for your sound card above, then pick your driver from the
21323 Persistent DMA buffers
21325 Linux can often have problems allocating DMA buffers for ISA sound
21326 cards on machines with more than 16MB of RAM. This is because ISA
21327 DMA buffers must exist below the 16MB boundary and it is quite
21328 possible that a large enough free block in this region cannot be
21329 found after the machine has been running for a while. If you say Y
21330 here the DMA buffers (64Kb) will be allocated at boot time and kept
21331 until the shutdown. This option is only useful if you said Y to
21332 "OSS sound modules", above. If you said M to "OSS sound modules"
21333 then you can get the persistent DMA buffer functionality by passing
21334 the command-line argument "dmabuf=1" to the sound.o module.
21336 Say Y unless you have 16MB or less RAM or a PCI sound card.
21338 Support for Aztech Sound Galaxy (non-PnP) cards
21339 CONFIG_SOUND_SGALAXY
21340 This module initializes the older non Plug and Play sound galaxy
21341 cards from Aztech. It supports the Waverider Pro 32 - 3D and the
21342 Galaxy Washington 16.
21344 If you compile the driver into the kernel, you have to add
21345 "sgalaxy=<io>,<irq>,<dma>,<dma2>,<sgbase>" to the kernel command
21348 Support for AD1816(A) based cards
21349 CONFIG_SOUND_AD1816
21350 Say M here if you have a sound card based on the Analog Devices
21353 If you compile the driver into the kernel, you have to add
21354 "ad1816=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
21356 Yamaha OPL3-SA1 audio controller
21357 CONFIG_SOUND_OPL3SA1
21358 Say Y or M if you have a Yamaha OPL3-SA1 sound chip, which is
21359 usually built into motherboards. Read
21360 <file:Documentation/sound/OPL3-SA> for details.
21362 If you compile the driver into the kernel, you have to add
21363 "opl3sa=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
21366 ProAudioSpectrum 16 support
21368 Answer Y only if you have a Pro Audio Spectrum 16, ProAudio Studio
21369 16 or Logitech SoundMan 16 sound card. Answer N if you have some
21370 other card made by Media Vision or Logitech since those are not
21371 PAS16 compatible. Please read <file:Documentation/sound/PAS16>.
21372 It is not necessary to add Sound Blaster support separately; it
21373 is included in PAS support.
21375 If you compile the driver into the kernel, you have to add
21376 "pas2=<io>,<irq>,<dma>,<dma2>,<sbio>,<sbirq>,<sbdma>,<sbdma2>
21377 to the kernel command line.
21379 Enable PAS16 joystick port
21380 CONFIG_PAS_JOYSTICK
21381 Say Y here to enable the Pro Audio Spectrum 16's auxiliary joystick
21384 100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support
21386 Answer Y if you have an original Sound Blaster card made by Creative
21387 Labs or a 100% hardware compatible clone (like the Thunderboard or
21388 SM Games). For an unknown card you may answer Y if the card claims
21389 to be Sound Blaster-compatible.
21391 Please read the file <file:Documentation/sound/Soundblaster>.
21393 You should also say Y here for cards based on the Avance Logic
21394 ALS-007 and ALS-1X0 chips (read <file:Documentation/sound/ALS>) and
21395 for cards based on ESS chips (read
21396 <file:Documentation/sound/ESS1868> and
21397 <file:Documentation/sound/ESS>). If you have an SB AWE 32 or SB AWE
21398 64, say Y here and also to "AWE32 synth" below and read
21399 <file:Documentation/sound/INSTALL.awe>. If you have an IBM Mwave
21400 card, say Y here and read <file:Documentation/sound/mwave>.
21402 If you compile the driver into the kernel and don't want to use
21403 isapnp, you have to add "sb=<io>,<irq>,<dma>,<dma2>" to the kernel
21406 You can say M here to compile this driver as a module; the module is
21409 Gravis Ultrasound support
21411 Say Y here for any type of Gravis Ultrasound card, including the GUS
21412 or GUS MAX. See also <file:Documentation/sound/ultrasound> for more
21413 information on configuring this card with modules.
21415 If you compile the driver into the kernel, you have to add
21416 "gus=<io>,<irq>,<dma>,<dma2>" to the kernel command line.
21418 MPU-401 support (NOT for SB16)
21419 CONFIG_SOUND_MPU401
21420 Be careful with this question. The MPU401 interface is supported by
21421 all sound cards. However, some natively supported cards have their
21422 own driver for MPU401. Enabling this MPU401 option with these cards
21423 will cause a conflict. Also, enabling MPU401 on a system that
21424 doesn't really have a MPU401 could cause some trouble. If your card
21425 was in the list of supported cards, look at the card specific
21426 instructions in the <file:Documentation/sound/README.OSS> file. It
21427 is safe to answer Y if you have a true MPU401 MIDI interface card.
21429 If you compile the driver into the kernel, you have to add
21430 "mpu401=<io>,<irq>" to the kernel command line.
21433 CONFIG_SOUND_UART6850
21434 This option enables support for MIDI interfaces based on the 6850
21435 UART chip. This interface is rarely found on sound cards. It's safe
21436 to answer N to this question.
21438 If you compile the driver into the kernel, you have to add
21439 "uart6850=<io>,<irq>" to the kernel command line.
21441 PSS (AD1848, ADSP-2115, ESC614) support
21443 Answer Y or M if you have an Orchid SW32, Cardinal DSP16, Beethoven
21444 ADSP-16 or some other card based on the PSS chipset (AD1848 codec +
21445 ADSP-2115 DSP chip + Echo ESC614 ASIC CHIP). For more information on
21446 how to compile it into the kernel or as a module see the file
21447 <file:Documentation/sound/PSS>.
21449 If you compile the driver into the kernel, you have to add
21450 "pss=<io>,<mssio>,<mssirq>,<mssdma>,<mpuio>,<mpuirq>" to the kernel
21453 Enable PSS mixer (Beethoven ADSP-16 and other compatible)
21455 Answer Y for Beethoven ADSP-16. You may try to say Y also for other
21456 cards if they have master volume, bass, treble, and you can't
21457 control it under Linux. If you answer N for Beethoven ADSP-16, you
21458 can't control master volume, bass, treble and synth volume.
21460 If you said M to "PSS support" above, you may enable or disable this
21461 PSS mixer with the module parameter pss_mixer. For more information
21462 see the file <file:Documentation/sound/PSS>.
21464 Have DSPxxx.LD firmware file
21465 CONFIG_PSS_HAVE_BOOT
21466 If you have the DSPxxx.LD file or SYNTH.LD file for you card, say Y
21467 to include this file. Without this file the synth device (OPL) may
21470 Full pathname of DSPxxx.LD firmware file
21471 CONFIG_PSS_BOOT_FILE
21472 Enter the full pathname of your DSPxxx.LD file or SYNTH.LD file,
21475 Microsoft Sound System support
21477 Again think carefully before answering Y to this question. It's
21478 safe to answer Y if you have the original Windows Sound System card
21479 made by Microsoft or Aztech SG 16 Pro (or NX16 Pro). Also you may
21480 say Y in case your card is NOT among these:
21482 ATI Stereo F/X, AdLib, Audio Excell DSP16, Cardinal DSP16,
21483 Ensoniq SoundScape (and compatibles made by Reveal and Spea),
21484 Gravis Ultrasound, Gravis Ultrasound ACE, Gravis Ultrasound Max,
21485 Gravis Ultrasound with 16 bit option, Logitech Sound Man 16,
21486 Logitech SoundMan Games, Logitech SoundMan Wave, MAD16 Pro (OPTi
21487 82C929), Media Vision Jazz16, MediaTriX AudioTriX Pro, Microsoft
21488 Windows Sound System (MSS/WSS), Mozart (OAK OTI-601), Orchid
21489 SW32, Personal Sound System (PSS), Pro Audio Spectrum 16, Pro
21490 Audio Studio 16, Pro Sonic 16, Roland MPU-401 MIDI interface,
21491 Sound Blaster 1.0, Sound Blaster 16, Sound Blaster 16ASP, Sound
21492 Blaster 2.0, Sound Blaster AWE32, Sound Blaster Pro, TI TM4000M
21493 notebook, ThunderBoard, Turtle Beach Tropez, Yamaha FM
21494 synthesizers (OPL2, OPL3 and OPL4), 6850 UART MIDI Interface.
21496 For cards having native support in VoxWare, consult the card
21497 specific instructions in <file:Documentation/sound/README.OSS>.
21498 Some drivers have their own MSS support and saying Y to this option
21499 will cause a conflict.
21501 If you compile the driver into the kernel, you have to add
21502 "ad1848=<io>,<irq>,<dma>,<dma2>[,<type>]" to the kernel command
21505 SGI Visual Workstation on-board audio
21507 Say Y or M if you have an SGI Visual Workstation and you want to be
21508 able to use its on-board audio. Read
21509 <file:Documentation/sound/vwsnd> for more info on this driver's
21512 NEC Vrc5477 AC97 sound
21513 CONFIG_SOUND_VRC5477
21514 Say Y here to enable sound support for the NEC Vrc5477 chip, an
21515 integrated, multi-function controller chip for MIPS CPUs. Works
21516 with the AC97 codec.
21518 Ensoniq SoundScape support
21519 CONFIG_SOUND_SSCAPE
21520 Answer Y if you have a sound card based on the Ensoniq SoundScape
21521 chipset. Such cards are being manufactured at least by Ensoniq, Spea
21522 and Reveal (Reveal makes also other cards).
21524 If you compile the driver into the kernel, you have to add
21525 "sscape=<io>,<irq>,<dma>,<mpuio>,<mpuirq>" to the kernel command
21528 MediaTriX AudioTriX Pro support
21530 Answer Y if you have the AudioTriX Pro sound card manufactured
21533 Have TRXPRO.HEX firmware file
21534 CONFIG_TRIX_HAVE_BOOT
21535 The MediaTrix AudioTrix Pro has an on-board microcontroller which
21536 needs to be initialized by downloading the code from the file
21537 TRXPRO.HEX in the DOS driver directory. If you don't have the
21538 TRXPRO.HEX file handy you may skip this step. However, the SB and
21539 MPU-401 modes of AudioTrix Pro will not work without this file!
21541 Full pathname of TRXPRO.HEX firmware file
21542 CONFIG_TRIX_BOOT_FILE
21543 Enter the full pathname of your TRXPRO.HEX file, starting from /.
21545 Support for OPTi MAD16 and/or Mozart based cards
21547 Answer Y if your card has a Mozart (OAK OTI-601) or MAD16 (OPTi
21548 82C928 or 82C929 or 82C931) audio interface chip. These chips are
21549 quite common so it's possible that many no-name cards have one of
21550 them. In addition the MAD16 chip is used in some cards made by known
21551 manufacturers such as Turtle Beach (Tropez), Reveal (some models)
21552 and Diamond (latest ones). Note however that the Tropez sound cards
21553 have their own driver; if you have one of those, say N here and Y or
21554 M to "Full support for Turtle Beach WaveFront", below.
21556 If you compile the driver into the kernel, you have to add
21557 "mad16=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the
21558 kernel command line.
21560 See also <file:Documentation/sound/Opti> and
21561 <file:Documentation/sound/MAD16> for more information on setting
21562 these cards up as modules.
21564 Full support for Turtle Beach WaveFront (Tropez Plus, Tropez, Maui) synth/sound cards
21565 CONFIG_SOUND_WAVEFRONT
21566 Answer Y or M if you have a Tropez Plus, Tropez or Maui sound card
21567 and read the files <file:Documentation/sound/Wavefront> and
21568 <file:Documentation/sound/Tropez+>.
21570 Support MIDI in older MAD16 based cards (requires SB)
21571 CONFIG_MAD16_OLDCARD
21572 Answer Y (or M) if you have an older card based on the C928 or
21573 Mozart chipset and you want to have MIDI support. If you enable this
21574 option you also need to enable support for Sound Blaster.
21576 Support for Crystal CS4232 based (PnP) cards
21577 CONFIG_SOUND_CS4232
21578 Say Y here if you have a card based on the Crystal CS4232 chip set,
21579 which uses its own Plug and Play protocol.
21581 If you compile the driver into the kernel, you have to add
21582 "cs4232=<io>,<irq>,<dma>,<dma2>,<mpuio>,<mpuirq>" to the kernel
21585 See <file:Documentation/sound/CS4232> for more information on
21586 configuring this card.
21588 Support for Crystal CS4297a on SiByte syncser
21589 CONFIG_SOUND_BCM_CS4297A
21590 The BCM91250A has a Crystal CS4297a on synchronous serial port B (in
21591 addition to the DB-9 serial port). Say Y or M here to enable the
21592 sound chip instead of the UART. Also note that CONFIG_KGDB should
21593 not be enabled at the same time, since it also attempts to use this
21596 Support for Yamaha OPL3-SA2 and SA3 based PnP cards
21597 CONFIG_SOUND_OPL3SA2
21598 Say Y or M if you have a card based on one of these Yamaha sound
21599 chipsets or the "SAx", which is actually a SA3. Read
21600 <file:Documentation/sound/OPL3-SA2> for more information on
21601 configuring these cards.
21603 If you compile the driver into the kernel and do not also
21604 configure in the optional ISA PnP support, you will have to add
21605 "opl3sa2=<io>,<irq>,<dma>,<dma2>,<mssio>,<mpuio>" to the kernel
21608 Support for Turtle Beach Wave Front (Maui, Tropez) synthesizers
21610 Say Y here if you have a Turtle Beach Wave Front, Maui, or Tropez
21613 If you compile the driver into the kernel, you have to add
21614 "maui=<io>,<irq>" to the kernel command line.
21616 Have OSWF.MOT firmware file
21617 CONFIG_MAUI_HAVE_BOOT
21618 Turtle Beach Maui and Tropez sound cards have a microcontroller
21619 which needs to be initialized prior to use. OSWF.MOT is a file
21620 distributed with the card's DOS/Windows drivers. Answer Y if you
21623 Full pathname of OSWF.MOT firmware file
21624 CONFIG_MAUI_BOOT_FILE
21625 Enter the full pathname of your OSWF.MOT file, starting from /.
21627 Support for Turtle Beach MultiSound Classic, Tahiti, Monterey
21628 CONFIG_SOUND_MSNDCLAS
21629 Say M here if you have a Turtle Beach MultiSound Classic, Tahiti or
21630 Monterey (not for the Pinnacle or Fiji).
21632 See <file:Documentation/sound/MultiSound> for important information
21633 about this driver. Note that it has been discontinued, but the
21634 Voyetra Turtle Beach knowledge base entry for it is still available
21635 at <http://www.voyetra-turtle-beach.com/site/kb_ftp/790.asp>.
21639 I/O port address for the MultiSound Classic and related cards.
21642 CONFIG_MSNDCLAS_IRQ
21643 Interrupt Request line for the MultiSound Classic and related cards.
21645 MSND Classic memory address
21646 CONFIG_MSNDCLAS_MEM
21647 Memory-mapped I/O base address for the MultiSound Classic and
21650 Full pathname of MSNDINIT.BIN firmware file
21651 CONFIG_MSNDCLAS_INIT_FILE
21652 The MultiSound cards have two firmware files which are required for
21653 operation, and are not currently included. These files can be
21654 obtained from Turtle Beach. See
21655 <file:Documentation/sound/MultiSound> for information on how to
21658 Full pathname of MSNDPERM.BIN firmware file
21659 CONFIG_MSNDCLAS_PERM_FILE
21660 The MultiSound cards have two firmware files which are required for
21661 operation, and are not currently included. These files can be
21662 obtained from Turtle Beach. See
21663 <file:Documentation/sound/MultiSound> for information on how to
21666 Support for Turtle Beach MultiSound Pinnacle, Fiji
21667 CONFIG_SOUND_MSNDPIN
21668 Say M here if you have a Turtle Beach MultiSound Pinnacle or Fiji.
21669 See <file:Documentation/sound/MultiSound> for important information
21670 about this driver. Note that it has been discontinued, but the
21671 Voyetra Turtle Beach knowledge base entry for it is still available
21672 at <http://www.voyetra-turtle-beach.com/site/kb_ftp/600.asp>.
21674 MSND Pinnacle IDE I/O 0
21675 CONFIG_MSNDPIN_IDE_IO0
21676 CD-ROM drive 0 memory-mapped I/O base address for the MultiSound
21677 Pinnacle and Fiji sound cards.
21679 MSND Pinnacle IDE I/O 1
21680 CONFIG_MSNDPIN_IDE_IO1
21681 CD-ROM drive 1 memory-mapped I/O base address for the MultiSound
21682 Pinnacle and Fiji sound cards.
21684 MSND Pinnacle IDE IRQ
21685 CONFIG_MSNDPIN_IDE_IRQ
21686 Interrupt request number for the IDE CD-ROM interface on the
21687 MultiSound Pinnacle and Fiji sound cards.
21691 Memory-mapped I/O base address for the primary synthesizer on
21692 MultiSound Pinnacle and Fiji sound cards.
21694 MSND Pinnacle MPU I/O
21695 CONFIG_MSNDPIN_MPU_IO
21696 Memory-mapped I/O base address for the Kurzweil daughterboard
21697 synthesizer on MultiSound Pinnacle and Fiji sound cards.
21699 MSND Pinnacle MPU IRQ
21700 CONFIG_MSNDPIN_MPU_IRQ
21701 Iinterrupt request number for the Kurzweil daughterboard
21702 synthesizer on MultiSound Pinnacle and Fiji sound cards.
21706 Interrupt request line for the primary synthesizer on MultiSound
21707 Pinnacle and Fiji sound cards.
21709 MSND Pinnacle joystick I/O
21710 CONFIG_MSNDPIN_JOYSTICK_IO
21711 Memory-mapped I/O base address for the joystick port on MultiSound
21712 Pinnacle and Fiji sound cards.
21714 MSND Pinnacle memory
21716 Memory-mapped I/O base address for the primary synthesizer on
21717 MultiSound Pinnacle and Fiji sound cards.
21719 Full pathname of PNDSPINI.BIN firmware file
21720 CONFIG_MSNDPIN_INIT_FILE
21721 The MultiSound cards have two firmware files which are required
21722 for operation, and are not currently included. These files can be
21723 obtained from Turtle Beach. See
21724 <file:Documentation/sound/MultiSound> for information on how to
21727 Full pathname of PNDSPERM.BIN firmware file
21728 CONFIG_MSNDPIN_PERM_FILE
21729 The MultiSound cards have two firmware files which are required for
21730 operation, and are not currently included. These files can be
21731 obtained from Turtle Beach. See
21732 <file:Documentation/sound/MultiSound> for information on how to
21735 MSND Pinnacle has S/PDIF I/O
21736 CONFIG_MSNDPIN_DIGITAL
21737 If you have the S/PDIF daughter board for the Pinnacle or Fiji,
21738 answer Y here; otherwise, say N. If you have this, you will be able
21739 to play and record from the S/PDIF port (digital signal). See
21740 <file:Documentation/sound/MultiSound> for information on how to make
21741 use of this capability.
21743 MSND Pinnacle non-PnP Mode
21744 CONFIG_MSNDPIN_NONPNP
21745 The Pinnacle and Fiji card resources can be configured either with
21746 PnP, or through a configuration port. Say Y here if your card is NOT
21747 in PnP mode. For the Pinnacle, configuration in non-PnP mode allows
21748 use of the IDE and joystick peripherals on the card as well; these
21749 do not show up when the card is in PnP mode. Specifying zero for any
21750 resource of a device will disable the device. If you are running the
21751 card in PnP mode, you must say N here and use isapnptools to
21752 configure the card's resources.
21754 MSND Pinnacle config port
21756 This is the port which the Pinnacle and Fiji uses to configure the
21757 card's resources when not in PnP mode. If your card is in PnP mode,
21758 then be sure to say N to the previous option, "MSND Pinnacle Non-PnP
21761 MSND buffer size (kB)
21762 CONFIG_MSND_FIFOSIZE
21763 Configures the size of each audio buffer, in kilobytes, for
21764 recording and playing in the MultiSound drivers (both the Classic
21765 and Pinnacle). Larger values reduce the chance of data overruns at
21766 the expense of overall latency. If unsure, use the default.
21768 Yamaha FM synthesizer (YM3812/OPL-3) support
21769 CONFIG_SOUND_YM3812
21770 Answer Y if your card has a FM chip made by Yamaha (OPL2/OPL3/OPL4).
21771 Answering Y is usually a safe and recommended choice, however some
21772 cards may have software (TSR) FM emulation. Enabling FM support with
21773 these cards may cause trouble (I don't currently know of any such
21774 cards, however). Please read the file
21775 <file:Documentation/sound/OPL3> if your card has an OPL3 chip.
21777 If you compile the driver into the kernel, you have to add
21778 "opl3=<io>" to the kernel command line.
21782 ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio)
21783 CONFIG_SOUND_ACI_MIXER
21784 ACI (Audio Command Interface) is a protocol used to communicate with
21785 the microcontroller on some sound cards produced by miro and
21786 Cardinal Technologies. The main function of the ACI is to control
21787 the mixer and to get a product identification.
21789 This VoxWare ACI driver currently supports the ACI functions on the
21790 miroSOUND PCM1-pro, PCM12 and PCM20 radio. On the PCM20 radio, ACI
21791 also controls the radio tuner. This is supported in the video4linux
21792 miropcm20 driver (say M or Y here and go back to "Multimedia
21793 devices" -> "Radio Adapters").
21795 This driver is also available as a module and will be called aci.o.
21798 CONFIG_SOUND_AWE32_SYNTH
21799 Say Y here if you have a Sound Blaster SB32, AWE32-PnP, SB AWE64 or
21800 similar sound card. See <file:Documentation/sound/README.awe>,
21801 <file:Documentation/sound/AWE32> and the Soundblaster-AWE
21802 mini-HOWTO, available from <http://www.tldp.org/docs.html#howto>
21805 Gallant Audio Cards (SC-6000 and SC-6600 based)
21806 CONFIG_SOUND_AEDSP16
21807 Answer Y if you have a Gallant's Audio Excel DSP 16 card. This
21808 driver supports Audio Excel DSP 16 but not the III nor PnP versions
21811 The Gallant's Audio Excel DSP 16 card can emulate either an SBPro or
21812 a Microsoft Sound System card, so you should have said Y to either
21813 "100% Sound Blaster compatibles (SB16/32/64, ESS, Jazz16) support"
21814 or "Microsoft Sound System support", above, and you need to answer
21815 the "MSS emulation" and "SBPro emulation" questions below
21816 accordingly. You should say Y to one and only one of these two
21819 Read the <file:Documentation/sound/README.OSS> file and the head of
21820 <file:drivers/sound/aedsp16.c> as well as
21821 <file:Documentation/sound/AudioExcelDSP16> to get more information
21822 about this driver and its configuration.
21824 Audio Excel DSP 16 (SBPro emulation)
21825 CONFIG_AEDSP16_SBPRO
21826 Answer Y if you want your audio card to emulate Sound Blaster Pro.
21827 You should then say Y to "100% Sound Blaster compatibles
21828 (SB16/32/64, ESS, Jazz16) support" and N to "Audio Excel DSP 16 (MSS
21831 If you compile the driver into the kernel, you have to add
21832 "aedsp16=<io>,<irq>,<dma>,<mssio>,<mpuio>,<mouirq>" to the kernel
21835 Audio Excel DSP 16 (MSS emulation)
21837 Answer Y if you want your audio card to emulate Microsoft Sound
21838 System. You should then say Y to "Microsoft Sound System support"
21839 and say N to "Audio Excel DSP 16 (SBPro emulation)".
21841 SC-6600 based audio cards (new Audio Excel DSP 16)
21843 The SC6600 is the new version of DSP mounted on the Audio Excel DSP
21844 16 cards. Find in the manual the FCC ID of your audio card and
21845 answer Y if you have an SC6600 DSP.
21847 SC-6600 Joystick Interface
21849 Say Y here in order to use the joystick interface of the Audio Excel
21852 SC-6600 CD-ROM Interface
21853 CONFIG_SC6600_CDROM (4=None, 3=IDE, 1=Panasonic, 0=Sony)
21854 This is used to activate the CD-ROM interface of the Audio Excel
21855 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
21858 SC-6600 CD-ROM Interface I/O Address
21859 CONFIG_SC6600_CDROMBASE
21860 Base I/O port address for the CD-ROM interface of the Audio Excel
21863 Audio Excel DSP 16 (MPU401 emulation)
21864 CONFIG_AEDSP16_MPU401
21865 Answer Y if you want your audio card to emulate the MPU-401 midi
21866 interface. You should then also say Y to "MPU-401 support".
21868 Note that the I/O base for MPU-401 support of aedsp16 is the same
21869 you have selected for "MPU-401 support". If you are using this
21870 driver as a module you have to specify the MPU I/O base address with
21871 the parameter 'mpu_base=0xNNN'.
21873 SC-6600 CDROM Interface (4=None, 3=IDE, 1=Panasonic, 0=?Sony?)
21874 CONFIG_SC6600_CDROM
21875 This is used to activate the CD-ROM interface of the Audio Excel
21876 DSP 16 card. Enter: 0 for Sony, 1 for Panasonic, 2 for IDE, 4 for no
21879 C-Media PCI (CMI8338/8738)
21881 Say Y or M if you have a PCI sound card using the CMI8338
21882 or the CMI8738 chipset. Data on these chips are available at
21883 <http://www.cmedia.com.tw/>.
21885 A userspace utility to control some internal registers of these
21886 chips is available at
21887 <http://member.nifty.ne.jp/Breeze/softwares/unix/cmictl-e.html>.
21889 Support CMI8738 based audio cards
21890 CONFIG_SOUND_CMPCI_CM8738
21891 Say Y or M if you have a PCI sound card using the CMI8338
21892 or the CMI8378 chipset. Data on this chip is available at
21893 <http://www.cmedia.com.tw/doc8738.htm>.
21895 A userspace utility to control some internal registers of these
21896 chips is available at
21897 <http://member.nifty.ne.jp/Breeze/softwares/unix/cmictl-e.html>.
21900 CONFIG_SOUND_CMPCI_JOYSTICK
21901 Say here in order to enable the joystick port on a sound crd using
21902 the CMI8338 or the CMI8738 chipset. Data on these chips are
21903 available at <http://www.cmedia.com.tw/>.
21905 Number of speakers (2, 4, 5, 6)
21906 CONFIG_SOUND_CMPCI_SPEAKERS
21907 Specify the number of speaker channels you want the card to drive,
21910 Enable S/PDIF loop for CMI8738
21911 CONFIG_SOUND_CMPCI_SPDIFLOOP
21912 Enable loopback from SPDIF in to SPDIF out. For discussion, see
21913 "The 8738 Audio SPDIF In/Out Technical Data" on the technical
21914 support page at <http://www.cmedia.com.tw/>.
21916 A userspace utility to control even more internal registers of these
21917 chips is available at
21918 <http://member.nifty.ne.jp/Breeze/softwares/unix/cmictl-e.html>.
21919 This package will among other things help you enable SPDIF
21920 out/in/loop/monitor.
21923 CONFIG_SOUND_CMPCI_FM
21924 Say Y here to enable the legacy FM (frequency-modulation) synthesis
21925 support on a card using the CMI8338 or CMI8378 chipset.
21927 FM I/O 388, 3C8, 3E0, 3E8
21928 CONFIG_SOUND_CMPCI_FMIO
21929 Set the base I/O address for FM synthesis control on a card using
21930 the CMI8338 or CMI8378 chipset.
21932 Enable legacy MPU-401
21933 CONFIG_SOUND_CMPCI_MIDI
21934 Say Y here to enable the legacy MP401 MIDI synthesis support on a
21935 card using the CMI8338 or CMI8378 chipset.
21937 MPU-401 I/O 330, 320, 310, 300
21938 CONFIG_SOUND_CMPCI_MPUIO
21939 Set the base I/O address for MP401 MIDI synthesis control on a card
21940 using the CMI8338 or CMI8378 chipset.
21942 Inverse S/PDIF in for CMI8738
21943 CONFIG_SOUND_CMPCI_SPDIFINVERSE
21944 Say Y here to have the driver invert the signal presented on SPDIF IN
21945 of a card using the CMI8338 or CMI8378 chipset.
21947 Use Line-in as Read-out
21948 CONFIG_SOUND_CMPCI_LINE_REAR
21949 Say Y here to enable using line-in jack as an output jack for a rear
21952 Use Line-in as Bass
21953 CONFIG_SOUND_CMPCI_LINE_BASS
21954 Say Y here to enable using line-in jack as an output jack for a bass
21957 Creative SBLive! (EMU10K1) based PCI sound cards
21958 CONFIG_SOUND_EMU10K1
21959 Say Y or M if you have a PCI sound card using the EMU10K1 chipset,
21960 such as the Creative SBLive!, SB PCI512 or Emu-APS.
21962 For more information on this driver and the degree of support for
21963 the different card models please check:
21965 <http://sourceforge.net/projects/emu10k1/>
21967 It is now possible to load dsp microcode patches into the EMU10K1
21968 chip. These patches are used to implement real time sound
21969 processing effects which include for example: signal routing,
21970 bass/treble control, AC3 passthrough, ...
21971 Userspace tools to create new patches and load/unload them can be
21972 found in the emu-tools package at the above URL.
21974 Creative SBLive! (EMU10K1) MIDI
21975 CONFIG_MIDI_EMU10K1
21976 Say Y if you want to be able to use the OSS /dev/sequencer
21977 interface. This code is still experimental.
21979 Crystal SoundFusion (CS4280/461x)
21980 CONFIG_SOUND_FUSION
21981 This module drives the Crystal SoundFusion devices (CS4280/46xx
21982 series) when wired as native sound drivers with AC97 codecs. If
21983 this driver does not work try the CS4232 driver.
21985 Ensoniq AudioPCI (ES1370) based PCI sound cards
21986 CONFIG_SOUND_ES1370
21987 Say Y or M if you have a PCI sound card utilizing the Ensoniq
21988 ES1370 chipset, such as Ensoniq's AudioPCI (non-97). To find
21989 out if your sound card uses an ES1370 without removing your
21990 computer's cover, use lspci -n and look for the PCI ID
21991 1274:5000. Since Ensoniq was bought by Creative Labs,
21992 Sound Blaster 64/PCI models are either ES1370 or ES1371 based.
21993 This driver differs slightly from OSS/Free, so PLEASE READ
21994 <file:Documentation/sound/es1370>.
21996 Ensoniq AudioPCI 97 (ES1371) based sound cards
21997 CONFIG_SOUND_ES1371
21998 Say Y or M if you have a PCI sound card utilizing the Ensoniq
21999 ES1371 chipset, such as Ensoniq's AudioPCI97. To find out if
22000 your sound card uses an ES1371 without removing your computer's
22001 cover, use lspci -n and look for the PCI ID 1274:1371. Since
22002 Ensoniq was bought by Creative Labs, Sound Blaster 64/PCI
22003 models are either ES1370 or ES1371 based. This driver differs
22004 slightly from OSS/Free, so PLEASE READ
22005 <file:Documentation/sound/es1371>.
22007 ESS Solo1 based PCI sound cards (eg. SC1938)
22008 CONFIG_SOUND_ESSSOLO1
22009 Say Y or M if you have a PCI sound card utilizing the ESS Technology
22010 Solo1 chip. To find out if your sound card uses a
22011 Solo1 chip without removing your computer's cover, use
22012 lspci -n and look for the PCI ID 125D:1969. This driver
22013 differs slightly from OSS/Free, so PLEASE READ
22014 <file:Documentation/sound/solo1>.
22016 S3 SonicVibes based PCI sound cards
22017 CONFIG_SOUND_SONICVIBES
22018 Say Y or M if you have a PCI sound card utilizing the S3
22019 SonicVibes chipset. To find out if your sound card uses a
22020 SonicVibes chip without removing your computer's cover, use
22021 lspci -n and look for the PCI ID 5333:CA00. This driver
22022 differs slightly from OSS/Free, so PLEASE READ
22023 <file:Documentation/sound/sonicvibes>.
22025 Trident 4DWave DX/NX, SiS 7018 or ALi 5451 PCI Audio Core
22026 CONFIG_SOUND_TRIDENT
22027 Say Y or M if you have a PCI sound card utilizing the Trident
22028 4DWave-DX/NX chipset or your mother board chipset has SiS 7018
22029 or ALi 5451 built-in. The SiS 7018 PCI Audio Core is embedded
22030 in SiS960 Super South Bridge and SiS540/630 Single Chipset.
22031 The ALi 5451 PCI Audio Core is embedded in ALi M1535, M1535D,
22032 M1535+ or M1535D+ South Bridge.
22034 Use lspci -n to find out if your sound card or chipset uses
22035 Trident 4DWave or SiS 7018. PCI ID 1023:2000 or 1023:2001 stands
22036 for Trident 4Dwave. PCI ID 1039:7018 stands for SiS7018. PCI ID
22037 10B9:5451 stands for ALi5451.
22039 This driver supports S/PDIF in/out (record/playback) for ALi 5451
22040 embedded in ALi M1535+ and M1535D+. Note that they aren't all
22041 enabled by default; you can enable them by saying Y to "/proc file
22042 system support" and "Sysctl support", and after the /proc file
22043 system has been mounted, executing the command
22045 command what is enabled
22047 echo 0>/proc/ALi5451 pcm out is also set to S/PDIF out. (Default).
22049 echo 1>/proc/ALi5451 use S/PDIF out to output pcm data.
22051 echo 2>/proc/ALi5451 use S/PDIF out to output non-pcm data.
22054 echo 3>/proc/ALi5451 record from Ac97 in(MIC, Line in...).
22057 echo 4>/proc/ALi5451 no matter Ac97 settings, record from S/PDIF
22061 This driver differs slightly from OSS/Free, so PLEASE READ the
22062 comments at the top of <file:drivers/sound/trident.c>.
22064 Rockwell WaveArtist
22065 CONFIG_SOUND_WAVEARTIST
22066 Say Y here to include support for the Rockwell WaveArtist sound
22067 system. This driver is mainly for the NetWinder.
22069 VIA 82Cxxx Audio Codec
22070 CONFIG_SOUND_VIA82CXXX
22071 Say Y here to include support for the audio codec found on VIA
22072 82Cxxx-based chips. Typically these are built into a motherboard.
22074 DO NOT select Sound Blaster or Adlib with this driver, unless
22075 you have a Sound Blaster or Adlib card in addition to your VIA
22079 CONFIG_MIDI_VIA82CXXX
22080 Answer Y to use the MIDI interface of the Via686. You may need to
22081 enable this in the BIOS before it will work. This is for connection
22082 to external MIDI hardware, and is not required for software playback
22085 NeoMagic 256AV/256ZX sound chipsets
22087 Say M here to include audio support for the NeoMagic 256AV/256ZX
22088 chipsets. These are the audio chipsets found in the Sony
22089 Z505S/SX/DX, some Sony F-series, and the Dell Latitude CPi and CPt
22090 laptops. It includes support for an AC97-compatible mixer and an
22091 apparently proprietary sound engine.
22093 See <file:Documentation/sound/NM256> for further information.
22095 ESS Maestro, Maestro2, Maestro2E driver
22096 CONFIG_SOUND_MAESTRO
22097 Say Y or M if you have a sound system driven by ESS's Maestro line
22098 of PCI sound chips. These include the Maestro 1, Maestro 2, and
22099 Maestro 2E. See <file:Documentation/sound/Maestro> for more
22102 ESS Maestro3/Allegro driver
22103 CONFIG_SOUND_MAESTRO3
22104 Say Y or M if you have a sound system driven by ESS's Maestro 3
22107 ForteMedia FM801 driver
22109 Say Y or M if you want driver support for the ForteMedia FM801 PCI
22110 audio controller (Abit AU10, Genius Sound Maker, HP Workstation
22111 zx2000, and others).
22115 Includes ASB 64 4D. Information on programming AdLib cards is
22116 available at <http://www.itsnet.com/home/ldragon/Specs/adlib.html>.
22118 Crystal Sound CS4281
22119 CONFIG_SOUND_CS4281
22120 Picture and feature list at
22121 <http://www.pcbroker.com/crystal4281.html>.
22123 16 bit sampling option of GUS (_NOT_ GUS MAX)
22125 Support for Gravis Ulstrasound (GUS) cards (other than the GUS),
22126 sampling at 16-bit width.
22129 CONFIG_SOUND_GUSMAX
22130 Support for Gravis Ulstrasound MAX.
22132 Intel ICH audio support
22134 Supports the following chipsets:
22145 These are audio drivers for integral audio in chipsets of motherboards.
22147 Intel's I/O Controller Hub (ICH) is used on 810/815/820/840/845/845D/850 motherboards.
22148 SiS 7012 is used on 645/735/745 motherboards.
22150 Verbose initialization
22151 CONFIG_SOUND_TRACEINIT
22152 Verbose soundcard initialization -- affects the format of autoprobe
22153 and initialization messages at boot time.
22155 TV card (bt848) mixer support
22156 CONFIG_SOUND_TVMIXER
22157 Support for audio mixer facilities on the BT848 TV frame-grabber
22162 16-bit support for the VIDC onboard sound hardware found on Acorn
22165 Loopback MIDI device support
22167 Support for MIDI loopback on port 1 or 2.
22169 Yamaha YMF7xx PCI audio (native mode)
22170 CONFIG_SOUND_YMFPCI
22171 Support for Yamaha cards with the following chipsets: YMF724,
22172 YMF724F, YMF740, YMF740C, YMF744, and YMF754.
22174 Two common cards that use this type of chip are Waveforce 192XG,
22175 and Waveforce 192 Digital.
22177 Yamaha PCI legacy ports support
22178 CONFIG_SOUND_YMFPCI_LEGACY
22179 Support for YMF7xx PCI cards emulating an MP401.
22181 RME Hammerfall (RME96XX) support
22182 CONFIG_SOUND_RME96XX
22183 Say Y or M if you have a Hammerfall or Hammerfall light multichannel card
22184 from RME. If you want to acess advanced features of the card, read
22185 Documentation/sound/rme96xx.
22187 Are you using a crosscompiler
22188 CONFIG_CROSSCOMPILE
22189 Say Y here if you are compiling the kernel on a different
22190 architecture than the one it is intended to run on.
22192 Kernel support for Linux/MIPS 32-bit binary compatibility
22193 CONFIG_MIPS32_COMPAT
22194 Select this option if you want Linux/MIPS 32-bit binary
22195 compatibility. Since all software available for Linux/MIPS is
22196 currently 32-bit you should say Y here.
22198 Kernel support for o32 binaries
22200 Select this option if you want to run o32 binaries. These are pure
22201 32-bit binaries as used by the 32-bit Linux/MIPS port. Most of
22202 existing binaries are in this format.
22206 Kernel support for n32 binaries
22208 Select this option if you want to run n32 binaries. These are
22209 64-bit binaries using 32-bit quantities for addressing and certain
22210 data that would normally be 64-bit. They are used in special
22215 Build fp exception handler module
22216 CONFIG_MIPS_FPE_MODULE
22217 Build the floating point exception handler module. This option is
22218 only useful for people working on the floating point exception
22219 handler. If you don't, say N.
22221 Galileo EV64120 Evaluation board
22222 CONFIG_MIPS_EV64120
22223 This is an evaluation board based on the Galileo GT-64120
22224 single-chip system controller that contains a MIPS R5000 compatible
22225 core running at 75/100MHz. Their website is located at
22226 <http://www.marvell.com/>. Say Y here if you wish to build a
22227 kernel for this platform.
22229 Galileo EV96100 Evaluation board
22230 CONFIG_MIPS_EV96100
22231 This is an evaluation board based on the Galielo GT-96100 LAN/WAN
22232 communications controllers containing a MIPS R5000 compatible core
22233 running at 83MHz. Their website is <http://www.marvell.com/>. Say Y
22234 here if you wish to build a kernel for this platform.
22236 Support for ITE 8172G board
22237 CONFIG_MIPS_ITE8172
22238 Ths is an evaluation board made by ITE <http://www.ite.com.tw/>
22239 with ATX form factor that utilizes a MIPS R5000 to work with its
22240 ITE8172G companion internet appliance chip. The MIPS core can be
22241 either a NEC Vr5432 or QED RM5231. Say Y here if you wish to build
22242 a kernel for this platform.
22244 Support for Globespan IVR board
22246 This is an evaluation board built by Globespan to showcase their
22247 iVR (Internet Video Recorder) design. It utilizes a QED RM5231
22248 R5000 MIPS core. More information can be found out their website
22249 located at <http://www.globespan.net/>. Say Y here if you wish to
22250 build a kernel for this platform.
22252 Support for Alchemy Semi PB1000 board
22254 This is an evaluation board built by Alchemy Semiconductor to
22255 showcase their Au1000 Internet Edge Processor. It is SOC design
22256 containing a MIPS32 core running at 266/400/500MHz with many
22257 integrated peripherals. Further information can be found at their
22258 website, <http://www.alchemysemi.com/>. Say Y here if you wish to
22259 build a kernel for this platform.
22261 Support for Philips Nino
22263 Say Y here to select a kernel for the Philips Nino Palm PC. The
22264 website at <http://www.realitydiluted.com/projects/nino/index.html>
22265 will have more information.
22267 # Choice: nino_model
22269 Say Y here to build a kernel specifically for Nino Palm PCs with
22270 4MB of memory. These include models 300/301/302/319.
22272 Model-200/210/312/320/325/350/390
22274 Say Y here to build a kernel specifically for Nino Palm PCs with
22275 8MB of memory. These include models 200/210/312/320/325/350/390.
22279 Say Y here to build a kernel specifically for Nino 500/501 color
22280 Palm PCs from Philips (INCOMPLETE).
22281 Model-300/301/302/319
22283 Enable run-time debugging
22284 CONFIG_RUNTIME_DEBUG
22285 If you say Y here, some debugging macros will do run-time checking.
22286 If you say N here, those macros will mostly turn to no-ops. Currently
22287 supported by MIPS arch. See include/asm-mips/debug.h for debuging macros.
22291 CONFIG_MIPS_UNCACHED
22292 If you say Y here there kernel will disable all CPU caches. This will
22293 reduce the system's performance dramatically but can help finding
22294 otherwise hard to track bugs. It can also useful if you're doing
22295 hardware debugging with a logic analyzer and need to see all traffic
22298 AU1000 ethernet controller on SGI MIPS system
22299 CONFIG_MIPS_AU1000_ENET
22300 If you have an Alchemy Semi AU1000 ethernet controller
22301 on an SGI MIPS system, say Y. Otherwise, say N.
22303 WD93 SCSI Controller on SGI MIPS system
22304 CONFIG_SGIWD93_SCSI
22305 If you have a Western Digital WD93 SCSI controller on
22306 an SGI MIPS system, say Y. Otherwise, say N.
22308 Magic System Request Key support
22310 If you say Y here, you will have some control over the system even
22311 if the system crashes for example during kernel debugging (e.g., you
22312 will be able to flush the buffer cache to disk, reboot the system
22313 immediately or dump some status information). This is accomplished
22314 by pressing various keys while holding SysRq (Alt+PrintScreen). It
22315 also works on a serial console (on PC hardware at least), if you
22316 send a BREAK and then within 5 seconds a command keypress. The
22317 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
22318 unless you really know what this hack does.
22322 ISDN ("Integrated Services Digital Networks", called RNIS in France)
22323 is a special type of fully digital telephone service; it's mostly
22324 used to connect to your Internet service provider (with SLIP or
22325 PPP). The main advantage is that the speed is higher than ordinary
22326 modem/telephone connections, and that you can have voice
22327 conversations while downloading stuff. It only works if your
22328 computer is equipped with an ISDN card and both you and your service
22329 provider purchased an ISDN line from the phone company. For
22330 details, read <http://alumni.caltech.edu/~dank/isdn/> on the WWW.
22332 This driver allows you to use an ISDN-card for networking
22333 connections and as dialin/out device. The isdn-tty's have a built
22334 in AT-compatible modem emulator. Network devices support autodial,
22335 channel-bundling, callback and caller-authentication without having
22336 a daemon running. A reduced T.70 protocol is supported with tty's
22337 suitable for German BTX. On D-Channel, the protocols EDSS1
22338 (Euro-ISDN) and 1TR6 (German style) are supported. See
22339 <file:Documentation/isdn/README> for more information.
22341 If you want to compile the ISDN code as a module ( = code which can
22342 be inserted in and removed from the running kernel whenever you
22343 want), say M here and read <file:Documentation/modules.txt>. The
22344 module will be called isdn.o. If unsure, say N.
22346 Support synchronous PPP
22348 Over digital connections such as ISDN, there is no need to
22349 synchronize sender and recipient's clocks with start and stop bits
22350 as is done over analog telephone lines. Instead, one can use
22351 "synchronous PPP". Saying Y here will include this protocol. This
22352 protocol is used by Cisco and Sun for example. So you want to say Y
22353 here if the other end of your ISDN connection supports it. You will
22354 need a special version of pppd (called ipppd) for using this
22355 feature. See <file:Documentation/isdn/README.syncppp> and
22356 <file:Documentation/isdn/syncPPP.FAQ> for more information.
22358 PPP filtering for ISDN
22360 Say Y here if you want to be able to filter the packets passing over
22361 IPPP interfaces. This allows you to control which packets count as
22362 activity (i.e. which packets will reset the idle timer or bring up
22363 a demand-dialled link) and which packets are to be dropped entirely.
22364 You need to say Y here if you wish to use the pass-filter and
22365 active-filter options to ipppd.
22369 Support generic MP (RFC 1717)
22371 With synchronous PPP enabled, it is possible to increase throughput
22372 by bundling several ISDN-connections, using this protocol. See
22373 <file:Documentation/isdn/README.syncppp> for more information.
22375 Use VJ-compression with synchronous PPP
22377 This enables Van Jacobson header compression for synchronous PPP.
22378 Say Y if the other end of the connection supports it.
22380 Support BSD compression
22381 CONFIG_ISDN_PPP_BSDCOMP
22382 Support for the BSD-Compress compression method for PPP, which uses
22383 the LZW compression method to compress each PPP packet before it is
22384 sent over the wire. The machine at the other end of the PPP link
22385 (usually your ISP) has to support the BSD-Compress compression
22386 method as well for this to be useful. Even if they don't support it,
22387 it is safe to say Y here.
22389 If you want to compile the driver as a module ( = code which can be
22390 inserted in and removed from the running kernel whenever you want),
22391 say M here and read <file:Documentation/modules.txt>. The module
22392 will be called isdn_bsdcomp.o.
22394 Support audio via ISDN
22396 If you say Y here, the modem-emulator will support a subset of the
22397 EIA Class 8 Voice commands. Using a getty with voice-support
22398 (mgetty+sendfax by gert@greenie.muc.de with an extension, available
22399 with the ISDN utility package for example), you will be able to use
22400 your Linux box as an ISDN-answering machine. Of course, this must be
22401 supported by the lowlevel driver also. Currently, the HiSax driver
22402 is the only voice-supporting driver. See
22403 <file:Documentation/isdn/README.audio> for more information.
22405 X.25 PLP on top of ISDN
22407 This feature provides the X.25 protocol over ISDN connections.
22408 See <file:Documentation/isdn/README.x25> for more information
22409 if you are thinking about using this.
22411 ISDN diversion services support
22412 CONFIG_ISDN_DIVERSION
22413 This option allows you to use some supplementary diversion
22414 services in conjunction with the HiSax driver on an EURO/DSS1
22417 Supported options are CD (call deflection), CFU (Call forward
22418 unconditional), CFB (Call forward when busy) and CFNR (call forward
22419 not reachable). Additionally the actual CFU, CFB and CFNR state may
22422 The use of CFU, CFB, CFNR and interrogation may be limited to some
22423 countries. The keypad protocol is still not implemented. CD should
22424 work in all countries if the service has been subscribed to.
22426 Please read the file <file:Documentation/isdn/README.diversion>.
22428 If you want to compile the driver as a module ( = code which can be
22429 inserted in and removed from the running kernel whenever you want),
22430 say M here and read <file:Documentation/modules.txt>. The module
22431 will be called dss1_divert.o.
22433 ICN 2B and 4B support
22434 CONFIG_ISDN_DRV_ICN
22435 This enables support for two kinds of ISDN-cards made by a German
22436 company called ICN. 2B is the standard version for a single ISDN
22437 line with two B-channels, 4B supports two ISDN lines. For running
22438 this card, additional firmware is necessary, which has to be
22439 downloaded into the card using a utility which is distributed
22440 separately. See <file:Documentation/isdn/README> and
22441 <file:Documentation/isdn/README.icn> for more
22444 If you want to compile this as a module ( = code which can be
22445 inserted in and removed from the running kernel whenever you want),
22446 say M here and read <file:Documentation/modules.txt>. The module
22447 will be called icn.o.
22450 CONFIG_ISDN_DRV_LOOP
22451 This driver provides a virtual ISDN card. Its primary purpose is
22452 testing of linklevel features or configuration without getting
22453 charged by your service-provider for lots of phone calls.
22454 You need will need the loopctrl utility from the latest isdn4k-utils
22455 package to set up this driver.
22457 If you want to compile the driver as a module ( = code which can be
22458 inserted in and removed from the running kernel whenever you want),
22459 say M here and read <file:Documentation/modules.txt>. The module
22460 will be called isdnloop.o.
22462 HiSax SiemensChipSet driver support
22463 CONFIG_ISDN_DRV_HISAX
22464 This is a driver supporting the Siemens chipset on various
22465 ISDN-cards (like AVM A1, Elsa ISDN cards, Teles S0-16.0, Teles
22466 S0-16.3, Teles S0-8, Teles/Creatix PnP, ITK micro ix1 and many
22469 HiSax is just the name of this driver, not the name of any hardware.
22471 If you have a card with such a chipset, you should say Y here and
22472 also to the configuration option of the driver for your particular
22475 If you want to compile this as a module ( = code which can be
22476 inserted in and removed from the running kernel whenever you want),
22477 say M here and read <file:Documentation/modules.txt>. The module
22478 will be called hisax.o. See <file:Documentation/isdn/README.HiSax>
22479 for more information on using this driver.
22481 HiSax Support for EURO/DSS1
22483 Say Y or N according to the D-channel protocol which your local
22484 telephone service company provides.
22486 The call control protocol E-DSS1 is used in most European countries.
22489 Support for German chargeinfo
22491 If you want that the HiSax hardware driver sends messages to the
22492 upper level of the isdn code on each AOCD (Advice Of Charge, During
22493 the call -- transmission of the fee information during a call) and
22494 on each AOCE (Advice Of Charge, at the End of the call --
22495 transmission of fee information at the end of the call), say Y here.
22496 This works only in Germany.
22498 Disable sending complete
22499 CONFIG_HISAX_NO_SENDCOMPLETE
22500 If you have trouble with some ugly exchanges or you live in
22501 Australia select this option.
22503 Disable sending low layer compatibility
22504 CONFIG_HISAX_NO_LLC
22505 If you have trouble with some ugly exchanges try to select this
22508 Disable keypad protocol option
22509 CONFIG_HISAX_NO_KEYPAD
22510 If you like to send special dial strings including * or # without
22511 using the keypad protocol, select this option.
22513 HiSax Support for German 1TR6
22515 Say Y or N according to the D-channel protocol which your local
22516 telephone service company provides.
22518 1TR6 is an old call control protocol which was used in Germany
22519 before E-DSS1 was established. Nowadays, all new lines in Germany
22522 HiSax Support for US NI1
22524 Enable this if you like to use ISDN in US on a NI1 basic rate
22527 Maximum number of cards supported by HiSax
22528 CONFIG_HISAX_MAX_CARDS
22529 This is used to allocate a driver-internal structure array with one
22530 entry for each HiSax card on your system.
22534 This enables HiSax support for the Teles ISDN-cards S0-16.0, S0-8
22535 and many compatibles.
22537 See <file:Documentation/isdn/README.HiSax> on how to configure it
22538 using the different cards, a different D-channel protocol, or
22539 non-standard IRQ/port/shmem settings.
22541 Teles 16.3 or PNP or PCMCIA
22543 This enables HiSax support for the Teles ISDN-cards S0-16.3 the
22544 Teles/Creatix PnP and the Teles PCMCIA.
22546 See <file:Documentation/isdn/README.HiSax> on how to configure it
22547 using the different cards, a different D-channel protocol, or
22548 non-standard IRQ/port settings.
22551 CONFIG_HISAX_TELESPCI
22552 This enables HiSax support for the Teles PCI.
22553 See <file:Documentation/isdn/README.HiSax> on how to configure it.
22557 This enables HiSax support for the Teles/Creatix parallel port
22558 S0BOX. See <file:Documentation/isdn/README.HiSax> on how to
22562 CONFIG_HISAX_AVM_A1
22563 This enables HiSax support for the AVM A1 (aka "Fritz").
22565 See <file:Documentation/isdn/README.HiSax> on how to configure it
22566 using the different cards, a different D-channel protocol, or
22567 non-standard IRQ/port settings.
22569 AVM PnP/PCI (Fritz!PnP/PCI)
22570 CONFIG_HISAX_FRITZPCI
22571 This enables HiSax support for the AVM "Fritz!PnP" and "Fritz!PCI".
22572 See <file:Documentation/isdn/README.HiSax> on how to configure it.
22574 AVM A1 PCMCIA (Fritz)
22575 CONFIG_HISAX_AVM_A1_PCMCIA
22576 This enables HiSax support for the AVM A1 "Fritz!PCMCIA").
22577 See <file:Documentation/isdn/README.HiSax> on how to configure it.
22581 This enables HiSax support for the Elsa Mircolink ISA cards, for the
22582 Elsa Quickstep series cards and Elsa PCMCIA.
22584 See <file:Documentation/isdn/README.HiSax> on how to configure it
22585 using the different cards, a different D-channel protocol, or
22586 non-standard IRQ/port settings.
22588 ITK ix1-micro Revision 2
22589 CONFIG_HISAX_IX1MICROR2
22590 This enables HiSax support for the ITK ix1-micro Revision 2 card.
22592 See <file:Documentation/isdn/README.HiSax> on how to configure it
22593 using the different cards, a different D-channel protocol, or
22594 non-standard IRQ/port settings.
22596 Eicon.Diehl Diva cards
22597 CONFIG_HISAX_DIEHLDIVA
22598 This enables HiSax support for the Eicon.Diehl Diva none PRO
22599 versions passive ISDN cards.
22601 See <file:Documentation/isdn/README.HiSax> on how to configure it
22602 using the different cards, a different D-channel protocol, or
22603 non-standard IRQ/port settings.
22606 CONFIG_HISAX_ASUSCOM
22607 This enables HiSax support for the AsusCom and their OEM versions
22608 passive ISDN ISA cards.
22610 See <file:Documentation/isdn/README.HiSax> on how to configure it
22611 using the different cards, a different D-channel protocol, or
22612 non-standard IRQ/port settings.
22615 CONFIG_HISAX_TELEINT
22616 This enables HiSax support for the TELEINT SA1 semiactiv ISDN card.
22618 See <file:Documentation/isdn/README.HiSax> on how to configure it
22619 using the different cards, a different D-channel protocol, or
22620 non-standard IRQ/port settings.
22624 This enables HiSax support for the HFC-S 2BDS0 based cards, like
22627 See <file:Documentation/isdn/README.HiSax> on how to configure it
22628 using the different cards, a different D-channel protocol, or
22629 non-standard IRQ/port settings.
22632 CONFIG_HISAX_SEDLBAUER
22633 This enables HiSax support for the Sedlbauer passive ISDN cards.
22635 See <file:Documentation/isdn/README.HiSax> on how to configure it
22636 using the different cards, a different D-channel protocol, or
22637 non-standard IRQ/port settings.
22639 USR Sportster internal TA
22640 CONFIG_HISAX_SPORTSTER
22641 This enables HiSax support for the USR Sportster internal TA card.
22643 See <file:Documentation/isdn/README.HiSax> on how to configure it
22644 using a different D-channel protocol, or non-standard IRQ/port
22649 This enables HiSax support for the ITH MIC card.
22651 See <file:Documentation/isdn/README.HiSax> on how to configure it
22652 using a different D-channel protocol, or non-standard IRQ/port
22656 CONFIG_HISAX_NETJET
22657 This enables HiSax support for the NetJet from Traverse
22660 See <file:Documentation/isdn/README.HiSax> on how to configure it
22661 using a different D-channel protocol, or non-standard IRQ/port
22665 CONFIG_HISAX_NETJET_U
22666 This enables HiSax support for the Netspider U interface ISDN card
22667 from Traverse Technologies.
22668 See <file:Documentation/isdn/README.HiSax> on how to configure it
22669 using a different D-channel protocol, or non-standard IRQ/port
22674 This enables HiSax support for the Dr. Neuhaus Niccy PnP or PCI.
22676 See <file:Documentation/isdn/README.HiSax> on how to configure it
22677 using a different D-channel protocol, or non-standard IRQ/port
22680 Siemens I-Surf card
22682 This enables HiSax support for the Siemens I-Talk/I-Surf card with
22684 See <file:Documentation/isdn/README.HiSax> on how to configure it
22685 using a different D-channel protocol, or non-standard IRQ/port
22689 CONFIG_HISAX_HSTSAPHIR
22690 This enables HiSax support for the HST Saphir card.
22692 See <file:Documentation/isdn/README.HiSax> on how to configure it
22693 using a different D-channel protocol, or non-standard IRQ/port
22697 CONFIG_HISAX_BKM_A4T
22698 This enables HiSax support for the Telekom A4T card.
22700 See <file:Documentation/isdn/README.HiSax> on how to configure it
22701 using a different D-channel protocol, or non-standard IRQ/port
22705 CONFIG_HISAX_SCT_QUADRO
22706 This enables HiSax support for the Scitel Quadro card.
22708 See <file:Documentation/isdn/README.HiSax> on how to configure it
22709 using a different D-channel protocol, or non-standard IRQ/port
22714 This enables HiSax support for the Gazel cards.
22716 See <file:Documentation/isdn/README.HiSax> on how to configure it
22717 using a different D-channel protocol, or non-standard IRQ/port
22721 CONFIG_HISAX_HFC_PCI
22722 This enables HiSax support for the HFC-S PCI 2BDS0 based cards.
22724 For more informations see under
22725 <file:Documentation/isdn/README.hfc-pci>.
22727 Winbond W6692 based cards
22729 This enables HiSax support for Winbond W6692 based PCI ISDN cards.
22731 See <file:Documentation/isdn/README.HiSax> on how to configure it
22732 using a different D-channel protocol, or non-standard IRQ/port
22735 HFC-S+, HFC-SP, HFC-PCMCIA cards
22736 CONFIG_HISAX_HFC_SX
22737 This enables HiSax support for the HFC-S+, HFC-SP and HFC-PCMCIA
22738 cards. This code is not finished yet.
22740 Formula-n enter:now PCI card (EXPERIMENTAL)
22741 CONFIG_HISAX_ENTERNOW_PCI
22742 This enables HiSax support for the Formula-n enter:now PCI
22746 CONFIG_HISAX_AMD7930
22747 This enables HiSax support for the AMD7930 chips on some SPARCs.
22748 This code is not finished yet.
22752 This enables debugging code in the new-style HiSax drivers, i.e.
22753 the ST5481 USB driver currently.
22754 If in doubt, say yes.
22756 ELSA PCMCIA MicroLink cards
22757 CONFIG_HISAX_ELSA_CS
22758 This enables the PCMCIA client driver for the Elsa PCMCIA MicroLink
22761 If you want to compile the driver as a module ( = code which can be
22762 inserted in and removed from the running kernel whenever you want),
22763 say M here and read <file:Documentation/modules.txt>. The module
22764 will be called elsa_cs.o.
22766 Sedlbauer PCMCIA cards
22767 CONFIG_HISAX_SEDLBAUER_CS
22768 This enables the PCMCIA client driver for the Sedlbauer Speed Star
22769 and Speed Star II cards.
22771 If you want to compile the driver as a module ( = code which can be
22772 inserted in and removed from the running kernel whenever you want),
22773 say M here and read <file:Documentation/modules.txt>. The module
22774 will be called sedlbauer_cs.o.
22776 CONFIG_HISAX_AVM_A1_CS
22777 This enables the PCMCIA client driver for the AVM A1 / Fritz!Card
22780 If you want to compile the driver as a module ( = code which can be
22781 inserted in and removed from the running kernel whenever you want),
22782 say M here and read <file:Documentation/modules.txt>. The module
22783 will be called avma1_cs.o.
22785 ST5481 USB ISDN modem
22786 CONFIG_HISAX_ST5481
22787 This enables the driver for ST5481 based USB ISDN adapters,
22788 e.g. the BeWan Gazel 128 USB
22791 CONFIG_ISDN_DRV_PCBIT
22792 This enables support for the PCBIT ISDN-card. This card is
22793 manufactured in Portugal by Octal. For running this card,
22794 additional firmware is necessary, which has to be downloaded into
22795 the card using a utility which is distributed separately. See
22796 <file:Documentation/isdn/README> and
22797 <file:Documentation/isdn/README.pcbit> for more information.
22799 If you want to compile this as a module ( = code which can be
22800 inserted in and removed from the running kernel whenever you want),
22801 say M here and read <file:Documentation/modules.txt>. The module
22802 will be called pcbit.o.
22804 Spellcaster support
22806 This enables support for the Spellcaster BRI ISDN boards. This
22807 driver currently builds only in a modularized version ( = code which
22808 can be inserted in and removed from the running kernel whenever you
22809 want, details in <file:Documentation/modules.txt>); the module will
22810 be called sc.o. See <file:Documentation/isdn/README.sc> and
22811 <http://www.spellcast.com/> for more information.
22813 Eicon active card support
22814 CONFIG_ISDN_DRV_EICON
22815 Say Y here if you have an Eicon active ISDN card. In order to use
22816 this card, additional firmware is necessary, which has to be loaded
22817 into the card using the eiconctrl utility which is part of the
22818 latest isdn4k-utils package. Please read the file
22819 <file:Documentation/isdn/README.eicon> for more information.
22821 Legacy Eicon driver
22822 CONFIG_ISDN_DRV_EICON_OLD
22823 Say Y here to use your Eicon active ISDN card with ISDN4Linux
22826 If you want to compile the driver as a module ( = code which can be
22827 inserted in and removed from the running kernel whenever you want),
22828 say M here and read <file:Documentation/modules.txt>. The module
22829 will be called eicon.o.
22831 Eicon PCI DIVA Server BRI/PRI/4BRI support
22832 CONFIG_ISDN_DRV_EICON_PCI
22833 Say Y here if you have an Eicon Diva Server (BRI/PRI/4BRI) ISDN
22834 card. Please read <file:Documentation/isdn/README.eicon> for more
22837 Eicon old-type (S,SX,SCOM,Quadro,S2M) card support
22838 CONFIG_ISDN_DRV_EICON_ISA
22839 Say Y here if you have an old-type Eicon active ISDN card. In order
22840 to use this card, additional firmware is necessary, which has to be
22841 loaded into the card using the eiconctrl utility which is part of
22842 the latest isdn4k-utils package. Please read the file
22843 <file:Documentation/isdn/README.eicon> for more information.
22845 Eicon driver type standalone
22846 CONFIG_ISDN_DRV_EICON_DIVAS
22847 Enable this option if you want the eicon driver as standalone
22848 version with no interface to the ISDN4Linux isdn module. If you
22849 say Y here, the eicon module only supports the Diva Server PCI
22850 cards and will provide its own IDI interface. You should say N
22853 If you want to compile the driver as a module ( = code which can be
22854 inserted in and removed from the running kernel whenever you want),
22855 say M here and read <file:Documentation/modules.txt>. The module
22856 will be called divas.o.
22858 Support AT-Fax Class 1 and 2 commands
22859 CONFIG_ISDN_TTY_FAX
22860 If you say Y here, the modem-emulator will support a subset of the
22861 Fax Class 1 and 2 commands. Using a getty with fax-support
22862 (mgetty+sendfax, hylafax), you will be able to use your Linux box as
22863 an ISDN-fax-machine. This must be supported by the lowlevel driver
22864 also. See <file:Documentation/isdn/README.fax> for more information.
22868 This provides the CAPI (Common ISDN Application Programming
22869 Interface, a standard making it easy for programs to access ISDN
22870 hardware, see <http://www.capi.org/>. This is needed for AVM's set
22871 of active ISDN controllers like B1, T1, M1.
22873 This code is also available as a module ( = code which can be
22874 inserted in and removed from the running kernel whenever you want).
22875 The modules will be called capi.o and kernelcapi.o. If you want to
22876 compile it as a module, say M here and read
22877 <file:Documentation/modules.txt>.
22879 CAPI2.0 /dev/capi20 support
22880 CONFIG_ISDN_CAPI_CAPI20
22881 This option will provide the CAPI 2.0 interface to userspace
22882 applications via /dev/capi20. Applications should use the
22883 standardized libcapi20 to access this functionality. You should say
22886 If you want to compile the driver as a module ( = code which can be
22887 inserted in and removed from the running kernel whenever you want),
22888 say M here and read <file:Documentation/modules.txt>. The module
22889 will be called capi.o.
22891 CAPI2.0 Middleware support
22892 CONFIG_ISDN_CAPI_MIDDLEWARE
22893 This option will enhance the capabilities of the /dev/capi20
22894 interface. It will provide a means of moving a data connection,
22895 established via the usual /dev/capi20 interface to a special tty
22896 device. If you want to use pppd with pppdcapiplugin to dial up to
22897 your ISP, say Y here.
22899 CAPI2.0 filesystem support
22900 CONFIG_ISDN_CAPI_CAPIFS
22901 This option provides a special file system, similar to /dev/pts with
22902 device nodes for the special ttys established by using the
22903 middleware extension above. If you want to use pppd with
22904 pppdcapiplugin to dial up to your ISP, say Y here.
22906 CAPI2.0 capidrv interface support
22907 CONFIG_ISDN_CAPI_CAPIDRV
22908 This option provides the glue code to hook up CAPI driven cards to
22909 the legacy isdn4linux link layer. If you have a card which is
22910 supported by a CAPI driver, but still want to use old features like
22911 ippp interfaces or ttyI emulation, say Y/M here.
22913 If you want to compile the driver as a module ( = code which can be
22914 inserted in and removed from the running kernel whenever you want),
22915 say M here and read <file:Documentation/modules.txt>. The module
22916 will be called capidrv.o.
22919 CONFIG_ISDN_DRV_AVMB1_B1ISA
22920 Enable support for the ISA version of the AVM B1 card.
22922 If you want to compile the driver as a module ( = code which can be
22923 inserted in and removed from the running kernel whenever you want),
22924 say M here and read <file:Documentation/modules.txt>. The module
22925 will be called b1isa.o.
22928 CONFIG_ISDN_DRV_AVMB1_B1CICI
22929 Enable support for the PCI version of the AVM B1 card.
22931 AVM B1 PCI V4 support
22932 CONFIG_ISDN_DRV_AVMB1_B1PCIV4
22933 Enable support for the V4 version of AVM B1 PCI card.
22935 AVM T1/T1-B ISA support
22936 CONFIG_ISDN_DRV_AVMB1_T1ISA
22937 Enable support for the AVM T1 T1B card.
22938 Note: This is a PRI card and handle 30 B-channels.
22940 If you want to compile the driver as a module ( = code which can be
22941 inserted in and removed from the running kernel whenever you want),
22942 say M here and read <file:Documentation/modules.txt>. The module
22943 will be called t1isa.o.
22945 AVM B1/M1/M2 PCMCIA support
22946 CONFIG_ISDN_DRV_AVMB1_B1PCMCIA
22947 Enable support for the PCMCIA version of the AVM B1 card.
22949 If you want to compile the driver as a module ( = code which can be
22950 inserted in and removed from the running kernel whenever you want),
22951 say M here and read <file:Documentation/modules.txt>. The module
22952 will be called b1pcmcia.o.
22954 AVM B1/M1/M2 PCMCIA cs module
22955 CONFIG_ISDN_DRV_AVMB1_AVM_CS
22956 Enable the PCMCIA client driver for the AVM B1/M1/M2
22959 If you want to compile the driver as a module ( = code which can be
22960 inserted in and removed from the running kernel whenever you want),
22961 say M here and read <file:Documentation/modules.txt>. The module
22962 will be called avm_cs.o.
22964 AVM T1/T1-B PCI support
22965 CONFIG_ISDN_DRV_AVMB1_T1PCI
22966 Enable support for the AVM T1 T1B card.
22967 Note: This is a PRI card and handle 30 B-channels.
22969 If you want to compile the driver as a module ( = code which can be
22970 inserted in and removed from the running kernel whenever you want),
22971 say M here and read <file:Documentation/modules.txt>. The module
22972 will be called t1pci.o.
22975 CONFIG_ISDN_DRV_AVMB1_C4
22976 Enable support for the AVM C4/C2 PCI cards.
22977 These cards handle 4/2 BRI ISDN lines (8/4 channels).
22979 If you want to compile the driver as a module ( = code which can be
22980 inserted in and removed from the running kernel whenever you want),
22981 say M here and read <file:Documentation/modules.txt>. The module
22982 will be called c4.o.
22984 Verbose reason code reporting (kernel size +=7K)
22985 CONFIG_ISDN_DRV_AVMB1_VERBOSE_REASON
22986 If you say Y here, the AVM B1 driver will give verbose reasons for
22987 disconnecting. This will increase the size of the kernel by 7 KB. If
22990 IBM Active 2000 support
22991 CONFIG_ISDN_DRV_ACT2000
22992 Say Y here if you have an IBM Active 2000 ISDN card. In order to use
22993 this card, additional firmware is necessary, which has to be loaded
22994 into the card using a utility which is part of the latest
22995 isdn4k-utils package. Please read the file
22996 <file:Documentation/isdn/README.act2000> for more information.
22998 If you want to compile the driver as a module ( = code which can be
22999 inserted in and removed from the running kernel whenever you want),
23000 say M here and read <file:Documentation/modules.txt>. The module
23001 will be called act2000.o.
23003 Auvertech TurboPAM support
23004 CONFIG_ISDN_DRV_TPAM
23005 This enables support for the Auvertech TurboPAM ISDN-card.
23006 For running this card, additional firmware is necessary, which has
23007 to be downloaded into the card using a utility which is distributed
23008 separately from the Auvertech's web site: <http://www.auvertech.fr/>.
23010 Please redirect all support questions to support@auvertech.fr.
23012 If you want to compile this as a module ( = code which can be
23013 inserted in and removed from the running kernel whenever you want),
23014 say M here and read <file:Documentation/modules.txt>. The module
23015 will be called tpam.o.
23017 Hypercope HYSDN cards (Champ, Ergo, Metro) support (module)
23019 Say Y here if you have one of Hypercope's active PCI ISDN cards
23020 Champ, Ergo and Metro. You will then get a module called hysdn.o.
23021 Please read the file <file:Documentation/isdn/README.hysdn> for more
23024 If you want to compile the driver as a module ( = code which can be
23025 inserted in and removed from the running kernel whenever you want),
23026 say M here and read <file:Documentation/modules.txt>. The module
23027 will be called hysdn.o.
23029 HYSDN CAPI 2.0 support
23031 Say Y here if you like to use Hypercope's CAPI 2.0 interface.
23033 Support for SUN4 machines (disables SUN4[CDM] support)
23035 Say Y here if, and only if, your machine is a Sun4. Note that
23036 a kernel compiled with this option will run only on Sun4.
23037 (And the current version will probably work only on sun4/330.)
23039 SPARC ESP SCSI support
23041 This is the driver for the Sun ESP SCSI host adapter. The ESP
23042 chipset is present in most SPARC SBUS-based computers.
23044 This support is also available as a module called esp.o ( = code
23045 which can be inserted in and removed from the running kernel
23046 whenever you want). If you want to compile it as a module, say M
23047 here and read <file:Documentation/modules.txt>.
23049 PTI Qlogic, ISP Driver
23050 CONFIG_SCSI_QLOGICPTI
23051 This driver supports SBUS SCSI controllers from PTI or QLogic. These
23052 controllers are known under Solaris as qpti and in the openprom as
23053 PTI,ptisp or QLGC,isp. Note that PCI QLogic SCSI controllers are
23054 driven by a different driver.
23056 This support is also available as a module called qlogicpti.o ( =
23057 code which can be inserted in and removed from the running kernel
23058 whenever you want). If you want to compile it as a module, say M
23059 here and read <file:Documentation/modules.txt>.
23062 CONFIG_PROM_CONSOLE
23063 Say Y to build a console driver for Sun machines that uses the
23064 terminal emulation built into their console PROMS.
23066 /dev/openprom device support
23067 CONFIG_SUN_OPENPROMIO
23068 This driver provides user programs with an interface to the SPARC
23069 PROM device tree. The driver implements a SunOS-compatible
23070 interface and a NetBSD-compatible interface.
23072 If you want to compile this as a module ( = code which can be
23073 inserted in and removed from the running kernel whenever you want),
23074 say M and read <file:Documentation/modules.txt>. If unsure, say Y.
23076 Openprom tree appears in /proc/openprom
23077 CONFIG_SUN_OPENPROMFS
23078 If you say Y, the OpenPROM device tree will be available as a
23079 virtual file system, which you can mount to /proc/openprom by "mount
23080 -t openpromfs none /proc/openprom".
23082 If you want to compile the /proc/openprom support as a module ( =
23083 code which can be inserted in and removed from the running kernel
23084 whenever you want), say M here and read
23085 <file:Documentation/modules.txt>.
23086 The module will be called openpromfs.o. If unsure, say M.
23088 Kernel support for Linux/Sparc 32bit binary compatibility
23089 CONFIG_SPARC32_COMPAT
23090 This allows you to run 32-bit binaries on your Ultra.
23091 Everybody wants this; say Y.
23093 Kernel support for 32-bit ELF binaries
23094 CONFIG_BINFMT_ELF32
23095 This allows you to run 32-bit Linux/ELF binaries on your machine.
23096 Everybody wants this; say Y.
23098 Kernel support for 32-bit (ie. SunOS) a.out binaries
23099 CONFIG_BINFMT_AOUT32
23100 This allows you to run 32-bit a.out format binaries on your Ultra.
23101 If you want to run SunOS binaries (see SunOS binary emulation below)
23102 or other a.out binaries, say Y. If unsure, say N.
23104 SunOS binary emulation
23106 This allows you to run most SunOS binaries. If you want to do this,
23107 say Y here and place appropriate files in /usr/gnemul/sunos. See
23108 <http://www.ultralinux.org/faq.html> for more information. If you
23109 want to run SunOS binaries on an Ultra you must also say Y to
23110 "Kernel support for 32-bit a.out binaries" above.
23112 Mostek real time clock support
23113 CONFIG_SUN_MOSTEK_RTC
23114 The Mostek RTC chip is used on all known Sun computers except
23115 some JavaStations. For a JavaStation you need to say Y both here
23116 and to "Enhanced Real Time Clock Support".
23118 Say Y here unless you are building a special purpose kernel.
23120 OBP Flash Device support
23122 The OpenBoot PROM on Ultra systems is flashable. If you want to be
23123 able to upgrade the OBP firmware, say Y here.
23125 JavaStation OS Flash SIMM
23127 If you say Y here, you will be able to boot from your JavaStation's
23130 Siemens SAB82532 serial support
23132 This driver supports the serial ports on newer (PCI) Ultra systems.
23133 Say Y if you want to be able to use your serial ports.
23135 Videopix Frame Grabber
23136 CONFIG_SUN_VIDEOPIX
23137 Say Y here to support the Videopix Frame Grabber from Sun
23138 Microsystems, commonly found on SPARCstations. This card, which is
23139 based on the Phillips SAA9051, can handle NTSC and PAL/SECAM and
23142 Sun bidirectional parallel port support
23144 Say Y here to support Sun's obsolete variant of IEEE1284
23145 bidirectional parallel port protocol as /dev/bppX. Can be built on
23148 Aurora Multiboard 1600se
23150 The Aurora Multiboard is a multi-port high-speed serial controller.
23151 If you have one of these, say Y.
23153 Tadpole TS102 Microcontroller support
23154 CONFIG_TADPOLE_TS102_UCTRL
23155 Say Y here to directly support the TS102 Microcontroller interface
23156 on the Tadpole Sparcbook 3. This device handles power-management
23157 events, and can also notice the attachment/detachment of external
23162 This driver provides support for the build-in sound devices on most
23163 Sun machines. If you want to be able to use this, select this option
23164 and one or more of the lowlevel drivers below. See
23165 <http://www.dementia.org/~shadow/sparcaudio.html> for more
23168 AMD7930 Lowlevel Driver
23169 CONFIG_SPARCAUDIO_AMD7930
23170 This driver supports the AMD 7930 chip found on sun4c, 4/6xx, and
23171 SparcClassic systems.
23173 CS4231 Lowlevel Driver
23174 CONFIG_SPARCAUDIO_CS4231
23175 This driver supports the Crystal Semiconductor CS4231 chip found on
23176 the SS4, SS5, and Ultras.
23178 DBRI Lowlevel Driver
23179 CONFIG_SPARCAUDIO_DBRI
23180 This driver supports the DBRI audio interface found on the SS10,
23181 SS20, LX, Sparcbook 3, and Voyager systems.
23183 Dummy Lowlevel Driver
23184 CONFIG_SPARCAUDIO_DUMMY
23185 This is a pseudo-driver used for debugging and testing the
23186 sparcaudio subsystem. Say N unless you want to work on this
23190 CONFIG_PARPORT_SUNBPP
23191 This driver provides support for the bidirectional parallel port
23192 found on many Sun machines. Note that many of the newer Ultras
23193 actually have pc style hardware instead.
23195 SPARC power management support
23197 Enable power management and CPU standby features on supported
23200 /proc/hardware support
23201 CONFIG_PROC_HARDWARE
23202 Say Y here to support the /proc/hardware file, which gives you
23203 access to information about the machine you're running on,
23204 including the model, CPU, MMU, clock speed, BogoMIPS rating,
23207 Bluetooth subsystem support
23209 Bluetooth is low-cost, low-power, short-range wireless technology.
23210 It was designed as a replacement for cables and other short-range
23211 technologies like IrDA. Bluetooth operates in personal area range
23212 that typically extends up to 10 meters. More information about
23213 Bluetooth can be found at <http://www.bluetooth.com/>.
23215 Linux Bluetooth subsystem consist of several layers:
23216 BlueZ Core (HCI device and connection manager, scheduler)
23217 HCI Device drivers (Interface to the hardware)
23218 SCO Module (SCO audio links)
23219 L2CAP Module (Logical Link Control and Adaptation Protocol)
23220 RFCOMM Module (RFCOMM Protocol)
23221 BNEP Module (Bluetooth Network Encapsulation Protocol)
23222 CMTP Module (CAPI Message Transport Protocol)
23224 Say Y here to compile Bluetooth support into the kernel or say M to
23225 compile it as module (bluez.o).
23227 To use Linux Bluetooth subsystem, you will need several user-space
23228 utilities like hciconfig and hcid. These utilities and updates to
23229 Bluetooth kernel modules are provided in the BlueZ package.
23230 For more information, see <http://www.bluez.org/>.
23232 L2CAP protocol support
23234 L2CAP (Logical Link Control and Adaptation Protocol) provides
23235 connection oriented and connection-less data transport. L2CAP
23236 support is required for most Bluetooth applications.
23238 Say Y here to compile L2CAP support into the kernel or say M to
23239 compile it as module (l2cap.o).
23243 SCO link provides voice transport over Bluetooth. SCO support is
23244 required for voice applications like Headset and Audio.
23246 Say Y here to compile SCO support into the kernel or say M to
23247 compile it as module (sco.o).
23249 RFCOMM protocol support
23250 CONFIG_BLUEZ_RFCOMM
23251 RFCOMM provides connection oriented stream transport. RFCOMM
23252 support is required for Dialup Networking, OBEX and other Bluetooth
23255 Say Y here to compile RFCOMM support into the kernel or say M to
23256 compile it as module (rfcomm.o).
23258 RFCOMM TTY emulation support
23259 CONFIG_BLUEZ_RFCOMM_TTY
23260 This option enables TTY emulation support for RFCOMM channels.
23262 BNEP protocol support
23264 BNEP (Bluetooth Network Encapsulation Protocol) is Ethernet
23265 emulation layer on top of Bluetooth. BNEP is required for
23266 Bluetooth PAN (Personal Area Network).
23268 Say Y here to compile BNEP support into the kernel or say M to
23269 compile it as module (bnep.o).
23271 BNEP multicast filter support
23272 CONFIG_BLUEZ_BNEP_MC_FILTER
23273 This option enables the multicast filter support for BNEP.
23275 BNEP protocol filter support
23276 CONFIG_BLUEZ_BNEP_PROTO_FILTER
23277 This option enables the protocol filter support for BNEP.
23279 CMTP protocol support
23281 CMTP (CAPI Message Transport Protocol) is a transport layer
23282 for CAPI messages. CMTP is required for the Bluetooth Common
23283 ISDN Access Profile.
23285 Say Y here to compile CMTP support into the kernel or say M to
23286 compile it as module (cmtp.o).
23289 CONFIG_BLUEZ_HCIUART
23290 Bluetooth HCI UART driver.
23291 This driver is required if you want to use Bluetooth devices with
23292 serial port interface. You will also need this driver if you have
23293 UART based Bluetooth PCMCIA and CF devices like Xircom Credit Card
23294 adapter and BrainBoxes Bluetooth PC Card.
23296 Say Y here to compile support for Bluetooth UART devices into the
23297 kernel or say M to compile it as module (hci_uart.o).
23299 HCI UART (H4) protocol support
23300 CONFIG_BLUEZ_HCIUART_H4
23301 UART (H4) is serial protocol for communication between Bluetooth
23302 device and host. This protocol is required for most Bluetooth devices
23303 with UART interface, including PCMCIA and CF cards.
23305 Say Y here to compile support for HCI UART (H4) protocol.
23307 HCI BCSP protocol support
23308 CONFIG_BLUEZ_HCIUART_BCSP
23309 BCSP (BlueCore Serial Protocol) is serial protocol for communication
23310 between Bluetooth device and host. This protocol is required for non
23311 USB Bluetooth devices based on CSR BlueCore chip, including PCMCIA and
23314 Say Y here to compile support for HCI BCSP protocol.
23316 HCI BCSP transmit CRC with every BCSP packet
23317 CONFIG_BLUEZ_HCIUART_BCSP_TXCRC
23318 If you say Y here, a 16-bit CRC checksum will be transmitted along with
23319 every BCSP (BlueCore Serial Protocol) packet sent to the Bluetooth chip.
23320 This increases reliability, but slightly reduces efficiency.
23323 CONFIG_BLUEZ_HCIUSB
23324 Bluetooth HCI USB driver.
23325 This driver is required if you want to use Bluetooth devices with
23328 Say Y here to compile support for Bluetooth USB devices into the
23329 kernel or say M to compile it as module (hci_usb.o).
23331 HCI USB SCO (voice) support
23332 CONFIG_BLUEZ_HCIUSB_SCO
23333 This option enables the SCO support in the HCI USB driver. You need this
23334 to transmit voice data with your Bluetooth USB device. And your device
23335 must also support sending SCO data over the HCI layer, because some of
23336 them sends the SCO data to an internal PCM adapter.
23338 Say Y here to compile support for HCI SCO data.
23340 HCI VHCI Virtual HCI device driver
23341 CONFIG_BLUEZ_HCIVHCI
23342 Bluetooth Virtual HCI device driver.
23343 This driver is required if you want to use HCI Emulation software.
23345 Say Y here to compile support for virtual HCI devices into the
23346 kernel or say M to compile it as module (hci_vhci.o).
23348 HCI BFUSB device driver
23349 CONFIG_BLUEZ_HCIBFUSB
23350 Bluetooth HCI BlueFRITZ! USB driver.
23351 This driver provides support for Bluetooth USB devices with AVM
23355 Say Y here to compile support for HCI BFUSB devices into the
23356 kernel or say M to compile it as module (bfusb.o).
23358 HCI DTL1 (PC Card) device driver
23359 CONFIG_BLUEZ_HCIDTL1
23360 Bluetooth HCI DTL1 (PC Card) driver.
23361 This driver provides support for Bluetooth PCMCIA devices with
23362 Nokia DTL1 interface:
23363 Nokia Bluetooth Card
23364 Socket Bluetooth CF Card
23366 Say Y here to compile support for HCI DTL1 devices into the
23367 kernel or say M to compile it as module (dtl1_cs.o).
23369 HCI BT3C (PC Card) device driver
23370 CONFIG_BLUEZ_HCIBT3C
23371 Bluetooth HCI BT3C (PC Card) driver.
23372 This driver provides support for Bluetooth PCMCIA devices with
23373 3Com BT3C interface:
23374 3Com Bluetooth Card (3CRWB6096)
23377 Say Y here to compile support for HCI BT3C devices into the
23378 kernel or say M to compile it as module (bt3c_cs.o).
23380 HCI BlueCard (PC Card) device driver
23381 CONFIG_BLUEZ_HCIBLUECARD
23382 Bluetooth HCI BlueCard (PC Card) driver.
23383 This driver provides support for Bluetooth PCMCIA devices with
23384 Anycom BlueCard interface:
23385 Anycom Bluetooth PC Card
23386 Anycom Bluetooth CF Card
23388 Say Y here to compile support for HCI BlueCard devices into the
23389 kernel or say M to compile it as module (bluecard_cs.o).
23391 HCI UART (PC Card) device driver
23392 CONFIG_BLUEZ_HCIBTUART
23393 Bluetooth HCI UART (PC Card) driver.
23394 This driver provides support for Bluetooth PCMCIA devices with
23396 Xircom CreditCard Bluetooth Adapter
23397 Xircom RealPort2 Bluetooth Adapter
23400 Cyber-blue Compact Flash Card
23402 Say Y here to compile support for HCI UART devices into the
23403 kernel or say M to compile it as module (btuart_cs.o).
23405 # The following options are for Linux when running on the Hitachi
23406 # SuperH family of RISC microprocessors.
23410 Selecting this option will allow the Linux kernel to emulate
23415 SuperH peripheral clock frequency
23416 CONFIG_SH_PCLK_FREQ
23417 Set this value or add "sh_pclk=" command line option to tell
23418 peripheral clock frequency to kernel, if your system has no RTC.
23419 Otherwise leave it 0, and kernel measures peripheral clock frequency
23420 using TMU and RTC while system startup.
23424 Wakeup UBC on startup
23426 Selecting this option will wakeup the User Break Controller (UBC) on
23427 startup. Although the UBC is left in an awake state when the processor
23428 comes up, some boot loaders misbehave by putting the UBC to sleep in a
23429 power saving state, which causes issues with things like ptrace().
23433 SuperH DMAC support
23435 Selecting this option will provide same API as PC's Direct Memory
23436 Access Controller(8237A) for SuperH DMAC.
23441 CompactFlash Connection Area
23443 If your board has "Directly Connected" CompactFlash, You should
23444 select the area where your CF is connected to.
23446 - "Area5" if CompactFlash is connected to Area 5 (0x14000000)
23447 - "Area6" if it is connected to Area 6 (0x18000000)
23449 "Area6" will work for most boards. For ADX, select "Area5".
23452 CONFIG_DCACHE_DISABLE
23453 This option allows you to run the kernel with data cache disabled.
23454 Say Y if you experience CPM lock-ups.
23457 # m68k-specific kernel options
23458 # Documented by Chris Lawrence <mailto:quango@themall.net> et al.
23462 This option enables support for the Amiga series of computers. If
23463 you plan to use this kernel on an Amiga, say Y here and browse the
23464 material available in <file:Documentation/m68k>; otherwise say N.
23466 Commodore A2232 serial support
23468 This option supports the 2232 7-port serial card shipped with the
23469 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
23470 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
23471 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
23472 ports were connected with 8 pin DIN connectors on the card bracket,
23473 for which 8 pin to DB25 adapters were supplied. The card also had
23474 jumpers internally to toggle various pinning configurations.
23476 This driver can be built as a module; but then "generic_serial.o"
23477 will also be built as a module. This has to be loaded before
23478 "ser_a2232.o". If you want to do this, answer M here and read
23479 "<file:Documentation/modules.txt>".
23481 Amiga NCR53c710 SCSI support
23482 CONFIG_SCSI_AMIGA7XX
23483 Support for various NCR53c710-based SCSI controllers on the Amiga.
23485 - the builtin SCSI controller on the Amiga 4000T,
23486 - the Amiga 4091 Zorro III SCSI-2 controller,
23487 - the MacroSystem Development's WarpEngine Amiga SCSI-2 controller
23489 <http://www.lysator.liu.se/amiga/ar/guide/ar310.guide?FEATURE5>),
23490 - the SCSI controller on the Phase5 Blizzard PowerUP 603e+
23491 accelerator card for the Amiga 1200,
23492 - the SCSI controller on the GVP Turbo 040/060 accelerator.
23493 Note that all of the above SCSI controllers, except for the builtin
23494 SCSI controller on the Amiga 4000T, reside on the Zorro expansion
23495 bus, so you also have to enable Zorro bus support if you want to use
23500 This option enables support for the 68000-based Atari series of
23501 computers (including the TT, Falcon and Medusa). If you plan to use
23502 this kernel on an Atari, say Y here and browse the material
23503 available in <file:Documentation/m68k>; otherwise say N.
23507 This option enables support for the Hades Atari clone. If you plan
23508 to use this kernel on a Hades, say Y here; otherwise say N.
23512 This option enables support for the Apple Macintosh series of
23513 computers (yes, there is experimental support now, at least for part
23516 Say N unless you're willing to code the remaining necessary support.
23521 This option enables support for the HP9000/300 series of
23522 workstations. Support for these machines is still very experimental.
23523 If you plan to try to use the kernel on such a machine say Y here.
23524 Everybody else says N.
23528 The Q40 is a Motorola 68040-based successor to the Sinclair QL
23529 manufactured in Germany. There is an official Q40 home page at
23530 <http://www.q40.de/>. This option enables support for the Q40 and
23531 Q60. Select your CPU below. For 68LC060 don't forget to enable FPU
23534 Q40/Q60 IDE interface support
23535 CONFIG_BLK_DEV_Q40IDE
23536 Enable the on-board IDE controller in the Q40/Q60. This should
23537 normally be on; disable it only if you are running a custom hard
23538 drive subsystem through an expansion card.
23542 This option enables support for the Sun 3 series of workstations.
23543 Note that if this option is enabled, support for all other m68k
23544 platforms above must be disabled in order to produce a working
23547 Also, you will want to enable 68020 support below, and disable
23548 all other CPU types. General Linux information on the Sun 3x series
23549 (now discontinued) is at
23550 <http://www.angelfire.com/ca2/tech68k/sun3.html>.
23552 If you don't want to compile a kernel for a Sun 3, say N.
23556 This option enables support for the Sun 3x series of workstations.
23557 Currently, only the Sun 3/80 is supported within the Sun 3x family.
23558 You will also want to enable 68030 support below
23559 General Linux information on the Sun 3x series (now discontinued)
23560 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
23562 If you don't want to compile a kernel for a Sun 3x, say N.
23564 Sun3x builtin serial support
23566 ZS refers to a type of asynchronous serial port built in to the Sun3
23567 and Sun3x workstations; if you have a Sun 3, you probably have
23568 these. Say 'Y' to support ZS ports directly. This option must be
23569 enabled in order to support the keyboard and mouse ports.
23571 Sun keyboard support
23572 CONFIG_SUN_KEYBOARD
23573 Say Y here to support the keyboard found on Sun 3 and 3x
23574 workstations. It can also be used support Sun Type-5 keyboards
23575 through an adaptor. See
23576 <http://www.suse.cz/development/input/adapters.html> and
23577 <http://sourceforge.net/projects/linuxconsole/> for details on the
23582 If you anticipate running this kernel on a computer with a MC68020
23583 processor, say Y. Otherwise, say N. Note that the 68020 requires a
23584 68851 MMU (Memory Management Unit) to run Linux/m68k, except on the
23585 Sun 3, which provides its own version.
23589 If you anticipate running this kernel on a computer with a MC68030
23590 processor, say Y. Otherwise, say N. Note that a MC68EC030 will not
23591 work, as it does not include an MMU (Memory Management Unit).
23595 If you anticipate running this kernel on a computer with a MC68LC040
23596 or MC68040 processor, say Y. Otherwise, say N. Note that an
23597 MC68EC040 will not work, as it does not include an MMU (Memory
23602 If you anticipate running this kernel on a computer with a MC68060
23603 processor, say Y. Otherwise, say N.
23605 Math emulation support
23607 At some point in the future, this will cause floating-point math
23608 instructions to be emulated by the kernel on machines that lack a
23609 floating-point math coprocessor. Thrill-seekers and chronically
23610 sleep-deprived psychotic hacker types can say Y now, everyone else
23611 should probably wait a while.
23613 Math emulation only kernel
23614 CONFIG_M68KFPU_EMU_ONLY
23615 This option prevents any floating-point instructions from being
23616 compiled into the kernel, thereby the kernel doesn't save any
23617 floating point context anymore during task switches, so this
23618 kernel will only be usable on machines without a floating-point
23619 math coprocessor. This makes the kernel a bit faster as no tests
23620 needs to be executed whether a floating-point instruction in the
23621 kernel should be executed or not.
23623 Math emulation extra precision
23624 CONFIG_M68KFPU_EMU_EXTRAPREC
23625 The fpu uses normally a few bit more during calculations for
23626 correct rounding, the emulator can (often) do the same but this
23627 extra calculation can cost quite some time, so you can disable
23628 it here. The emulator will then "only" calculate with a 64 bit
23629 mantissa and round slightly incorrect, what is more then enough
23632 Advanced configuration options
23634 This gives you access to some advanced options for the CPU. The
23635 defaults should be fine for most users, but these options may make
23636 it possible for you to improve performance somewhat if you know what
23639 Note that the answer to this question won't directly affect the
23640 kernel: saying N will just cause the configurator to skip all
23641 the questions about these options.
23643 Most users should say N to this question.
23645 Use one physical chunk of memory only
23646 CONFIG_SINGLE_MEMORY_CHUNK
23647 Ignore all but the first contiguous chunk of physical memory for VM
23648 purposes. This will save a few bytes kernel size and may speed up
23649 some operations. Say N if not sure.
23651 Use read-modify-write instructions
23653 This allows to use certain instructions that work with indivisible
23654 read-modify-write bus cycles. While this is faster than the
23655 workaround of disabling interrupts, it can conflict with DMA
23656 ( = direct memory access) on many Amiga systems, and it is also said
23657 to destabilize other machines. It is very likely that this will
23658 cause serious problems on any Amiga or Atari Medusa if set. The only
23659 configuration where it should work are 68030-based Ataris, where it
23660 apparently improves performance. But you've been warned! Unless you
23661 really know what you are doing, say N. Try Y only if you're quite
23664 Amiga Zorro (AutoConfig) bus support
23666 This enables support for the Zorro bus in the Amiga. If you have
23667 expansion cards in your Amiga that conform to the Amiga
23668 AutoConfig(tm) specification, say Y, otherwise N. Note that even
23669 expansion cards that do not fit in the Zorro slots but fit in e.g.
23670 the CPU slot may fall in this category, so you have to say Y to let
23673 Zorro device name database
23675 By default, the kernel contains a database of all known Zorro device
23676 names to make the information in /proc/iomem comprehensible to the
23677 user. This database increases the size of the kernel image by about
23678 15KB, but it gets freed after the system boots up, so it doesn't
23679 take up kernel memory. Anyway, if you are building an installation
23680 floppy or kernel for an embedded system where kernel image size
23681 really matters, you can disable this feature and you'll get device
23682 ID numbers instead of names.
23684 When in doubt, say Y.
23686 Amiga 1200/600 PCMCIA support
23687 CONFIG_AMIGA_PCMCIA
23688 Include support in the kernel for pcmcia on Amiga 1200 and Amiga
23689 600. If you intend to use pcmcia cards say Y; otherwise say N.
23691 Hisoft Whippet PCMCIA serial support
23692 CONFIG_WHIPPET_SERIAL
23693 HiSoft has a web page at <http://www.hisoft.co.uk/>, but there
23694 is no listing for the Whippet in their Amiga section.
23696 Amiga Zorro II ramdisk support
23698 This enables support for using Chip RAM and Zorro II RAM as a
23699 ramdisk or as a swap partition. Say Y if you want to include this
23700 driver in the kernel. This driver is also available as a module
23701 ( = code which can be inserted in and removed from the running
23702 kernel whenever you want). The module is called z2ram.o. If you want
23703 to compile it as a module, say M here and read
23704 <file:Documentation/modules.txt>.
23706 Support for ST-RAM as swap space
23708 Some Atari 68k machines (including the 520STF and 1020STE) divide
23709 their addressable memory into ST and TT sections. The TT section
23710 (up to 512MB) is the main memory; the ST section (up to 4MB) is
23711 accessible to the built-in graphics board, runs slower, and is
23712 present mainly for backward compatibility with older machines.
23714 This enables support for using (parts of) ST-RAM as swap space,
23715 instead of as normal system memory. This can first enhance system
23716 performance if you have lots of alternate RAM (compared to the size
23717 of ST-RAM), because executable code always will reside in faster
23718 memory. ST-RAM will remain as ultra-fast swap space. On the other
23719 hand, it allows much improved dynamic allocations of ST-RAM buffers
23720 for device driver modules (e.g. floppy, ACSI, SLM printer, DMA
23721 sound). The probability that such allocations at module load time
23722 fail is drastically reduced.
23724 ST-RAM statistics in /proc
23726 Say Y here to report ST-RAM usage statistics in /proc/stram. See
23727 the help for CONFIG_STRAM_SWAP for discussion of ST-RAM and its
23732 This enables support for the Atari ACSI interface. The driver
23733 supports hard disks and CD-ROMs, which have 512-byte sectors, or can
23734 be switched to that mode. Due to the ACSI command format, only disks
23735 up to 1 GB are supported. Special support for certain ACSI to SCSI
23736 adapters, which could relax that, isn't included yet. The ACSI
23737 driver is also the basis for certain other drivers for devices
23738 attached to the ACSI bus: Atari SLM laser printer, BioNet-100
23739 Ethernet, and PAMsNet Ethernet. If you want to use one of these
23740 devices, you need ACSI support, too.
23742 This driver is also available as a module ( = code which can be
23743 inserted in and removed from the running kernel whenever you want).
23744 The module will be called acsi.o.
23746 Probe all LUNs on each ACSI device
23747 CONFIG_ACSI_MULTI_LUN
23748 If you have a ACSI device that supports more than one LUN (Logical
23749 Unit Number), e.g. a CD jukebox, you should say Y here so that all
23750 will be found by the ACSI driver. An ACSI device with multiple LUNs
23751 acts logically like multiple ACSI devices. The vast majority of ACSI
23752 devices have only one LUN, and so most people can say N here and
23753 should in fact do so, because it is safer.
23755 Atari SLM laser printer support
23757 If you have an Atari SLM laser printer, say Y to include support for
23758 it in the kernel. Otherwise, say N. This driver is also available as
23759 a module ( = code which can be inserted in and removed from the
23760 running kernel whenever you want). The module will be called
23761 acsi_slm.o. Be warned: the driver needs much ST-RAM and can cause
23762 problems due to that fact!
23764 A3000 WD33C93A support
23766 If you have an Amiga 3000 and have SCSI devices connected to the
23767 built-in SCSI controller, say Y. Otherwise, say N. This driver is
23768 also available as a module ( = code which can be inserted in and
23769 removed from the running kernel whenever you want). The module is
23770 called wd33c93.o. If you want to compile it as a module, say M here
23771 and read <file:Documentation/modules.txt>.
23773 A2091 WD33C93A support
23775 If you have a Commodore A2091 SCSI controller, say Y. Otherwise,
23776 say N. This driver is also available as a module ( = code which can
23777 be inserted in and removed from the running kernel whenever you
23778 want). The module is called wd33c93.o. If you want to compile it as
23779 a module, say M here and read <file:Documentation/modules.txt>.
23781 GVP Series II WD33C93A support
23783 If you have a Great Valley Products Series II SCSI controller,
23784 answer Y. Also say Y if you have a later model of GVP SCSI
23785 controller (such as the GVP A4008 or a Combo board). Otherwise,
23786 answer N. This driver does NOT work for the T-Rex series of
23787 accelerators from TekMagic and GVP-M.
23789 This driver is also available as a module ( = code which can be
23790 inserted in and removed from the running kernel whenever you
23791 want). The module will be called gvp11.o. If you want to compile it
23792 as a module, say M here and read <file:Documentation/modules.txt>.
23794 CyberStorm SCSI support
23795 CONFIG_CYBERSTORM_SCSI
23796 If you have an Amiga with an original (MkI) Phase5 Cyberstorm
23797 accelerator board and the optional Cyberstorm SCSI controller,
23798 answer Y. Otherwise, say N.
23800 CyberStorm II SCSI support
23801 CONFIG_CYBERSTORMII_SCSI
23802 If you have an Amiga with a Phase5 Cyberstorm MkII accelerator board
23803 and the optional Cyberstorm SCSI controller, say Y. Otherwise,
23806 Blizzard 2060 SCSI support
23807 CONFIG_BLZ2060_SCSI
23808 If you have an Amiga with a Phase5 Blizzard 2060 accelerator board
23809 and want to use the onboard SCSI controller, say Y. Otherwise,
23812 Blizzard 1230IV/1260 SCSI support
23813 CONFIG_BLZ1230_SCSI
23814 If you have an Amiga 1200 with a Phase5 Blizzard 1230IV or Blizzard
23815 1260 accelerator, and the optional SCSI module, say Y. Otherwise,
23818 Fastlane SCSI support
23819 CONFIG_FASTLANE_SCSI
23820 If you have the Phase5 Fastlane Z3 SCSI controller, or plan to use
23821 one in the near future, say Y to this question. Otherwise, say N.
23823 BSC Oktagon SCSI support
23824 CONFIG_OKTAGON_SCSI
23825 If you have the BSC Oktagon SCSI disk controller for the Amiga, say
23826 Y to this question. If you're in doubt about whether you have one,
23828 <http://amiga.resource.cx/exp/search.pl?product=oktagon>.
23830 Atari native SCSI support
23832 If you have an Atari with built-in NCR5380 SCSI controller (TT,
23833 Falcon, ...) say Y to get it supported. Of course also, if you have
23834 a compatible SCSI controller (e.g. for Medusa). This driver is also
23835 available as a module ( = code which can be inserted in and removed
23836 from the running kernel whenever you want). The module is called
23837 atari_scsi.o. If you want to compile it as a module, say M here and
23838 read <file:Documentation/modules.txt>. This driver supports both
23839 styles of NCR integration into the system: the TT style (separate
23840 DMA), and the Falcon style (via ST-DMA, replacing ACSI). It does
23841 NOT support other schemes, like in the Hades (without DMA).
23843 Long delays for Toshiba CD-ROMs
23844 CONFIG_ATARI_SCSI_TOSHIBA_DELAY
23845 This option increases the delay after a SCSI arbitration to
23846 accommodate some flaky Toshiba CD-ROM drives. Say Y if you intend to
23847 use a Toshiba CD-ROM drive; otherwise, the option is not needed and
23848 would impact performance a bit, so say N.
23850 Reset SCSI-devices at boottime
23851 CONFIG_ATARI_SCSI_RESET_BOOT
23852 Reset the devices on your Atari whenever it boots. This makes the
23853 boot process fractionally longer but may assist recovery from errors
23854 that leave the devices with SCSI operations partway completed.
23856 Hades SCSI DMA emulator
23858 This option enables code which emulates the TT SCSI DMA chip on the
23859 Hades. This increases the SCSI transfer rates at least ten times
23860 compared to PIO transfers.
23864 This option will enable support for the ESP SCSI controller found
23865 onboard the Sun 3/80.
23869 If you have a Village Tronic Ariadne Ethernet adapter, say Y.
23872 This driver is also available as a module ( = code which can be
23873 inserted in and removed from the running kernel whenever you
23874 want). The module is called ariadne.o. If you want to compile it as
23875 a module, say M here and read <file:Documentation/modules.txt>.
23877 Zorro NS8390-based Ethernet support
23879 This driver is for Zorro Ethernet cards using an NS8390-compatible
23880 chipset, like the Village Tronic Ariadne II and the Individual
23881 Computers X-Surf Ethernet cards. If you have such a card, say Y.
23884 This driver is also available as a module ( = code which can be
23885 inserted in and removed from the running kernel whenever you want).
23886 The module is called zorro8390.o. If you want to compile it as
23887 a module, say M here and read <file:Documentation/modules.txt>.
23891 If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
23894 This driver is also available as a module ( = code which can be
23895 inserted in and removed from the running kernel whenever you
23896 want). The module is called a2065.o. If you want to compile it as a
23897 module, say M here and read <file:Documentation/modules.txt>.
23901 If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
23903 This driver is also available as a module ( = code which can be
23904 inserted in and removed from the running kernel whenever you
23905 want). The module is called hydra.o. If you want to compile it as a
23906 module, say M here and read <file:Documentation/modules.txt>.
23910 This option will enable support for the OBIO (onboard io) NCR5380
23911 SCSI controller found in the Sun 3/50 and 3/60, as well as for
23912 "Sun3" type VME scsi controllers also based on the NCR5380.
23913 General Linux information on the Sun 3 series (now discontinued)
23914 is at <http://www.angelfire.com/ca2/tech68k/sun3.html>.
23916 PCMCIA NE2000 and compatibles support
23918 If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,
23921 This driver is also available as a module ( = code which can be
23922 inserted in and removed from the running kernel whenever you
23923 want). The module is called apne.o. If you want to compile it as a
23924 module, say M here and read <file:Documentation/modules.txt>.
23926 Atari Lance support
23928 Say Y to include support for several Atari Ethernet adapters based
23929 on the AMD Lance chipset: RieblCard (with or without battery), or
23930 PAMCard VME (also the version by Rhotron, with different addresses).
23933 CONFIG_ATARI_BIONET
23934 Say Y to include support for BioData's BioNet-100 Ethernet adapter
23935 for the ACSI port. The driver works (has to work...) with a polled
23936 I/O scheme, so it's rather slow :-(
23939 CONFIG_ATARI_PAMSNET
23940 Say Y to include support for the PAMsNet Ethernet adapter for the
23941 ACSI port ("ACSI node"). The driver works (has to work...) with a
23942 polled I/O scheme, so it's rather slow :-(
23944 Amiga mouse support
23946 If you want to be able to use an Amiga mouse in Linux, say Y.
23948 This driver is also available as a module ( = code which can be
23949 inserted in and removed from the running kernel whenever you want).
23950 The module is called amigamouse.o. If you want to compile it as a
23951 module, say M here and read <file:Documentation/modules.txt>.
23953 Atari mouse support
23955 If you want to be able to use an Atari mouse in Linux, say Y.
23957 This driver is also available as a module ( = code which can be
23958 inserted in and removed from the running kernel whenever you want).
23959 The module is called atarimouse.o. If you want to compile it as a
23960 module, say M here and read <file:Documentation/modules.txt>.
23962 Atari MFP serial support
23963 CONFIG_ATARI_MFPSER
23964 If you like to use the MFP serial ports ("Modem1", "Serial1") under
23965 Linux, say Y. The driver equally supports all kinds of MFP serial
23966 ports and automatically detects whether Serial1 is available.
23968 This driver is also available as a module ( = code which can be
23969 inserted in and removed from the running kernel whenever you want).
23970 If you want to compile it as a module, say M here and read
23971 <file:Documentation/modules.txt>.
23973 Note for Falcon users: You also have an MFP port, it's just not
23974 wired to the outside... But you could use the port under Linux.
23976 Atari SCC serial support
23978 If you have serial ports based on a Zilog SCC chip (Modem2, Serial2,
23979 LAN) and like to use them under Linux, say Y. All built-in SCC's are
23980 supported (TT, MegaSTE, Falcon), and also the ST-ESCC. If you have
23981 two connectors for channel A (Serial2 and LAN), they are visible as
23982 two separate devices.
23984 This driver is also available as a module ( = code which can be
23985 inserted in and removed from the running kernel whenever you want).
23986 If you want to compile it as a module, say M here and read
23987 <file:Documentation/modules.txt>.
23989 Atari SCC serial DMA support
23990 CONFIG_ATARI_SCC_DMA
23991 This enables DMA support for receiving data on channel A of the SCC.
23992 If you have a TT you may say Y here and read
23993 drivers/char/atari_SCC.README. All other users should say N here,
23994 because only the TT has SCC-DMA, even if your machine keeps claiming
23997 Atari MIDI serial support
23999 If you want to use your Atari's MIDI port in Linux, say Y.
24001 This driver is also available as a module ( = code which can be
24002 inserted in and removed from the running kernel whenever you
24003 want). If you want to compile it as a module, say M here and read
24004 <file:Documentation/modules.txt>.
24006 Atari DSP56k Digital Signal Processor support
24007 CONFIG_ATARI_DSP56K
24008 If you want to be able to use the DSP56001 in Falcons, say Y. This
24009 driver is still experimental, and if you don't know what it is, or
24010 if you don't have this processor, just say N.
24012 This driver is also available as a module ( = code which can be
24013 inserted in and removed from the running kernel whenever you want).
24014 If you want to compile it as a module, say M here and read
24015 <file:Documentation/modules.txt>.
24017 Support for early boot text console
24019 Say Y here to see progress messages from the boot firmware in text
24020 mode. Requires either BootX or Open Firmware.
24022 Amiga builtin serial support
24023 CONFIG_AMIGA_BUILTIN_SERIAL
24024 If you want to use your Amiga's built-in serial port in Linux,
24027 This driver is also available as a module ( = code which can be
24028 inserted in and removed from the running kernel whenever you
24029 want). If you want to compile it as a module, say M here and read
24030 <file:Documentation/modules.txt>.
24032 GVP IO-Extender support
24034 If you want to use a GVP IO-Extender serial card in Linux, say Y.
24037 GVP IO-Extender parallel printer support
24039 Say Y to enable driving a printer from the parallel port on your
24040 GVP IO-Extender card, N otherwise.
24042 GVP IO-Extender PLIP support
24043 CONFIG_GVPIOEXT_PLIP
24044 Say Y to enable doing IP over the parallel port on your GVP
24045 IO-Extender card, N otherwise.
24047 Multiface Card III serial support
24048 CONFIG_MULTIFACE_III_TTY
24049 If you want to use a Multiface III card's serial port in Linux,
24052 This driver is also available as a module ( = code which can be
24053 inserted in and removed from the running kernel whenever you want).
24054 If you want to compile it as a module, say M here and read
24055 <file:Documentation/modules.txt>.
24057 Amiga/Atari/PowerMac DMA sound support
24059 Support built-in audio chips accessible by DMA on various machines
24060 that have them. Note that this symbol does not affect the kernel
24061 directly; rather, it controls whether configuration questions
24062 enabling DMA sound drivers for various specific machine
24063 architectures will be used.
24065 Atari DMA sound support
24066 CONFIG_DMASOUND_ATARI
24067 If you want to use the internal audio of your Atari in Linux, answer
24068 Y to this question. This will provide a Sun-like /dev/audio,
24069 compatible with the Linux/i386 sound system. Otherwise, say N.
24071 This driver is also available as a module ( = code which can be
24072 inserted in and removed from the running kernel whenever you
24073 want). If you want to compile it as a module, say M here and read
24074 <file:Documentation/modules.txt>.
24076 PowerMac DMA sound support
24077 CONFIG_DMASOUND_PMAC
24078 If you want to use the internal audio of your PowerMac in Linux,
24079 answer Y to this question. This will provide a Sun-like /dev/audio,
24080 compatible with the Linux/i386 sound system. Otherwise, say N.
24082 This driver is also available as a module ( = code which can be
24083 inserted in and removed from the running kernel whenever you
24084 want). If you want to compile it as a module, say M here and read
24085 <file:Documentation/modules.txt>.
24087 Amiga DMA sound support
24088 CONFIG_DMASOUND_PAULA
24089 If you want to use the internal audio of your Amiga in Linux, answer
24090 Y to this question. This will provide a Sun-like /dev/audio,
24091 compatible with the Linux/i386 sound system. Otherwise, say N.
24093 This driver is also available as a module ( = code which can be
24094 inserted in and removed from the running kernel whenever you
24095 want). If you want to compile it as a module, say M here and read
24096 <file:Documentation/modules.txt>.
24099 CONFIG_DMASOUND_Q40
24100 If you want to use the internal audio of your Q40 in Linux, answer
24101 Y to this question. This will provide a Sun-like /dev/audio,
24102 compatible with the Linux/i386 sound system. Otherwise, say N.
24104 This driver is also available as a module ( = code which can be
24105 inserted in and removed from the running kernel whenever you
24106 want). If you want to compile it as a module, say M here and read
24107 <file:Documentation/modules.txt>.
24109 HP DCA serial support
24111 If you want to use the internal "DCA" serial ports on an HP300
24112 machine, say Y here.
24114 HP on-board LANCE support
24116 If you want to use the builtin "LANCE" Ethernet controller on an
24117 HP300 machine, say Y here.
24121 Say Y here to enable support for the "DIO" expansion bus used in
24122 HP300 machines. If you are using such a system you almost certainly
24128 There are four types of PowerPC chips supported. The more common
24129 types (601, 603, 604, 740, 750, 7400), the Motorola embedded
24130 versions (821, 823, 850, 855, 860, 8260), the IBM embedded versions
24131 (403 and 405) and the high end 64 bit Power processors (Power 3,
24132 Power 4). Unless you are building a kernel for one of the embedded
24133 processor systems, or a 64 bit IBM RS/6000, choose 6xx. Note that
24134 the kernel runs in 32-bit mode even on 64-bit chips. Also note that
24135 because the 82xx family has a 603e core, specific support for that
24136 chipset is asked later on.
24138 Motorola MPC8260 CPM support
24140 The MPC8260 CPM (Communications Processor Module) is a typical
24141 embedded CPU made by Motorola. Selecting this option means that
24142 you wish to build a kernel for a machine with specifically an 8260
24145 If in doubt, say N.
24147 # Choice: ppc4xxtype
24150 Select Oak if you have an IBM 403GCX "Oak" Evaluation Board.
24152 Select Walnut if you have an IBM 405GP "Walnut" Evaluation Board.
24154 More information on these boards is available at:
24155 <http://www.chips.ibm.com/products/powerpc/tools/evk_pn.html#GCX>.
24159 Select Walnut if you have an IBM 405GP "Walnut" Evaluation Board.
24161 Workarounds for PPC601 bugs
24162 CONFIG_PPC601_SYNC_FIX
24163 Some versions of the PPC601 (the first PowerPC chip) have bugs which
24164 mean that extra synchronization instructions are required near
24165 certain instructions, typically those that make major changes to the
24166 CPU state. These extra instructions reduce performance slightly.
24167 If you say N here, these extra instructions will not be included,
24168 resulting in a kernel which will run faster but may not run at all
24169 on some systems with the PPC601 chip.
24171 If in doubt, say Y here.
24173 8xx Cache (Copy-Back or Writethrough)
24174 CONFIG_8xx_COPYBACK
24175 Saying Y here will cause the cache on an MPC8xx processor to be used
24176 in Copy-Back mode. If you say N here, it is used in Writethrough
24179 If in doubt, say Y here.
24181 MPC860 (Pre Rev. C) CPU6 Silicon Errata
24183 MPC860 CPUs, prior to Rev C have some bugs in the silicon, which
24184 require workarounds for Linux (and most other OSes to work). If you
24185 get a BUG() very early in boot, this might fix the problem. For
24186 more details read the document entitled "MPC860 Family Device Errata
24187 Reference" on Motorola's website. This option also incurs a
24190 If in doubt, say N here.
24192 MPC8xx direct IDE support on PCMCIA port
24193 CONFIG_BLK_DEV_MPC8xx_IDE
24194 This option provides support for IDE on Motorola MPC8xx Systems.
24195 Please see 'Type of MPC8xx IDE interface' for details.
24199 # Choice: mpc8xxtype
24200 Type of MPC8xx IDE interface
24201 CONFIG_IDE_8xx_PCCARD
24202 Select how the IDE devices are connected to the MPC8xx system:
24204 8xx_PCCARD uses the 8xx internal PCMCIA interface in combination
24205 with a PC Card (e.g. ARGOSY portable Hard Disk Adapter),
24206 ATA PC Card HDDs or ATA PC Flash Cards (example: TQM8xxL
24209 8xx_DIRECT is used for directly connected IDE devices using the 8xx
24210 internal PCMCIA interface (example: IVMS8 systems)
24212 EXT_DIRECT is used for IDE devices directly connected to the 8xx
24213 bus using some glue logic, but _not_ the 8xx internal
24214 PCMCIA interface (example: IDIF860 systems)
24218 If you would like to use SMC2 as a serial port, say Y here.
24220 If in doubt, say Y here.
24222 Use SMC2 for Console
24224 If you are going to have a serial console on your device and are
24225 using SMC2 for your serial port, say Y here, else say N.
24227 Use the alternate SMC2 I/O
24229 If you have an MPC823 or MPC850 and would like to use the alternate
24230 SMC2 for I/O, say Y here.
24232 If in doubt, say N here.
24234 Enable SCC2 and SCC3 for UART
24236 If your MPC8xx board has other SCC ports that you would like to use
24237 for for a serial port, say Y here.
24239 If in doubt, say N here.
24241 # Choice: ppc6xxtype
24244 Linux currently supports several different kinds of PowerPC-based
24245 machines: Apple Power Macintoshes and clones (such as the Motorola
24246 Starmax series), PReP (PowerPC Reference Platform) machines (such
24247 as the Motorola PowerStacks, Motorola cPCI/VME embedded systems,
24248 and some IBM RS/6000 systems), CHRP (Common Hardware Reference
24249 Platform), and several embedded PowerPC systems containing 4xx, 6xx,
24250 7xx, 8xx, 74xx, and 82xx processors. Currently, the default option
24251 is to build a kernel which works on the first three.
24253 Select PowerMac/PReP/MTX/CHRP if configuring for any of the above.
24255 Select Gemini if configuring for a Synergy Microsystems' Gemini
24256 series Single Board Computer. More information is available at:
24257 <http://www.synergymicro.com/PressRel/97_10_15.html>.
24259 Select APUS if configuring for a PowerUP Amiga. More information is
24260 available at: <http://linux-apus.sourceforge.net/>.
24262 Note that Total Impact briQ is handled as a CHRP machine.
24266 Select Gemini if configuring for a Synergy Microsystems' Gemini
24267 series Single Board Computer. More information is available at:
24268 <http://www.synergymicro.com/PressRel/97_10_15.html>.
24272 Select APUS if configuring for a PowerUP Amiga.
24273 More information is available at:
24274 <http://linux-apus.sourceforge.net/>.
24276 AltiVec kernel support
24278 This option enables kernel support for the Altivec extensions to the
24279 PowerPC processor. The kernel currently supports saving and restoring
24280 altivec registers, and turning on the 'altivec enable' bit so user
24281 processes can execute altivec instructions.
24283 This option is only usefully if you have a processor that supports
24284 altivec (G4, otherwise known as 74xx series), but does not have
24285 any affect on a non-altivec cpu (it does, however add code to the
24288 If in doubt, say Y here.
24290 Thermal Management Support
24292 G3 and G4 processors have an on-chip temperature sensor called the
24293 'Thermal Assist Unit (TAU)', which, in theory, can measure the on-die
24294 temperature within 2-4 degrees Celsius. This option shows the current
24295 on-die temperature in /proc/cpuinfo if the cpu supports it.
24297 Unfortunately, on some chip revisions, this sensor is very inaccurate
24298 and in some cases, does not work at all, so don't assume the cpu
24299 temp is actually what /proc/cpuinfo says it is.
24301 Interrupt driven TAU driver
24303 The TAU supports an interrupt driven mode which causes an interrupt
24304 whenever the temperature goes out of range. This is the fastest way
24305 to get notified the temp has exceeded a range. With this option off,
24306 a timer is used to re-check the temperature periodically.
24308 However, on some cpus it appears that the TAU interrupt hardware
24309 is buggy and can cause a situation which would lead unexplained hard
24312 Unless you are extending the TAU driver, or enjoy kernel/hardware
24313 debugging, leave this option off.
24315 Average high and low temp
24317 The TAU hardware can compare the temperature to an upper and lower bound.
24318 The default behaviour is to show both the upper and lower bound in
24319 /proc/cpuinfo. If the range is large, the temperature is either changing
24320 a lot, or the TAU hardware is broken (likely on some G4's). If the range
24321 is small (around 4 degrees), the temperature is relatively stable.
24323 Power management support for PowerBooks
24325 This provides support for putting a PowerBook to sleep; it also
24326 enables media bay support. Power management works on the
24327 PB2400/3400/3500, Wallstreet, Lombard, and Bronze PowerBook G3. You
24328 must get the power management daemon, pmud, to make it work and you
24329 must have the /dev/pmu device (see the pmud README).
24331 Get pmud from <ftp://ftp.samba.org/pub/ppclinux/pmud/>.
24333 If you have a PowerBook, you should say Y.
24335 You may also want to compile the dma sound driver as a module and
24336 have it autoloaded. The act of removing the module shuts down the
24337 sound hardware for more power savings.
24340 CONFIG_PMAC_APM_EMU
24341 This driver provides an emulated /dev/apm_bios and /proc/apm. The
24342 first one is mostly intended for XFree to sleep & wakeup properly,
24343 the second ones provides some battery informations to allow existing
24344 APM utilities to work. It provides less useful informations than
24345 tools specifically designed for PowerBooks or /proc/pmu/battery_x
24347 Backlight control for LCD screens
24348 CONFIG_PMAC_BACKLIGHT
24349 Say Y here to build in code to manage the LCD backlight on a
24350 Macintosh PowerBook. With this code, the backlight will be turned
24351 on and off appropriately on power-management and lid-open/lid-closed
24352 events; also, the PowerBook button device will be enabled so you can
24353 change the screen brightness.
24355 # Choice: ppc8xxtype
24356 Embedded 8xx Board Type
24358 Single-board computers based around the PowerPC MPC8xx chips and
24359 intended for embedded applications. The following types are
24363 Embedded Planet RPX Lite. PC104 form-factor SBC based on the MPC823.
24366 Embedded Planet RPX Classic Low-fat. Credit-card-size SBC based on
24370 Bright Star Engineering ip-Engine.
24376 MPC8xx based family of mini modules, half credit card size,
24377 up to 64 MB of RAM, 8 MB Flash, (Fast) Ethernet, 2 x serial ports,
24378 2 x CAN bus interface, ...
24379 Manufacturer: TQ Components, www.tq-group.de
24380 Date of Release: October (?) 1999
24381 End of Life: not yet :-)
24383 - module: <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>
24384 - starter kit: <http://www.denx.de/PDF/STK8xxLHWM201.pdf>
24385 - images: <http://www.denx.de/embedded-ppc-en.html>
24388 FingerPrint Sensor System (based on TQM850L)
24389 Manufacturer: IKENDI AG, <http://www.ikendi.com/>
24390 Date of Release: November 1999
24391 End of life: end 2000 ?
24395 MPC823 based board used in the "Tele Server" product
24396 Manufacturer: Speech Design, <http://www.speech-design.de/>
24397 Date of Release: Mid 2000 (?)
24399 URL: <http://www.speech-design.de/>
24400 select "English", then "Teleteam Solutions", then "TeleServer"
24403 MPC860 based board used in the "Integrated Voice Mail System",
24404 Small Version (8 voice channels)
24405 Manufacturer: Speech Design, <http://www.speech-design.de/>
24406 Date of Release: December 2000 (?)
24408 URL: <http://www.speech-design.de/>
24411 MPC860 based board used in the "Integrated Voice Mail System",
24412 Large Version (24 voice channels)
24413 Manufacturer: Speech Design, <http://www.speech-design.de/>
24414 Date of Release: March 2001 (?)
24416 URL: <http://www.speech-design.de/>
24419 Service Module (based on TQM850L)
24420 Manufacturer: Dependable Computer Systems, <http://www.decomsys.com/>
24421 Date of Release: end 2000 (?)
24422 End of life: mid 2001 (?)
24423 URL: <http://www.tz-mikroelektronik.de/ServiceModule/index.html>
24426 Hermes-Pro ISDN/LAN router with integrated 8 x hub
24427 Manufacturer: Multidata Gesellschaft für Datentechnik und Informatik
24428 <http://www.multidata.de/>
24429 Date of Release: 2000 (?)
24431 URL: <http://www.multidata.de/english/products/hpro.htm>
24434 VMEBus IP (Industry Pack) carrier board with MPC860
24435 Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
24438 URL: <http://www.microsys.de/html/ip860.html>
24441 PCU = Peripheral Controller Unit, Extended
24442 Manufacturer: Siemens AG, ICN (Information and Communication Networks)
24443 <http://www.siemens.de/page/1,3771,224315-1-999_2_226207-0,00.html>
24444 Date of Release: April 2001
24445 End of life: August 2001
24450 The RPX-Classic is a single-board computer based on the Motorola
24451 MPC860. It features 16MB of DRAM and a variable amount of flash,
24452 I2C EEPROM, thermal monitoring, a PCMCIA slot, a DIP switch and two
24453 LEDs. Variants with Ethernet ports exist. Say Y here to support it
24458 Say Y here to support the Bright Star Engineering ipEngine SBC.
24459 This is a credit-card-sized device featuring a MPC823 processor,
24460 26MB DRAM, 4MB flash, Ethernet, a 16K-gate FPGA, USB, an LCD/video
24461 controller, and two RS232 ports.
24465 Say Y here to support the TQM823L, one of an MPC8xx-based family of
24466 mini SBCs (half credit-card size) from TQ Components first released
24467 in late 1999. Technical references are at
24468 <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
24469 <http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
24470 <http://www.denx.de/embedded-ppc-en.html>.
24474 Say Y here to support the TQM850L, one of an MPC8xx-based family of
24475 mini SBCs (half credit-card size) from TQ Components first released
24476 in late 1999. Technical references are at
24477 <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
24478 <http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
24479 <http://www.denx.de/embedded-ppc-en.html>.
24483 Say Y here to support the TQM855L, one of an MPC8xx-based family of
24484 mini SBCs (half credit-card size) from TQ Components first released
24485 in late 1999. Technical references are at
24486 <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
24487 <http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
24488 <http://www.denx.de/embedded-ppc-en.html>.
24492 Say Y here to support the TQM860L, one of an MPC8xx-based family of
24493 mini SBCs (half credit-card size) from TQ Components first released
24494 in late 1999. Technical references are at
24495 <http://www.denx.de/PDF/TQM8xxLHWM201.pdf>, and
24496 <http://www.denx.de/PDF/STK8xxLHWM201.pdf>, and an image at
24497 <http://www.denx.de/embedded-ppc-en.html>.
24501 Say Y here to support the FingerPrint Sensor from AKENDI IG, based
24502 on the TQ Components TQM850L module, released November 1999 and
24503 discontinued a year later.
24507 Say Y here to support the TQM860, one of an MPC8xx-based family of
24508 SBCs (credit-card size) from TQ Components first released in
24509 mid-1999 and discontinued mid-2000.
24513 Say Y here to support the Service Module 850 from Dependable
24514 Computer Systems, an SBC based on the TQM850L module by TQ
24515 Components. This board is no longer in production. The
24516 manufacturer's website is at <http://www.decomsys.com/>.
24520 Say Y here to support the Speech Design 823 Tele-Server from Speech
24521 Design, released in 2000. The manufacturer's website is at
24522 <http://www.speech-design.de/>.
24526 Say Y here to support the Integrated Voice-Mail Small 8-channel SBC
24527 from Speech Design, released March 2001. The manufacturer's website
24528 is at <http://www.speech-design.de/>.
24530 # IVML24 is not yet active
24533 Say Y here to support the Integrated Voice-Mail Large 24-channel SBC
24534 from Speech Design, released March 2001. The manufacturer's website
24535 is at <http://www.speech-design.de/>.
24539 MBX is a line of Motorola single-board computer based around the
24540 MPC821 and MPC860 processors, and intended for embedded-controller
24541 applications. Say Y here to support these boards directly.
24545 The Wincept 100/110 is a Motorola single-board computer based on the
24546 MPC821 PowerPC, introduced in 1998 and designed to be used in
24547 thin-client machines. Say Y to support it directly.
24549 # More systems that will be supported soon, according to
24550 # Wolfgang Denk <wd@denx.de>:
24553 # MPC8260 based module
24555 # Manufacturer: TQ Components, www.tq-group.de
24556 # Date of Release: June 2001
24557 # End of Life: not yet :-)
24558 # URL: <http://www.denx.de/PDF/TQM82xx_SPEC_Rev003.pdf>
24561 # VMEBus IP (Industry Pack) carrier board with MPC860
24563 # Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
24564 # Date of Release: ?
24566 # URL: <http://www.microsys.de/html/ip860.html>
24569 # VMEBus Board with PCI extension with MPC8240 CPU
24571 # Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
24572 # Date of Release: early 2001 (?)
24574 # URL: <http://www.microsys.de/html/cu824.html>
24577 # Modular system with MPC8260 CPU
24579 # Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
24580 # Date of Release: mid 2001
24582 # URL: <http://www.microsys.de/html/pm826.html>
24585 # PCU = Peripheral Controller Unit; E = extended (?)
24587 # Mfr: Siemens AG, ICN (Information and Communication Networks)
24588 # <http://www.siemens.de/page/1,3771,224315-1-999_2_226207-0,00.html>
24589 # Date of Release: April 2001
24593 # Choice: ppc82xxtype
24594 Embedded 82xx Board Type
24597 The EST8260 is a single-board computer manufactured by Wind River
24598 Systems, Inc. (formerly Embedded Support Tools Corp.) and based on
24599 the MPC8260. Wind River Systems has a website at
24600 <http://www.windriver.com/>, but the EST8260 cannot be found on it
24601 and has probably been discontinued or rebadged.
24604 MPC8260 based module, little larger than credit card,
24605 up to 128 MB global + 64 MB local RAM, 32 MB Flash,
24606 32 kB EEPROM, 256 kB L@ Cache, 10baseT + 100baseT Ethernet,
24607 2 x serial ports, ...
24608 Manufacturer: TQ Components, www.tq-group.de
24609 Date of Release: June 2001
24610 End of Life: not yet :-)
24611 URL: <http://www.denx.de/PDF/TQM82xx_SPEC_Rev005.pdf>
24614 Modular system with MPC8260 CPU
24615 Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
24616 Date of Release: mid 2001
24618 URL: <http://www.microsys.de/html/pm826.html>
24621 VMEBus Board with PCI extension with MPC8240 CPU
24622 Manufacturer: MicroSys GmbH, <http://www.microsys.de/>
24623 Date of Release: early 2001 (?)
24625 URL: <http://www.microsys.de/html/cu824.html>
24627 ADB raw keycode support
24628 CONFIG_MAC_ADBKEYCODES
24629 This provides support for sending raw ADB keycodes to console
24630 devices. This is the default up to 2.4.0, but in future this may be
24631 phased out in favor of generic Linux keycodes. If you say Y here,
24632 you can dynamically switch via the
24633 /proc/sys/dev/mac_hid/keyboard_sends_linux_keycodes
24634 sysctl and with the "keyboard_sends_linux_keycodes=" kernel
24637 This option is now deprecated and will be removed in a future
24640 If unsure, say N here.
24642 I2C/SPI Microcode Patch
24644 Motorola releases microcode updates for their 8xx CPM modules. The
24645 microcode update file has updates for IIC, SMC and USB. Currently only
24646 the USB update is available by default, if the MPC8xx USB option is
24647 enabled. If in doubt, say 'N' here.
24649 Mouse button 2+3 emulation support
24650 CONFIG_MAC_EMUMOUSEBTN
24651 This provides generic support for emulating the 2nd and 3rd mouse
24652 button with keypresses. If you say Y here, the emulation is still
24653 disabled by default. The emulation is controlled by these sysctl
24655 /proc/sys/dev/mac_hid/mouse_button_emulation
24656 /proc/sys/dev/mac_hid/mouse_button2_keycode
24657 /proc/sys/dev/mac_hid/mouse_button3_keycode
24659 Set high memory pool address
24660 CONFIG_HIGHMEM_START_BOOL
24661 Unless you know what you are doing you *should not* set this option.
24663 It can be used to override the default PKMAP_BASE address which
24664 is the location of the high memory pool. This can be useful in
24665 optimizing virtual memory usage in a system.
24667 Set maximum low memory
24668 CONFIG_LOWMEM_SIZE_BOOL
24669 Unless you know what you are doing you *should not* set this option.
24671 It can be used to override the standard calculated value of
24672 MAX_LOW_MEM. This can be useful in optimizing virtual memory usage
24675 Set custom kernel base address
24676 CONFIG_KERNEL_START_BOOL
24677 Unless you know what you are doing you *should not* set this option.
24679 It can be used to override the standard PAGE_OFFSET/KERNELBASE
24680 value used by the kernel. This can be useful in controlling
24681 amount of virtual address space available to the kernel.
24683 Set custom user task size
24684 CONFIG_TASK_SIZE_BOOL
24685 Unless you know what you are doing you *should not* set this option.
24687 It can be used to override the standard TASK_SIZE value used
24688 by the kernel. This can be useful in controlling amount of
24689 virtual address space available to user tasks.
24691 Enhanced Real Time Clock Support (/dev/rtc)
24693 If you say Y here and create a character special file /dev/rtc with
24694 major number 10 and minor number 135 using mknod ("man mknod"), you
24695 will get access to the real time clock (or hardware clock) built
24696 into your computer.
24698 If unsure, say Y here.
24700 Support for Open Firmware device tree in /proc
24701 CONFIG_PROC_DEVICETREE
24702 This option adds a device-tree directory under /proc which contains
24703 an image of the device tree that the kernel copies from Open
24704 Firmware. If unsure, say Y here.
24706 RTAS (RunTime Abstraction Services) in /proc
24708 When you use this option, you will be able to use RTAS from
24711 RTAS stands for RunTime Abstraction Services and should
24712 provide a portable way to access and set system information. This is
24713 commonly used on RS/6000 (pSeries) computers.
24715 You can access RTAS via the special proc file system entry rtas.
24716 Don't confuse this rtas entry with the one in /proc/device-tree/rtas
24719 If you don't know if you can use RTAS look into
24720 /proc/device-tree/rtas. If there are some entries, it is very likely
24721 that you will be able to use RTAS.
24723 You can do cool things with rtas. To print out information about
24724 various sensors in the system, just do a
24726 $ cat /proc/rtas/sensors
24728 or if you power off your machine at night but want it running when
24729 you enter your office at 7:45 am, do a
24731 # date -d 'tomorrow 7:30' +%s > /proc/rtas/poweron
24737 Support for Lpar Configuration data in /proc
24739 This option adds lparcfg entry as /proc/ppc64/lparcfg which returns
24740 system configuration info in <key word>=<value> pairs.
24742 MESH (Power Mac internal SCSI) support
24744 Many Power Macintoshes and clones have a MESH (Macintosh Enhanced
24745 SCSI Hardware) SCSI bus adaptor (the 7200 doesn't, but all of the
24746 other Power Macintoshes do). Say Y to include support for this SCSI
24747 adaptor. This driver is also available as a module called mesh.o
24748 ( = code which can be inserted in and removed from the running
24749 kernel whenever you want). If you want to compile it as a module,
24750 say M here and read <file:Documentation/modules.txt>.
24752 Maximum synchronous transfer rate (MB/s) (0 = async)
24753 CONFIG_SCSI_MESH_SYNC_RATE
24754 On Power Macintoshes (and clones) where the MESH SCSI bus adaptor
24755 drives a bus which is entirely internal to the machine (such as the
24756 7500, 7600, 8500, etc.), the MESH is capable of synchronous
24757 operation at up to 10 MB/s. On machines where the SCSI bus
24758 controlled by the MESH can have external devices connected, it is
24759 usually rated at 5 MB/s. 5 is a safe value here unless you know the
24760 MESH SCSI bus is internal only; in that case you can say 10. Say 0
24761 to disable synchronous operation.
24763 53C94 (Power Mac external SCSI) support
24764 CONFIG_SCSI_MAC53C94
24765 On Power Macintoshes (and clones) with two SCSI buses, the external
24766 SCSI bus is usually controlled by a 53C94 SCSI bus adaptor. Older
24767 machines which only have one SCSI bus, such as the 7200, also use
24768 the 53C94. Say Y to include support for the 53C94.
24770 This driver is also available as a module called mac53c94.o ( = code
24771 which can be inserted in and removed from the running kernel
24772 whenever you want). If you want to compile it as a module, say M
24773 here and read <file:Documentation/modules.txt>.
24775 MACE (Power Mac Ethernet) support
24777 Power Macintoshes and clones with Ethernet built-in on the
24778 motherboard will usually use a MACE (Medium Access Control for
24779 Ethernet) interface. Say Y to include support for the MACE chip.
24781 This driver is also available as a module called mace.o ( = code
24782 which can be inserted in and removed from the running kernel
24783 whenever you want). If you want to compile it as a module, say M
24784 here and read <file:Documentation/modules.txt>.
24786 Use AAUI port instead of TP by default
24787 CONFIG_MACE_AAUI_PORT
24788 Some Apple machines (notably the Apple Network Server) which use the
24789 MACE ethernet chip have an Apple AUI port (small 15-pin connector),
24790 instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say
24791 Y here if you have such a machine. If unsure, say N.
24792 The driver will default to AAUI on ANS anyway, and if you use it as
24793 a module, you can provide the port_aaui=0|1 to force the driver.
24795 BMAC (G3 Ethernet) support
24797 Say Y for support of BMAC Ethernet interfaces. These are used on G3
24800 This driver is also available as a module called bmac.o ( = code
24801 which can be inserted in and removed from the running kernel
24802 whenever you want). If you want to compile it as a module, say M
24803 here and read <file:Documentation/modules.txt>.
24805 GMAC (G4/iBook Ethernet) support
24807 Say Y for support of GMAC Ethernet interfaces. These are used on G4
24808 and iBook computers.
24810 This driver is also available as a module called gmac.o ( = code
24811 which can be inserted in and removed from the running kernel
24812 whenever you want). If you want to compile it as a module, say M
24813 here and read <file:Documentation/modules.txt>.
24815 National DP83902AV (Oak Ethernet) support
24817 Say Y if your machine has this type of Ethernet network card.
24819 This driver is also available as a module called oaknet.o ( = code
24820 which can be inserted in and removed from the running kernel
24821 whenever you want). If you want to compile it as a module, say M
24822 here and read <file:Documentation/modules.txt>.
24826 Support for audio/video capture and overlay devices and FM radio
24827 cards. The exact capabilities of each device vary. User tools for
24828 this are available from
24829 <ftp://ftp.uk.linux.org/pub/linux/video4linux/>.
24831 If you are interested in writing a driver for such an audio/video
24832 device or user software interacting with such a driver, please read
24833 the file <file:Documentation/video4linux/API.html>.
24835 This driver is also available as a module called videodev.o ( = code
24836 which can be inserted in and removed from the running kernel
24837 whenever you want). If you want to compile it as a module, say M
24838 here and read <file:Documentation/modules.txt>.
24840 Video For Linux /proc file system information
24841 CONFIG_VIDEO_PROC_FS
24842 If you say Y here, you are able to access video device information
24845 To use this option, you have to check, that the "/proc file system
24846 support" (CONFIG_PROC_FS) is enabled too.
24848 AIMSlab RadioTrack (aka RadioReveal) support
24849 CONFIG_RADIO_RTRACK
24850 Choose Y here if you have one of these FM radio cards, and then fill
24851 in the port address below.
24853 Note that newer AIMSlab RadioTrack cards have a different chipset
24854 and are not supported by this driver. For these cards, use the
24855 RadioTrack II driver below.
24857 If you have a GemTeks combined (PnP) sound- and radio card you must
24858 use this driver as a module and setup the card with isapnptools.
24859 You must also pass the module a suitable io parameter, 0x248 has
24860 been reported to be used by these cards.
24862 In order to control your radio card, you will need to use programs
24863 that are compatible with the Video For Linux API. Information on
24864 this API and pointers to "v4l" programs may be found on the WWW at
24865 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>. More
24866 information is contained in the file
24867 <file:Documentation/video4linux/radiotrack.txt>.
24869 If you want to compile this driver as a module ( = code which can be
24870 inserted in and removed from the running kernel whenever you want),
24871 say M here and read <file:Documentation/modules.txt>. The module
24872 will be called radio-aimslab.o.
24874 RadioTrack I/O port
24875 CONFIG_RADIO_RTRACK_PORT
24876 Enter either 0x30f or 0x20f here. The card default is 0x30f, if you
24877 haven't changed the jumper setting on the card.
24879 AIMSlab RadioTrack II support
24880 CONFIG_RADIO_RTRACK2
24881 Choose Y here if you have this FM radio card, and then fill in the
24882 port address below.
24884 In order to control your radio card, you will need to use programs
24885 that are compatible with the Video For Linux API. Information on
24886 this API and pointers to "v4l" programs may be found on the WWW at
24887 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
24889 If you want to compile this driver as a module ( = code which can be
24890 inserted in and removed from the running kernel whenever you want),
24891 say M here and read <file:Documentation/modules.txt>. The module
24892 will be called radio-rtrack2.o.
24894 RadioTrack II I/O port
24895 CONFIG_RADIO_RTRACK2_PORT
24896 Enter either 0x30c or 0x20c here. The card default is 0x30c, if you
24897 haven't changed the jumper setting on the card.
24899 Aztech/Packard Bell Radio
24900 CONFIG_RADIO_AZTECH
24901 Choose Y here if you have one of these FM radio cards, and then fill
24902 in the port address below.
24904 In order to control your radio card, you will need to use programs
24905 that are compatible with the Video For Linux API. Information on
24906 this API and pointers to "v4l" programs may be found on the WWW at
24907 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
24909 If you want to compile this driver as a module ( = code which can be
24910 inserted in and removed from the running kernel whenever you want),
24911 say M here and read <file:Documentation/modules.txt>. The module
24912 will be called radio-aztech.o.
24914 Aztech/Packard Bell radio card I/O port
24915 CONFIG_RADIO_AZTECH_PORT
24916 Enter either 0x350 or 0x358 here. The card default is 0x350, if you
24917 haven't changed the setting of jumper JP3 on the card. Removing the
24918 jumper sets the card to 0x358.
24920 ADS Cadet AM/FM Radio Tuner Card
24922 Choose Y here if you have one of these AM/FM radio cards, and then
24923 fill in the port address below.
24925 In order to control your radio card, you will need to use programs
24926 that are compatible with the Video For Linux API. Information on
24927 this API and pointers to "v4l" programs may be found on the WWW at
24928 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
24930 Further documentation on this driver can be found on the WWW at
24931 <http://linux.blackhawke.net/cadet.html>.
24933 If you want to compile this driver as a module ( = code which can be
24934 inserted in and removed from the running kernel whenever you want),
24935 say M here and read <file:Documentation/modules.txt>. The module
24936 will be called radio-cadet.o.
24939 CONFIG_RADIO_SF16FMI
24940 Choose Y here if you have one of these FM radio cards. If you
24941 compile the driver into the kernel and your card is not PnP one, you
24942 have to add "sf16fm=<io>" to the kernel command line (I/O address is
24945 In order to control your radio card, you will need to use programs
24946 that are compatible with the Video For Linux API. Information on
24947 this API and pointers to "v4l" programs may be found on the WWW at
24948 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
24950 If you want to compile this driver as a module ( = code which can be
24951 inserted in and removed from the running kernel whenever you want),
24952 say M here and read <file:Documentation/modules.txt>. The module
24953 will be called radio-sf16fmi.o.
24956 CONFIG_RADIO_SF16FMR2
24957 Choose Y here if you have one of these FM radio cards. If you
24958 compile the driver into the kernel and your card is not PnP one, you
24959 have to add "sf16fmr2=<io>" to the kernel command line (I/O address is
24960 0x284 or 0x384, default 0x384).
24962 In order to control your radio card, you will need to use programs
24963 that are compatible with the Video For Linux API. Information on
24964 this API and pointers to "v4l" programs may be found on the WWW at
24965 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
24967 If you want to compile this driver as a module ( = code which can be
24968 inserted in and removed from the running kernel whenever you want),
24969 say M here and read <file:Documentation/modules.txt>. The module
24970 will be called radio-sf16fmr2.o.
24972 Typhoon Radio (a.k.a. EcoRadio)
24973 CONFIG_RADIO_TYPHOON
24974 Choose Y here if you have one of these FM radio cards, and then fill
24975 in the port address and the frequency used for muting below.
24977 In order to control your radio card, you will need to use programs
24978 that are compatible with the Video For Linux API. Information on
24979 this API and pointers to "v4l" programs may be found on the WWW at
24980 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
24982 If you want to compile this driver as a module ( = code which can be
24983 inserted in and removed from the running kernel whenever you want),
24984 say M here and read <file:Documentation/modules.txt>. The module
24985 will be called radio-typhoon.o.
24987 Support for /proc/radio-typhoon
24988 CONFIG_RADIO_TYPHOON_PROC_FS
24989 Say Y here if you want the typhoon radio card driver to write
24990 status information (frequency, volume, muted, mute frequency,
24991 base address) to /proc/radio-typhoon. The file can be viewed with
24992 your favorite pager (i.e. use "more /proc/radio-typhoon" or "less
24993 /proc/radio-typhoon" or simply "cat /proc/radio-typhoon").
24995 Typhoon I/O port (0x316 or 0x336)
24996 CONFIG_RADIO_TYPHOON_PORT
24997 Enter the I/O port of your Typhoon or EcoRadio radio card.
24999 Typhoon frequency set when muting the device (kHz)
25000 CONFIG_RADIO_TYPHOON_MUTEFREQ
25001 Enter the frequency used for muting the radio. The device is never
25002 completely silent. If the volume is just turned down, you can still
25003 hear silent voices and music. For that reason, the frequency of the
25004 radio device is set to the frequency you can enter here whenever
25005 the device is muted. There should be no local radio station at that
25009 CONFIG_RADIO_ZOLTRIX
25010 Choose Y here if you have one of these FM radio cards, and then fill
25011 in the port address below.
25013 In order to control your radio card, you will need to use programs
25014 that are compatible with the Video For Linux API. Information on
25015 this API and pointers to "v4l" programs may be found on the WWW at
25016 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
25018 If you want to compile this driver as a module ( = code which can be
25019 inserted in and removed from the running kernel whenever you want),
25020 say M here and read <file:Documentation/modules.txt>. The module
25021 will be called radio-zoltrix.o.
25023 ZOLTRIX I/O port (0x20c or 0x30c)
25024 CONFIG_RADIO_ZOLTRIX_PORT
25025 Enter the I/O port of your Zoltrix radio card.
25027 I2C on parallel port
25029 I2C is a simple serial bus system used in many micro controller
25030 applications. Saying Y here will allow you to use your parallel
25031 port as an I2C interface.
25033 If you want to compile this driver as a module ( = code which can be
25034 inserted in and removed from the running kernel whenever you want),
25035 say M here and read <file:Documentation/modules.txt>. The module
25036 will be called i2c-parport.o.
25038 miroSOUND PCM20 radio
25039 CONFIG_RADIO_MIROPCM20
25040 Choose Y here if you have this FM radio card. You also need to say Y
25041 to "ACI mixer (miroSOUND PCM1-pro/PCM12/PCM20 radio)" (in "Sound")
25044 In order to control your radio card, you will need to use programs
25045 that are compatible with the Video For Linux API. Information on
25046 this API and pointers to "v4l" programs may be found on the WWW at
25047 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
25049 If you want to compile this driver as a module ( = code which can be
25050 inserted in and removed from the running kernel whenever you want),
25051 say M here and read <file:Documentation/modules.txt>. The module
25052 will be called miropcm20.o.
25054 miroSOUND PCM20 radio RDS user interface (EXPERIMENTAL)
25055 CONFIG_RADIO_MIROPCM20_RDS
25056 Choose Y here if you want to see RDS/RBDS information like
25057 RadioText, Programme Service name, Clock Time and date, Programme
25058 TYpe and Traffic Announcement/Programme identification. You also
25059 need to say Y to "miroSOUND PCM20 radio" and devfs!
25061 It's not possible to read the raw RDS packets from the device, so
25062 the driver cant provide an V4L interface for this. But the
25063 availability of RDS is reported over V4L by the basic driver
25064 already. Here RDS can be read from files in /dev/v4l/rds.
25066 As module the driver will be called miropcm20-rds.o.
25068 Maestro on board radio
25069 CONFIG_RADIO_MAESTRO
25070 Say Y here to directly support the on-board radio tuner on the
25071 Maestro 2 or 2E sound card.
25073 In order to control your radio card, you will need to use programs
25074 that are compatible with the Video For Linux API. Information on
25075 this API and pointers to "v4l" programs may be found on the WWW at
25076 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
25078 If you want to compile this driver as a module ( = code which can be
25079 inserted in and removed from the running kernel whenever you want),
25080 say M here and read <file:Documentation/modules.txt>. The module
25081 will be called radio-maestro.o.
25083 Guillemot MAXI Radio FM 2000 Radio Card
25084 CONFIG_RADIO_MAXIRADIO
25085 Choose Y here if you have this radio card. This card may also be
25086 found as GemTek PCI FM.
25088 In order to control your radio card, you will need to use programs
25089 that are compatible with the Video For Linux API. Information on
25090 this API and pointers to "v4l" programs may be found on the WWW at
25091 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
25093 If you want to compile this driver as a module ( = code which can be
25094 inserted in and removed from the running kernel whenever you want),
25095 say M here and read <file:Documentation/modules.txt>. The module
25096 will be called radio-maxiradio.o.
25098 GemTek Radio Card support
25099 CONFIG_RADIO_GEMTEK
25100 Choose Y here if you have this FM radio card, and then fill in the
25101 port address below.
25103 In order to control your radio card, you will need to use programs
25104 that are compatible with the Video For Linux API. Information on
25105 this API and pointers to "v4l" programs may be found on the WWW at
25106 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
25108 If you want to compile this driver as a module ( = code which can be
25109 inserted in and removed from the running kernel whenever you want),
25110 say M here and read <file:Documentation/modules.txt>. The module
25111 will be called radio-gemtek.o.
25114 CONFIG_RADIO_GEMTEK_PORT
25115 Enter either 0x20c, 0x30c, 0x24c or 0x34c here. The card default is
25116 0x34c, if you haven't changed the jumper setting on the card. On
25117 Sound Vision 16 Gold PnP with FM Radio (ESS1869+FM GemTek), the I/O
25120 GemTek PCI Radio Card support
25121 CONFIG_RADIO_GEMTEK_PCI
25122 Choose Y here if you have this PCI FM radio card.
25124 In order to control your radio card, you will need to use programs
25125 that are compatible with the Video for Linux API. Information on
25126 this API and pointers to "v4l" programs may be found on the WWW at
25127 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
25129 If you want to compile this driver as a module ( = code which can be
25130 inserted in and removed from the running kernel whenever you want),
25131 say M here and read <file:Documentation/modules.txt>. The module
25132 will be called radio-gemtek-pci.o.
25134 PlanB Video-In for PowerMacs
25136 PlanB is the V4L driver for the PowerMac 7x00/8x00 series video
25137 input hardware. If you want to experiment with this, say Y.
25138 Otherwise, or if you don't understand a word, say N.
25139 See <http://www.cpu.lu/~mlan/planb.html> for more info.
25141 Saying M will compile this driver as a module (planb.o).
25143 TerraTec ActiveRadio
25144 CONFIG_RADIO_TERRATEC
25145 Choose Y here if you have this FM radio card, and then fill in the
25146 port address below. (TODO)
25148 Note: This driver is in its early stages. Right now volume and
25149 frequency control and muting works at least for me, but
25150 unfortunately I have not found anybody who wants to use this card
25151 with Linux. So if it is this what YOU are trying to do right now,
25152 PLEASE DROP ME A NOTE!! Rolf Offermanns (rolf@offermanns.de)
25154 In order to control your radio card, you will need to use programs
25155 that are compatible with the Video For Linux API. Information on
25156 this API and pointers to "v4l" programs may be found on the WWW at
25157 <http://roadrunner.swansea.uk.linux.org/v4l.shtml>.
25159 If you want to compile this driver as a module ( = code which can be
25160 inserted in and removed from the running kernel whenever you want),
25161 say M here and read <file:Documentation/modules.txt>. The module
25162 will be called radio-terratec.o.
25164 Terratec I/O port (normally 0x590)
25165 CONFIG_RADIO_TERRATEC_PORT
25166 Fill in the I/O port of your TerraTec FM radio card. If unsure, go
25169 Trust FM radio card
25171 This is a driver for the Trust FM radio cards. Say Y if you have
25172 such a card and want to use it under Linux.
25174 This driver is also available as a module called radio-trust.o ( =
25175 code which can be inserted in and removed from the running kernel
25176 whenever you want). If you want to compile it as a module, say M
25177 here and read <file:Documentation/modules.txt>.
25179 Trust I/O port (usually 0x350 or 0x358)
25180 CONFIG_RADIO_TRUST_PORT
25181 Enter the I/O port of your Trust FM radio card. If unsure, try the
25182 values "0x350" or "0x358".
25184 BT848 Video For Linux
25186 Support for BT848 based frame grabber/overlay boards. This includes
25187 the Miro, Hauppauge and STB boards. Please read the material in
25188 <file:Documentation/video4linux/bttv> for more information.
25190 If you say Y or M here, you need to say Y or M to "I2C support" and
25191 "I2C bit-banging interfaces" in the character device section.
25193 This driver is available as a module called bttv.o ( = code
25194 which can be inserted in and removed from the running kernel
25195 whenever you want). If you want to compile it as a module, say M
25196 here and read <file:Documentation/modules.txt>.
25200 Audio DMA support for bt878 based grabber boards. As you might have
25201 already noticed, bt878 is listed with two functions in /proc/pci.
25202 Function 0 does the video stuff (bt848 compatible), function 1 does
25203 the same for audio data. This is a driver for the audio part of
25204 the chip. If you say 'Y' here you get a oss-compatible dsp device
25205 where you can record from. If you want just watch TV you probably
25206 don't need this driver as most TV cards handle sound with a short
25207 cable from the TV card to your sound card's line-in.
25209 This driver is available as a module called btaudio.o ( = code
25210 which can be inserted in and removed from the running kernel
25211 whenever you want). If you want to compile it as a module, say M
25212 here and read <file:Documentation/modules.txt>.
25214 SGI Vino Video For Linux
25216 Say Y here to include support for SGI VINO (Video In No Out) system
25217 found on SGI Indy workstations.
25219 Stradis 4:2:2 MPEG-2 video driver
25220 CONFIG_VIDEO_STRADIS
25221 Say Y here to enable support for the Stradis 4:2:2 MPEG-2 video
25222 driver for PCI. There is a product page at
25223 <http://www.stradis.com/decoder.html>.
25225 Zoran ZR36057/36060 Video For Linux
25227 Say Y here to include support for video cards based on the Zoran
25228 ZR36057/36060 encoder/decoder chip (including the Iomega Buz and the
25229 Miro DC10 and DC30 video capture cards).
25231 Include support for Iomega Buz
25232 CONFIG_VIDEO_ZORAN_BUZ
25233 Say Y here to include support for the Iomega Buz video card. There
25234 is a Buz/Linux homepage at <http://www.lysator.liu.se/~gz/buz/>.
25236 Miro DC10(+) support
25237 CONFIG_VIDEO_ZORAN_DC10
25238 Say Y to support the Pinnacle Systems Studio DC10 plus TV/Video
25239 card. Linux page at
25240 <http://lhd.datapower.com/db/dispproduct.php3?DISP?1511>. Vendor
25241 page at <http://www.pinnaclesys.com/>.
25243 Linux Media Labs LML33 support
25244 CONFIG_VIDEO_ZORAN_LML33
25245 Say Y here to support the Linux Media Labs LML33 TV/Video card.
25246 Resources page is at <http://www.linuxmedialabs.com/lml33doc.html>.
25248 Zoran ZR36120/36125 Video For Linux
25249 CONFIG_VIDEO_ZR36120
25250 Support for ZR36120/ZR36125 based frame grabber/overlay boards.
25251 This includes the Victor II, WaveWatcher, Video Wonder, Maxi-TV,
25252 and Buster boards. Please read the material in
25253 <file:Documentation/video4linux/zr36120.txt> for more information.
25255 This driver is also available as a module called zr36120.o ( = code
25256 which can be inserted in and removed from the running kernel
25257 whenever you want). If you want to compile it as a module, say M
25258 here and read <file:Documentation/modules.txt>.
25260 SAA5249 Teletext processor
25261 CONFIG_VIDEO_SAA5249
25262 Support for I2C bus based teletext using the SAA5249 chip. At the
25263 moment this is only useful on some European WinTV cards.
25265 This driver is also available as a module called saa5249.o ( = code
25266 which can be inserted in and removed from the running kernel
25267 whenever you want). If you want to compile it as a module, say M
25268 here and read <file:Documentation/modules.txt>.
25270 QuickCam BW Video For Linux
25271 CONFIG_VIDEO_BWQCAM
25272 Say Y have if you the black and white version of the QuickCam
25273 camera. See the next option for the color version.
25275 This driver is also available as a module called bw-qcam.o ( = code
25276 which can be inserted in and removed from the running kernel
25277 whenever you want). If you want to compile it as a module, say M
25278 here and read <file:Documentation/modules.txt>.
25280 QuickCam Colour Video For Linux
25282 This is the video4linux driver for the colour version of the
25283 Connectix QuickCam. If you have one of these cameras, say Y here,
25284 otherwise say N. This driver does not work with the original
25285 monochrome QuickCam, QuickCam VC or QuickClip. It is also available
25286 as a module (c-qcam.o).
25287 Read <file:Documentation/video4linux/CQcam.txt> for more information.
25289 W9966 Webcam (FlyCam Supra and others) Video For Linux
25291 Video4linux driver for Winbond's w9966 based Webcams.
25292 Currently tested with the LifeView FlyCam Supra.
25293 If you have one of these cameras, say Y here
25295 This driver is also available as a module (w9966.o).
25297 Check out <file:drivers/media/video4linux/w9966.txt> and
25298 <file:drivers/media/video/w9966.c> for more information.
25300 Philips SAA7114H for SiByte BCM91250A
25301 CONFIG_VIDEO_SWARM_7114H
25302 Say Y or M to build the video4linux driver for the Philips SAA7114H
25303 video decoder on Broadcom SWARM board (BCM91250A). The decoder chip
25304 is on the BCM1250's "E2" 8-bit FIFO port.
25306 CPiA Video For Linux
25308 This is the video4linux driver for cameras based on Vision's CPiA
25309 (Colour Processor Interface ASIC), such as the Creative Labs Video
25310 Blaster Webcam II. If you have one of these cameras, say Y here
25311 and select parallel port and/or USB lowlevel support below,
25312 otherwise say N. This will not work with the Creative Webcam III.
25314 Please read <file:Documentation/video4linux/README.cpia> for more
25317 This driver is also available as a module (cpia.o).
25319 CPiA Parallel Port Lowlevel Support
25320 CONFIG_VIDEO_CPIA_PP
25321 This is the lowlevel parallel port support for cameras based on
25322 Vision's CPiA (Colour Processor Interface ASIC), such as the
25323 Creative Webcam II. If you have the parallel port version of one
25324 of these cameras, say Y here, otherwise say N. It is also available
25325 as a module (cpia_pp.o).
25327 CPiA USB Lowlevel Support
25328 CONFIG_VIDEO_CPIA_USB
25329 This is the lowlevel USB support for cameras based on Vision's CPiA
25330 (Colour Processor Interface ASIC), such as the Creative Webcam II.
25331 If you have the USB version of one of these cameras, say Y here,
25332 otherwise say N. This will not work with the Creative Webcam III.
25333 It is also available as a module (cpia_usb.o).
25335 Mediavision Pro Movie Studio Video For Linux
25337 Say Y if you have such a thing. This driver is also available as a
25338 module called pms.o ( = code which can be inserted in and removed
25339 from the running kernel whenever you want). If you want to compile
25340 it as a module, say M here and read
25341 <file:Documentation/modules.txt>.
25343 Sony Vaio Picturebook Motion Eye Video For Linux
25345 This is the video4linux driver for the Motion Eye camera found
25346 in the Vaio Picturebook laptops. Please read the material in
25347 <file:Documentation/video4linux/meye.txt> for more information.
25349 If you say Y or M here, you need to say Y or M to "Sony Programmable
25350 I/O Control Device" in the character device section.
25352 This driver is available as a module called meye.o ( = code
25353 which can be inserted in and removed from the running kernel
25354 whenever you want). If you want to compile it as a module, say M
25355 here and read <file:Documentation/modules.txt>.
25357 IBM's S/390 architecture
25359 Select this option, if you want to run the Kernel on one of IBM's
25360 mainframes of the S/390 generation. You should have installed the
25361 s390-compiler released by IBM (based on gcc-2.95.1) before.
25363 Merge some code into the kernel to make the image IPLable
25365 If you want to use the produced kernel to IPL directly from a
25366 device, you have to merge a bootsector specific to the device
25367 into the first bytes of the kernel. You will have to select the
25368 IPL device on another question, that pops up, when you select
25371 IPL from a S/390 tape unit
25373 Select this option if you want to IPL the image from a Tape.
25375 IPL from a virtual card reader emulated by VM/ESA
25377 Select this option if you are running under VM/ESA and want
25378 to IPL the image from the emulated card reader.
25381 Select this option, if you want to use PFAULT pseudo page fault
25382 handling under VM. If running native or in LPAR, this option
25383 has no effect. If your VM does not support PFAULT, PAGEEX
25384 pseudo page fault handling will be used.
25385 Note that VM 4.2 supports PFAULT but has a bug in its
25386 implementation that causes some problems.
25387 Everybody who wants to run Linux under VM != VM4.2 should select
25390 CONFIG_SHARED_KERNEL
25391 Select this option, if you want to share the text segment of the
25392 Linux kernel between different VM guests. This reduces memory
25393 usage with lots of guests but greatly increases kernel size.
25394 You should only select this option if you know what you are
25395 doing and want to exploit this feature.
25397 Support for IBM-style disk-labels (S/390)
25398 CONFIG_S390_PARTITION
25399 Enable this option to assure standard IBM labels on the DASDs.
25400 You must enable it, if you are planning to access DASDs also
25401 attached to another IBM mainframe operation system (OS/390,
25404 Support for DASD hard disks
25406 Enable this option if you want to access DASDs directly utilizing
25407 S/390's or zSeries' channel subsystem commands. This is necessary for running
25408 natively on a single image or an LPAR.
25410 Support for ECKD hard disks
25412 ECKD (Extended Count Key Data) devices are the most commonly used
25413 devices on zSeries and S/390. You should enable this option unless you are
25414 very sure you have no ECKD device.
25416 ECKD demand loading
25417 CONFIG_DASD_AUTO_ECKD
25418 This option enables demand loading of the ECKD module.
25420 Support for FBA hard disks
25422 Select this option if you want to use FBA (Fixed Block) devices.
25423 If you are not sure what it is, say "Y".
25426 CONFIG_DASD_AUTO_FBA
25427 This option enables demand loading of the FBA module.
25429 Support for DIAG access to CMS reserved Disks
25431 Select this option if you want to use CMS reserved Disks under VM
25432 with the Diagnose250 command. If you are not running under VM or
25433 unsure what it is, say "N".
25435 DIAG demand loading
25436 CONFIG_DASD_AUTO_DIAG
25437 This option enables demand loading of the DIAG module.
25439 Merge some code into the kernel to make the image IPLable
25441 If you want to use the produced kernel to IPL directly from a
25442 device, you have to merge a bootsector specific to the device
25443 into the first bytes of the kernel. You will have to select the
25444 IPL device on another question, that pops up, when you select
25447 Support for 3215 line mode terminal
25449 Include support for IBM 3215 line-mode terminals.
25451 Support for console on 3215 line mode terminal
25452 CONFIG_TN3215_CONSOLE
25453 Include support for using an IBM 3215 line-mode terminal as a
25454 Linux system console.
25456 Support for 3270 line mode terminal
25458 Include support for IBM 3270 line-mode terminals.
25460 Support for console on 3270 line mode terminal
25461 CONFIG_TN3270_CONSOLE
25462 Include support for using an IBM 3270 line-mode terminal as a Linux
25463 system console. Available only if 3270 support is compiled in
25466 Support for HWC line mode terminal
25468 Include support for IBM HWC line-mode terminals.
25470 Console on HWC line mode terminal
25472 Include support for using an IBM HWC line-mode terminal as the Linux
25475 Control Program Identification
25477 Allows for Control Program Identification via the HWC interface,
25478 i.e. provides a mean to pass an OS instance name (system name)
25481 This option should only be selected as a module since the
25482 system name has to be passed as module parameter. The module
25483 will be called hwc_cpi.o.
25485 S/390 tape device support
25487 Select this option if you want to access channel-attached tape
25488 devices on IBM S/390 or zSeries.
25489 If you select this option you will also want to select at
25490 least one of the tape interface options and one of the tape
25491 hardware options in order to access a tape device.
25492 This option is also available as a module. The module will be
25493 called tape390.o and include all selected interfaces.
25494 The hardware drivers will be seperate modules.
25495 If unsure, say "Y".
25497 Support for tape character devices
25498 CONFIG_S390_TAPE_CHAR
25499 Select this option if you want to access your channel-attached
25500 tape devices using the character device interface.
25501 This interface is similar to other Linux tape devices like
25502 SCSI-Tapes (st) and the floppy tape device (ftape).
25503 If unsure, say "Y".
25505 Support for tape block devices
25506 CONFIG_S390_TAPE_BLOCK
25507 Select this option if you want to access your channel-attached tape
25508 devices using the block device interface. This interface is similar
25509 to CD-ROM devices on other platforms. The tapes can only be
25510 accessed read-only when using this interface. Have a look at
25511 Documentation/s390/TAPE for further information about creating
25512 volumes for and using this interface. It is safe to say "Y" here.
25514 Support for 3490 tape hardware
25515 CONFIG_S390_TAPE_3490
25516 Select this option if you want to access IBM 3490 magnetic
25517 tape subsystems and 100% compatibles.
25518 This option is also available as a module. The module will be
25519 called tape3490.o. If CONFIG_S390_TAPE is selected as a module,
25520 this hardware driver cannot be built-in but is only available
25522 It is safe to say "Y" here.
25524 Support for 3480 tape hardware
25525 CONFIG_S390_TAPE_3480
25526 Select this option if you want to access IBM 3480 magnetic
25527 tape subsystems and 100% compatibles.
25528 This option is also available as a module. The module will be
25529 called tape3480.o. If CONFIG_S390_TAPE is selected as a module,
25530 this hardware driver cannot be built-in but is only available
25532 It is safe to say "Y" here.
25536 Select this option if you want to use channel-to-channel networking
25537 on IBM S/390 or zSeries. This device driver supports real CTC
25538 coupling using ESCON. It also supports virtual CTCs when running
25539 under VM. It will use the channel device configuration if this is
25540 available. This option is also available as a module which will be
25541 called ctc.o. If you do not know what it is, it's safe to say "Y".
25544 CONFIG_BLK_DEV_XPRAM
25545 Select this option if you want to use your expanded storage on S/390
25546 or zSeries as a disk. This is useful as a _fast_ swap device if you
25547 want to access more than 2G of memory when running in 31 bit mode.
25548 This option is also available as a module which will be called
25549 xpram.o. If unsure, say "N".
25553 Select this option in order to get the interrupts processed faster
25554 on your S/390 or zSeries machine. If selected, after an interrupt
25555 is processed, the channel subsystem will be asked for other pending
25556 interrupts which will also be processed before leaving the interrupt
25557 context. This speeds up the I/O a lot. Say "Y".
25559 IUCV device support (VM only)
25561 Select this option if you want to use inter-user communication
25562 vehicle networking under VM or VIF. This option is also available
25563 as a module which will be called iucv.o. If unsure, say "Y".
25565 Process warning machine checks
25566 CONFIG_MACHCHK_WARNING
25567 Select this option if you want the machine check handler on IBM S/390 or
25568 zSeries to process warning machine checks (e.g. on power failures).
25569 If unsure, say "Y".
25571 Use chscs for Common I/O
25573 Select this option if you want the s390 common I/O layer to use information
25574 obtained by channel subsystem calls. This will enable Linux to process link
25575 failures and resource accessibility events. Moreover, if you have procfs
25576 enabled, you'll be able to toggle chpids logically offline and online. Even
25577 if you don't understand what this means, you should say "Y".
25579 Process warning machine checks
25580 CONFIG_MACHCHK_WARNING
25581 Select this option if you want the machine check handler on IBM S/390 or
25582 zSeries to process warning machine checks (e.g. on power failures).
25583 If unsure, say "Y".
25585 Use chscs for Common I/O
25587 Select this option if you want the s390 common I/O layer to use information
25588 obtained by channel subsystem calls. This will enable Linux to process link
25589 failures and resource accessibility events. Moreover, if you have procfs
25590 enabled, you'll be able to toggle chpids logically offline and online. Even
25591 if you don't understand what this means, you should say "Y".
25593 Kernel support for 31 bit ELF binaries
25594 CONFIG_S390_SUPPORT
25595 Select this option if you want to enable your system kernel to
25596 handle system-calls from ELF binaries for 31 bit ESA. This option
25597 (and some other stuff like libraries and such) is needed for
25598 executing 31 bit applications. It is safe to say "Y".
25600 Channel Device Configuration
25602 The channel device layer is a layer to provide a consistent
25603 interface for configuration & default machine check (devices
25604 appearing & disappearing) handling on Linux for s/390 & z/Series
25607 s/390 & z/Series channel devices include among others
25609 lcs (the most common ethernet/token ring/fddi standard on
25611 ctc/escon hi speed like serial link standard on zSeries
25612 claw used to talk to cisco routers.
25613 qeth gigabit ethernet.
25615 These devices use two channels one read & one write for
25616 configuration & communication (& a third channel, the data
25617 channel the case of gigabit ethernet). The motivation
25618 behind developing this layer was that there was a lot of
25619 duplicate code among the channel device drivers for
25622 Also the lcs & ctc drivers tended to fight over
25623 3088/08's & 3088/1F's which could be either 2216/3172
25624 channel attached lcs compatible devices or escon/ctc pipes
25625 had to be configured separately as they couldn't autodetect,
25626 this is now simplified by doing the configuration in a single
25627 place (the channel device layer).
25629 This layer isn't invasive & it is quite okay to use channel
25630 drivers which don't use the channel device layer in
25631 conjunction with drivers which do.
25633 For more info see the chandev manpage usually distributed in
25634 <file:Documentation/s390/chandev.8> in the Linux source tree.
25636 SAB3036 tuner support
25638 Say Y here to include support for Philips SAB3036 compatible tuners.
25639 If in doubt, say N.
25641 Compaq SMART2 support
25643 This is the driver for Compaq Smart Array controllers. Everyone
25644 using these boards should say Y here. See the file
25645 <file:Documentation/cpqarray.txt> for the current list of boards
25646 supported by this driver, and for further information on the use of
25649 This driver is also available as a module ( = code which can be
25650 inserted in and removed from the running kernel whenever you want).
25651 If you want to compile it as a module, say M here and read
25652 <file:Documentation/modules.txt>. The module will be called
25655 Show crashed user process info
25656 CONFIG_PROCESS_DEBUG
25657 Say Y to print all process fault locations to the console. This is
25658 a debugging option; you probably do not want to set it unless you
25659 are an S390 port maintainer.
25664 # CML2 transition note: CML1 asks ARCH_ARCA5K, then has ARCH_A5K and ARCH_ARK
25665 # as subquestions. CML2 asks the subquestions in the armtype menu and makes
25666 # ARCH_ARCA5K a derived symbol.
25669 This selects what ARM system you wish to build the kernel for. It
25670 also selects to some extent the CPU type. If you are unsure what
25671 to set this option to, please consult any information supplied with
25677 Say Y here to to support the Acorn A5000. Linux can support the
25678 internal IDE disk and CD-ROM interface, serial and parallel port,
25679 and the floppy drive. Note that on some A5000s the floppy is
25680 plugged into the wrong socket on the motherboard.
25684 The Acorn Archimedes was an personal computer based on an 8K ARM2
25685 processor, released in 1987. It supported 512K of RAM and 2 800K
25686 floppy disks. Picture and more detailed specifications at
25687 <http://www.computingmuseum.com/museum/archi.htm>.
25690 CONFIG_ARCH_EBSA110
25691 This is an evaluation board for the StrongARM processor available
25692 from Digital. It has limited hardware on-board, including an onboard
25693 Ethernet interface, two PCMCIA sockets, two serial ports and a
25698 On the Acorn Risc-PC, Linux can support the internal IDE disk and
25699 CD-ROM interface, serial and parallel port, and the floppy drive.
25701 2MB physical memory
25703 Say Y here if your Archimedes or A5000 system has only 2MB of
25704 memory, otherwise say N. The resulting kernel will not run on a
25705 machine with 4MB of memory.
25709 Say Y here if you intend to run this kernel on the CATS.
25711 Saying N will reduce the size of the Footbridge kernel.
25713 EBSA285 (addin mode)
25714 CONFIG_ARCH_EBSA285_ADDIN
25715 Say Y here if you intend to run this kernel on the EBSA285 card
25718 Saying N will reduce the size of the Footbridge kernel.
25720 EBSA285 (host mode)
25721 CONFIG_ARCH_EBSA285_HOST
25722 Say Y here if you intend to run this kernel on the EBSA285 card
25723 in host ("central function") mode.
25725 Saying N will reduce the size of the Footbridge kernel.
25727 LinkUp Systems L7200 SDB
25729 Say Y here if you intend to run this kernel on a LinkUp Systems
25730 L7200 Software Development Board which uses an ARM720T processor.
25731 Information on this board can be obtained at:
25733 <http://www.linkupsys.com/>
25735 If you have any questions or comments about the Linux kernel port
25736 to this board, send e-mail to sjhill@cotw.com.
25739 CONFIG_ARCH_NETWINDER
25740 Say Y here if you intend to run this kernel on the Rebel.COM
25741 NetWinder. Information about this machine can be found at:
25743 <http://www.netwinder.org/>
25745 Saying N will reduce the size of the Footbridge kernel.
25749 Say Y here if you intend to run this kernel on the ARM Prospector
25752 Compaq Personal Server
25753 CONFIG_ARCH_PERSONAL_SERVER
25754 Say Y here if you intend to run this kernel on the Compaq
25757 Saying N will reduce the size of the Footbridge kernel.
25759 The Compaq Personal Server is not available for purchase.
25760 There are no product plans beyond the current research
25761 prototypes at this time. Information is available at:
25763 <http://crl.research.compaq.com/projects/personalserver/>
25765 If you have any questions or comments about the Compaq Personal
25766 Server, send e-mail to skiff@crl.dec.com.
25768 Cirrus Logic EDB-7211 evaluation board
25769 CONFIG_ARCH_EDB7211
25770 Say Y here if you intend to run this kernel on a Cirrus Logic EDB-7211
25773 EP7211 infrared support
25775 Say Y here if you wish to use the infrared port on the EP7211. Note
25776 that you can't use the first UART and the infrared port at the same
25777 time, and that the EP7211 only supports SIR mode, at speeds up to
25778 115.2 kbps. To use the I/R port, you will need to get the source to
25779 irda-utils and apply the patch at
25780 <http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2001-June/003510.html>.
25783 CONFIG_SA1100_ASSABET
25784 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
25785 Microprocessor Development Board (also known as the Assabet).
25788 CONFIG_ASSABET_NEPONSET
25789 Say Y here if you are using the Intel(R) StrongARM(R) SA-1110
25790 Microprocessor Development Board (Assabet) with the SA-1111
25791 Development Board (Nepon).
25794 CONFIG_SA1100_H3600
25795 Say Y here if you intend to run this kernel on the Compaq iPAQ
25796 H3600 handheld computer. Information about this machine and the
25797 Linux port to this machine can be found at:
25799 <http://www.handhelds.org/Compaq/index.html#iPAQ_H3600>
25800 <http://www.compaq.com/products/handhelds/pocketpc/>
25803 CONFIG_SA1100_BRUTUS
25804 Say Y here if you are using the Intel(R) StrongARM(R) SA-1100
25805 Microprocessor Development Board (also known as the Brutus).
25809 Say Y here if you are using the Linux Advanced Radio Terminal
25810 (also known as the LART). See <http://www.lart.tudelft.nl/> for
25811 information on the LART.
25814 CONFIG_SA1100_GRAPHICSCLIENT
25815 Say Y here if you are using an Applied Data Systems Intel(R)
25816 StrongARM(R) SA-1100 based Graphics Client SBC. See
25817 <http://www.applieddata.net/> for information on this system.
25820 CONFIG_SA1100_GRAPHICSMASTER
25821 Say Y here if you are using an Applied Data Systems Intel(R)
25822 StrongARM(R) SA-1100 based Graphics Master SBC with SA-1111
25823 StrongARM companion chip. See
25824 <http://www.applieddata.net/products_masterSpec.asp> for information
25828 CONFIG_SA1100_ADSBITSY
25829 Say Y here if you are using Applied Data Systems Intel(R)
25830 StrongARM(R) 1110 based Bitsy, 3 x 5 inches in size, Compaq - IPAQ -
25832 <http://www.applieddata.net/products_bitsySpec.asp> for more
25837 Say Y here if you are using the Compaq Itsy experimental pocket
25838 computer. See <http://research.compaq.com/wrl/projects/itsy/> for
25843 Say Y here if you are using a Portable Linux Embedded Board
25844 (also known as PLEB). See <http://www.cse.unsw.edu.au/~pleb/>
25845 for more information.
25849 The Intrinsyc CerfBoard is based on the StrongARM 1110.
25850 More information is available at:
25851 <http://www.intrinsyc.com/products/referenceplatforms/cerfboard.html>.
25853 Say Y if configuring for an Intrinsyc CerfBoard.
25857 CONFIG_SA1100_FLEXANET
25858 Say Y here if you intend to run this kernel on the FlexaNet
25859 handheld instruments. Information about this machine can be
25860 found at: <http://www.flexanet.com/>.
25863 CONFIG_SA1100_NANOENGINE
25864 The nanoEngine is a StrongARM 1110-based single board computer
25865 from Bright Star Engineering. More information is available at:
25866 <http://www.brightstareng.com/arm/nanoeng.htm>.
25868 Say Y if configuring for a nanoEngine.
25872 CONFIG_SA1100_PANGOLIN
25873 Pangolin is a StrongARM 1110-based evaluation platform produced
25874 by Dialogue Technology. It has EISA slots for ease of configuration
25875 with SDRAM/Flash memory card, USB/Serial/Audio card, Compact Flash
25876 card, and TFT-LCD card.
25878 Say Y if configuring for a Pangolin.
25882 CONFIG_SA1100_VICTOR
25883 Say Y here if you are using a Visu Aide Intel(R) StrongARM(R)
25884 SA-1100 based Victor Digital Talking Book Reader. See
25885 <http://www.visuaide.com/pagevictor.en.html> for information on
25889 Cerf on-board RAM size
25890 CONFIG_SA1100_CERF_8MB
25891 Declare the size of the CerfBoard's on-board RAM.
25892 Alternatives are 8, 16, 32, and 64MB.
25895 CONFIG_SA1100_CERF_16MB
25896 Declare that the CerfBoard has 16MB RAM.
25899 CONFIG_SA1100_CERF_32MB
25900 Declare that the CerfBoard has 32MB RAM.
25903 CONFIG_SA1100_CERF_64MB
25904 Declare that the CerfBoard has 64MB RAM.
25906 # Choice: cerf_flash
25907 Cerf flash memory size
25908 CONFIG_SA1100_CERF_FLASH_8MB
25909 Tell the Cerf kernel the size of on-board memory. The choices
25910 are 8MB, 16MB, or 32MB.
25913 CONFIG_SA1100_CERF_FLASH_16MB
25914 Configure the Cerf kernel to expect 16MB of flash memory.
25917 CONFIG_SA1100_CERF_FLASH_32MB
25918 Configure the Cerf kernel to expect 32MB of flash memory.
25920 Support ARM610 processor
25922 The ARM610 is the successor to the ARM3 processor
25923 and was produced by VLSI Technology Inc.
25925 Say Y if you want support for the ARM610 processor.
25928 Support ARM710 processor
25930 A 32-bit RISC microprocessor based on the ARM7 processor core
25931 designed by Advanced RISC Machines Ltd. The ARM710 is the
25932 successor to the ARM610 processor. It was released in
25933 July 1994 by VLSI Technology Inc.
25935 Say Y if you want support for the ARM710 processor.
25938 Support ARM720T processor
25940 A 32-bit RISC processor with 8kByte Cache, Write Buffer and
25941 MMU built around an ARM7TDMI core.
25943 Say Y if you want support for the ARM720T processor.
25946 Support ARM920T processor
25948 The ARM920T is licensed to be produced by numerous vendors,
25949 and is used in the Maverick EP9312. More information at
25950 <http://linuxdevices.com/products/PD2382866068.html>.
25952 Say Y if you want support for the ARM920T processor.
25955 Support ARM1020 processor
25957 The ARM1020 is the cached version of the ARM10 processor,
25958 with an addition of a floating-point unit.
25960 Say Y if you want support for the ARM1020 processor.
25964 CONFIG_CPU_ICACHE_DISABLE
25965 Say Y here to disable the processor instruction cache. Unless
25966 you have a reason not to or are unsure, say N.
25969 CONFIG_CPU_DCACHE_DISABLE
25970 Say Y here to disable the processor data cache. Unless
25971 you have a reason not to or are unsure, say N.
25973 Force write through D-cache
25974 CONFIG_CPU_DCACHE_WRITETHROUGH
25975 Say Y here to use the data cache in write-through mode. Unless you
25976 specifically require this or are unsure, say N.
25978 Round robin I and D cache replacement algorithm
25979 CONFIG_CPU_CACHE_ROUND_ROBIN
25980 Say Y here to use the predictable round-robin cache replacement
25981 policy. Unless you specifically require this or are unsure, say N.
25983 Disable branch prediction
25984 CONFIG_CPU_BPREDICT_DISABLE
25985 Say Y here to disable branch prediction. If unsure, say N.
25987 Compressed boot loader in ROM/flash
25989 Say Y here if you intend to execute your compressed kernel image (zImage)
25990 directly from ROM or flash. If unsure, say N.
25992 Compressed ROM boot loader base address
25993 CONFIG_ZBOOT_ROM_TEXT
25994 The base address for zImage. Unless you have special requirements, you
25995 should not change this value.
25997 Compressed ROM boot loader BSS address
25998 CONFIG_ZBOOT_ROM_BSS
25999 The base address of 64KiB of read/write memory, which must be available
26000 while the decompressor is running. Unless you have special requirements,
26001 you should not change this value.
26003 Support StrongARM SA-110 processor
26005 The Intel StrongARM(R) SA-110 is a 32-bit microprocessor and
26006 is available at five speeds ranging from 100 MHz to 233 MHz.
26007 More information is available at
26008 <http://developer.intel.com/design/strong/sa110.htm>.
26010 Say Y if you want support for the SA-110 processor.
26014 CONFIG_SA1100_PFS168
26015 The Radisys Corp. PFS-168 (aka Tulsa) is an Intel® StrongArm® SA-1110 based
26016 computer which includes the SA-1111 Microprocessor Companion Chip and other
26017 custom I/O designed to add connectivity and multimedia features for vending
26018 and business machine applications. Say Y here if you require support for
26022 CONFIG_SA1100_JORNADA720
26023 Say Y here if you want to build a kernel for the HP Jornada 720
26024 handheld computer. See <http://www.hp.com/jornada/products/720>
26027 InHand Electronics OmniMeter
26028 CONFIG_SA1100_OMNIMETER
26029 Say Y here if you are using the inhand electronics OmniMeter. See
26030 <http://www.inhandelectronics.com/html/omni1.html> for details.
26032 Load kernel using Angel Debug Monitor
26034 Say Y if you plan to load the kernel using Angel, ARM Ltd's target
26035 debug stub. If you are not using Angel, you must say N. It is
26036 important to get this setting correct.
26039 CONFIG_ARCH_CDB89712
26040 This is an evaluation board from Cirrus for the CS89712 processor. The
26041 board includes 2 serial ports, Ethernet, IRDA, and expansion headers.
26042 It comes with 16 MB SDRAM and 8 MB flash ROM.
26044 CLPS-711X internal ROM bootstrap
26045 CONFIG_EP72XX_ROM_BOOT
26046 If you say Y here, your CLPS711x-based kernel will use the bootstrap
26047 mode memory map instead of the normal memory map.
26049 Processors derived from the Cirrus CLPS-711X core support two boot modes.
26050 Normal mode boots from the external memory device at CS0. Bootstrap mode
26051 rearranges parts of the memory map, placing an internal 128 byte bootstrap
26052 ROM at CS0. This option performs the address map changes required to
26053 support booting in this mode.
26055 You almost surely want to say N here.
26059 Say Y to include the NWFPE floating point emulator in the kernel.
26060 This is necessary to run most binaries. Linux does not currently
26061 support floating point hardware so you need to say Y here even if
26062 your machine has an FPA or floating point co-processor podule.
26064 It is also possible to say M to build the emulator as a module
26065 (nwfpe.o) or indeed to leave it out altogether. However, unless you
26066 know what you are doing this can easily render your machine
26067 unbootable. Saying Y is the safe option.
26069 You may say N here if you are going to load the Acorn FPEmulator
26070 early in the bootup.
26072 FastFPE math emulation
26074 Say Y here to include the FAST floating point emulator in the kernel.
26075 This is an experimental much faster emulator which has only 32 bit
26076 precision for the mantissa. It does not support any exceptions.
26077 This makes it very simple, it is approximately 4-8 times faster than
26080 It should be sufficient for most programs. It is definitely not
26081 suitable if you do scientific calculations that need double
26082 precision for iteration formulas that sum up lots of very small
26083 numbers. If you do not feel you need a faster FP emulation you
26084 should better choose NWFPE.
26086 It is also possible to say M to build the emulator as a module
26087 (fastfpe.o). But keep in mind that you should only load the FP
26088 emulator early in the bootup. You should never change from NWFPE to
26089 FASTFPE or vice versa in an active system!
26091 DS1620 thermometer support
26093 Say Y here to include support for the thermal management hardware
26094 found in the NetWinder. This driver allows the user to control the
26095 temperature set points and to read the current temperature.
26097 It is also possible to say M here to build it as a module (ds1620.o)
26098 It is recommended to be used on a NetWinder, but it is not a
26101 Check for stack overflows
26102 CONFIG_DEBUG_STACKOVERFLOW
26103 This option make do_IRQ() check for enough stack space beeing left.
26104 This is safe to enable.
26106 Debug high memory support
26107 CONFIG_DEBUG_HIGHMEM
26108 This options enables addition error checking for high memory systems.
26109 Disable for production systems.
26111 Verbose kernel error messages
26112 CONFIG_DEBUG_ERRORS
26113 This option controls verbose debugging information which can be
26114 printed when the kernel detects an internal error. This debugging
26115 information is useful to kernel hackers when tracking down problems,
26116 but mostly meaningless to other people. It's safe to say Y unless
26117 you are concerned with the code size or don't want to see these
26120 Compile kernel with frame pointer
26121 CONFIG_FRAME_POINTER
26122 If you say Y here, the resulting kernel will be slightly larger and
26123 slower, but it will give very useful debugging information. If you
26124 don't debug the kernel, you can say N, but we may not be able to
26125 solve problems without frame pointers.
26127 Verbose user fault messages
26129 When a user program crashes due to an exception, the kernel can
26130 print a brief message explaining what the problem was. This is
26131 sometimes helpful for debugging but serves no purpose on a
26132 production system. Most people should say N here.
26134 Include gdb debugging information in kernel binary
26136 Say Y here to include source-level debugging information in the
26137 `vmlinux' binary image. This is handy if you want to use gdb or
26138 addr2line to debug the kernel. It has no impact on the in-memory
26139 footprint of the running kernel but it can increase the amount of
26140 time and disk space needed for compilation of the kernel. If in
26143 Kernel low-level debugging functions
26145 Say Y here to include definitions of printascii, printchar, printhex
26146 in the kernel. This is helpful if you are debugging code that
26147 executes before the console is initialized.
26149 Kernel low-level debugging messages via footbridge serial port
26150 CONFIG_DEBUG_DC21285_PORT
26151 Say Y here if you want the debug print routines to direct their
26152 output to the serial port in the DC21285 (Footbridge). Saying N
26153 will cause the debug messages to appear on the first 16550
26156 Kernel low-level debugging messages via UART2
26157 CONFIG_DEBUG_CLPS711X_UART2
26158 Say Y here if you want the debug print routines to direct their
26159 output to the second serial port on these devices. Saying N will
26160 cause the debug messages to appear on the first serial port.
26162 Kernel log buffer length shift
26163 CONFIG_LOG_BUF_SHIFT
26164 The kernel log buffer has a fixed size of :
26165 64 kB (2^16) on MULTIQUAD and IA64,
26166 128 kB (2^17) on S390
26167 32 kB (2^15) on SMP systems
26168 16 kB (2^14) on UP systems
26170 You have the ability to change this size with this paramter which
26171 fixes the bit shift of to get the buffer length (which must be a
26172 power of 2). Eg: a value of 16 sets the buffer to 64 kB (2^16).
26173 The default value of 0 uses standard values above.
26175 Disable pgtable cache
26176 CONFIG_NO_PGT_CACHE
26177 Normally the kernel maintains a `quicklist' of preallocated
26178 pagetable structures in order to increase performance. On machines
26179 with very few pages this may however be a loss. Say Y here to
26180 disable the pgtable cache.
26182 RISC OS personality
26184 Say Y here to include the kernel code necessary if you want to run
26185 Acorn RISC OS/Arthur binaries under Linux. This code is still very
26186 experimental; if this sounds frightening, say N and sleep in peace.
26187 You can also say M here to compile this support as a module (which
26188 will be called arthur.o).
26190 Initial kernel command line
26192 On some architectures (EBSA110 and CATS), there is currently no way
26193 for the boot loader to pass arguments to the kernel. For these
26194 architectures, you should supply some command-line options at build
26195 time by entering them here. As a minimum, you should specify the
26196 memory size and the root device (e.g., mem=64M root=/dev/nfs).
26198 Kernel-mode alignment trap handler
26199 CONFIG_ALIGNMENT_TRAP
26200 ARM processors can not fetch/store information which is not
26201 naturally aligned on the bus, i.e., a 4 byte fetch must start at an
26202 address divisible by 4. On 32-bit ARM processors, these non-aligned
26203 fetch/store instructions will be emulated in software if you say
26204 here, which has a severe performance impact. This is necessary for
26205 correct operation of some network protocols. With an IP-only
26206 configuration it is safe to say N, otherwise say Y.
26208 DC21285 serial port support
26209 CONFIG_SERIAL_21285
26210 If you have a machine based on a 21285 (Footbridge) StrongARM(R)/
26211 PCI bridge you can enable its onboard serial port by enabling this
26212 option. The device has major ID 4, minor 64.
26214 Console on DC21285 serial port
26215 CONFIG_SERIAL_21285_CONSOLE
26216 If you have enabled the serial port on the 21285 footbridge you can
26217 make it the console by answering Y to this option.
26219 SA1100 serial port support
26220 CONFIG_SERIAL_SA1100
26221 * Orphaned entry retained 20 April 2001 by Russell King *
26222 * If you read this note from the configurator, please contact *
26223 * the Configure.help maintainers. *
26224 If you have a machine based on a SA1100/SA1110 StrongARM CPU you can
26225 enable its onboard serial port by enabling this option.
26226 Please read <file:Documentation/arm/SA1100/serial_UART> for further
26229 Console on SA1100 serial port
26230 CONFIG_SERIAL_SA1100_CONSOLE
26231 * Orphaned entry retained 20 April 2001 by Russell King *
26232 * If you read this note from the configurator, please contact *
26233 * the Configure.help maintainers. *
26234 If you have enabled the serial port on the SA1100/SA1110 StrongARM
26235 CPU you can make it the console by answering Y to this option.
26237 L7200 serial port support
26238 CONFIG_SERIAL_L7200
26239 * Orphaned entry retained 20 April 2001 by Russell King *
26240 * If you read this note from the configurator, please contact *
26241 * the Configure.help maintainers. *
26242 If you have a LinkUp Systems L7200 board you can enable its two
26243 onboard serial ports by enabling this option. The device numbers
26244 are major ID 4 with minor 64 and 65 respectively.
26246 Console on L7200 serial port
26247 CONFIG_SERIAL_L7200_CONSOLE
26248 * Orphaned entry retained 20 April 2001 by Russell King *
26249 * If you read this note from the configurator, please contact *
26250 * the Configure.help maintainers. *
26251 If you have enabled the serial ports on the L7200 development board
26252 you can make the first serial port the console by answering Y to
26255 L7200 SDB keyboard support
26256 CONFIG_KEYBOARD_L7200
26257 * Orphaned entry retained 20 April 2001 by Russell King *
26258 * If you read this note from the configurator, please contact *
26259 * the Configure.help maintainers. *
26260 Enable this option if you would like to be able to use a keyboard
26261 on a LinkUp Systems L7200 board.
26263 L7200 SDB Fujitsu keyboard support
26264 CONFIG_KEYBOARD_L7200_NORM
26265 * Orphaned entry retained 20 April 2001 by Russell King *
26266 * If you read this note from the configurator, please contact *
26267 * the Configure.help maintainers. *
26268 Select the Fujitsu keyboard if you want a normal QWERTY style
26269 keyboard on the LinkUp SDB.
26271 L7200 SDB Prototype keyboard support
26272 CONFIG_KEYBOARD_L7200_DEMO
26273 * Orphaned entry retained 20 April 2001 by Russell King *
26274 * If you read this note from the configurator, please contact *
26275 * the Configure.help maintainers. *
26276 Select the prototype keyboard if you want to play with the
26277 LCD/keyboard combination on the LinkUp SDB.
26280 CONFIG_HOST_FOOTBRIDGE
26281 * Orphaned entry retained 20 April 2001 by Russell King *
26282 * If you read this note from the configurator, please contact *
26283 * the Configure.help maintainers. *
26284 The 21285 Footbridge chip can operate in either `host mode' or
26285 `add-in' mode. Say Y if your 21285 is in host mode, and therefore
26286 is the configuration master, otherwise say N. This must not be
26287 set to Y if the card is used in 'add-in' mode.
26289 MFM hard disk support
26291 Support the MFM hard drives on the Acorn Archimedes both
26292 on-board the A4x0 motherboards and via the Acorn MFM modules.
26293 Drives up to 64MB are supported. If you haven't got one of these
26294 machines or drives just say N.
26296 Old Archimedes floppy (1772) support
26297 CONFIG_BLK_DEV_FD1772
26298 Support the floppy drive on the Acorn Archimedes (A300, A4x0, A540,
26299 R140 and R260) series of computers; it supports only 720K floppies
26300 at the moment. If you don't have one of these machines just answer
26303 Autodetect hard drive geometry
26304 CONFIG_BLK_DEV_MFM_AUTODETECT
26305 If you answer Y, the MFM code will attempt to automatically detect
26306 the cylinders/heads/sectors count on your hard drive. WARNING: This
26307 sometimes doesn't work and it also does some dodgy stuff which
26308 potentially might damage your drive.
26310 NetWinder /dev/flash support
26312 If you say Y here and create a character device /dev/flash with
26313 major 10 and minor 160 you can manipulate the flash ROM containing
26314 the NetWinder firmware. Be careful as accidentally overwriting the
26315 flash contents can render your computer unbootable. On no account
26316 allow random users access to this device. :-)
26318 This driver is also available as a module ( = code which can be
26319 inserted in and removed from the running kernel whenever you want).
26320 The module will be called nwflash.o. If you want to compile it as a
26321 module, say M here and read <file:Documentation/modules.txt>.
26323 If you're not sure, say N.
26325 SRM environment variables in procfs
26327 If you enable this option, a subdirectory inside /proc called
26328 /proc/srm_environment will give you access to the all important
26329 SRM environment variables (those which have a name) and also
26330 to all others (by their internal number).
26332 SRM is something like a BIOS for Alpha machines. There are some
26333 other such BIOSes, like AlphaBIOS, which this driver cannot
26334 support (hey, that's not SRM!).
26336 Despite the fact that this driver doesn't work on all Alphas (but
26337 only on those which have SRM as their firmware), it's save to
26338 build it even if your particular machine doesn't know about SRM
26339 (or if you intend to compile a generic kernel). It will simply
26340 not create those subdirectory in /proc (and give you some warning,
26343 This driver is also available as a module and will be called
26346 Footbridge internal watchdog
26347 CONFIG_21285_WATCHDOG
26348 The Intel Footbridge chip contains a builtin watchdog circuit. Say Y
26349 here if you wish to use this. Alternatively say M to compile the
26350 driver as a module, which will be called wdt285.o.
26352 This driver does not work on all machines. In particular, early CATS
26353 boards have hardware problems that will cause the machine to simply
26354 lock up if the watchdog fires.
26356 "If in doubt, leave it out" - say N.
26358 NetWinder WB83C977 watchdog
26359 CONFIG_977_WATCHDOG
26360 Say Y here to include support for the WB977 watchdog included in
26361 NetWinder machines. Alternatively say M to compile the driver as
26362 a module, which will be called wdt977.o.
26364 Not sure? It's safe to say N.
26366 IrDA subsystem support
26368 Say Y here if you want to build support for the IrDA (TM) protocols.
26369 The Infrared Data Associations (tm) specifies standards for wireless
26370 infrared communication and is supported by most laptops and PDA's.
26372 To use Linux support for the IrDA (tm) protocols, you will also need
26373 some user-space utilities like irattach. For more information, see
26374 the file <file:Documentation/networking/irda.txt>. You also want to
26375 read the IR-HOWTO, available at
26376 <http://www.tldp.org/docs.html#howto>.
26378 If you want to exchange bits of data (vCal, vCard) with a PDA, you
26379 will need to install some OBEX application, such as OpenObex :
26380 <http://sourceforge.net/projects/openobex/>
26382 This support is also available as a module called irda.o. If you
26383 want to compile it as a module, say M here and read
26384 <file:Documentation/modules.txt>.
26386 Ultra (connectionless) protocol
26388 Say Y here to support the connectionless Ultra IRDA protocol.
26389 Ultra allows to exchange data over IrDA with really simple devices
26390 (watch, beacon) without the overhead of the IrDA protocol (no handshaking,
26391 no management frames, simple fixed header).
26392 Ultra is available as a special socket : socket(AF_IRDA, SOCK_DGRAM, 1);
26394 IrDA cache last LSAP
26395 CONFIG_IRDA_CACHE_LAST_LSAP
26396 Say Y here if you want IrLMP to cache the last LSAP used. This
26397 makes sense since most frames will be sent/received on the same
26398 connection. Enabling this option will save a hash-lookup per frame.
26403 CONFIG_IRDA_FAST_RR
26404 Say Y here is you want IrLAP to send fast RR (Receive Ready) frames
26405 when acting as a primary station.
26406 Disabling this option will make latency over IrDA very bad. Enabling
26407 this option will make the IrDA stack send more packet than strictly
26408 necessary, thus reduce your battery life (but not that much).
26410 Fast RR will make IrLAP send out a RR frame immediately when
26411 receiving a frame if its own transmit queue is currently empty. This
26412 will give a lot of speed improvement when receiving much data since
26413 the secondary station will not have to wait the max. turn around
26414 time (usually 500ms) before it is allowed to transmit the next time.
26415 If the transmit queue of the secondary is also empty, the primary will
26416 start backing-off before sending another RR frame, waiting longer
26417 each time until the back-off reaches the max. turn around time.
26418 This back-off increase in controlled via
26419 /proc/sys/net/irda/fast_poll_increase
26423 IrDA debugging information
26425 Say Y here if you want the IrDA subsystem to write debug information
26426 to your syslog. You can change the debug level in
26427 /proc/sys/net/irda/debug .
26428 When this option is enabled, the IrDA also perform many extra internal
26429 verifications which will usually prevent the kernel to crash in case of
26432 If unsure, say Y (since it makes it easier to find the bugs).
26436 Say Y here if you want to build support for the IrLAN protocol. If
26437 you want to compile it as a module (irlan.o), say M here and read
26438 <file:Documentation/modules.txt>. IrLAN emulates an Ethernet and
26439 makes it possible to put up a wireless LAN using infrared beams.
26441 The IrLAN protocol can be used to talk with infrared access points
26442 like the HP NetbeamIR, or the ESI JetEye NET. You can also connect
26443 to another Linux machine running the IrLAN protocol for ad-hoc
26448 Say Y here if you want to build support for the IrNET protocol. If
26449 you want to compile it as a module (irnet.o), say M here and read
26450 <file:Documentation/modules.txt>. IrNET is a PPP driver, so you
26451 will also need a working PPP subsystem (driver, daemon and
26454 IrNET is an alternate way to transfer TCP/IP traffic over IrDA. It
26455 uses synchronous PPP over a set of point to point IrDA sockets. You
26456 can use it between Linux machine or with W2k.
26460 Say Y here if you want to build support for the IrCOMM protocol. If
26461 you want to compile it as a module (you will get ircomm.o and
26462 ircomm-tty.o), say M here and read <file:Documentation/modules.txt>.
26463 IrCOMM implements serial port emulation, and makes it possible to
26464 use all existing applications that understands TTY's with an
26465 infrared link. Thus you should be able to use application like PPP,
26466 minicom and others. Enabling this option will create two modules
26467 called ircomm and ircomm_tty.
26469 IrTTY IrDA Device Driver
26471 Say Y here if you want to build support for the IrTTY line
26472 discipline. If you want to compile it as a module (irtty.o), say M
26473 here and read <file:Documentation/modules.txt>. IrTTY makes it
26474 possible to use Linux's own serial driver for all IrDA ports that
26475 are 16550 compatible. Most IrDA chips are 16550 compatible so you
26476 should probably say Y to this option. Using IrTTY will however
26477 limit the speed of the connection to 115200 bps (IrDA SIR mode).
26481 IrPORT IrDA serial driver
26483 Say Y here if you want to build support for the IrPORT IrDA device
26484 driver. If you want to compile it as a module (irport.o), say M here
26485 and read <file:Documentation/modules.txt>. IrPORT can be used
26486 instead of IrTTY and sometimes this can be better. One example is
26487 if your IrDA port does not have echo-canceling, which will work OK
26488 with IrPORT since this driver is working in half-duplex mode only.
26489 You don't need to use irattach with IrPORT, but you just insert it
26490 the same way as FIR drivers (insmod irport io=0x3e8 irq=11). Notice
26491 that IrPORT is a SIR device driver which means that speed is limited
26496 USB IrDA FIR dongle Device Driver
26498 Say Y here if you want to build support for the USB IrDA FIR Dongle
26499 device driver. If you want to compile it as a module (irda-usb.o),
26500 say M here and read <file:Documentation/modules.txt>. IrDA-USB
26501 support the various IrDA USB dongles available and most of their
26502 peculiarities. Those dongles plug in the USB port of your computer,
26503 are plug and play, and support SIR and FIR (4Mbps) speeds. On the
26504 other hand, those dongles tend to be less efficient than a FIR
26507 Please note that the driver is still experimental. And of course,
26508 you will need both USB and IrDA support in your kernel...
26510 Datafab MDCFE-B Compact Flash Reader support
26511 CONFIG_USB_STORAGE_DATAFAB
26512 This option enables a sub-driver of the USB Mass Storage driver. These
26513 sub-drivers are considered experimental, and should only be used by very
26514 brave people. System crashes and other bad things are likely to occur if
26515 you use this driver. If in doubt, select N.
26517 HP CD-Writer 82xx support
26518 CONFIG_USB_STORAGE_HP8200e
26519 This option enables a sub-driver of the USB Mass Storage driver. These
26520 sub-drivers are considered experimental, and should only be used by very
26521 brave people. System crashes and other bad things are likely to occur if
26522 you use this driver. If in doubt, select N.
26524 Lexar Jumpshot Compact Flash Reader
26525 CONFIG_USB_STORAGE_JUMPSHOT
26526 This option enables a sub-driver of the USB Mass Storage driver. These
26527 sub-drivers are considered experimental, and should only be used by very
26528 brave people. System crashes and other bad things are likely to occur if
26529 you use this driver. If in doubt, select N.
26531 Tieman Voyager USB Braille display support (EXPERIMENTAL)
26533 Say Y here if you want to use the Voyager USB Braille display from
26534 Tieman. See <file:Documentation/usb/brlvger.txt> for more
26537 This code is also available as a module ( = code which can be
26538 inserted in and removed from the running kernel whenever you want).
26539 The module will be called brlvger.o. If you want to compile it as
26540 a module, say M here and read <file:Documentation/modules.txt>.
26542 KB Gear JamStudio tablet support
26544 Say Y here if you want to use the USB version of the KB Gear
26545 JamStudio tablet. Make sure to say Y to "Mouse support"
26546 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
26547 (CONFIG_INPUT_EVDEV) as well.
26549 This driver is also available as a module ( = code which can be
26550 inserted in and removed from the running kernel whenever you want).
26551 The module will be called kbtab.o. If you want to compile it as a
26552 module, say M here and read <file:Documentation/modules.txt>.
26554 USB Inside Out Edgeport Serial Driver (TI devices)
26555 CONFIG_USB_SERIAL_EDGEPORT_TI
26556 Say Y here if you want to use any of the devices from Inside Out
26557 Networks (Digi) that are not supported by the io_edgeport driver.
26558 This includes the Edgeport/1 device.
26560 This code is also available as a module ( = code which can be
26561 inserted in and removed from the running kernel whenever you want).
26562 The module will be called io_ti.o. If you want to compile it
26563 as a module, say M here and read <file:Documentation/modules.txt>.
26565 USB Keyspan MPR Firmware
26566 CONFIG_USB_SERIAL_KEYSPAN_MPR
26567 Say Y here to include firmware for the Keyspan MPR converter.
26569 Winbond W83977AF IrDA Device Driver
26571 Say Y here if you want to build IrDA support for the Winbond
26572 W83977AF super-io chipset. This driver should be used for the IrDA
26573 chipset in the Corel NetWinder. The driver supports SIR, MIR and
26574 FIR (4Mbps) speeds.
26576 If you want to compile it as a module, say M here and read
26577 <file:Documentation/modules.txt>. The module will be called
26580 NSC PC87108/PC87338 IrDA Device Driver
26582 Say Y here if you want to build support for the NSC PC87108 and
26583 PC87338 IrDA chipsets. This driver supports SIR,
26584 MIR and FIR (4Mbps) speeds.
26586 If you want to compile it as a module, say M here and read
26587 <file:Documentation/modules.txt>. The module will be called
26590 National Semiconductor DP83820 support
26592 This is a driver for the National Semiconductor DP83820 series
26593 of gigabit ethernet MACs. Cards using this chipset include:
26595 SMC 9452TX SMC SMC9462TX
26596 D-Link DGE-500T PureData PDP8023Z-TG
26597 SOHO-GA2000T SOHO-GA2500T.
26600 This driver supports the use of zero copy on tx, checksum
26601 validation on rx, and 64 bit addressing.
26603 If you want to compile the driver as a module ( = code which can be
26604 inserted in and removed from the running kernel whenever you want),
26605 say M here and read <file:Documentation/modules.txt>. The module
26606 will be called ns83820.o.
26608 Toshiba Type-O IR Port device driver (old driver)
26610 Say Y here if you want to build support for the Toshiba Type-O IR
26611 chipset. This chipset is used by the Toshiba Libretto 100CT, and
26612 many more laptops. This driver is obsolete, will no more be
26613 maintained and will be removed in favor of the new driver.
26614 If you want to compile it as a module, say M here and read
26615 <file:Documentation/modules.txt>.
26616 The module will be called toshoboe.o.
26618 Toshiba Type-O IR Port device driver
26620 Say Y here if you want to build support for the Toshiba Type-O IR
26621 and Donau oboe chipsets. These chipsets are used by the Toshiba
26622 Libretto 100/110CT, Tecra 8100, Portege 7020 and many more laptops.
26623 If you want to compile it as a module, say M here and read
26624 <file:Documentation/modules.txt>.
26625 The module will be called donauboe.o.
26628 CONFIG_SMC_IRCC_FIR
26629 Say Y here if you want to build support for the SMC Infrared
26630 Communications Controller. It is used in the Fujitsu Lifebook 635t
26631 and Sony PCG-505TX. If you want to compile it as a module, say M
26632 here and read <file:Documentation/modules.txt>. The module will be
26636 CONFIG_VIA_IRCC_FIR
26637 Say Y here if you want to build support for the VIA Fast Infrared
26638 Communications Controller. It is used in all sorts of VIA686a- and
26639 VT1211-based notebooks. If you want to compile it as a module, say M
26640 here and read <file:Documentation/modules.txt>. The module will be
26643 ALi M5123 FIR controller driver
26645 Say Y here if you want to build support for the ALi M5123 FIR
26646 Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C,
26647 M1535, M1535D, M1535+, M1535D Sourth Bridge. This driver supports
26648 SIR, MIR and FIR (4Mbps) speeds.
26650 If you want to compile it as a module, say M here and read
26651 <file:Documentation/modules.txt>. The module will be called
26654 VLSI 82C147 PCI-IrDA SIR/MIR/FIR Controller driver
26656 Say Y here if you want to build support for the VLSI 82C147
26657 PCI-IrDA Controller. This controller is used by the HP OmniBook 800
26658 and 5500 notebooks. The driver provides support for SIR, MIR and
26659 FIR (4Mbps) speeds.
26661 If you want to compile it as a module, say M here and read
26662 <file:Documentation/modules.txt>. The module will be called vlsi_ir.o.
26664 Serial dongle support
26666 Say Y here if you have an infrared device that connects to your
26667 computer's serial port. These devices are called dongles. Then say Y
26668 or M to the driver for your particular dongle below.
26670 Note that the answer to this question won't directly affect the
26671 kernel: saying N will just cause the configurator to skip all
26672 the questions about serial dongles.
26674 ESI JetEye PC dongle
26676 Say Y here if you want to build support for the Extended Systems
26677 JetEye PC dongle. If you want to compile it as a module, say M here
26678 and read <file:Documentation/modules.txt>. The ESI dongle attaches
26679 to the normal 9-pin serial port connector, and can currently only be
26680 used by IrTTY. To activate support for ESI dongles you will have to
26681 start irattach like this: "irattach -d esi".
26683 If you want to compile the driver as a module ( = code which can be
26684 inserted in and removed from the running kernel whenever you want),
26685 say M here and read <file:Documentation/modules.txt>. The module
26686 will be called esi.o.
26688 ACTiSYS IR-220L and IR220L+ dongle
26689 CONFIG_ACTISYS_DONGLE
26690 Say Y here if you want to build support for the ACTiSYS IR-220L and
26691 IR220L+ dongles. If you want to compile it as a module, say M here
26692 and read <file:Documentation/modules.txt>. The ACTiSYS dongles
26693 attaches to the normal 9-pin serial port connector, and can
26694 currently only be used by IrTTY. To activate support for ACTiSYS
26695 dongles you will have to start irattach like this:
26696 "irattach -d actisys" or "irattach -d actisys+".
26698 If you want to compile the driver as a module ( = code which can be
26699 inserted in and removed from the running kernel whenever you want),
26700 say M here and read <file:Documentation/modules.txt>. The module
26701 will be called actisys.o.
26703 Tekram IrMate 210B dongle
26704 CONFIG_TEKRAM_DONGLE
26705 Say Y here if you want to build support for the Tekram IrMate 210B
26706 dongle. If you want to compile it as a module, say M here and read
26707 <file:Documentation/modules.txt>. The Tekram dongle attaches to the
26708 normal 9-pin serial port connector, and can currently only be used
26709 by IrTTY. To activate support for Tekram dongles you will have to
26710 start irattach like this: "irattach -d tekram".
26712 If you want to compile the driver as a module ( = code which can be
26713 inserted in and removed from the running kernel whenever you want),
26714 say M here and read <file:Documentation/modules.txt>. The module
26715 will be called tekram.o.
26717 Greenwich GIrBIL dongle
26718 CONFIG_GIRBIL_DONGLE
26719 Say Y here if you want to build support for the Greenwich GIrBIL
26720 dongle. If you want to compile it as a module, say M here and read
26721 <file:Documentation/modules.txt>. The Greenwich dongle attaches to
26722 the normal 9-pin serial port connector, and can currently only be
26723 used by IrTTY. To activate support for Greenwich dongles you will
26724 have to insert "irattach -d girbil" in the /etc/irda/drivers script.
26726 If you want to compile the driver as a module ( = code which can be
26727 inserted in and removed from the running kernel whenever you want),
26728 say M here and read <file:Documentation/modules.txt>. The module
26729 will be called girbil.o.
26731 Parallax LiteLink dongle
26732 CONFIG_LITELINK_DONGLE
26733 Say Y here if you want to build support for the Parallax Litelink
26734 dongle. If you want to compile it as a module, say M here and read
26735 <file:Documentation/modules.txt>. The Parallax dongle attaches to
26736 the normal 9-pin serial port connector, and can currently only be
26737 used by IrTTY. To activate support for Parallax dongles you will
26738 have to start irattach like this "irattach -d litelink".
26740 If you want to compile the driver as a module ( = code which can be
26741 inserted in and removed from the running kernel whenever you want),
26742 say M here and read <file:Documentation/modules.txt>. The module
26743 will be called litelink.o.
26745 Microchip MCP2120 dongle
26746 CONFIG_MCP2120_DONGLE
26747 Say Y here if you want to build support for the Microchip MCP2120
26748 dongle. If you want to compile it as a module, say M here and read
26749 <file:Documentation/modules.txt>. The MCP2120 dongle attaches to
26750 the normal 9-pin serial port connector, and can currently only be
26751 used by IrTTY. To activate support for MCP2120 dongles you will
26752 have to insert "irattach -d mcp2120" in the /etc/irda/drivers script.
26754 You must build this dongle yourself. For more information see:
26755 <http://www.eyetap.org/~tangf/irda_sir_linux.html>
26758 CONFIG_OLD_BELKIN_DONGLE
26759 Say Y here if you want to build support for the Adaptec Airport 1000
26760 and 2000 dongles. If you want to compile it as a module, say M here
26761 and read <file:Documentation/modules.txt>. The module will be
26762 called old_belkin.o. Some information is contained in the comments
26763 at the top of <file:drivers/net/irda/old_belkin.c>.
26765 ACTiSYS IR-200L dongle (Experimental)
26766 CONFIG_ACT200L_DONGLE
26767 Say Y here if you want to build support for the ACTiSYS IR-200L
26768 dongle. If you want to compile it as a module, say M here and read
26769 Documentation/modules.txt. The ACTiSYS IR-200L dongle attaches to
26770 the normal 9-pin serial port connector, and can currently only be
26771 used by IrTTY. To activate support for ACTiSYS IR-200L dongles
26772 you will have to start irattach like this: "irattach -d act200l".
26774 Mobile Action MA600 dongle (Experimental)
26775 CONFIG_MA600_DONGLE
26776 Say Y here if you want to build support for the Mobile Action MA600
26777 dongle. If you want to compile it as a module, say M here and read
26778 <file:Documentation/modules.txt>. The MA600 dongle attaches to
26779 the normal 9-pin serial port connector, and can currently only be
26780 tested on IrCOMM. To activate support for MA600 dongles you will
26781 have to insert "irattach -d ma600" in the /etc/irda/drivers script.
26782 Note: irutils 0.9.15 requires no modification. irutils 0.9.9 needs
26783 modification. For more information, download the following tar gzip
26786 There is a pre-compiled module on
26787 <http://engsvr.ust.hk/~eetwl95/download/ma600-2.4.x.tar.gz>
26789 VME (Motorola and BVM) support
26791 Say Y here if you want to build a kernel for a 680x0 based VME
26792 board. Boards currently supported include Motorola boards MVME147,
26793 MVME162, MVME166, MVME167, MVME172, and MVME177. BVME4000 and
26794 BVME6000 boards from BVM Ltd are also supported.
26798 Say Y to include support for early Motorola VME boards. This will
26799 build a kernel which can run on MVME147 single-board computers. If
26800 you select this option you will have to select the appropriate
26801 drivers for SCSI, Ethernet and serial ports later on.
26803 MVME162, 166 and 167 support
26805 Say Y to include support for Motorola VME boards. This will build a
26806 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
26807 MVME177 boards. If you select this option you will have to select
26808 the appropriate drivers for SCSI, Ethernet and serial ports later
26811 BVME4000 and BVME6000 support
26813 Say Y to include support for VME boards from BVM Ltd. This will
26814 build a kernel which can run on BVME4000 and BVME6000 boards. If
26815 you select this option you will have to select the appropriate
26816 drivers for SCSI, Ethernet and serial ports later on.
26818 Use write-through caching for 68060 supervisor accesses
26819 CONFIG_060_WRITETHROUGH
26820 The 68060 generally uses copyback caching of recently accessed data.
26821 Copyback caching means that memory writes will be held in an on-chip
26822 cache and only written back to memory some time later. Saying Y
26823 here will force supervisor (kernel) accesses to use writethrough
26824 caching. Writethrough caching means that data is written to memory
26825 straight away, so that cache and memory data always agree.
26826 Writethrough caching is less efficient, but is needed for some
26827 drivers on 68060 based systems where the 68060 bus snooping signal
26828 is hardwired on. The 53c710 SCSI driver is known to suffer from
26831 WD33C93 SCSI driver for MVME147
26832 CONFIG_MVME147_SCSI
26833 Support for the on-board SCSI controller on the Motorola MVME147
26834 single-board computer.
26836 SCC support for MVME147 serial ports
26838 This is the driver for the serial ports on the Motorola MVME147
26839 boards. Everyone using one of these boards should say Y here.
26841 NCR53C710 SCSI driver for MVME16x
26842 CONFIG_MVME16x_SCSI
26843 The Motorola MVME162, 166, 167, 172 and 177 boards use the NCR53C710
26844 SCSI controller chip. Almost everyone using one of these boards
26845 will want to say Y to this question.
26847 NCR53C710 SCSI driver for BVME6000
26848 CONFIG_BVME6000_SCSI
26849 The BVME4000 and BVME6000 boards from BVM Ltd use the NCR53C710
26850 SCSI controller chip. Almost everyone using one of these boards
26851 will want to say Y to this question.
26853 MVME147 (Lance) Ethernet support
26855 Support for the on-board Ethernet interface on the Motorola MVME147
26856 single-board computer. Say Y here to include the
26857 driver for this chip in your kernel. If you want to compile it as
26858 a module, say M here and read <file:Documentation/modules.txt>.
26860 MVME16x Ethernet support
26862 This is the driver for the Ethernet interface on the Motorola
26863 MVME162, 166, 167, 172 and 177 boards. Say Y here to include the
26864 driver for this chip in your kernel. If you want to compile it as
26865 a module, say M here and read <file:Documentation/modules.txt>.
26867 BVME6000 Ethernet support
26868 CONFIG_BVME6000_NET
26869 This is the driver for the Ethernet interface on BVME4000 and
26870 BVME6000 VME boards. Say Y here to include the driver for this chip
26871 in your kernel. If you want to compile it as a module, say M here
26872 and read <file:Documentation/modules.txt>.
26874 CD2401 support for MVME166/7 serial ports
26876 This is the driver for the serial ports on the Motorola MVME166,
26877 167, and 172 boards. Everyone using one of these boards should say
26880 SCC support for MVME162 serial ports
26882 This is the driver for the serial ports on the Motorola MVME162 and
26883 172 boards. Everyone using one of these boards should say Y here.
26885 SCC support for BVME6000 serial ports
26886 CONFIG_BVME6000_SCC
26887 This is the driver for the serial ports on the BVME4000 and BVME6000
26888 boards from BVM Ltd. Everyone using one of these boards should say
26891 7-Segment Display support
26893 This is the driver for the 7-segment display and LED present on
26894 Sun Microsystems CompactPCI models CP1400 and CP1500.
26896 This driver is also available as a module ( = code which can be
26897 inserted in and removed from the running kernel whenever you want).
26898 The module will be called display7seg.o. If you want to compile it
26899 as a module, say M here and read <file:Documentation/modules.txt>.
26901 If you do not have a CompactPCI model CP1400 or CP1500, or
26902 another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
26903 you should say N to this option.
26908 Support version 1 of the Etrax 100LX.
26911 CONFIG_ETRAX100LX_V2
26912 Support version 2 of the Etrax 100LX.
26914 Etrax-100-LX-for-xsim-simulator
26916 Support the xsim ETRAX Simulator.
26918 DRAM size (dec, in MB)
26919 CONFIG_ETRAX_DRAM_SIZE
26920 Size of DRAM (decimal in MB) typically 2, 8 or 16.
26922 ETRAX Flash Memory configuration
26923 CONFIG_ETRAX_FLASH_BUSWIDTH
26924 Width in bytes of the Flash bus (1, 2 or 4). Is usually 2.
26927 LED configuration on PA
26928 CONFIG_ETRAX_PA_LEDS
26929 The Etrax network driver is responsible for flashing LED's when
26930 packets arrive and are sent. It uses macros defined in
26931 <file:include/asm-cris/io.h>, and those macros are defined after what
26932 YOU choose in this option. The actual bits used are configured
26933 separately. Select this if the LEDs are on port PA. Some products
26934 put the leds on PB or a memory-mapped latch (CSP0) instead.
26936 LED configuration on PB
26937 CONFIG_ETRAX_PB_LEDS
26938 The Etrax network driver is responsible for flashing LED's when
26939 packets arrive and are sent. It uses macros defined in
26940 <file:include/asm-cris/io.h>, and those macros are defined after what
26941 YOU choose in this option. The actual bits used are configured
26942 separately. Select this if the LEDs are on port PB. Some products
26943 put the leds on PA or a memory-mapped latch (CSP0) instead.
26945 LED configuration on CSP0
26946 CONFIG_ETRAX_CSP0_LEDS
26947 The Etrax network driver is responsible for flashing LED's when
26948 packets arrive and are sent. It uses macros defined in
26949 <file:include/asm-cris/io.h>, and those macros are defined after what
26950 YOU choose in this option. The actual bits used are configured
26951 separately. Select this if the LEDs are on a memory-mapped latch
26952 using chip select CSP0, this is mapped at 0x90000000.
26953 Some products put the leds on PA or PB instead.
26956 CONFIG_ETRAX_NO_LEDS
26957 Select this option if you don't have any LED at all.
26959 First green LED bit
26961 Bit to use for the first green LED.
26962 Most Axis products use bit 2 here.
26966 Bit to use for the first red LED.
26967 Most Axis products use bit 3 here.
26968 For products with only one controllable LED,
26969 set this to same as CONFIG_ETRAX_LED1G (normally 2).
26971 Second green LED bit
26973 Bit to use for the second green LED. The "Active" LED.
26974 Most Axis products use bit 4 here.
26975 For products with only one controllable LED,
26976 set this to same as CONFIG_ETRAX_LED1G (normally 2).
26980 Bit to use for the second red LED.
26981 Most Axis products use bit 5 here.
26982 For products with only one controllable LED,
26983 set this to same as CONFIG_ETRAX_LED1G (normally 2).
26985 Third green LED bit
26987 Bit to use for the third green LED. The "Drive" LED.
26988 For products with only one or two controllable LEDs,
26989 set this to same as CONFIG_ETRAX_LED1G (normally 2).
26993 Bit to use for the third red LED.
26994 For products with only one or two controllable LEDs,
26995 set this to same as CONFIG_ETRAX_LED1G (normally 2).
26997 Fourth green LED bit
26999 Bit to use for the fourth green LED.
27000 For products with only one or two controllable LEDs,
27001 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27005 Bit to use for the fourth red LED.
27006 For products with only one or two controllable LEDs,
27007 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27009 Fifth green LED bit
27011 Bit to use for the fifth green LED.
27012 For products with only one or two controllable LEDs,
27013 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27017 Bit to use for the fifth red LED.
27018 For products with only one or two controllable LEDs,
27019 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27021 Sixth green LED bit
27023 Bit to use for the sixth green LED. The "Drive" LED.
27024 For products with only one or two controllable LEDs,
27025 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27029 Bit to use for the sixth red LED.
27030 For products with only one or two controllable LEDs,
27031 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27033 Seventh green LED bit
27035 Bit to use for the seventh green LED.
27036 For products with only one or two controllable LEDs,
27037 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27039 Seventh red LED bit
27041 Bit to use for the seventh red LED.
27042 For products with only one or two controllable LEDs,
27043 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27045 Eighth yellow LED bit
27047 Bit to use for the eighth yellow LED. The "Drive" LED.
27048 For products with only one or two controllable LEDs,
27049 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27051 Ninth yellow LED bit
27053 Bit to use for the ninth yellow LED.
27054 For products with only one or two controllable LEDs,
27055 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27057 Tenth yellow LED bit
27058 CONFIG_ETRAX_LED10Y
27059 Bit to use for the tenth yellow LED.
27060 For products with only one or two controllable LEDs,
27061 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27063 Eleventh yellow LED bit
27064 CONFIG_ETRAX_LED11Y
27065 Bit to use for the eleventh yellow LED.
27066 For products with only one or two controllable LEDs,
27067 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27069 Twelfth red LED bit
27070 CONFIG_ETRAX_LED12R
27071 Bit to use for the twelfth red LED.
27072 For products with only one or two controllable LEDs,
27073 set this to same as CONFIG_ETRAX_LED1G (normally 2).
27075 Flash LED off during activity
27076 CONFIG_ETRAX_LED_OFF_DURING_ACTIVITY
27077 This option allows you to decide whether the network LED (and
27078 Bluetooth LED in case you use Bluetooth) will be on or off when
27079 the network is connected, and whether it should flash off or on
27080 when there is activity. If you say y to this option the network
27081 LED will be lit when there is a connection, and will flash off
27082 when there is activity.
27084 PA button configuration
27085 CONFIG_ETRAX_PA_BUTTON_BITMASK
27086 This is a bitmask with information about what bits on PA that
27087 are used for buttons.
27088 Most products has a so called TEST button on PA1, if that's true
27090 Use 00 if there are no buttons on PA.
27091 If the bitmask is <> 00 a button driver will be included in the gpio
27092 driver. Etrax general I/O support must be enabled.
27094 PA changeable direction bits
27095 CONFIG_ETRAX_PA_CHANGEABLE_DIR
27096 This is a bitmask with information of what bits in PA that a user
27097 can change direction on using ioctl's.
27098 Bit set = changeable.
27099 You probably want 00 here.
27101 PA changeable data bits
27102 CONFIG_ETRAX_PA_CHANGEABLE_BITS
27103 This is a bitmask with information of what bits in PA that a user
27104 can change change the value on using ioctl's.
27105 Bit set = changeable.
27106 You probably want 00 here.
27108 PA changeable direction bits
27109 CONFIG_ETRAX_PB_CHANGEABLE_DIR
27110 This is a bitmask with information of what bits in PB that a user
27111 can change direction on using ioctl's.
27112 Bit set = changeable.
27113 You probably want 00 here.
27115 PB changeable data bits
27116 CONFIG_ETRAX_PB_CHANGEABLE_BITS
27117 This is a bitmask with information of what bits in PB that a user
27118 can change the value on using ioctl's.
27119 Bit set = changeable.
27120 You probably want 00 here.
27122 Kernel debugger (kgdb)
27124 The CRIS version of gdb can be used to remotely debug a running
27125 Linux kernel via the serial debug port. Provided you have gdb-cris
27126 installed, run gdb-cris vmlinux, then type
27128 (gdb) set remotebaud 115200 <- kgdb uses 115200 as default
27129 (gdb) target remote /dev/ttyS0 <- maybe you use another port
27131 This should connect you to your booted kernel (or boot it now if you
27132 didn't before). The kernel halts when it boots, waiting for gdb if
27133 this option is turned on!
27135 Etrax bus waitstates
27136 CONFIG_ETRAX_DEF_R_WAITSTATES
27137 Waitstates for SRAM, Flash and peripherals (not DRAM). 95f8 is a
27138 good choice for most Axis products...
27140 Etrax bus configuration
27141 CONFIG_ETRAX_DEF_R_BUS_CONFIG
27142 Assorted bits controlling write mode, DMA burst length etc. 104 is
27143 a good choice for most Axis products...
27145 Etrax SDRAM configuration
27147 Enable this if you use SDRAM chips and configure
27148 R_SDRAM_CONFIG and R_SDRAM_TIMING as well.
27150 DRAM size (dec, in MB)
27151 CONFIG_ETRAX_DEF_R_DRAM_CONFIG
27152 The R_DRAM_CONFIG register specifies everything on how the DRAM
27153 chips in the system are connected to the Etrax CPU. This is
27154 different depending on the manufacturer, chip type and number of
27155 chips. So this value often needs to be different for each Axis
27159 CONFIG_ETRAX_DEF_R_DRAM_TIMING
27160 Different DRAM chips have different speeds. Current Axis products
27161 use 50ns DRAM chips which can use the timing: 5611.
27163 Etrax SDRAM configuration
27164 CONFIG_ETRAX_DEF_R_SDRAM_CONFIG
27165 The R_SDRAM_CONFIG register specifies everything on how the SDRAM
27166 chips in the system are connected to the Etrax CPU. This is
27167 different depending on the manufacturer, chip type and number of
27168 chips. So this value often needs to be different for each Axis
27172 CONFIG_ETRAX_DEF_R_SDRAM_TIMING
27173 Different SDRAM chips have different timing.
27175 Etrax General port A direction
27176 CONFIG_ETRAX_DEF_R_PORT_PA_DIR
27177 Configures the direction of general port A bits. 1 is out, 0 is in.
27178 This is often totally different depending on the product used.
27179 There are some guidelines though - if you know that only LED's are
27180 connected to port PA, then they are usually connected to bits 2-4
27181 and you can therefore use 1c. On other boards which don't have the
27182 LED's at the general ports, these bits are used for all kinds of
27183 stuff. If you don't know what to use, it is always safe to put all
27184 as inputs, although floating inputs isn't good.
27186 Etrax General port A data
27187 CONFIG_ETRAX_DEF_R_PORT_PA_DATA
27188 Configures the initial data for the general port A bits. Most
27189 products should use 00 here.
27191 Etrax General port B config
27192 CONFIG_ETRAX_DEF_R_PORT_PB_CONFIG
27193 Configures the type of the general port B bits. 1 is chip select,
27194 0 is port. Most products should use 00 here.
27196 Etrax General port B direction
27197 CONFIG_ETRAX_DEF_R_PORT_PB_DIR
27198 Configures the direction of general port B bits. 1 is out, 0 is in.
27199 This is often totally different depending on the product used. Bits
27200 0 and 1 on port PB are usually used for I2C communication, but the
27201 kernel I2C driver sets the appropriate directions itself so you
27202 don't need to take that into consideration when setting this option.
27203 If you don't know what to use, it is always safe to put all as
27206 Etrax General port B data
27207 CONFIG_ETRAX_DEF_R_PORT_PB_DATA
27208 Configures the initial data for the general port A bits. Most
27209 products should use FF here.
27211 Etrax General port device
27213 Enables the Etrax general port device (major 120, minors 0 and 1).
27214 You can use this driver to access the general port bits. It supports
27216 #include <linux/etraxgpio.h>
27217 fd = open("/dev/gpioa", O_RDWR); // or /dev/gpiob
27218 ioctl(fd, _IO(ETRAXGPIO_IOCTYPE, IO_SETBITS), bits_to_set);
27219 ioctl(fd, _IO(ETRAXGPIO_IOCTYPE, IO_CLRBITS), bits_to_clear);
27220 val = ioctl(fd, _IO(ETRAXGPIO_IOCTYPE, IO_READBITS), NULL);
27221 Remember that you need to setup the port directions appropriately in
27222 the General configuration.
27224 Etrax parallel data support
27225 CONFIG_ETRAX_PARDATA
27226 Adds support for writing data to the parallel port par0 of the ETRAX
27227 100. If you create a character special file with major number 126,
27228 you can write to the data bits of par0.
27229 Note: you need to disable Etrax100 parallel port support.
27231 Etrax parallel LCD (HD44780) Driver
27232 CONFIG_ETRAX_LCD_HD44780
27233 Adds support for a HD44780 controlled LCD connected to the parallel
27234 port par0 of the Etrax.
27236 Etrax Serial port ser0 support
27237 CONFIG_ETRAX_SERIAL
27238 Enables the ETRAX 100 serial driver for ser0 (ttyS0)
27239 You probably want this enabled.
27242 CONFIG_ETRAX_SERIAL_PROC_ENTRY
27243 Enables /proc/serial entry where errors and statistics can be
27244 viewed. CONFIG_PROC_FS must also be set for this to work.
27246 Etrax Serial port fast flush of DMA using fast timer API
27247 CONFIG_ETRAX_SERIAL_FAST_TIMER
27248 Select this to have the serial DMAs flushed at a higher rate than
27249 normally, possible by using the fast timer API, the timeout is
27250 approx. 4 character times.
27253 Etrax Serial port fast flush of DMA
27254 CONFIG_ETRAX_SERIAL_FLUSH_DMA_FAST
27255 Select this to have the serial DMAs flushed at a higher rate than
27256 normally possible through a fast timer interrupt (currently at
27260 Etrax Serial port receive flush timeout
27261 CONFIG_ETRAX_SERIAL_RX_TIMEOUT_TICKS
27262 Number of timer ticks between flush of receive fifo (1 tick = 10ms).
27263 Try 0-3 for low latency applications. Approx 5 for high load
27264 applications (e.g. PPP). Maybe this should be more adaptive some
27267 Etrax Serial port ser0 DTR, RI, DSR and CD support on PB
27268 CONFIG_ETRAX_SER0_DTR_RI_DSR_CD_ON_PB
27269 Enables the status and control signals DTR, RI, DSR and CD on PB for
27272 Serial port 1 enabled
27273 CONFIG_ETRAX_SERIAL_PORT1
27274 Enables the ETRAX 100 serial driver for ser1 (ttyS1).
27276 Etrax Serial port ser1 DTR, RI, DSR and CD support on PB
27277 CONFIG_ETRAX_SER1_DTR_RI_DSR_CD_ON_PB
27278 Enables the status and control signals DTR, RI, DSR and CD on PB for
27281 Serial port 2 enabled
27282 CONFIG_ETRAX_SERIAL_PORT2
27283 Enables the ETRAX 100 serial driver for ser2 (ttyS2).
27285 Etrax Serial port ser2 DTR, RI, DSR and CD support on PA
27286 CONFIG_ETRAX_SER2_DTR_RI_DSR_CD_ON_PA
27287 Enables the status and control signals DTR, RI, DSR and CD on PA for
27290 Serial port 3 enabled
27291 CONFIG_ETRAX_SERIAL_PORT3
27292 Enables the ETRAX 100 serial driver for ser3 (ttyS3).
27294 Etrax100 RS-485 support
27296 Enables support for RS-485 serial communication. For a primer on
27297 RS-485, see <http://www.hw.cz/english/docs/rs485/rs485.html>.
27299 Etrax100 RS-485 mode on PA
27300 CONFIG_ETRAX_RS485_ON_PA
27301 Control Driver Output Enable on RS485 transceiver using a pin on PA
27303 Axis 2400/2401 uses PA 3.
27305 Etrax100 RS-485 mode on PA bit
27306 CONFIG_ETRAX_RS485_ON_PA_BIT
27307 Control Driver Output Enable on RS485 transceiver using a this bit
27311 CONFIG_ETRAX_SER0_DTR_ON_PB_BIT
27312 Specify the pin of the PB port to carry the DTR signal for serial
27316 CONFIG_ETRAX_SER0_RI_ON_PB_BIT
27317 Specify the pin of the PB port to carry the RI signal for serial
27321 CONFIG_ETRAX_SER0_DSR_ON_PB_BIT
27322 Specify the pin of the PB port to carry the DSR signal for serial
27326 CONFIG_ETRAX_SER0_CD_ON_PB_BIT
27327 Specify the pin of the PB port to carry the CD signal for serial
27331 CONFIG_ETRAX_SER1_DTR_ON_PB_BIT
27332 Specify the pin of the PB port to carry the DTR signal for serial
27336 CONFIG_ETRAX_SER1_RI_ON_PB_BIT
27337 Specify the pin of the PB port to carry the RI signal for serial
27341 CONFIG_ETRAX_SER1_DSR_ON_PB_BIT
27342 Specify the pin of the PB port to carry the DSR signal for serial
27346 CONFIG_ETRAX_SER1_CD_ON_PB_BIT
27347 Specify the pin of the PB port to carry the CD signal for serial
27351 CONFIG_ETRAX_SER2_DTR_ON_PA_BIT
27352 Specify the pin of the PA port to carry the DTR signal for serial
27356 CONFIG_ETRAX_SER2_RI_ON_PA_BIT
27357 Specify the pin of the PA port to carry the RI signal for serial
27361 CONFIG_ETRAX_SER2_DSR_ON_PA_BIT
27362 Specify the pin of the PA port to carry the DTR signal for serial
27366 CONFIG_ETRAX_SER2_CD_ON_PA_BIT
27367 Specify the pin of the PA port to carry the CD signal for serial
27370 Etrax100 RS-485 disable receiver
27371 CONFIG_ETRAX_RS485_DISABLE_RECEIVER
27372 It's necessary to disable the serial receiver to avoid serial
27373 loopback. Not all products are able to do this in software only.
27374 Axis 2400/2401 must disable receiver.
27376 Etrax100 I2C Support
27378 Enables an I2C driver on PB0 and PB1 on ETRAX100.
27380 i2c_arg = I2C_WRITEARG(STA013_WRITE_ADDR, reg, val);
27381 ioctl(fd, _IO(ETRAXI2C_IOCTYPE, I2C_WRITEREG), i2c_arg);
27382 i2c_arg = I2C_READARG(STA013_READ_ADDR, reg);
27383 val = ioctl(fd, _IO(ETRAXI2C_IOCTYPE, I2C_READREG), i2c_arg);
27385 Etrax100 I2C configuration
27386 CONFIG_ETRAX_I2C_USES_PB_NOT_PB_I2C
27387 Select whether to use the special I2C mode in the PB I/O register or
27388 not. This option needs to be selected in order to use some drivers
27389 that access the I2C I/O pins directly instead of going through the
27390 I2C driver, like the DS1302 realtime-clock driver. If you are
27391 uncertain, choose Y here.
27393 Etrax100 I2C EEPROM (NVRAM) support
27394 CONFIG_ETRAX_I2C_EEPROM
27395 Enables I2C EEPROM (non-volatile RAM) on PB0 and PB1 using the I2C
27396 driver. Select size option: Probed, 2k, 8k, 16k.
27397 (Probing works for 2k and 8k but not that well for 16k)
27399 Etrax100 I2C EEPROM (NVRAM) size/16kB
27400 CONFIG_ETRAX_I2C_EEPROM_16KB
27403 Etrax100 I2C EEPROM (NVRAM) size/2kB
27404 CONFIG_ETRAX_I2C_EEPROM_2KB
27407 Etrax100 I2C EEPROM (NVRAM) size/8kB
27408 CONFIG_ETRAX_I2C_EEPROM_8KB
27411 # Choice: etrax_eeprom
27412 Etrax100 I2C EEPROM (NVRAM) size/probe
27413 CONFIG_ETRAX_I2C_EEPROM_PROBE
27414 Specifies size or auto probe of the EEPROM size.
27415 Options: Probed, 2k, 8k, 16k.
27416 (Probing works for 2k and 8k but not that well for 16k)
27418 Etrax DS1302 Real-Time Clock driver
27419 CONFIG_ETRAX_DS1302
27420 Enables the driver for the DS1302 Real-Time Clock battery-backed
27421 chip on some products. The kernel reads the time when booting, and
27422 the date can be set using ioctl(fd, RTC_SET_TIME, &rt) with rt a
27423 rtc_time struct (see <file:include/asm-cris/rtc.h>) on the /dev/rtc
27424 device, major 121. You can check the time with cat /proc/rtc, but
27425 normal time reading should be done using libc function time and
27428 Etrax DS1302 RST on the Generic Port
27429 CONFIG_ETRAX_DS1302_RST_ON_GENERIC_PORT
27430 If your product has the RST signal line for the DS1302 RTC on the
27431 Generic Port then say Y here, otherwise leave it as N in which
27432 case the RST signal line is assumed to be connected to Port PB
27433 (just like the SCL and SDA lines).
27435 Etrax DS1302 RST bit number
27436 CONFIG_ETRAX_DS1302_RSTBIT
27437 This is the bit number for the RST signal line of the DS1302 RTC on
27438 the selected port. If you have selected the generic port then it
27439 should be bit 27, otherwise your best bet is bit 5.
27441 Etrax DS1302 SCL bit number
27442 CONFIG_ETRAX_DS1302_SCLBIT
27443 This is the bit number for the SCL signal line of the DS1302 RTC on
27444 Port PB. This is probably best left at 3.
27446 Etrax DS1302 SDA bit number
27447 CONFIG_ETRAX_DS1302_SDABIT
27448 This is the bit number for the SDA signal line of the DS1302 RTC on
27449 Port PB. This is probably best left at 2.
27451 Etrax 100 IDE Reset
27452 CONFIG_ETRAX_IDE_CSP0_8_RESET
27453 Configures the pin used to reset the IDE bus.
27455 Etrax 100 IDE Reset
27456 CONFIG_ETRAX_IDE_CSPE1_16_RESET
27457 Configures the pin used to reset the IDE bus.
27459 Delay for drives to regain consciousness
27460 CONFIG_ETRAX_IDE_DELAY
27461 Sets the time to wait for disks to regain consciousness after reset.
27463 Etrax 100 IDE Reset
27464 CONFIG_ETRAX_IDE_G27_RESET
27465 Configures the pin used to reset the IDE bus.
27467 # Choice: ide_reset
27468 IDE reset on PB Bit 7
27469 CONFIG_ETRAX_IDE_PB7_RESET
27470 Configures the pin used to reset the IDE bus.
27473 CONFIG_ETRAX_USB_HOST
27474 This option enables the host functionality of the ETRAX 100LX
27475 built-in USB controller. In host mode the controller is designed
27476 for CTRL and BULK traffic only, INTR traffic may work as well
27477 however (depending on the requirements of timeliness).
27479 USB 1.1 host port 1 enabled
27480 CONFIG_ETRAX_USB_HOST_PORT1
27481 This option enables port 1 of the ETRAX 100LX USB root hub (RH).
27483 USB 1.1 host port 2 enabled
27484 CONFIG_ETRAX_USB_HOST_PORT2
27485 This option enables port 2 of the ETRAX 100LX USB root hub (RH).
27487 ETRAX 100LX 10/100Mbit Ethernet controller
27488 CONFIG_ETRAX_ETHERNET
27489 This option enables the ETRAX 100LX built-in 10/100Mbit Ethernet
27492 ETRAX 100LX Synchronous serial ports
27493 CONFIG_ETRAX_SYNCHRONOUS_SERIAL
27494 This option enables support for the ETRAX 100LX built-in
27495 synchronous serial ports. These ports are used for continuous
27496 streamed data like audio. The default setting is compatible
27497 with the STA 013 MP3 decoder, but can easily be tuned to fit
27498 any other audio encoder/decoder and SPI.
27500 ETRAX 100LX Synchronous serial port 0 enabled
27501 CONFIG_ETRAX_SYNCHRONOUS_SERIAL_PORT0
27502 Enables the ETRAX 100LX synchronous serial port 0 (syncser0).
27504 ETRAX 100LX Synchronous serial port 0 uses DMA
27505 CONFIG_ETRAX_SYNCHRONOUS_SERIAL0_DMA
27506 Makes synchronous serial port 0 use DMA.
27508 ETRAX 100LX Synchronous serial port 1 enabled
27509 CONFIG_ETRAX_SYNCHRONOUS_SERIAL_PORT1
27510 Enables the ETRAX 100LX synchronous serial port 1 (syncser1).
27512 ETRAX 100LX Synchronous serial port 1 uses DMA
27513 CONFIG_ETRAX_SYNCHRONOUS_SERIAL1_DMA
27514 Makes synchronous serial port 1 use DMA.
27516 Delay for drives to regain consciousness
27518 Number of seconds to wait for IDE drives to spin up after an IDE
27523 The ARTPEC-1 is a video-compression chip used in the AXIS 2100
27524 network camera, which is built around an ETRAX-100 board. With this
27525 option selected, the ETRAX kernel configures a DMA channel at boot
27526 time to talk to the chip.
27528 Axis flash-map support
27529 CONFIG_ETRAX_AXISFLASHMAP
27530 This option enables MTD mapping of flash devices. Needed to use
27531 flash memories. If unsure, say Y.
27533 Byte-offset of partition table sector
27534 CONFIG_ETRAX_PTABLE_SECTOR
27535 Byte-offset of the partition table in the first flash chip.
27536 The default value is 64kB and should not be changed unless
27537 you know exactly what you are doing. The only valid reason
27538 for changing this is when the flash block size is bigger
27539 than 64kB (e.g. when using two parallel 16 bit flashes).
27541 Enable Etrax100 watchdog
27542 CONFIG_ETRAX_WATCHDOG
27543 Enable the built-in watchdog timer support on Etrax100 embedded
27546 # Choice: crisdebug
27548 CONFIG_ETRAX_DEBUG_PORT0
27549 Choose a serial port for the ETRAX debug console. Default to
27552 Etrax debug port on ser1
27553 CONFIG_ETRAX_DEBUG_PORT1
27554 Use serial port 1 for the console.
27556 Etrax debug port on ser2
27557 CONFIG_ETRAX_DEBUG_PORT2
27558 Use serial port 2 for the console.
27560 Etrax debug port on ser3
27561 CONFIG_ETRAX_DEBUG_PORT3
27562 Use serial port 3 for the console.
27564 No Etrax debug port
27565 CONFIG_ETRAX_DEBUG_PORT_NULL
27566 Disable serial-port debugging.
27568 Parallel port support
27569 CONFIG_ETRAX_PARPORT
27570 Say Y here to enable the ETRAX on-board parallel ports.
27572 Parallel port 0 enabled
27573 CONFIG_ETRAX_PARALLEL_PORT0
27574 Say Y here to enable parallel port 0.
27576 Parallel port 1 enabled
27577 CONFIG_ETRAX_PARALLEL_PORT1
27578 Say Y here to enable parallel port 1.
27580 # Choice: crisrescue
27581 Select a product rescue port
27582 CONFIG_ETRAX_RESCUE_SER0
27583 Select one of the four serial ports as a rescue port. The default
27587 CONFIG_ETRAX_RESCUE_SER1
27588 Use serial port 1 as the rescue port.
27591 CONFIG_ETRAX_RESCUE_SER2
27592 Use serial port 2 as the rescue port.
27595 CONFIG_ETRAX_RESCUE_SER3
27596 Use serial port 3 as the rescue port.
27598 RIO Hardware Watchdog support
27599 CONFIG_WATCHDOG_RIO
27600 Say Y here to support the hardware watchdog capability on Sun RIO
27601 machines. The watchdog timeout period is normally one minute but
27602 can be changed with a boot-time parameter.
27604 CP1XXX Hardware Watchdog support
27605 CONFIG_WATCHDOG_CP1XXX
27606 This is the driver for the hardware watchdog timers present on
27607 Sun Microsystems CompactPCI models CP1400 and CP1500.
27609 This driver is also available as a module ( = code which can be
27610 inserted in and removed from the running kernel whenever you want).
27611 The module will be called cpwatchdog.o. If you want to compile it
27612 as a module, say M here and read <file:Documentation/modules.txt>.
27614 If you do not have a CompactPCI model CP1400 or CP1500, or
27615 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
27616 you should say N to this option.
27621 Select your IA-64 processor type. The default is Intel Itanium.
27622 This choice is safe for all IA-64 systems, but may not perform
27623 optimally on systems with, say, Itanium 2 or newer processors.
27627 Select this to configure for an Itanium 2 (McKinley) processor.
27629 # Choice: ia64system
27631 CONFIG_IA64_GENERIC
27632 This selects the system type of your hardware. A "generic" kernel
27633 will run on any supported IA-64 system. However, if you configure
27634 a kernel for your specific system, it will be faster and smaller.
27636 generic For any supported IA-64 system
27637 DIG-compliant For DIG ("Developer's Interface Guide") compliant systems
27639 SGI-SN2 For SGI SN2 systems
27640 Ski-simulator For the HP simulator (<http://www.hpl.hp.com/research/linux/ski/>)
27642 If you don't know what to do, choose "generic".
27645 Build a kernel that runs on HP zx1-based systems. This adds support
27646 for the zx1 IOMMU and makes root bus bridges appear in PCI config space
27647 (required for zx1 agpgart support).
27651 CONFIG_IA64_PAGE_SIZE_4KB
27652 This lets you select the page size of the kernel. For best IA-64
27653 performance, a page size of 8KB or 16KB is recommended. For best
27654 IA-32 compatibility, a page size of 4KB should be selected (the vast
27655 majority of IA-32 binaries work perfectly fine with a larger page
27656 size). For Itanium systems, do NOT chose a page size larger than
27659 4KB For best IA-32 compatibility
27660 8KB For best IA-64 performance
27661 16KB For best IA-64 performance
27662 64KB Not for Itanium.
27664 If you don't know what to do, choose 8KB.
27666 Enable Itanium B-step specific code
27667 CONFIG_ITANIUM_BSTEP_SPECIFIC
27668 Select this option to build a kernel for an Itanium prototype system
27669 with a B-step CPU. Only B3 step CPUs are supported. You have a B3-step
27670 CPU if the "revision" field in /proc/cpuinfo is equal to 4. If the
27671 "revision" field shows a number bigger than 4, you do not have to turn
27674 Enable IA-64 Machine Check Abort
27676 Say Y here to enable machine check support for IA-64. If you're
27679 Use PAL_HALT_LIGHT in idle loop
27680 CONFIG_IA64_PAL_IDLE
27681 Say Y here to enable use of PAL_HALT_LIGHT in the cpu_idle loop.
27682 This allows the CPU to enter a low power state when idle. You
27683 can enable CONFIG_IA64_PALINFO and check /proc/pal/cpu0/power_info
27684 to see the power consumption and latency for this state. If you're
27685 unsure your firmware supports it, answer N.
27687 Disable IA-64 Virtual Hash Page Table
27688 CONFIG_DISABLE_VHPT
27689 The Virtual Hash Page Table (VHPT) enhances virtual address
27690 translation performance. Normally you want the VHPT active but you
27691 can select this option to disable the VHPT for debugging. If you're
27694 Turn on compare-and-exchange bug checking (slow!)
27695 CONFIG_IA64_DEBUG_CMPXCHG
27696 Selecting this option turns on bug checking for the IA64
27697 compare-and-exchange instructions. This is slow! Itaniums
27698 from step B3 or later don't have this problem. If you're unsure,
27701 IA64 IRQ bug checking
27702 CONFIG_IA64_DEBUG_IRQ
27703 Selecting this option turns on bug checking for the IA64 irq_save
27704 and restore instructions. It's useful for tracking down spinlock
27705 problems, but slow! If you're unsure, select N.
27707 Early printk support
27708 CONFIG_IA64_EARLY_PRINTK
27709 Selecting this option uses a UART or VGA screen (or both) for
27710 printk() output before the consoles are initialised. It is useful
27711 for debugging problems early in the boot process, but only if you
27712 have a serial terminal or a VGA screen attached. If you're unsure,
27715 Early printk on serial port
27716 CONFIG_IA64_EARLY_PRINTK_UART
27717 Select this option to use a serial port for early printk() output.
27718 You must also select either CONFIG_IA64_EARLY_PRINTK_UART_BASE or
27719 CONFIG_SERIAL_HCDP. If you select CONFIG_SERIAL_HCDP, early
27720 printk() output will appear on the first console device described by
27721 the HCDP. If you set CONFIG_IA64_EARLY_PRINTK_UART_BASE, the HCDP
27725 CONFIG_IA64_EARLY_PRINTK_UART_BASE
27726 The physical MMIO address of the UART to use for early printk().
27727 This overrides any UART located using the EFI HCDP table.
27729 Early printk on VGA
27730 CONFIG_IA64_EARLY_PRINTK_VGA
27731 Select this option to use VGA for early printk() output.
27733 Print possible IA64 hazards to console
27734 CONFIG_IA64_PRINT_HAZARDS
27735 Selecting this option prints more information for Illegal Dependency
27736 Faults, that is, for Read after Write, Write after Write or Write
27737 after Read violations. If you're unsure, select Y.
27739 Performance monitor support
27741 Selects whether support for the IA-64 performance monitor hardware
27742 is included in the kernel. This makes some kernel data-structures a
27743 little bigger and slows down execution a bit, but it is still
27744 usually a good idea to turn this on. If you're unsure, say N.
27747 CONFIG_IA64_PALINFO
27748 If you say Y here, you are able to get PAL (Processor Abstraction
27749 Layer) information in /proc/pal. This contains useful information
27750 about the processors in your systems, such as cache and TLB sizes
27751 and the PAL firmware version in use.
27753 To use this option, you have to check that the "/proc file system
27754 support" (CONFIG_PROC_FS) is enabled, too.
27756 PPC4xx DMA controller support
27758 Select this to enable support for the PPC4xx general purpose DMA
27763 This option reverses the mapping between the hardware UART and software
27764 device. Selecting UART0 gives the normal mapping of UART0=ttyS0 and
27765 UART1=ttyS1. Selecting UART1 gives the reverse mapping of UART0=ttyS1
27766 and UART1=ttyS0. Most people will use UART0.
27768 PowerPC 405 on-chip ethernet
27769 CONFIG_IBM_OCP_ENET
27770 If you want to use the 405 built-in ethernet select this.
27772 CONFIG_IBM_OCP_ENET_ERROR_MSG
27773 Enable this option to print verbose debug messages for troubleshooting.
27775 PowerPC 405 on-chip ethernet -- Number of receive buffers
27776 CONFIG_IBM_OCP_ENET_RX_BUFF
27777 Number of ethernet receive (read) buffers. Unless you know what you
27778 are doing the default should be fine.
27780 PowerPC 405 on-chip ethernet -- Number of transmit buffers
27781 CONFIG_IBM_OCP_ENET_TX_BUFF
27782 Number of ethernet transmit (write) buffers. Unless you know what
27783 you are doing the default should be fine.
27785 PowerPC 405 on-chip ethernet -- Amount of bytes to Reserve on a skb
27786 CONFIG_IBM_OCP_ENET_SKB_RES
27787 Many standard ethernet drivers need to reserve 2 bytes of data
27788 on the skb before giving the data ptr to the hardware. This is
27789 so the IP data will be 16-byte aligned when it goes up the stack.
27790 This is a requirement for some processors and it can cause major
27791 slow downs on others. The 405GP dose not have problems with the
27792 misaligned data so the default is 0. If you need to route the
27793 incoming ethernet packets to another device that has alignment
27794 requirements this can help remove a data copy. A value of 2 can
27795 help at getting 16-byte aligned IP data for another device. A
27796 larger value can be used when routing to a IP tunnel device.
27797 Make sure XXX_DESC_SIZE - XXX_SKB_RES >= 1514, or larger if VLANS
27800 PPC 405 I2C Algorithm
27801 CONFIG_PPC405_I2C_ALGO
27802 Enable this option to use the built-in I2C on your 405.
27804 PPC 405 I2C Adapter
27805 CONFIG_PPC405_I2C_ADAP
27806 Enable this option to use the built-in I2C on your 405.
27808 /proc/efi/vars support
27810 If you say Y here, you are able to get EFI (Extensible Firmware
27811 Interface) variable information in /proc/efi/vars. You may read,
27812 write, create, and destroy EFI variables through this interface.
27814 To use this option, you have to check that the "/proc file system
27815 support" (CONFIG_PROC_FS) is enabled, too.
27817 Kernel support for IA-32 emulation
27818 CONFIG_IA32_SUPPORT
27819 IA64 processors can run IA32 (that is, x86) binaries by emulating
27820 the IA32 instruction set. Say Y here to build in kernel support for
27821 this. If in doubt, say Y.
27823 Physical memory granularity (16 MB)
27824 CONFIG_IA64_GRANULE_16MB
27825 IA64 identity-mapped regions use a large page size. We'll call such
27826 large pages "granules". If you can think of a better name that's
27827 unambiguous, let us know... Unless your identity-mapped regions are
27828 very large, select a granule size of 16MB.
27830 Physical memory granularity (64 MB)
27831 CONFIG_IA64_GRANULE_64MB
27832 IA64 identity-mapped regions use a large page size. We'll call such
27833 large pages "granules". If you can think of a better name that's
27834 unambiguous, let us know... Unless your identity-mapped regions are
27835 very large, select a granule size of 16MB. (This is the "large" choice.)
27837 Enable SGI SN extra debugging code
27838 CONFIG_IA64_SGI_SN_DEBUG
27839 Turns on extra debugging code in the SGI SN (Scalable NUMA) platform
27840 for IA64. Unless you are debugging problems on an SGI SN IA64 box,
27843 Enable SGI Medusa Simulator Support
27844 CONFIG_IA64_SGI_SN_SIM
27845 If you are compiling a kernel that will run under SGI's IA64
27846 simulator (Medusa) then say Y, otherwise say N.
27850 IRIX PCIBA-inspired user mode PCI interface for the SGI SN (Scalable
27851 NUMA) platform for IA64. Unless you are compiling a kernel for an SGI SN IA64 box, say N.
27853 Enable protocol mode for the L1 console
27854 SERIAL_SGI_L1_PROTOCOL
27855 Uses protocol mode instead of raw mode for the level 1 console on the
27856 SGI SN (Scalable NUMA) platform for IA64. If you are compiling for
27857 an SGI SN box then Y is the recommended value, otherwise say N.
27859 Directly Connected Compact Flash support
27861 Compact Flash is a small, removable mass storage device introduced
27862 in 1994 originally as a PCMCIA device. If you say `Y' here, you
27863 compile in support for Compact Flash devices directly connected to
27864 a SuperH processor. A Compact Flash FAQ is available at
27865 <http://www.compactflash.org/faqs/faq.htm>.
27867 If your board has "Directly Connected" CompactFlash at area 5 or 6,
27868 you may want to enable this option. Then, you can use CF as
27869 primary IDE drive (only tested for SanDisk).
27871 If in doubt, select 'N'.
27874 CONFIG_DEBUG_KERNEL
27875 Say Y here if you are developing drivers or trying to debug and
27876 identify kernel problems.
27878 Debug memory allocations
27880 Say Y here to have the kernel do limited verification on memory
27881 allocation as well as poisoning memory on free to catch use of freed
27884 Memory mapped I/O debugging
27885 CONFIG_DEBUG_IOVIRT
27886 Say Y here to get warned whenever an attempt is made to do I/O on
27887 obviously invalid addresses such as those generated when ioremap()
27888 calls are forgotten. Memory mapped I/O will go through an extra
27889 check to catch access to unmapped ISA addresses, an access method
27890 that can still be used by old drivers that are being ported from
27894 CONFIG_DEBUG_SPINLOCK
27895 Say Y here and build SMP to catch missing spinlock initialization
27896 and certain other kinds of spinlock errors commonly made. This is
27897 best used in conjunction with the NMI watchdog so that spinlock
27898 deadlocks are also debuggable.
27900 Additional run-time checks
27902 Enables some internal consistency checks for kernel debugging.
27903 You should normally say N.
27905 Read-write spinlock debugging
27906 CONFIG_DEBUG_RWLOCK
27907 If you say Y here then read-write lock processing will count how many
27908 times it has tried to get the lock and issue an error message after
27909 too many attempts. If you suspect a rwlock problem or a kernel
27910 hacker asks for this option then say Y. Otherwise say N.
27912 Semaphore debugging
27913 CONFIG_DEBUG_SEMAPHORE
27914 If you say Y here then semaphore processing will issue lots of
27915 verbose debugging messages. If you suspect a semaphore problem or a
27916 kernel hacker asks for this option then say Y. Otherwise say N.
27918 Verbose BUG() reporting (adds 70K)
27919 CONFIG_DEBUG_BUGVERBOSE
27920 Say Y here to make BUG() panics output the file name and line number
27921 of the BUG call as well as the EIP and oops trace. This aids
27922 debugging but costs about 70-100K of memory.
27924 Include kgdb kernel debugger
27926 Include in-kernel hooks for kgdb, the Linux kernel source level
27927 debugger. For i386 architecture there is project page at
27928 <http://kgdb.sourceforge.net/>.
27930 Include xmon kernel debugger
27932 Include in-kernel hooks for the xmon kernel monitor/debugger
27933 supported by the PPC port.
27935 Include BDI2000 debugger support
27937 Include in-kernel support for the Abatron BDI2000 debugger. To
27938 learn more about the Abatron BDI2000, visit the web page at
27939 <http://www.abatron.ch/>.
27941 Add additional CFLAGS to the kernel build
27942 CONFIG_MORE_COMPILE_OPTIONS
27943 If you want to add additional CFLAGS to the kernel build, such as
27944 -g for KGDB, XMON or the BDI2000, enable this option and then
27945 enter what you would like to add in the next question.
27947 Include kgdb kernel debugger
27949 Include in-kernel hooks for kdb, the source level debugger for the
27953 CONFIG_IODC_CONSOLE
27954 IODC is HP's pre-PCI standard for device identification (a la PCI
27955 vendor, device IDs), detection, configuration, initialization and so
27956 on. It also can provide firmware function to do the actual IO,
27957 which are slow, not really defined for runtime usage and generally
27960 See <http://www.linuxhq.com/kernel/v2.4/doc/parisc/IODC.txt.html>
27961 for the gory details.
27963 Say Y here to enable use of the IODC firmware functions for console
27964 I/O. This is only useful on older PA-RISC workstations. If in
27969 Say Y here to enable DMA management routines for the first
27970 generation of PA-RISC cache-coherent machines. Programs the
27971 U2/Uturn chip in "Virtual Mode" and use the I/O MMU.
27973 LBA/Elroy PCI support
27975 Say Y here to give the PA-RISC kernel access to PCI configuration
27976 and IO-port space on PA-RISC workstations equipped with a Lower Bus
27977 Adapter (LBA). This includes A, B, C, J, L, and N-class machines
27978 with 4-digit model numbers, also the A300.
27982 Say Y here to directly support the LASI controller chip found on
27983 PA-RISC workstations. Linux-oriented documentation for this chip
27984 can be found at <http://www.parisc-linux.org/documentation/>.
27986 LASI/ASP builtin parallel-port
27988 Say Y here to build in low-level parallel-support for PC-style
27989 hardware integrated in the LASI-Controller (on the GSC Bus) for
27990 HP-PARISC workstations.
27992 Fujitsu Vendor Specific
27993 CONFIG_BLK_DEV_IDEDISK_FUJITSU
27994 Enable vendor-specific code for Fujitsu IDE disks. Unless you are
27995 the IDE maintainer, you probably do not want to mess with this.
27997 IBM Vendor Specific
27998 CONFIG_BLK_DEV_IDEDISK_IBM
27999 Enable vendor-specific code for IBM IDE disks. Unless you are the
28000 IDE maintainer, you probably do not want to mess with this.
28002 Maxtor Vendor Specific
28003 CONFIG_BLK_DEV_IDEDISK_MAXTOR
28004 Enable vendor-specific code for Maxtor IDE disks. Unless you are
28005 the IDE maintainer, you probably do not want to mess with this.
28007 Quantum Vendor Specific
28008 CONFIG_BLK_DEV_IDEDISK_QUANTUM
28009 Enable vendor-specific code for Quantum IDE disks. Unless you are
28010 the IDE maintainer, you probably do not want to mess with this.
28012 Seagate Vendor Specific
28013 CONFIG_BLK_DEV_IDEDISK_SEAGATE
28014 Enable vendor-specific code for Seagate IDE disks. Unless you are
28015 the IDE maintainer, you probably do not want to mess with this.
28017 Western Digital Vendor Specific
28018 CONFIG_BLK_DEV_IDEDISK_WD
28019 Enable vendor-specific code for Western Digital IDE disks. Unless
28020 you are the IDE maintainer, you probably do not want to mess with
28023 TiVo Commerial Application Specific
28024 CONFIG_BLK_DEV_TIVO
28025 Enable vendor-specific code for TiVo IDE disks. Unless you are the
28026 IDE maintainer, you probably do not want to mess with this.
28028 # Choice: superhsys
28031 Select Generic if configuring for a generic SuperH system.
28032 The "generic" option compiles in *all* the possible hardware
28033 support and relies on the sh_mv= kernel command option to choose
28034 at runtime which routines to use. "MV" stands for "machine vector";
28035 each of the machines below is described by a machine vector.
28037 Select SolutionEngine if configuring for a Hitachi SH7709
28038 or SH7750/7750S evaluation board.
28040 Select SHMobileSolutionEngine if configuring for SH-Mobile Solution
28043 Select Overdrive if configuring for a ST407750 Overdrive board.
28044 More information at
28045 <http://linuxsh.sourceforge.net/docs/7750overdrive.php3>.
28047 Select HP620 if configuring for a HP Jornada HP620.
28048 More information (hardware only) at
28049 <http://www.hp.com/jornada/>.
28051 Select HP680 if configuring for a HP Jornada HP680.
28052 More information (hardware only) at
28053 <http://www.hp.com/jornada/products/680/>.
28055 Select HP690 if configuring for a HP Jornada HP690.
28056 More information (hardware only) at
28057 <http://www.hp.com/jornada/products/680/>.
28059 Select CqREEK if configuring for a CqREEK SH7708 or SH7750.
28060 More information at
28061 <http://sources.redhat.com/ecos/hardware.html#SuperH>.
28063 Select DMIDA if configuring for a DataMyte 4000 Industrial
28064 Digital Assistant. More information at <http://www.dmida.com/>.
28066 Select EC3104 if configuring for a system with an Eclipse
28067 International EC3104 chip, e.g. the Harris AD2000 or Compaq Aero 8000.
28069 Select Dreamcast if configuring for a SEGA Dreamcast.
28070 More information at
28071 <http://www.m17n.org/linux-sh/dreamcast/>. There is a
28072 Dreamcast project is at <http://linuxdc.sourceforge.net/>.
28074 Select BareCPU if you know what this means, and it applies
28077 # These may have to be merged in when we go to CML2:
28078 # - "SolutionEngine7751" for Hitachi SolutionEngine (7751)
28079 # - "STB1_Harp" for STMicroelectronics HARP
28080 # - "CqREEK" for CQ Publishing CqREEK SH-4
28081 # - "CAT68701" for CAT 68701 Evaluation Board (SH7708)
28082 # - "BigSur" for Big Sur Evaluation Board
28083 # - "SH2000" for SH2000 Evaluation Board (SH7709A)
28084 # - "ADX" for A&D ADX
28087 CONFIG_SH_SOLUTION_ENGINE
28088 Select SolutionEngine if configuring for a Hitachi SH7709
28089 or SH7750 evaluation board.
28091 7751 SolutionEngine
28092 CONFIG_SH_7751_SOLUTION_ENGINE
28093 Select 7751 SolutionEngine if configuring for a Hitachi SH7751
28096 SHMobileSolutionEngine
28097 CONFIG_SH_MOBILE_SOLUTION_ENGINE
28098 Select SHMobileSolutionEngine if configuring for SH-Mobile Solution
28102 CONFIG_SH_OVERDRIVE
28103 Select Overdrive if configuring for a ST407750 Overdrive board.
28104 More information at
28105 <http://linuxsh.sourceforge.net/docs/7750overdrive.php3>.
28109 Select HP620 if configuring for a HP jornada HP620.
28110 More information (hardware only) at
28111 <http://www.hp.com/jornada/>.
28115 Select HP680 if configuring for a HP Jornada HP680.
28116 More information (hardware only) at
28117 <http://www.hp.com/jornada/products/680/>.
28121 Select HP690 if configuring for a HP Jornada HP690.
28122 More information (hardware only)
28123 at <http://www.hp.com/jornada/products/680/>.
28127 Select CqREEK if configuring for a CqREEK SH7708 or SH7750.
28128 More information at
28129 <http://sources.redhat.com/ecos/hardware.html#SuperH>.
28133 Select DMIDA if configuring for a DataMyte 4000 Industrial
28134 Digital Assistant. More information at <http://www.dmida.com/>.
28138 Select EC3104 if configuring for a system with an Eclipse
28139 International EC3104 chip, e.g. the Harris AD2000.
28142 CONFIG_SH_DREAMCAST
28143 Select Dreamcast if configuring for a SEGA Dreamcast.
28144 More information at
28145 <http://www.m17n.org/linux-sh/dreamcast/>. There is a
28146 Dreamcast project is at <http://linuxdc.sourceforge.net/>.
28150 SH-2000 is a single-board computer based around SH7709A chip
28151 intended for embedded applications.
28152 It has an Ethernet interface (CS8900A), direct connected
28153 Compact Flash socket, three serial ports and PC-104 bus.
28154 More information at <http://sh2000.sh-linux.org>.
28158 "Bare CPU" aka "unknown" means an SH-based system which is not one
28159 of the specific ones mentioned above, which means you need to enter
28160 all sorts of stuff like CONFIG_MEMORY_START because the config
28161 system doesn't already know what it is. You get a machine vector
28162 without any platform-specific code in it, so things like the RTC may
28165 This option is for the early stages of porting to a new machine.
28167 # Choice: superhtype
28169 CONFIG_CPU_SUBTYPE_SH7707
28170 Select the type of SuperH processor you have. This information is
28171 used for optimizing and configuration purposes.
28173 Select SH7707 if you have a 60 Mhz SH-3 HD6417707 CPU.
28175 Select SH7708 if you have a 60 Mhz SH-3 HD6417708S or
28176 if you have a 100 Mhz SH-3 HD6417708R CPU.
28178 Select SH7709 if you have a 80 Mhz SH-3 HD6417709 CPU.
28180 Select SH7750 if you have a 200 Mhz SH-4 HD6417750 CPU.
28182 Select SH7751 if you have a SH7751
28184 Select ST40STB1 if you have a ST40STB1
28185 Select ST40RA/ST40STB1 if you have a ST40RA
28186 (previously known as ST40STB1).
28188 Select ST40GX1 if you have an ST40GX1.
28190 Select SH7300 if you have a HD6417300 CPU.
28193 CONFIG_CPU_SUBTYPE_SH7708
28194 Select SH7708 if you have a 60 Mhz SH-3 HD6417708S or
28195 if you have a 100 Mhz SH-3 HD6417708R CPU.
28198 CONFIG_CPU_SUBTYPE_SH7709
28199 Select SH7709 if you have a 80 Mhz SH-3 HD6417709 CPU.
28202 CONFIG_CPU_SUBTYPE_SH7750
28203 Select SH7750 if you have a 200 Mhz SH-4 HD6417750 CPU.
28206 CONFIG_CPU_SUBTYPE_SH7751
28207 Select SH7751 if you have a 166 Mhz SH-4 HD6417751 CPU.
28210 CONFIG_CPU_SUBTYPE_ST40STB1
28211 Select ST40RA/ST40STB1 if you have a ST40RA. This chip was
28212 previously called the ST40STB1. Early versions were also
28213 erronously labelled ST40AR166.
28216 CONFIG_CPU_SUBTYPE_ST40GX1
28217 Select ST40GX1 if you have a ST40GX1 CPU.
28220 CONFIG_CPU_SUBTYPE_SH7300
28221 Select SH7300 if you have a HD6417300 CPU.
28224 CONFIG_ST40_LMI_MEMORY
28225 Currently all ST40 CPUs have two external buses the
28226 'Local Memory Interface' (LMI) which supports SDRAM and
28227 DDR SDRAM, and the 'Enhanced flash Memory Interface' (EMI),
28228 which supports SDRAM, Flash, peripherials and MPX. Linux
28229 can support memory on either of these buses, it is simply
28230 necessary to specify its base address. This option is simply
28231 a shortcut method of specifying that RAM starts from the
28234 Physical memory start address
28235 CONFIG_MEMORY_START
28236 Computers built with Hitachi SuperH processors always
28237 map the ROM starting at address zero. But the processor
28238 does not specify the range that RAM takes.
28240 The physical memory (RAM) start address will be automatically
28241 set to 08000000, unless you selected one of the following
28242 processor types: SolutionEngine, Overdrive, HP620, HP680, HP690,
28243 in which case the start address will be set to 0c000000.
28245 Tweak this only when porting to a new machine which is not already
28246 known by the config system. Changing it from the known correct
28247 value on any of the known systems will only lead to disaster.
28249 Hitachi HD64461 companion chip support
28251 The Hitachi HD64461 provides an interface for
28252 the SH7709 CPU, supporting a LCD controller,
28253 CRT color controller, IrDA up to 4 Mbps, and a
28254 PCMCIA controller supporting 2 slots.
28256 More information is available at
28257 <http://semiconductor.hitachi.com/windowsce/superh/sld013.htm>.
28259 Say Y if you want support for the HD64461.
28262 HD64461 PCMCIA enabler
28263 CONFIG_HD64461_ENABLER
28264 Say Y here if you want to enable PCMCIA support
28265 via the HD64461 companion chip.
28268 HD64461 virtualized IRQ number
28270 The default setting of the HD64461 IRQ is 36.
28272 Do not change this unless you know what you are doing.
28274 Hitachi HD64465 companion chip support
28276 The Hitachi HD64465 provides an interface for
28277 the SH7750 CPU, supporting a LCD controller,
28278 CRT color controller, IrDA, USB, PCMCIA,
28279 keyboard controller, and a printer interface.
28281 More information is available at
28282 <http://global.hitachi.com/New/cnews/E/1998/981019B.html>.
28284 Say Y if you want support for the HD64465.
28287 HD64465 virtualized IRQ number
28289 The default setting of the HD64465 IRQ is 5.
28291 Do not change this unless you know what you are doing.
28293 HD64465 start address
28294 CONFIG_HD64465_IOBASE
28295 The default setting of the HD64465 IO base address is 0xb0000000.
28297 Do not change this unless you know what you are doing.
28299 Early printk support
28300 CONFIG_SH_EARLY_PRINTK
28301 Say Y here to redirect kernel printk messages to the serial port
28302 used by the SH-IPL bootloader, starting very early in the boot
28303 process and ending when the kernel's serial console is initialised.
28304 This option is only useful porting the kernel to a new machine,
28305 when the kernel may crash or hang before the serial console is
28306 initialised. If unsure, say N.
28308 SuperH SCI (serial) support
28310 Selecting this option will allow the Linux kernel to transfer data
28311 over SCI (Serial Communication Interface) and/or SCIF (Serial
28312 Communication Interface with FIFO) which are built into the Hitachi
28313 SuperH processor. The option provides 1 to 3 (depending
28314 on the CPU model) standard Linux tty devices, /dev/ttySC[012]; one
28315 of these is normally used as the system console.
28317 If in doubt, press "y".
28319 Use LinuxSH standard BIOS
28320 CONFIG_SH_STANDARD_BIOS
28321 Say Y here if your target has the gdb-sh-stub
28322 package from www.m17n.org (or any conforming standard LinuxSH BIOS)
28323 in FLASH or EPROM. The kernel will use standard BIOS calls during
28324 boot for various housekeeping tasks (including calls to read and
28325 write characters to a system console, get a MAC address from an
28326 on-board Ethernet interface, and shut down the hardware). Note this
28327 does not work with machines with an existing operating system in
28328 mask ROM and no flash (WindowsCE machines fall in this category).
28331 GDB Stub kernel debug
28332 CONFIG_DEBUG_KERNEL_WITH_GDB_STUB
28333 If you say Y here, it will be possible to remotely debug the SuperH
28334 kernel using gdb, if you have the gdb-sh-stub package from
28335 www.m17n.org (or any conforming standard LinuxSH BIOS) in FLASH or
28336 EPROM. This enlarges your kernel image disk size by several
28337 megabytes but allows you to load, run and debug the kernel image
28338 remotely using gdb. This is only useful for kernel hackers. If
28341 Console output to GDB
28343 If you are using GDB for remote debugging over a serial port and
28344 would like kernel messages to be formatted into GDB $O packets so
28345 that GDB prints them as program output, say 'Y'.
28347 802.1Q VLAN Support
28349 Select this and you will be able to create 802.1Q VLAN interfaces on your
28350 ethernet interfaces. 802.1Q VLAN supports almost everything a regular
28351 ethernet interface does, including firewalling, bridging, and of course
28352 IP traffic. You will need the 'vconfig' tool from the VLAN project in
28353 order to effectively use VLANs. See the VLAN web page for more
28354 information: <http://www.candelatech.com/~greear/vlan.html> If unsure,
28355 you can safely say 'N'.
28357 ARC console support
28359 Support for the PROM-based console on MIPS machines built according
28360 to the Advanced Risc Computing specification, which is now (2001)
28361 dead. These included boxes from Deskstation, Acer, Olivetti and
28362 NEC. There is a history at <http://www.openbsd.org/arc.html>.
28365 CONFIG_ARCH_AUTCPU12
28366 Say Y if you intend to run the kernel on the autronix autcpu12
28367 board. This board is based on a Cirrus Logic CS89712.
28370 CONFIG_BLK_DEV_IT8172
28371 Say Y here to support the on-board IDE controller on the Integrated
28372 Technology Express, Inc. ITE8172 SBC. Vendor page at
28373 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
28374 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
28376 Support ARM926T processor
28378 This is a variant of the ARM920. It has slightly different
28379 instruction sequences for cache and TLB operations. Curiously,
28380 there is no documentation on it at the ARM corporate website.
28382 Say Y if you want support for the ARM926T processor.
28385 Support CPU clock change (EXPERIMENTAL)
28387 CPU clock scaling allows you to change the clock speed of the
28388 running CPU on the fly. This is a nice method to save battery power,
28389 because the lower the clock speed, the less power the CPU
28390 consumes. Note that this driver doesn't automatically change the CPU
28391 clock speed, you need some userland tools (which still have to be
28392 written) to implement the policy. If you don't understand what this
28393 is all about, it's safe to say 'N'.
28397 Choose this option if you have a SIS graphics card. AGP support is
28398 required for this driver to work.
28400 Etrax Ethernet slave support (over lp0/1)
28401 CONFIG_ETRAX_ETHERNET_LPSLAVE
28402 This option enables a slave ETRAX 100 or ETRAX 100LX, connected to a
28403 master ETRAX 100 or ETRAX 100LX through par0 and par1, to act as an
28404 Ethernet controller.
28406 Slave has its own LEDs
28407 CONFIG_ETRAX_ETHERNET_LPSLAVE_HAS_LEDS
28408 Enable if the slave has it's own LEDs.
28412 Enable this to get support for ATA/IDE. You can't use parallel
28413 ports or SCSI ports at the same time.
28416 CONFIG_ETRAX_NETWORK_LED_ON_WHEN_LINK
28418 Selecting LED_on_when_link will light the LED when there is a
28419 connection and will flash off when there is activity.
28421 Selecting LED_on_when_activity will light the LED only when
28424 This setting will also affect the behaviour of other activity LEDs
28427 Power button bit on port G
28428 CONFIG_ETRAX_POWERBUTTON_BIT
28429 Configure where power button is connected.
28432 CONFIG_ETRAX_ROOT_DEVICE
28433 Specifies the device that should be mounted as root file system
28434 when booting from flash. The axisflashmap driver adds an additional
28435 mtd partition for the appended root file system image, so this option
28436 should normally be the mtdblock device for the partition after the
28437 last partition in the partition table.
28439 Serial port 0 enabled
28440 CONFIG_ETRAX_SERIAL_PORT0
28441 Enables the ETRAX 100 serial driver for ser0 (ttyS0)
28442 Normally you want this on, unless you use external DMA 1 that uses
28443 the same DMA channels.
28445 Shutdown bit on port CSP0
28446 CONFIG_ETRAX_SHUTDOWN_BIT
28447 Configure what pin on CSPO-port that is used for controlling power
28450 Software Shutdown Support
28451 CONFIG_ETRAX_SOFT_SHUTDOWN
28452 Enable this if Etrax is used with a power-supply that can be turned
28453 off and on with PS_ON signal. Gives the possibility to detect
28454 powerbutton and then do a power off after unmounting disks.
28456 Disable watchdog during Oops printouts
28457 CONFIG_ETRAX_WATCHDOG_NICE_DOGGY
28458 By enabling this you make sure that the watchdog does not bite while
28459 printing oopses. Recommended for development systems but not for
28460 production releases.
28462 Compaq iPAQ Handheld sleeve support
28463 CONFIG_H3600_SLEEVE
28464 Choose this option to enable support for extension packs (sleeves)
28465 for the Compaq iPAQ H3XXX series of handheld computers. This option
28466 is required for the CF, PCMCIA, Bluetooth and GSM/GPRS extension
28469 AVM Fritz!Card PCI/PCIv2/PnP support (EXPERIMENTAL)
28470 CONFIG_HISAX_FRITZ_PCIPNP
28471 This enables the driver for the AVM Fritz!Card PCI, Fritz!Card PCI v2
28472 and Fritz!Card PnP.
28473 (the latter also needs you to select "ISA Plug and Play support"
28474 from the menu "Plug and Play configuration")
28476 IBM PCI Hotplug driver
28477 CONFIG_HOTPLUG_PCI_IBM
28478 Say Y here if you have a motherboard with a IBM PCI Hotplug
28481 This code is also available as a module ( = code which can be
28482 inserted in and removed from the running kernel whenever you want).
28483 The module will be called cpqphp.o. If you want to compile it
28484 as a module, say M here and read Documentation/modules.txt.
28486 When in doubt, say N.
28488 Enable autotest (llsc). Option to run cache test instead of booting
28489 CONFIG_IA64_SGI_AUTOTEST
28490 Build a kernel used for hardware validation. If you include the
28491 keyword "autotest" on the boot command line, the kernel does NOT boot.
28492 Instead, it starts all cpus and runs cache coherency tests instead.
28496 IEC61883-6 (Audio transmission) support
28497 CONFIG_IEEE1394_AMDTP
28498 This option enables the Audio & Music Data Transmission Protocol
28499 (IEC61883-6) driver, which implements audio transmission over
28502 The userspace interface is documented in amdtp.h.
28504 If you want to compile this as a module ( = code which can be
28505 inserted in and removed from the running kernel whenever you want),
28506 say M here and read Documentation/modules.txt. The module
28507 will be called amdtp.o.
28509 IEC61883-1 Plug support
28510 CONFIG_IEEE1394_CMP
28511 This option enables the Connection Management Procedures
28512 (IEC61883-1) driver, which implements input and output plugs.
28514 If you want to compile this as a module ( = code which can be
28515 inserted in and removed from the running kernel whenever you want),
28516 say M here and read Documentation/modules.txt. The module
28517 will be called cmp.o.
28519 OHCI-DV I/O support
28520 CONFIG_IEEE1394_DV1394
28521 This driver allows you to transmit and receive DV (digital video)
28522 streams on an OHCI-1394 card using a simple frame-oriented
28525 The user-space API for dv1394 is documented in dv1394.h.
28527 If you want to compile this as a module ( = code which can be
28528 inserted in and removed from the running kernel whenever you want),
28529 say M here and read Documentation/modules.txt. The module
28530 will be called dv1394.o.
28533 CONFIG_IEEE1394_ETH1394
28534 Extremely Experimental! This driver is a Linux specific way to use your
28535 IEEE1394 Host as an Ethernet type device. This is _NOT_ IP1394.
28537 Support for older IT8172 (Rev C)
28539 Say Y here to support the older, Revision C version of the Integrated
28540 Technology Express, Inc. ITE8172 SBC. Vendor page at
28541 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
28542 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
28544 Enable Smart Card Reader 0 Support
28546 Say Y here to support smart-card reader 0 (SCR0) on the Integrated
28547 Technology Express, Inc. ITE8172 SBC. Vendor page at
28548 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
28549 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
28551 Enable Smart Card Reader 1 Support
28553 Say Y here to support smart-card reader 1 (SCR1) on the Integrated
28554 Technology Express, Inc. ITE8172 SBC. Vendor page at
28555 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
28556 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
28558 IT8172 IDE Tuning support
28559 CONFIG_IT8172_TUNING
28560 Say Y here to support tuning the ITE8172's IDE interface. This makes
28561 it possible to set DMA channel or PIO opration and the transfer rate.
28563 Enable protocol mode for the L1 console
28564 CONFIG_SERIAL_SGI_L1_PROTOCOL
28565 Uses protocol mode instead of raw mode for the level 1 console on the
28566 SGI SN (Scalable NUMA) platform for IA64. If you are compiling for
28567 an SGI SN box then Y is the recommended value, otherwise say N.
28569 New bus configuration (EXPERIMENTAL)
28571 This configures your Tulip card specifically for the card and
28572 system cache line size type you are using.
28574 This is experimental code, not yet tested on many boards.
28578 Hotplug firmware loading support (EXPERIMENTAL)
28580 This option is provided for the case where no in-kernel-tree modules require
28581 hotplug firmware loading support, but a module built outside the kernel tree
28584 NatSemi SCx200 support
28586 This provides basic support for the National Semiconductor SCx200
28587 processor. Right now this is just a driver for the GPIO pins.
28589 If you don't know what to do here, say N.
28591 This support is also available as a module. If compiled as a
28592 module, it will be called scx200.o.
28594 NatSemi SCx200 GPIO support
28596 Give userspace access to the GPIO pins on the National
28597 Semiconductor SCx200 processors.
28599 This support is also available as a module. If compiled as a
28600 module, it will be called scx200_gpio.o.
28602 NatSemi SCx200 Watchdog
28604 Enable the built-in watchdog timer support on the National
28605 Semiconductor SCx200 processors.
28607 If compiled as a module, it will be called scx200_watchdog.o.
28609 Flash device mapped with DOCCS on NatSemi SCx200
28610 CONFIG_MTD_SCx200_DOCFLASH
28611 Enable support for a flash chip mapped using the DOCCS signal on a
28612 National Semiconductor SCx200 processor.
28614 If you don't know what to do here, say N.
28616 If compiled as a module, it will be called scx200_docflash.o.
28618 BIOS flash chip on AMD76x southbridge
28619 CONFIG_MTD_AMD76XROM
28620 Support for treating the BIOS flash chip on AMD76x motherboards
28621 as an MTD device - with this you can reprogram your BIOS.
28625 If compiled as a module, it will be called amd76xrom.o.
28627 BIOS flash chip on Intel Hub Controller 2
28629 Support for treating the BIOS flash chip on ICH2 motherboards
28630 as an MTD device - with this you can reprogram your BIOS.
28634 If compiled as a module, it will be called ich2rom.o.
28636 BIOS flash chip on Intel SCB2 boards
28637 CONFIG_MTD_SCB2_FLASH
28638 Support for treating the BIOS flash chip on Intel SCB2 boards
28639 as an MTD device - with this you can reprogram your BIOS.
28643 If compiled as a module, it will be called scb2_flash.o.
28645 Flash chips on Tsunami TIG bus
28647 Support for the flash chip on Tsunami TIG bus.
28649 If compiled as a module, it will be called tsunami_flash.o.
28651 Flash chips on LASAT board
28653 Support for the flash chips on the Lasat 100 and 200 boards.
28655 If compiled as a module, it will be called lasat.o.
28657 CFI flash device on SnapGear/SecureEdge
28659 Support for flash chips on NETtel/SecureEdge/SnapGear boards.
28661 If compiled as a module, it will be called nettel.o.
28663 CFI Flash device mapped on DIL/Net PC
28664 CONFIG_MTD_DILNETPC
28665 MTD map driver for SSV DIL/Net PC Boards "DNP" and "ADNP".
28666 For details, see <http://www.ssv-embedded.de/ssv/pc104/p169.htm>
28667 and <http://www.ssv-embedded.de/ssv/pc104/p170.htm>
28669 If compiled as a module, it will be called dilnetpc.o.
28671 Size of DIL/Net PC flash boot partition
28672 CONFIG_MTD_DILNETPC_BOOTSIZE
28673 The amount of space taken up by the kernel or Etherboot
28674 on the DIL/Net PC flash chips.
28676 CFI Flash device mapped on Epxa10db
28677 CONFIG_MTD_EPXA10DB
28678 This enables support for the flash devices on the Altera
28679 Excalibur XA10 Development Board. If you are building a kernel
28680 for on of these boards then you should say 'Y' otherwise say 'N'.
28682 If compiled as a module, it will be called epxa10db-flash.o.
28684 CFI Flash device mapped on the FortuNet board
28685 CONFIG_MTD_FORTUNET
28686 This enables access to the Flash on the FortuNet board. If you
28687 have such a board, say 'Y'.
28689 If compiled as a module, it will be called fortunet.o.
28691 NV-RAM mapping AUTCPU12 board
28692 CONFIG_MTD_AUTCPU12
28693 This enables access to the NV-RAM on autronix autcpu12 board.
28694 If you have such a board, say 'Y'.
28696 If compiled as a module, it will be called autcpu12-nvram.o.
28698 CFI Flash device mapped on EDB7312
28700 This enables access to the CFI Flash on the Cogent EDB7312 board.
28701 If you have such a board, say 'Y' here.
28703 If compiled as a module, it will be called edb7312.o.
28705 JEDEC Flash device mapped on impA7
28707 This enables access to the NOR Flash on the impA7 board of
28708 implementa GmbH. If you have such a board, say 'Y' here.
28710 If compiled as a module, it will be called impa7.o.
28712 JEDEC Flash device mapped on Ceiva/Polaroid PhotoMax Digital Picture Frame
28714 This enables access to the flash chips on the Ceiva/Polaroid
28715 PhotoMax Digital Picture Frame.
28716 If you have such a device, say 'Y'.
28718 If compiled as a module, it will be called ceiva.o.
28720 System flash on MBX860 board
28722 This enables access routines for the flash chips on the Motorola
28723 MBX860 board. If you have one of these boards and would like
28724 to use the flash chips on it, say 'Y'.
28726 If compiled as a module, it will be called mbx860.o.
28730 Mapping for accessing flash devices on add-in cards like the Intel XScale
28731 IQ80310 card, and the Intel EBSA285 card in blank ROM programming mode
28732 (please see the manual for the link settings).
28734 If compiled as a module, it will be called pci.o.
28736 If you are not sure, say N.
28740 Map driver for accessing PCMCIA linear flash memory cards. These
28741 cards are usually around 4-16MiB in size. This does not include
28742 Compact Flash cards which are treated as IDE devices.
28744 If compiled as a module, it will be called pcmciamtd.o.
28746 Generic uClinux RAM/ROM filesystem support
28748 Map driver to support image based filesystems for uClinux.
28750 If compiled as a module, it will be called uclinux.o.
28752 NatSemi SCx200 I2C using GPIO pins
28754 Enable the use of two GPIO pins of a SCx200 processor as an I2C bus.
28756 If you don't know what to do here, say N.
28758 If compiled as a module, it will be called scx200_i2c.o.
28760 GPIO pin used for SCL
28761 CONFIG_SCx200_I2C_SCL
28762 Enter the GPIO pin number used for the SCL signal. This value can
28763 also be specified with a module parameter.
28765 GPIO pin used for SDA
28766 CONFIG_SCx200_I2C_SDA
28767 Enter the GPIO pin number used for the SSA signal. This value can
28768 also be specified with a module parameter.
28770 NatSemi SCx200 ACCESS.bus
28772 Enable the use of the ACCESS.bus controllers of a SCx200 processor.
28774 If you don't know what to do here, say N.
28776 If compiled as a module, it will be called scx200_acb.o.
28778 IPMI top-level message handler
28779 CONFIG_IPMI_HANDLER
28780 This enables the central IPMI message handler, required for IPMI
28781 to work. Note that you must have this enabled to do any other IPMI
28784 IPMI is a standard for managing sensors (temperature,
28785 voltage, etc.) in a system.
28787 See Documentation/IPMI.txt for more details on the driver.
28791 Generate a panic event to all BMCs on a panic
28792 CONFIG_IPMI_PANIC_EVENT
28793 When a panic occurs, this will cause the IPMI message handler to
28794 generate an IPMI event describing the panic to each interface
28795 registered with the message handler.
28797 Device interface for IPMI
28798 CONFIG_IPMI_DEVICE_INTERFACE
28799 This provides an IOCTL interface to the IPMI message handler so
28800 userland processes may use IPMI. It supports poll() and select().
28804 Provides a driver for a KCS-style interface to a BMC.
28806 IPMI Watchdog Timer
28807 CONFIG_IPMI_WATCHDOG
28808 This enables the IPMI watchdog timer.
28812 This option is provided for the case where no in-kernel-tree
28813 modules require CRC32 functions, but a module built outside the
28814 kernel tree does. Such modules that use library CRC32 functions
28815 require that you say M or Y here.
28817 Chassis LCD and LED support
28818 CONFIG_CHASSIS_LCD_LED
28819 Say Y here if you want to enable support for the Heartbeat,
28820 Disk/Network activities LEDs on some PA-RISC machines,
28821 or support for the LCD that can be found on recent material.
28823 This has nothing to do with LED State support for A, J and E class.
28827 VSC/GSC/HSC bus support
28829 The VSC, GSC and HSC busses were used from the earliest 700-series
28830 workstations up to and including the C360/J2240 workstations. They
28831 were also used in servers from the E-class to the K-class. They
28832 are not found in B1000, C3000, J5000, A500, L1000, N4000 and upwards.
28833 If in doubt, say "Y".
28837 Say Y here to support the Wax multifunction chip found in some
28838 older systems, including B/C/D/R class and 715/64, 715/80 and
28839 715/100. Wax includes an EISA adapter, a serial port (not always
28840 used), a HIL interface chip and is also known to be used as the
28841 GSC bridge for an X.25 GSC card.
28843 GSCtoPCI/Dino PCI support
28845 Say Y here to support the Dino & Cujo GSC to PCI bridges found in
28846 machines from the B132 to the C360, the J2240 and the A180. Some
28847 GSC/HSC cards (eg gigabit & dual 100 Mbit Ethernet) have a Dino on
28848 the card, and you also need to say Y here if you have such a card.
28849 Note that Dino also supplies one of the serial ports on certain
28850 machines. If in doubt, say Y.
28854 Use the IA-PC HPET (High Precision Event Timer) to manage
28855 time in preference to the PIT and RTC, if a HPET is
28856 present. The HPET provides a stable time base on SMP
28857 systems, unlike the RTC, but it is more expensive to access,
28858 as it is off-chip. You can find the HPET spec at
28859 <http://www.intel.com/labs/platcomp/hpet/hpetspec.htm>.
28865 Support the K8 IOMMU. Needed to run systems with more than 4GB of memory
28866 properly with 32-bit PCI devices that do not support DAC (Double Address
28867 Cycle). The IOMMU can be turned off at runtime with the iommu=off parameter.
28868 Normally the kernel will take the right choice by itself.
28871 Debug __init statements
28873 Fill __init and __initdata at the end of boot. This helps debugging
28874 invalid uses of __init and __initdata after initialization.
28878 Force the IOMMU to on even when you have less than 4GB of memory and add
28880 Can be disabled at boot time with iommu=noforce.
28884 Add a simple leak tracer to the IOMMU code. This is useful when you
28885 are debugging a buggy device driver that leaks IOMMU mappings.
28887 pSeries Hypervisor Virtual Console support
28889 pSeries machines when partitioned support a hypervisor virtual
28890 console. This driver allows each pSeries partition to have a console
28891 which is accessed via the HMC.
28894 This option provides the core Cryptographic API.
28897 HMAC: Keyed-Hashing for Message Authentication (RFC2104).
28898 This is required for IPSec.
28901 These are 'Null' algorithms, used by IPsec, which do nothing.
28904 MD4 message digest algorithm (RFC1320).
28907 MD5 message digest algorithm (RFC1321).
28910 SHA-1 secure hash standard (FIPS 180-1/DFIPS 180-2).
28912 CONFIG_CRYPTO_SHA256
28913 SHA256 secure hash standard (DFIPS 180-2).
28915 This version of SHA implements a 256 bit hash with 128 bits of
28916 security against collision attacks.
28918 CONFIG_CRYPTO_SHA512
28919 SHA512 secure hash standard (DFIPS 180-2).
28921 This version of SHA implements a 512 bit hash with 256 bits of
28922 security against collision attacks.
28924 This code also includes SHA-384, a 384 bit hash with 192 bits
28925 of security against collision attacks.
28927 CONFIG_CRYPTO_WP512
28928 Whirlpool hash algorithm 512, 384 and 256-bit hashes
28930 Whirlpool-512 is part of the NESSIE cryptographic primitives.
28931 Whirlpool will be part of the ISO/IEC 10118-3:2003(E) standard
28934 http://planeta.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html
28937 DES cipher algorithm (FIPS 46-2), and Triple DES EDE (FIPS 46-3).
28939 CONFIG_CRYPTO_BLOWFISH
28940 Blowfish cipher algorithm, by Bruce Schneier.
28942 This is a variable key length cipher which can use keys from 32
28943 bits to 448 bits in length. It's fast, simple and specifically
28944 designed for use on "large microprocessors".
28946 See also <http://www.counterpane.com/blowfish.html>.
28948 CONFIG_CRYPTO_TWOFISH
28949 Twofish cipher algorithm.
28951 Twofish was submitted as an AES (Advanced Encryption Standard)
28952 candidate cipher by researchers at CounterPane Systems. It is a
28953 16 round block cipher supporting key sizes of 128, 192, and 256
28957 http://www.counterpane.com/twofish.html
28959 CONFIG_CRYPTO_SERPENT
28960 Serpent cipher algorithm, by Anderson, Biham & Knudsen.
28962 Keys are allowed to be from 0 to 256 bits in length, in steps
28963 of 8 bits. Also includes the 'Tnepres' algorithm, a reversed
28964 variant of Serpent for compatibility with old kerneli code.
28967 http://www.cl.cam.ac.uk/~rja14/serpent.html
28970 AES cipher algorithms (FIPS-197). AES uses the Rijndael
28973 Rijndael appears to be consistently a very good performer in
28974 both hardware and software across a wide range of computing
28975 environments regardless of its use in feedback or non-feedback
28976 modes. Its key setup time is excellent, and its key agility is
28977 good. Rijndael's very low memory requirements make it very well
28978 suited for restricted-space environments, in which it also
28979 demonstrates excellent performance. Rijndael's operations are
28980 among the easiest to defend against power and timing attacks.
28982 The AES specifies three key sizes: 128, 192 and 256 bits
28984 See http://csrc.nist.gov/encryption/aes/ for more information.
28986 CONFIG_CRYPTO_CAST5
28987 CAST5 (CAST-128) cipher algorithm.
28989 The CAST5 encryption algorithm (synonymous with CAST-128) is
28990 described in RFC2144.
28992 CONFIG_CRYPTO_CAST6
28993 CAST6 (CAST-256) cipher algorithm.
28995 The CAST6 encryption algorithm (synonymous with CAST-256) is
28996 described in RFC2612.
28999 TEA cipher algorithm.
29001 Tiny Encryption Algorithm is a simple cipher that uses
29002 many rounds for security. It is very fast and uses
29005 Xtendend Tiny Encryption Algorithm is a modification to
29006 the TEA algorithm to address a potential key weakness
29007 in the TEA algorithm.
29009 Xtendend Encryption Tiny Algorithm is a mis-implementation
29010 of the XTEA algorithm for compatibility purposes.
29013 ARC4 cipher algorithm.
29015 ARC4 is a stream cipher using keys ranging from 8 bits to 2048
29016 bits in length. This algorithm is required for driver-based
29017 WEP, but it should not be for other purposes because of the
29018 weakness of the algorithm.
29020 CONFIG_CRYPTO_KHAZAD
29021 Khazad cipher algorithm.
29023 Khazad was a finalist in the initial NESSIE competition. It is
29024 an algorithm optimized for 64-bit processors with good performance
29025 on 32-bit processors. Khazad uses an 128 bit key size.
29028 http://planeta.terra.com.br/informatica/paulobarreto/KhazadPage.html
29030 CONFIG_CRYPTO_ANUBIS
29031 Anubis cipher algorithm.
29033 Anubis is a variable key length cipher which can use keys from
29034 128 bits to 320 bits in length. It was evaluated as a entrant
29035 in the NESSIE competition.
29038 https://www.cosic.esat.kuleuven.ac.be/nessie/reports/
29039 http://planeta.terra.com.br/informatica/paulobarreto/AnubisPage.html
29041 CONFIG_CRYPTO_DEFLATE
29042 This is the Deflate algorithm (RFC1951), specified for use in
29043 IPSec with the IPCOMP protocol (RFC3173, RFC2394).
29045 You will most probably want this if using IPSec.
29047 CONFIG_CRYPTO_MICHAEL_MIC
29048 Michael MIC is used for message integrity protection in TKIP
29049 (IEEE 802.11i). This algorithm is required for TKIP, but it
29050 should not be used for other purposes because of the weakness
29054 Quick & dirty crypto test module.
29056 CONFIG_SOUND_WM97XX
29057 Say Y here to support the Wolfson WM9705 and WM9712 touchscreen
29058 controllers. These controllers are mainly found in PDA's
29059 i.e. Dell Axim and Toshiba e740
29061 This is experimental code.
29062 Please see Documentation/wolfson-touchscreen.txt for
29063 a complete list of parameters.
29065 In order to use this driver, a char device called wm97xx with a major
29066 number of 10 and minor number 16 will have to be created under
29070 mknod /dev/touchscreen/wm97xx c 10 16
29072 If you want to compile this as a module ( = code which can be
29073 inserted in and removed from the running kernel whenever you want),
29074 say M here. The module will be called ac97_plugin_wm97xx.o.
29079 # A couple of things I keep forgetting:
29080 # capitalize: AppleTalk, Ethernet, DOS, DMA, FAT, FTP, Internet,
29081 # Intel, IRQ, ISDN, Linux, MSDOS, NetWare, NetWinder,
29082 # NFS, PCI, SCSI, SPARC
29083 # two words: file system, hard drive, hard disk, home page,
29084 # user space, web site
29085 # other: it's safe to save; daemon; use --, not - or ---;
29086 # use KB for 1024 bytes, not kB or K.
29089 # This is used by Emacs' spell checker ispell.el:
29091 # LocalWords: CONFIG coprocessor DX Pentium SX lilo loadlin HOWTO ftp ibiblio
29092 # LocalWords: unc edu docs emu README kB BLK DEV FD Thinkpad fd MFM RLL IDE gz
29093 # LocalWords: cdrom diskless netboot nfs xzvf ATAPI MB ide pavia rubini pl pd
29094 # LocalWords: HD CD-ROMs IDECD NEC MITSUMI filesystem XT XD PCI BIOS cezar ATEN
29095 # LocalWords: ISA EISA Microchannel VESA BIOSes IPC SYSVIPC ipc Ctrl dmesg hlt
29096 # LocalWords: BINFMT Linkable http ac uk jo html GCC SPARC AVANTI CABRIOLET EB
29097 # LocalWords: netscape gcc LD CC toplevel MODVERSIONS insmod rmmod modprobe IP
29098 # LocalWords: genksyms INET loopback gatewaying Ethernet PPP ARP Arp MEMSIZE
29099 # LocalWords: howto multicasting MULTICAST MBONE firewalling ipfw ACCT resp ip
29100 # LocalWords: proc acct IPIP encapsulator decapsulator klogd RARP EXT PS
29101 # LocalWords: telnetting subnetted NAGLE rlogin NOSR ttyS TGA techinfo mbone nl
29102 # LocalWords: Mb SKB IPX Novell dosemu DDP ATALK vmalloc visar ehome
29103 # LocalWords: SD CHR scsi thingy SG CD LUNs LUN jukebox Adaptec BusLogic EATA
29104 # LocalWords: buslogic DMA DPT ATT eata dma PIO UltraStor fdomain umsdos ext
29105 # LocalWords: QLOGIC qlogic TMC seagate Trantor ultrastor FASST wd NETDEVICES
29106 # LocalWords: unix BBS linux CSLIP PLIP Kirch's LDP CSlip SL SCC IRQ csustan
29107 # LocalWords: Turbo Laplink plip NCSA port's ReQuest IRQs EQL SMC AMD PCnet NE
29108 # LocalWords: COM ELPLUS Com EtherLinkIII VLB Arcnet Cabletron DEPCA DE carlos
29109 # LocalWords: depca EtherWorks EWRK ewrk SEEQ EtherExpress EEXPRESS NI xxx dia
29110 # LocalWords: EtherExpress WaveLAN wavelan PCLAN HPLAN VG SK Ansel Xen de ZNET
29111 # LocalWords: PCMCIA cb stanford LAN TEC RealTek ATP atp DLINK NetTools VISWS
29112 # LocalWords: TR Sony CDU caddyless cdu Mitsumi MCD cd mcd XA MultiSession CDA
29113 # LocalWords: Matsushita Panasonic SBPCD Soundblaster Longshine sbpcd Aztech
29114 # LocalWords: Okano Wearnes AZTCD CDD SE aztcd sonycd Goldstar GSCD Philips fs
29115 # LocalWords: LMS OPTCD Sanyo SJCD minix faqs xiafs XIA msdos mtools Cichocki
29116 # LocalWords: std softlinks umssync NetworkFileSharing nfsd mountd CDs HPFS TI
29117 # LocalWords: hpfs SYSV SCO iBCS Wyse WordPerfect tsx mit unixes sysv NR irisa
29118 # LocalWords: SMB WfW Cyclades async mux Logitech busmouse MouseSystem aka AST
29119 # LocalWords: PSMOUSE Compaq trackballs Travelmate Inport ATIXL ATI busmice ld
29120 # LocalWords: gpm config QIC DYNCONF FTAPE Stor Ftape ftape pcsndrv manpage NT
29121 # LocalWords: readprofile diskdrives org com masq EtherTalk tcp netrom sunacm
29122 # LocalWords: misc AIC aic pio scc Portmaster eql GIS PhotoCDs MCDX Perell PG
29123 # LocalWords: mcdx gscd optcd sjcd ISP hdparm Workgroups Lan samba PARIDE PCD
29124 # LocalWords: filesystems smbfs ATA ppp PCTech RZ www powerquest txt CMD ESDI
29125 # LocalWords: chipset FB multicast MROUTE appletalk ifconfig IBMTR multiport
29126 # LocalWords: Multisession STALDRV EasyIO EC EasyConnection ISTALLION ONboard
29127 # LocalWords: Brumby pci TNC cis ohio faq usenet NETLINK dev hydra ca Tyne mem
29128 # LocalWords: carleton DECstation SUNFD JENSEN Noname XXXM SLiRP LILO's amifb
29129 # LocalWords: pppd Zilog ZS SRM bootloader ez mainmenu rarp ipfwadm paride pcd
29130 # LocalWords: RTNETLINK mknod xos MTU lwared Macs netatalk macs cs Wolff
29131 # LocalWords: dartmouth flowerpt MultiMaster FlashPoint tudelft etherexpress
29132 # LocalWords: ICL EtherTeam ETH IDESCSI TXC SmartRAID SmartCache httpd sjc dlp
29133 # LocalWords: thesphere TwoServers BOOTP DHCP ncpfs BPQETHER BPQ MG HIPPI cern
29134 # LocalWords: bsd comp SPARCstation le SunOS ie Gracilis PackeTwin PT pt LU FX
29135 # LocalWords: FX TEAC CR LCS mS ramdisk IDETAPE cmd fperllo encis tcfs unisa
29136 # LocalWords: Vertos Genoa Funai hsfs NCP NetWare tgz APM apm ioctls UltraLite
29137 # LocalWords: TravelMate CDT LCD backlight VC RPC Mips AXP barlow cdrtools pg
29138 # LocalWords: PMAX MILO Alphas Multia Tseng linuxelf endian mipsel mips drv HT
29139 # LocalWords: kerneld callouts AdvanSys advansys Admin WDT DataStor EP verden
29140 # LocalWords: wdt hdb hdc bugfix SiS vlb Acculogic CSA DTC dtc Holtek ht QDI
29141 # LocalWords: QD qd UMC umc ALI ali lena fnet fr azstarnet cdr fb MDA ps esdi
29142 # LocalWords: Avanti XL AlphaStations Jensen DECpc AXPpci UDB Cabriolet MCA RC
29143 # LocalWords: AlphaPC mca AOUT OUTput PPro sipx gwdg lo nwe FourPort Boca unm
29144 # LocalWords: Keepalive linefill RELCOM keepalive analogue CDR conf CDI INIT
29145 # LocalWords: OPTi isp irq noisp VFAT vfat NTFS losetup dmsdosfs dosfs ISDN MP
29146 # LocalWords: NOWAYOUT behaviour dialin isdn callback BTX Teles XXXX LVM lvm
29147 # LocalWords: ICN EDSS Cisco
29148 # LocalWords: ipppd syncppp RFC MPP VJ downloaded icn NICCY Creatix shmem ufr
29149 # LocalWords: ibp md ARCnet ether encap NDIS arcether ODI Amigas AmiTCP NetBSD
29150 # LocalWords: initrd tue util DES funet des OnNet BIOSP smc Travan Iomega CMS
29151 # LocalWords: FC DC dc PPA IOMEGA's ppa RNFS FMV Fujitsu ARPD arpd loran layes
29152 # LocalWords: FRAD indiana framerelay DLCI DCLIs Sangoma SDLA mrouted sync sec
29153 # LocalWords: Starmode Metricom MosquitoNet mosquitonet kbit nfsroot Digiboard
29154 # LocalWords: DIGI Xe Xeve digiboard UMISC touchscreens mtu Ethernets HBAs MEX
29155 # LocalWords: Shifflett netcom js jshiffle WIC DECchip ELCP EtherPower dst RTC
29156 # LocalWords: rtc SMP lp Digi Intl RightSwitch DGRS dgrs AFFS Amiga UFS SDL AP
29157 # LocalWords: Solaris RISCom riscom syncPPP PCBIT pcbit sparc anu au artoo MFB
29158 # LocalWords: hitchcock Crynwr cnam pktdrvr NCSA's CyDROM CyCD-ROM FreeBSD NeXT
29159 # LocalWords: NeXTstep disklabel disklabels SMD FFS tm AmigaOS diskfiles Un IQ
29160 # LocalWords: Bernd informatik rwth aachen uae affs multihosting bytecode java
29161 # LocalWords: applets applet JDK ncsa cabi SNI Alphatronix readme LANs scarab
29162 # LocalWords: winsock RNIS caltech OSPF honour Honouring Mbit LocalTalk DEFRAG
29163 # LocalWords: localtalk download Packetwin Baycom baycom interwork ASCII JNT
29164 # LocalWords: Camtec proxying indyramp defragment defragmented UDP FAS FASXX
29165 # LocalWords: FastSCSI SIO FDC qlogicfas QLogic qlogicisp setbaycom ife ee LJ
29166 # LocalWords: ethz ch Travelmates ProAudioSpectrum ProAudio SoundMan SB SBPro
29167 # LocalWords: Thunderboard SM OPL FM ADLIB TSR Gravis MPU PSS ADI SW DSP codec
29168 # LocalWords: ADSP ESC ASIC daughtercard GUSMAX MSS NX AdLib Excell Ensoniq YM
29169 # LocalWords: SoundScape Spea MediaTriX AudioTriX WSS OTI ThunderBoard VoxWare
29170 # LocalWords: Soundscape SSCAPE TRIX MediaTrix PnP Maui dsp midixx EIA getty
29171 # LocalWords: mgetty sendfax gert greenie muc lowlevel Lasermate LanManager io
29172 # LocalWords: OOPSes trackball binghamton mobileip ncr IOMAPPED settags ns ser
29173 # LocalWords: setsync NEGO MPARITY autotuning prefetch PIIX cdwrite utils rc
29174 # LocalWords: PCWATCHDOG berkprod bitgate boldt ucsb jf kyoto jp euc Tetsuyasu
29175 # LocalWords: YAMADA tetsu cauchy nslab ntt nevod perm su doc kaf kheops wsc
29176 # LocalWords: traduc Bourgin dbourgin menuconfig kfill READMEs HOWTOs Virge WA
29177 # LocalWords: IDEDISK IDEFLOPPY EIDE firewalls QMAGIC ZMAGIC LocalWords opti
29178 # LocalWords: SVGATextMode vga svga Xkernel syr jmwobus comfaqs dhcp flakey GD
29179 # LocalWords: IPv IPng interoperability ipng ipv radio's tapr pkthome PLP nano
29180 # LocalWords: Ses Mhz sethdlc SOUNDMODEM WindowsSoundSystem smdiag pcf inka ES
29181 # LocalWords: smmixer ptt circ soundmodem MKISS FDDI DEFEA DEFPA DEFXX redhat
29182 # LocalWords: HyperNews khg mconv sed lina wuftpd MicroChannel netlink irc cum
29183 # LocalWords: raudio RealAudio PPROP NETBIOS GUI IBMMCA ELMC Racal Interlan fi
29184 # LocalWords: eth shapecfg src esp PCWD PREVSTAT bootparam sig bitwizard SBC
29185 # LocalWords: downloads AFSK TCM FP Karn KA FSK RUH LinkSys cron mouseman LLC
29186 # LocalWords: SyQuest SyQuest's CCITT MicroSolutions BPCD bpcd ESPSERIAL PROM
29187 # LocalWords: SUNESP openprom OPENPROMIO quango themall al TT MC MMU LC RMW AA
29188 # LocalWords: INSNS Ataris AutoConfig ZORRO OCS AMIFB Agnus Denise ECS CDTV GB
29189 # LocalWords: AGA Cybervision CYBER GSP TMS DMI Zorro ACSI ROMs SLM BioNet GVP
29190 # LocalWords: PAMsNet TekMagic Cyberstorm MkI CYBERSTORMII MkII BLZ onboard cx
29191 # LocalWords: Village Tronic ATARILANCE RieblCard PAMCard VME MFP sangoma LAPB
29192 # LocalWords: Rhotron BioData's Multiface AMIGAMOUSE COPCON Amiga's bitplanes
29193 # LocalWords: ATARIMOUSE MFPSER SCC's MegaSTE ESCC Atari's GVPIOEXT DMASOUND
29194 # LocalWords: fdutils cisco univercd rpcg htm iface lapb LAPBETHER tpqic qic
29195 # LocalWords: SYNTH xd en binfmt aout ipip terra ipx sd sr sg wic framebuffer
29196 # LocalWords: ibmmca lapbether mkiss dlci sdla fmv eepro eexpress ni hp ne es
29197 # LocalWords: ibmtr isofs ROMFS romfs pcxx cyclades istallion psaux msbusmouse
29198 # LocalWords: atixlmouse sbin softdog pcwd USS Lite ACI miroSOUND PCM miroPCM
29199 # LocalWords: microcontroller miro Voxware downloading teles acsi slm gvp ltpc
29200 # LocalWords: atari ariadne amigamouse atarimouse builtin IPDDP maths bradford
29201 # LocalWords: AppleTalk Farallon PhoneNet Zubkoff lnz SCCB HAPN WANs vesafb nt
29202 # LocalWords: wanrouter WANPIPE multiprotocol Mbps wanpipe EtherWORKS nodma SC
29203 # LocalWords: smp HiSax SiemensChipSet Siemens AVM Elsa ITK hisax PCC MICROR
29204 # LocalWords: Mircolink EURO DSS Spellcaster BRI sc spellcast Digiboards GPIO
29205 # LocalWords: SYMBIOS COMPAT SDMS rev ASUS Tekram HX VX API ibmmcascsi ASY asy
29206 # LocalWords: loader's PCnetPCI automounter AUTOFS amd autofs VT Gallant's Pnp
29207 # LocalWords: AEDSP aedsp enskip tik Sysctl sysctl PARPORT parport pnp IDs EPP
29208 # LocalWords: Autoprobe bart patrickr HDLS READBACK AB usr DAMA DS SparQ aten
29209 # LocalWords: Symbios PCscsi tmscsim RoamAbout GHz Hinds contrib mathematik ok
29210 # LocalWords: darmstadt okir DIGIEPCA International's Xem digiepca epca bootup
29211 # LocalWords: zorro CAPI AVMB capi avmb VP SYN syncookies EM em pc Ethertalk
29212 # LocalWords: Dayna DL Daynatalk LT PhoneNET ATB Daystar queueing CMDS SCBs ls
29213 # LocalWords: SCB STATS Thinnet ThunderLAN TLAN Netelligent NetFlex tlan james
29214 # LocalWords: caldera Preload Preloading slowdowns schoebel uni NBD nbd prog
29215 # LocalWords: stuttgart rdist TRANS hostnames mango jukeboxes ESS userland PD
29216 # LocalWords: hardlinked NAMETRANS env mtab fstab umount nologin runlevel gid
29217 # LocalWords: adm Nodename hostname uname Kernelname bootp nmi DI OV StegFS
29218 # LocalWords: KERNNAME kname ktype kernelname Kerneltype KERNTYPE Alt RX mdafb
29219 # LocalWords: dataless kerneltype SYSNAME Comtrol Rocketport palmtop fbset EGS
29220 # LocalWords: nvram SYSRQ SysRq PrintScreen sysrq NVRAMs NvRAM Shortwave RTTY
29221 # LocalWords: Sitor Amtor Pactor GTOR hayes TX TMOUT JFdocs BIGMEM DAC IRQ's
29222 # LocalWords: IDEPCI IDEDMA PDC pdc TRM trm raidtools luthien nuclecu BAGET VR
29223 # LocalWords: unam mx miguel koobera uic EMUL solaris pp ieee lpsg co DMAs TOS
29224 # LocalWords: BLDCONFIG preloading jumperless BOOTINIT modutils multipath GRE
29225 # LocalWords: misconfigured autoconfiguration IPGRE ICMP tracert ipautofw PIM
29226 # LocalWords: netis rlynch autofw ipportfw monmouth ipsubs portforwarding pimd
29227 # LocalWords: portfw PIMSM netweb usc pim pf EUI aggregatable PB decapsulate
29228 # LocalWords: ipddp Decapsulation DECAP bool HAMRADIO tcpdump af CDs tx FBCON
29229 # LocalWords: ethertap multisession PPC MMIO GDT GDTH ICP gdth hamradio bpp
29230 # LocalWords: lmh weejock AIMSlab RadioTrack RTRACK HZP OptoSCC TRX rx TRXECHO
29231 # LocalWords: DMASCC paccomm dmascc addr cfg oevsv oe kib picpar FDX baudrate
29232 # LocalWords: baudrates fdx HDX hdx PSK kanren frforum QoS SCHED CBQ SCH sched
29233 # LocalWords: sch cbq CSZ Shenker Zhang csz SFQ sfq TBF tbf PFIFO fifo PRIO RW
29234 # LocalWords: prio Micom xIO dwmw rimi OMIRR omirr omirrd unicode ntfs cmu NIC
29235 # LocalWords: Braam braam Schmidt's freiburg nls codepages codepage Romanian
29236 # LocalWords: Slovak Slovenian Sorbian Nordic iso Catalan Faeroese Galician SZ
29237 # LocalWords: Valencian Slovene Esperanto Estonian Latvian Belarusian KOI mt
29238 # LocalWords: charset Inuit Greenlandic Sami Lappish koi Alexey Kuznetsov's sa
29239 # LocalWords: Specialix specialix DTR RTS RTSCTS cycladesZ Exabyte ftape's inr
29240 # LocalWords: Iomega's LBFM claus ZFTAPE VFS zftape zft William's lzrw DFLT kb
29241 # LocalWords: MTSETBLK MTIOCTOP qft setblk zftape's tar's afio's setdrvbuffer
29242 # LocalWords: Procfs Exabyte's THR FCD sysvinit init PSC pscwdt VMIDI Euro SAB
29243 # LocalWords: Mostek Fastlane PowerMac PReP PMAC PowerPC Macintoshes Starmax
29244 # LocalWords: PowerStack Starmaxes MCOMMON DEVICETREE ATY IMS IMSTT videodev
29245 # LocalWords: BT Hauppauge STB bttv Quickcam BW BWQCAM bw qcam Mediavision PMS
29246 # LocalWords: pms Avatar Freecom Imation Superdisk BPCK bpck COMM comm DSTR ru
29247 # LocalWords: dstr EPAT EPEZ epat EPIA epia FreeCom FRPW frpw KingByte KBIC HW
29248 # LocalWords: KingByte's kbic OnSpec ValuStore FASTROUTE fastroute FLOWCONTROL
29249 # LocalWords: struct APIC realtime OSs LynxOS CNC tmp cvf HFS hfs ADFS Risc os
29250 # LocalWords: adfs ncpmount namespace SUBDIR reexport NDS kcore FT SPX spx DAT
29251 # LocalWords: interserver BLKSZ NUMBUFFERS apmd Tadpole ANA roestock QuickCam
29252 # LocalWords: isapnptools Colour CQCAM colour Connectix QuickClip prive mentre
29253 # LocalWords: KMOD kmod conformant utexas kharker UnixWare Mwave cgi cl ts ibm
29254 # LocalWords: eXchange threepio oakland simtel pre ULTRAMCA EtherLink isa luik
29255 # LocalWords: EtherLink OpenBSD pts DEVPTS devpts ptmx ttyp glibc readback SA
29256 # LocalWords: mwave OLDCARD isdnloop linklevel loopctrl Eicon Diehl DIEHLDIVA
29257 # LocalWords: ASUSCOM AsusCom TELEINT semiactiv Sedlbauer Sportster TA MIC ITH
29258 # LocalWords: NETjet NetJet Niccy Neuhaus sparcs AOC AOCD AOCE Microlink SAA
29259 # LocalWords: teletext WinTV saa iproute tc Quadra Performa PowerBook tor AUN
29260 # LocalWords: setserial compsoc steve Econet econet AUNUDP psched TEQL TLE CLS
29261 # LocalWords: teql FW Ingres TwistedPair MTRR MTRRs mtrr cfs crypto TD ktti KT
29262 # LocalWords: PHd ICS ipchains adelaide rustcorp syslog Cumana steganography
29263 # LocalWords: AcornSCSI EcoSCSI EESOX EESOXSCSI Powertec POWERTECSCSI dec SF
29264 # LocalWords: RadioReveal gatekeeper aimslab aztech FMI sf fmi RTL rtl cesdis
29265 # LocalWords: Yellowfin gsfc nasa gov yellowfin pcnet Mylex LNE lne EtherH hs
29266 # LocalWords: EBSA chattr RiscOS Winmodem AGP Atomwide DUALSP pcsp robinson CT
29267 # LocalWords: SGALAXY Waverider DSPxxx TRXPRO AudioTrix OSWF MOT CFB DSY kbps
29268 # LocalWords: tuwien kkudielk LVD mega lun MAXTAGS Gbps arcnet Olicom SNA PAE
29269 # LocalWords: SysKonnect tms sna etherboot ufs NetBEUI MultiSound MSNDCLAS GX
29270 # LocalWords: MSNDINIT MSNDPERM MSNDPIN PNDSPINI PNDSPERM Ensoniq's RetinaZ SS
29271 # LocalWords: AudioPCI lspci SonicVibes sonicvibes SPARCs roadrunner CLgen UPA
29272 # LocalWords: swansea shtml Zoltrix zoltrix BINUTILS EGCS binutils VIDC DACs
29273 # LocalWords: CyberVision Cirrus PowerBooks Topcat SBUS CGsix TurboGX BWtwo SS
29274 # LocalWords: CGthree TCX unswappable vfb fbcon hicolor truecolor AFB ILBM SOC
29275 # LocalWords: IPLAN gracilis Fibre SBus SparcSTORAGE SV jnewbigin swin QNX qnx
29276 # LocalWords: PTY PTYS ptyxx ttyxx PTYs ssh sb Avance ALS pss pvv kerneli hd
29277 # LocalWords: synth WaveFront MSND NONPNP AudioExcelDSP STRAM APUS CHRP MBX Nx
29278 # LocalWords: PowerMac's BMAC radiotrack rtrack miropcm OFFBOARD HPT UDMA DVD
29279 # LocalWords: hpt fokus gmd Cyrix DXL SLC DLC NexGen MediaGX GXm IDT WinChip
29280 # LocalWords: MMX MII valkyrie mdacon vdolive VDOLive cuseeme CU hippi rrunner
29281 # LocalWords: SeeMe ipmasqadm juanjox ipmarkfw markfw TNCs Microdyne rhine lib
29282 # LocalWords: libc jsX gamepad gameport CHF FCS FPGaming MadCatz ASSASIN GrIP
29283 # LocalWords: Assasin gamepads GamePad PDPI gamecards gamecard WingMan BSP WCS
29284 # LocalWords: ThunderPad CyberMan SideWinder ThrustMaster DirectConnect NES XF
29285 # LocalWords: Millenium SNES PSX Multisystem Nintendo PlayStation Amstrad CPC
29286 # LocalWords: Sega TurboGraFX Steffen Schwenke Multiststem PDIF FIFOSIZE EPLUS
29287 # LocalWords: PowerUP RoadRunner tahallah dos functionkey setterm imladris Woz
29288 # LocalWords: PowerMacs Winbond Algorithmics ALGOR algor ECOFF IRIX SGI SGI's
29289 # LocalWords: gfx virtualized Xpmac mklinux XFree FBDev Woodhouse mvhi Seeq fp
29290 # LocalWords: SGISEEQ HIgh ADB ADBMOUSE crosscompiler CROSSCOMPILE FPE GDB gdb
29291 # LocalWords: JOYPORT rp spoofing DawiControl NOGENSUPP EEPROM HSSI Alessandro
29292 # LocalWords: singleprocessor tex MATHEMU FRIQ Maxell friq Alcor XLT AlphaBook
29293 # LocalWords: AlphaPCI DP LX Miata Mikasa Noritake RPX UX BX Takara EV PRIMO
29294 # LocalWords: TSC Matrox Productiva matroxfb matrox multihead ia linuxhq MFW
29295 # LocalWords: mfw AAA MCS Initio XXU initio imm AutoDetect IZIP CTR usec HDLC
29296 # LocalWords: COSA SRP muni cz kas cosa Alteon AceNIC acenic VTOC OSes GMT SAx
29297 # LocalWords: Inspiron localtime INTS Thinkpads Ralf Brown's Flightstick NNN
29298 # LocalWords: Xterminator Blackhawk NN mpu ioports DCA HPDCA HPLANCE DIO Corel
29299 # LocalWords: GemTek gemtek CMDLINE IrDA PDA's irmanager irattach RR AVA DN rg
29300 # LocalWords: uit dagb irda LSAP IrLMP RR's IrLAP IR alloc skb's kfree skb's
29301 # LocalWords: GZIP IrLAN NetbeamIR ESI JetEye IrOBEX IrCOMM TTY's minicom dti
29302 # LocalWords: ircomm ircomm pluto thiguchi IrTTY Linux's bps NetWinder MIR NSC
29303 # LocalWords: ACTiSYS dongle dongles esi actisys IrMate tekram BVM MVME
29304 # LocalWords: BVME BVME WRITETHROUGH copyback writethrough fwmark syncookie tu
29305 # LocalWords: alphalinux GOBIOS csn chemnitz nat ACARD AMI MegaRAID megaraid
29306 # LocalWords: QNXFS ISI isicom xterms Apollos VPN RCPCI rcpci sgi visws pcmcia
29307 # LocalWords: IrLPT UIRCC Tecra Strebel jstrebel suse Eichwalder ke INI INIA
29308 # LocalWords: FCP qlogicfc sym isapnp DTLK DoubleTalk rcsys dtlk DMAP SGIVW ar
29309 # LocalWords: dmabuf EcoRadio MUTEFREQ GIrBIL girbil tepkom vol mha diplom PQS
29310 # LocalWords: bmac Microgate SyncLink synclink hdlc excl ioaddr Tane tanep TCQ
29311 # LocalWords: PDS SMALLDOS charsets bigfoot kernelfr mcs cls fw rsvp SKnet sk
29312 # LocalWords: SKMC USB UHCI OHCI intel compaq usb ohci HCD Virt Compaq's hcd
29313 # LocalWords: VROOTHUB KBD ARRs MCRs NWBUTTON nwbutton NUM WaveArtist APNE cpu
29314 # LocalWords: apne blackhawke PlanB lu mlan planb NWFPE FPA nwfpe unbootable
29315 # LocalWords: FPEmulator ds vmlinux initialization discardable pgtable PGT mdw
29316 # LocalWords: quicklist pagetable arthur StrongARM podule podules Autodetect
29317 # LocalWords: dodgy IrPORT irport Litelink litelink SuSE rtfm internet hda CY
29318 # LocalWords: multmode DriveReady SeekComplete DriveStatusError miscompile AEC
29319 # LocalWords: mainboard's Digital's alim FastTrak aec PIIXn piix Gayle Eyetech
29320 # LocalWords: Catweasel IDEDOUBLER Powerbook Centris ICSIDE RapIDE OSM HDM IOP
29321 # LocalWords: HDM's OSM's lan FibreChannel ECP autoprobe itg lbl ipmasq cjb IC
29322 # LocalWords: bieringer Caulfield's dreamtime decnet SIOCFIGCONF SIOCGIFCONF
29323 # LocalWords: rtnetlink Endnode Aironet Arlan Telxon ylenurme arlan ACB aeschi
29324 # LocalWords: Sealevel sealevel Cyclom br wanconfig tarball conectiva cycsyn
29325 # LocalWords: devel bazar cyclomx NetGear GA IBMOL Lanstreamer uhci eu efs CYZ
29326 # LocalWords: olympic linuxtr usbcore acm EZUSB downloader EFS XFS INTR op IIC
29327 # LocalWords: heine soundcore JavaStations JavaStation GemTeks TerraTec TODO
29328 # LocalWords: ActiveRadio Standalone terratec Rolf Offermanns rolf offermanns
29329 # LocalWords: Zoran ZR Buz LML CPQ DA cpqarray PPDEV deviceid vlp ppdev atyfb
29330 # LocalWords: AcceleRAID eXtremeRAID NETFILTER Netfilter masqueraded netfilter
29331 # LocalWords: kernelnotes Cardbus PCMCIA's CardBus clgenfb Permedia YAM MMAP
29332 # LocalWords: mmapped ATM atm PVCs SVCs InARP ATMARP neighbour neighbours MPOA
29333 # LocalWords: VCs ENI FPGA Tonga MMF MF UTP printks ZeitNet ZN ZATM uPD SAR PN
29334 # LocalWords: approx NICStAR NICs ForeRunnerLE Madge Collage ATMizer Dxxxx VCI
29335 # LocalWords: ServeRAID IPS ips ipslinux gzip BSDCOMP LZW RAYCS Interphase app
29336 # LocalWords: Tachyon IPHASE Surfboard NextLevel SURFboard jacksonville Tigon
29337 # LocalWords: fventuri adelphia siglercm linuxpower AceNICs Starfire starfire
29338 # LocalWords: ISOC CPiA cpia uss ACPI UDF DirectCD udf CDRW's OSF Manx acpi DM
29339 # LocalWords: Unixware cymru Computone IntelliPort Intelliport computone SI sx
29340 # LocalWords: adbmouse DRI DRM dlabs GMX PLCs Applicom fieldbus applicom int
29341 # LocalWords: VWSND eg ESSSOLO CFU CFNR scribed eiconctrl eicon hylafax KFPU
29342 # LocalWords: EXTRAPREC fpu mainboards KHTTPD kHTTPd khttpd Xcelerator SBNI tw
29343 # LocalWords: LOGIBUSMOUSE Granch granch sbni Raylink NOHIGHMEM Athlon SIM sim
29344 # LocalWords: hpl Tourrilhes DuraLAN starfire Davicom davicom dmfe auk tms tr
29345 # LocalWords: TokenExpress Belkin Peracom eTek DVDs infradead Cxxx Adlib AV ZX
29346 # LocalWords: NeoMagic CPi CPt Celeron decapsulation Undeletion BFS bfs nVidia
29347 # LocalWords: OnStream Irongate Riva phonedev QuickNet LineJack PhoneJack IXJ
29348 # LocalWords: Quicknet PhoneJACK LineJACK ixj pnpdump Quicknet's Joandi SSID
29349 # LocalWords: aironet quickconfig adhoc btw bap NONCS cardservices Xircom lin
29350 # LocalWords: Netwave AirSurfer netwave HomePNA failover MVP iMacs ALi aktual
29351 # LocalWords: Aladin HIDBP usbkbd KEYBDEV MOUSEDEV JOYDEV EVDEV UAB WhiteHEAT
29352 # LocalWords: Handspring ov DABUSB URB URB's dabusb CRAMFS NFSv ELV IOAPIC WIP
29353 # LocalWords: NLMv SMBus ALGOBIT algo PHILIPSPAR philips elv Velleman velleman
29354 # LocalWords: ALGOPCF Elektor elektor CHARDEV dfx TDFX tdfx Extensa dof gravis
29355 # LocalWords: assasin logitech Overdrive thrustmaster DWave Aureal magellan db
29356 # LocalWords: SpaceTec SpaceOrb SpaceBall spaceorb FLX spaceball turbografx zr
29357 # LocalWords: amiga ESS's WaveWatcher Maxi belkin RW's ata glx GART MPV Baget
29358 # LocalWords: OpenGL Xserver agpgart HOTPLUG CyberPro Integraphics Netwinder
29359 # LocalWords: aty FONTWIDTH eni zatm nicstar ForeRunner OC DECstations DEC's
29360 # LocalWords: PHYsical SUNI reinsertion ChipSAR KVC PHY ClassID iphase iadbg
29361 # LocalWords: DEVS FireWire PCILynx pcilynx LOCALRAM miro's DV RAWIO GRED Mk
29362 # LocalWords: Diffserv DSMARK Ingress Qdisc TCINDEX TMSPCI tmspci Ringode JE
29363 # LocalWords: MADGEMC madgemc TokenRing SMCTR TokenCard smctr Wacom Graphire
29364 # LocalWords: mousedev ConnectTech HandSpring Xirlink IBMCAM ibmcam SN
29365 # LocalWords: DEVICEFS yyy Cymraeg Dwave SIMM JSFLASH JavaStation's multilink
29366 # LocalWords: nsc ircc DDB Vrc CMN TB PROMs Vino rivafb DDC Matroxes MGA TVO
29367 # LocalWords: MAVEN fbdev crtc maven matroxset NTSC PCA SBA AAL SKFP DAS SAS
29368 # LocalWords: skfp Intuos ADMtek's pegasus PLUSB plusb pointopoint mp rio Xeon
29369 # LocalWords: DEVFS devfs dd bs EDSS german TELESPCI FRITZPCI HFC HFCS BDS HST
29370 # LocalWords: ISURF ISAR Saphir HSTSAPHIR Telekom BKM Scitel Quadro SCT Gazel
29371 # LocalWords: SP PRI Hypercope HYSDN Hypercope's hysdn IbssJoinNetTimeout FTDI
29372 # LocalWords: ARCNet Keyspan PDA ADMtek sgalaxy sgbase opl mpuio mpuirq sbio
29373 # LocalWords: sbirq sbdma gus uart mssio mssirq mssdma sscape maui mouirq iph
29374 # LocalWords: CHDLC UPS's usbmouse wacom wmforce keybdev joydev fibre Trunking
29375 # LocalWords: Etherchannel IOC Moxa Intellio moxa SmartIO mxser Mixcom EFI ir
29376 # LocalWords: MIXCOMWD mixcomwd SENDCOMPLETE GMAC iBook gmac OAKNET oaknet PCG
29377 # LocalWords: diffserv irlan irtty toshoboe IrCC Lifebook idex AUTODMA FIP Cxx
29378 # LocalWords: Yenta Databook TCIC FMVJ fmvj NMCLAN LiveWire nmclan XIRC xirc
29379 # LocalWords: loadkeys setfont shm SuperIO soc SOCAL socal FCAL fc fcal COMX
29380 # LocalWords: MultiGate ITConsult comx CMX HiCOMX downloadable hw LoCOMX PROTO
29381 # LocalWords: locomx MixCOM mixcom proto MyriCOM MYRI Sbus myri sbus IBMLS hme
29382 # LocalWords: lanstreamer baseT HAPPYMEAL qfe sunhme SUNLANCE sunlance BigMAC
29383 # LocalWords: SUNBMAC sunbmac QuadEthernet SUNQE qe FastEthernet sunqe DSB PTI
29384 # LocalWords: DSBR dsbr procinfo QLOGICPTI qpti ptisp QLGC qlogicpti se LBA NF
29385 # LocalWords: OPENPROMFS OpenPROM openpromfs OBP OpenBoot flashable Multiboard
29386 # LocalWords: SPARCAUDIO SparcClassic Ultras DBRI Sparcbook sparcaudio SUNBPP
29387 # LocalWords: UltraDMA WDC CRC CONNTRACK IPTABLES iptables nfmark interface's
29388 # LocalWords: tdfxfb TNTx HGA hgafb VERBOSEDEBUG SunTrunking SunSoft XIRTULIP
29389 # LocalWords: ethercards PNIC Macronix MXIC ASIX xircom Mustek MDC gphoto mdc
29390 # LocalWords: CramFs Cramfs uid cramfs AVM's kernelcapi PCIV cdrdao Cdparanoia
29391 # LocalWords: DMX Domex dmx wellington ftdi sio Accton Billington Corega FEter
29392 # LocalWords: MELCO LUA PNA Linksys SNC chkdsk AWACS Webcam RAMFS Ramfs ramfs
29393 # LocalWords: ramfiles MAKEDEV pty WDTPCI APA apa
29395 # The following sets edit modes for GNU EMACS
29397 # case-fold-search:nil
29399 # adaptive-fill:nil