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