2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
9 The Alpha is a 64-bit general-purpose processor designed and
10 marketed by the Digital Equipment Corporation of blessed memory, now
11 Compaq. Alpha Linux dates from 1995-1996 and was the first non-x86
12 port. The Alpha Linux project has a home page at
13 <http://www.alphalinux.org/>.
26 config RWSEM_GENERIC_SPINLOCK
29 config RWSEM_XCHGADD_ALGORITHM
33 config GENERIC_ISA_DMA
43 prompt "Alpha system type"
49 This is the system type of your hardware. A "generic" kernel will
50 run on any supported Alpha system. However, if you configure a
51 kernel for your specific system, it will be faster and smaller.
53 To find out what type of Alpha system you have, you may want to
54 check out the Linux/Alpha FAQ, accessible on the WWW from
55 <http://www.alphalinux.org/>. In summary:
57 Alcor/Alpha-XLT AS 600
58 Alpha-XL XL-233, XL-266
59 AlphaBook1 Alpha laptop
60 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
61 Cabriolet AlphaPC64, AlphaPCI64
63 EB164 EB164 21164 evaluation board
64 EB64+ EB64+ 21064 evaluation board
65 EB66 EB66 21066 evaluation board
66 EB66+ EB66+ 21066 evaluation board
67 Jensen DECpc 150, DEC 2000 model 300,
70 Miata Personal Workstation 433a, 433au, 500a,
73 Noname AXPpci33, UDB (Multia)
74 Noritake AS 1000A, AS 600A, AS 800
76 Rawhide AS 1200, AS 4000, AS 4100
77 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
79 Sable AS 2000, AS 2100
83 Wildfire AlphaServer GS 40/80/160/320
85 If you don't know what to do, choose "generic".
88 bool "Alcor/Alpha-XLT"
90 For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
91 slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O
92 Address, CIA) - a 383 pin plastic PGA). It provides a DRAM
93 controller (256-bit memory bus) and a PCI interface. It also does
94 all the work required to support an external Bcache and to maintain
95 memory coherence when a PCI device DMAs into (or out of) memory.
100 XL-233 and XL-266-based Alpha systems.
105 Dec AlphaBook1/Burns Alpha-based laptops.
107 config ALPHA_AVANTI_CH
110 config ALPHA_CABRIOLET
113 Cabriolet AlphaPC64, AlphaPCI64 systems. Derived from EB64+ but now
114 baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA
115 slots, 4 PCI slots (one pair are on a shared slot), uses plug-in
116 Bcache SIMMs. Requires power supply with 3.3V output.
121 Various 21264 systems with the tsunami core logic chipset.
122 API Networks: 264DP, UP2000(+), CS20;
123 Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40.
128 EB164 21164 evaluation board from DEC. Uses 21164 and ALCOR. Has
129 ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is
130 shared with an ISA slot) and 2 32-bit PCI slots. Uses plus-in
131 Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD,
132 MOUSE (PS2 style), RTC/NVRAM. Boot ROM is Flash. PC-AT-sized
133 motherboard. Requires power supply with 3.3V output.
135 config ALPHA_EB64P_CH
141 A Digital DS group board. Uses 21066 or 21066A. I/O sub-system is
142 identical to EB64+. Baby PC-AT size. Runs from standard PC power
143 supply. The EB66 schematic was published as a marketing poster
144 advertising the 21066 as "the first microprocessor in the world with
150 Later variant of the EB66 board.
155 Apparently an obscure OEM single-board computer based on the
156 Typhoon/Tsunami chipset family. Information on it is scanty.
161 DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
162 of the first-generation Alpha systems. A number of these systems
163 seem to be available on the second- hand market. The Jensen is a
164 floor-standing tower system which originally used a 150MHz 21064 It
165 used programmable logic to interface a 486 EISA I/O bridge to the
171 A technical overview of this board is available at
172 <http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html>.
177 The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a,
178 or 600au). There is an Installation HOWTO for this hardware at
179 <http://members.brabant.chello.nl/~s.vandereijk/miata.html>.
184 AlphaServer 1000-based Alpha systems.
186 config ALPHA_NAUTILUS
189 Alpha systems based on the AMD 751 & ALI 1543C chipsets.
191 config ALPHA_NONAME_CH
194 config ALPHA_NORITAKE
197 AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based
209 AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines.
211 <http://www.alphalinux.org/docs/rawhide/4100_install.shtml>.
216 Samsung APC164UX. There is a page on known problems and workarounds
217 at <http://www.alphalinux.org/faq/FAQ-11.html>.
228 Digital AlphaServer 2000 and 2100-based systems.
236 Alpha 11164-based OEM single-board computer.
241 config ALPHA_WILDFIRE
244 AlphaServer GS 40/80/160/320 SMP based on the EV67 core.
248 # clear all implied options (don't want default values for those):
249 # Most of these machines have ISA slots; not exactly sure which don't,
250 # and this doesn't activate hordes of code, so do it always.
255 Find out whether you have ISA slots on your motherboard. ISA is the
256 name of a bus system, i.e. the way the CPU talks to the other stuff
257 inside your box. Other bus systems are PCI, EISA, MicroChannel
258 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
259 newer boards don't support it. If you have ISA, say Y, otherwise N.
265 The Extended Industry Standard Architecture (EISA) bus was
266 developed as an open alternative to the IBM MicroChannel bus.
268 The EISA bus provided some of the features of the IBM MicroChannel
269 bus while maintaining backward compatibility with cards made for
270 the older ISA bus. The EISA bus saw limited use between 1988 and
271 1995 when it was made obsolete by the PCI bus.
273 Say Y here if you are building a kernel for an EISA-based machine.
283 MicroChannel Architecture is found in some IBM PS/2 machines and
284 laptops. It is a bus system similar to PCI or ISA. See
285 <file:Documentation/mca.txt> (and especially the web page given
286 there) before attempting to build an MCA bus kernel.
290 depends on !ALPHA_JENSEN
293 Find out whether you have a PCI motherboard. PCI is the name of a
294 bus system, i.e. the way the CPU talks to the other stuff inside
295 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
296 VESA. If you have PCI, say Y, otherwise N.
298 The PCI-HOWTO, available from
299 <http://www.linuxdoc.org/docs.html#howto>, contains valuable
300 information about which PCI hardware does work under Linux and which
305 depends on ALPHA_BOOK1 || ALPHA_NONAME_CH
308 The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia
309 UDB). This design was produced by Digital's Technical OEM (TOEM)
310 group. It uses the 21066 processor running at 166MHz or 233MHz. It
311 is a baby-AT size, and runs from a standard PC power supply. It has
312 5 ISA slots and 3 PCI slots (one pair are a shared slot). There are
313 2 versions, with either PS/2 or large DIN connectors for the
318 depends on ALPHA_JENSEN || ALPHA_SABLE && !ALPHA_GAMMA || ALPHA_NORITAKE && !ALPHA_PRIMO || ALPHA_MIKASA && !ALPHA_PRIMO || ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P_CH || ALPHA_XL || ALPHA_NONAME || ALPHA_EB66 || ALPHA_EB66P || ALPHA_P2K
323 depends on ALPHA_NONAME || ALPHA_EB66 || ALPHA_EB66P || ALPHA_P2K
328 depends on !ALPHA_PRIMO && (ALPHA_NORITAKE || ALPHA_MIKASA) || ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P_CH || ALPHA_XL
333 depends on ALPHA_CABRIOLET || ALPHA_EB64P_CH
336 Uses 21064 or 21064A and APECs. Has ISA and PCI expansion (3 ISA,
337 2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
338 ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI
339 (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),
340 SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM. PC-AT size.
341 Runs from standard PC power supply.
345 depends on ALPHA_RX164 || ALPHA_RAWHIDE || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN || ALPHA_SABLE && ALPHA_GAMMA || ALPHA_NORITAKE && ALPHA_PRIMO || ALPHA_MIKASA && ALPHA_PRIMO || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR
350 depends on ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN || ALPHA_NORITAKE && ALPHA_PRIMO || ALPHA_MIKASA && ALPHA_PRIMO || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR
354 bool "EV56 CPU (speed >= 366MHz)?" if ALPHA_ALCOR
355 default y if ALPHA_RX164 || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN || ALPHA_PC164 || ALPHA_TAKARA
358 prompt "EV56 CPU (speed >= 333MHz)?"
359 depends on ALPHA_NORITAKE && ALPHA_PRIMO
362 prompt "EV56 CPU (speed >= 400MHz)?"
363 depends on ALPHA_RAWHIDE
366 bool "EV5 CPU daughtercard (model 5/xxx)?"
367 depends on ALPHA_NORITAKE || ALPHA_MIKASA
369 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
372 bool "EV5 CPU(s) (model 5/xxx)?"
373 depends on ALPHA_SABLE
375 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
379 depends on ALPHA_SABLE
384 depends on ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN
389 depends on ALPHA_NAUTILUS || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK || ALPHA_DP264 || ALPHA_EIGER
394 depends on ALPHA_SHARK || ALPHA_DP264 || ALPHA_EIGER
398 bool "EV67 (or later) CPU (speed > 600MHz)?" if ALPHA_DP264 || ALPHA_EIGER
399 default y if ALPHA_NAUTILUS || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK
401 Is this a machine based on the EV67 core? If in doubt, select N here
402 and the machine will be treated as an EV6.
406 depends on ALPHA_RAWHIDE
411 depends on ALPHA_RX164
414 config ALPHA_IRONGATE
416 depends on ALPHA_NAUTILUS
420 bool "Use SRM as bootloader" if ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_NAUTILUS || ALPHA_NONAME
421 default y if ALPHA_JENSEN || ALPHA_MIKASA || ALPHA_SABLE || ALPHA_NORITAKE || ALPHA_DP264 || ALPHA_RAWHIDE || ALPHA_EIGER || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK
423 There are two different types of booting firmware on Alphas: SRM,
424 which is command line driven, and ARC, which uses menus and arrow
425 keys. Details about the Linux/Alpha booting process are contained in
426 the Linux/Alpha FAQ, accessible on the WWW from
427 <http://www.alphalinux.org/>.
429 The usual way to load Linux on an Alpha machine is to use MILO
430 (a bootloader that lets you pass command line parameters to the
431 kernel just like lilo does for the x86 architecture) which can be
432 loaded either from ARC or can be installed directly as a permanent
433 firmware replacement from floppy (which requires changing a certain
434 jumper on the motherboard). If you want to do either of these, say N
435 here. If MILO doesn't work on your system (true for Jensen
436 motherboards), you can bypass it altogether and boot Linux directly
437 from an SRM console; say Y here in order to do that. Note that you
438 won't be able to boot from an IDE disk using SRM.
444 depends on ALPHA_ALCOR || ALPHA_MIKASA || ALPHA_SABLE || ALPHA_NORITAKE || ALPHA_RAWHIDE
449 depends on ALPHA_XL || ALPHA_AVANTI_CH
452 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based
454 <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.
456 config ALPHA_BROKEN_IRQ_MASK
458 depends on ALPHA_GENERIC || ALPHA_PC164
462 bool "Symmetric multi-processing support"
463 depends on ALPHA_SABLE || ALPHA_RAWHIDE || ALPHA_DP264 || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_GENERIC || ALPHA_SHARK
465 This enables support for systems with more than one CPU. If you have
466 a system with only one CPU, like most personal computers, say N. If
467 you have a system with more than one CPU, say Y.
469 If you say N here, the kernel will run on single and multiprocessor
470 machines, but will use only one CPU of a multiprocessor machine. If
471 you say Y here, the kernel will run on many, but not all,
472 singleprocessor machines. On a singleprocessor machine, the kernel
473 will run faster if you say N here.
475 Note that if you say Y here and choose architecture "586" or
476 "Pentium" under "Processor family", the kernel will not work on 486
477 architectures. Similarly, multiprocessor kernels for the "PPro"
478 architecture may not work on all Pentium based boards.
480 People using multiprocessor machines who say Y here should also say
481 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
482 Management" code will be disabled if you say Y here.
484 See also the <file:Documentation/smp.tex>,
485 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
486 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
487 <http://www.linuxdoc.org/docs.html#howto>.
489 If you don't know what to do here, say N.
497 int "Maximum number of CPUs (2-64)"
502 bool "Discontiguous Memory Support (EXPERIMENTAL)"
503 depends on EXPERIMENTAL
505 Say Y to upport efficient handling of discontiguous physical memory,
506 for architectures which are either NUMA (Non-Uniform Memory Access)
507 or have huge holes in the physical address space for other reasons.
508 See <file:Documentation/vm/numa> for more.
511 bool "NUMA Support (EXPERIMENTAL)"
512 depends on DISCONTIGMEM
514 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
515 Access). This option is for configuring high-end multiprocessor
516 server machines. If in doubt, say N.
518 # LARGE_VMALLOC is racy, if you *really* need it then fix it first
519 config ALPHA_LARGE_VMALLOC
522 Process creation and other aspects of virtual memory management can
523 be streamlined if we restrict the kernel to one PGD for all vmalloc
524 allocations. This equates to about 8GB.
526 Under normal circumstances, this is so far and above what is needed
527 as to be laughable. However, there are certain applications (such
528 as benchmark-grade in-kernel web serving) that can make use of as
529 much vmalloc space as is available.
531 Say N unless you know you need gobs and gobs of vmalloc space.
533 config VERBOSE_MCHECK
534 bool "Verbose Machine Checks"
536 source "drivers/pci/Kconfig"
539 bool "Support for hot-pluggable devices"
541 Say Y here if you want to plug devices into your computer while
542 the system is running, and be able to use them quickly. In many
543 cases, the devices can likewise be unplugged at any time too.
545 One well known example of this is PCMCIA- or PC-cards, credit-card
546 size devices such as network cards, modems or hard drives which are
547 plugged into slots found on all modern laptop computers. Another
548 example, used on modern desktops as well as laptops, is USB.
550 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
551 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
552 Then your kernel will automatically call out to a user mode "policy
553 agent" (/sbin/hotplug) to load modules and set up software needed
554 to use devices as you hotplug them.
556 source "drivers/pcmcia/Kconfig"
559 prompt "Kernel core (/proc/kcore) format"
566 If you enabled support for /proc file system then the file
567 /proc/kcore will contain the kernel core image. This can be used
570 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
572 You have two choices here: ELF and A.OUT. Selecting ELF will make
573 /proc/kcore appear in ELF core format as defined by the Executable
574 and Linking Format specification. Selecting A.OUT will choose the
575 old "a.out" format which may be necessary for some old versions
576 of binutils or on some architectures.
578 This is especially useful if you have compiled the kernel with the
579 "-g" option to preserve debugging information. It is mainly used
580 for examining kernel data structures on the live kernel so if you
581 don't understand what this means or are not a kernel hacker, just
582 leave it at its default value ELF.
587 Not necessary unless you're using a very out-of-date binutils
588 version. You probably want KCORE_ELF.
593 tristate "SRM environment through procfs"
596 If you enable this option, a subdirectory inside /proc called
597 /proc/srm_environment will give you access to the all important
598 SRM environment variables (those which have a name) and also
599 to all others (by their internal number).
601 SRM is something like a BIOS for Alpha machines. There are some
602 other such BIOSes, like AlphaBIOS, which this driver cannot
603 support (hey, that's not SRM!).
605 Despite the fact that this driver doesn't work on all Alphas (but
606 only on those which have SRM as their firmware), it's save to
607 build it even if your particular machine doesn't know about SRM
608 (or if you intend to compile a generic kernel). It will simply
609 not create those subdirectory in /proc (and give you some warning,
612 This driver is also available as a module and will be called
616 tristate "Kernel support for a.out (ECOFF) binaries"
618 A.out (Assembler.OUTput) is a set of formats for libraries and
619 executables used in the earliest versions of UNIX. Linux used the
620 a.out formats QMAGIC and ZMAGIC until they were replaced with the
623 As more and more programs are converted to ELF, the use for a.out
624 will gradually diminish. If you disable this option it will reduce
625 your kernel by one page. This is not much and by itself does not
626 warrant removing support. However its removal is a good idea if you
627 wish to ensure that absolutely none of your programs will use this
628 older executable format. If you don't know what to answer at this
629 point then answer Y. If someone told you "You need a kernel with
630 QMAGIC support" then you'll have to say Y here. You may answer M to
631 compile a.out support as a module and later load the module when you
632 want to use a program or library in a.out format. The module will be
633 called binfmt_aout.o. Saying M or N here is dangerous though,
634 because some crucial programs on your system might still be in A.OUT
638 bool "OSF/1 v4 readv/writev compatibility"
639 depends on BINFMT_AOUT
641 Say Y if you are using OSF/1 binaries (like Netscape and Acrobat)
642 with v4 shared libraries freely available from Compaq. If you're
643 going to use shared libraries from Tru64 version 5.0 or later, say N.
646 tristate "Kernel support for ELF binaries"
648 ELF (Executable and Linkable Format) is a format for libraries and
649 executables used across different architectures and operating
650 systems. Saying Y here will enable your kernel to run ELF binaries
651 and enlarge it by about 13 KB. ELF support under Linux has now all
652 but replaced the traditional Linux a.out formats (QMAGIC and ZMAGIC)
653 because it is portable (this does *not* mean that you will be able
654 to run executables from different architectures or operating systems
655 however) and makes building run-time libraries very easy. Many new
656 executables are distributed solely in ELF format. You definitely
659 Information about ELF is contained in the ELF HOWTO available from
660 <http://www.linuxdoc.org/docs.html#howto>.
662 If you find that after upgrading from Linux kernel 1.2 and saying Y
663 here, you still can't run any ELF binaries (they just crash), then
664 you'll have to install the newest ELF runtime libraries, including
665 ld.so (check the file <file:Documentation/Changes> for location and
668 If you want to compile this as a module ( = code which can be
669 inserted in and removed from the running kernel whenever you want),
670 say M here and read <file:Documentation/modules.txt>. The module
671 will be called binfmt_elf.o. Saying M or N here is dangerous because
672 some crucial programs on your system might be in ELF format.
675 tristate "Kernel support for MISC binaries"
677 If you say Y here, it will be possible to plug wrapper-driven binary
678 formats into the kernel. You will like this especially when you use
679 programs that need an interpreter to run like Java, Python or
680 Emacs-Lisp. It's also useful if you often run DOS executables under
681 the Linux DOS emulator DOSEMU (read the DOSEMU-HOWTO, available from
682 <http://www.linuxdoc.org/docs.html#howto>). Once you have
683 registered such a binary class with the kernel, you can start one of
684 those programs simply by typing in its name at a shell prompt; Linux
685 will automatically feed it to the correct interpreter.
687 You can do other nice things, too. Read the file
688 <file:Documentation/binfmt_misc.txt> to learn how to use this
689 feature, and <file:Documentation/java.txt> for information about how
690 to include Java support.
692 You must say Y to "/proc file system support" (CONFIG_PROC_FS) to
693 use this part of the kernel.
695 You may say M here for module support and later load the module when
696 you have use for it; the module is called binfmt_misc.o. If you
697 don't know what to answer at this point, say Y.
700 tristate "Kernel support for Linux/Intel ELF binaries"
702 Say Y here if you want to be able to execute Linux/Intel ELF
703 binaries just like native Alpha binaries on your Alpha machine. For
704 this to work, you need to have the emulator /usr/bin/em86 in place.
706 You can get the same functionality by saying N here and saying Y to
707 "Kernel support for MISC binaries".
709 You may answer M to compile the emulation support as a module and
710 later load the module when you want to use a Linux/Intel binary. The
711 module will be called binfmt_em86.o. If unsure, say Y.
713 source "drivers/parport/Kconfig"
717 source "drivers/mtd/Kconfig"
719 source "drivers/pnp/Kconfig"
721 source "drivers/block/Kconfig"
723 source "drivers/md/Kconfig"
726 menu "ATA/ATAPI/MFM/RLL support"
729 tristate "ATA/ATAPI/MFM/RLL support"
731 If you say Y here, your kernel will be able to manage low cost mass
732 storage units such as ATA/(E)IDE and ATAPI units. The most common
733 cases are IDE hard drives and ATAPI CD-ROM drives.
735 If your system is pure SCSI and doesn't use these interfaces, you
738 Integrated Disk Electronics (IDE aka ATA-1) is a connecting standard
739 for mass storage units such as hard disks. It was designed by
740 Western Digital and Compaq Computer in 1984. It was then named
741 ST506. Quite a number of disks use the IDE interface.
743 AT Attachment (ATA) is the superset of the IDE specifications.
744 ST506 was also called ATA-1.
746 Fast-IDE is ATA-2 (also named Fast ATA), Enhanced IDE (EIDE) is
747 ATA-3. It provides support for larger disks (up to 8.4GB by means of
748 the LBA standard), more disks (4 instead of 2) and for other mass
749 storage units such as tapes and cdrom. UDMA/33 (aka UltraDMA/33) is
750 ATA-4 and provides faster (and more CPU friendly) transfer modes
751 than previous PIO (Programmed processor Input/Output) from previous
752 ATA/IDE standards by means of fast DMA controllers.
754 ATA Packet Interface (ATAPI) is a protocol used by EIDE tape and
755 CD-ROM drives, similar in many respects to the SCSI protocol.
757 SMART IDE (Self Monitoring, Analysis and Reporting Technology) was
758 designed in order to prevent data corruption and disk crash by
759 detecting pre hardware failure conditions (heat, access time, and
760 the like...). Disks built since June 1995 may follow this standard.
761 The kernel itself don't manage this; however there are quite a
762 number of user programs such as smart that can query the status of
763 SMART parameters disk.
765 If you want to compile this driver as a module ( = code which can be
766 inserted in and removed from the running kernel whenever you want),
767 say M here and read <file:Documentation/modules.txt>. The module
768 will be called ide.o.
770 For further information, please read <file:Documentation/ide.txt>.
774 source "drivers/ide/Kconfig"
782 tristate "SCSI support"
784 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
785 any other SCSI device under Linux, say Y and make sure that you know
786 the name of your SCSI host adapter (the card inside your computer
787 that "speaks" the SCSI protocol, also called SCSI controller),
788 because you will be asked for it.
790 You also need to say Y here if you want support for the parallel
791 port version of the 100 MB IOMEGA ZIP drive.
793 This driver is also available as a module ( = code which can be
794 inserted in and removed from the running kernel whenever you want).
795 The module will be called scsi_mod.o. If you want to compile it as
796 a module, say M here and read <file:Documentation/modules.txt> and
797 <file:Documentation/scsi/scsi.txt>. However, do not compile this as a
798 module if your root file system (the one containing the directory /)
799 is located on a SCSI device.
801 source "drivers/scsi/Kconfig"
806 source "drivers/message/fusion/Kconfig"
812 menu "Network device support"
816 bool "Network device support"
818 You can say N here if you don't intend to connect your Linux box to
819 any other computer at all or if all your connections will be over a
820 telephone line with a modem either via UUCP (UUCP is a protocol to
821 forward mail and news between unix hosts over telephone lines; read
822 the UUCP-HOWTO, available from
823 <http://www.linuxdoc.org/docs.html#howto>) or dialing up a shell
824 account or a BBS, even using term (term is a program which gives you
825 almost full Internet connectivity if you have a regular dial up
826 shell account on some Internet connected Unix computer. Read
827 <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>).
829 You'll have to say Y if your computer contains a network card that
830 you want to use under Linux (make sure you know its name because you
831 will be asked for it and read the Ethernet-HOWTO (especially if you
832 plan to use more than one network card under Linux)) or if you want
833 to use SLIP (Serial Line Internet Protocol is the protocol used to
834 send Internet traffic over telephone lines or null modem cables) or
835 CSLIP (compressed SLIP) or PPP (Point to Point Protocol, a better
836 and newer replacement for SLIP) or PLIP (Parallel Line Internet
837 Protocol is mainly used to create a mini network by connecting the
838 parallel ports of two local machines) or AX.25/KISS (protocol for
839 sending Internet traffic over amateur radio links).
841 Make sure to read the NET-3-HOWTO. Eventually, you will have to read
842 Olaf Kirch's excellent and free book "Network Administrator's
843 Guide", to be found in <http://www.linuxdoc.org/docs.html#guide>. If
846 source "drivers/net/Kconfig"
848 source "drivers/atm/Kconfig"
852 source "net/ax25/Kconfig"
854 source "drivers/isdn/Kconfig"
857 menu "Old CD-ROM drivers (not SCSI, not IDE)"
860 bool "Support non-SCSI/IDE/ATAPI CDROM drives"
862 If you have a CD-ROM drive that is neither SCSI nor IDE/ATAPI, say Y
863 here, otherwise N. Read the CD-ROM-HOWTO, available from
864 <http://www.linuxdoc.org/docs.html#howto>.
866 Note that the answer to this question doesn't directly affect the
867 kernel: saying N will just cause the configurator to skip all
868 the questions about these CD-ROM drives. If you are unsure what you
869 have, say Y and find out whether you have one of the following
872 For each of these drivers, a file Documentation/cdrom/{driver_name}
873 exists. Especially in cases where you do not know exactly which kind
874 of drive you have you should read there. Most of these drivers use a
875 file drivers/cdrom/{driver_name}.h where you can define your
876 interface parameters and switch some internal goodies.
878 All these CD-ROM drivers are also usable as a module ( = code which
879 can be inserted in and removed from the running kernel whenever you
880 want). If you want to compile them as module, say M instead of Y and
881 read <file:Documentation/modules.txt>.
883 If you want to use any of these CD-ROM drivers, you also have to
884 answer Y or M to "ISO 9660 CD-ROM file system support" below (this
885 answer will get "defaulted" for you if you enable any of the Linux
888 source "drivers/cdrom/Kconfig"
892 source "drivers/input/Kconfig"
894 source "drivers/char/Kconfig"
896 #source drivers/misc/Config.in
897 source "drivers/media/Kconfig"
902 menu "Console drivers"
906 bool "VGA text console"
908 Saying Y here will allow you to use Linux in text mode through a
909 display that complies with the generic VGA standard. Virtually
912 The program SVGATextMode can be used to utilize SVGA video cards to
913 their full potential in text mode. Download it from
914 <ftp://ibiblio.org/pub/Linux/utils/console/>.
918 # if [ "$CONFIG_PCI" = "y" -a "$CONFIG_VGA_CONSOLE" = "y" ]; then
919 # bool ' Allow VGA on any bus?' CONFIG_VGA_HOSE
920 # if [ "$CONFIG_VGA_HOSE" = "y" ]; then
921 # define_bool CONFIG_DUMMY_CONSOLE y
924 source "drivers/video/Kconfig"
937 tristate "Sound card support"
939 If you have a sound card in your computer, i.e. if it can say more
940 than an occasional beep, say Y. Be sure to have all the information
941 about your sound card and its configuration down (I/O port,
942 interrupt and DMA channel), because you will be asked for it.
944 You want to read the Sound-HOWTO, available from
945 <http://www.linuxdoc.org/docs.html#howto>. General information about
946 the modular sound system is contained in the files
947 <file:Documentation/sound/Introduction>. The file
948 <file:Documentation/sound/README.OSS> contains some slightly
949 outdated but still useful information as well.
951 If you have a PnP sound card and you want to configure it at boot
952 time using the ISA PnP tools (read
953 <http://www.roestock.demon.co.uk/isapnptools/>), then you need to
954 compile the sound card support as a module ( = code which can be
955 inserted in and removed from the running kernel whenever you want)
956 and load that module after the PnP configuration is finished. To do
957 this, say M here and read <file:Documentation/modules.txt> as well
958 as <file:Documentation/sound/README.modules>; the module will be
961 I'm told that even without a sound card, you can make your computer
962 say more than an occasional beep, by programming the PC speaker.
963 Kernel patches and supporting utilities to do that are in the pcsp
964 package, available at <ftp://ftp.infradead.org/pub/pcsp/>.
966 source "sound/Kconfig"
970 source "drivers/usb/Kconfig"
972 source "net/bluetooth/Kconfig"
975 menu "Kernel hacking"
977 config ALPHA_LEGACY_START_ADDRESS
978 bool "Legacy kernel start address"
980 The 2.4 kernel changed the kernel start address from 0x310000
981 to 0x810000 to make room for the Wildfire's larger SRM console.
983 If you're using aboot 0.7 or later, the bootloader will examine the
984 ELF headers to determine where to transfer control. Unfortunately,
985 most older bootloaders -- APB or MILO -- hardcoded the kernel start
986 address rather than examining the ELF headers, and the result is a
989 Say Y if you have a broken bootloader. Say N if you do not, or if
990 you wish to run on Wildfire.
993 bool "Kernel debugging"
995 Say Y here if you are developing drivers or trying to debug and
996 identify kernel problems.
999 tristate "Kernel FP software completion" if DEBUG_KERNEL
1000 default y if !DEBUG_KERNEL
1002 This option is required for IEEE compliant floating point arithmetic
1003 on the Alpha. The only time you would ever not say Y is to say M in
1004 order to debug the code. Say Y unless you know what you are doing.
1007 bool "Debug memory allocations"
1008 depends on DEBUG_KERNEL
1010 Say Y here to have the kernel do limited verification on memory
1011 allocation as well as poisoning memory on free to catch use of freed
1015 bool "Magic SysRq key"
1016 depends on DEBUG_KERNEL
1018 If you say Y here, you will have some control over the system even
1019 if the system crashes for example during kernel debugging (e.g., you
1020 will be able to flush the buffer cache to disk, reboot the system
1021 immediately or dump some status information). This is accomplished
1022 by pressing various keys while holding SysRq (Alt+PrintScreen). It
1023 also works on a serial console (on PC hardware at least), if you
1024 send a BREAK and then within 5 seconds a command keypress. The
1025 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
1026 unless you really know what this hack does.
1028 config DEBUG_SPINLOCK
1029 bool "Spinlock debugging"
1030 depends on DEBUG_KERNEL
1032 Say Y here and build SMP to catch missing spinlock initialization
1033 and certain other kinds of spinlock errors commonly made. This is
1034 best used in conjunction with the NMI watchdog so that spinlock
1035 deadlocks are also debuggable.
1038 bool "Read-write spinlock debugging"
1039 depends on DEBUG_KERNEL
1041 If you say Y here then read-write lock processing will count how many
1042 times it has tried to get the lock and issue an error message after
1043 too many attempts. If you suspect a rwlock problem or a kernel
1044 hacker asks for this option then say Y. Otherwise say N.
1046 config DEBUG_SEMAPHORE
1047 bool "Semaphore debugging"
1048 depends on DEBUG_KERNEL
1050 If you say Y here then semaphore processing will issue lots of
1051 verbose debugging messages. If you suspect a semaphore problem or a
1052 kernel hacker asks for this option then say Y. Otherwise say N.
1056 source "security/Kconfig"
1058 source "crypto/Kconfig"
1060 source "lib/Kconfig"