1 # SPDX-License-Identifier: GPL-2.0-only !! 1 # $Id: config.in,v 1.113 2002/01/24 22:14:44 davem Exp $
2 config CSKY !! 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_DMA_PREP_COHERENT <<
7 select ARCH_HAS_GCOV_PROFILE_ALL <<
8 select ARCH_HAS_SYNC_DMA_FOR_CPU <<
9 select ARCH_HAS_SYNC_DMA_FOR_DEVICE <<
10 select ARCH_USE_BUILTIN_BSWAP <<
11 select ARCH_USE_QUEUED_RWLOCKS <<
12 select ARCH_USE_QUEUED_SPINLOCKS <<
13 select ARCH_HAS_CURRENT_STACK_POINTER <<
14 select ARCH_INLINE_READ_LOCK if !PREEM <<
15 select ARCH_INLINE_READ_LOCK_BH if !PR <<
16 select ARCH_INLINE_READ_LOCK_IRQ if !P <<
17 select ARCH_INLINE_READ_LOCK_IRQSAVE i <<
18 select ARCH_INLINE_READ_UNLOCK if !PRE <<
19 select ARCH_INLINE_READ_UNLOCK_BH if ! <<
20 select ARCH_INLINE_READ_UNLOCK_IRQ if <<
21 select ARCH_INLINE_READ_UNLOCK_IRQREST <<
22 select ARCH_INLINE_WRITE_LOCK if !PREE <<
23 select ARCH_INLINE_WRITE_LOCK_BH if !P <<
24 select ARCH_INLINE_WRITE_LOCK_IRQ if ! <<
25 select ARCH_INLINE_WRITE_LOCK_IRQSAVE <<
26 select ARCH_INLINE_WRITE_UNLOCK if !PR <<
27 select ARCH_INLINE_WRITE_UNLOCK_BH if <<
28 select ARCH_INLINE_WRITE_UNLOCK_IRQ if <<
29 select ARCH_INLINE_WRITE_UNLOCK_IRQRES <<
30 select ARCH_INLINE_SPIN_TRYLOCK if !PR <<
31 select ARCH_INLINE_SPIN_TRYLOCK_BH if <<
32 select ARCH_INLINE_SPIN_LOCK if !PREEM <<
33 select ARCH_INLINE_SPIN_LOCK_BH if !PR <<
34 select ARCH_INLINE_SPIN_LOCK_IRQ if !P <<
35 select ARCH_INLINE_SPIN_LOCK_IRQSAVE i <<
36 select ARCH_INLINE_SPIN_UNLOCK if !PRE <<
37 select ARCH_INLINE_SPIN_UNLOCK_BH if ! <<
38 select ARCH_INLINE_SPIN_UNLOCK_IRQ if <<
39 select ARCH_INLINE_SPIN_UNLOCK_IRQREST <<
40 select ARCH_NEED_CMPXCHG_1_EMU <<
41 select ARCH_WANT_FRAME_POINTERS if !CP <<
42 select ARCH_WANT_DEFAULT_TOPDOWN_MMAP_ <<
43 select COMMON_CLK <<
44 select CLKSRC_MMIO <<
45 select CSKY_MPINTC if CPU_CK860 <<
46 select CSKY_MP_TIMER if CPU_CK860 <<
47 select CSKY_APB_INTC <<
48 select DMA_DIRECT_REMAP <<
49 select IRQ_DOMAIN <<
50 select DW_APB_TIMER_OF <<
51 select GENERIC_IOREMAP <<
52 select GENERIC_LIB_ASHLDI3 <<
53 select GENERIC_LIB_ASHRDI3 <<
54 select GENERIC_LIB_LSHRDI3 <<
55 select GENERIC_LIB_MULDI3 <<
56 select GENERIC_LIB_CMPDI2 <<
57 select GENERIC_LIB_UCMPDI2 <<
58 select GENERIC_ALLOCATOR <<
59 select GENERIC_ATOMIC64 <<
60 select GENERIC_CPU_DEVICES <<
61 select GENERIC_IRQ_CHIP <<
62 select GENERIC_IRQ_PROBE <<
63 select GENERIC_IRQ_SHOW <<
64 select GENERIC_IRQ_MULTI_HANDLER <<
65 select GENERIC_SCHED_CLOCK <<
66 select GENERIC_SMP_IDLE_THREAD <<
67 select GENERIC_TIME_VSYSCALL <<
68 select GENERIC_VDSO_32 <<
69 select GENERIC_GETTIMEOFDAY <<
70 select GX6605S_TIMER if CPU_CK610 <<
71 select HAVE_ARCH_TRACEHOOK <<
72 select HAVE_ARCH_AUDITSYSCALL <<
73 select HAVE_ARCH_JUMP_LABEL if !CPU_CK <<
74 select HAVE_ARCH_JUMP_LABEL_RELATIVE <<
75 select HAVE_ARCH_MMAP_RND_BITS <<
76 select HAVE_ARCH_SECCOMP_FILTER <<
77 select HAVE_CONTEXT_TRACKING_USER <<
78 select HAVE_VIRT_CPU_ACCOUNTING_GEN <<
79 select HAVE_DEBUG_BUGVERBOSE <<
80 select HAVE_DEBUG_KMEMLEAK <<
81 select HAVE_DYNAMIC_FTRACE <<
82 select HAVE_DYNAMIC_FTRACE_WITH_REGS <<
83 select HAVE_GENERIC_VDSO <<
84 select HAVE_FUNCTION_TRACER <<
85 select HAVE_FUNCTION_GRAPH_TRACER <<
86 select HAVE_FUNCTION_ERROR_INJECTION <<
87 select HAVE_FTRACE_MCOUNT_RECORD <<
88 select HAVE_KERNEL_GZIP <<
89 select HAVE_KERNEL_LZO <<
90 select HAVE_KERNEL_LZMA <<
91 select HAVE_KPROBES if !CPU_CK610 <<
92 select HAVE_KPROBES_ON_FTRACE if !CPU_ <<
93 select HAVE_KRETPROBES if !CPU_CK610 <<
94 select HAVE_PAGE_SIZE_4KB <<
95 select HAVE_PERF_EVENTS <<
96 select HAVE_PERF_REGS <<
97 select HAVE_PERF_USER_STACK_DUMP <<
98 select HAVE_DMA_CONTIGUOUS <<
99 select HAVE_REGS_AND_STACK_ACCESS_API <<
100 select HAVE_STACKPROTECTOR <<
101 select HAVE_SYSCALL_TRACEPOINTS <<
102 select HOTPLUG_CORE_SYNC_DEAD if HOTPL <<
103 select LOCK_MM_AND_FIND_VMA <<
104 select MAY_HAVE_SPARSE_IRQ <<
105 select MODULES_USE_ELF_RELA if MODULES <<
106 select OF <<
107 select OF_EARLY_FLATTREE <<
108 select PERF_USE_VMALLOC if CPU_CK610 <<
109 select RTC_LIB <<
110 select TIMER_OF <<
111 select GENERIC_PCI_IOMAP <<
112 select HAVE_PCI <<
113 select PCI_DOMAINS_GENERIC if PCI <<
114 select PCI_SYSCALL if PCI <<
115 select PCI_MSI if PCI <<
116 select TRACE_IRQFLAGS_SUPPORT <<
117 <<
118 config LOCKDEP_SUPPORT <<
119 def_bool y <<
120 <<
121 config ARCH_SUPPORTS_UPROBES <<
122 def_bool y if !CPU_CK610 <<
123 <<
124 config CPU_HAS_CACHEV2 <<
125 bool <<
126 <<
127 config CPU_HAS_FPUV2 <<
128 bool <<
129 <<
130 config CPU_HAS_HILO <<
131 bool <<
132 <<
133 config CPU_HAS_TLBI <<
134 bool <<
135 <<
136 config CPU_HAS_LDSTEX <<
137 bool <<
138 help <<
139 For SMP, CPU needs "ldex&stex" instr <<
140 <<
141 config CPU_NEED_TLBSYNC <<
142 bool <<
143 <<
144 config CPU_NEED_SOFTALIGN <<
145 bool <<
146 <<
147 config CPU_NO_USER_BKPT <<
148 bool <<
149 help <<
150 For abiv2 we couldn't use "trap 1" a <<
151 abiv2 is 16/32bit instruction set an <<
152 So we need a 16bit instruction as us <<
153 instruction exception. <<
154 In kernel we parse the *regs->pc to <<
155 5
156 config GENERIC_CALIBRATE_DELAY !! 6 mainmenu "Linux/SPARC Kernel Configuration"
157 def_bool y <<
158 7
159 config GENERIC_CSUM !! 8 config MMU
160 def_bool y !! 9 bool
>> 10 default y
161 11
162 config GENERIC_HWEIGHT !! 12 config UID16
163 def_bool y !! 13 bool
>> 14 default y
164 15
165 config MMU !! 16 config HIGHMEM
166 def_bool y !! 17 bool
>> 18 default y
167 19
168 config STACKTRACE_SUPPORT !! 20 config GENERIC_ISA_DMA
169 def_bool y !! 21 bool
>> 22 default y
170 23
171 config TIME_LOW_RES !! 24 source "init/Kconfig"
172 def_bool y <<
173 25
174 config CPU_ASID_BITS <<
175 int <<
176 default "8" if (CPU_CK610 || CPU_C <<
177 default "12" if (CPU_CK860) <<
178 <<
179 config L1_CACHE_SHIFT <<
180 int <<
181 default "4" if (CPU_CK610) <<
182 default "5" if (CPU_CK807 || CPU_C <<
183 default "6" if (CPU_CK860) <<
184 <<
185 config ARCH_MMAP_RND_BITS_MIN <<
186 default 8 <<
187 <<
188 # max bits determined by the following formula <<
189 # VA_BITS - PAGE_SHIFT - 3 <<
190 config ARCH_MMAP_RND_BITS_MAX <<
191 default 17 <<
192 <<
193 menu "Processor type and features" <<
194 <<
195 choice <<
196 prompt "CPU MODEL" <<
197 default CPU_CK807 <<
198 <<
199 config CPU_CK610 <<
200 bool "CSKY CPU ck610" <<
201 select CPU_NEED_TLBSYNC <<
202 select CPU_NEED_SOFTALIGN <<
203 select CPU_NO_USER_BKPT <<
204 <<
205 config CPU_CK810 <<
206 bool "CSKY CPU ck810" <<
207 select CPU_HAS_HILO <<
208 select CPU_NEED_TLBSYNC <<
209 <<
210 config CPU_CK807 <<
211 bool "CSKY CPU ck807" <<
212 select CPU_HAS_HILO <<
213 <<
214 config CPU_CK860 <<
215 bool "CSKY CPU ck860" <<
216 select CPU_HAS_TLBI <<
217 select CPU_HAS_CACHEV2 <<
218 select CPU_HAS_LDSTEX <<
219 select CPU_HAS_FPUV2 <<
220 endchoice <<
221 <<
222 choice <<
223 prompt "PAGE OFFSET" <<
224 default PAGE_OFFSET_80000000 <<
225 <<
226 config PAGE_OFFSET_80000000 <<
227 bool "PAGE OFFSET 2G (user:kernel = 2: <<
228 <<
229 config PAGE_OFFSET_A0000000 <<
230 bool "PAGE OFFSET 2.5G (user:kernel = <<
231 endchoice <<
232 <<
233 config PAGE_OFFSET <<
234 hex <<
235 default 0x80000000 if PAGE_OFFSET_8000 <<
236 default 0xa0000000 if PAGE_OFFSET_A000 <<
237 choice <<
238 <<
239 prompt "C-SKY PMU type" <<
240 depends on PERF_EVENTS <<
241 depends on CPU_CK807 || CPU_CK810 || C <<
242 <<
243 config CPU_PMU_NONE <<
244 bool "None" <<
245 <<
246 config CSKY_PMU_V1 <<
247 bool "Performance Monitoring Unit Ver. <<
248 <<
249 endchoice <<
250 <<
251 choice <<
252 prompt "Power Manager Instruction (wai <<
253 default CPU_PM_NONE <<
254 <<
255 config CPU_PM_NONE <<
256 bool "None" <<
257 <<
258 config CPU_PM_WAIT <<
259 bool "wait" <<
260 <<
261 config CPU_PM_DOZE <<
262 bool "doze" <<
263 <<
264 config CPU_PM_STOP <<
265 bool "stop" <<
266 endchoice <<
267 <<
268 menuconfig HAVE_TCM <<
269 bool "Tightly-Coupled/Sram Memory" <<
270 depends on !COMPILE_TEST <<
271 help <<
272 The implementation are not only used <<
273 but also used by sram on SOC bus. It <<
274 software interface, so that old tcm <<
275 re-used directly. <<
276 <<
277 if HAVE_TCM <<
278 config ITCM_RAM_BASE <<
279 hex "ITCM ram base" <<
280 default 0xffffffff <<
281 <<
282 config ITCM_NR_PAGES <<
283 int "Page count of ITCM size: NR*4KB" <<
284 range 1 256 <<
285 default 32 <<
286 <<
287 config HAVE_DTCM <<
288 bool "DTCM Support" <<
289 <<
290 config DTCM_RAM_BASE <<
291 hex "DTCM ram base" <<
292 depends on HAVE_DTCM <<
293 default 0xffffffff <<
294 <<
295 config DTCM_NR_PAGES <<
296 int "Page count of DTCM size: NR*4KB" <<
297 depends on HAVE_DTCM <<
298 range 1 256 <<
299 default 32 <<
300 endif <<
301 26
302 config CPU_HAS_VDSP !! 27 menu "General setup"
303 bool "CPU has VDSP coprocessor" !! 28
304 depends on CPU_HAS_FPU && CPU_HAS_FPUV !! 29 config VT
305 !! 30 bool
306 config CPU_HAS_FPU !! 31 default y
307 bool "CPU has FPU coprocessor" !! 32 ---help---
308 depends on CPU_CK807 || CPU_CK810 || C !! 33 If you say Y here, you will get support for terminal devices with
309 !! 34 display and keyboard devices. These are called "virtual" because you
310 config CPU_HAS_ICACHE_INS !! 35 can run several virtual terminals (also called virtual consoles) on
311 bool "CPU has Icache invalidate instru !! 36 one physical terminal. This is rather useful, for example one
312 depends on CPU_HAS_CACHEV2 !! 37 virtual terminal can collect system messages and warnings, another
313 !! 38 one can be used for a text-mode user session, and a third could run
314 config CPU_HAS_TEE !! 39 an X session, all in parallel. Switching between virtual terminals
315 bool "CPU has Trusted Execution Enviro !! 40 is done with certain key combinations, usually Alt-<function key>.
316 depends on CPU_CK810 !! 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.
>> 55
>> 56 If unsure, say Y, or else you won't be able to do much with your new
>> 57 shiny Linux system :-)
>> 58
>> 59 config VT_CONSOLE
>> 60 bool
>> 61 default y
>> 62 ---help---
>> 63 The system console is the device which receives all kernel messages
>> 64 and warnings and which allows logins in single user mode. If you
>> 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.)
>> 77
>> 78 If unsure, say Y.
>> 79
>> 80 config HW_CONSOLE
>> 81 bool
>> 82 default y
317 83
318 config SMP 84 config SMP
319 bool "Symmetric Multi-Processing (SMP) !! 85 bool "Symmetric multi-processing support (does not work on sun4/sun4c)"
320 depends on CPU_CK860 !! 86 ---help---
321 default n !! 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>.
>> 110
>> 111 If you don't know what to do here, say N.
322 112
323 config NR_CPUS 113 config NR_CPUS
324 int "Maximum number of CPUs (2-32)" 114 int "Maximum number of CPUs (2-32)"
325 range 2 32 <<
326 depends on SMP 115 depends on SMP
327 default "4" !! 116 default "32"
328 117
329 config HIGHMEM !! 118 # Identify this as a Sparc32 build
330 bool "High Memory Support" !! 119 config SPARC32
331 depends on !CPU_CK610 !! 120 bool
332 select KMAP_LOCAL <<
333 default y 121 default y
>> 122 help
>> 123 SPARC is a family of RISC microprocessors designed and marketed by
>> 124 Sun Microsystems, incorporated. They are very widely found in Sun
>> 125 workstations and clones. This port covers the original 32-bit SPARC;
>> 126 it is old and stable and usually considered one of the "big three"
>> 127 along with the Intel and Alpha ports. The UltraLinux project
>> 128 maintains both the SPARC32 and SPARC64 ports; its web page is
>> 129 available at <http://www.ultralinux.org/>.
334 130
335 config DRAM_BASE !! 131 # Global things across all Sun machines.
336 hex "DRAM start addr (the same with me !! 132 config ISA
337 default 0x0 !! 133 bool
338 <<
339 config HOTPLUG_CPU <<
340 bool "Support for hot-pluggable CPUs" <<
341 select GENERIC_IRQ_MIGRATION <<
342 depends on SMP <<
343 help 134 help
344 Say Y here to allow turning CPUs off !! 135 ISA is found on Espresso only and is not supported currently.
345 controlled through /sys/devices/syst !! 136 Say N
346 137
347 Say N if you want to disable CPU hot !! 138 config EISA
>> 139 bool
>> 140 help
>> 141 EISA is not supported.
>> 142 Say N
348 143
349 config HAVE_EFFICIENT_UNALIGNED_STRING_OPS !! 144 config MCA
350 bool "Enable EFFICIENT_UNALIGNED_STRIN !! 145 bool
351 depends on CPU_CK807 || CPU_CK810 || C <<
352 help 146 help
353 Say Y here to enable EFFICIENT_UNALI !! 147 MCA is not supported.
354 deal with unaligned access by hardwa !! 148 Say N
>> 149
>> 150 config PCMCIA
>> 151 tristate
>> 152 ---help---
>> 153 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
>> 154 computer. These are credit-card size devices such as network cards,
>> 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>.
>> 164
>> 165 To compile this driver as modules, choose M here: the
>> 166 modules will be called pcmcia_core and ds.
>> 167
>> 168 config SBUS
>> 169 bool
>> 170 default y
>> 171
>> 172 config SBUSCHAR
>> 173 bool
>> 174 default y
>> 175
>> 176 config SERIAL_CONSOLE
>> 177 bool
>> 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.
>> 196
>> 197 If unsure, say N.
>> 198
>> 199 config SUN_AUXIO
>> 200 bool
>> 201 default y
>> 202
>> 203 config SUN_IO
>> 204 bool
>> 205 default y
>> 206
>> 207 config RWSEM_GENERIC_SPINLOCK
>> 208 bool
>> 209 default y
>> 210
>> 211 config RWSEM_XCHGADD_ALGORITHM
>> 212 bool
>> 213
>> 214 config SUN_PM
>> 215 bool
>> 216 default y
>> 217 help
>> 218 Enable power management and CPU standby features on supported
>> 219 SPARC platforms.
>> 220
>> 221 config SUN4
>> 222 bool "Support for SUN4 machines (disables SUN4[CDM] support)"
>> 223 help
>> 224 Say Y here if, and only if, your machine is a sun4. Note that
>> 225 a kernel compiled with this option will run only on sun4.
>> 226 (And the current version will probably work only on sun4/330.)
>> 227
>> 228 if !SUN4
>> 229
>> 230 config PCI
>> 231 bool "Support for PCI and PS/2 keyboard/mouse"
>> 232 help
>> 233 CONFIG_PCI is needed for all JavaStation's (including MrCoffee),
>> 234 CP-1200, JavaEngine-1, Corona, Red October, and Serengeti SGSC.
>> 235 All of these platforms are extremely obscure, so say N if unsure.
>> 236
>> 237 source "drivers/pci/Kconfig"
>> 238
>> 239 endif
>> 240
>> 241 config SUN_OPENPROMFS
>> 242 tristate "Openprom tree appears in /proc/openprom"
>> 243 help
>> 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".
>> 247
>> 248 To compile the /proc/openprom support as a module, choose M here: the
>> 249 module will be called openpromfs. If unsure, choose M.
>> 250
>> 251 source "fs/Kconfig.binfmt"
>> 252
>> 253 config SUNOS_EMUL
>> 254 bool "SunOS binary emulation"
>> 255 help
>> 256 This allows you to run most SunOS binaries. If you want to do this,
>> 257 say Y here and place appropriate files in /usr/gnemul/sunos. See
>> 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.
>> 261
>> 262 source "drivers/parport/Kconfig"
>> 263
>> 264 config PRINTER
>> 265 tristate "Parallel printer support"
>> 266 depends on PARPORT
>> 267 ---help---
>> 268 If you intend to attach a printer to the parallel port of your Linux
>> 269 box (as opposed to using a serial printer; if the connector at the
>> 270 printer has 9 or 25 holes ["female"], then it's serial), say Y.
>> 271 Also read the Printing-HOWTO, available from
>> 272 <http://www.tldp.org/docs.html#howto>.
>> 273
>> 274 It is possible to share one parallel port among several devices
>> 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.
>> 279
>> 280 If you have several parallel ports, you can specify which ports to
>> 281 use with the "lp" kernel command line option. (Try "man bootparam"
>> 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>.
>> 285
>> 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.
>> 288
>> 289 endmenu
>> 290
>> 291 source "drivers/base/Kconfig"
>> 292
>> 293 source "drivers/video/Kconfig"
>> 294
>> 295 source "drivers/mtd/Kconfig"
>> 296
>> 297 source "drivers/serial/Kconfig"
>> 298
>> 299 if !SUN4
>> 300 source "drivers/sbus/char/Kconfig"
>> 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.
>> 386
>> 387 Note that this has nothing to do with the network file systems NFS
>> 388 or Coda; you can say N here even if you intend to use NFS or Coda.
>> 389
>> 390 To compile this driver as a module, choose M here: the
>> 391 module will be called nbd.
>> 392
>> 393 If unsure, say N.
>> 394
>> 395 source "drivers/md/Kconfig"
>> 396
>> 397 config BLK_DEV_RAM
>> 398 tristate "RAM disk support"
>> 399 ---help---
>> 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
>> 434 endmenu
>> 435
>> 436 # Don't frighten a common SBus user
>> 437 if PCI
>> 438
>> 439 source "drivers/ide/Kconfig"
>> 440
>> 441 endif
>> 442
>> 443 source "drivers/isdn/Kconfig"
>> 444
>> 445 source "drivers/scsi/Kconfig"
>> 446
>> 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.
>> 493
>> 494 When not in use, each additional set of 256 PTYs occupy
>> 495 approximately 8 KB of kernel memory on 32-bit architectures.
355 496
356 endmenu 497 endmenu
357 498
358 source "arch/csky/Kconfig.platforms" !! 499 source "drivers/input/Kconfig"
>> 500
>> 501 source "fs/Kconfig"
>> 502
>> 503 source "sound/Kconfig"
>> 504
>> 505 source "drivers/usb/Kconfig"
>> 506
>> 507 menu "Watchdog"
>> 508
>> 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.
>> 515
>> 516 To compile this driver as a module, choose M here: the
>> 517 module will be called softdog.
>> 518
>> 519 endmenu
>> 520
>> 521
>> 522 menu "Kernel hacking"
>> 523
>> 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.
>> 555
>> 556 endmenu
>> 557
>> 558 source "security/Kconfig"
>> 559
>> 560 source "crypto/Kconfig"
>> 561
>> 562 source "lib/Kconfig"
359 563
360 source "kernel/Kconfig.hz" <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.