kbuild: silence CHK/UPD messages according to $(quiet)
[linux-block.git] / arch / xtensa / Kconfig
CommitLineData
8e1a6dd2 1# For a description of the syntax of this configuration file,
e403149c 2# see Documentation/kbuild/kconfig-language.txt.
8e1a6dd2
CZ
3
4mainmenu "Linux/Xtensa Kernel Configuration"
5
6config FRAME_POINTER
7 bool
8 default n
9
66701b14
CL
10config ZONE_DMA
11 bool
12 default y
13
8e1a6dd2
CZ
14config XTENSA
15 bool
16 default y
17 help
18 Xtensa processors are 32-bit RISC machines designed by Tensilica
19 primarily for embedded systems. These processors are both
20 configurable and extensible. The Linux port to the Xtensa
21 architecture supports all processor configurations and extensions,
22 with reasonable minimum requirements. The Xtensa Linux project has
23 a home page at <http://xtensa.sourceforge.net/>.
24
8e1a6dd2
CZ
25config RWSEM_XCHGADD_ALGORITHM
26 bool
27 default y
28
d4337aa5
AM
29config GENERIC_FIND_NEXT_BIT
30 bool
31 default y
32
33config GENERIC_HWEIGHT
34 bool
35 default y
36
8e1a6dd2
CZ
37config GENERIC_HARDIRQS
38 bool
39 default y
40
f0d1b0b3
DH
41config ARCH_HAS_ILOG2_U32
42 bool
43 default n
44
45config ARCH_HAS_ILOG2_U64
46 bool
47 default n
48
5ea81769
AV
49config NO_IOPORT
50 def_bool y
51
bdc80787
PA
52config HZ
53 int
54 default 100
55
8e1a6dd2
CZ
56source "init/Kconfig"
57
58menu "Processor type and features"
59
60choice
61 prompt "Xtensa Processor Configuration"
173d6681 62 default XTENSA_VARIANT_FSF
8e1a6dd2 63
173d6681
CZ
64config XTENSA_VARIANT_FSF
65 bool "fsf"
8e1a6dd2
CZ
66endchoice
67
68config MMU
69 bool
70 default y
71
72config XTENSA_UNALIGNED_USER
73 bool "Unaligned memory access in use space"
74 ---help---
75 The Xtensa architecture currently does not handle unaligned
76 memory accesses in hardware but through an exception handler.
77 Per default, unaligned memory accesses are disabled in user space.
78
79 Say Y here to enable unaligned memory access in user space.
80
81config PREEMPT
82 bool "Preemptible Kernel"
83 ---help---
84 This option reduces the latency of the kernel when reacting to
85 real-time or interactive events by allowing a low priority process to
86 be preempted even if it is in kernel mode executing a system call.
87 Unfortunately the kernel code has some race conditions if both
88 CONFIG_SMP and CONFIG_PREEMPT are enabled, so this option is
89 currently disabled if you are building an SMP kernel.
90
91 Say Y here if you are building a kernel for a desktop, embedded
92 or real-time system. Say N if you are unsure.
93
94config MATH_EMULATION
95 bool "Math emulation"
96 help
97 Can we use information of configuration file?
98
99config HIGHMEM
100 bool "High memory support"
101
102endmenu
103
104menu "Platform options"
105
106choice
107 prompt "Xtensa System Type"
108 default XTENSA_PLATFORM_ISS
109
110config XTENSA_PLATFORM_ISS
111 bool "ISS"
112 help
113 ISS is an acronym for Tensilica's Instruction Set Simulator.
114
115config XTENSA_PLATFORM_XT2000
116 bool "XT2000"
117 help
118 XT2000 is the name of Tensilica's feature-rich emulation platform.
119 This hardware is capable of running a full Linux distribution.
120
121endchoice
122
123
124config XTENSA_CALIBRATE_CCOUNT
125 bool "Auto calibration of the CPU clock rate"
126 ---help---
127 On some platforms (XT2000, for example), the CPU clock rate can
128 vary. The frequency can be determined, however, by measuring
129 against a well known, fixed frequency, such as an UART oscillator.
130
131config XTENSA_CPU_CLOCK
132 int "CPU clock rate [MHz]"
133 depends on !XTENSA_CALIBRATE_CCOUNT
134 default "16"
135
136config GENERIC_CALIBRATE_DELAY
137 bool "Auto calibration of the BogoMIPS value"
138 ---help---
82300bf4 139 The BogoMIPS value can easily be derived from the CPU frequency.
8e1a6dd2
CZ
140
141config CMDLINE_BOOL
142 bool "Default bootloader kernel arguments"
143
144config CMDLINE
145 string "Initial kernel command string"
146 depends on CMDLINE_BOOL
147 default "console=ttyS0,38400 root=/dev/ram"
148 help
149 On some architectures (EBSA110 and CATS), there is currently no way
150 for the boot loader to pass arguments to the kernel. For these
151 architectures, you should supply some command-line options at build
152 time by entering them here. As a minimum, you should specify the
153 memory size and the root device (e.g., mem=64M root=/dev/nfs).
154
155config SERIAL_CONSOLE
156 bool
157 depends on XTENSA_PLATFORM_ISS
158 default y
159
160config XTENSA_ISS_NETWORK
161 bool
162 depends on XTENSA_PLATFORM_ISS
163 default y
164
82300bf4
CZ
165source "mm/Kconfig"
166
8e1a6dd2
CZ
167endmenu
168
169menu "Bus options"
170
171config PCI
172 bool "PCI support" if !XTENSA_PLATFORM_ISS
173 depends on !XTENSA_PLATFORM_ISS
174 default y
175 help
176 Find out whether you have a PCI motherboard. PCI is the name of a
177 bus system, i.e. the way the CPU talks to the other stuff inside
178 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
179 VESA. If you have PCI, say Y, otherwise N.
180
8e1a6dd2
CZ
181source "drivers/pci/Kconfig"
182
183config HOTPLUG
184
185 bool "Support for hot-pluggable devices"
186 ---help---
187 Say Y here if you want to plug devices into your computer while
188 the system is running, and be able to use them quickly. In many
189 cases, the devices can likewise be unplugged at any time too.
190
191 One well known example of this is PCMCIA- or PC-cards, credit-card
192 size devices such as network cards, modems or hard drives which are
193 plugged into slots found on all modern laptop computers. Another
194 example, used on modern desktops as well as laptops, is USB.
195
196 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
197 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
198 Then your kernel will automatically call out to a user mode "policy
199 agent" (/sbin/hotplug) to load modules and set up software needed
200 to use devices as you hotplug them.
201
202source "drivers/pcmcia/Kconfig"
203
204source "drivers/pci/hotplug/Kconfig"
205
206endmenu
207
cab00891 208menu "Executable file formats"
8e1a6dd2
CZ
209
210# only elf supported
211config KCORE_ELF
212 bool
213 depends on PROC_FS
214 default y
215 help
216 If you enabled support for /proc file system then the file
217 /proc/kcore will contain the kernel core image in ELF format. This
218 can be used in gdb:
219
220 $ cd /usr/src/linux ; gdb vmlinux /proc/kcore
221
222 This is especially useful if you have compiled the kernel with the
223 "-g" option to preserve debugging information. It is mainly used
224 for examining kernel data structures on the live kernel.
225
226source "fs/Kconfig.binfmt"
227
228endmenu
229
d5950b43
SR
230source "net/Kconfig"
231
8e1a6dd2
CZ
232source "drivers/Kconfig"
233
234source "fs/Kconfig"
235
236menu "Xtensa initrd options"
237 depends on BLK_DEV_INITRD
238
239 config EMBEDDED_RAMDISK
240 bool "Embed root filesystem ramdisk into the kernel"
241
242config EMBEDDED_RAMDISK_IMAGE
cab00891 243 string "Filename of gzipped ramdisk image"
8e1a6dd2
CZ
244 depends on EMBEDDED_RAMDISK
245 default "ramdisk.gz"
246 help
247 This is the filename of the ramdisk image to be built into the
248 kernel. Relative pathnames are relative to arch/xtensa/boot/ramdisk/.
249 The ramdisk image is not part of the kernel distribution; you must
250 provide one yourself.
251endmenu
252
253source "arch/xtensa/Kconfig.debug"
254
255source "security/Kconfig"
256
257source "crypto/Kconfig"
258
259source "lib/Kconfig"
260
261