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 <<
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 5
77 config ARCH_MTD_XIP !! 6 mainmenu "Linux Kernel Configuration"
78 def_bool y <<
79 7
80 config NO_IOPORT_MAP !! 8 config X86
81 def_bool n !! 9 bool
82 !! 10 default y
83 config HZ !! 11 help
84 int !! 12 This is Linux's home port. Linux was originally native to the Intel
85 default 100 !! 13 386, and runs on all the later x86 processors including the Intel
86 !! 14 486, 586, Pentiums, and various instruction-set-compatible chips by
87 config LOCKDEP_SUPPORT !! 15 AMD, Cyrix, and others.
88 def_bool y <<
89 <<
90 config STACKTRACE_SUPPORT <<
91 def_bool y <<
92 16
93 config MMU 17 config MMU
94 def_bool n !! 18 bool
95 select PFAULT !! 19 default y
96 20
97 config HAVE_XTENSA_GPIO32 !! 21 config SBUS
98 def_bool n !! 22 bool
99 23
100 config KASAN_SHADOW_OFFSET !! 24 config UID16
101 hex !! 25 bool
102 default 0x6e400000 !! 26 default y
103 27
104 config CPU_BIG_ENDIAN !! 28 config GENERIC_ISA_DMA
105 def_bool $(success,test "$(shell,echo !! 29 bool
>> 30 default y
106 31
107 config CPU_LITTLE_ENDIAN !! 32 source "init/Kconfig"
108 def_bool !CPU_BIG_ENDIAN <<
109 33
110 config CC_HAVE_CALL0_ABI <<
111 def_bool $(success,test "$(shell,echo <<
112 34
113 menu "Processor type and features" 35 menu "Processor type and features"
114 36
115 choice 37 choice
116 prompt "Xtensa Processor Configuration !! 38 prompt "Subarchitecture Type"
117 default XTENSA_VARIANT_FSF !! 39 default X86_PC
>> 40
>> 41 config X86_PC
>> 42 bool "PC-compatible"
>> 43 help
>> 44 Choose this option if your computer is a standard PC or compatible.
118 45
119 config XTENSA_VARIANT_FSF !! 46 config X86_VOYAGER
120 bool "fsf - default (not generic) conf !! 47 bool "Voyager (NCR)"
121 select MMU !! 48 help
>> 49 Voyager is a MCA based 32 way capable SMP architecture proprietary
>> 50 to NCR Corp. Machine classes 345x/35xx/4100/51xx are voyager based.
>> 51
>> 52 *** WARNING ***
>> 53
>> 54 If you do not specifically know you have a Voyager based machine,
>> 55 say N here otherwise the kernel you build will not be bootable.
>> 56
>> 57 config X86_NUMAQ
>> 58 bool "NUMAQ (IBM/Sequent)"
>> 59 help
>> 60 This option is used for getting Linux to run on a (IBM/Sequent) NUMA
>> 61 multiquad box. This changes the way that processors are bootstrapped,
>> 62 and uses Clustered Logical APIC addressing mode instead of Flat Logical.
>> 63 You will need a new lynxer.elf file to flash your firmware with - send
>> 64 email to Martin.Bligh@us.ibm.com
122 65
123 config XTENSA_VARIANT_DC232B !! 66 config X86_SUMMIT
124 bool "dc232b - Diamond 232L Standard C !! 67 bool "Summit/EXA (IBM x440)"
125 select MMU !! 68 depends on SMP
126 select HAVE_XTENSA_GPIO32 <<
127 help 69 help
128 This variant refers to Tensilica's D !! 70 This option is needed for IBM systems that use the Summit/EXA chipset.
>> 71 In particular, it is needed for the x440.
>> 72
>> 73 If you don't have one of these computers, you should say N here.
129 74
130 config XTENSA_VARIANT_DC233C !! 75 config X86_BIGSMP
131 bool "dc233c - Diamond 233L Standard C !! 76 bool "Support for other sub-arch SMP systems with more than 8 CPUs"
132 select MMU !! 77 depends on SMP
133 select HAVE_XTENSA_GPIO32 <<
134 help 78 help
135 This variant refers to Tensilica's D !! 79 This option is needed for the systems that have more than 8 CPUs
>> 80 and if the system is not of any sub-arch type above.
>> 81
>> 82 If you don't have such a system, you should say N here.
136 83
137 config XTENSA_VARIANT_CUSTOM !! 84 config X86_VISWS
138 bool "Custom Xtensa processor configur !! 85 bool "SGI 320/540 (Visual Workstation)"
139 select HAVE_XTENSA_GPIO32 <<
140 help 86 help
141 Select this variant to use a custom !! 87 The SGI Visual Workstation series is an IA32-based workstation
142 You will be prompted for a processor !! 88 based on SGI systems chips with some legacy PC hardware attached.
143 endchoice !! 89
>> 90 Say Y here to create a kernel to run on the SGI 320 or 540.
>> 91
>> 92 A kernel compiled for the Visual Workstation will not run on PCs
>> 93 and vice versa. See <file:Documentation/sgi-visws.txt> for details.
>> 94
>> 95 config X86_GENERICARCH
>> 96 bool "Generic architecture (Summit, bigsmp, default)"
>> 97 depends on SMP
>> 98 help
>> 99 This option compiles in the Summit, bigsmp, default subarchitectures.
>> 100 It is intended for a generic binary kernel.
144 101
145 config XTENSA_VARIANT_CUSTOM_NAME !! 102 config X86_ES7000
146 string "Xtensa Processor Custom Core V !! 103 bool "Support for Unisys ES7000 IA32 series"
147 depends on XTENSA_VARIANT_CUSTOM !! 104 depends on SMP
148 help 105 help
149 Provide the name of a custom Xtensa !! 106 Support for Unisys ES7000 systems. Say 'Y' here if this kernel is
150 This CORENAME selects arch/xtensa/va !! 107 supposed to run on an IA32-based Unisys ES7000 system.
151 Don't forget you have to select MMU !! 108 Only choose this option if you have such a system, otherwise you
>> 109 should say N here.
152 110
153 config XTENSA_VARIANT_NAME !! 111 endchoice
154 string <<
155 default "dc232b" <<
156 default "dc233c" <<
157 default "fsf" <<
158 default XTENSA_VARIANT_CUSTOM_NAME <<
159 112
160 config XTENSA_VARIANT_MMU !! 113 config ACPI_SRAT
161 bool "Core variant has a Full MMU (TLB !! 114 bool
162 depends on XTENSA_VARIANT_CUSTOM <<
163 default y 115 default y
164 select MMU !! 116 depends on NUMA && (X86_SUMMIT || X86_GENERICARCH)
165 help <<
166 Build a Conventional Kernel with ful <<
167 ie: it supports a TLB with auto-load <<
168 117
169 config XTENSA_VARIANT_HAVE_PERF_EVENTS !! 118 config X86_CYCLONE_TIMER
170 bool "Core variant has Performance Mon !! 119 bool
171 depends on XTENSA_VARIANT_CUSTOM !! 120 default y
172 default n !! 121 depends on X86_SUMMIT || X86_GENERICARCH
173 help <<
174 Enable if core variant has Performan <<
175 External Registers Interface. <<
176 122
177 If unsure, say N. !! 123 config ES7000_CLUSTERED_APIC
>> 124 bool
>> 125 default y
>> 126 depends on SMP && X86_ES7000 && MPENTIUMIII
178 127
179 config XTENSA_FAKE_NMI !! 128 choice
180 bool "Treat PMM IRQ as NMI" !! 129 prompt "Processor family"
181 depends on XTENSA_VARIANT_HAVE_PERF_EV !! 130 default M686
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 131
187 If there are other interrupts at or !! 132 config M386
188 but not above the EXCM level, PMM IR !! 133 bool "386"
189 but only if these IRQs are not used. !! 134 ---help---
190 saying that this is not safe, and a !! 135 This is the processor type of your CPU. This information is used for
191 actually fire. !! 136 optimizing purposes. In order to compile a kernel that can run on
>> 137 all x86 CPU types (albeit not optimally fast), you can specify
>> 138 "386" here.
>> 139
>> 140 The kernel will not necessarily run on earlier architectures than
>> 141 the one you have chosen, e.g. a Pentium optimized kernel will run on
>> 142 a PPro, but not necessarily on a i486.
>> 143
>> 144 Here are the settings recommended for greatest speed:
>> 145 - "386" for the AMD/Cyrix/Intel 386DX/DXL/SL/SLC/SX, Cyrix/TI
>> 146 486DLC/DLC2, UMC 486SX-S and NexGen Nx586. Only "386" kernels
>> 147 will run on a 386 class machine.
>> 148 - "486" for the AMD/Cyrix/IBM/Intel 486DX/DX2/DX4 or
>> 149 SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or U5S.
>> 150 - "586" for generic Pentium CPUs lacking the TSC
>> 151 (time stamp counter) register.
>> 152 - "Pentium-Classic" for the Intel Pentium.
>> 153 - "Pentium-MMX" for the Intel Pentium MMX.
>> 154 - "Pentium-Pro" for the Intel Pentium Pro.
>> 155 - "Pentium-II" for the Intel Pentium II or pre-Coppermine Celeron.
>> 156 - "Pentium-III" for the Intel Pentium III or Coppermine Celeron.
>> 157 - "Pentium-4" for the Intel Pentium 4 or P4-based Celeron.
>> 158 - "K6" for the AMD K6, K6-II and K6-III (aka K6-3D).
>> 159 - "Athlon" for the AMD K7 family (Athlon/Duron/Thunderbird).
>> 160 - "Crusoe" for the Transmeta Crusoe series.
>> 161 - "Winchip-C6" for original IDT Winchip.
>> 162 - "Winchip-2" for IDT Winchip 2.
>> 163 - "Winchip-2A" for IDT Winchips with 3dNow! capabilities.
>> 164 - "CyrixIII/VIA C3" for VIA Cyrix III or VIA C3.
>> 165 - "VIA C3-2 for VIA C3-2 "Nehemiah" (model 9 and above).
>> 166
>> 167 If you don't know what to do, choose "386".
>> 168
>> 169 config M486
>> 170 bool "486"
>> 171 help
>> 172 Select this for a 486 series processor, either Intel or one of the
>> 173 compatible processors from AMD, Cyrix, IBM, or Intel. Includes DX,
>> 174 DX2, and DX4 variants; also SL/SLC/SLC2/SLC3/SX/SX2 and UMC U5D or
>> 175 U5S.
>> 176
>> 177 config M586
>> 178 bool "586/K5/5x86/6x86/6x86MX"
>> 179 help
>> 180 Select this for an 586 or 686 series processor such as the AMD K5,
>> 181 the Intel 5x86 or 6x86, or the Intel 6x86MX. This choice does not
>> 182 assume the RDTSC (Read Time Stamp Counter) instruction.
>> 183
>> 184 config M586TSC
>> 185 bool "Pentium-Classic"
>> 186 help
>> 187 Select this for a Pentium Classic processor with the RDTSC (Read
>> 188 Time Stamp Counter) instruction for benchmarking.
>> 189
>> 190 config M586MMX
>> 191 bool "Pentium-MMX"
>> 192 help
>> 193 Select this for a Pentium with the MMX graphics/multimedia
>> 194 extended instructions.
>> 195
>> 196 config M686
>> 197 bool "Pentium-Pro"
>> 198 help
>> 199 Select this for Intel Pentium Pro chips. This enables the use of
>> 200 Pentium Pro extended instructions, and disables the init-time guard
>> 201 against the f00f bug found in earlier Pentiums.
>> 202
>> 203 config MPENTIUMII
>> 204 bool "Pentium-II/Celeron(pre-Coppermine)"
>> 205 help
>> 206 Select this for Intel chips based on the Pentium-II and
>> 207 pre-Coppermine Celeron core. This option enables an unaligned
>> 208 copy optimization, compiles the kernel with optimization flags
>> 209 tailored for the chip, and applies any applicable Pentium Pro
>> 210 optimizations.
>> 211
>> 212 config MPENTIUMIII
>> 213 bool "Pentium-III/Celeron(Coppermine)/Pentium-III Xeon"
>> 214 help
>> 215 Select this for Intel chips based on the Pentium-III and
>> 216 Celeron-Coppermine core. This option enables use of some
>> 217 extended prefetch instructions in addition to the Pentium II
>> 218 extensions.
>> 219
>> 220 config MPENTIUM4
>> 221 bool "Pentium-4/Celeron(P4-based)/Xeon"
>> 222 help
>> 223 Select this for Intel Pentium 4 chips. This includes both
>> 224 the Pentium 4 and P4-based Celeron chips. This option
>> 225 enables compile flags optimized for the chip, uses the
>> 226 correct cache shift, and applies any applicable Pentium III
>> 227 optimizations.
>> 228
>> 229 config MK6
>> 230 bool "K6/K6-II/K6-III"
>> 231 help
>> 232 Select this for an AMD K6-family processor. Enables use of
>> 233 some extended instructions, and passes appropriate optimization
>> 234 flags to GCC.
>> 235
>> 236 config MK7
>> 237 bool "Athlon/Duron/K7"
>> 238 help
>> 239 Select this for an AMD Athlon K7-family processor. Enables use of
>> 240 some extended instructions, and passes appropriate optimization
>> 241 flags to GCC.
>> 242
>> 243 config MK8
>> 244 bool "Opteron/Athlon64/Hammer/K8"
>> 245 help
>> 246 Select this for an AMD Opteron or Athlon64 Hammer-family processor. Enables
>> 247 use of some extended instructions, and passes appropriate optimization
>> 248 flags to GCC.
>> 249
>> 250 config MELAN
>> 251 bool "Elan"
>> 252
>> 253 config MCRUSOE
>> 254 bool "Crusoe"
>> 255 help
>> 256 Select this for a Transmeta Crusoe processor. Treats the processor
>> 257 like a 586 with TSC, and sets some GCC optimization flags (like a
>> 258 Pentium Pro with no alignment requirements).
>> 259
>> 260 config MWINCHIPC6
>> 261 bool "Winchip-C6"
>> 262 help
>> 263 Select this for an IDT Winchip C6 chip. Linux and GCC
>> 264 treat this chip as a 586TSC with some extended instructions
>> 265 and alignment requirements.
>> 266
>> 267 config MWINCHIP2
>> 268 bool "Winchip-2"
>> 269 help
>> 270 Select this for an IDT Winchip-2. Linux and GCC
>> 271 treat this chip as a 586TSC with some extended instructions
>> 272 and alignment requirements.
>> 273
>> 274 config MWINCHIP3D
>> 275 bool "Winchip-2A/Winchip-3"
>> 276 help
>> 277 Select this for an IDT Winchip-2A or 3. Linux and GCC
>> 278 treat this chip as a 586TSC with some extended instructions
>> 279 and alignment reqirements. Also enable out of order memory
>> 280 stores for this CPU, which can increase performance of some
>> 281 operations.
>> 282
>> 283 config MCYRIXIII
>> 284 bool "CyrixIII/VIA-C3"
>> 285 help
>> 286 Select this for a Cyrix III or C3 chip. Presently Linux and GCC
>> 287 treat this chip as a generic 586. Whilst the CPU is 686 class,
>> 288 it lacks the cmov extension which gcc assumes is present when
>> 289 generating 686 code.
>> 290 Note that Nehemiah (Model 9) and above will not boot with this
>> 291 kernel due to them lacking the 3DNow! instructions used in earlier
>> 292 incarnations of the CPU.
>> 293
>> 294 config MVIAC3_2
>> 295 bool "VIA C3-2 (Nehemiah)"
>> 296 help
>> 297 Select this for a VIA C3 "Nehemiah". Selecting this enables usage
>> 298 of SSE and tells gcc to treat the CPU as a 686.
>> 299 Note, this kernel will not boot on older (pre model 9) C3s.
192 300
193 If unsure, say N. !! 301 endchoice
194 302
195 config PFAULT !! 303 config X86_GENERIC
196 bool "Handle protection faults" if EXP !! 304 bool "Generic x86 support"
>> 305 help
>> 306 Including some tuning for non selected x86 CPUs too.
>> 307 when it has moderate overhead. This is intended for generic
>> 308 distributions kernels.
>> 309
>> 310 #
>> 311 # Define implied options from the CPU selection here
>> 312 #
>> 313 config X86_CMPXCHG
>> 314 bool
>> 315 depends on !M386
197 default y 316 default y
198 help <<
199 Handle protection faults. MMU config <<
200 noMMU configurations may disable it <<
201 generates protection faults or fault <<
202 317
203 If unsure, say Y. !! 318 config X86_XADD
>> 319 bool
>> 320 depends on !M386
>> 321 default y
204 322
205 config XTENSA_UNALIGNED_USER !! 323 config X86_L1_CACHE_SHIFT
206 bool "Unaligned memory access in user !! 324 int
207 help !! 325 default "7" if MPENTIUM4 || X86_GENERIC
208 The Xtensa architecture currently do !! 326 default "4" if MELAN || M486 || M386
209 memory accesses in hardware but thro !! 327 default "5" if MWINCHIP3D || MWINCHIP2 || MWINCHIPC6 || MCRUSOE || MCYRIXIII || MK6 || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || M586 || MVIAC3_2
210 Per default, unaligned memory access !! 328 default "6" if MK7 || MK8
211 329
212 Say Y here to enable unaligned memor !! 330 config RWSEM_GENERIC_SPINLOCK
>> 331 bool
>> 332 depends on M386
>> 333 default y
213 334
214 config XTENSA_LOAD_STORE !! 335 config RWSEM_XCHGADD_ALGORITHM
215 bool "Load/store exception handler for !! 336 bool
216 help !! 337 depends on !M386
217 The Xtensa architecture only allows !! 338 default y
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 339
223 Say Y here to enable exception handl !! 340 config X86_PPRO_FENCE
224 byte and 2-byte access to memory att !! 341 bool
>> 342 depends on M686 || M586MMX || M586TSC || M586 || M486 || M386
>> 343 default y
225 344
226 config HAVE_SMP !! 345 config X86_F00F_BUG
227 bool "System Supports SMP (MX)" !! 346 bool
228 depends on XTENSA_VARIANT_CUSTOM !! 347 depends on M586MMX || M586TSC || M586 || M486 || M386
229 select XTENSA_MX !! 348 default y
230 help <<
231 This option is used to indicate that <<
232 supports Multiprocessing. Multiproce <<
233 the CPU core definition and currentl <<
234 349
235 Multiprocessor support is implemente !! 350 config X86_WP_WORKS_OK
236 interrupt controllers. !! 351 bool
>> 352 depends on !M386
>> 353 default y
237 354
238 The MX interrupt distributer adds In !! 355 config X86_INVLPG
239 and causes the IRQ numbers to be inc !! 356 bool
240 like the open cores ethernet driver !! 357 depends on !M386
>> 358 default y
241 359
242 You still have to select "Enable SMP !! 360 config X86_BSWAP
>> 361 bool
>> 362 depends on !M386
>> 363 default y
243 364
244 config SMP !! 365 config X86_POPAD_OK
245 bool "Enable Symmetric multi-processin !! 366 bool
246 depends on HAVE_SMP !! 367 depends on !M386
247 select GENERIC_SMP_IDLE_THREAD !! 368 default y
248 help <<
249 Enabled SMP Software; allows more th <<
250 to be activated during startup. <<
251 369
252 config NR_CPUS !! 370 config X86_ALIGNMENT_16
253 depends on SMP !! 371 bool
254 int "Maximum number of CPUs (2-32)" !! 372 depends on MWINCHIP3D || MWINCHIP2 || MWINCHIPC6 || MCYRIXIII || MELAN || MK6 || M586MMX || M586TSC || M586 || M486 || MVIAC3_2
255 range 2 32 !! 373 default y
256 default "4" <<
257 374
258 config HOTPLUG_CPU !! 375 config X86_GOOD_APIC
259 bool "Enable CPU hotplug support" !! 376 bool
260 depends on SMP !! 377 depends on MK7 || MPENTIUM4 || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || MK8
261 help !! 378 default y
262 Say Y here to allow turning CPUs off <<
263 controlled through /sys/devices/syst <<
264 379
265 Say N if you want to disable CPU hot !! 380 config X86_INTEL_USERCOPY
>> 381 bool
>> 382 depends on MPENTIUM4 || MPENTIUMIII || MPENTIUMII || M586MMX || X86_GENERIC || MK8 || MK7
>> 383 default y
266 384
267 config SECONDARY_RESET_VECTOR !! 385 config X86_USE_PPRO_CHECKSUM
268 bool "Secondary cores use alternative !! 386 bool
>> 387 depends on MWINCHIP3D || MWINCHIP2 || MWINCHIPC6 || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMIII || MPENTIUMII || M686 || MK8 || MVIAC3_2
269 default y 388 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 389
276 config FAST_SYSCALL_XTENSA !! 390 config X86_USE_3DNOW
277 bool "Enable fast atomic syscalls" !! 391 bool
278 default n !! 392 depends on MCYRIXIII || MK7
>> 393 default y
>> 394
>> 395 config X86_OOSTORE
>> 396 bool
>> 397 depends on MWINCHIP3D || MWINCHIP2 || MWINCHIPC6
>> 398 default y
>> 399
>> 400 config HPET_TIMER
>> 401 bool "HPET Timer Support"
279 help 402 help
280 fast_syscall_xtensa is a syscall tha !! 403 This enables the use of the HPET for the kernel's internal timer.
281 on UP kernel when processor has no s !! 404 HPET is the next generation timer replacing legacy 8254s.
>> 405 You can safely choose Y here. However, HPET will only be
>> 406 activated if the platform and the BIOS support this feature.
>> 407 Otherwise the 8254 will be used for timing services.
282 408
283 This syscall is deprecated. It may h !! 409 Choose N to continue using the legacy 8254 timer.
284 invalid arguments. It is provided on <<
285 Only enable it if your userspace sof <<
286 410
287 If unsure, say N. !! 411 config HPET_EMULATE_RTC
>> 412 def_bool HPET_TIMER && RTC=y
288 413
289 config FAST_SYSCALL_SPILL_REGISTERS !! 414 config SMP
290 bool "Enable spill registers syscall" !! 415 bool "Symmetric multi-processing support"
291 default n !! 416 ---help---
>> 417 This enables support for systems with more than one CPU. If you have
>> 418 a system with only one CPU, like most personal computers, say N. If
>> 419 you have a system with more than one CPU, say Y.
>> 420
>> 421 If you say N here, the kernel will run on single and multiprocessor
>> 422 machines, but will use only one CPU of a multiprocessor machine. If
>> 423 you say Y here, the kernel will run on many, but not all,
>> 424 singleprocessor machines. On a singleprocessor machine, the kernel
>> 425 will run faster if you say N here.
>> 426
>> 427 Note that if you say Y here and choose architecture "586" or
>> 428 "Pentium" under "Processor family", the kernel will not work on 486
>> 429 architectures. Similarly, multiprocessor kernels for the "PPro"
>> 430 architecture may not work on all Pentium based boards.
>> 431
>> 432 People using multiprocessor machines who say Y here should also say
>> 433 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
>> 434 Management" code will be disabled if you say Y here.
>> 435
>> 436 See also the <file:Documentation/smp.tex>,
>> 437 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
>> 438 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
>> 439 <http://www.tldp.org/docs.html#howto>.
>> 440
>> 441 If you don't know what to do here, say N.
>> 442
>> 443 config NR_CPUS
>> 444 int "Maximum number of CPUs (2-255)"
>> 445 depends on SMP
>> 446 default "32" if X86_NUMAQ || X86_SUMMIT || X86_BIGSMP || X86_ES7000
>> 447 default "8"
292 help 448 help
293 fast_syscall_spill_registers is a sy !! 449 This allows you to specify the maximum number of CPUs which this
294 register windows of a calling usersp !! 450 kernel will support. The maximum supported value is 255 and the
>> 451 minimum value which makes sense is 2.
>> 452
>> 453 This is purely to save memory - each supported CPU adds
>> 454 approximately eight kilobytes to the kernel image.
>> 455
>> 456 config PREEMPT
>> 457 bool "Preemptible Kernel"
>> 458 help
>> 459 This option reduces the latency of the kernel when reacting to
>> 460 real-time or interactive events by allowing a low priority process to
>> 461 be preempted even if it is in kernel mode executing a system call.
>> 462 This allows applications to run more reliably even when the system is
>> 463 under load.
>> 464
>> 465 Say Y here if you are building a kernel for a desktop, embedded
>> 466 or real-time system. Say N if you are unsure.
>> 467
>> 468 config X86_UP_APIC
>> 469 bool "Local APIC support on uniprocessors" if !SMP
>> 470 depends on !(X86_VISWS || X86_VOYAGER)
>> 471 ---help---
>> 472 A local APIC (Advanced Programmable Interrupt Controller) is an
>> 473 integrated interrupt controller in the CPU. If you have a single-CPU
>> 474 system which has a processor with a local APIC, you can say Y here to
>> 475 enable and use it. If you say Y here even though your machine doesn't
>> 476 have a local APIC, then the kernel will still run with no slowdown at
>> 477 all. The local APIC supports CPU-generated self-interrupts (timer,
>> 478 performance counters), and the NMI watchdog which detects hard
>> 479 lockups.
>> 480
>> 481 If you have a system with several CPUs, you do not need to say Y
>> 482 here: the local APIC will be used automatically.
>> 483
>> 484 config X86_UP_IOAPIC
>> 485 bool "IO-APIC support on uniprocessors"
>> 486 depends on !SMP && X86_UP_APIC
>> 487 help
>> 488 An IO-APIC (I/O Advanced Programmable Interrupt Controller) is an
>> 489 SMP-capable replacement for PC-style interrupt controllers. Most
>> 490 SMP systems and a small number of uniprocessor systems have one.
>> 491 If you have a single-CPU system with an IO-APIC, you can say Y here
>> 492 to use it. If you say Y here even though your machine doesn't have
>> 493 an IO-APIC, then the kernel will still run with no slowdown at all.
>> 494
>> 495 If you have a system with several CPUs, you do not need to say Y
>> 496 here: the IO-APIC will be used automatically.
295 497
296 This syscall is deprecated. It may h !! 498 config X86_LOCAL_APIC
297 invalid arguments. It is provided on !! 499 bool
298 Only enable it if your userspace sof !! 500 depends on !SMP && X86_UP_APIC
>> 501 default y
>> 502
>> 503 config X86_IO_APIC
>> 504 bool
>> 505 depends on !SMP && X86_UP_IOAPIC
>> 506 default y
>> 507
>> 508 config X86_TSC
>> 509 bool
>> 510 depends on (MWINCHIP3D || MWINCHIP2 || MCRUSOE || MCYRIXIII || MK7 || MK6 || MPENTIUM4 || MPENTIUMIII || MPENTIUMII || M686 || M586MMX || M586TSC || MK8 || MVIAC3_2) && !X86_NUMAQ
>> 511 default y
>> 512
>> 513 config X86_MCE
>> 514 bool "Machine Check Exception"
>> 515 ---help---
>> 516 Machine Check Exception support allows the processor to notify the
>> 517 kernel if it detects a problem (e.g. overheating, component failure).
>> 518 The action the kernel takes depends on the severity of the problem,
>> 519 ranging from a warning message on the console, to halting the machine.
>> 520 Your processor must be a Pentium or newer to support this - check the
>> 521 flags in /proc/cpuinfo for mce. Note that some older Pentium systems
>> 522 have a design flaw which leads to false MCE events - hence MCE is
>> 523 disabled on all P5 processors, unless explicitly enabled with "mce"
>> 524 as a boot argument. Similarly, if MCE is built in and creates a
>> 525 problem on some new non-standard machine, you can boot with "nomce"
>> 526 to disable it. MCE support simply ignores non-MCE processors like
>> 527 the 386 and 486, so nearly everyone can say Y here.
>> 528
>> 529 config X86_MCE_NONFATAL
>> 530 bool "Check for non-fatal errors on AMD Athlon/Duron / Intel Pentium 4"
>> 531 depends on X86_MCE
>> 532 help
>> 533 Enabling this feature starts a timer that triggers every 5 seconds which
>> 534 will look at the machine check registers to see if anything happened.
>> 535 Non-fatal problems automatically get corrected (but still logged).
>> 536 Disable this if you don't want to see these messages.
>> 537 Seeing the messages this option prints out may be indicative of dying hardware,
>> 538 or out-of-spec (ie, overclocked) hardware.
>> 539 This option only does something on certain CPUs.
>> 540 (AMD Athlon/Duron and Intel Pentium 4)
>> 541
>> 542 config X86_MCE_P4THERMAL
>> 543 bool "check for P4 thermal throttling interrupt."
>> 544 depends on X86_MCE && (X86_UP_APIC || SMP)
>> 545 help
>> 546 Enabling this feature will cause a message to be printed when the P4
>> 547 enters thermal throttling.
>> 548
>> 549 config TOSHIBA
>> 550 tristate "Toshiba Laptop support"
>> 551 ---help---
>> 552 This adds a driver to safely access the System Management Mode of
>> 553 the CPU on Toshiba portables with a genuine Toshiba BIOS. It does
>> 554 not work on models with a Phoenix BIOS. The System Management Mode
>> 555 is used to set the BIOS and power saving options on Toshiba portables.
>> 556
>> 557 For information on utilities to make use of this driver see the
>> 558 Toshiba Linux utilities web site at:
>> 559 <http://www.buzzard.org.uk/toshiba/>.
>> 560
>> 561 Say Y if you intend to run this kernel on a Toshiba portable.
>> 562 Say N otherwise.
>> 563
>> 564 config I8K
>> 565 tristate "Dell laptop support"
>> 566 ---help---
>> 567 This adds a driver to safely access the System Management Mode
>> 568 of the CPU on the Dell Inspiron 8000. The System Management Mode
>> 569 is used to read cpu temperature and cooling fan status and to
>> 570 control the fans on the I8K portables.
>> 571
>> 572 This driver has been tested only on the Inspiron 8000 but it may
>> 573 also work with other Dell laptops. You can force loading on other
>> 574 models by passing the parameter `force=1' to the module. Use at
>> 575 your own risk.
>> 576
>> 577 For information on utilities to make use of this driver see the
>> 578 I8K Linux utilities web site at:
>> 579 <http://www.debian.org/~dz/i8k/>
>> 580
>> 581 Say Y if you intend to run this kernel on a Dell Inspiron 8000.
>> 582 Say N otherwise.
>> 583
>> 584 config MICROCODE
>> 585 tristate "/dev/cpu/microcode - Intel IA32 CPU microcode support"
>> 586 ---help---
>> 587 If you say Y here and also to "/dev file system support" in the
>> 588 'File systems' section, you will be able to update the microcode on
>> 589 Intel processors in the IA32 family, e.g. Pentium Pro, Pentium II,
>> 590 Pentium III, Pentium 4, Xeon etc. You will obviously need the
>> 591 actual microcode binary data itself which is not shipped with the
>> 592 Linux kernel.
>> 593
>> 594 For latest news and information on obtaining all the required
>> 595 ingredients for this driver, check:
>> 596 <http://www.urbanmyth.org/microcode/>.
>> 597
>> 598 To compile this driver as a module, choose M here: the
>> 599 module will be called microcode.
>> 600 If you use modprobe or kmod you may also want to add the line
>> 601 'alias char-major-10-184 microcode' to your /etc/modules.conf file.
>> 602
>> 603 config X86_MSR
>> 604 tristate "/dev/cpu/*/msr - Model-specific register support"
>> 605 help
>> 606 This device gives privileged processes access to the x86
>> 607 Model-Specific Registers (MSRs). It is a character device with
>> 608 major 202 and minors 0 to 31 for /dev/cpu/0/msr to /dev/cpu/31/msr.
>> 609 MSR accesses are directed to a specific CPU on multi-processor
>> 610 systems.
>> 611
>> 612 config X86_CPUID
>> 613 tristate "/dev/cpu/*/cpuid - CPU information support"
>> 614 help
>> 615 This device gives processes access to the x86 CPUID instruction to
>> 616 be executed on a specific processor. It is a character device
>> 617 with major 203 and minors 0 to 31 for /dev/cpu/0/cpuid to
>> 618 /dev/cpu/31/cpuid.
>> 619
>> 620 config EDD
>> 621 tristate "BIOS Enhanced Disk Drive calls determine boot disk (EXPERIMENTAL)"
>> 622 depends on EXPERIMENTAL
>> 623 help
>> 624 Say Y or M here if you want to enable BIOS Enhanced Disk Drive
>> 625 Services real mode BIOS calls to determine which disk
>> 626 BIOS tries boot from. This information is then exported via driverfs.
299 627
300 If unsure, say N. !! 628 This option is experimental, but believed to be safe,
>> 629 and most disk controller BIOS vendors do not yet implement this feature.
301 630
302 choice 631 choice
303 prompt "Kernel ABI" !! 632 prompt "High Memory Support"
304 default KERNEL_ABI_DEFAULT !! 633 default NOHIGHMEM
>> 634
>> 635 config NOHIGHMEM
>> 636 bool "off"
>> 637 ---help---
>> 638 Linux can use up to 64 Gigabytes of physical memory on x86 systems.
>> 639 However, the address space of 32-bit x86 processors is only 4
>> 640 Gigabytes large. That means that, if you have a large amount of
>> 641 physical memory, not all of it can be "permanently mapped" by the
>> 642 kernel. The physical memory that's not permanently mapped is called
>> 643 "high memory".
>> 644
>> 645 If you are compiling a kernel which will never run on a machine with
>> 646 more than 1 Gigabyte total physical RAM, answer "off" here (default
>> 647 choice and suitable for most users). This will result in a "3GB/1GB"
>> 648 split: 3GB are mapped so that each process sees a 3GB virtual memory
>> 649 space and the remaining part of the 4GB virtual memory space is used
>> 650 by the kernel to permanently map as much physical memory as
>> 651 possible.
>> 652
>> 653 If the machine has between 1 and 4 Gigabytes physical RAM, then
>> 654 answer "4GB" here.
>> 655
>> 656 If more than 4 Gigabytes is used then answer "64GB" here. This
>> 657 selection turns Intel PAE (Physical Address Extension) mode on.
>> 658 PAE implements 3-level paging on IA32 processors. PAE is fully
>> 659 supported by Linux, PAE mode is implemented on all recent Intel
>> 660 processors (Pentium Pro and better). NOTE: If you say "64GB" here,
>> 661 then the kernel will not boot on CPUs that don't support PAE!
>> 662
>> 663 The actual amount of total physical memory will either be
>> 664 auto detected or can be forced by using a kernel command line option
>> 665 such as "mem=256M". (Try "man bootparam" or see the documentation of
>> 666 your boot loader (lilo or loadlin) about how to pass options to the
>> 667 kernel at boot time.)
>> 668
>> 669 If unsure, say "off".
>> 670
>> 671 config HIGHMEM4G
>> 672 bool "4GB"
305 help 673 help
306 Select ABI for the kernel code. This !! 674 Select this if you have a 32-bit processor and between 1 and 4
307 supported userspace ABI and any comb !! 675 gigabytes of physical RAM.
308 kernel/userspace ABI is possible and !! 676
309 !! 677 config HIGHMEM64G
310 In case both kernel and userspace su !! 678 bool "64GB"
311 all register windows support code wi !! 679 help
312 build. !! 680 Select this if you have a 32-bit processor and more than 4
313 !! 681 gigabytes of physical RAM.
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 682
332 endchoice 683 endchoice
333 684
334 config USER_ABI_CALL0 !! 685 config HIGHMEM
335 bool 686 bool
>> 687 depends on HIGHMEM64G || HIGHMEM4G
>> 688 default y
336 689
337 choice !! 690 config X86_PAE
338 prompt "Userspace ABI" !! 691 bool
339 default USER_ABI_DEFAULT !! 692 depends on HIGHMEM64G
340 help !! 693 default y
341 Select supported userspace ABI. <<
342 694
343 If unsure, choose the default ABI. !! 695 # Common NUMA Features
>> 696 config NUMA
>> 697 bool "Numa Memory Allocation Support"
>> 698 depends on SMP && HIGHMEM64G && (X86_PC || X86_NUMAQ || X86_GENERICARCH || (X86_SUMMIT && ACPI && !ACPI_HT_ONLY))
>> 699 default n if X86_PC
>> 700 default y if (X86_NUMAQ || X86_SUMMIT)
>> 701
>> 702 # Need comments to help the hapless user trying to turn on NUMA support
>> 703 comment "NUMA (NUMA-Q) requires SMP, 64GB highmem support"
>> 704 depends on X86_NUMAQ && (!HIGHMEM64G || !SMP)
344 705
345 config USER_ABI_DEFAULT !! 706 comment "NUMA (Summit) requires SMP, 64GB highmem support, full ACPI"
346 bool "Default ABI only" !! 707 depends on X86_SUMMIT && (!HIGHMEM64G || !ACPI || ACPI_HT_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 708
352 config USER_ABI_CALL0_ONLY !! 709 config DISCONTIGMEM
353 bool "Call0 ABI only" !! 710 bool
354 select USER_ABI_CALL0 !! 711 depends on NUMA
355 help !! 712 default y
356 Select this option to support only c <<
357 Windowed ABI binaries will crash wit <<
358 an illegal instruction exception on <<
359 713
360 Choose this option if you're plannin !! 714 config HAVE_ARCH_BOOTMEM_NODE
361 built with call0 ABI. !! 715 bool
>> 716 depends on NUMA
>> 717 default y
362 718
363 config USER_ABI_CALL0_PROBE !! 719 config HIGHPTE
364 bool "Support both windowed and call0 !! 720 bool "Allocate 3rd-level pagetables from highmem"
365 select USER_ABI_CALL0 !! 721 depends on HIGHMEM4G || HIGHMEM64G
366 help !! 722 help
367 Select this option to support both w !! 723 The VM uses one page table entry for each page of physical memory.
368 ABIs. When enabled all processes are !! 724 For systems with a lot of RAM, this can be wasteful of precious
369 and a fast user exception handler fo !! 725 low memory. Setting this option will put user-space page table
370 used to turn on PS.WOE bit on the fi !! 726 entries in high memory.
371 the userspace. !! 727
>> 728 config MATH_EMULATION
>> 729 bool "Math emulation"
>> 730 ---help---
>> 731 Linux can emulate a math coprocessor (used for floating point
>> 732 operations) if you don't have one. 486DX and Pentium processors have
>> 733 a math coprocessor built in, 486SX and 386 do not, unless you added
>> 734 a 487DX or 387, respectively. (The messages during boot time can
>> 735 give you some hints here ["man dmesg"].) Everyone needs either a
>> 736 coprocessor or this emulation.
>> 737
>> 738 If you don't have a math coprocessor, you need to say Y here; if you
>> 739 say Y here even though you have a coprocessor, the coprocessor will
>> 740 be used nevertheless. (This behavior can be changed with the kernel
>> 741 command line option "no387", which comes handy if your coprocessor
>> 742 is broken. Try "man bootparam" or see the documentation of your boot
>> 743 loader (lilo or loadlin) about how to pass options to the kernel at
>> 744 boot time.) This means that it is a good idea to say Y here if you
>> 745 intend to use this kernel on different machines.
>> 746
>> 747 More information about the internals of the Linux math coprocessor
>> 748 emulation can be found in <file:arch/i386/math-emu/README>.
>> 749
>> 750 If you are not sure, say Y; apart from resulting in a 66 KB bigger
>> 751 kernel, it won't hurt.
>> 752
>> 753 config MTRR
>> 754 bool "MTRR (Memory Type Range Register) support"
>> 755 ---help---
>> 756 On Intel P6 family processors (Pentium Pro, Pentium II and later)
>> 757 the Memory Type Range Registers (MTRRs) may be used to control
>> 758 processor access to memory ranges. This is most useful if you have
>> 759 a video (VGA) card on a PCI or AGP bus. Enabling write-combining
>> 760 allows bus write transfers to be combined into a larger transfer
>> 761 before bursting over the PCI/AGP bus. This can increase performance
>> 762 of image write operations 2.5 times or more. Saying Y here creates a
>> 763 /proc/mtrr file which may be used to manipulate your processor's
>> 764 MTRRs. Typically the X server should use this.
>> 765
>> 766 This code has a reasonably generic interface so that similar
>> 767 control registers on other processors can be easily supported
>> 768 as well:
>> 769
>> 770 The Cyrix 6x86, 6x86MX and M II processors have Address Range
>> 771 Registers (ARRs) which provide a similar functionality to MTRRs. For
>> 772 these, the ARRs are used to emulate the MTRRs.
>> 773 The AMD K6-2 (stepping 8 and above) and K6-3 processors have two
>> 774 MTRRs. The Centaur C6 (WinChip) has 8 MCRs, allowing
>> 775 write-combining. All of these processors are supported by this code
>> 776 and it makes sense to say Y here if you have one of them.
>> 777
>> 778 Saying Y here also fixes a problem with buggy SMP BIOSes which only
>> 779 set the MTRRs for the boot CPU and not for the secondary CPUs. This
>> 780 can lead to all sorts of problems, so it's good to say Y here.
372 781
373 This option should be enabled for th !! 782 You can safely say Y even if your machine doesn't have MTRRs, you'll
374 both call0 and windowed ABIs in user !! 783 just add about 9 KB to your kernel.
375 784
376 Note that Xtensa ISA does not guaran !! 785 See <file:Documentation/mtrr.txt> for more information.
377 raise an illegal instruction excepti <<
378 PS.WOE is disabled, check whether th <<
379 786
380 endchoice !! 787 config HAVE_DEC_LOCK
>> 788 bool
>> 789 depends on (SMP || PREEMPT) && X86_CMPXCHG
>> 790 default y
>> 791
>> 792 # turning this on wastes a bunch of space.
>> 793 # Summit needs it only when NUMA is on
>> 794 config BOOT_IOREMAP
>> 795 bool
>> 796 depends on ((X86_SUMMIT || X86_GENERICARCH) && NUMA)
>> 797 default y
381 798
382 endmenu 799 endmenu
383 800
384 config XTENSA_CALIBRATE_CCOUNT <<
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 801
391 config SERIAL_CONSOLE !! 802 menu "Power management options (ACPI, APM)"
392 def_bool n !! 803 depends on !X86_VOYAGER
393 804
394 config PLATFORM_HAVE_XIP !! 805 source kernel/power/Kconfig
395 def_bool n <<
396 806
397 menu "Platform options" !! 807 source "drivers/acpi/Kconfig"
398 808
399 choice !! 809 menu "APM (Advanced Power Management) BIOS Support"
400 prompt "Xtensa System Type" !! 810 depends on PM
401 default XTENSA_PLATFORM_ISS !! 811
>> 812 config APM
>> 813 tristate "APM (Advanced Power Management) BIOS support"
>> 814 depends on PM
>> 815 ---help---
>> 816 APM is a BIOS specification for saving power using several different
>> 817 techniques. This is mostly useful for battery powered laptops with
>> 818 APM compliant BIOSes. If you say Y here, the system time will be
>> 819 reset after a RESUME operation, the /proc/apm device will provide
>> 820 battery status information, and user-space programs will receive
>> 821 notification of APM "events" (e.g. battery status change).
>> 822
>> 823 If you select "Y" here, you can disable actual use of the APM
>> 824 BIOS by passing the "apm=off" option to the kernel at boot time.
>> 825
>> 826 Note that the APM support is almost completely disabled for
>> 827 machines with more than one CPU.
>> 828
>> 829 In order to use APM, you will need supporting software. For location
>> 830 and more information, read <file:Documentation/pm.txt> and the
>> 831 Battery Powered Linux mini-HOWTO, available from
>> 832 <http://www.tldp.org/docs.html#howto>.
>> 833
>> 834 This driver does not spin down disk drives (see the hdparm(8)
>> 835 manpage ("man 8 hdparm") for that), and it doesn't turn off
>> 836 VESA-compliant "green" monitors.
>> 837
>> 838 This driver does not support the TI 4000M TravelMate and the ACER
>> 839 486/DX4/75 because they don't have compliant BIOSes. Many "green"
>> 840 desktop machines also don't have compliant BIOSes, and this driver
>> 841 may cause those machines to panic during the boot phase.
>> 842
>> 843 Generally, if you don't have a battery in your machine, there isn't
>> 844 much point in using this driver and you should say N. If you get
>> 845 random kernel OOPSes or reboots that don't seem to be related to
>> 846 anything, try disabling/enabling this option (or disabling/enabling
>> 847 APM in your BIOS).
>> 848
>> 849 Some other things you should try when experiencing seemingly random,
>> 850 "weird" problems:
>> 851
>> 852 1) make sure that you have enough swap space and that it is
>> 853 enabled.
>> 854 2) pass the "no-hlt" option to the kernel
>> 855 3) switch on floating point emulation in the kernel and pass
>> 856 the "no387" option to the kernel
>> 857 4) pass the "floppy=nodma" option to the kernel
>> 858 5) pass the "mem=4M" option to the kernel (thereby disabling
>> 859 all but the first 4 MB of RAM)
>> 860 6) make sure that the CPU is not over clocked.
>> 861 7) read the sig11 FAQ at <http://www.bitwizard.nl/sig11/>
>> 862 8) disable the cache from your BIOS settings
>> 863 9) install a fan for the video card or exchange video RAM
>> 864 10) install a better fan for the CPU
>> 865 11) exchange RAM chips
>> 866 12) exchange the motherboard.
>> 867
>> 868 To compile this driver as a module, choose M here: the
>> 869 module will be called apm.
>> 870
>> 871 config APM_IGNORE_USER_SUSPEND
>> 872 bool "Ignore USER SUSPEND"
>> 873 depends on APM
>> 874 help
>> 875 This option will ignore USER SUSPEND requests. On machines with a
>> 876 compliant APM BIOS, you want to say N. However, on the NEC Versa M
>> 877 series notebooks, it is necessary to say Y because of a BIOS bug.
>> 878
>> 879 config APM_DO_ENABLE
>> 880 bool "Enable PM at boot time"
>> 881 depends on APM
>> 882 ---help---
>> 883 Enable APM features at boot time. From page 36 of the APM BIOS
>> 884 specification: "When disabled, the APM BIOS does not automatically
>> 885 power manage devices, enter the Standby State, enter the Suspend
>> 886 State, or take power saving steps in response to CPU Idle calls."
>> 887 This driver will make CPU Idle calls when Linux is idle (unless this
>> 888 feature is turned off -- see "Do CPU IDLE calls", below). This
>> 889 should always save battery power, but more complicated APM features
>> 890 will be dependent on your BIOS implementation. You may need to turn
>> 891 this option off if your computer hangs at boot time when using APM
>> 892 support, or if it beeps continuously instead of suspending. Turn
>> 893 this off if you have a NEC UltraLite Versa 33/C or a Toshiba
>> 894 T400CDT. This is off by default since most machines do fine without
>> 895 this feature.
>> 896
>> 897 config APM_CPU_IDLE
>> 898 bool "Make CPU Idle calls when idle"
>> 899 depends on APM
>> 900 help
>> 901 Enable calls to APM CPU Idle/CPU Busy inside the kernel's idle loop.
>> 902 On some machines, this can activate improved power savings, such as
>> 903 a slowed CPU clock rate, when the machine is idle. These idle calls
>> 904 are made after the idle loop has run for some length of time (e.g.,
>> 905 333 mS). On some machines, this will cause a hang at boot time or
>> 906 whenever the CPU becomes idle. (On machines with more than one CPU,
>> 907 this option does nothing.)
>> 908
>> 909 config APM_DISPLAY_BLANK
>> 910 bool "Enable console blanking using APM"
>> 911 depends on APM
>> 912 help
>> 913 Enable console blanking using the APM. Some laptops can use this to
>> 914 turn off the LCD backlight when the screen blanker of the Linux
>> 915 virtual console blanks the screen. Note that this is only used by
>> 916 the virtual console screen blanker, and won't turn off the backlight
>> 917 when using the X Window system. This also doesn't have anything to
>> 918 do with your VESA-compliant power-saving monitor. Further, this
>> 919 option doesn't work for all laptops -- it might not turn off your
>> 920 backlight at all, or it might print a lot of errors to the console,
>> 921 especially if you are using gpm.
>> 922
>> 923 config APM_RTC_IS_GMT
>> 924 bool "RTC stores time in GMT"
>> 925 depends on APM
>> 926 help
>> 927 Say Y here if your RTC (Real Time Clock a.k.a. hardware clock)
>> 928 stores the time in GMT (Greenwich Mean Time). Say N if your RTC
>> 929 stores localtime.
>> 930
>> 931 It is in fact recommended to store GMT in your RTC, because then you
>> 932 don't have to worry about daylight savings time changes. The only
>> 933 reason not to use GMT in your RTC is if you also run a broken OS
>> 934 that doesn't understand GMT.
>> 935
>> 936 config APM_ALLOW_INTS
>> 937 bool "Allow interrupts during APM BIOS calls"
>> 938 depends on APM
>> 939 help
>> 940 Normally we disable external interrupts while we are making calls to
>> 941 the APM BIOS as a measure to lessen the effects of a badly behaving
>> 942 BIOS implementation. The BIOS should reenable interrupts if it
>> 943 needs to. Unfortunately, some BIOSes do not -- especially those in
>> 944 many of the newer IBM Thinkpads. If you experience hangs when you
>> 945 suspend, try setting this to Y. Otherwise, say N.
>> 946
>> 947 config APM_REAL_MODE_POWER_OFF
>> 948 bool "Use real mode APM BIOS call to power off"
>> 949 depends on APM
>> 950 help
>> 951 Use real mode APM BIOS calls to switch off the computer. This is
>> 952 a work-around for a number of buggy BIOSes. Switch this option on if
>> 953 your computer crashes instead of powering off properly.
402 954
403 config XTENSA_PLATFORM_ISS !! 955 endmenu
404 bool "ISS" <<
405 select XTENSA_CALIBRATE_CCOUNT <<
406 select SERIAL_CONSOLE <<
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 956
427 endchoice !! 957 source "arch/i386/kernel/cpu/cpufreq/Kconfig"
428 958
429 config PLATFORM_NR_IRQS !! 959 endmenu
430 int <<
431 default 3 if XTENSA_PLATFORM_XT2000 <<
432 default 0 <<
433 960
434 config XTENSA_CPU_CLOCK <<
435 int "CPU clock rate [MHz]" <<
436 depends on !XTENSA_CALIBRATE_CCOUNT <<
437 default 16 <<
438 961
439 config GENERIC_CALIBRATE_DELAY !! 962 menu "Bus options (PCI, PCMCIA, EISA, MCA, ISA)"
440 bool "Auto calibration of the BogoMIPS <<
441 help <<
442 The BogoMIPS value can easily be der <<
443 963
444 config CMDLINE_BOOL !! 964 config X86_VISWS_APIC
445 bool "Default bootloader kernel argume !! 965 bool
>> 966 depends on X86_VISWS
>> 967 default y
446 968
447 config CMDLINE !! 969 config X86_LOCAL_APIC
448 string "Initial kernel command string" !! 970 bool
449 depends on CMDLINE_BOOL !! 971 depends on (X86_VISWS || SMP) && !X86_VOYAGER
450 default "console=ttyS0,38400 root=/dev !! 972 default y
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 973
458 config USE_OF !! 974 config X86_IO_APIC
459 bool "Flattened Device Tree support" !! 975 bool
460 select OF !! 976 depends on SMP && !(X86_VISWS || X86_VOYAGER)
461 select OF_EARLY_FLATTREE !! 977 default y
462 help !! 978
463 Include support for flattened device !! 979 config PCI
>> 980 bool "PCI support" if !X86_VISWS
>> 981 depends on !X86_VOYAGER
>> 982 default y if X86_VISWS
>> 983 help
>> 984 Find out whether you have a PCI motherboard. PCI is the name of a
>> 985 bus system, i.e. the way the CPU talks to the other stuff inside
>> 986 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
>> 987 VESA. If you have PCI, say Y, otherwise N.
>> 988
>> 989 The PCI-HOWTO, available from
>> 990 <http://www.tldp.org/docs.html#howto>, contains valuable
>> 991 information about which PCI hardware does work under Linux and which
>> 992 doesn't.
>> 993
>> 994 choice
>> 995 prompt "PCI access mode"
>> 996 depends on PCI && !X86_VISWS
>> 997 default PCI_GOANY
>> 998
>> 999 config PCI_GOBIOS
>> 1000 bool "BIOS"
>> 1001 ---help---
>> 1002 On PCI systems, the BIOS can be used to detect the PCI devices and
>> 1003 determine their configuration. However, some old PCI motherboards
>> 1004 have BIOS bugs and may crash if this is done. Also, some embedded
>> 1005 PCI-based systems don't have any BIOS at all. Linux can also try to
>> 1006 detect the PCI hardware directly without using the BIOS.
>> 1007
>> 1008 With this option, you can specify how Linux should detect the PCI
>> 1009 devices. If you choose "BIOS", the BIOS will be used, if you choose
>> 1010 "Direct", the BIOS won't be used, and if you choose "Any", the
>> 1011 kernel will try the direct access method and falls back to the BIOS
>> 1012 if that doesn't work. If unsure, go with the default, which is
>> 1013 "Any".
>> 1014
>> 1015 config PCI_GODIRECT
>> 1016 bool "Direct"
>> 1017
>> 1018 config PCI_GOANY
>> 1019 bool "Any"
464 1020
465 config BUILTIN_DTB_SOURCE !! 1021 endchoice
466 string "DTB to build into the kernel i <<
467 depends on OF <<
468 1022
469 config PARSE_BOOTPARAM !! 1023 config PCI_BIOS
470 bool "Parse bootparam block" !! 1024 bool
>> 1025 depends on !X86_VISWS && PCI && (PCI_GOBIOS || PCI_GOANY)
471 default y 1026 default y
472 help <<
473 Parse parameters passed to the kerne <<
474 be disabled if the kernel is known t <<
475 1027
476 If unsure, say Y. !! 1028 config PCI_DIRECT
>> 1029 bool
>> 1030 depends on PCI && ((PCI_GODIRECT || PCI_GOANY) || X86_VISWS)
>> 1031 default y
477 1032
478 choice !! 1033 source "drivers/pci/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 1034
486 config XTENSA_SIMCALL_ISS !! 1035 config ISA
487 bool "simcall" !! 1036 bool "ISA support"
>> 1037 depends on !(X86_VOYAGER || X86_VISWS)
488 help 1038 help
489 Use simcall instruction. simcall is !! 1039 Find out whether you have ISA slots on your motherboard. ISA is the
490 it does nothing on hardware. !! 1040 name of a bus system, i.e. the way the CPU talks to the other stuff
>> 1041 inside your box. Other bus systems are PCI, EISA, MicroChannel
>> 1042 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
>> 1043 newer boards don't support it. If you have ISA, say Y, otherwise N.
491 1044
492 config XTENSA_SIMCALL_GDBIO !! 1045 config EISA
493 bool "GDBIO" !! 1046 bool "EISA support"
494 help !! 1047 depends on ISA
495 Use break instruction. It is availab !! 1048 ---help---
496 is attached to it via JTAG. !! 1049 The Extended Industry Standard Architecture (EISA) bus was
>> 1050 developed as an open alternative to the IBM MicroChannel bus.
497 1051
498 endchoice !! 1052 The EISA bus provided some of the features of the IBM MicroChannel
>> 1053 bus while maintaining backward compatibility with cards made for
>> 1054 the older ISA bus. The EISA bus saw limited use between 1988 and
>> 1055 1995 when it was made obsolete by the PCI bus.
499 1056
500 config BLK_DEV_SIMDISK !! 1057 Say Y here if you are building a kernel for an EISA-based machine.
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 <<
545 If unsure, say N. <<
546 <<
547 config XTFPGA_LCD_BASE_ADDR <<
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 <<
617 If unsure, say N. <<
618 <<
619 config MEMMAP_CACHEATTR <<
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 1058
683 If unsure, leave the default value h !! 1059 Otherwise, say N.
684 1060
685 choice !! 1061 source "drivers/eisa/Kconfig"
686 prompt "Relocatable vectors location" !! 1062
687 default XTENSA_VECTORS_IN_TEXT !! 1063 config MCA
>> 1064 bool "MCA support"
>> 1065 depends on !(X86_VISWS || X86_VOYAGER)
688 help 1066 help
689 Choose whether relocatable vectors a !! 1067 MicroChannel Architecture is found in some IBM PS/2 machines and
690 or placed separately at runtime. Thi !! 1068 laptops. It is a bus system similar to PCI or ISA. See
691 configurations without VECBASE regis !! 1069 <file:Documentation/mca.txt> (and especially the web page given
692 placed at their hardware-defined loc !! 1070 there) before attempting to build an MCA bus kernel.
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 1071
711 endchoice !! 1072 config MCA
>> 1073 depends on X86_VOYAGER
>> 1074 default y if X86_VOYAGER
712 1075
713 config VECTORS_ADDR !! 1076 source "drivers/mca/Kconfig"
714 hex "Kernel vectors virtual address" !! 1077
715 default 0x00000000 !! 1078 config SCx200
716 depends on XTENSA_VECTORS_SEPARATE !! 1079 tristate "NatSemi SCx200 support"
717 help !! 1080 depends on !X86_VOYAGER
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 1081 help
738 This is the base address used for bo !! 1082 This provides basic support for the National Semiconductor SCx200
739 in noMMU configurations. !! 1083 processor. Right now this is just a driver for the GPIO pins.
740 1084
741 If unsure, leave the default value h !! 1085 If you don't know what to do here, say N.
742 1086
743 choice !! 1087 This support is also available as a module. If compiled as a
744 prompt "KSEG layout" !! 1088 module, it will be called scx200.
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 1089
772 endchoice !! 1090 config HOTPLUG
>> 1091 bool "Support for hot-pluggable devices"
>> 1092 ---help---
>> 1093 Say Y here if you want to plug devices into your computer while
>> 1094 the system is running, and be able to use them quickly. In many
>> 1095 cases, the devices can likewise be unplugged at any time too.
773 1096
774 config HIGHMEM !! 1097 One well known example of this is PCMCIA- or PC-cards, credit-card
775 bool "High Memory Support" !! 1098 size devices such as network cards, modems or hard drives which are
776 depends on MMU !! 1099 plugged into slots found on all modern laptop computers. Another
777 select KMAP_LOCAL !! 1100 example, used on modern desktops as well as laptops, is USB.
778 help !! 1101
779 Linux can use the full amount of RAM !! 1102 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
780 default. However, the default MMUv2 !! 1103 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
781 lowermost 128 MB of memory linearly !! 1104 Then your kernel will automatically call out to a user mode "policy
782 at 0xd0000000 (cached) and 0xd800000 !! 1105 agent" (/sbin/hotplug) to load modules and set up software needed
783 When there are more than 128 MB memo !! 1106 to use devices as you hotplug them.
784 all of it can be "permanently mapped <<
785 The physical memory that's not perma <<
786 "high memory". <<
787 1107
788 If you are compiling a kernel which !! 1108 source "drivers/pcmcia/Kconfig"
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 1109
805 Don't change if unsure. !! 1110 source "drivers/pci/hotplug/Kconfig"
806 1111
807 endmenu 1112 endmenu
808 1113
809 menu "Power management options" <<
810 1114
811 config ARCH_HIBERNATION_POSSIBLE !! 1115 menu "Executable file formats"
812 def_bool y <<
813 1116
814 source "kernel/power/Kconfig" !! 1117 source "fs/Kconfig.binfmt"
815 1118
816 endmenu 1119 endmenu
>> 1120
>> 1121 source "drivers/Kconfig"
>> 1122
>> 1123 source "fs/Kconfig"
>> 1124
>> 1125 source "arch/i386/oprofile/Kconfig"
>> 1126
>> 1127
>> 1128 menu "Kernel hacking"
>> 1129
>> 1130 config DEBUG_KERNEL
>> 1131 bool "Kernel debugging"
>> 1132 help
>> 1133 Say Y here if you are developing drivers or trying to debug and
>> 1134 identify kernel problems.
>> 1135
>> 1136 config DEBUG_STACKOVERFLOW
>> 1137 bool "Check for stack overflows"
>> 1138 depends on DEBUG_KERNEL
>> 1139
>> 1140 config DEBUG_SLAB
>> 1141 bool "Debug memory allocations"
>> 1142 depends on DEBUG_KERNEL
>> 1143 help
>> 1144 Say Y here to have the kernel do limited verification on memory
>> 1145 allocation as well as poisoning memory on free to catch use of freed
>> 1146 memory.
>> 1147
>> 1148 config DEBUG_IOVIRT
>> 1149 bool "Memory mapped I/O debugging"
>> 1150 depends on DEBUG_KERNEL
>> 1151 help
>> 1152 Say Y here to get warned whenever an attempt is made to do I/O on
>> 1153 obviously invalid addresses such as those generated when ioremap()
>> 1154 calls are forgotten. Memory mapped I/O will go through an extra
>> 1155 check to catch access to unmapped ISA addresses, an access method
>> 1156 that can still be used by old drivers that are being ported from
>> 1157 2.0/2.2.
>> 1158
>> 1159 config MAGIC_SYSRQ
>> 1160 bool "Magic SysRq key"
>> 1161 depends on DEBUG_KERNEL
>> 1162 help
>> 1163 If you say Y here, you will have some control over the system even
>> 1164 if the system crashes for example during kernel debugging (e.g., you
>> 1165 will be able to flush the buffer cache to disk, reboot the system
>> 1166 immediately or dump some status information). This is accomplished
>> 1167 by pressing various keys while holding SysRq (Alt+PrintScreen). It
>> 1168 also works on a serial console (on PC hardware at least), if you
>> 1169 send a BREAK and then within 5 seconds a command keypress. The
>> 1170 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
>> 1171 unless you really know what this hack does.
>> 1172
>> 1173 config DEBUG_SPINLOCK
>> 1174 bool "Spinlock debugging"
>> 1175 depends on DEBUG_KERNEL
>> 1176 help
>> 1177 Say Y here and build SMP to catch missing spinlock initialization
>> 1178 and certain other kinds of spinlock errors commonly made. This is
>> 1179 best used in conjunction with the NMI watchdog so that spinlock
>> 1180 deadlocks are also debuggable.
>> 1181
>> 1182 config DEBUG_PAGEALLOC
>> 1183 bool "Page alloc debugging"
>> 1184 depends on DEBUG_KERNEL
>> 1185 help
>> 1186 Unmap pages from the kernel linear mapping after free_pages().
>> 1187 This results in a large slowdown, but helps to find certain types
>> 1188 of memory corruptions.
>> 1189
>> 1190 config DEBUG_HIGHMEM
>> 1191 bool "Highmem debugging"
>> 1192 depends on DEBUG_KERNEL && HIGHMEM
>> 1193 help
>> 1194 This options enables addition error checking for high memory systems.
>> 1195 Disable for production systems.
>> 1196
>> 1197 config DEBUG_INFO
>> 1198 bool "Compile the kernel with debug info"
>> 1199 depends on DEBUG_KERNEL
>> 1200 help
>> 1201 If you say Y here the resulting kernel image will include
>> 1202 debugging info resulting in a larger kernel image.
>> 1203 Say Y here only if you plan to use gdb to debug the kernel.
>> 1204 If you don't debug the kernel, you can say N.
>> 1205
>> 1206 config DEBUG_SPINLOCK_SLEEP
>> 1207 bool "Sleep-inside-spinlock checking"
>> 1208 help
>> 1209 If you say Y here, various routines which may sleep will become very
>> 1210 noisy if they are called with a spinlock held.
>> 1211
>> 1212 config FRAME_POINTER
>> 1213 bool "Compile the kernel with frame pointers"
>> 1214 help
>> 1215 If you say Y here the resulting kernel image will be slightly larger
>> 1216 and slower, but it will give very useful debugging information.
>> 1217 If you don't debug the kernel, you can say N, but we may not be able
>> 1218 to solve problems without frame pointers.
>> 1219
>> 1220 config X86_EXTRA_IRQS
>> 1221 bool
>> 1222 depends on X86_LOCAL_APIC || X86_VOYAGER
>> 1223 default y
>> 1224
>> 1225 config X86_FIND_SMP_CONFIG
>> 1226 bool
>> 1227 depends on X86_LOCAL_APIC || X86_VOYAGER
>> 1228 default y
>> 1229
>> 1230 config X86_MPPARSE
>> 1231 bool
>> 1232 depends on X86_LOCAL_APIC && !X86_VISWS
>> 1233 default y
>> 1234
>> 1235 endmenu
>> 1236
>> 1237 source "security/Kconfig"
>> 1238
>> 1239 source "crypto/Kconfig"
>> 1240
>> 1241 source "lib/Kconfig"
>> 1242
>> 1243 config X86_SMP
>> 1244 bool
>> 1245 depends on SMP && !X86_VOYAGER
>> 1246 default y
>> 1247
>> 1248 config X86_HT
>> 1249 bool
>> 1250 depends on SMP && !(X86_VISWS || X86_VOYAGER)
>> 1251 default y
>> 1252
>> 1253 config X86_BIOS_REBOOT
>> 1254 bool
>> 1255 depends on !(X86_VISWS || X86_VOYAGER)
>> 1256 default y
>> 1257
>> 1258 config X86_TRAMPOLINE
>> 1259 bool
>> 1260 depends on SMP || X86_VISWS
>> 1261 default y
>> 1262
>> 1263 config PC
>> 1264 bool
>> 1265 depends on X86 && !EMBEDDED
>> 1266 default y
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.