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 used for
55 optimizing purposes. In order to compile a kernel that can run on
56 all PA CPUs (albeit not optimally fast), you can specify "PA7000"
59 Specifying "PA8000" here will allow you to select a 64-bit kernel
60 which is required on some machines.
63 bool "PA7100LC/PA7300LC"
65 Select this option for a 7100LC or 7300LC processor, as used
66 in the 712, 715/Mirage, A180, B132, C160L and some other machines.
71 Select this option for the PCX-T' processor, as used in C110, D100
77 Select this option for PCX-U to PCX-W2 processors.
81 # Define implied options from the CPU selection here
90 depends on PA7000 || PA7100LC || PA7200
97 Enable this if you want to support 64bit kernel on PA-RISC platform.
99 At the moment, only people willing to use more than 2GB of RAM,
100 or having a 64bit-only capable PA-RISC machine should say Y here.
102 Since there is no 64bit userland on PA-RISC, there is no point to
103 enable this option otherwise. The 64bit kernel is significantly bigger
104 and slower than the 32bit one.
110 bool "32-bit firmware"
113 This option will enable owners of C160, C180, C200, C240, C360, J280,
114 J282, J2240 and some D/K/R class to run a 64bit kernel with their
117 Nobody should try this option unless they know what they are doing.
122 bool "Symmetric multi-processing support"
124 This enables support for systems with more than one CPU. If you have
125 a system with only one CPU, like most personal computers, say N. If
126 you have a system with more than one CPU, say Y.
128 If you say N here, the kernel will run on single and multiprocessor
129 machines, but will use only one CPU of a multiprocessor machine. If
130 you say Y here, the kernel will run on many, but not all,
131 singleprocessor machines. On a singleprocessor machine, the kernel
132 will run faster if you say N here.
134 See also the <file:Documentation/smp.txt>,
135 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available
136 at <http://www.tldp.org/docs.html#howto>.
138 If you don't know what to do here, say N.
142 # bool "Preemptible Kernel"
151 bool "Support for HP-UX binaries"
155 int "Maximum number of CPUs (2-32)"
163 source "drivers/parisc/Kconfig"
166 menu "Executable file formats"
168 source "fs/Kconfig.binfmt"
172 source "drivers/Kconfig"
176 source "arch/parisc/oprofile/Kconfig"
178 menu "Kernel hacking"
181 bool "Kernel debugging"
183 Say Y here if you are developing drivers or trying to debug and
184 identify kernel problems.
187 bool "Debug memory allocations"
188 depends on DEBUG_KERNEL
190 Say Y here to have the kernel do limited verification on memory
191 allocation as well as poisoning memory on free to catch use of freed
195 bool "Magic SysRq key"
196 depends on DEBUG_KERNEL
198 If you say Y here, you will have some control over the system even
199 if the system crashes for example during kernel debugging (e.g., you
200 will be able to flush the buffer cache to disk, reboot the system
201 immediately or dump some status information). This is accomplished
202 by pressing various keys while holding SysRq (Alt+PrintScreen). It
203 also works on a serial console (on PC hardware at least), if you
204 send a BREAK and then within 5 seconds a command keypress. The
205 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
206 unless you really know what this hack does.
209 bool "Compile the kernel with frame pointers"
211 If you say Y here the resulting kernel image will be slightly larger
212 and slower, but it will give very useful debugging information.
213 If you don't debug the kernel, you can say N, but we may not be able
214 to solve problems without frame pointers.
217 bool "Compile the kernel with debug info"
218 depends on DEBUG_KERNEL
220 If you say Y here the resulting kernel image will include
221 debugging info resulting in a larger kernel image.
222 Say Y here only if you plan to use gdb to debug the kernel.
223 If you don't debug the kernel, you can say N.
227 source "kernel/vserver/Kconfig"
229 source "security/Kconfig"
231 source "crypto/Kconfig"