1da177e4c3
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
631 lines
19 KiB
Plaintext
631 lines
19 KiB
Plaintext
# $Id: config.in,v 1.158 2002/01/24 22:14:44 davem Exp $
|
|
# For a description of the syntax of this configuration file,
|
|
# see the Configure script.
|
|
#
|
|
|
|
mainmenu "Linux/UltraSPARC Kernel Configuration"
|
|
|
|
config 64BIT
|
|
def_bool y
|
|
|
|
config MMU
|
|
bool
|
|
default y
|
|
|
|
config TIME_INTERPOLATION
|
|
bool
|
|
default y
|
|
|
|
choice
|
|
prompt "Kernel page size"
|
|
default SPARC64_PAGE_SIZE_8KB
|
|
|
|
config SPARC64_PAGE_SIZE_8KB
|
|
bool "8KB"
|
|
help
|
|
This lets you select the page size of the kernel.
|
|
|
|
8KB and 64KB work quite well, since Sparc ELF sections
|
|
provide for up to 64KB alignment.
|
|
|
|
Therefore, 512KB and 4MB are for expert hackers only.
|
|
|
|
If you don't know what to do, choose 8KB.
|
|
|
|
config SPARC64_PAGE_SIZE_64KB
|
|
bool "64KB"
|
|
|
|
config SPARC64_PAGE_SIZE_512KB
|
|
bool "512KB"
|
|
|
|
config SPARC64_PAGE_SIZE_4MB
|
|
bool "4MB"
|
|
|
|
endchoice
|
|
|
|
source "init/Kconfig"
|
|
|
|
config SYSVIPC_COMPAT
|
|
bool
|
|
depends on COMPAT && SYSVIPC
|
|
default y
|
|
|
|
menu "General machine setup"
|
|
|
|
config BBC_I2C
|
|
tristate "UltraSPARC-III bootbus i2c controller driver"
|
|
depends on PCI
|
|
help
|
|
The BBC devices on the UltraSPARC III have two I2C controllers. The
|
|
first I2C controller connects mainly to configuration PROMs (NVRAM,
|
|
CPU configuration, DIMM types, etc.). The second I2C controller
|
|
connects to environmental control devices such as fans and
|
|
temperature sensors. The second controller also connects to the
|
|
smartcard reader, if present. Say Y to enable support for these.
|
|
|
|
config VT
|
|
bool "Virtual terminal" if EMBEDDED
|
|
select INPUT
|
|
default y
|
|
---help---
|
|
If you say Y here, you will get support for terminal devices with
|
|
display and keyboard devices. These are called "virtual" because you
|
|
can run several virtual terminals (also called virtual consoles) on
|
|
one physical terminal. This is rather useful, for example one
|
|
virtual terminal can collect system messages and warnings, another
|
|
one can be used for a text-mode user session, and a third could run
|
|
an X session, all in parallel. Switching between virtual terminals
|
|
is done with certain key combinations, usually Alt-<function key>.
|
|
|
|
The setterm command ("man setterm") can be used to change the
|
|
properties (such as colors or beeping) of a virtual terminal. The
|
|
man page console_codes(4) ("man console_codes") contains the special
|
|
character sequences that can be used to change those properties
|
|
directly. The fonts used on virtual terminals can be changed with
|
|
the setfont ("man setfont") command and the key bindings are defined
|
|
with the loadkeys ("man loadkeys") command.
|
|
|
|
You need at least one virtual terminal device in order to make use
|
|
of your keyboard and monitor. Therefore, only people configuring an
|
|
embedded system would want to say N here in order to save some
|
|
memory; the only way to log into such a system is then via a serial
|
|
or network connection.
|
|
|
|
If unsure, say Y, or else you won't be able to do much with your new
|
|
shiny Linux system :-)
|
|
|
|
config VT_CONSOLE
|
|
bool "Support for console on virtual terminal" if EMBEDDED
|
|
depends on VT
|
|
default y
|
|
---help---
|
|
The system console is the device which receives all kernel messages
|
|
and warnings and which allows logins in single user mode. If you
|
|
answer Y here, a virtual terminal (the device used to interact with
|
|
a physical terminal) can be used as system console. This is the most
|
|
common mode of operations, so you should say Y here unless you want
|
|
the kernel messages be output only to a serial port (in which case
|
|
you should say Y to "Console on serial port", below).
|
|
|
|
If you do say Y here, by default the currently visible virtual
|
|
terminal (/dev/tty0) will be used as system console. You can change
|
|
that with a kernel command line option such as "console=tty3" which
|
|
would use the third virtual terminal as system console. (Try "man
|
|
bootparam" or see the documentation of your boot loader (lilo or
|
|
loadlin) about how to pass options to the kernel at boot time.)
|
|
|
|
If unsure, say Y.
|
|
|
|
config HW_CONSOLE
|
|
bool
|
|
default y
|
|
|
|
config SMP
|
|
bool "Symmetric multi-processing support"
|
|
---help---
|
|
This enables support for systems with more than one CPU. If you have
|
|
a system with only one CPU, say N. If you have a system with more than
|
|
one CPU, say Y.
|
|
|
|
If you say N here, the kernel will run on single and multiprocessor
|
|
machines, but will use only one CPU of a multiprocessor machine. If
|
|
you say Y here, the kernel will run on many, but not all,
|
|
singleprocessor machines. On a singleprocessor machine, the kernel
|
|
will run faster if you say N here.
|
|
|
|
People using multiprocessor machines who say Y here should also say
|
|
Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
|
|
Management" code will be disabled if you say Y here.
|
|
|
|
See also the <file:Documentation/smp.txt>,
|
|
<file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
If you don't know what to do here, say N.
|
|
|
|
config PREEMPT
|
|
bool "Preemptible Kernel"
|
|
help
|
|
This option reduces the latency of the kernel when reacting to
|
|
real-time or interactive events by allowing a low priority process to
|
|
be preempted even if it is in kernel mode executing a system call.
|
|
This allows applications to run more reliably even when the system is
|
|
under load.
|
|
|
|
Say Y here if you are building a kernel for a desktop, embedded
|
|
or real-time system. Say N if you are unsure.
|
|
|
|
config NR_CPUS
|
|
int "Maximum number of CPUs (2-64)"
|
|
range 2 64
|
|
depends on SMP
|
|
default "32"
|
|
|
|
source "drivers/cpufreq/Kconfig"
|
|
|
|
config US3_FREQ
|
|
tristate "UltraSPARC-III CPU Frequency driver"
|
|
depends on CPU_FREQ
|
|
select CPU_FREQ_TABLE
|
|
help
|
|
This adds the CPUFreq driver for UltraSPARC-III processors.
|
|
|
|
For details, take a look at <file:Documentation/cpu-freq>.
|
|
|
|
If in doubt, say N.
|
|
|
|
config US2E_FREQ
|
|
tristate "UltraSPARC-IIe CPU Frequency driver"
|
|
depends on CPU_FREQ
|
|
select CPU_FREQ_TABLE
|
|
help
|
|
This adds the CPUFreq driver for UltraSPARC-IIe processors.
|
|
|
|
For details, take a look at <file:Documentation/cpu-freq>.
|
|
|
|
If in doubt, say N.
|
|
|
|
# Identify this as a Sparc64 build
|
|
config SPARC64
|
|
bool
|
|
default y
|
|
help
|
|
SPARC is a family of RISC microprocessors designed and marketed by
|
|
Sun Microsystems, incorporated. This port covers the newer 64-bit
|
|
UltraSPARC. The UltraLinux project maintains both the SPARC32 and
|
|
SPARC64 ports; its web page is available at
|
|
<http://www.ultralinux.org/>.
|
|
|
|
# Global things across all Sun machines.
|
|
config RWSEM_GENERIC_SPINLOCK
|
|
bool
|
|
|
|
config RWSEM_XCHGADD_ALGORITHM
|
|
bool
|
|
default y
|
|
|
|
config GENERIC_CALIBRATE_DELAY
|
|
bool
|
|
default y
|
|
|
|
choice
|
|
prompt "SPARC64 Huge TLB Page Size"
|
|
depends on HUGETLB_PAGE
|
|
default HUGETLB_PAGE_SIZE_4MB
|
|
|
|
config HUGETLB_PAGE_SIZE_4MB
|
|
bool "4MB"
|
|
|
|
config HUGETLB_PAGE_SIZE_512K
|
|
depends on !SPARC64_PAGE_SIZE_4MB
|
|
bool "512K"
|
|
|
|
config HUGETLB_PAGE_SIZE_64K
|
|
depends on !SPARC64_PAGE_SIZE_4MB && !SPARC64_PAGE_SIZE_512K
|
|
bool "64K"
|
|
|
|
endchoice
|
|
|
|
config GENERIC_ISA_DMA
|
|
bool
|
|
default y
|
|
|
|
config ISA
|
|
bool
|
|
help
|
|
Find out whether you have ISA slots on your motherboard. ISA is the
|
|
name of a bus system, i.e. the way the CPU talks to the other stuff
|
|
inside your box. Other bus systems are PCI, EISA, MicroChannel
|
|
(MCA) or VESA. ISA is an older system, now being displaced by PCI;
|
|
newer boards don't support it. If you have ISA, say Y, otherwise N.
|
|
|
|
config ISAPNP
|
|
bool
|
|
help
|
|
Say Y here if you would like support for ISA Plug and Play devices.
|
|
Some information is in <file:Documentation/isapnp.txt>.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called isapnp.
|
|
|
|
If unsure, say Y.
|
|
|
|
config EISA
|
|
bool
|
|
---help---
|
|
The Extended Industry Standard Architecture (EISA) bus was
|
|
developed as an open alternative to the IBM MicroChannel bus.
|
|
|
|
The EISA bus provided some of the features of the IBM MicroChannel
|
|
bus while maintaining backward compatibility with cards made for
|
|
the older ISA bus. The EISA bus saw limited use between 1988 and
|
|
1995 when it was made obsolete by the PCI bus.
|
|
|
|
Say Y here if you are building a kernel for an EISA-based machine.
|
|
|
|
Otherwise, say N.
|
|
|
|
config MCA
|
|
bool
|
|
help
|
|
MicroChannel Architecture is found in some IBM PS/2 machines and
|
|
laptops. It is a bus system similar to PCI or ISA. See
|
|
<file:Documentation/mca.txt> (and especially the web page given
|
|
there) before attempting to build an MCA bus kernel.
|
|
|
|
config PCMCIA
|
|
tristate
|
|
---help---
|
|
Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
|
|
computer. These are credit-card size devices such as network cards,
|
|
modems or hard drives often used with laptops computers. There are
|
|
actually two varieties of these cards: the older 16 bit PCMCIA cards
|
|
and the newer 32 bit CardBus cards. If you want to use CardBus
|
|
cards, you need to say Y here and also to "CardBus support" below.
|
|
|
|
To use your PC-cards, you will need supporting software from David
|
|
Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
|
|
for location). Please also read the PCMCIA-HOWTO, available from
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
To compile this driver as modules, choose M here: the
|
|
modules will be called pcmcia_core and ds.
|
|
|
|
config SBUS
|
|
bool
|
|
default y
|
|
|
|
config SBUSCHAR
|
|
bool
|
|
default y
|
|
|
|
config SUN_AUXIO
|
|
bool
|
|
default y
|
|
|
|
config SUN_IO
|
|
bool
|
|
default y
|
|
|
|
config PCI
|
|
bool "PCI support"
|
|
help
|
|
Find out whether you have a PCI motherboard. PCI is the name of a
|
|
bus system, i.e. the way the CPU talks to the other stuff inside
|
|
your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
|
|
VESA. If you have PCI, say Y, otherwise N.
|
|
|
|
The PCI-HOWTO, available from
|
|
<http://www.tldp.org/docs.html#howto>, contains valuable
|
|
information about which PCI hardware does work under Linux and which
|
|
doesn't.
|
|
|
|
config PCI_DOMAINS
|
|
bool
|
|
default PCI
|
|
|
|
config RTC
|
|
tristate
|
|
depends on PCI
|
|
default y
|
|
---help---
|
|
If you say Y here and create a character special file /dev/rtc with
|
|
major number 10 and minor number 135 using mknod ("man mknod"), you
|
|
will get access to the real time clock (or hardware clock) built
|
|
into your computer.
|
|
|
|
Every PC has such a clock built in. It can be used to generate
|
|
signals from as low as 1Hz up to 8192Hz, and can also be used
|
|
as a 24 hour alarm. It reports status information via the file
|
|
/proc/driver/rtc and its behaviour is set by various ioctls on
|
|
/dev/rtc.
|
|
|
|
If you run Linux on a multiprocessor machine and said Y to
|
|
"Symmetric Multi Processing" above, you should say Y here to read
|
|
and set the RTC in an SMP compatible fashion.
|
|
|
|
If you think you have a use for such a device (such as periodic data
|
|
sampling), then say Y here, and read <file:Documentation/rtc.txt>
|
|
for details.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called rtc.
|
|
|
|
source "drivers/pci/Kconfig"
|
|
|
|
config SUN_OPENPROMFS
|
|
tristate "Openprom tree appears in /proc/openprom"
|
|
help
|
|
If you say Y, the OpenPROM device tree will be available as a
|
|
virtual file system, which you can mount to /proc/openprom by "mount
|
|
-t openpromfs none /proc/openprom".
|
|
|
|
To compile the /proc/openprom support as a module, choose M here: the
|
|
module will be called openpromfs. If unsure, choose M.
|
|
|
|
config SPARC32_COMPAT
|
|
bool "Kernel support for Linux/Sparc 32bit binary compatibility"
|
|
help
|
|
This allows you to run 32-bit binaries on your Ultra.
|
|
Everybody wants this; say Y.
|
|
|
|
config COMPAT
|
|
bool
|
|
depends on SPARC32_COMPAT
|
|
default y
|
|
|
|
config UID16
|
|
bool
|
|
depends on SPARC32_COMPAT
|
|
default y
|
|
|
|
config BINFMT_ELF32
|
|
tristate "Kernel support for 32-bit ELF binaries"
|
|
depends on SPARC32_COMPAT
|
|
help
|
|
This allows you to run 32-bit Linux/ELF binaries on your Ultra.
|
|
Everybody wants this; say Y.
|
|
|
|
config BINFMT_AOUT32
|
|
bool "Kernel support for 32-bit (ie. SunOS) a.out binaries"
|
|
depends on SPARC32_COMPAT
|
|
help
|
|
This allows you to run 32-bit a.out format binaries on your Ultra.
|
|
If you want to run SunOS binaries (see SunOS binary emulation below)
|
|
or other a.out binaries, say Y. If unsure, say N.
|
|
|
|
source "fs/Kconfig.binfmt"
|
|
|
|
config SUNOS_EMUL
|
|
bool "SunOS binary emulation"
|
|
depends on BINFMT_AOUT32
|
|
help
|
|
This allows you to run most SunOS binaries. If you want to do this,
|
|
say Y here and place appropriate files in /usr/gnemul/sunos. See
|
|
<http://www.ultralinux.org/faq.html> for more information. If you
|
|
want to run SunOS binaries on an Ultra you must also say Y to
|
|
"Kernel support for 32-bit a.out binaries" above.
|
|
|
|
config SOLARIS_EMUL
|
|
tristate "Solaris binary emulation (EXPERIMENTAL)"
|
|
depends on SPARC32_COMPAT && EXPERIMENTAL
|
|
help
|
|
This is experimental code which will enable you to run (many)
|
|
Solaris binaries on your SPARC Linux machine.
|
|
|
|
To compile this code as a module, choose M here: the
|
|
module will be called solaris.
|
|
|
|
source "drivers/parport/Kconfig"
|
|
|
|
config PRINTER
|
|
tristate "Parallel printer support"
|
|
depends on PARPORT
|
|
---help---
|
|
If you intend to attach a printer to the parallel port of your Linux
|
|
box (as opposed to using a serial printer; if the connector at the
|
|
printer has 9 or 25 holes ["female"], then it's serial), say Y.
|
|
Also read the Printing-HOWTO, available from
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
It is possible to share one parallel port among several devices
|
|
(e.g. printer and ZIP drive) and it is safe to compile the
|
|
corresponding drivers into the kernel.
|
|
To compile this driver as a module, choose M here and read
|
|
<file:Documentation/parport.txt>. The module will be called lp.
|
|
|
|
If you have several parallel ports, you can specify which ports to
|
|
use with the "lp" kernel command line option. (Try "man bootparam"
|
|
or see the documentation of your boot loader (lilo or loadlin) about
|
|
how to pass options to the kernel at boot time.) The syntax of the
|
|
"lp" command line option can be found in <file:drivers/char/lp.c>.
|
|
|
|
If you have more than 8 printers, you need to increase the LP_NO
|
|
macro in lp.c and the PARPORT_MAX macro in parport.h.
|
|
|
|
config ENVCTRL
|
|
tristate "SUNW, envctrl support"
|
|
depends on PCI
|
|
help
|
|
Kernel support for temperature and fan monitoring on Sun SME
|
|
machines.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called envctrl.
|
|
|
|
config DISPLAY7SEG
|
|
tristate "7-Segment Display support"
|
|
depends on PCI
|
|
---help---
|
|
This is the driver for the 7-segment display and LED present on
|
|
Sun Microsystems CompactPCI models CP1400 and CP1500.
|
|
|
|
To compile this driver as a module, choose M here: the
|
|
module will be called display7seg.
|
|
|
|
If you do not have a CompactPCI model CP1400 or CP1500, or
|
|
another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
|
|
you should say N to this option.
|
|
|
|
config CMDLINE_BOOL
|
|
bool "Default bootloader kernel arguments"
|
|
|
|
config CMDLINE
|
|
string "Initial kernel command string"
|
|
depends on CMDLINE_BOOL
|
|
default "console=ttyS0,9600 root=/dev/sda1"
|
|
help
|
|
Say Y here if you want to be able to pass default arguments to
|
|
the kernel. This will be overridden by the bootloader, if you
|
|
use one (such as SILO). This is most useful if you want to boot
|
|
a kernel from TFTP, and want default options to be available
|
|
with having them passed on the command line.
|
|
|
|
NOTE: This option WILL override the PROM bootargs setting!
|
|
|
|
endmenu
|
|
|
|
source "drivers/base/Kconfig"
|
|
|
|
source "drivers/video/Kconfig"
|
|
|
|
source "drivers/serial/Kconfig"
|
|
|
|
source "drivers/sbus/char/Kconfig"
|
|
|
|
source "drivers/mtd/Kconfig"
|
|
|
|
source "drivers/block/Kconfig"
|
|
|
|
source "drivers/ide/Kconfig"
|
|
|
|
source "drivers/scsi/Kconfig"
|
|
|
|
source "drivers/fc4/Kconfig"
|
|
|
|
source "drivers/md/Kconfig"
|
|
|
|
if PCI
|
|
source "drivers/message/fusion/Kconfig"
|
|
endif
|
|
|
|
source "drivers/ieee1394/Kconfig"
|
|
|
|
source "net/Kconfig"
|
|
|
|
source "drivers/isdn/Kconfig"
|
|
|
|
source "drivers/telephony/Kconfig"
|
|
|
|
# This one must be before the filesystem configs. -DaveM
|
|
|
|
menu "Unix98 PTY support"
|
|
|
|
config UNIX98_PTYS
|
|
bool "Unix98 PTY support"
|
|
---help---
|
|
A pseudo terminal (PTY) is a software device consisting of two
|
|
halves: a master and a slave. The slave device behaves identical to
|
|
a physical terminal; the master device is used by a process to
|
|
read data from and write data to the slave, thereby emulating a
|
|
terminal. Typical programs for the master side are telnet servers
|
|
and xterms.
|
|
|
|
Linux has traditionally used the BSD-like names /dev/ptyxx for
|
|
masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
|
|
has a number of problems. The GNU C library glibc 2.1 and later,
|
|
however, supports the Unix98 naming standard: in order to acquire a
|
|
pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
|
|
terminal is then made available to the process and the pseudo
|
|
terminal slave can be accessed as /dev/pts/<number>. What was
|
|
traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
|
|
|
|
The entries in /dev/pts/ are created on the fly by a virtual
|
|
file system; therefore, if you say Y here you should say Y to
|
|
"/dev/pts file system for Unix98 PTYs" as well.
|
|
|
|
If you want to say Y here, you need to have the C library glibc 2.1
|
|
or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
|
|
Read the instructions in <file:Documentation/Changes> pertaining to
|
|
pseudo terminals. It's safe to say N.
|
|
|
|
config UNIX98_PTY_COUNT
|
|
int "Maximum number of Unix98 PTYs in use (0-2048)"
|
|
depends on UNIX98_PTYS
|
|
default "256"
|
|
help
|
|
The maximum number of Unix98 PTYs that can be used at any one time.
|
|
The default is 256, and should be enough for desktop systems. Server
|
|
machines which support incoming telnet/rlogin/ssh connections and/or
|
|
serve several X terminals may want to increase this: every incoming
|
|
connection and every xterm uses up one PTY.
|
|
|
|
When not in use, each additional set of 256 PTYs occupy
|
|
approximately 8 KB of kernel memory on 32-bit architectures.
|
|
|
|
endmenu
|
|
|
|
menu "XFree86 DRI support"
|
|
|
|
config DRM
|
|
bool "Direct Rendering Manager (XFree86 DRI support)"
|
|
help
|
|
Kernel-level support for the Direct Rendering Infrastructure (DRI)
|
|
introduced in XFree86 4.0. If you say Y here, you need to select
|
|
the module that's right for your graphics card from the list below.
|
|
These modules provide support for synchronization, security, and
|
|
DMA transfers. Please see <http://dri.sourceforge.net/> for more
|
|
details. You should also select and configure AGP
|
|
(/dev/agpgart) support.
|
|
|
|
config DRM_FFB
|
|
tristate "Creator/Creator3D"
|
|
depends on DRM && BROKEN
|
|
help
|
|
Choose this option if you have one of Sun's Creator3D-based graphics
|
|
and frame buffer cards. Product page at
|
|
<http://www.sun.com/desktop/products/Graphics/creator3d.html>.
|
|
|
|
config DRM_TDFX
|
|
tristate "3dfx Banshee/Voodoo3+"
|
|
depends on DRM
|
|
help
|
|
Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
|
|
graphics card. If M is selected, the module will be called tdfx.
|
|
|
|
config DRM_R128
|
|
tristate "ATI Rage 128"
|
|
depends on DRM
|
|
help
|
|
Choose this option if you have an ATI Rage 128 graphics card. If M
|
|
is selected, the module will be called r128. AGP support for
|
|
this card is strongly suggested (unless you have a PCI version).
|
|
|
|
endmenu
|
|
|
|
source "drivers/input/Kconfig"
|
|
|
|
source "drivers/i2c/Kconfig"
|
|
|
|
source "fs/Kconfig"
|
|
|
|
source "drivers/media/Kconfig"
|
|
|
|
source "sound/Kconfig"
|
|
|
|
source "drivers/usb/Kconfig"
|
|
|
|
source "drivers/infiniband/Kconfig"
|
|
|
|
source "drivers/char/watchdog/Kconfig"
|
|
|
|
source "arch/sparc64/oprofile/Kconfig"
|
|
|
|
source "arch/sparc64/Kconfig.debug"
|
|
|
|
source "security/Kconfig"
|
|
|
|
source "crypto/Kconfig"
|
|
|
|
source "lib/Kconfig"
|