arch/arm/Kconfig - LeafOS-Devices/android_kernel_realme_mt6785 - Gitiles

 #
 # For a description of the syntax of this configuration file,
 # see Documentation/kbuild/kconfig-language.txt.
 #

 mainmenu "Linux Kernel Configuration"

 config ARM
 	bool
 	default y
 	help
 	  The ARM series is a line of low-power-consumption RISC chip designs
 	  licensed by ARM ltd and targeted at embedded applications and
 	  handhelds such as the Compaq IPAQ.  ARM-based PCs are no longer
 	  manufactured, but  legacy ARM-based PC hardware remains popular in
 	  Europe.  There is an ARM Linux project with a web page at
 	  <http://www.arm.linux.org.uk/>.

 config MMU
 	bool
 	default 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 SBUS
 	bool

 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 UID16
 	bool
 	default y

 config RWSEM_GENERIC_SPINLOCK
 	bool
 	default y

 config RWSEM_XCHGADD_ALGORITHM
 	bool

 config GENERIC_CALIBRATE_DELAY
 	bool
 	default y

 config GENERIC_BUST_SPINLOCK
 	bool

 config GENERIC_ISA_DMA
 	bool

 config GENERIC_IOMAP
 	bool
 	default y

 config FIQ
 	bool

 source "init/Kconfig"

 menu "System Type"

 choice
 	prompt "ARM system type"
 	default ARCH_RPC

 config ARCH_CLPS7500
 	bool "Cirrus-CL-PS7500FE"
 	select TIMER_ACORN
 	select ISA

 config ARCH_CLPS711X
 	bool "CLPS711x/EP721x-based"

 config ARCH_CO285
 	bool "Co-EBSA285"
 	select FOOTBRIDGE
 	select FOOTBRIDGE_ADDIN

 config ARCH_EBSA110
 	bool "EBSA-110"
 	select ISA
 	help
 	  This is an evaluation board for the StrongARM processor available
 	  from Digital. It has limited hardware on-board, including an onboard
 	  Ethernet interface, two PCMCIA sockets, two serial ports and a
 	  parallel port.

 config ARCH_CAMELOT
 	bool "Epxa10db"
 	help
 	  This enables support for Altera's Excalibur XA10 development board.
 	  If you would like to build your kernel to run on one of these boards
 	  then you must say 'Y' here. Otherwise say 'N'

 config ARCH_FOOTBRIDGE
 	bool "FootBridge"
 	select FOOTBRIDGE

 config ARCH_INTEGRATOR
 	bool "Integrator"
 	select ARM_AMBA
 	select ICST525

 config ARCH_IOP3XX
 	bool "IOP3xx-based"
 	select PCI

 config ARCH_IXP4XX
 	bool "IXP4xx-based"
 	select DMABOUNCE
 	select PCI

 config ARCH_IXP2000
 	bool "IXP2400/2800-based"
 	select PCI

 config ARCH_L7200
 	bool "LinkUp-L7200"
 	select FIQ
 	help
 	  Say Y here if you intend to run this kernel on a LinkUp Systems
 	  L7200 Software Development Board which uses an ARM720T processor.
 	  Information on this board can be obtained at:

 	  <http://www.linkupsys.com/>

 	  If you have any questions or comments about the Linux kernel port
 	  to this board, send e-mail to <sjhill@cotw.com>.

 config ARCH_PXA
 	bool "PXA2xx-based"

 config ARCH_RPC
 	bool "RiscPC"
 	select ARCH_ACORN
 	select FIQ
 	select TIMER_ACORN
 	help
 	  On the Acorn Risc-PC, Linux can support the internal IDE disk and
 	  CD-ROM interface, serial and parallel port, and the floppy drive.

 config ARCH_SA1100
 	bool "SA1100-based"
 	select ISA
 	select DISCONTIGMEM

 config ARCH_S3C2410
 	bool "Samsung S3C2410"
 	help
 	  Samsung S3C2410X CPU based systems, such as the Simtec Electronics
 	  BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
 	  the Samsung SMDK2410 development board (and derviatives).

 config ARCH_SHARK
 	bool "Shark"
 	select ISA
 	select ISA_DMA
 	select PCI

 config ARCH_LH7A40X
 	bool "Sharp LH7A40X"
 	help
 	  Say Y here for systems based on one of the Sharp LH7A40X
 	  System on a Chip processors.  These CPUs include an ARM922T
 	  core with a wide array of integrated devices for
 	  hand-held and low-power applications.

 config ARCH_OMAP
 	bool "TI OMAP"

 config ARCH_VERSATILE
 	bool "Versatile"
 	select ARM_AMBA
 	select ICST307
 	help
 	  This enables support for ARM Ltd Versatile board.

 config ARCH_IMX
 	bool "IMX"

 config ARCH_H720X
 	bool "Hynix-HMS720x-based"
 	help
 	  This enables support for systems based on the Hynix HMS720x

 endchoice

 source "arch/arm/mach-clps711x/Kconfig"

 source "arch/arm/mach-epxa10db/Kconfig"

 source "arch/arm/mach-footbridge/Kconfig"

 source "arch/arm/mach-integrator/Kconfig"

 source "arch/arm/mach-iop3xx/Kconfig"

 source "arch/arm/mach-ixp4xx/Kconfig"

 source "arch/arm/mach-ixp2000/Kconfig"

 source "arch/arm/mach-pxa/Kconfig"

 source "arch/arm/mach-sa1100/Kconfig"

 source "arch/arm/mach-omap/Kconfig"

 source "arch/arm/mach-s3c2410/Kconfig"

 source "arch/arm/mach-lh7a40x/Kconfig"

 source "arch/arm/mach-imx/Kconfig"

 source "arch/arm/mach-h720x/Kconfig"

 source "arch/arm/mach-versatile/Kconfig"

 # Definitions to make life easier
 config ARCH_ACORN
 	bool

 source arch/arm/mm/Kconfig

 #  bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
 config XSCALE_PMU
 	bool
 	depends on CPU_XSCALE && !XSCALE_PMU_TIMER
 	default y

 endmenu

 source "arch/arm/common/Kconfig"

 config FORCE_MAX_ZONEORDER
 	int
 	depends on SA1111
 	default "9"

 menu "Bus support"

 config ARM_AMBA
 	bool

 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 ISA_DMA
 	bool

 config ISA_DMA_API
 	bool
 	default y

 config PCI
 	bool "PCI support" if ARCH_INTEGRATOR_AP
 	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.

 # Select the host bridge type
 config PCI_HOST_VIA82C505
 	bool
 	depends on PCI && ARCH_SHARK
 	default y

 source "drivers/pci/Kconfig"

 source "drivers/pcmcia/Kconfig"

 endmenu

 menu "Kernel Features"

 config SMP
 	bool "Symmetric Multi-Processing (EXPERIMENTAL)"
 	depends on EXPERIMENTAL #&& n
 	help
 	  This enables support for systems with more than one CPU. If you have
 	  a system with only one CPU, like most personal computers, 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, single
 	  processor machines. On a single processor machine, the kernel will
 	  run faster if you say N here.

 	  See also the <file:Documentation/smp.tex>,
 	  <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
 	  <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
 	  <http://www.linuxdoc.org/docs.html#howto>.

 	  If you don't know what to do here, say N.

 config NR_CPUS
 	int "Maximum number of CPUs (2-32)"
 	range 2 32
 	depends on SMP
 	default "4"

 config PREEMPT
 	bool "Preemptible Kernel (EXPERIMENTAL)"
 	depends on EXPERIMENTAL
 	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 DISCONTIGMEM
 	bool
 	default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
 	help
 	  Say Y to support efficient handling of discontiguous physical memory,
 	  for architectures which are either NUMA (Non-Uniform Memory Access)
 	  or have huge holes in the physical address space for other reasons.
 	  See <file:Documentation/vm/numa> for more.

 config LEDS
 	bool "Timer and CPU usage LEDs"
 	depends on ARCH_CDB89712 || ARCH_CO285 || ARCH_EBSA110 || \
 		   ARCH_EBSA285 || ARCH_IMX || ARCH_INTEGRATOR || \
 		   ARCH_LUBBOCK || MACH_MAINSTONE || ARCH_NETWINDER || \
 		   ARCH_OMAP || ARCH_P720T || ARCH_PXA_IDP || \
 		   ARCH_SA1100 || ARCH_SHARK || ARCH_VERSATILE
 	help
 	  If you say Y here, the LEDs on your machine will be used
 	  to provide useful information about your current system status.

 	  If you are compiling a kernel for a NetWinder or EBSA-285, you will
 	  be able to select which LEDs are active using the options below. If
 	  you are compiling a kernel for the EBSA-110 or the LART however, the
 	  red LED will simply flash regularly to indicate that the system is
 	  still functional. It is safe to say Y here if you have a CATS
 	  system, but the driver will do nothing.

 config LEDS_TIMER
 	bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) || \
 			    MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
 	depends on LEDS
 	default y if ARCH_EBSA110
 	help
 	  If you say Y here, one of the system LEDs (the green one on the
 	  NetWinder, the amber one on the EBSA285, or the red one on the LART)
 	  will flash regularly to indicate that the system is still
 	  operational. This is mainly useful to kernel hackers who are
 	  debugging unstable kernels.

 	  The LART uses the same LED for both Timer LED and CPU usage LED
 	  functions. You may choose to use both, but the Timer LED function
 	  will overrule the CPU usage LED.

 config LEDS_CPU
 	bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
 			!ARCH_OMAP) || MACH_OMAP_H2 || MACH_OMAP_PERSEUS2
 	depends on LEDS
 	help
 	  If you say Y here, the red LED will be used to give a good real
 	  time indication of CPU usage, by lighting whenever the idle task
 	  is not currently executing.

 	  The LART uses the same LED for both Timer LED and CPU usage LED
 	  functions. You may choose to use both, but the Timer LED function
 	  will overrule the CPU usage LED.

 config ALIGNMENT_TRAP
 	bool
 	default y if !ARCH_EBSA110
 	help
 	  ARM processors can not fetch/store information which is not
 	  naturally aligned on the bus, i.e., a 4 byte fetch must start at an
 	  address divisible by 4. On 32-bit ARM processors, these non-aligned
 	  fetch/store instructions will be emulated in software if you say
 	  here, which has a severe performance impact. This is necessary for
 	  correct operation of some network protocols. With an IP-only
 	  configuration it is safe to say N, otherwise say Y.

 endmenu

 menu "Boot options"

 # Compressed boot loader in ROM.  Yes, we really want to ask about
 # TEXT and BSS so we preserve their values in the config files.
 config ZBOOT_ROM_TEXT
 	hex "Compressed ROM boot loader base address"
 	default "0"
 	help
 	  The physical address at which the ROM-able zImage is to be
 	  placed in the target.  Platforms which normally make use of
 	  ROM-able zImage formats normally set this to a suitable
 	  value in their defconfig file.

 	  If ZBOOT_ROM is not enabled, this has no effect.

 config ZBOOT_ROM_BSS
 	hex "Compressed ROM boot loader BSS address"
 	default "0"
 	help
 	  The base address of 64KiB of read/write memory in the target
 	  for the ROM-able zImage, which must be available while the
 	  decompressor is running.  Platforms which normally make use of
 	  ROM-able zImage formats normally set this to a suitable
 	  value in their defconfig file.

 	  If ZBOOT_ROM is not enabled, this has no effect.

 config ZBOOT_ROM
 	bool "Compressed boot loader in ROM/flash"
 	depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
 	help
 	  Say Y here if you intend to execute your compressed kernel image
 	  (zImage) directly from ROM or flash.  If unsure, say N.

 config CMDLINE
 	string "Default kernel command string"
 	default ""
 	help
 	  On some architectures (EBSA110 and CATS), there is currently no way
 	  for the boot loader to pass arguments to the kernel. For these
 	  architectures, you should supply some command-line options at build
 	  time by entering them here. As a minimum, you should specify the
 	  memory size and the root device (e.g., mem=64M root=/dev/nfs).

 config XIP_KERNEL
 	bool "Kernel Execute-In-Place from ROM"
 	depends on !ZBOOT_ROM
 	help
 	  Execute-In-Place allows the kernel to run from non-volatile storage
 	  directly addressable by the CPU, such as NOR flash. This saves RAM
 	  space since the text section of the kernel is not loaded from flash
 	  to RAM.  Read-write sections, such as the data section and stack,
 	  are still copied to RAM.  The XIP kernel is not compressed since
 	  it has to run directly from flash, so it will take more space to
 	  store it.  The flash address used to link the kernel object files,
 	  and for storing it, is configuration dependent. Therefore, if you
 	  say Y here, you must know the proper physical address where to
 	  store the kernel image depending on your own flash memory usage.

 	  Also note that the make target becomes "make xipImage" rather than
 	  "make zImage" or "make Image".  The final kernel binary to put in
 	  ROM memory will be arch/arm/boot/xipImage.

 	  If unsure, say N.

 config XIP_PHYS_ADDR
 	hex "XIP Kernel Physical Location"
 	depends on XIP_KERNEL
 	default "0x00080000"
 	help
 	  This is the physical address in your flash memory the kernel will
 	  be linked for and stored to.  This address is dependent on your
 	  own flash usage.

 endmenu

 if (ARCH_SA1100 || ARCH_INTEGRATOR)

 menu "CPU Frequency scaling"

 source "drivers/cpufreq/Kconfig"

 config CPU_FREQ_SA1100
 	bool
 	depends on CPU_FREQ && (SA1100_H3100 || SA1100_H3600 || SA1100_H3800 || SA1100_LART || SA1100_PLEB || SA1100_BADGE4 || SA1100_HACKKIT)
 	default y

 config CPU_FREQ_SA1110
 	bool
 	depends on CPU_FREQ && (SA1100_ASSABET || SA1100_CERF || SA1100_PT_SYSTEM3)
 	default y

 config CPU_FREQ_INTEGRATOR
 	tristate "CPUfreq driver for ARM Integrator CPUs"
 	depends on ARCH_INTEGRATOR && CPU_FREQ
 	default y
 	help
 	  This enables the CPUfreq driver for ARM Integrator CPUs.

 	  For details, take a look at <file:Documentation/cpu-freq>.

 	  If in doubt, say Y.

 endmenu

 endif

 menu "Floating point emulation"

 comment "At least one emulation must be selected"

 config FPE_NWFPE
 	bool "NWFPE math emulation"
 	---help---
 	  Say Y to include the NWFPE floating point emulator in the kernel.
 	  This is necessary to run most binaries. Linux does not currently
 	  support floating point hardware so you need to say Y here even if
 	  your machine has an FPA or floating point co-processor podule.

 	  You may say N here if you are going to load the Acorn FPEmulator
 	  early in the bootup.

 config FPE_NWFPE_XP
 	bool "Support extended precision"
 	depends on FPE_NWFPE && !CPU_BIG_ENDIAN
 	help
 	  Say Y to include 80-bit support in the kernel floating-point
 	  emulator.  Otherwise, only 32 and 64-bit support is compiled in.
 	  Note that gcc does not generate 80-bit operations by default,
 	  so in most cases this option only enlarges the size of the
 	  floating point emulator without any good reason.

 	  You almost surely want to say N here.

 config FPE_FASTFPE
 	bool "FastFPE math emulation (EXPERIMENTAL)"
 	depends on !CPU_32v3 && EXPERIMENTAL
 	---help---
 	  Say Y here to include the FAST floating point emulator in the kernel.
 	  This is an experimental much faster emulator which now also has full
 	  precision for the mantissa.  It does not support any exceptions.
 	  It is very simple, and approximately 3-6 times faster than NWFPE.

 	  It should be sufficient for most programs.  It may be not suitable
 	  for scientific calculations, but you have to check this for yourself.
 	  If you do not feel you need a faster FP emulation you should better
 	  choose NWFPE.

 config VFP
 	bool "VFP-format floating point maths"
 	depends on CPU_V6 || CPU_ARM926T
 	help
 	  Say Y to include VFP support code in the kernel. This is needed
 	  if your hardware includes a VFP unit.

 	  Please see <file:Documentation/arm/VFP/release-notes.txt> for
 	  release notes and additional status information.

 	  Say N if your target does not have VFP hardware.

 endmenu

 menu "Userspace binary formats"

 source "fs/Kconfig.binfmt"

 config ARTHUR
 	tristate "RISC OS personality"
 	help
 	  Say Y here to include the kernel code necessary if you want to run
 	  Acorn RISC OS/Arthur binaries under Linux. This code is still very
 	  experimental; if this sounds frightening, say N and sleep in peace.
 	  You can also say M here to compile this support as a module (which
 	  will be called arthur).

 endmenu

 menu "Power management options"

 config PM
 	bool "Power Management support"
 	---help---
 	  "Power Management" means that parts of your computer are shut
 	  off or put into a power conserving "sleep" mode if they are not
 	  being used.  There are two competing standards for doing this: APM
 	  and ACPI.  If you want to use either one, say Y here and then also
 	  to the requisite support below.

 	  Power Management is most important for battery powered laptop
 	  computers; if you have a laptop, check out the Linux Laptop home
 	  page on the WWW at <http://www.linux-on-laptops.com/> or
 	  Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
 	  and the Battery Powered Linux mini-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.

 	  Note that, even if you say N here, Linux on the x86 architecture
 	  will issue the hlt instruction if nothing is to be done, thereby
 	  sending the processor to sleep and saving power.

 config APM
 	tristate "Advanced Power Management Emulation"
 	depends on PM
 	---help---
 	  APM is a BIOS specification for saving power using several different
 	  techniques. This is mostly useful for battery powered laptops with
 	  APM compliant BIOSes. If you say Y here, the system time will be
 	  reset after a RESUME operation, the /proc/apm device will provide
 	  battery status information, and user-space programs will receive
 	  notification of APM "events" (e.g. battery status change).

 	  If you select "Y" here, you can disable actual use of the APM
 	  BIOS by passing the "apm=off" option to the kernel at boot time.

 	  Note that the APM support is almost completely disabled for
 	  machines with more than one CPU.

 	  In order to use APM, you will need supporting software. For location
 	  and more information, read <file:Documentation/pm.txt> and the
 	  Battery Powered Linux mini-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.

 	  This driver does not spin down disk drives (see the hdparm(8)
 	  manpage ("man 8 hdparm") for that), and it doesn't turn off
 	  VESA-compliant "green" monitors.

 	  This driver does not support the TI 4000M TravelMate and the ACER
 	  486/DX4/75 because they don't have compliant BIOSes. Many "green"
 	  desktop machines also don't have compliant BIOSes, and this driver
 	  may cause those machines to panic during the boot phase.

 	  Generally, if you don't have a battery in your machine, there isn't
 	  much point in using this driver and you should say N. If you get
 	  random kernel OOPSes or reboots that don't seem to be related to
 	  anything, try disabling/enabling this option (or disabling/enabling
 	  APM in your BIOS).

 	  Some other things you should try when experiencing seemingly random,
 	  "weird" problems:

 	  1) make sure that you have enough swap space and that it is
 	  enabled.
 	  2) pass the "no-hlt" option to the kernel
 	  3) switch on floating point emulation in the kernel and pass
 	  the "no387" option to the kernel
 	  4) pass the "floppy=nodma" option to the kernel
 	  5) pass the "mem=4M" option to the kernel (thereby disabling
 	  all but the first 4 MB of RAM)
 	  6) make sure that the CPU is not over clocked.
 	  7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
 	  8) disable the cache from your BIOS settings
 	  9) install a fan for the video card or exchange video RAM
 	  10) install a better fan for the CPU
 	  11) exchange RAM chips
 	  12) exchange the motherboard.

 	  To compile this driver as a module, choose M here: the
 	  module will be called apm.

 endmenu

 menu "Device Drivers"

 source "drivers/base/Kconfig"

 if ALIGNMENT_TRAP
 source "drivers/mtd/Kconfig"
 endif

 source "drivers/parport/Kconfig"

 source "drivers/pnp/Kconfig"

 source "drivers/block/Kconfig"

 source "drivers/acorn/block/Kconfig"

 if PCMCIA || ARCH_CLPS7500 || ARCH_IOP3XX || ARCH_IXP4XX \
 	|| ARCH_L7200 || ARCH_LH7A40X || ARCH_PXA || ARCH_RPC \
 	|| ARCH_S3C2410 || ARCH_SA1100 || ARCH_SHARK || FOOTBRIDGE
 source "drivers/ide/Kconfig"
 endif

 source "drivers/scsi/Kconfig"

 source "drivers/md/Kconfig"

 source "drivers/message/fusion/Kconfig"

 source "drivers/ieee1394/Kconfig"

 source "drivers/message/i2o/Kconfig"

 source "net/Kconfig"

 source "drivers/isdn/Kconfig"

 # input before char - char/joystick depends on it. As does USB.

 source "drivers/input/Kconfig"

 source "drivers/char/Kconfig"

 source "drivers/i2c/Kconfig"

 #source "drivers/l3/Kconfig"

 source "drivers/misc/Kconfig"

 source "drivers/media/Kconfig"

 source "drivers/video/Kconfig"

 source "sound/Kconfig"

 source "drivers/usb/Kconfig"

 source "drivers/mmc/Kconfig"

 endmenu

 source "fs/Kconfig"

 source "arch/arm/oprofile/Kconfig"

 source "arch/arm/Kconfig.debug"

 source "security/Kconfig"

 source "crypto/Kconfig"

 source "lib/Kconfig"
	#
	# For a description of the syntax of this configuration file,
	# see Documentation/kbuild/kconfig-language.txt.
	#

	mainmenu "Linux Kernel Configuration"

	config ARM
	bool
	default y
	help
	The ARM series is a line of low-power-consumption RISC chip designs
	licensed by ARM ltd and targeted at embedded applications and
	handhelds such as the Compaq IPAQ. ARM-based PCs are no longer
	manufactured, but legacy ARM-based PC hardware remains popular in
	Europe. There is an ARM Linux project with a web page at
	<http://www.arm.linux.org.uk/>.

	config MMU
	bool
	default 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 SBUS
	bool

	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 UID16
	bool
	default y

	config RWSEM_GENERIC_SPINLOCK
	bool
	default y

	config RWSEM_XCHGADD_ALGORITHM
	bool

	config GENERIC_CALIBRATE_DELAY
	bool
	default y

	config GENERIC_BUST_SPINLOCK
	bool

	config GENERIC_ISA_DMA
	bool

	config GENERIC_IOMAP
	bool
	default y

	config FIQ
	bool

	source "init/Kconfig"

	menu "System Type"

	choice
	prompt "ARM system type"
	default ARCH_RPC

	config ARCH_CLPS7500
	bool "Cirrus-CL-PS7500FE"
	select TIMER_ACORN
	select ISA

	config ARCH_CLPS711X
	bool "CLPS711x/EP721x-based"

	config ARCH_CO285
	bool "Co-EBSA285"
	select FOOTBRIDGE
	select FOOTBRIDGE_ADDIN

	config ARCH_EBSA110
	bool "EBSA-110"
	select ISA
	help
	This is an evaluation board for the StrongARM processor available
	from Digital. It has limited hardware on-board, including an onboard
	Ethernet interface, two PCMCIA sockets, two serial ports and a
	parallel port.

	config ARCH_CAMELOT
	bool "Epxa10db"
	help
	This enables support for Altera's Excalibur XA10 development board.
	If you would like to build your kernel to run on one of these boards
	then you must say 'Y' here. Otherwise say 'N'

	config ARCH_FOOTBRIDGE
	bool "FootBridge"
	select FOOTBRIDGE

	config ARCH_INTEGRATOR
	bool "Integrator"
	select ARM_AMBA
	select ICST525

	config ARCH_IOP3XX
	bool "IOP3xx-based"
	select PCI

	config ARCH_IXP4XX
	bool "IXP4xx-based"
	select DMABOUNCE
	select PCI

	config ARCH_IXP2000
	bool "IXP2400/2800-based"
	select PCI

	config ARCH_L7200
	bool "LinkUp-L7200"
	select FIQ
	help
	Say Y here if you intend to run this kernel on a LinkUp Systems
	L7200 Software Development Board which uses an ARM720T processor.
	Information on this board can be obtained at:

	<http://www.linkupsys.com/>

	If you have any questions or comments about the Linux kernel port
	to this board, send e-mail to <sjhill@cotw.com>.

	config ARCH_PXA
	bool "PXA2xx-based"

	config ARCH_RPC
	bool "RiscPC"
	select ARCH_ACORN
	select FIQ
	select TIMER_ACORN
	help
	On the Acorn Risc-PC, Linux can support the internal IDE disk and
	CD-ROM interface, serial and parallel port, and the floppy drive.

	config ARCH_SA1100
	bool "SA1100-based"
	select ISA
	select DISCONTIGMEM

	config ARCH_S3C2410
	bool "Samsung S3C2410"
	help
	Samsung S3C2410X CPU based systems, such as the Simtec Electronics
	BAST (<http://www.simtec.co.uk/products/EB110ITX/>), the IPAQ 1940 or
	the Samsung SMDK2410 development board (and derviatives).

	config ARCH_SHARK
	bool "Shark"
	select ISA
	select ISA_DMA
	select PCI

	config ARCH_LH7A40X
	bool "Sharp LH7A40X"
	help
	Say Y here for systems based on one of the Sharp LH7A40X
	System on a Chip processors. These CPUs include an ARM922T
	core with a wide array of integrated devices for
	hand-held and low-power applications.

	config ARCH_OMAP
	bool "TI OMAP"

	config ARCH_VERSATILE
	bool "Versatile"
	select ARM_AMBA
	select ICST307
	help
	This enables support for ARM Ltd Versatile board.

	config ARCH_IMX
	bool "IMX"

	config ARCH_H720X
	bool "Hynix-HMS720x-based"
	help
	This enables support for systems based on the Hynix HMS720x

	endchoice

	source "arch/arm/mach-clps711x/Kconfig"

	source "arch/arm/mach-epxa10db/Kconfig"

	source "arch/arm/mach-footbridge/Kconfig"

	source "arch/arm/mach-integrator/Kconfig"

	source "arch/arm/mach-iop3xx/Kconfig"

	source "arch/arm/mach-ixp4xx/Kconfig"

	source "arch/arm/mach-ixp2000/Kconfig"

	source "arch/arm/mach-pxa/Kconfig"

	source "arch/arm/mach-sa1100/Kconfig"

	source "arch/arm/mach-omap/Kconfig"

	source "arch/arm/mach-s3c2410/Kconfig"

	source "arch/arm/mach-lh7a40x/Kconfig"

	source "arch/arm/mach-imx/Kconfig"

	source "arch/arm/mach-h720x/Kconfig"

	source "arch/arm/mach-versatile/Kconfig"

	# Definitions to make life easier
	config ARCH_ACORN
	bool

	source arch/arm/mm/Kconfig

	# bool 'Use XScale PMU as timer source' CONFIG_XSCALE_PMU_TIMER
	config XSCALE_PMU
	bool
	depends on CPU_XSCALE && !XSCALE_PMU_TIMER
	default y

	endmenu

	source "arch/arm/common/Kconfig"

	config FORCE_MAX_ZONEORDER
	int
	depends on SA1111
	default "9"

	menu "Bus support"

	config ARM_AMBA
	bool

	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 ISA_DMA
	bool

	config ISA_DMA_API
	bool
	default y

	config PCI
	bool "PCI support" if ARCH_INTEGRATOR_AP
	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.

	# Select the host bridge type
	config PCI_HOST_VIA82C505
	bool
	depends on PCI && ARCH_SHARK
	default y

	source "drivers/pci/Kconfig"

	source "drivers/pcmcia/Kconfig"

	endmenu

	menu "Kernel Features"

	config SMP
	bool "Symmetric Multi-Processing (EXPERIMENTAL)"
	depends on EXPERIMENTAL #&& n
	help
	This enables support for systems with more than one CPU. If you have
	a system with only one CPU, like most personal computers, 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, single
	processor machines. On a single processor machine, the kernel will
	run faster if you say N here.

	See also the <file:Documentation/smp.tex>,
	<file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
	<file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
	<http://www.linuxdoc.org/docs.html#howto>.

	If you don't know what to do here, say N.

	config NR_CPUS
	int "Maximum number of CPUs (2-32)"
	range 2 32
	depends on SMP
	default "4"

	config PREEMPT
	bool "Preemptible Kernel (EXPERIMENTAL)"
	depends on EXPERIMENTAL
	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 DISCONTIGMEM
	bool
	default (ARCH_LH7A40X && !LH7A40X_CONTIGMEM)
	help
	Say Y to support efficient handling of discontiguous physical memory,
	for architectures which are either NUMA (Non-Uniform Memory Access)
	or have huge holes in the physical address space for other reasons.
	See <file:Documentation/vm/numa> for more.

	config LEDS
	bool "Timer and CPU usage LEDs"
	depends on ARCH_CDB89712 \|\| ARCH_CO285 \|\| ARCH_EBSA110 \|\| \
	ARCH_EBSA285 \|\| ARCH_IMX \|\| ARCH_INTEGRATOR \|\| \
	ARCH_LUBBOCK \|\| MACH_MAINSTONE \|\| ARCH_NETWINDER \|\| \
	ARCH_OMAP \|\| ARCH_P720T \|\| ARCH_PXA_IDP \|\| \
	ARCH_SA1100 \|\| ARCH_SHARK \|\| ARCH_VERSATILE
	help
	If you say Y here, the LEDs on your machine will be used
	to provide useful information about your current system status.

	If you are compiling a kernel for a NetWinder or EBSA-285, you will
	be able to select which LEDs are active using the options below. If
	you are compiling a kernel for the EBSA-110 or the LART however, the
	red LED will simply flash regularly to indicate that the system is
	still functional. It is safe to say Y here if you have a CATS
	system, but the driver will do nothing.

	config LEDS_TIMER
	bool "Timer LED" if (!ARCH_CDB89712 && !ARCH_OMAP) \|\| \
	MACH_OMAP_H2 \|\| MACH_OMAP_PERSEUS2
	depends on LEDS
	default y if ARCH_EBSA110
	help
	If you say Y here, one of the system LEDs (the green one on the
	NetWinder, the amber one on the EBSA285, or the red one on the LART)
	will flash regularly to indicate that the system is still
	operational. This is mainly useful to kernel hackers who are
	debugging unstable kernels.

	The LART uses the same LED for both Timer LED and CPU usage LED
	functions. You may choose to use both, but the Timer LED function
	will overrule the CPU usage LED.

	config LEDS_CPU
	bool "CPU usage LED" if (!ARCH_CDB89712 && !ARCH_EBSA110 && \
	!ARCH_OMAP) \|\| MACH_OMAP_H2 \|\| MACH_OMAP_PERSEUS2
	depends on LEDS
	help
	If you say Y here, the red LED will be used to give a good real
	time indication of CPU usage, by lighting whenever the idle task
	is not currently executing.

	The LART uses the same LED for both Timer LED and CPU usage LED
	functions. You may choose to use both, but the Timer LED function
	will overrule the CPU usage LED.

	config ALIGNMENT_TRAP
	bool
	default y if !ARCH_EBSA110
	help
	ARM processors can not fetch/store information which is not
	naturally aligned on the bus, i.e., a 4 byte fetch must start at an
	address divisible by 4. On 32-bit ARM processors, these non-aligned
	fetch/store instructions will be emulated in software if you say
	here, which has a severe performance impact. This is necessary for
	correct operation of some network protocols. With an IP-only
	configuration it is safe to say N, otherwise say Y.

	endmenu

	menu "Boot options"

	# Compressed boot loader in ROM. Yes, we really want to ask about
	# TEXT and BSS so we preserve their values in the config files.
	config ZBOOT_ROM_TEXT
	hex "Compressed ROM boot loader base address"
	default "0"
	help
	The physical address at which the ROM-able zImage is to be
	placed in the target. Platforms which normally make use of
	ROM-able zImage formats normally set this to a suitable
	value in their defconfig file.

	If ZBOOT_ROM is not enabled, this has no effect.

	config ZBOOT_ROM_BSS
	hex "Compressed ROM boot loader BSS address"
	default "0"
	help
	The base address of 64KiB of read/write memory in the target
	for the ROM-able zImage, which must be available while the
	decompressor is running. Platforms which normally make use of
	ROM-able zImage formats normally set this to a suitable
	value in their defconfig file.

	If ZBOOT_ROM is not enabled, this has no effect.

	config ZBOOT_ROM
	bool "Compressed boot loader in ROM/flash"
	depends on ZBOOT_ROM_TEXT != ZBOOT_ROM_BSS
	help
	Say Y here if you intend to execute your compressed kernel image
	(zImage) directly from ROM or flash. If unsure, say N.

	config CMDLINE
	string "Default kernel command string"
	default ""
	help
	On some architectures (EBSA110 and CATS), there is currently no way
	for the boot loader to pass arguments to the kernel. For these
	architectures, you should supply some command-line options at build
	time by entering them here. As a minimum, you should specify the
	memory size and the root device (e.g., mem=64M root=/dev/nfs).

	config XIP_KERNEL
	bool "Kernel Execute-In-Place from ROM"
	depends on !ZBOOT_ROM
	help
	Execute-In-Place allows the kernel to run from non-volatile storage
	directly addressable by the CPU, such as NOR flash. This saves RAM
	space since the text section of the kernel is not loaded from flash
	to RAM. Read-write sections, such as the data section and stack,
	are still copied to RAM. The XIP kernel is not compressed since
	it has to run directly from flash, so it will take more space to
	store it. The flash address used to link the kernel object files,
	and for storing it, is configuration dependent. Therefore, if you
	say Y here, you must know the proper physical address where to
	store the kernel image depending on your own flash memory usage.

	Also note that the make target becomes "make xipImage" rather than
	"make zImage" or "make Image". The final kernel binary to put in
	ROM memory will be arch/arm/boot/xipImage.

	If unsure, say N.

	config XIP_PHYS_ADDR
	hex "XIP Kernel Physical Location"
	depends on XIP_KERNEL
	default "0x00080000"
	help
	This is the physical address in your flash memory the kernel will
	be linked for and stored to. This address is dependent on your
	own flash usage.

	endmenu

	if (ARCH_SA1100 \|\| ARCH_INTEGRATOR)

	menu "CPU Frequency scaling"

	source "drivers/cpufreq/Kconfig"

	config CPU_FREQ_SA1100
	bool
	depends on CPU_FREQ && (SA1100_H3100 \|\| SA1100_H3600 \|\| SA1100_H3800 \|\| SA1100_LART \|\| SA1100_PLEB \|\| SA1100_BADGE4 \|\| SA1100_HACKKIT)
	default y

	config CPU_FREQ_SA1110
	bool
	depends on CPU_FREQ && (SA1100_ASSABET \|\| SA1100_CERF \|\| SA1100_PT_SYSTEM3)
	default y

	config CPU_FREQ_INTEGRATOR
	tristate "CPUfreq driver for ARM Integrator CPUs"
	depends on ARCH_INTEGRATOR && CPU_FREQ
	default y
	help
	This enables the CPUfreq driver for ARM Integrator CPUs.

	For details, take a look at <file:Documentation/cpu-freq>.

	If in doubt, say Y.

	endmenu

	endif

	menu "Floating point emulation"

	comment "At least one emulation must be selected"

	config FPE_NWFPE
	bool "NWFPE math emulation"
	---help---
	Say Y to include the NWFPE floating point emulator in the kernel.
	This is necessary to run most binaries. Linux does not currently
	support floating point hardware so you need to say Y here even if
	your machine has an FPA or floating point co-processor podule.

	You may say N here if you are going to load the Acorn FPEmulator
	early in the bootup.

	config FPE_NWFPE_XP
	bool "Support extended precision"
	depends on FPE_NWFPE && !CPU_BIG_ENDIAN
	help
	Say Y to include 80-bit support in the kernel floating-point
	emulator. Otherwise, only 32 and 64-bit support is compiled in.
	Note that gcc does not generate 80-bit operations by default,
	so in most cases this option only enlarges the size of the
	floating point emulator without any good reason.

	You almost surely want to say N here.

	config FPE_FASTFPE
	bool "FastFPE math emulation (EXPERIMENTAL)"
	depends on !CPU_32v3 && EXPERIMENTAL
	---help---
	Say Y here to include the FAST floating point emulator in the kernel.
	This is an experimental much faster emulator which now also has full
	precision for the mantissa. It does not support any exceptions.
	It is very simple, and approximately 3-6 times faster than NWFPE.

	It should be sufficient for most programs. It may be not suitable
	for scientific calculations, but you have to check this for yourself.
	If you do not feel you need a faster FP emulation you should better
	choose NWFPE.

	config VFP
	bool "VFP-format floating point maths"
	depends on CPU_V6 \|\| CPU_ARM926T
	help
	Say Y to include VFP support code in the kernel. This is needed
	if your hardware includes a VFP unit.

	Please see <file:Documentation/arm/VFP/release-notes.txt> for
	release notes and additional status information.

	Say N if your target does not have VFP hardware.

	endmenu

	menu "Userspace binary formats"

	source "fs/Kconfig.binfmt"

	config ARTHUR
	tristate "RISC OS personality"
	help
	Say Y here to include the kernel code necessary if you want to run
	Acorn RISC OS/Arthur binaries under Linux. This code is still very
	experimental; if this sounds frightening, say N and sleep in peace.
	You can also say M here to compile this support as a module (which
	will be called arthur).

	endmenu

	menu "Power management options"

	config PM
	bool "Power Management support"
	---help---
	"Power Management" means that parts of your computer are shut
	off or put into a power conserving "sleep" mode if they are not
	being used. There are two competing standards for doing this: APM
	and ACPI. If you want to use either one, say Y here and then also
	to the requisite support below.

	Power Management is most important for battery powered laptop
	computers; if you have a laptop, check out the Linux Laptop home
	page on the WWW at <http://www.linux-on-laptops.com/> or
	Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>
	and the Battery Powered Linux mini-HOWTO, available from
	<http://www.tldp.org/docs.html#howto>.

	Note that, even if you say N here, Linux on the x86 architecture
	will issue the hlt instruction if nothing is to be done, thereby
	sending the processor to sleep and saving power.

	config APM
	tristate "Advanced Power Management Emulation"
	depends on PM
	---help---
	APM is a BIOS specification for saving power using several different
	techniques. This is mostly useful for battery powered laptops with
	APM compliant BIOSes. If you say Y here, the system time will be
	reset after a RESUME operation, the /proc/apm device will provide
	battery status information, and user-space programs will receive
	notification of APM "events" (e.g. battery status change).

	If you select "Y" here, you can disable actual use of the APM
	BIOS by passing the "apm=off" option to the kernel at boot time.

	Note that the APM support is almost completely disabled for
	machines with more than one CPU.

	In order to use APM, you will need supporting software. For location
	and more information, read <file:Documentation/pm.txt> and the
	Battery Powered Linux mini-HOWTO, available from
	<http://www.tldp.org/docs.html#howto>.

	This driver does not spin down disk drives (see the hdparm(8)
	manpage ("man 8 hdparm") for that), and it doesn't turn off
	VESA-compliant "green" monitors.

	This driver does not support the TI 4000M TravelMate and the ACER
	486/DX4/75 because they don't have compliant BIOSes. Many "green"
	desktop machines also don't have compliant BIOSes, and this driver
	may cause those machines to panic during the boot phase.

	Generally, if you don't have a battery in your machine, there isn't
	much point in using this driver and you should say N. If you get
	random kernel OOPSes or reboots that don't seem to be related to
	anything, try disabling/enabling this option (or disabling/enabling
	APM in your BIOS).

	Some other things you should try when experiencing seemingly random,
	"weird" problems:

	1) make sure that you have enough swap space and that it is
	enabled.
	2) pass the "no-hlt" option to the kernel
	3) switch on floating point emulation in the kernel and pass
	the "no387" option to the kernel
	4) pass the "floppy=nodma" option to the kernel
	5) pass the "mem=4M" option to the kernel (thereby disabling
	all but the first 4 MB of RAM)
	6) make sure that the CPU is not over clocked.
	7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
	8) disable the cache from your BIOS settings
	9) install a fan for the video card or exchange video RAM
	10) install a better fan for the CPU
	11) exchange RAM chips
	12) exchange the motherboard.

	To compile this driver as a module, choose M here: the
	module will be called apm.

	endmenu

	menu "Device Drivers"

	source "drivers/base/Kconfig"

	if ALIGNMENT_TRAP
	source "drivers/mtd/Kconfig"
	endif

	source "drivers/parport/Kconfig"

	source "drivers/pnp/Kconfig"

	source "drivers/block/Kconfig"

	source "drivers/acorn/block/Kconfig"

	if PCMCIA \|\| ARCH_CLPS7500 \|\| ARCH_IOP3XX \|\| ARCH_IXP4XX \
	\|\| ARCH_L7200 \|\| ARCH_LH7A40X \|\| ARCH_PXA \|\| ARCH_RPC \
	\|\| ARCH_S3C2410 \|\| ARCH_SA1100 \|\| ARCH_SHARK \|\| FOOTBRIDGE
	source "drivers/ide/Kconfig"
	endif

	source "drivers/scsi/Kconfig"

	source "drivers/md/Kconfig"

	source "drivers/message/fusion/Kconfig"

	source "drivers/ieee1394/Kconfig"

	source "drivers/message/i2o/Kconfig"

	source "net/Kconfig"

	source "drivers/isdn/Kconfig"

	# input before char - char/joystick depends on it. As does USB.

	source "drivers/input/Kconfig"

	source "drivers/char/Kconfig"

	source "drivers/i2c/Kconfig"

	#source "drivers/l3/Kconfig"

	source "drivers/misc/Kconfig"

	source "drivers/media/Kconfig"

	source "drivers/video/Kconfig"

	source "sound/Kconfig"

	source "drivers/usb/Kconfig"

	source "drivers/mmc/Kconfig"

	endmenu

	source "fs/Kconfig"

	source "arch/arm/oprofile/Kconfig"

	source "arch/arm/Kconfig.debug"

	source "security/Kconfig"

	source "crypto/Kconfig"

	source "lib/Kconfig"