1 # SPDX-License-Identifier: GPL-2.0 !! 1 #
2 config XTENSA !! 2 # For a description of the syntax of this configuration file,
3 def_bool y !! 3 # see Documentation/kbuild/kconfig-language.txt.
4 select ARCH_32BIT_OFF_T !! 4 #
5 select ARCH_HAS_CPU_CACHE_ALIASING !! 5 config ALPHA
6 select ARCH_HAS_BINFMT_FLAT if !MMU !! 6 bool
7 select ARCH_HAS_CURRENT_STACK_POINTER !! 7 default y
8 select ARCH_HAS_DEBUG_VM_PGTABLE !! 8 help
9 select ARCH_HAS_DMA_PREP_COHERENT if M !! 9 The Alpha is a 64-bit general-purpose processor designed and
10 select ARCH_HAS_GCOV_PROFILE_ALL !! 10 marketed by the Digital Equipment Corporation of blessed memory,
11 select ARCH_HAS_KCOV !! 11 now Hewlett-Packard. The Alpha Linux project has a home page at
12 select ARCH_HAS_SYNC_DMA_FOR_CPU if MM !! 12 <http://www.alphalinux.org/>.
13 select ARCH_HAS_SYNC_DMA_FOR_DEVICE if <<
14 select ARCH_HAS_DMA_SET_UNCACHED if MM <<
15 select ARCH_HAS_STRNCPY_FROM_USER if ! <<
16 select ARCH_HAS_STRNLEN_USER <<
17 select ARCH_NEED_CMPXCHG_1_EMU <<
18 select ARCH_USE_MEMTEST <<
19 select ARCH_USE_QUEUED_RWLOCKS <<
20 select ARCH_USE_QUEUED_SPINLOCKS <<
21 select ARCH_WANT_IPC_PARSE_VERSION <<
22 select BUILDTIME_TABLE_SORT <<
23 select CLONE_BACKWARDS <<
24 select COMMON_CLK <<
25 select DMA_NONCOHERENT_MMAP if MMU <<
26 select GENERIC_ATOMIC64 <<
27 select GENERIC_IRQ_SHOW <<
28 select GENERIC_LIB_CMPDI2 <<
29 select GENERIC_LIB_MULDI3 <<
30 select GENERIC_LIB_UCMPDI2 <<
31 select GENERIC_PCI_IOMAP <<
32 select GENERIC_SCHED_CLOCK <<
33 select GENERIC_IOREMAP if MMU <<
34 select HAVE_ARCH_AUDITSYSCALL <<
35 select HAVE_ARCH_JUMP_LABEL if !XIP_KE <<
36 select HAVE_ARCH_KASAN if MMU && !XIP_ <<
37 select HAVE_ARCH_KCSAN <<
38 select HAVE_ARCH_SECCOMP_FILTER <<
39 select HAVE_ARCH_TRACEHOOK <<
40 select HAVE_ASM_MODVERSIONS <<
41 select HAVE_CONTEXT_TRACKING_USER <<
42 select HAVE_DEBUG_KMEMLEAK <<
43 select HAVE_DMA_CONTIGUOUS <<
44 select HAVE_EXIT_THREAD <<
45 select HAVE_FUNCTION_TRACER <<
46 select HAVE_GCC_PLUGINS if GCC_VERSION <<
47 select HAVE_HW_BREAKPOINT if PERF_EVEN <<
48 select HAVE_IRQ_TIME_ACCOUNTING <<
49 select HAVE_PAGE_SIZE_4KB <<
50 select HAVE_PCI <<
51 select HAVE_PERF_EVENTS <<
52 select HAVE_STACKPROTECTOR <<
53 select HAVE_SYSCALL_TRACEPOINTS <<
54 select HAVE_VIRT_CPU_ACCOUNTING_GEN <<
55 select IRQ_DOMAIN <<
56 select LOCK_MM_AND_FIND_VMA <<
57 select MODULES_USE_ELF_RELA <<
58 select PERF_USE_VMALLOC <<
59 select TRACE_IRQFLAGS_SUPPORT <<
60 help <<
61 Xtensa processors are 32-bit RISC ma <<
62 primarily for embedded systems. The <<
63 configurable and extensible. The Li <<
64 architecture supports all processor <<
65 with reasonable minimum requirements <<
66 a home page at <http://www.linux-xte <<
67 13
68 config GENERIC_HWEIGHT !! 14 config 64BIT
69 def_bool y 15 def_bool y
70 16
71 config ARCH_HAS_ILOG2_U32 !! 17 config MMU
72 def_bool n !! 18 bool
>> 19 default y
73 20
74 config ARCH_HAS_ILOG2_U64 !! 21 config UID16
75 def_bool n !! 22 bool
76 23
77 config ARCH_MTD_XIP !! 24 config RWSEM_GENERIC_SPINLOCK
78 def_bool y !! 25 bool
79 26
80 config NO_IOPORT_MAP !! 27 config RWSEM_XCHGADD_ALGORITHM
81 def_bool n !! 28 bool
>> 29 default y
82 30
83 config HZ !! 31 config GENERIC_ISA_DMA
84 int !! 32 bool
85 default 100 !! 33 default y
86 34
87 config LOCKDEP_SUPPORT !! 35 source "init/Kconfig"
88 def_bool y <<
89 36
90 config STACKTRACE_SUPPORT <<
91 def_bool y <<
92 37
93 config MMU !! 38 menu "System setup"
94 def_bool n <<
95 select PFAULT <<
96 39
97 config HAVE_XTENSA_GPIO32 !! 40 choice
98 def_bool n !! 41 prompt "Alpha system type"
>> 42 default ALPHA_GENERIC
>> 43 ---help---
>> 44 This is the system type of your hardware. A "generic" kernel will
>> 45 run on any supported Alpha system. However, if you configure a
>> 46 kernel for your specific system, it will be faster and smaller.
99 47
100 config KASAN_SHADOW_OFFSET !! 48 To find out what type of Alpha system you have, you may want to
101 hex !! 49 check out the Linux/Alpha FAQ, accessible on the WWW from
102 default 0x6e400000 !! 50 <http://www.alphalinux.org/>. In summary:
103 51
104 config CPU_BIG_ENDIAN !! 52 Alcor/Alpha-XLT AS 600
105 def_bool $(success,test "$(shell,echo !! 53 Alpha-XL XL-233, XL-266
>> 54 AlphaBook1 Alpha laptop
>> 55 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, AS 400
>> 56 Cabriolet AlphaPC64, AlphaPCI64
>> 57 DP264 DP264
>> 58 EB164 EB164 21164 evaluation board
>> 59 EB64+ EB64+ 21064 evaluation board
>> 60 EB66 EB66 21066 evaluation board
>> 61 EB66+ EB66+ 21066 evaluation board
>> 62 Jensen DECpc 150, DEC 2000 model 300,
>> 63 DEC 2000 model 500
>> 64 LX164 AlphaPC164-LX
>> 65 Lynx AS 2100A
>> 66 Miata Personal Workstation 433a, 433au, 500a,
>> 67 500au, 600a, or 600au
>> 68 Marvel AlphaServer ES47 / ES80 / GS1280
>> 69 Mikasa AS 1000
>> 70 Noname AXPpci33, UDB (Multia)
>> 71 Noritake AS 1000A, AS 600A, AS 800
>> 72 PC164 AlphaPC164
>> 73 Rawhide AS 1200, AS 4000, AS 4100
>> 74 Ruffian RPX164-2, AlphaPC164-UX, AlphaPC164-BX
>> 75 SX164 AlphaPC164-SX
>> 76 Sable AS 2000, AS 2100
>> 77 Shark DS 20L
>> 78 Takara Takara
>> 79 Titan AlphaServer ES45 / DS25
>> 80 Wildfire AlphaServer GS 40/80/160/320
106 81
107 config CPU_LITTLE_ENDIAN !! 82 If you don't know what to do, choose "generic".
108 def_bool !CPU_BIG_ENDIAN !! 83
>> 84 config ALPHA_GENERIC
>> 85 bool "Generic"
>> 86 help
>> 87 A generic kernel will run on all supported Alpha hardware.
109 88
110 config CC_HAVE_CALL0_ABI !! 89 config ALPHA_ALCOR
111 def_bool $(success,test "$(shell,echo !! 90 bool "Alcor/Alpha-XLT"
>> 91 help
>> 92 For systems using the Digital ALCOR chipset: 5 chips (4, 64-bit data
>> 93 slices (Data Switch, DSW) - 208-pin PQFP and 1 control (Control, I/O
>> 94 Address, CIA) - a 383 pin plastic PGA). It provides a DRAM
>> 95 controller (256-bit memory bus) and a PCI interface. It also does
>> 96 all the work required to support an external Bcache and to maintain
>> 97 memory coherence when a PCI device DMAs into (or out of) memory.
112 98
113 menu "Processor type and features" !! 99 config ALPHA_XL
>> 100 bool "Alpha-XL"
>> 101 help
>> 102 XL-233 and XL-266-based Alpha systems.
114 103
115 choice !! 104 config ALPHA_BOOK1
116 prompt "Xtensa Processor Configuration !! 105 bool "AlphaBook1"
117 default XTENSA_VARIANT_FSF !! 106 help
>> 107 Dec AlphaBook1/Burns Alpha-based laptops.
118 108
119 config XTENSA_VARIANT_FSF !! 109 config ALPHA_AVANTI_CH
120 bool "fsf - default (not generic) conf !! 110 bool "Avanti"
121 select MMU <<
122 111
123 config XTENSA_VARIANT_DC232B !! 112 config ALPHA_CABRIOLET
124 bool "dc232b - Diamond 232L Standard C !! 113 bool "Cabriolet"
125 select MMU <<
126 select HAVE_XTENSA_GPIO32 <<
127 help 114 help
128 This variant refers to Tensilica's D !! 115 Cabriolet AlphaPC64, AlphaPCI64 systems. Derived from EB64+ but now
>> 116 baby-AT with Flash boot ROM, no on-board SCSI or Ethernet. 3 ISA
>> 117 slots, 4 PCI slots (one pair are on a shared slot), uses plug-in
>> 118 Bcache SIMMs. Requires power supply with 3.3V output.
129 119
130 config XTENSA_VARIANT_DC233C !! 120 config ALPHA_DP264
131 bool "dc233c - Diamond 233L Standard C !! 121 bool "DP264"
132 select MMU <<
133 select HAVE_XTENSA_GPIO32 <<
134 help 122 help
135 This variant refers to Tensilica's D !! 123 Various 21264 systems with the tsunami core logic chipset.
>> 124 API Networks: 264DP, UP2000(+), CS20;
>> 125 Compaq: DS10(E,L), XP900, XP1000, DS20(E), ES40.
136 126
137 config XTENSA_VARIANT_CUSTOM !! 127 config ALPHA_EB164
138 bool "Custom Xtensa processor configur !! 128 bool "EB164"
139 select HAVE_XTENSA_GPIO32 <<
140 help 129 help
141 Select this variant to use a custom !! 130 EB164 21164 evaluation board from DEC. Uses 21164 and ALCOR. Has
142 You will be prompted for a processor !! 131 ISA and PCI expansion (3 ISA slots, 2 64-bit PCI slots (one is
143 endchoice !! 132 shared with an ISA slot) and 2 32-bit PCI slots. Uses plus-in
>> 133 Bcache SIMMs. I/O sub-system provides SuperI/O (2S, 1P, FD), KBD,
>> 134 MOUSE (PS2 style), RTC/NVRAM. Boot ROM is Flash. PC-AT-sized
>> 135 motherboard. Requires power supply with 3.3V output.
144 136
145 config XTENSA_VARIANT_CUSTOM_NAME !! 137 config ALPHA_EB64P_CH
146 string "Xtensa Processor Custom Core V !! 138 bool "EB64+"
147 depends on XTENSA_VARIANT_CUSTOM !! 139
148 help !! 140 config ALPHA_EB66
149 Provide the name of a custom Xtensa !! 141 bool "EB66"
150 This CORENAME selects arch/xtensa/va <<
151 Don't forget you have to select MMU <<
152 <<
153 config XTENSA_VARIANT_NAME <<
154 string <<
155 default "dc232b" <<
156 default "dc233c" <<
157 default "fsf" <<
158 default XTENSA_VARIANT_CUSTOM_NAME <<
159 <<
160 config XTENSA_VARIANT_MMU <<
161 bool "Core variant has a Full MMU (TLB <<
162 depends on XTENSA_VARIANT_CUSTOM <<
163 default y <<
164 select MMU <<
165 help <<
166 Build a Conventional Kernel with ful <<
167 ie: it supports a TLB with auto-load <<
168 <<
169 config XTENSA_VARIANT_HAVE_PERF_EVENTS <<
170 bool "Core variant has Performance Mon <<
171 depends on XTENSA_VARIANT_CUSTOM <<
172 default n <<
173 help 142 help
174 Enable if core variant has Performan !! 143 A Digital DS group board. Uses 21066 or 21066A. I/O sub-system is
175 External Registers Interface. !! 144 identical to EB64+. Baby PC-AT size. Runs from standard PC power
>> 145 supply. The EB66 schematic was published as a marketing poster
>> 146 advertising the 21066 as "the first microprocessor in the world with
>> 147 embedded PCI".
176 148
177 If unsure, say N. !! 149 config ALPHA_EB66P
>> 150 bool "EB66+"
>> 151 help
>> 152 Later variant of the EB66 board.
178 153
179 config XTENSA_FAKE_NMI !! 154 config ALPHA_EIGER
180 bool "Treat PMM IRQ as NMI" !! 155 bool "Eiger"
181 depends on XTENSA_VARIANT_HAVE_PERF_EV <<
182 default n <<
183 help 156 help
184 If PMM IRQ is the only IRQ at EXCM l !! 157 Apparently an obscure OEM single-board computer based on the
185 treat it as NMI, which improves accu !! 158 Typhoon/Tsunami chipset family. Information on it is scanty.
186 159
187 If there are other interrupts at or !! 160 config ALPHA_JENSEN
188 but not above the EXCM level, PMM IR !! 161 bool "Jensen"
189 but only if these IRQs are not used. !! 162 help
190 saying that this is not safe, and a !! 163 DEC PC 150 AXP (aka Jensen): This is a very old Digital system - one
191 actually fire. !! 164 of the first-generation Alpha systems. A number of these systems
>> 165 seem to be available on the second- hand market. The Jensen is a
>> 166 floor-standing tower system which originally used a 150MHz 21064 It
>> 167 used programmable logic to interface a 486 EISA I/O bridge to the
>> 168 CPU.
192 169
193 If unsure, say N. !! 170 config ALPHA_LX164
>> 171 bool "LX164"
>> 172 help
>> 173 A technical overview of this board is available at
>> 174 <http://www.unix-ag.org/Linux-Alpha/Architectures/LX164.html>.
194 175
195 config PFAULT !! 176 config ALPHA_LYNX
196 bool "Handle protection faults" if EXP !! 177 bool "Lynx"
197 default y <<
198 help 178 help
199 Handle protection faults. MMU config !! 179 AlphaServer 2100A-based systems.
200 noMMU configurations may disable it <<
201 generates protection faults or fault <<
202 180
203 If unsure, say Y. !! 181 config ALPHA_MARVEL
>> 182 bool "Marvel"
>> 183 help
>> 184 AlphaServer ES47 / ES80 / GS1280 based on EV7.
204 185
205 config XTENSA_UNALIGNED_USER !! 186 config ALPHA_MIATA
206 bool "Unaligned memory access in user !! 187 bool "Miata"
207 help 188 help
208 The Xtensa architecture currently do !! 189 The Digital PersonalWorkStation (PWS 433a, 433au, 500a, 500au, 600a,
209 memory accesses in hardware but thro !! 190 or 600au). There is an Installation HOWTO for this hardware at
210 Per default, unaligned memory access !! 191 <http://members.brabant.chello.nl/~s.vandereijk/miata.html>.
211 192
212 Say Y here to enable unaligned memor !! 193 config ALPHA_MIKASA
>> 194 bool "Mikasa"
>> 195 help
>> 196 AlphaServer 1000-based Alpha systems.
213 197
214 config XTENSA_LOAD_STORE !! 198 config ALPHA_NAUTILUS
215 bool "Load/store exception handler for !! 199 bool "Nautilus"
216 help 200 help
217 The Xtensa architecture only allows !! 201 Alpha systems based on the AMD 751 & ALI 1543C chipsets.
218 instruction bus with l32r and l32i i <<
219 instructions raise an exception with <<
220 This makes it hard to use some confi <<
221 literals in FLASH memory attached to <<
222 202
223 Say Y here to enable exception handl !! 203 config ALPHA_NONAME_CH
224 byte and 2-byte access to memory att !! 204 bool "Noname"
225 205
226 config HAVE_SMP !! 206 config ALPHA_NORITAKE
227 bool "System Supports SMP (MX)" !! 207 bool "Noritake"
228 depends on XTENSA_VARIANT_CUSTOM <<
229 select XTENSA_MX <<
230 help 208 help
231 This option is used to indicate that !! 209 AlphaServer 1000A, AlphaServer 600A, and AlphaServer 800-based
232 supports Multiprocessing. Multiproce !! 210 systems.
233 the CPU core definition and currentl <<
234 211
235 Multiprocessor support is implemente !! 212 config ALPHA_PC164
236 interrupt controllers. !! 213 bool "PC164"
237 214
238 The MX interrupt distributer adds In !! 215 config ALPHA_P2K
239 and causes the IRQ numbers to be inc !! 216 bool "Platform2000"
240 like the open cores ethernet driver <<
241 217
242 You still have to select "Enable SMP !! 218 config ALPHA_RAWHIDE
>> 219 bool "Rawhide"
>> 220 help
>> 221 AlphaServer 1200, AlphaServer 4000 and AlphaServer 4100 machines.
>> 222 See HOWTO at
>> 223 <http://www.alphalinux.org/docs/rawhide/4100_install.shtml>.
243 224
244 config SMP !! 225 config ALPHA_RUFFIAN
245 bool "Enable Symmetric multi-processin !! 226 bool "Ruffian"
246 depends on HAVE_SMP <<
247 select GENERIC_SMP_IDLE_THREAD <<
248 help 227 help
249 Enabled SMP Software; allows more th !! 228 Samsung APC164UX. There is a page on known problems and workarounds
250 to be activated during startup. !! 229 at <http://www.alphalinux.org/faq/FAQ-11.html>.
251 230
252 config NR_CPUS !! 231 config ALPHA_RX164
253 depends on SMP !! 232 bool "RX164"
254 int "Maximum number of CPUs (2-32)" <<
255 range 2 32 <<
256 default "4" <<
257 233
258 config HOTPLUG_CPU !! 234 config ALPHA_SX164
259 bool "Enable CPU hotplug support" !! 235 bool "SX164"
260 depends on SMP !! 236
>> 237 config ALPHA_SABLE
>> 238 bool "Sable"
261 help 239 help
262 Say Y here to allow turning CPUs off !! 240 Digital AlphaServer 2000 and 2100-based systems.
263 controlled through /sys/devices/syst <<
264 241
265 Say N if you want to disable CPU hot !! 242 config ALPHA_SHARK
>> 243 bool "Shark"
266 244
267 config SECONDARY_RESET_VECTOR !! 245 config ALPHA_TAKARA
268 bool "Secondary cores use alternative !! 246 bool "Takara"
269 default y <<
270 depends on HAVE_SMP <<
271 help 247 help
272 Secondary cores may be configured to !! 248 Alpha 11164-based OEM single-board computer.
273 or all cores may use primary reset v <<
274 Say Y here to supply handler for the <<
275 249
276 config FAST_SYSCALL_XTENSA !! 250 config ALPHA_TITAN
277 bool "Enable fast atomic syscalls" !! 251 bool "Titan"
278 default n <<
279 help 252 help
280 fast_syscall_xtensa is a syscall tha !! 253 AlphaServer ES45/DS25 SMP based on EV68 and Titan chipset.
281 on UP kernel when processor has no s <<
282 254
283 This syscall is deprecated. It may h !! 255 config ALPHA_WILDFIRE
284 invalid arguments. It is provided on !! 256 bool "Wildfire"
285 Only enable it if your userspace sof !! 257 help
>> 258 AlphaServer GS 40/80/160/320 SMP based on the EV67 core.
286 259
287 If unsure, say N. !! 260 endchoice
288 261
289 config FAST_SYSCALL_SPILL_REGISTERS !! 262 # clear all implied options (don't want default values for those):
290 bool "Enable spill registers syscall" !! 263 # Most of these machines have ISA slots; not exactly sure which don't,
291 default n !! 264 # and this doesn't activate hordes of code, so do it always.
>> 265 config ISA
>> 266 bool
>> 267 default y
292 help 268 help
293 fast_syscall_spill_registers is a sy !! 269 Find out whether you have ISA slots on your motherboard. ISA is the
294 register windows of a calling usersp !! 270 name of a bus system, i.e. the way the CPU talks to the other stuff
>> 271 inside your box. Other bus systems are PCI, EISA, MicroChannel
>> 272 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
>> 273 newer boards don't support it. If you have ISA, say Y, otherwise N.
295 274
296 This syscall is deprecated. It may h !! 275 config PCI
297 invalid arguments. It is provided on !! 276 bool
298 Only enable it if your userspace sof !! 277 depends on !ALPHA_JENSEN
>> 278 default y
>> 279 help
>> 280 Find out whether you have a PCI motherboard. PCI is the name of a
>> 281 bus system, i.e. the way the CPU talks to the other stuff inside
>> 282 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
>> 283 VESA. If you have PCI, say Y, otherwise N.
>> 284
>> 285 The PCI-HOWTO, available from
>> 286 <http://www.tldp.org/docs.html#howto>, contains valuable
>> 287 information about which PCI hardware does work under Linux and which
>> 288 doesn't.
299 289
300 If unsure, say N. !! 290 config PCI_DOMAINS
>> 291 bool
>> 292 default y
301 293
302 choice !! 294 config ALPHA_CORE_AGP
303 prompt "Kernel ABI" !! 295 bool
304 default KERNEL_ABI_DEFAULT !! 296 depends on ALPHA_GENERIC || ALPHA_TITAN || ALPHA_MARVEL
>> 297 default y
>> 298
>> 299 config ALPHA_NONAME
>> 300 bool
>> 301 depends on ALPHA_BOOK1 || ALPHA_NONAME_CH
>> 302 default y
305 help 303 help
306 Select ABI for the kernel code. This !! 304 The AXPpci33 (aka NoName), is based on the EB66 (includes the Multia
307 supported userspace ABI and any comb !! 305 UDB). This design was produced by Digital's Technical OEM (TOEM)
308 kernel/userspace ABI is possible and !! 306 group. It uses the 21066 processor running at 166MHz or 233MHz. It
309 !! 307 is a baby-AT size, and runs from a standard PC power supply. It has
310 In case both kernel and userspace su !! 308 5 ISA slots and 3 PCI slots (one pair are a shared slot). There are
311 all register windows support code wi !! 309 2 versions, with either PS/2 or large DIN connectors for the
312 build. !! 310 keyboard.
313 <<
314 If unsure, choose the default ABI. <<
315 <<
316 config KERNEL_ABI_DEFAULT <<
317 bool "Default ABI" <<
318 help <<
319 Select this option to compile kernel <<
320 selected for the toolchain. <<
321 Normally cores with windowed registe <<
322 cores without it use call0 ABI. <<
323 <<
324 config KERNEL_ABI_CALL0 <<
325 bool "Call0 ABI" if CC_HAVE_CALL0_ABI <<
326 help <<
327 Select this option to compile kernel <<
328 toolchain that defaults to windowed <<
329 When this option is not selected the <<
330 be used for the kernel code. <<
331 311
332 endchoice !! 312 config ALPHA_EV4
>> 313 bool
>> 314 depends on ALPHA_JENSEN || (ALPHA_SABLE && !ALPHA_GAMMA) || ALPHA_LYNX || ALPHA_NORITAKE && !ALPHA_PRIMO || ALPHA_MIKASA && !ALPHA_PRIMO || ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P_CH || ALPHA_XL || ALPHA_NONAME || ALPHA_EB66 || ALPHA_EB66P || ALPHA_P2K
>> 315 default y if !ALPHA_LYNX
>> 316
>> 317 config ALPHA_LCA
>> 318 bool
>> 319 depends on ALPHA_NONAME || ALPHA_EB66 || ALPHA_EB66P || ALPHA_P2K
>> 320 default y
333 321
334 config USER_ABI_CALL0 !! 322 config ALPHA_APECS
335 bool 323 bool
>> 324 depends on !ALPHA_PRIMO && (ALPHA_NORITAKE || ALPHA_MIKASA) || ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P_CH || ALPHA_XL
>> 325 default y
336 326
337 choice !! 327 config ALPHA_EB64P
338 prompt "Userspace ABI" !! 328 bool
339 default USER_ABI_DEFAULT !! 329 depends on ALPHA_CABRIOLET || ALPHA_EB64P_CH
>> 330 default y
340 help 331 help
341 Select supported userspace ABI. !! 332 Uses 21064 or 21064A and APECs. Has ISA and PCI expansion (3 ISA,
>> 333 2 PCI, one pair are on a shared slot). Supports 36-bit DRAM SIMs.
>> 334 ISA bus generated by Intel SaturnI/O PCI-ISA bridge. On-board SCSI
>> 335 (NCR 810 on PCI) Ethernet (Digital 21040), KBD, MOUSE (PS2 style),
>> 336 SuperI/O (2S, 1P, FD), RTC/NVRAM. Boot ROM is EPROM. PC-AT size.
>> 337 Runs from standard PC power supply.
>> 338
>> 339 config ALPHA_EV5
>> 340 bool "EV5 CPU(s) (model 5/xxx)?" if ALPHA_LYNX
>> 341 default y if ALPHA_RX164 || ALPHA_RAWHIDE || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN || ALPHA_SABLE && ALPHA_GAMMA || ALPHA_NORITAKE && ALPHA_PRIMO || ALPHA_MIKASA && ALPHA_PRIMO || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR
>> 342
>> 343 config ALPHA_EV4
>> 344 bool
>> 345 default y if ALPHA_LYNX && !ALPHA_EV5
>> 346
>> 347 config ALPHA_CIA
>> 348 bool
>> 349 depends on ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN || ALPHA_NORITAKE && ALPHA_PRIMO || ALPHA_MIKASA && ALPHA_PRIMO || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR
>> 350 default y
>> 351
>> 352 config ALPHA_EV56
>> 353 bool "EV56 CPU (speed >= 366MHz)?" if ALPHA_ALCOR
>> 354 default y if ALPHA_RX164 || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN || ALPHA_PC164 || ALPHA_TAKARA
>> 355
>> 356 config ALPHA_EV56
>> 357 prompt "EV56 CPU (speed >= 333MHz)?"
>> 358 depends on ALPHA_NORITAKE && ALPHA_PRIMO
342 359
343 If unsure, choose the default ABI. !! 360 config ALPHA_EV56
>> 361 prompt "EV56 CPU (speed >= 400MHz)?"
>> 362 depends on ALPHA_RAWHIDE
344 363
345 config USER_ABI_DEFAULT !! 364 config ALPHA_PRIMO
346 bool "Default ABI only" !! 365 bool "EV5 CPU daughtercard (model 5/xxx)?"
>> 366 depends on ALPHA_NORITAKE || ALPHA_MIKASA
347 help 367 help
348 Assume default userspace ABI. For XE !! 368 Say Y if you have an AS 1000 5/xxx or an AS 1000A 5/xxx.
349 call0 ABI binaries may be run on suc <<
350 will not work correctly for them. <<
351 369
352 config USER_ABI_CALL0_ONLY !! 370 config ALPHA_GAMMA
353 bool "Call0 ABI only" !! 371 bool "EV5 CPU(s) (model 5/xxx)?"
354 select USER_ABI_CALL0 !! 372 depends on ALPHA_SABLE
355 help 373 help
356 Select this option to support only c !! 374 Say Y if you have an AS 2000 5/xxx or an AS 2100 5/xxx.
357 Windowed ABI binaries will crash wit !! 375
358 an illegal instruction exception on !! 376 config ALPHA_GAMMA
>> 377 bool
>> 378 depends on ALPHA_LYNX
>> 379 default y
>> 380
>> 381 config ALPHA_T2
>> 382 bool
>> 383 depends on ALPHA_SABLE || ALPHA_LYNX
>> 384 default y
>> 385
>> 386 config ALPHA_PYXIS
>> 387 bool
>> 388 depends on ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_RUFFIAN
>> 389 default y
>> 390
>> 391 config ALPHA_EV6
>> 392 bool
>> 393 depends on ALPHA_NAUTILUS || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK || ALPHA_DP264 || ALPHA_EIGER || ALPHA_MARVEL
>> 394 default y
359 395
360 Choose this option if you're plannin !! 396 config ALPHA_TSUNAMI
361 built with call0 ABI. !! 397 bool
>> 398 depends on ALPHA_SHARK || ALPHA_DP264 || ALPHA_EIGER
>> 399 default y
362 400
363 config USER_ABI_CALL0_PROBE !! 401 config ALPHA_EV67
364 bool "Support both windowed and call0 !! 402 bool "EV67 (or later) CPU (speed > 600MHz)?" if ALPHA_DP264 || ALPHA_EIGER
365 select USER_ABI_CALL0 !! 403 default y if ALPHA_NAUTILUS || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK || ALPHA_MARVEL
366 help 404 help
367 Select this option to support both w !! 405 Is this a machine based on the EV67 core? If in doubt, select N here
368 ABIs. When enabled all processes are !! 406 and the machine will be treated as an EV6.
369 and a fast user exception handler fo <<
370 used to turn on PS.WOE bit on the fi <<
371 the userspace. <<
372 407
373 This option should be enabled for th !! 408 config ALPHA_EV7
374 both call0 and windowed ABIs in user !! 409 bool
>> 410 depends on ALPHA_MARVEL
>> 411 default y
375 412
376 Note that Xtensa ISA does not guaran !! 413 config ALPHA_MCPCIA
377 raise an illegal instruction excepti !! 414 bool
378 PS.WOE is disabled, check whether th !! 415 depends on ALPHA_RAWHIDE
>> 416 default y
379 417
380 endchoice !! 418 config ALPHA_POLARIS
>> 419 bool
>> 420 depends on ALPHA_RX164
>> 421 default y
381 422
382 endmenu !! 423 config ALPHA_IRONGATE
>> 424 bool
>> 425 depends on ALPHA_NAUTILUS
>> 426 default y
383 427
384 config XTENSA_CALIBRATE_CCOUNT !! 428 config ALPHA_AVANTI
385 def_bool n !! 429 bool
>> 430 depends on ALPHA_XL || ALPHA_AVANTI_CH
>> 431 default y
386 help 432 help
387 On some platforms (XT2000, for examp !! 433 Avanti AS 200, AS 205, AS 250, AS 255, AS 300, and AS 400-based
388 vary. The frequency can be determin !! 434 Alphas. Info at
389 against a well known, fixed frequenc !! 435 <http://www.unix-ag.org/Linux-Alpha/Architectures/Avanti.html>.
390 436
391 config SERIAL_CONSOLE !! 437 config ALPHA_BROKEN_IRQ_MASK
392 def_bool n !! 438 bool
>> 439 depends on ALPHA_GENERIC || ALPHA_PC164
>> 440 default y
393 441
394 config PLATFORM_HAVE_XIP !! 442 config ALPHA_SRM
395 def_bool n !! 443 bool "Use SRM as bootloader" if ALPHA_CABRIOLET || ALPHA_AVANTI_CH || ALPHA_EB64P || ALPHA_PC164 || ALPHA_TAKARA || ALPHA_EB164 || ALPHA_ALCOR || ALPHA_MIATA || ALPHA_LX164 || ALPHA_SX164 || ALPHA_NAUTILUS || ALPHA_NONAME
>> 444 default y if ALPHA_JENSEN || ALPHA_MIKASA || ALPHA_SABLE || ALPHA_LYNX || ALPHA_NORITAKE || ALPHA_DP264 || ALPHA_RAWHIDE || ALPHA_EIGER || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_SHARK || ALPHA_MARVEL
>> 445 ---help---
>> 446 There are two different types of booting firmware on Alphas: SRM,
>> 447 which is command line driven, and ARC, which uses menus and arrow
>> 448 keys. Details about the Linux/Alpha booting process are contained in
>> 449 the Linux/Alpha FAQ, accessible on the WWW from
>> 450 <http://www.alphalinux.org/>.
>> 451
>> 452 The usual way to load Linux on an Alpha machine is to use MILO
>> 453 (a bootloader that lets you pass command line parameters to the
>> 454 kernel just like lilo does for the x86 architecture) which can be
>> 455 loaded either from ARC or can be installed directly as a permanent
>> 456 firmware replacement from floppy (which requires changing a certain
>> 457 jumper on the motherboard). If you want to do either of these, say N
>> 458 here. If MILO doesn't work on your system (true for Jensen
>> 459 motherboards), you can bypass it altogether and boot Linux directly
>> 460 from an SRM console; say Y here in order to do that. Note that you
>> 461 won't be able to boot from an IDE disk using SRM.
396 462
397 menu "Platform options" !! 463 If unsure, say N.
398 464
399 choice !! 465 config EARLY_PRINTK
400 prompt "Xtensa System Type" !! 466 bool
401 default XTENSA_PLATFORM_ISS !! 467 depends on ALPHA_GENERIC || ALPHA_SRM
>> 468 default y
402 469
403 config XTENSA_PLATFORM_ISS !! 470 config EISA
404 bool "ISS" !! 471 bool
405 select XTENSA_CALIBRATE_CCOUNT !! 472 depends on ALPHA_GENERIC || ALPHA_JENSEN || ALPHA_ALCOR || ALPHA_MIKASA || ALPHA_SABLE || ALPHA_LYNX || ALPHA_NORITAKE || ALPHA_RAWHIDE
406 select SERIAL_CONSOLE !! 473 default y
407 help <<
408 ISS is an acronym for Tensilica's In <<
409 <<
410 config XTENSA_PLATFORM_XT2000 <<
411 bool "XT2000" <<
412 help <<
413 XT2000 is the name of Tensilica's fe <<
414 This hardware is capable of running <<
415 <<
416 config XTENSA_PLATFORM_XTFPGA <<
417 bool "XTFPGA" <<
418 select ETHOC if ETHERNET <<
419 select PLATFORM_WANT_DEFAULT_MEM if !M <<
420 select SERIAL_CONSOLE <<
421 select XTENSA_CALIBRATE_CCOUNT <<
422 select PLATFORM_HAVE_XIP <<
423 help <<
424 XTFPGA is the name of Tensilica boar <<
425 This hardware is capable of running <<
426 474
427 endchoice !! 475 config SMP
>> 476 bool "Symmetric multi-processing support"
>> 477 depends on ALPHA_SABLE || ALPHA_LYNX || ALPHA_RAWHIDE || ALPHA_DP264 || ALPHA_WILDFIRE || ALPHA_TITAN || ALPHA_GENERIC || ALPHA_SHARK || ALPHA_MARVEL
>> 478 ---help---
>> 479 This enables support for systems with more than one CPU. If you have
>> 480 a system with only one CPU, like most personal computers, say N. If
>> 481 you have a system with more than one CPU, say Y.
>> 482
>> 483 If you say N here, the kernel will run on single and multiprocessor
>> 484 machines, but will use only one CPU of a multiprocessor machine. If
>> 485 you say Y here, the kernel will run on many, but not all,
>> 486 singleprocessor machines. On a singleprocessor machine, the kernel
>> 487 will run faster if you say N here.
>> 488
>> 489 Note that if you say Y here and choose architecture "586" or
>> 490 "Pentium" under "Processor family", the kernel will not work on 486
>> 491 architectures. Similarly, multiprocessor kernels for the "PPro"
>> 492 architecture may not work on all Pentium based boards.
>> 493
>> 494 People using multiprocessor machines who say Y here should also say
>> 495 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
>> 496 Management" code will be disabled if you say Y here.
>> 497
>> 498 See also the <file:Documentation/smp.tex>,
>> 499 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
>> 500 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
>> 501 <http://www.tldp.org/docs.html#howto>.
428 502
429 config PLATFORM_NR_IRQS !! 503 If you don't know what to do here, say N.
430 int <<
431 default 3 if XTENSA_PLATFORM_XT2000 <<
432 default 0 <<
433 504
434 config XTENSA_CPU_CLOCK !! 505 config HAVE_DEC_LOCK
435 int "CPU clock rate [MHz]" !! 506 bool
436 depends on !XTENSA_CALIBRATE_CCOUNT !! 507 depends on SMP
437 default 16 !! 508 default y
438 509
439 config GENERIC_CALIBRATE_DELAY !! 510 config NR_CPUS
440 bool "Auto calibration of the BogoMIPS !! 511 int "Maximum number of CPUs (2-64)"
441 help !! 512 depends on SMP
442 The BogoMIPS value can easily be der !! 513 default "64"
443 514
444 config CMDLINE_BOOL !! 515 config DISCONTIGMEM
445 bool "Default bootloader kernel argume !! 516 bool "Discontiguous Memory Support (EXPERIMENTAL)"
>> 517 depends on EXPERIMENTAL
>> 518 help
>> 519 Say Y to upport efficient handling of discontiguous physical memory,
>> 520 for architectures which are either NUMA (Non-Uniform Memory Access)
>> 521 or have huge holes in the physical address space for other reasons.
>> 522 See <file:Documentation/vm/numa> for more.
>> 523
>> 524 config NUMA
>> 525 bool "NUMA Support (EXPERIMENTAL)"
>> 526 depends on DISCONTIGMEM
>> 527 help
>> 528 Say Y to compile the kernel to support NUMA (Non-Uniform Memory
>> 529 Access). This option is for configuring high-end multiprocessor
>> 530 server machines. If in doubt, say N.
446 531
447 config CMDLINE !! 532 # LARGE_VMALLOC is racy, if you *really* need it then fix it first
448 string "Initial kernel command string" !! 533 config ALPHA_LARGE_VMALLOC
449 depends on CMDLINE_BOOL !! 534 bool
450 default "console=ttyS0,38400 root=/dev !! 535 ---help---
451 help !! 536 Process creation and other aspects of virtual memory management can
452 On some architectures (EBSA110 and C !! 537 be streamlined if we restrict the kernel to one PGD for all vmalloc
453 for the boot loader to pass argument !! 538 allocations. This equates to about 8GB.
454 architectures, you should supply som !! 539
455 time by entering them here. As a min !! 540 Under normal circumstances, this is so far and above what is needed
456 memory size and the root device (e.g !! 541 as to be laughable. However, there are certain applications (such
>> 542 as benchmark-grade in-kernel web serving) that can make use of as
>> 543 much vmalloc space as is available.
>> 544
>> 545 Say N unless you know you need gobs and gobs of vmalloc space.
>> 546
>> 547 config VERBOSE_MCHECK
>> 548 bool "Verbose Machine Checks"
>> 549
>> 550 config VERBOSE_MCHECK_ON
>> 551 int "Verbose Printing Mode (0=off, 1=on, 2=all)"
>> 552 depends on VERBOSE_MCHECK
>> 553 default 1
>> 554 ---help---
>> 555 This option allows the default printing mode to be set, and then
>> 556 possibly overridden by a boot command argument.
>> 557
>> 558 For example, if one wanted the option of printing verbose
>> 559 machine checks, but wanted the default to be as if verbose
>> 560 machine check printing was turned off, then one would choose
>> 561 the printing mode to be 0. Then, upon reboot, one could add
>> 562 the boot command line "verbose_mcheck=1" to get the normal
>> 563 verbose machine check printing, or "verbose_mcheck=2" to get
>> 564 the maximum information available.
>> 565
>> 566 Take the default (1) unless you want more control or more info.
>> 567
>> 568 source "drivers/pci/Kconfig"
>> 569 source "drivers/eisa/Kconfig"
>> 570
>> 571 config HOTPLUG
>> 572 bool "Support for hot-pluggable devices"
>> 573 ---help---
>> 574 Say Y here if you want to plug devices into your computer while
>> 575 the system is running, and be able to use them quickly. In many
>> 576 cases, the devices can likewise be unplugged at any time too.
>> 577
>> 578 One well known example of this is PCMCIA- or PC-cards, credit-card
>> 579 size devices such as network cards, modems or hard drives which are
>> 580 plugged into slots found on all modern laptop computers. Another
>> 581 example, used on modern desktops as well as laptops, is USB.
>> 582
>> 583 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
>> 584 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
>> 585 Then your kernel will automatically call out to a user mode "policy
>> 586 agent" (/sbin/hotplug) to load modules and set up software needed
>> 587 to use devices as you hotplug them.
>> 588
>> 589 source "drivers/pcmcia/Kconfig"
>> 590
>> 591 config SRM_ENV
>> 592 tristate "SRM environment through procfs"
>> 593 depends on PROC_FS
>> 594 ---help---
>> 595 If you enable this option, a subdirectory inside /proc called
>> 596 /proc/srm_environment will give you access to the all important
>> 597 SRM environment variables (those which have a name) and also
>> 598 to all others (by their internal number).
>> 599
>> 600 SRM is something like a BIOS for Alpha machines. There are some
>> 601 other such BIOSes, like AlphaBIOS, which this driver cannot
>> 602 support (hey, that's not SRM!).
>> 603
>> 604 Despite the fact that this driver doesn't work on all Alphas (but
>> 605 only on those which have SRM as their firmware), it's save to
>> 606 build it even if your particular machine doesn't know about SRM
>> 607 (or if you intend to compile a generic kernel). It will simply
>> 608 not create those subdirectory in /proc (and give you some warning,
>> 609 of course).
457 610
458 config USE_OF !! 611 This driver is also available as a module and will be called
459 bool "Flattened Device Tree support" !! 612 srm_env then.
460 select OF <<
461 select OF_EARLY_FLATTREE <<
462 help <<
463 Include support for flattened device <<
464 613
465 config BUILTIN_DTB_SOURCE !! 614 source "fs/Kconfig.binfmt"
466 string "DTB to build into the kernel i <<
467 depends on OF <<
468 615
469 config PARSE_BOOTPARAM !! 616 source "drivers/parport/Kconfig"
470 bool "Parse bootparam block" <<
471 default y <<
472 help <<
473 Parse parameters passed to the kerne <<
474 be disabled if the kernel is known t <<
475 617
476 If unsure, say Y. !! 618 endmenu
477 619
478 choice !! 620 source "drivers/base/Kconfig"
479 prompt "Semihosting interface" <<
480 default XTENSA_SIMCALL_ISS <<
481 depends on XTENSA_PLATFORM_ISS <<
482 help <<
483 Choose semihosting interface that wi <<
484 block device and networking. <<
485 621
486 config XTENSA_SIMCALL_ISS !! 622 source "drivers/mtd/Kconfig"
487 bool "simcall" <<
488 help <<
489 Use simcall instruction. simcall is <<
490 it does nothing on hardware. <<
491 623
492 config XTENSA_SIMCALL_GDBIO !! 624 source "drivers/pnp/Kconfig"
493 bool "GDBIO" <<
494 help <<
495 Use break instruction. It is availab <<
496 is attached to it via JTAG. <<
497 625
498 endchoice !! 626 source "drivers/block/Kconfig"
499 627
500 config BLK_DEV_SIMDISK !! 628 source "drivers/md/Kconfig"
501 tristate "Host file-based simulated bl <<
502 default n <<
503 depends on XTENSA_PLATFORM_ISS && BLOC <<
504 help <<
505 Create block devices that map to fil <<
506 Device binding to host file may be c <<
507 interface provided the device is not <<
508 <<
509 config BLK_DEV_SIMDISK_COUNT <<
510 int "Number of host file-based simulat <<
511 range 1 10 <<
512 depends on BLK_DEV_SIMDISK <<
513 default 2 <<
514 help <<
515 This is the default minimal number o <<
516 Kernel/module parameter 'simdisk_cou <<
517 value at runtime. More file names (b <<
518 specified as parameters, simdisk_cou <<
519 <<
520 config SIMDISK0_FILENAME <<
521 string "Host filename for the first si <<
522 depends on BLK_DEV_SIMDISK = y <<
523 default "" <<
524 help <<
525 Attach a first simdisk to a host fil <<
526 contains a root file system. <<
527 <<
528 config SIMDISK1_FILENAME <<
529 string "Host filename for the second s <<
530 depends on BLK_DEV_SIMDISK = y && BLK_ <<
531 default "" <<
532 help <<
533 Another simulated disk in a host fil <<
534 storage. <<
535 <<
536 config XTFPGA_LCD <<
537 bool "Enable XTFPGA LCD driver" <<
538 depends on XTENSA_PLATFORM_XTFPGA <<
539 default n <<
540 help <<
541 There's a 2x16 LCD on most of XTFPGA <<
542 progress messages there during bootu <<
543 during board bringup. <<
544 629
545 If unsure, say N. !! 630 source "drivers/ide/Kconfig"
546 631
547 config XTFPGA_LCD_BASE_ADDR !! 632 source "drivers/scsi/Kconfig"
548 hex "XTFPGA LCD base address" <<
549 depends on XTFPGA_LCD <<
550 default "0x0d0c0000" <<
551 help <<
552 Base address of the LCD controller i <<
553 Different boards from XTFPGA family <<
554 addresses. Please consult prototypin <<
555 the correct address. Wrong address h <<
556 <<
557 config XTFPGA_LCD_8BIT_ACCESS <<
558 bool "Use 8-bit access to XTFPGA LCD" <<
559 depends on XTFPGA_LCD <<
560 default n <<
561 help <<
562 LCD may be connected with 4- or 8-bi <<
563 only be used with 8-bit interface. P <<
564 guide for your board for the correct <<
565 <<
566 comment "Kernel memory layout" <<
567 <<
568 config INITIALIZE_XTENSA_MMU_INSIDE_VMLINUX <<
569 bool "Initialize Xtensa MMU inside the <<
570 depends on !XTENSA_VARIANT_FSF && !XTE <<
571 default y if XTENSA_VARIANT_DC233C || <<
572 help <<
573 Earlier version initialized the MMU <<
574 before jumping to _startup in head.S <<
575 it was possible to place a software <<
576 then enter your normal kernel breakp <<
577 to the kernel mappings (0XC0000000). <<
578 <<
579 This unfortunately won't work for U- <<
580 work for using KEXEC to have a hot k <<
581 KDUMP. <<
582 <<
583 So now the MMU is initialized in hea <<
584 use hardware breakpoints (gdb 'hbrea <<
585 xt-gdb can't place a Software Breakp <<
586 to mapping the MMU and after mapping <<
587 was mapped gdb wouldn't remove the b <<
588 PC wouldn't match. Since Hardware Br <<
589 Linux configurations it seems reason <<
590 and leave this older mechanism for u <<
591 not to follow Tensilica's recommenda <<
592 <<
593 Selecting this will cause U-Boot to <<
594 address at 0x00003000 instead of the <<
595 <<
596 If in doubt, say Y. <<
597 <<
598 config XIP_KERNEL <<
599 bool "Kernel Execute-In-Place from ROM <<
600 depends on PLATFORM_HAVE_XIP <<
601 help <<
602 Execute-In-Place allows the kernel t <<
603 directly addressable by the CPU, suc <<
604 space since the text section of the <<
605 to RAM. Read-write sections, such as <<
606 are still copied to RAM. The XIP ker <<
607 it has to run directly from flash, s <<
608 store it. The flash address used to <<
609 and for storing it, is configuration <<
610 say Y here, you must know the proper <<
611 store the kernel image depending on <<
612 <<
613 Also note that the make target becom <<
614 "make Image" or "make uImage". The f <<
615 ROM memory will be arch/xtensa/boot/ <<
616 633
617 If unsure, say N. !! 634 if PCI
>> 635 source "drivers/message/fusion/Kconfig"
>> 636 endif
618 637
619 config MEMMAP_CACHEATTR !! 638 source "drivers/ieee1394/Kconfig"
620 hex "Cache attributes for the memory a <<
621 depends on !MMU <<
622 default 0x22222222 <<
623 help <<
624 These cache attributes are set up fo <<
625 specifies cache attributes for the c <<
626 region: bits 0..3 -- for addresses 0 <<
627 bits 4..7 -- for addresses 0x2000000 <<
628 <<
629 Cache attribute values are specific <<
630 For region protection MMUs: <<
631 1: WT cached, <<
632 2: cache bypass, <<
633 4: WB cached, <<
634 f: illegal. <<
635 For full MMU: <<
636 bit 0: executable, <<
637 bit 1: writable, <<
638 bits 2..3: <<
639 0: cache bypass, <<
640 1: WB cache, <<
641 2: WT cache, <<
642 3: special (c and e are illegal, <<
643 For MPU: <<
644 0: illegal, <<
645 1: WB cache, <<
646 2: WB, no-write-allocate cache, <<
647 3: WT cache, <<
648 4: cache bypass. <<
649 <<
650 config KSEG_PADDR <<
651 hex "Physical address of the KSEG mapp <<
652 depends on INITIALIZE_XTENSA_MMU_INSID <<
653 default 0x00000000 <<
654 help <<
655 This is the physical address where K <<
656 the chosen KSEG layout help for the <<
657 Unpacked kernel image (including vec <<
658 within KSEG. <<
659 Physical memory below this address i <<
660 <<
661 If unsure, leave the default value h <<
662 <<
663 config KERNEL_VIRTUAL_ADDRESS <<
664 hex "Kernel virtual address" <<
665 depends on MMU && XIP_KERNEL <<
666 default 0xd0003000 <<
667 help <<
668 This is the virtual address where th <<
669 XIP kernel may be mapped into KSEG o <<
670 provided here must match kernel load <<
671 KERNEL_LOAD_ADDRESS. <<
672 <<
673 config KERNEL_LOAD_ADDRESS <<
674 hex "Kernel load address" <<
675 default 0x60003000 if !MMU <<
676 default 0x00003000 if MMU && INITIALIZ <<
677 default 0xd0003000 if MMU && !INITIALI <<
678 help <<
679 This is the address where the kernel <<
680 It is virtual address for MMUv2 conf <<
681 for all other configurations. <<
682 639
683 If unsure, leave the default value h !! 640 source "net/Kconfig"
684 641
685 choice !! 642 source "drivers/isdn/Kconfig"
686 prompt "Relocatable vectors location" <<
687 default XTENSA_VECTORS_IN_TEXT <<
688 help <<
689 Choose whether relocatable vectors a <<
690 or placed separately at runtime. Thi <<
691 configurations without VECBASE regis <<
692 placed at their hardware-defined loc <<
693 <<
694 config XTENSA_VECTORS_IN_TEXT <<
695 bool "Merge relocatable vectors into k <<
696 depends on !MTD_XIP <<
697 help <<
698 This option puts relocatable vectors <<
699 with proper alignment. <<
700 This is a safe choice for most confi <<
701 <<
702 config XTENSA_VECTORS_SEPARATE <<
703 bool "Put relocatable vectors at fixed <<
704 help <<
705 This option puts relocatable vectors <<
706 Vectors are merged with the .init da <<
707 are copied into their designated loc <<
708 Use it to put vectors into IRAM or o <<
709 XIP-aware MTD support. <<
710 643
711 endchoice !! 644 source "drivers/cdrom/Kconfig"
712 645
713 config VECTORS_ADDR !! 646 source "drivers/input/Kconfig"
714 hex "Kernel vectors virtual address" <<
715 default 0x00000000 <<
716 depends on XTENSA_VECTORS_SEPARATE <<
717 help <<
718 This is the virtual address of the ( <<
719 It must be within KSEG if MMU is use <<
720 <<
721 config XIP_DATA_ADDR <<
722 hex "XIP kernel data virtual address" <<
723 depends on XIP_KERNEL <<
724 default 0x00000000 <<
725 help <<
726 This is the virtual address where XI <<
727 It must be within KSEG if MMU is use <<
728 <<
729 config PLATFORM_WANT_DEFAULT_MEM <<
730 def_bool n <<
731 <<
732 config DEFAULT_MEM_START <<
733 hex <<
734 prompt "PAGE_OFFSET/PHYS_OFFSET" if !M <<
735 default 0x60000000 if PLATFORM_WANT_DE <<
736 default 0x00000000 <<
737 help <<
738 This is the base address used for bo <<
739 in noMMU configurations. <<
740 647
741 If unsure, leave the default value h !! 648 source "drivers/char/Kconfig"
742 649
743 choice !! 650 #source drivers/misc/Config.in
744 prompt "KSEG layout" !! 651 source "drivers/media/Kconfig"
745 depends on MMU <<
746 default XTENSA_KSEG_MMU_V2 <<
747 <<
748 config XTENSA_KSEG_MMU_V2 <<
749 bool "MMUv2: 128MB cached + 128MB unca <<
750 help <<
751 MMUv2 compatible kernel memory map: <<
752 at KSEG_PADDR to 0xd0000000 with cac <<
753 without cache. <<
754 KSEG_PADDR must be aligned to 128MB. <<
755 <<
756 config XTENSA_KSEG_256M <<
757 bool "256MB cached + 256MB uncached" <<
758 depends on INITIALIZE_XTENSA_MMU_INSID <<
759 help <<
760 TLB way 6 maps 256MB starting at KSE <<
761 with cache and to 0xc0000000 without <<
762 KSEG_PADDR must be aligned to 256MB. <<
763 <<
764 config XTENSA_KSEG_512M <<
765 bool "512MB cached + 512MB uncached" <<
766 depends on INITIALIZE_XTENSA_MMU_INSID <<
767 help <<
768 TLB way 6 maps 512MB starting at KSE <<
769 with cache and to 0xc0000000 without <<
770 KSEG_PADDR must be aligned to 256MB. <<
771 652
772 endchoice !! 653 source "fs/Kconfig"
773 654
774 config HIGHMEM !! 655 source "drivers/video/Kconfig"
775 bool "High Memory Support" <<
776 depends on MMU <<
777 select KMAP_LOCAL <<
778 help <<
779 Linux can use the full amount of RAM <<
780 default. However, the default MMUv2 <<
781 lowermost 128 MB of memory linearly <<
782 at 0xd0000000 (cached) and 0xd800000 <<
783 When there are more than 128 MB memo <<
784 all of it can be "permanently mapped <<
785 The physical memory that's not perma <<
786 "high memory". <<
787 <<
788 If you are compiling a kernel which <<
789 machine with more than 128 MB total <<
790 N here. <<
791 <<
792 If unsure, say Y. <<
793 <<
794 config ARCH_FORCE_MAX_ORDER <<
795 int "Order of maximal physically conti <<
796 default "10" <<
797 help <<
798 The kernel page allocator limits the <<
799 contiguous allocations. The limit is <<
800 defines the maximal power of two of <<
801 allocated as a single contiguous blo <<
802 overriding the default setting when <<
803 large blocks of physically contiguou <<
804 656
805 Don't change if unsure. !! 657 source "sound/Kconfig"
806 658
807 endmenu !! 659 source "drivers/usb/Kconfig"
808 660
809 menu "Power management options" !! 661 source "arch/alpha/oprofile/Kconfig"
810 662
811 config ARCH_HIBERNATION_POSSIBLE !! 663 menu "Kernel hacking"
812 def_bool y !! 664
>> 665 config ALPHA_LEGACY_START_ADDRESS
>> 666 bool "Legacy kernel start address"
>> 667 depends on ALPHA_GENERIC
>> 668 default n
>> 669 ---help---
>> 670 The 2.4 kernel changed the kernel start address from 0x310000
>> 671 to 0x810000 to make room for the Wildfire's larger SRM console.
>> 672 Recent consoles on Titan and Marvel machines also require the
>> 673 extra room.
>> 674
>> 675 If you're using aboot 0.7 or later, the bootloader will examine the
>> 676 ELF headers to determine where to transfer control. Unfortunately,
>> 677 most older bootloaders -- APB or MILO -- hardcoded the kernel start
>> 678 address rather than examining the ELF headers, and the result is a
>> 679 hard lockup.
813 680
814 source "kernel/power/Kconfig" !! 681 Say Y if you have a broken bootloader. Say N if you do not, or if
>> 682 you wish to run on Wildfire, Titan, or Marvel.
>> 683
>> 684 config ALPHA_LEGACY_START_ADDRESS
>> 685 bool
>> 686 depends on !ALPHA_GENERIC && !ALPHA_TITAN && !ALPHA_MARVEL && !ALPHA_WILDFIRE
>> 687 default y
>> 688
>> 689 config DEBUG_KERNEL
>> 690 bool "Kernel debugging"
>> 691 help
>> 692 Say Y here if you are developing drivers or trying to debug and
>> 693 identify kernel problems.
>> 694
>> 695 config MATHEMU
>> 696 tristate "Kernel FP software completion" if DEBUG_KERNEL
>> 697 default y if !DEBUG_KERNEL
>> 698 help
>> 699 This option is required for IEEE compliant floating point arithmetic
>> 700 on the Alpha. The only time you would ever not say Y is to say M in
>> 701 order to debug the code. Say Y unless you know what you are doing.
>> 702
>> 703 config DEBUG_SLAB
>> 704 bool "Debug memory allocations"
>> 705 depends on DEBUG_KERNEL
>> 706 help
>> 707 Say Y here to have the kernel do limited verification on memory
>> 708 allocation as well as poisoning memory on free to catch use of freed
>> 709 memory.
>> 710
>> 711 config MAGIC_SYSRQ
>> 712 bool "Magic SysRq key"
>> 713 depends on DEBUG_KERNEL
>> 714 help
>> 715 If you say Y here, you will have some control over the system even
>> 716 if the system crashes for example during kernel debugging (e.g., you
>> 717 will be able to flush the buffer cache to disk, reboot the system
>> 718 immediately or dump some status information). This is accomplished
>> 719 by pressing various keys while holding SysRq (Alt+PrintScreen). It
>> 720 also works on a serial console (on PC hardware at least), if you
>> 721 send a BREAK and then within 5 seconds a command keypress. The
>> 722 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
>> 723 unless you really know what this hack does.
>> 724
>> 725 config DEBUG_SPINLOCK
>> 726 bool "Spinlock debugging"
>> 727 depends on DEBUG_KERNEL
>> 728 help
>> 729 Say Y here and build SMP to catch missing spinlock initialization
>> 730 and certain other kinds of spinlock errors commonly made. This is
>> 731 best used in conjunction with the NMI watchdog so that spinlock
>> 732 deadlocks are also debuggable.
>> 733
>> 734 config DEBUG_RWLOCK
>> 735 bool "Read-write spinlock debugging"
>> 736 depends on DEBUG_KERNEL
>> 737 help
>> 738 If you say Y here then read-write lock processing will count how many
>> 739 times it has tried to get the lock and issue an error message after
>> 740 too many attempts. If you suspect a rwlock problem or a kernel
>> 741 hacker asks for this option then say Y. Otherwise say N.
>> 742
>> 743 config DEBUG_SEMAPHORE
>> 744 bool "Semaphore debugging"
>> 745 depends on DEBUG_KERNEL
>> 746 help
>> 747 If you say Y here then semaphore processing will issue lots of
>> 748 verbose debugging messages. If you suspect a semaphore problem or a
>> 749 kernel hacker asks for this option then say Y. Otherwise say N.
>> 750
>> 751 config DEBUG_INFO
>> 752 bool "Compile the kernel with debug info"
>> 753 depends on DEBUG_KERNEL
>> 754 help
>> 755 If you say Y here the resulting kernel image will include
>> 756 debugging info resulting in a larger kernel image.
>> 757 Say Y here only if you plan to use gdb to debug the kernel.
>> 758 If you don't debug the kernel, you can say N.
815 759
816 endmenu 760 endmenu
>> 761
>> 762 source "security/Kconfig"
>> 763
>> 764 source "crypto/Kconfig"
>> 765
>> 766 source "lib/Kconfig"
>> 767
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.