1 # SPDX-License-Identifier: GPL-2.0 !! 1 # $Id: config.in,v 1.113 2002/01/24 22:14:44 davem Exp $
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 <<
6 select ARCH_HAS_BINFMT_FLAT if !MMU <<
7 select ARCH_HAS_CURRENT_STACK_POINTER <<
8 select ARCH_HAS_DEBUG_VM_PGTABLE <<
9 select ARCH_HAS_DMA_PREP_COHERENT if M <<
10 select ARCH_HAS_GCOV_PROFILE_ALL <<
11 select ARCH_HAS_KCOV <<
12 select ARCH_HAS_SYNC_DMA_FOR_CPU if MM <<
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 <<
68 config GENERIC_HWEIGHT <<
69 def_bool y <<
70 <<
71 config ARCH_HAS_ILOG2_U32 <<
72 def_bool n <<
73 <<
74 config ARCH_HAS_ILOG2_U64 <<
75 def_bool n <<
76 <<
77 config ARCH_MTD_XIP <<
78 def_bool y <<
79 <<
80 config NO_IOPORT_MAP <<
81 def_bool n <<
82 <<
83 config HZ <<
84 int <<
85 default 100 <<
86 5
87 config LOCKDEP_SUPPORT !! 6 mainmenu "Linux/SPARC Kernel Configuration"
88 def_bool y <<
89 <<
90 config STACKTRACE_SUPPORT <<
91 def_bool y <<
92 7
93 config MMU 8 config MMU
94 def_bool n !! 9 bool
95 select PFAULT !! 10 default y
96 <<
97 config HAVE_XTENSA_GPIO32 <<
98 def_bool n <<
99 <<
100 config KASAN_SHADOW_OFFSET <<
101 hex <<
102 default 0x6e400000 <<
103 11
104 config CPU_BIG_ENDIAN !! 12 config UID16
105 def_bool $(success,test "$(shell,echo !! 13 bool
>> 14 default y
106 15
107 config CPU_LITTLE_ENDIAN !! 16 config HIGHMEM
108 def_bool !CPU_BIG_ENDIAN !! 17 bool
>> 18 default y
109 19
110 config CC_HAVE_CALL0_ABI !! 20 config GENERIC_ISA_DMA
111 def_bool $(success,test "$(shell,echo !! 21 bool
>> 22 default y
112 23
113 menu "Processor type and features" !! 24 source "init/Kconfig"
114 25
115 choice <<
116 prompt "Xtensa Processor Configuration <<
117 default XTENSA_VARIANT_FSF <<
118 26
119 config XTENSA_VARIANT_FSF !! 27 menu "General setup"
120 bool "fsf - default (not generic) conf <<
121 select MMU <<
122 28
123 config XTENSA_VARIANT_DC232B !! 29 config VT
124 bool "dc232b - Diamond 232L Standard C !! 30 bool
125 select MMU !! 31 default y
126 select HAVE_XTENSA_GPIO32 !! 32 ---help---
127 help !! 33 If you say Y here, you will get support for terminal devices with
128 This variant refers to Tensilica's D !! 34 display and keyboard devices. These are called "virtual" because you
129 !! 35 can run several virtual terminals (also called virtual consoles) on
130 config XTENSA_VARIANT_DC233C !! 36 one physical terminal. This is rather useful, for example one
131 bool "dc233c - Diamond 233L Standard C !! 37 virtual terminal can collect system messages and warnings, another
132 select MMU !! 38 one can be used for a text-mode user session, and a third could run
133 select HAVE_XTENSA_GPIO32 !! 39 an X session, all in parallel. Switching between virtual terminals
134 help !! 40 is done with certain key combinations, usually Alt-<function key>.
135 This variant refers to Tensilica's D !! 41
>> 42 The setterm command ("man setterm") can be used to change the
>> 43 properties (such as colors or beeping) of a virtual terminal. The
>> 44 man page console_codes(4) ("man console_codes") contains the special
>> 45 character sequences that can be used to change those properties
>> 46 directly. The fonts used on virtual terminals can be changed with
>> 47 the setfont ("man setfont") command and the key bindings are defined
>> 48 with the loadkeys ("man loadkeys") command.
>> 49
>> 50 You need at least one virtual terminal device in order to make use
>> 51 of your keyboard and monitor. Therefore, only people configuring an
>> 52 embedded system would want to say N here in order to save some
>> 53 memory; the only way to log into such a system is then via a serial
>> 54 or network connection.
136 55
137 config XTENSA_VARIANT_CUSTOM !! 56 If unsure, say Y, or else you won't be able to do much with your new
138 bool "Custom Xtensa processor configur !! 57 shiny Linux system :-)
139 select HAVE_XTENSA_GPIO32 <<
140 help <<
141 Select this variant to use a custom <<
142 You will be prompted for a processor <<
143 endchoice <<
144 58
145 config XTENSA_VARIANT_CUSTOM_NAME !! 59 config VT_CONSOLE
146 string "Xtensa Processor Custom Core V !! 60 bool
147 depends on XTENSA_VARIANT_CUSTOM !! 61 default y
148 help !! 62 ---help---
149 Provide the name of a custom Xtensa !! 63 The system console is the device which receives all kernel messages
150 This CORENAME selects arch/xtensa/va !! 64 and warnings and which allows logins in single user mode. If you
151 Don't forget you have to select MMU !! 65 answer Y here, a virtual terminal (the device used to interact with
>> 66 a physical terminal) can be used as system console. This is the most
>> 67 common mode of operations, so you should say Y here unless you want
>> 68 the kernel messages be output only to a serial port (in which case
>> 69 you should say Y to "Console on serial port", below).
>> 70
>> 71 If you do say Y here, by default the currently visible virtual
>> 72 terminal (/dev/tty0) will be used as system console. You can change
>> 73 that with a kernel command line option such as "console=tty3" which
>> 74 would use the third virtual terminal as system console. (Try "man
>> 75 bootparam" or see the documentation of your boot loader (lilo or
>> 76 loadlin) about how to pass options to the kernel at boot time.)
152 77
153 config XTENSA_VARIANT_NAME !! 78 If unsure, say Y.
154 string <<
155 default "dc232b" <<
156 default "dc233c" <<
157 default "fsf" <<
158 default XTENSA_VARIANT_CUSTOM_NAME <<
159 79
160 config XTENSA_VARIANT_MMU !! 80 config HW_CONSOLE
161 bool "Core variant has a Full MMU (TLB !! 81 bool
162 depends on XTENSA_VARIANT_CUSTOM <<
163 default y 82 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 <<
174 Enable if core variant has Performan <<
175 External Registers Interface. <<
176 83
177 If unsure, say N. !! 84 config SMP
>> 85 bool "Symmetric multi-processing support (does not work on sun4/sun4c)"
>> 86 ---help---
>> 87 This enables support for systems with more than one CPU. If you have
>> 88 a system with only one CPU, like most personal computers, say N. If
>> 89 you have a system with more than one CPU, say Y.
>> 90
>> 91 If you say N here, the kernel will run on single and multiprocessor
>> 92 machines, but will use only one CPU of a multiprocessor machine. If
>> 93 you say Y here, the kernel will run on many, but not all,
>> 94 singleprocessor machines. On a singleprocessor machine, the kernel
>> 95 will run faster if you say N here.
>> 96
>> 97 Note that if you say Y here and choose architecture "586" or
>> 98 "Pentium" under "Processor family", the kernel will not work on 486
>> 99 architectures. Similarly, multiprocessor kernels for the "PPro"
>> 100 architecture may not work on all Pentium based boards.
>> 101
>> 102 People using multiprocessor machines who say Y here should also say
>> 103 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
>> 104 Management" code will be disabled if you say Y here.
>> 105
>> 106 See also the <file:Documentation/smp.tex>,
>> 107 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
>> 108 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
>> 109 <http://www.tldp.org/docs.html#howto>.
178 110
179 config XTENSA_FAKE_NMI !! 111 If you don't know what to do here, say N.
180 bool "Treat PMM IRQ as NMI" <<
181 depends on XTENSA_VARIANT_HAVE_PERF_EV <<
182 default n <<
183 help <<
184 If PMM IRQ is the only IRQ at EXCM l <<
185 treat it as NMI, which improves accu <<
186 <<
187 If there are other interrupts at or <<
188 but not above the EXCM level, PMM IR <<
189 but only if these IRQs are not used. <<
190 saying that this is not safe, and a <<
191 actually fire. <<
192 112
193 If unsure, say N. !! 113 config NR_CPUS
>> 114 int "Maximum number of CPUs (2-32)"
>> 115 depends on SMP
>> 116 default "32"
194 117
195 config PFAULT !! 118 # Identify this as a Sparc32 build
196 bool "Handle protection faults" if EXP !! 119 config SPARC32
>> 120 bool
197 default y 121 default y
198 help 122 help
199 Handle protection faults. MMU config !! 123 SPARC is a family of RISC microprocessors designed and marketed by
200 noMMU configurations may disable it !! 124 Sun Microsystems, incorporated. They are very widely found in Sun
201 generates protection faults or fault !! 125 workstations and clones. This port covers the original 32-bit SPARC;
202 !! 126 it is old and stable and usually considered one of the "big three"
203 If unsure, say Y. !! 127 along with the Intel and Alpha ports. The UltraLinux project
204 !! 128 maintains both the SPARC32 and SPARC64 ports; its web page is
205 config XTENSA_UNALIGNED_USER !! 129 available at <http://www.ultralinux.org/>.
206 bool "Unaligned memory access in user <<
207 help <<
208 The Xtensa architecture currently do <<
209 memory accesses in hardware but thro <<
210 Per default, unaligned memory access <<
211 <<
212 Say Y here to enable unaligned memor <<
213 130
214 config XTENSA_LOAD_STORE !! 131 # Global things across all Sun machines.
215 bool "Load/store exception handler for !! 132 config ISA
>> 133 bool
216 help 134 help
217 The Xtensa architecture only allows !! 135 ISA is found on Espresso only and is not supported currently.
218 instruction bus with l32r and l32i i !! 136 Say N
219 instructions raise an exception with <<
220 This makes it hard to use some confi <<
221 literals in FLASH memory attached to <<
222 <<
223 Say Y here to enable exception handl <<
224 byte and 2-byte access to memory att <<
225 137
226 config HAVE_SMP !! 138 config EISA
227 bool "System Supports SMP (MX)" !! 139 bool
228 depends on XTENSA_VARIANT_CUSTOM <<
229 select XTENSA_MX <<
230 help 140 help
231 This option is used to indicate that !! 141 EISA is not supported.
232 supports Multiprocessing. Multiproce !! 142 Say N
233 the CPU core definition and currentl <<
234 <<
235 Multiprocessor support is implemente <<
236 interrupt controllers. <<
237 <<
238 The MX interrupt distributer adds In <<
239 and causes the IRQ numbers to be inc <<
240 like the open cores ethernet driver <<
241 <<
242 You still have to select "Enable SMP <<
243 143
244 config SMP !! 144 config MCA
245 bool "Enable Symmetric multi-processin !! 145 bool
246 depends on HAVE_SMP <<
247 select GENERIC_SMP_IDLE_THREAD <<
248 help 146 help
249 Enabled SMP Software; allows more th !! 147 MCA is not supported.
250 to be activated during startup. !! 148 Say N
251 <<
252 config NR_CPUS <<
253 depends on SMP <<
254 int "Maximum number of CPUs (2-32)" <<
255 range 2 32 <<
256 default "4" <<
257 149
258 config HOTPLUG_CPU !! 150 config PCMCIA
259 bool "Enable CPU hotplug support" !! 151 tristate
260 depends on SMP !! 152 ---help---
261 help !! 153 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
262 Say Y here to allow turning CPUs off !! 154 computer. These are credit-card size devices such as network cards,
263 controlled through /sys/devices/syst !! 155 modems or hard drives often used with laptops computers. There are
>> 156 actually two varieties of these cards: the older 16 bit PCMCIA cards
>> 157 and the newer 32 bit CardBus cards. If you want to use CardBus
>> 158 cards, you need to say Y here and also to "CardBus support" below.
>> 159
>> 160 To use your PC-cards, you will need supporting software from David
>> 161 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
>> 162 for location). Please also read the PCMCIA-HOWTO, available from
>> 163 <http://www.tldp.org/docs.html#howto>.
264 164
265 Say N if you want to disable CPU hot !! 165 To compile this driver as modules, choose M here: the
>> 166 modules will be called pcmcia_core and ds.
266 167
267 config SECONDARY_RESET_VECTOR !! 168 config SBUS
268 bool "Secondary cores use alternative !! 169 bool
269 default y 170 default y
270 depends on HAVE_SMP <<
271 help <<
272 Secondary cores may be configured to <<
273 or all cores may use primary reset v <<
274 Say Y here to supply handler for the <<
275 171
276 config FAST_SYSCALL_XTENSA !! 172 config SBUSCHAR
277 bool "Enable fast atomic syscalls" !! 173 bool
278 default n !! 174 default y
279 help <<
280 fast_syscall_xtensa is a syscall tha <<
281 on UP kernel when processor has no s <<
282 175
283 This syscall is deprecated. It may h !! 176 config SERIAL_CONSOLE
284 invalid arguments. It is provided on !! 177 bool
285 Only enable it if your userspace sof !! 178 default y
>> 179 ---help---
>> 180 If you say Y here, it will be possible to use a serial port as the
>> 181 system console (the system console is the device which receives all
>> 182 kernel messages and warnings and which allows logins in single user
>> 183 mode). This could be useful if some terminal or printer is connected
>> 184 to that serial port.
>> 185
>> 186 Even if you say Y here, the currently visible virtual console
>> 187 (/dev/tty0) will still be used as the system console by default, but
>> 188 you can alter that using a kernel command line option such as
>> 189 "console=ttyS1". (Try "man bootparam" or see the documentation of
>> 190 your boot loader (lilo or loadlin) about how to pass options to the
>> 191 kernel at boot time.)
>> 192
>> 193 If you don't have a VGA card installed and you say Y here, the
>> 194 kernel will automatically use the first serial line, /dev/ttyS0, as
>> 195 system console.
286 196
287 If unsure, say N. 197 If unsure, say N.
288 198
289 config FAST_SYSCALL_SPILL_REGISTERS !! 199 config SUN_AUXIO
290 bool "Enable spill registers syscall" !! 200 bool
291 default n !! 201 default y
292 help <<
293 fast_syscall_spill_registers is a sy <<
294 register windows of a calling usersp <<
295 <<
296 This syscall is deprecated. It may h <<
297 invalid arguments. It is provided on <<
298 Only enable it if your userspace sof <<
299 202
300 If unsure, say N. !! 203 config SUN_IO
>> 204 bool
>> 205 default y
301 206
302 choice !! 207 config RWSEM_GENERIC_SPINLOCK
303 prompt "Kernel ABI" !! 208 bool
304 default KERNEL_ABI_DEFAULT !! 209 default y
305 help <<
306 Select ABI for the kernel code. This <<
307 supported userspace ABI and any comb <<
308 kernel/userspace ABI is possible and <<
309 210
310 In case both kernel and userspace su !! 211 config RWSEM_XCHGADD_ALGORITHM
311 all register windows support code wi !! 212 bool
312 build. <<
313 213
314 If unsure, choose the default ABI. !! 214 config SUN_PM
>> 215 bool
>> 216 default y
>> 217 help
>> 218 Enable power management and CPU standby features on supported
>> 219 SPARC platforms.
315 220
316 config KERNEL_ABI_DEFAULT !! 221 config SUN4
317 bool "Default ABI" !! 222 bool "Support for SUN4 machines (disables SUN4[CDM] support)"
318 help 223 help
319 Select this option to compile kernel !! 224 Say Y here if, and only if, your machine is a sun4. Note that
320 selected for the toolchain. !! 225 a kernel compiled with this option will run only on sun4.
321 Normally cores with windowed registe !! 226 (And the current version will probably work only on sun4/330.)
322 cores without it use call0 ABI. <<
323 227
324 config KERNEL_ABI_CALL0 !! 228 if !SUN4
325 bool "Call0 ABI" if CC_HAVE_CALL0_ABI !! 229
>> 230 config PCI
>> 231 bool "Support for PCI and PS/2 keyboard/mouse"
326 help 232 help
327 Select this option to compile kernel !! 233 CONFIG_PCI is needed for all JavaStation's (including MrCoffee),
328 toolchain that defaults to windowed !! 234 CP-1200, JavaEngine-1, Corona, Red October, and Serengeti SGSC.
329 When this option is not selected the !! 235 All of these platforms are extremely obscure, so say N if unsure.
330 be used for the kernel code. <<
331 236
332 endchoice !! 237 source "drivers/pci/Kconfig"
333 238
334 config USER_ABI_CALL0 !! 239 endif
335 bool <<
336 240
337 choice !! 241 config SUN_OPENPROMFS
338 prompt "Userspace ABI" !! 242 tristate "Openprom tree appears in /proc/openprom"
339 default USER_ABI_DEFAULT <<
340 help 243 help
341 Select supported userspace ABI. !! 244 If you say Y, the OpenPROM device tree will be available as a
>> 245 virtual file system, which you can mount to /proc/openprom by "mount
>> 246 -t openpromfs none /proc/openprom".
342 247
343 If unsure, choose the default ABI. !! 248 To compile the /proc/openprom support as a module, choose M here: the
>> 249 module will be called openpromfs. If unsure, choose M.
344 250
345 config USER_ABI_DEFAULT !! 251 source "fs/Kconfig.binfmt"
346 bool "Default ABI only" <<
347 help <<
348 Assume default userspace ABI. For XE <<
349 call0 ABI binaries may be run on suc <<
350 will not work correctly for them. <<
351 252
352 config USER_ABI_CALL0_ONLY !! 253 config SUNOS_EMUL
353 bool "Call0 ABI only" !! 254 bool "SunOS binary emulation"
354 select USER_ABI_CALL0 <<
355 help 255 help
356 Select this option to support only c !! 256 This allows you to run most SunOS binaries. If you want to do this,
357 Windowed ABI binaries will crash wit !! 257 say Y here and place appropriate files in /usr/gnemul/sunos. See
358 an illegal instruction exception on !! 258 <http://www.ultralinux.org/faq.html> for more information. If you
>> 259 want to run SunOS binaries on an Ultra you must also say Y to
>> 260 "Kernel support for 32-bit a.out binaries" above.
359 261
360 Choose this option if you're plannin !! 262 source "drivers/parport/Kconfig"
361 built with call0 ABI. <<
362 263
363 config USER_ABI_CALL0_PROBE !! 264 config PRINTER
364 bool "Support both windowed and call0 !! 265 tristate "Parallel printer support"
365 select USER_ABI_CALL0 !! 266 depends on PARPORT
366 help !! 267 ---help---
367 Select this option to support both w !! 268 If you intend to attach a printer to the parallel port of your Linux
368 ABIs. When enabled all processes are !! 269 box (as opposed to using a serial printer; if the connector at the
369 and a fast user exception handler fo !! 270 printer has 9 or 25 holes ["female"], then it's serial), say Y.
370 used to turn on PS.WOE bit on the fi !! 271 Also read the Printing-HOWTO, available from
371 the userspace. !! 272 <http://www.tldp.org/docs.html#howto>.
372 273
373 This option should be enabled for th !! 274 It is possible to share one parallel port among several devices
374 both call0 and windowed ABIs in user !! 275 (e.g. printer and ZIP drive) and it is safe to compile the
>> 276 corresponding drivers into the kernel. If you want to compile this
>> 277 driver as a module however, choose M here and read
>> 278 <file:Documentation/parport.txt>. The module will be called lp.
375 279
376 Note that Xtensa ISA does not guaran !! 280 If you have several parallel ports, you can specify which ports to
377 raise an illegal instruction excepti !! 281 use with the "lp" kernel command line option. (Try "man bootparam"
378 PS.WOE is disabled, check whether th !! 282 or see the documentation of your boot loader (lilo or loadlin) about
>> 283 how to pass options to the kernel at boot time.) The syntax of the
>> 284 "lp" command line option can be found in <file:drivers/char/lp.c>.
379 285
380 endchoice !! 286 If you have more than 8 printers, you need to increase the LP_NO
>> 287 macro in lp.c and the PARPORT_MAX macro in parport.h.
381 288
382 endmenu 289 endmenu
383 290
384 config XTENSA_CALIBRATE_CCOUNT !! 291 source "drivers/base/Kconfig"
385 def_bool n <<
386 help <<
387 On some platforms (XT2000, for examp <<
388 vary. The frequency can be determin <<
389 against a well known, fixed frequenc <<
390 292
391 config SERIAL_CONSOLE !! 293 source "drivers/video/Kconfig"
392 def_bool n <<
393 294
394 config PLATFORM_HAVE_XIP !! 295 source "drivers/mtd/Kconfig"
395 def_bool n <<
396 296
397 menu "Platform options" !! 297 source "drivers/serial/Kconfig"
398 298
399 choice !! 299 if !SUN4
400 prompt "Xtensa System Type" !! 300 source "drivers/sbus/char/Kconfig"
401 default XTENSA_PLATFORM_ISS !! 301 endif
>> 302
>> 303
>> 304 menu "Block devices"
>> 305
>> 306 config BLK_DEV_FD
>> 307 bool "Normal floppy disk support"
>> 308 ---help---
>> 309 If you want to use the floppy disk drive(s) of your PC under Linux,
>> 310 say Y. Information about this driver, especially important for IBM
>> 311 Thinkpad users, is contained in <file:Documentation/floppy.txt>.
>> 312 That file also contains the location of the Floppy driver FAQ as
>> 313 well as location of the fdutils package used to configure additional
>> 314 parameters of the driver at run time.
>> 315
>> 316 To compile this driver as a module, choose M here: the
>> 317 module will be called floppy.
>> 318
>> 319 config BLK_DEV_LOOP
>> 320 tristate "Loopback device support"
>> 321 ---help---
>> 322 Saying Y here will allow you to use a regular file as a block
>> 323 device; you can then create a file system on that block device and
>> 324 mount it just as you would mount other block devices such as hard
>> 325 drive partitions, CD-ROM drives or floppy drives. The loop devices
>> 326 are block special device files with major number 7 and typically
>> 327 called /dev/loop0, /dev/loop1 etc.
>> 328
>> 329 This is useful if you want to check an ISO 9660 file system before
>> 330 burning the CD, or if you want to use floppy images without first
>> 331 writing them to floppy. Furthermore, some Linux distributions avoid
>> 332 the need for a dedicated Linux partition by keeping their complete
>> 333 root file system inside a DOS FAT file using this loop device
>> 334 driver.
>> 335
>> 336 The loop device driver can also be used to "hide" a file system in a
>> 337 disk partition, floppy, or regular file, either using encryption
>> 338 (scrambling the data) or steganography (hiding the data in the low
>> 339 bits of, say, a sound file). This is also safe if the file resides
>> 340 on a remote file server. If you want to do this, you will first have
>> 341 to acquire and install a kernel patch from
>> 342 <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
>> 343 say Y to this option.
>> 344
>> 345 Note that alternative ways to use encrypted file systems are
>> 346 provided by the cfs package, which can be gotten from
>> 347 <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
>> 348 package, available at <http://tcfs.dia.unisa.it/>. You do not need
>> 349 to say Y here if you want to use one of these. However, using cfs
>> 350 requires saying Y to "NFS file system support" below while using
>> 351 tcfs requires applying a kernel patch. An alternative steganography
>> 352 solution is provided by StegFS, also available from
>> 353 <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
>> 354
>> 355 To use the loop device, you need the losetup utility and a recent
>> 356 version of the mount program, both contained in the util-linux
>> 357 package. The location and current version number of util-linux is
>> 358 contained in the file <file:Documentation/Changes>.
>> 359
>> 360 Note that this loop device has nothing to do with the loopback
>> 361 device used for network connections from the machine to itself.
>> 362
>> 363 To compile this driver as a module, choose M here: the
>> 364 module will be called loop.
>> 365
>> 366 Most users will answer N here.
>> 367
>> 368 config BLK_DEV_NBD
>> 369 tristate "Network block device support"
>> 370 depends on NET
>> 371 ---help---
>> 372 Saying Y here will allow your computer to be a client for network
>> 373 block devices, i.e. it will be able to use block devices exported by
>> 374 servers (mount file systems on them etc.). Communication between
>> 375 client and server works over TCP/IP networking, but to the client
>> 376 program this is hidden: it looks like a regular local file access to
>> 377 a block device special file such as /dev/nd0.
>> 378
>> 379 Network block devices also allows you to run a block-device in
>> 380 userland (making server and client physically the same computer,
>> 381 communicating using the loopback network device).
>> 382
>> 383 Read <file:Documentation/nbd.txt> for more information, especially
>> 384 about where to find the server code, which runs in user space and
>> 385 does not need special kernel support.
402 386
403 config XTENSA_PLATFORM_ISS !! 387 Note that this has nothing to do with the network file systems NFS
404 bool "ISS" !! 388 or Coda; you can say N here even if you intend to use NFS or Coda.
405 select XTENSA_CALIBRATE_CCOUNT <<
406 select SERIAL_CONSOLE <<
407 help <<
408 ISS is an acronym for Tensilica's In <<
409 389
410 config XTENSA_PLATFORM_XT2000 !! 390 To compile this driver as a module, choose M here: the
411 bool "XT2000" !! 391 module will be called nbd.
412 help <<
413 XT2000 is the name of Tensilica's fe <<
414 This hardware is capable of running <<
415 392
416 config XTENSA_PLATFORM_XTFPGA !! 393 If unsure, say N.
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 394
427 endchoice !! 395 source "drivers/md/Kconfig"
428 396
429 config PLATFORM_NR_IRQS !! 397 config BLK_DEV_RAM
430 int !! 398 tristate "RAM disk support"
431 default 3 if XTENSA_PLATFORM_XT2000 !! 399 ---help---
432 default 0 !! 400 Saying Y here will allow you to use a portion of your RAM memory as
>> 401 a block device, so that you can make file systems on it, read and
>> 402 write to it and do all the other things that you can do with normal
>> 403 block devices (such as hard drives). It is usually used to load and
>> 404 store a copy of a minimal root file system off of a floppy into RAM
>> 405 during the initial install of Linux.
>> 406
>> 407 Note that the kernel command line option "ramdisk=XX" is now
>> 408 obsolete. For details, read <file:Documentation/ramdisk.txt>.
>> 409
>> 410 To compile this driver as a module, choose M here: the
>> 411 module will be called rd.
>> 412
>> 413 Most normal users won't need the RAM disk functionality, and can
>> 414 thus say N here.
>> 415
>> 416 config BLK_DEV_RAM_SIZE
>> 417 int "Default RAM disk size"
>> 418 depends on BLK_DEV_RAM
>> 419 default "4096"
>> 420 help
>> 421 The default value is 4096. Only change this if you know what are
>> 422 you doing. If you are using IBM S/390, then set this to 8192.
>> 423
>> 424 config BLK_DEV_INITRD
>> 425 bool "Initial RAM disk (initrd) support"
>> 426 depends on BLK_DEV_RAM=y
>> 427 help
>> 428 The initial RAM disk is a RAM disk that is loaded by the boot loader
>> 429 (loadlin or lilo) and that is mounted as root before the normal boot
>> 430 procedure. It is typically used to load modules needed to mount the
>> 431 "real" root file system, etc. See <file:Documentation/initrd.txt>
>> 432 for details.
433 433
434 config XTENSA_CPU_CLOCK !! 434 endmenu
435 int "CPU clock rate [MHz]" <<
436 depends on !XTENSA_CALIBRATE_CCOUNT <<
437 default 16 <<
438 435
439 config GENERIC_CALIBRATE_DELAY !! 436 # Don't frighten a common SBus user
440 bool "Auto calibration of the BogoMIPS !! 437 if PCI
441 help <<
442 The BogoMIPS value can easily be der <<
443 438
444 config CMDLINE_BOOL !! 439 source "drivers/ide/Kconfig"
445 bool "Default bootloader kernel argume <<
446 440
447 config CMDLINE !! 441 endif
448 string "Initial kernel command string" <<
449 depends on CMDLINE_BOOL <<
450 default "console=ttyS0,38400 root=/dev <<
451 help <<
452 On some architectures (EBSA110 and C <<
453 for the boot loader to pass argument <<
454 architectures, you should supply som <<
455 time by entering them here. As a min <<
456 memory size and the root device (e.g <<
457 442
458 config USE_OF !! 443 source "drivers/isdn/Kconfig"
459 bool "Flattened Device Tree support" <<
460 select OF <<
461 select OF_EARLY_FLATTREE <<
462 help <<
463 Include support for flattened device <<
464 444
465 config BUILTIN_DTB_SOURCE !! 445 source "drivers/scsi/Kconfig"
466 string "DTB to build into the kernel i !! 446
467 depends on OF !! 447 source "drivers/fc4/Kconfig"
>> 448
>> 449 source "net/Kconfig"
>> 450
>> 451 # This one must be before the filesystem configs. -DaveM
>> 452
>> 453 menu "Unix98 PTY support"
>> 454
>> 455 config UNIX98_PTYS
>> 456 bool "Unix98 PTY support"
>> 457 ---help---
>> 458 A pseudo terminal (PTY) is a software device consisting of two
>> 459 halves: a master and a slave. The slave device behaves identical to
>> 460 a physical terminal; the master device is used by a process to
>> 461 read data from and write data to the slave, thereby emulating a
>> 462 terminal. Typical programs for the master side are telnet servers
>> 463 and xterms.
>> 464
>> 465 Linux has traditionally used the BSD-like names /dev/ptyxx for
>> 466 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
>> 467 has a number of problems. The GNU C library glibc 2.1 and later,
>> 468 however, supports the Unix98 naming standard: in order to acquire a
>> 469 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
>> 470 terminal is then made available to the process and the pseudo
>> 471 terminal slave can be accessed as /dev/pts/<number>. What was
>> 472 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
>> 473
>> 474 The entries in /dev/pts/ are created on the fly by a virtual
>> 475 file system; therefore, if you say Y here you should say Y to
>> 476 "/dev/pts file system for Unix98 PTYs" as well.
>> 477
>> 478 If you want to say Y here, you need to have the C library glibc 2.1
>> 479 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
>> 480 Read the instructions in <file:Documentation/Changes> pertaining to
>> 481 pseudo terminals. It's safe to say N.
>> 482
>> 483 config UNIX98_PTY_COUNT
>> 484 int "Maximum number of Unix98 PTYs in use (0-2048)"
>> 485 depends on UNIX98_PTYS
>> 486 default "256"
>> 487 help
>> 488 The maximum number of Unix98 PTYs that can be used at any one time.
>> 489 The default is 256, and should be enough for desktop systems. Server
>> 490 machines which support incoming telnet/rlogin/ssh connections and/or
>> 491 serve several X terminals may want to increase this: every incoming
>> 492 connection and every xterm uses up one PTY.
468 493
469 config PARSE_BOOTPARAM !! 494 When not in use, each additional set of 256 PTYs occupy
470 bool "Parse bootparam block" !! 495 approximately 8 KB of kernel memory on 32-bit architectures.
471 default y <<
472 help <<
473 Parse parameters passed to the kerne <<
474 be disabled if the kernel is known t <<
475 496
476 If unsure, say Y. !! 497 endmenu
477 498
478 choice !! 499 source "drivers/input/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 <<
486 config XTENSA_SIMCALL_ISS <<
487 bool "simcall" <<
488 help <<
489 Use simcall instruction. simcall is <<
490 it does nothing on hardware. <<
491 <<
492 config XTENSA_SIMCALL_GDBIO <<
493 bool "GDBIO" <<
494 help <<
495 Use break instruction. It is availab <<
496 is attached to it via JTAG. <<
497 <<
498 endchoice <<
499 <<
500 config BLK_DEV_SIMDISK <<
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 500
545 If unsure, say N. !! 501 source "fs/Kconfig"
546 502
547 config XTFPGA_LCD_BASE_ADDR !! 503 source "sound/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 504
617 If unsure, say N. !! 505 source "drivers/usb/Kconfig"
618 506
619 config MEMMAP_CACHEATTR !! 507 menu "Watchdog"
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 <<
683 If unsure, leave the default value h <<
684 <<
685 choice <<
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 <<
711 endchoice <<
712 <<
713 config VECTORS_ADDR <<
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 <<
741 If unsure, leave the default value h <<
742 <<
743 choice <<
744 prompt "KSEG layout" <<
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 508
772 endchoice !! 509 config SOFT_WATCHDOG
>> 510 tristate "Software watchdog"
>> 511 help
>> 512 A software monitoring watchdog. This will fail to reboot your system
>> 513 from some situations that the hardware watchdog will recover
>> 514 from. Equally it's a lot cheaper to install.
773 515
774 config HIGHMEM !! 516 To compile this driver as a module, choose M here: the
775 bool "High Memory Support" !! 517 module will be called softdog.
776 depends on MMU !! 518
777 select KMAP_LOCAL !! 519 endmenu
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 520
792 If unsure, say Y. <<
793 521
794 config ARCH_FORCE_MAX_ORDER !! 522 menu "Kernel hacking"
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 523
805 Don't change if unsure. !! 524 config DEBUG_SLAB
>> 525 bool "Debug memory allocations"
>> 526
>> 527 config MAGIC_SYSRQ
>> 528 bool "Magic SysRq key"
>> 529 help
>> 530 If you say Y here, you will have some control over the system even
>> 531 if the system crashes for example during kernel debugging (e.g., you
>> 532 will be able to flush the buffer cache to disk, reboot the system
>> 533 immediately or dump some status information). This is accomplished
>> 534 by pressing various keys while holding SysRq (Alt+PrintScreen). It
>> 535 also works on a serial console (on PC hardware at least), if you
>> 536 send a BREAK and then within 5 seconds a command keypress. The
>> 537 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
>> 538 unless you really know what this hack does.
>> 539
>> 540 config DEBUG_SPINLOCK
>> 541 bool "Spinlock debugging"
>> 542
>> 543 config DEBUG_SPINLOCK_SLEEP
>> 544 bool "Sleep-inside-spinlock checking"
>> 545 help
>> 546 If you say Y here, various routines which may sleep will become very
>> 547 noisy if they are called with a spinlock held.
>> 548
>> 549 config DEBUG_BUGVERBOSE
>> 550 bool "Verbose BUG() reporting (adds 70K)"
>> 551 help
>> 552 Say Y here to make BUG() panics output the file name and line number
>> 553 of the BUG call as well as the EIP and oops trace. This aids
>> 554 debugging but costs about 70-100K of memory.
806 555
807 endmenu 556 endmenu
808 557
809 menu "Power management options" !! 558 source "security/Kconfig"
810 559
811 config ARCH_HIBERNATION_POSSIBLE !! 560 source "crypto/Kconfig"
812 def_bool y <<
813 561
814 source "kernel/power/Kconfig" !! 562 source "lib/Kconfig"
815 563
816 endmenu <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.