1 # $Id: config.in,v 1.158 2002/01/24 22:14:44 davem Exp $
2 # For a description of the syntax of this configuration file,
3 # see the Configure script.
6 mainmenu "Linux/UltraSPARC Kernel Configuration"
15 config TIME_INTERPOLATION
21 menu "General machine setup"
24 tristate "UltraSPARC-III bootbus i2c controller driver"
27 The BBC devices on the UltraSPARC III have two I2C controllers. The
28 first I2C controller connects mainly to configuration PROMs (NVRAM,
29 CPU configuration, DIMM types, etc.). The second I2C controller
30 connects to environmental control devices such as fans and
31 temperature sensors. The second controller also connects to the
32 smartcard reader, if present. Say Y to enable support for these.
35 bool "Virtual terminal" if EMBEDDED
39 If you say Y here, you will get support for terminal devices with
40 display and keyboard devices. These are called "virtual" because you
41 can run several virtual terminals (also called virtual consoles) on
42 one physical terminal. This is rather useful, for example one
43 virtual terminal can collect system messages and warnings, another
44 one can be used for a text-mode user session, and a third could run
45 an X session, all in parallel. Switching between virtual terminals
46 is done with certain key combinations, usually Alt-<function key>.
48 The setterm command ("man setterm") can be used to change the
49 properties (such as colors or beeping) of a virtual terminal. The
50 man page console_codes(4) ("man console_codes") contains the special
51 character sequences that can be used to change those properties
52 directly. The fonts used on virtual terminals can be changed with
53 the setfont ("man setfont") command and the key bindings are defined
54 with the loadkeys ("man loadkeys") command.
56 You need at least one virtual terminal device in order to make use
57 of your keyboard and monitor. Therefore, only people configuring an
58 embedded system would want to say N here in order to save some
59 memory; the only way to log into such a system is then via a serial
60 or network connection.
62 If unsure, say Y, or else you won't be able to do much with your new
63 shiny Linux system :-)
66 bool "Support for console on virtual terminal" if EMBEDDED
70 The system console is the device which receives all kernel messages
71 and warnings and which allows logins in single user mode. If you
72 answer Y here, a virtual terminal (the device used to interact with
73 a physical terminal) can be used as system console. This is the most
74 common mode of operations, so you should say Y here unless you want
75 the kernel messages be output only to a serial port (in which case
76 you should say Y to "Console on serial port", below).
78 If you do say Y here, by default the currently visible virtual
79 terminal (/dev/tty0) will be used as system console. You can change
80 that with a kernel command line option such as "console=tty3" which
81 would use the third virtual terminal as system console. (Try "man
82 bootparam" or see the documentation of your boot loader (lilo or
83 loadlin) about how to pass options to the kernel at boot time.)
92 bool "Symmetric multi-processing support"
94 This enables support for systems with more than one CPU. If you have
95 a system with only one CPU, like most personal computers, say N. If
96 you have a system with more than one CPU, say Y.
98 If you say N here, the kernel will run on single and multiprocessor
99 machines, but will use only one CPU of a multiprocessor machine. If
100 you say Y here, the kernel will run on many, but not all,
101 singleprocessor machines. On a singleprocessor machine, the kernel
102 will run faster if you say N here.
104 Note that if you say Y here and choose architecture "586" or
105 "Pentium" under "Processor family", the kernel will not work on 486
106 architectures. Similarly, multiprocessor kernels for the "PPro"
107 architecture may not work on all Pentium based boards.
109 People using multiprocessor machines who say Y here should also say
110 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
111 Management" code will be disabled if you say Y here.
113 See also the <file:Documentation/smp.txt>,
114 <file:Documentation/i386/IO-APIC.txt>,
115 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
116 <http://www.tldp.org/docs.html#howto>.
118 If you don't know what to do here, say N.
121 bool "Preemptible Kernel"
123 This option reduces the latency of the kernel when reacting to
124 real-time or interactive events by allowing a low priority process to
125 be preempted even if it is in kernel mode executing a system call.
126 This allows applications to run more reliably even when the system is
129 Say Y here if you are building a kernel for a desktop, embedded
130 or real-time system. Say N if you are unsure.
133 int "Maximum number of CPUs (2-64)"
138 source "drivers/cpufreq/Kconfig"
140 config CPU_FREQ_TABLE
141 tristate "CPU frequency table helpers"
145 Many CPUFreq drivers use these helpers, so only say N here if
146 the CPUFreq driver of your choice doesn't need these helpers.
151 tristate "UltraSPARC-III CPU Frequency driver"
152 depends on CPU_FREQ_TABLE
154 This adds the CPUFreq driver for UltraSPARC-III processors.
156 For details, take a look at <file:Documentation/cpu-freq>.
161 tristate "UltraSPARC-IIe CPU Frequency driver"
162 depends on CPU_FREQ_TABLE
164 This adds the CPUFreq driver for UltraSPARC-IIe processors.
166 For details, take a look at <file:Documentation/cpu-freq>.
170 # Identify this as a Sparc64 build
175 SPARC is a family of RISC microprocessors designed and marketed by
176 Sun Microsystems, incorporated. This port covers the newer 64-bit
177 UltraSPARC. The UltraLinux project maintains both the SPARC32 and
178 SPARC64 ports; its web page is available at
179 <http://www.ultralinux.org/>.
181 # Global things across all Sun machines.
182 config RWSEM_GENERIC_SPINLOCK
185 config RWSEM_XCHGADD_ALGORITHM
190 prompt "SPARC64 Huge TLB Page Size"
191 depends on HUGETLB_PAGE
192 default HUGETLB_PAGE_SIZE_4MB
194 config HUGETLB_PAGE_SIZE_4MB
197 config HUGETLB_PAGE_SIZE_512K
200 config HUGETLB_PAGE_SIZE_64K
205 config GENERIC_ISA_DMA
212 Find out whether you have ISA slots on your motherboard. ISA is the
213 name of a bus system, i.e. the way the CPU talks to the other stuff
214 inside your box. Other bus systems are PCI, EISA, MicroChannel
215 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
216 newer boards don't support it. If you have ISA, say Y, otherwise N.
221 Say Y here if you would like support for ISA Plug and Play devices.
222 Some information is in <file:Documentation/isapnp.txt>.
224 To compile this driver as a module, choose M here: the
225 module will be called isapnp.
232 The Extended Industry Standard Architecture (EISA) bus was
233 developed as an open alternative to the IBM MicroChannel bus.
235 The EISA bus provided some of the features of the IBM MicroChannel
236 bus while maintaining backward compatibility with cards made for
237 the older ISA bus. The EISA bus saw limited use between 1988 and
238 1995 when it was made obsolete by the PCI bus.
240 Say Y here if you are building a kernel for an EISA-based machine.
247 MicroChannel Architecture is found in some IBM PS/2 machines and
248 laptops. It is a bus system similar to PCI or ISA. See
249 <file:Documentation/mca.txt> (and especially the web page given
250 there) before attempting to build an MCA bus kernel.
255 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
256 computer. These are credit-card size devices such as network cards,
257 modems or hard drives often used with laptops computers. There are
258 actually two varieties of these cards: the older 16 bit PCMCIA cards
259 and the newer 32 bit CardBus cards. If you want to use CardBus
260 cards, you need to say Y here and also to "CardBus support" below.
262 To use your PC-cards, you will need supporting software from David
263 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
264 for location). Please also read the PCMCIA-HOWTO, available from
265 <http://www.tldp.org/docs.html#howto>.
267 To compile this driver as modules, choose M here: the
268 modules will be called pcmcia_core and ds.
289 Find out whether you have a PCI motherboard. PCI is the name of a
290 bus system, i.e. the way the CPU talks to the other stuff inside
291 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
292 VESA. If you have PCI, say Y, otherwise N.
294 The PCI-HOWTO, available from
295 <http://www.tldp.org/docs.html#howto>, contains valuable
296 information about which PCI hardware does work under Linux and which
308 If you say Y here and create a character special file /dev/rtc with
309 major number 10 and minor number 135 using mknod ("man mknod"), you
310 will get access to the real time clock (or hardware clock) built
313 Every PC has such a clock built in. It can be used to generate
314 signals from as low as 1Hz up to 8192Hz, and can also be used
315 as a 24 hour alarm. It reports status information via the file
316 /proc/driver/rtc and its behaviour is set by various ioctls on
319 If you run Linux on a multiprocessor machine and said Y to
320 "Symmetric Multi Processing" above, you should say Y here to read
321 and set the RTC in an SMP compatible fashion.
323 If you think you have a use for such a device (such as periodic data
324 sampling), then say Y here, and read <file:Documentation/rtc.txt>
327 To compile this driver as a module, choose M here: the
328 module will be called rtc.
330 source "drivers/pci/Kconfig"
332 config SUN_OPENPROMFS
333 tristate "Openprom tree appears in /proc/openprom"
335 If you say Y, the OpenPROM device tree will be available as a
336 virtual file system, which you can mount to /proc/openprom by "mount
337 -t openpromfs none /proc/openprom".
339 To compile the /proc/openprom support as a module, choose M here: the
340 module will be called openpromfs. If unsure, choose M.
342 config SPARC32_COMPAT
343 bool "Kernel support for Linux/Sparc 32bit binary compatibility"
345 This allows you to run 32-bit binaries on your Ultra.
346 Everybody wants this; say Y.
350 depends on SPARC32_COMPAT
355 depends on SPARC32_COMPAT
359 tristate "Kernel support for 32-bit ELF binaries"
360 depends on SPARC32_COMPAT
362 This allows you to run 32-bit Linux/ELF binaries on your Ultra.
363 Everybody wants this; say Y.
366 bool "Kernel support for 32-bit (ie. SunOS) a.out binaries"
367 depends on SPARC32_COMPAT
369 This allows you to run 32-bit a.out format binaries on your Ultra.
370 If you want to run SunOS binaries (see SunOS binary emulation below)
371 or other a.out binaries, say Y. If unsure, say N.
373 source "fs/Kconfig.binfmt"
376 bool "SunOS binary emulation"
377 depends on BINFMT_AOUT32
379 This allows you to run most SunOS binaries. If you want to do this,
380 say Y here and place appropriate files in /usr/gnemul/sunos. See
381 <http://www.ultralinux.org/faq.html> for more information. If you
382 want to run SunOS binaries on an Ultra you must also say Y to
383 "Kernel support for 32-bit a.out binaries" above.
386 tristate "Solaris binary emulation (EXPERIMENTAL)"
387 depends on SPARC32_COMPAT && EXPERIMENTAL
389 This is experimental code which will enable you to run (many)
390 Solaris binaries on your SPARC Linux machine.
392 To compile this code as a module, choose M here: the
393 module will be called solaris.
395 source "drivers/parport/Kconfig"
398 tristate "Parallel printer support"
401 If you intend to attach a printer to the parallel port of your Linux
402 box (as opposed to using a serial printer; if the connector at the
403 printer has 9 or 25 holes ["female"], then it's serial), say Y.
404 Also read the Printing-HOWTO, available from
405 <http://www.tldp.org/docs.html#howto>.
407 It is possible to share one parallel port among several devices
408 (e.g. printer and ZIP drive) and it is safe to compile the
409 corresponding drivers into the kernel.
410 To compile this driver as a module, choose M here and read
411 <file:Documentation/parport.txt>. The module will be called lp.
413 If you have several parallel ports, you can specify which ports to
414 use with the "lp" kernel command line option. (Try "man bootparam"
415 or see the documentation of your boot loader (lilo or loadlin) about
416 how to pass options to the kernel at boot time.) The syntax of the
417 "lp" command line option can be found in <file:drivers/char/lp.c>.
419 If you have more than 8 printers, you need to increase the LP_NO
420 macro in lp.c and the PARPORT_MAX macro in parport.h.
423 tristate "SUNW, envctrl support"
426 Kernel support for temperature and fan monitoring on Sun SME
429 To compile this driver as a module, choose M here: the
430 module will be called envctrl.
433 tristate "7-Segment Display support"
436 This is the driver for the 7-segment display and LED present on
437 Sun Microsystems CompactPCI models CP1400 and CP1500.
439 To compile this driver as a module, choose M here: the
440 module will be called display7seg.
442 If you do not have a CompactPCI model CP1400 or CP1500, or
443 another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
444 you should say N to this option.
447 bool "Default bootloader kernel arguments"
450 string "Initial kernel command string"
451 depends on CMDLINE_BOOL
452 default "console=ttyS0,9600 root=/dev/sda1"
454 Say Y here if you want to be able to pass default arguments to
455 the kernel. This will be overridden by the bootloader, if you
456 use one (such as SILO). This is most useful if you want to boot
457 a kernel from TFTP, and want default options to be available
458 with having them passed on the command line.
460 NOTE: This option WILL override the PROM bootargs setting!
464 source "drivers/base/Kconfig"
466 source "drivers/video/Kconfig"
468 source "drivers/serial/Kconfig"
470 source "drivers/sbus/char/Kconfig"
472 source "drivers/mtd/Kconfig"
474 source "drivers/block/Kconfig"
476 source "drivers/ide/Kconfig"
478 source "drivers/scsi/Kconfig"
480 source "drivers/fc4/Kconfig"
482 source "drivers/md/Kconfig"
485 source "drivers/message/fusion/Kconfig"
488 source "drivers/ieee1394/Kconfig"
492 source "drivers/isdn/Kconfig"
494 source "drivers/telephony/Kconfig"
496 # This one must be before the filesystem configs. -DaveM
498 menu "Unix98 PTY support"
501 bool "Unix98 PTY support"
503 A pseudo terminal (PTY) is a software device consisting of two
504 halves: a master and a slave. The slave device behaves identical to
505 a physical terminal; the master device is used by a process to
506 read data from and write data to the slave, thereby emulating a
507 terminal. Typical programs for the master side are telnet servers
510 Linux has traditionally used the BSD-like names /dev/ptyxx for
511 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
512 has a number of problems. The GNU C library glibc 2.1 and later,
513 however, supports the Unix98 naming standard: in order to acquire a
514 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
515 terminal is then made available to the process and the pseudo
516 terminal slave can be accessed as /dev/pts/<number>. What was
517 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
519 The entries in /dev/pts/ are created on the fly by a virtual
520 file system; therefore, if you say Y here you should say Y to
521 "/dev/pts file system for Unix98 PTYs" as well.
523 If you want to say Y here, you need to have the C library glibc 2.1
524 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
525 Read the instructions in <file:Documentation/Changes> pertaining to
526 pseudo terminals. It's safe to say N.
528 config UNIX98_PTY_COUNT
529 int "Maximum number of Unix98 PTYs in use (0-2048)"
530 depends on UNIX98_PTYS
533 The maximum number of Unix98 PTYs that can be used at any one time.
534 The default is 256, and should be enough for desktop systems. Server
535 machines which support incoming telnet/rlogin/ssh connections and/or
536 serve several X terminals may want to increase this: every incoming
537 connection and every xterm uses up one PTY.
539 When not in use, each additional set of 256 PTYs occupy
540 approximately 8 KB of kernel memory on 32-bit architectures.
544 menu "XFree86 DRI support"
547 bool "Direct Rendering Manager (XFree86 DRI support)"
549 Kernel-level support for the Direct Rendering Infrastructure (DRI)
550 introduced in XFree86 4.0. If you say Y here, you need to select
551 the module that's right for your graphics card from the list below.
552 These modules provide support for synchronization, security, and
553 DMA transfers. Please see <http://dri.sourceforge.net/> for more
554 details. You should also select and configure AGP
555 (/dev/agpgart) support.
558 tristate "Creator/Creator3D"
561 Choose this option if you have one of Sun's Creator3D-based graphics
562 and frame buffer cards. Product page at
563 <http://www.sun.com/desktop/products/Graphics/creator3d.html>.
566 tristate "3dfx Banshee/Voodoo3+"
569 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
570 graphics card. If M is selected, the module will be called tdfx.
573 tristate "ATI Rage 128"
576 Choose this option if you have an ATI Rage 128 graphics card. If M
577 is selected, the module will be called r128. AGP support for
578 this card is strongly suggested (unless you have a PCI version).
582 source "drivers/input/Kconfig"
584 source "drivers/i2c/Kconfig"
588 source "drivers/media/Kconfig"
590 source "sound/Kconfig"
592 source "drivers/usb/Kconfig"
594 source "drivers/char/watchdog/Kconfig"
596 source "arch/sparc64/oprofile/Kconfig"
598 source "arch/sparc64/Kconfig.debug"
600 source "kernel/vserver/Kconfig"
602 source "security/Kconfig"
604 source "crypto/Kconfig"