2 # For a description of the syntax of this configuration file,
3 # see Documentation/kbuild/kconfig-language.txt.
6 mainmenu "Linux/PA-RISC Kernel Configuration"
12 The PA-RISC microprocessor is designed by Hewlett-Packard and used
13 in many of their workstations & servers (HP9000 700 and 800 series,
14 and later HP3000 series). The PA-RISC Linux project home page is
15 at <http://www.parisc-linux.org/>.
28 config RWSEM_GENERIC_SPINLOCK
32 config RWSEM_XCHGADD_ALGORITHM
35 config GENERIC_ISA_DMA
38 # unless you want to implement ACPI on PA-RISC ... ;-)
45 menu "Processor type and features"
48 prompt "Processor type"
54 This is the processor type of your CPU. This information is
55 used for optimizing purposes. In order to compile a kernel
56 that can run on all 32-bit PA CPUs (albeit not optimally fast),
57 you can specify "PA7000" here.
59 Specifying "PA8000" here will allow you to select a 64-bit kernel
60 which is required on some machines.
65 Select this option for the PCX-L processor, as used in the
66 712, 715/64, 715/80, 715/100, 715/100XC, 725/100, 743, 748,
67 D200, D210, D300, D310 and E-class
72 Select this option for the PCX-T' processor, as used in the
73 C100, C110, J100, J110, J210XC, D250, D260, D350, D360,
74 K100, K200, K210, K220, K400, K410 and K420
79 Select this option for the PCX-L2 processor, as used in the
80 744, A180, B132L, B160L, B180L, C132L, C160L, C180L,
81 D220, D230, D320 and D330.
86 Select this option for PCX-U to PCX-W2 processors.
90 # Define implied options from the CPU selection here
98 depends on PA7000 || PA7100LC || PA7200 || PA7300LC
108 Enable this if you want to support 64bit kernel on PA-RISC platform.
110 At the moment, only people willing to use more than 2GB of RAM,
111 or having a 64bit-only capable PA-RISC machine should say Y here.
113 Since there is no 64bit userland on PA-RISC, there is no point to
114 enable this option otherwise. The 64bit kernel is significantly bigger
115 and slower than the 32bit one.
121 bool "Symmetric multi-processing support"
123 This enables support for systems with more than one CPU. If you have
124 a system with only one CPU, like most personal computers, say N. If
125 you have a system with more than one CPU, say Y.
127 If you say N here, the kernel will run on single and multiprocessor
128 machines, but will use only one CPU of a multiprocessor machine. If
129 you say Y here, the kernel will run on many, but not all,
130 singleprocessor machines. On a singleprocessor machine, the kernel
131 will run faster if you say N here.
133 See also the <file:Documentation/smp.txt>,
134 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available
135 at <http://www.tldp.org/docs.html#howto>.
137 If you don't know what to do here, say N.
145 bool "Discontiguous memory support (EXPERIMENTAL)"
146 depends on EXPERIMENTAL
148 Say Y to support efficient handling of discontiguous physical memory,
149 for architectures which are either NUMA (Non-Uniform Memory Access)
150 or have huge holes in the physical address space for other reasons.
151 See <file:Documentation/vm/numa> for more.
155 # bool "Preemptible Kernel"
164 bool "Support for HP-UX binaries"
168 int "Maximum number of CPUs (2-32)"
176 source "drivers/parisc/Kconfig"
179 menu "Executable file formats"
181 source "fs/Kconfig.binfmt"
185 source "drivers/Kconfig"
189 source "arch/parisc/oprofile/Kconfig"
191 menu "Kernel hacking"
194 bool "Kernel debugging"
196 Say Y here if you are developing drivers or trying to debug and
197 identify kernel problems.
200 bool "Debug memory allocations"
201 depends on DEBUG_KERNEL
203 Say Y here to have the kernel do limited verification on memory
204 allocation as well as poisoning memory on free to catch use of freed
208 bool "Magic SysRq key"
209 depends on DEBUG_KERNEL
211 If you say Y here, you will have some control over the system even
212 if the system crashes for example during kernel debugging (e.g., you
213 will be able to flush the buffer cache to disk, reboot the system
214 immediately or dump some status information). This is accomplished
215 by pressing various keys while holding SysRq (Alt+PrintScreen). It
216 also works on a serial console (on PC hardware at least), if you
217 send a BREAK and then within 5 seconds a command keypress. The
218 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
219 unless you really know what this hack does.
221 config DEBUG_SPINLOCK
222 bool "Spinlock debugging"
223 depends on DEBUG_KERNEL
225 Say Y here and build SMP to catch missing spinlock initialization
226 and certain other kinds of spinlock errors commonly made. This is
227 best used in conjunction with the NMI watchdog so that spinlock
228 deadlocks are also debuggable.
231 bool "Read-write spinlock debugging"
232 depends on DEBUG_KERNEL && SMP
234 If you say Y here then read-write lock processing will count how many
235 times it has tried to get the lock and issue an error message after
236 too many attempts. If you suspect a rwlock problem or a kernel
237 hacker asks for this option then say Y. Otherwise say N.
240 bool "Compile the kernel with frame pointers"
242 If you say Y here the resulting kernel image will be slightly larger
243 and slower, but it will give very useful debugging information.
244 If you don't debug the kernel, you can say N, but we may not be able
245 to solve problems without frame pointers.
248 bool "Compile the kernel with debug info"
249 depends on DEBUG_KERNEL
251 If you say Y here the resulting kernel image will include
252 debugging info resulting in a larger kernel image.
253 Say Y here only if you plan to use gdb to debug the kernel.
254 If you don't debug the kernel, you can say N.
258 source "kernel/vserver/Kconfig"
260 source "security/Kconfig"
262 source "crypto/Kconfig"