1 # SPDX-License-Identifier: GPL-2.0 !! 1 # $Id: config.in,v 1.158 2002/01/24 22:14:44 davem Exp $
2 config SUPERH !! 2 # For a description of the syntax of this configuration file,
3 def_bool y !! 3 # see the Configure script.
4 select ARCH_32BIT_OFF_T !! 4 #
5 select ARCH_HAS_CPU_CACHE_ALIASING <<
6 select ARCH_HAVE_NMI_SAFE_CMPXCHG if ( <<
7 select ARCH_HAS_BINFMT_FLAT if !MMU <<
8 select ARCH_HAS_CPU_FINALIZE_INIT <<
9 select ARCH_HAS_CURRENT_STACK_POINTER <<
10 select ARCH_HAS_GIGANTIC_PAGE <<
11 select ARCH_HAS_GCOV_PROFILE_ALL <<
12 select ARCH_HAS_PTE_SPECIAL <<
13 select ARCH_HAS_TICK_BROADCAST if GENE <<
14 select ARCH_HIBERNATION_POSSIBLE if MM <<
15 select ARCH_MIGHT_HAVE_PC_PARPORT <<
16 select ARCH_WANT_IPC_PARSE_VERSION <<
17 select ARCH_NEED_CMPXCHG_1_EMU <<
18 select CPU_NO_EFFICIENT_FFS <<
19 select DMA_DECLARE_COHERENT <<
20 select GENERIC_ATOMIC64 <<
21 select GENERIC_CMOS_UPDATE if SH_SH03 <<
22 select GENERIC_IDLE_POLL_SETUP <<
23 select GENERIC_IRQ_SHOW <<
24 select GENERIC_LIB_ASHLDI3 <<
25 select GENERIC_LIB_ASHRDI3 <<
26 select GENERIC_LIB_LSHRDI3 <<
27 select GENERIC_PCI_IOMAP if PCI <<
28 select GENERIC_SCHED_CLOCK <<
29 select GENERIC_SMP_IDLE_THREAD <<
30 select GUP_GET_PXX_LOW_HIGH if X2TLB <<
31 select HAS_IOPORT if HAS_IOPORT_MAP <<
32 select GENERIC_IOREMAP if MMU <<
33 select HAVE_ARCH_AUDITSYSCALL <<
34 select HAVE_ARCH_KGDB <<
35 select HAVE_ARCH_SECCOMP_FILTER <<
36 select HAVE_ARCH_TRACEHOOK <<
37 select HAVE_DEBUG_BUGVERBOSE <<
38 select HAVE_DEBUG_KMEMLEAK <<
39 select HAVE_DYNAMIC_FTRACE <<
40 select HAVE_GUP_FAST if MMU <<
41 select HAVE_FUNCTION_GRAPH_TRACER <<
42 select HAVE_FUNCTION_TRACER <<
43 select HAVE_FTRACE_MCOUNT_RECORD <<
44 select HAVE_HW_BREAKPOINT <<
45 select HAVE_IOREMAP_PROT if MMU && !X2 <<
46 select HAVE_KERNEL_BZIP2 <<
47 select HAVE_KERNEL_GZIP <<
48 select HAVE_KERNEL_LZMA <<
49 select HAVE_KERNEL_LZO <<
50 select HAVE_KERNEL_XZ <<
51 select HAVE_KPROBES <<
52 select HAVE_KRETPROBES <<
53 select HAVE_MIXED_BREAKPOINTS_REGS <<
54 select HAVE_MOD_ARCH_SPECIFIC if DWARF <<
55 select HAVE_NMI <<
56 select HAVE_PATA_PLATFORM <<
57 select HAVE_PERF_EVENTS <<
58 select HAVE_REGS_AND_STACK_ACCESS_API <<
59 select HAVE_UID16 <<
60 select HAVE_SOFTIRQ_ON_OWN_STACK if IR <<
61 select HAVE_STACKPROTECTOR <<
62 select HAVE_SYSCALL_TRACEPOINTS <<
63 select IRQ_FORCED_THREADING <<
64 select LOCK_MM_AND_FIND_VMA <<
65 select MODULES_USE_ELF_RELA <<
66 select NEED_SG_DMA_LENGTH <<
67 select NO_DMA if !MMU && !DMA_COHERENT <<
68 select NO_GENERIC_PCI_IOPORT_MAP if PC <<
69 select OLD_SIGACTION <<
70 select OLD_SIGSUSPEND <<
71 select PCI_DOMAINS if PCI <<
72 select PERF_EVENTS <<
73 select PERF_USE_VMALLOC <<
74 select RTC_LIB <<
75 select SPARSE_IRQ <<
76 select TRACE_IRQFLAGS_SUPPORT <<
77 help <<
78 The SuperH is a RISC processor targe <<
79 and consumer electronics; it was als <<
80 gaming console. The SuperH port has <<
81 <http://www.linux-sh.org/>. <<
82 5
83 config GENERIC_BUG !! 6 mainmenu "Linux/UltraSPARC Kernel Configuration"
84 def_bool y <<
85 depends on BUG <<
86 7
87 config GENERIC_HWEIGHT !! 8 config 64BIT
88 def_bool y 9 def_bool y
89 10
90 config GENERIC_CALIBRATE_DELAY !! 11 config MMU
91 bool 12 bool
>> 13 default y
92 14
93 config GENERIC_LOCKBREAK !! 15 source "init/Kconfig"
94 def_bool y <<
95 depends on SMP && PREEMPTION <<
96 16
97 config ARCH_SUSPEND_POSSIBLE <<
98 def_bool n <<
99 17
100 config ARCH_HIBERNATION_POSSIBLE !! 18 menu "General setup"
101 def_bool n <<
102 19
103 config SYS_SUPPORTS_APM_EMULATION !! 20 config BBC_I2C
104 bool !! 21 tristate "UltraSPARC-III bootbus i2c controller driver"
105 select ARCH_SUSPEND_POSSIBLE !! 22 depends on PCI
>> 23 help
>> 24 The BBC devices on the UltraSPARC III have two I2C controllers. The
>> 25 first I2C controller connects mainly to configuration PROMs (NVRAM,
>> 26 CPU configuration, DIMM types, etc.). The second I2C controller
>> 27 connects to environmental control devices such as fans and
>> 28 temperature sensors. The second controller also connects to the
>> 29 smartcard reader, if present. Say Y to enable support for these.
106 30
107 config SYS_SUPPORTS_SMP !! 31 config VT
108 bool !! 32 bool "Virtual terminal" if EMBEDDED
>> 33 select INPUT
>> 34 default y
>> 35 ---help---
>> 36 If you say Y here, you will get support for terminal devices with
>> 37 display and keyboard devices. These are called "virtual" because you
>> 38 can run several virtual terminals (also called virtual consoles) on
>> 39 one physical terminal. This is rather useful, for example one
>> 40 virtual terminal can collect system messages and warnings, another
>> 41 one can be used for a text-mode user session, and a third could run
>> 42 an X session, all in parallel. Switching between virtual terminals
>> 43 is done with certain key combinations, usually Alt-<function key>.
>> 44
>> 45 The setterm command ("man setterm") can be used to change the
>> 46 properties (such as colors or beeping) of a virtual terminal. The
>> 47 man page console_codes(4) ("man console_codes") contains the special
>> 48 character sequences that can be used to change those properties
>> 49 directly. The fonts used on virtual terminals can be changed with
>> 50 the setfont ("man setfont") command and the key bindings are defined
>> 51 with the loadkeys ("man loadkeys") command.
>> 52
>> 53 You need at least one virtual terminal device in order to make use
>> 54 of your keyboard and monitor. Therefore, only people configuring an
>> 55 embedded system would want to say N here in order to save some
>> 56 memory; the only way to log into such a system is then via a serial
>> 57 or network connection.
>> 58
>> 59 If unsure, say Y, or else you won't be able to do much with your new
>> 60 shiny Linux system :-)
>> 61
>> 62 config VT_CONSOLE
>> 63 bool "Support for console on virtual terminal" if EMBEDDED
>> 64 depends on VT
>> 65 default y
>> 66 ---help---
>> 67 The system console is the device which receives all kernel messages
>> 68 and warnings and which allows logins in single user mode. If you
>> 69 answer Y here, a virtual terminal (the device used to interact with
>> 70 a physical terminal) can be used as system console. This is the most
>> 71 common mode of operations, so you should say Y here unless you want
>> 72 the kernel messages be output only to a serial port (in which case
>> 73 you should say Y to "Console on serial port", below).
>> 74
>> 75 If you do say Y here, by default the currently visible virtual
>> 76 terminal (/dev/tty0) will be used as system console. You can change
>> 77 that with a kernel command line option such as "console=tty3" which
>> 78 would use the third virtual terminal as system console. (Try "man
>> 79 bootparam" or see the documentation of your boot loader (lilo or
>> 80 loadlin) about how to pass options to the kernel at boot time.)
>> 81
>> 82 If unsure, say Y.
109 83
110 config SYS_SUPPORTS_NUMA !! 84 config HW_CONSOLE
111 bool 85 bool
>> 86 default y
112 87
113 config STACKTRACE_SUPPORT !! 88 config SMP
114 def_bool y !! 89 bool "Symmetric multi-processing support"
>> 90 ---help---
>> 91 This enables support for systems with more than one CPU. If you have
>> 92 a system with only one CPU, like most personal computers, say N. If
>> 93 you have a system with more than one CPU, say Y.
115 94
116 config LOCKDEP_SUPPORT !! 95 If you say N here, the kernel will run on single and multiprocessor
117 def_bool y !! 96 machines, but will use only one CPU of a multiprocessor machine. If
>> 97 you say Y here, the kernel will run on many, but not all,
>> 98 singleprocessor machines. On a singleprocessor machine, the kernel
>> 99 will run faster if you say N here.
>> 100
>> 101 Note that if you say Y here and choose architecture "586" or
>> 102 "Pentium" under "Processor family", the kernel will not work on 486
>> 103 architectures. Similarly, multiprocessor kernels for the "PPro"
>> 104 architecture may not work on all Pentium based boards.
>> 105
>> 106 People using multiprocessor machines who say Y here should also say
>> 107 Y to "Enhanced Real Time Clock Support", below. The "Advanced Power
>> 108 Management" code will be disabled if you say Y here.
118 109
119 config ARCH_HAS_ILOG2_U32 !! 110 See also the <file:Documentation/smp.tex>,
120 def_bool n !! 111 <file:Documentation/smp.txt>, <file:Documentation/i386/IO-APIC.txt>,
>> 112 <file:Documentation/nmi_watchdog.txt> and the SMP-HOWTO available at
>> 113 <http://www.tldp.org/docs.html#howto>.
>> 114
>> 115 If you don't know what to do here, say N.
>> 116
>> 117 config PREEMPT
>> 118 bool "Preemptible Kernel"
>> 119 help
>> 120 This option reduces the latency of the kernel when reacting to
>> 121 real-time or interactive events by allowing a low priority process to
>> 122 be preempted even if it is in kernel mode executing a system call.
>> 123 This allows applications to run more reliably even when the system is
>> 124 under load.
121 125
122 config ARCH_HAS_ILOG2_U64 !! 126 Say Y here if you are building a kernel for a desktop, embedded
123 def_bool n !! 127 or real-time system. Say N if you are unsure.
124 128
125 config NO_IOPORT_MAP !! 129 config NR_CPUS
126 def_bool !PCI !! 130 int "Maximum number of CPUs (2-64)"
127 depends on !SH_SHMIN && !SH_HP6XX && ! !! 131 depends on SMP
128 !SH_DREAMCAST !! 132 default "64"
>> 133
>> 134 config CPU_FREQ
>> 135 bool "CPU Frequency scaling"
>> 136 help
>> 137 Clock scaling allows you to change the clock speed of CPUs on the
>> 138 fly. Currently there are only sparc64 drivers for UltraSPARC-III
>> 139 and UltraSPARC-IIe processors.
>> 140
>> 141 For details, take a look at linux/Documentation/cpufreq.
>> 142
>> 143 If in doubt, say N.
>> 144
>> 145 config CPU_FREQ_TABLE
>> 146 tristate "CPU frequency table helpers"
>> 147 depends on CPU_FREQ
>> 148 default y
>> 149 help
>> 150 Many CPUFreq drivers use these helpers, so only say N here if
>> 151 the CPUFreq driver of your choice doesn't need these helpers.
129 152
130 config IO_TRAPPED !! 153 If in doubt, say Y.
>> 154
>> 155 config US3_FREQ
>> 156 tristate "UltraSPARC-III CPU Frequency driver"
>> 157 depends on CPU_FREQ_TABLE
>> 158 help
>> 159 This adds the CPUFreq driver for UltraSPARC-III processors.
>> 160
>> 161 For details, take a look at linux/Documentation/cpufreq.
>> 162
>> 163 If in doubt, say N.
>> 164
>> 165 config US2E_FREQ
>> 166 tristate "UltraSPARC-IIe CPU Frequency driver"
>> 167 depends on CPU_FREQ_TABLE
>> 168 help
>> 169 This adds the CPUFreq driver for UltraSPARC-IIe processors.
>> 170
>> 171 For details, take a look at linux/Documentation/cpufreq.
>> 172
>> 173 If in doubt, say N.
>> 174
>> 175 source "drivers/cpufreq/Kconfig"
>> 176
>> 177 # Identify this as a Sparc64 build
>> 178 config SPARC64
131 bool 179 bool
>> 180 default y
>> 181 help
>> 182 SPARC is a family of RISC microprocessors designed and marketed by
>> 183 Sun Microsystems, incorporated. This port covers the newer 64-bit
>> 184 UltraSPARC. The UltraLinux project maintains both the SPARC32 and
>> 185 SPARC64 ports; its web page is available at
>> 186 <http://www.ultralinux.org/>.
>> 187
>> 188 config HOTPLUG
>> 189 bool "Support for hot-pluggable devices"
>> 190 ---help---
>> 191 Say Y here if you want to plug devices into your computer while
>> 192 the system is running, and be able to use them quickly. In many
>> 193 cases, the devices can likewise be unplugged at any time too.
>> 194
>> 195 One well known example of this is PCMCIA- or PC-cards, credit-card
>> 196 size devices such as network cards, modems or hard drives which are
>> 197 plugged into slots found on all modern laptop computers. Another
>> 198 example, used on modern desktops as well as laptops, is USB.
>> 199
>> 200 Enable HOTPLUG and KMOD, and build a modular kernel. Get agent
>> 201 software (at <http://linux-hotplug.sourceforge.net/>) and install it.
>> 202 Then your kernel will automatically call out to a user mode "policy
>> 203 agent" (/sbin/hotplug) to load modules and set up software needed
>> 204 to use devices as you hotplug them.
132 205
133 config SWAP_IO_SPACE !! 206 # Global things across all Sun machines.
>> 207 config RWSEM_GENERIC_SPINLOCK
134 bool 208 bool
135 209
136 config DMA_COHERENT !! 210 config RWSEM_XCHGADD_ALGORITHM
137 bool 211 bool
>> 212 default y
138 213
139 config DMA_NONCOHERENT !! 214 choice
140 def_bool !NO_DMA && !DMA_COHERENT !! 215 prompt "SPARC64 Huge TLB Page Size"
141 select ARCH_HAS_DMA_PREP_COHERENT !! 216 depends on HUGETLB_PAGE
142 select ARCH_HAS_SYNC_DMA_FOR_DEVICE !! 217 default HUGETLB_PAGE_SIZE_4MB
143 select DMA_DIRECT_REMAP <<
144 218
145 config PGTABLE_LEVELS !! 219 config HUGETLB_PAGE_SIZE_4MB
146 default 3 if X2TLB !! 220 bool "4MB"
147 default 2 <<
148 221
149 menu "System type" !! 222 config HUGETLB_PAGE_SIZE_512K
>> 223 bool "512K"
150 224
151 # !! 225 config HUGETLB_PAGE_SIZE_64K
152 # Processor families !! 226 bool "64K"
153 # !! 227
154 config CPU_SH2 !! 228 endchoice
155 bool <<
156 select SH_INTC <<
157 229
158 config CPU_SH2A !! 230 config GENERIC_ISA_DMA
159 bool 231 bool
160 select CPU_SH2 !! 232 default y
161 select UNCACHED_MAPPING <<
162 233
163 config CPU_J2 !! 234 config ISA
164 bool 235 bool
165 select CPU_SH2 !! 236 help
166 select OF !! 237 Find out whether you have ISA slots on your motherboard. ISA is the
167 select OF_EARLY_FLATTREE !! 238 name of a bus system, i.e. the way the CPU talks to the other stuff
>> 239 inside your box. Other bus systems are PCI, EISA, MicroChannel
>> 240 (MCA) or VESA. ISA is an older system, now being displaced by PCI;
>> 241 newer boards don't support it. If you have ISA, say Y, otherwise N.
168 242
169 config CPU_SH3 !! 243 config ISAPNP
170 bool 244 bool
171 select CPU_HAS_INTEVT !! 245 help
172 select CPU_HAS_SR_RB !! 246 Say Y here if you would like support for ISA Plug and Play devices.
173 select SH_INTC !! 247 Some information is in <file:Documentation/isapnp.txt>.
174 select SYS_SUPPORTS_SH_TMU !! 248
>> 249 To compile this driver as a module, choose M here: the
>> 250 module will be called isapnp.
175 251
176 config CPU_SH4 !! 252 If unsure, say Y.
>> 253
>> 254 config EISA
177 bool 255 bool
178 select ARCH_SUPPORTS_HUGETLBFS if MMU !! 256 ---help---
179 select CPU_HAS_INTEVT !! 257 The Extended Industry Standard Architecture (EISA) bus was
180 select CPU_HAS_SR_RB !! 258 developed as an open alternative to the IBM MicroChannel bus.
181 select CPU_HAS_FPU if !CPU_SH4AL_DSP !! 259
182 select SH_INTC !! 260 The EISA bus provided some of the features of the IBM MicroChannel
183 select SYS_SUPPORTS_SH_TMU !! 261 bus while maintaining backward compatibility with cards made for
>> 262 the older ISA bus. The EISA bus saw limited use between 1988 and
>> 263 1995 when it was made obsolete by the PCI bus.
184 264
185 config CPU_SH4A !! 265 Say Y here if you are building a kernel for an EISA-based machine.
>> 266
>> 267 Otherwise, say N.
>> 268
>> 269 config MCA
186 bool 270 bool
187 select CPU_SH4 !! 271 help
>> 272 MicroChannel Architecture is found in some IBM PS/2 machines and
>> 273 laptops. It is a bus system similar to PCI or ISA. See
>> 274 <file:Documentation/mca.txt> (and especially the web page given
>> 275 there) before attempting to build an MCA bus kernel.
>> 276
>> 277 config PCMCIA
>> 278 tristate
>> 279 ---help---
>> 280 Say Y here if you want to attach PCMCIA- or PC-cards to your Linux
>> 281 computer. These are credit-card size devices such as network cards,
>> 282 modems or hard drives often used with laptops computers. There are
>> 283 actually two varieties of these cards: the older 16 bit PCMCIA cards
>> 284 and the newer 32 bit CardBus cards. If you want to use CardBus
>> 285 cards, you need to say Y here and also to "CardBus support" below.
188 286
189 config CPU_SH4AL_DSP !! 287 To use your PC-cards, you will need supporting software from David
>> 288 Hinds' pcmcia-cs package (see the file <file:Documentation/Changes>
>> 289 for location). Please also read the PCMCIA-HOWTO, available from
>> 290 <http://www.tldp.org/docs.html#howto>.
>> 291
>> 292 To compile this driver as modules, choose M here: the
>> 293 modules will be called pcmcia_core and ds.
>> 294
>> 295 config SBUS
190 bool 296 bool
191 select CPU_SH4A !! 297 default y
192 select CPU_HAS_DSP <<
193 298
194 config CPU_SHX2 !! 299 config SBUSCHAR
195 bool 300 bool
>> 301 default y
196 302
197 config CPU_SHX3 !! 303 config SUN_AUXIO
198 bool 304 bool
199 select DMA_COHERENT !! 305 default y
200 select SYS_SUPPORTS_SMP <<
201 select SYS_SUPPORTS_NUMA <<
202 306
203 config ARCH_SHMOBILE !! 307 config SUN_IO
204 bool 308 bool
205 select ARCH_SUSPEND_POSSIBLE !! 309 default y
206 select PM <<
207 310
208 config CPU_HAS_PMU !! 311 config PCI
209 depends on CPU_SH4 || CPU_SH4A !! 312 bool "PCI support"
210 default y !! 313 help
211 bool !! 314 Find out whether you have a PCI motherboard. PCI is the name of a
>> 315 bus system, i.e. the way the CPU talks to the other stuff inside
>> 316 your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
>> 317 VESA. If you have PCI, say Y, otherwise N.
>> 318
>> 319 The PCI-HOWTO, available from
>> 320 <http://www.tldp.org/docs.html#howto>, contains valuable
>> 321 information about which PCI hardware does work under Linux and which
>> 322 doesn't.
>> 323
>> 324 config PCI_DOMAINS
>> 325 bool
>> 326 default PCI
>> 327
>> 328 config RTC
>> 329 tristate
>> 330 depends on PCI
>> 331 default y
>> 332 ---help---
>> 333 If you say Y here and create a character special file /dev/rtc with
>> 334 major number 10 and minor number 135 using mknod ("man mknod"), you
>> 335 will get access to the real time clock (or hardware clock) built
>> 336 into your computer.
212 337
213 choice !! 338 Every PC has such a clock built in. It can be used to generate
214 prompt "Processor sub-type selection" !! 339 signals from as low as 1Hz up to 8192Hz, and can also be used
>> 340 as a 24 hour alarm. It reports status information via the file
>> 341 /proc/driver/rtc and its behaviour is set by various ioctls on
>> 342 /dev/rtc.
215 343
216 # !! 344 If you run Linux on a multiprocessor machine and said Y to
217 # Processor subtypes !! 345 "Symmetric Multi Processing" above, you should say Y here to read
218 # !! 346 and set the RTC in an SMP compatible fashion.
219 347
220 # SH-2 Processor Support !! 348 If you think you have a use for such a device (such as periodic data
>> 349 sampling), then say Y here, and read <file:Documentation/rtc.txt>
>> 350 for details.
221 351
222 config CPU_SUBTYPE_SH7619 !! 352 To compile this driver as a module, choose M here: the
223 bool "Support SH7619 processor" !! 353 module will be called rtc.
224 select CPU_SH2 <<
225 select SYS_SUPPORTS_SH_CMT <<
226 <<
227 config CPU_SUBTYPE_J2 <<
228 bool "Support J2 processor" <<
229 select CPU_J2 <<
230 select SYS_SUPPORTS_SMP <<
231 select GENERIC_CLOCKEVENTS_BROADCAST i <<
232 <<
233 # SH-2A Processor Support <<
234 <<
235 config CPU_SUBTYPE_SH7201 <<
236 bool "Support SH7201 processor" <<
237 select CPU_SH2A <<
238 select CPU_HAS_FPU <<
239 select SYS_SUPPORTS_SH_MTU2 <<
240 <<
241 config CPU_SUBTYPE_SH7203 <<
242 bool "Support SH7203 processor" <<
243 select CPU_SH2A <<
244 select CPU_HAS_FPU <<
245 select SYS_SUPPORTS_SH_CMT <<
246 select SYS_SUPPORTS_SH_MTU2 <<
247 select PINCTRL <<
248 <<
249 config CPU_SUBTYPE_SH7206 <<
250 bool "Support SH7206 processor" <<
251 select CPU_SH2A <<
252 select SYS_SUPPORTS_SH_CMT <<
253 select SYS_SUPPORTS_SH_MTU2 <<
254 <<
255 config CPU_SUBTYPE_SH7263 <<
256 bool "Support SH7263 processor" <<
257 select CPU_SH2A <<
258 select CPU_HAS_FPU <<
259 select SYS_SUPPORTS_SH_CMT <<
260 select SYS_SUPPORTS_SH_MTU2 <<
261 <<
262 config CPU_SUBTYPE_SH7264 <<
263 bool "Support SH7264 processor" <<
264 select CPU_SH2A <<
265 select CPU_HAS_FPU <<
266 select SYS_SUPPORTS_SH_CMT <<
267 select SYS_SUPPORTS_SH_MTU2 <<
268 select PINCTRL <<
269 <<
270 config CPU_SUBTYPE_SH7269 <<
271 bool "Support SH7269 processor" <<
272 select CPU_SH2A <<
273 select CPU_HAS_FPU <<
274 select SYS_SUPPORTS_SH_CMT <<
275 select SYS_SUPPORTS_SH_MTU2 <<
276 select PINCTRL <<
277 <<
278 config CPU_SUBTYPE_MXG <<
279 bool "Support MX-G processor" <<
280 select CPU_SH2A <<
281 select SYS_SUPPORTS_SH_MTU2 <<
282 help <<
283 Select MX-G if running on an R8A0302 <<
284 <<
285 # SH-3 Processor Support <<
286 <<
287 config CPU_SUBTYPE_SH7705 <<
288 bool "Support SH7705 processor" <<
289 select CPU_SH3 <<
290 <<
291 config CPU_SUBTYPE_SH7706 <<
292 bool "Support SH7706 processor" <<
293 select CPU_SH3 <<
294 help <<
295 Select SH7706 if you have a 133 Mhz <<
296 <<
297 config CPU_SUBTYPE_SH7707 <<
298 bool "Support SH7707 processor" <<
299 select CPU_SH3 <<
300 help <<
301 Select SH7707 if you have a 60 Mhz <<
302 <<
303 config CPU_SUBTYPE_SH7708 <<
304 bool "Support SH7708 processor" <<
305 select CPU_SH3 <<
306 help <<
307 Select SH7708 if you have a 60 Mhz <<
308 if you have a 100 Mhz SH-3 HD6417708 <<
309 <<
310 config CPU_SUBTYPE_SH7709 <<
311 bool "Support SH7709 processor" <<
312 select CPU_SH3 <<
313 help <<
314 Select SH7709 if you have a 80 Mhz <<
315 <<
316 config CPU_SUBTYPE_SH7710 <<
317 bool "Support SH7710 processor" <<
318 select CPU_SH3 <<
319 select CPU_HAS_DSP <<
320 help <<
321 Select SH7710 if you have a SH3-DSP <<
322 <<
323 config CPU_SUBTYPE_SH7712 <<
324 bool "Support SH7712 processor" <<
325 select CPU_SH3 <<
326 select CPU_HAS_DSP <<
327 help <<
328 Select SH7712 if you have a SH3-DSP <<
329 <<
330 config CPU_SUBTYPE_SH7720 <<
331 bool "Support SH7720 processor" <<
332 select CPU_SH3 <<
333 select CPU_HAS_DSP <<
334 select SYS_SUPPORTS_SH_CMT <<
335 select USB_OHCI_SH if USB_OHCI_HCD <<
336 select PINCTRL <<
337 help <<
338 Select SH7720 if you have a SH3-DSP <<
339 <<
340 config CPU_SUBTYPE_SH7721 <<
341 bool "Support SH7721 processor" <<
342 select CPU_SH3 <<
343 select CPU_HAS_DSP <<
344 select SYS_SUPPORTS_SH_CMT <<
345 select USB_OHCI_SH if USB_OHCI_HCD <<
346 help <<
347 Select SH7721 if you have a SH3-DSP <<
348 <<
349 # SH-4 Processor Support <<
350 <<
351 config CPU_SUBTYPE_SH7750 <<
352 bool "Support SH7750 processor" <<
353 select CPU_SH4 <<
354 help <<
355 Select SH7750 if you have a 200 Mhz <<
356 <<
357 config CPU_SUBTYPE_SH7091 <<
358 bool "Support SH7091 processor" <<
359 select CPU_SH4 <<
360 help <<
361 Select SH7091 if you have an SH-4 ba <<
362 the Dreamcast, Naomi, and Naomi 2). <<
363 <<
364 config CPU_SUBTYPE_SH7750R <<
365 bool "Support SH7750R processor" <<
366 select CPU_SH4 <<
367 <<
368 config CPU_SUBTYPE_SH7750S <<
369 bool "Support SH7750S processor" <<
370 select CPU_SH4 <<
371 <<
372 config CPU_SUBTYPE_SH7751 <<
373 bool "Support SH7751 processor" <<
374 select CPU_SH4 <<
375 help <<
376 Select SH7751 if you have a 166 Mhz <<
377 or if you have a HD6417751R CPU. <<
378 <<
379 config CPU_SUBTYPE_SH7751R <<
380 bool "Support SH7751R processor" <<
381 select CPU_SH4 <<
382 <<
383 config CPU_SUBTYPE_SH7760 <<
384 bool "Support SH7760 processor" <<
385 select CPU_SH4 <<
386 <<
387 # SH-4A Processor Support <<
388 <<
389 config CPU_SUBTYPE_SH7723 <<
390 bool "Support SH7723 processor" <<
391 select CPU_SH4A <<
392 select CPU_SHX2 <<
393 select ARCH_SHMOBILE <<
394 select ARCH_SPARSEMEM_ENABLE <<
395 select SYS_SUPPORTS_SH_CMT <<
396 select PINCTRL <<
397 help <<
398 Select SH7723 if you have an SH-Mobi <<
399 <<
400 config CPU_SUBTYPE_SH7724 <<
401 bool "Support SH7724 processor" <<
402 select CPU_SH4A <<
403 select CPU_SHX2 <<
404 select ARCH_SHMOBILE <<
405 select ARCH_SPARSEMEM_ENABLE <<
406 select SYS_SUPPORTS_SH_CMT <<
407 select PINCTRL <<
408 help <<
409 Select SH7724 if you have an SH-Mobi <<
410 <<
411 config CPU_SUBTYPE_SH7734 <<
412 bool "Support SH7734 processor" <<
413 select CPU_SH4A <<
414 select CPU_SHX2 <<
415 select PINCTRL <<
416 help <<
417 Select SH7734 if you have a SH4A SH7 <<
418 <<
419 config CPU_SUBTYPE_SH7757 <<
420 bool "Support SH7757 processor" <<
421 select CPU_SH4A <<
422 select CPU_SHX2 <<
423 select PINCTRL <<
424 help <<
425 Select SH7757 if you have a SH4A SH7 <<
426 <<
427 config CPU_SUBTYPE_SH7763 <<
428 bool "Support SH7763 processor" <<
429 select CPU_SH4A <<
430 select USB_OHCI_SH if USB_OHCI_HCD <<
431 help <<
432 Select SH7763 if you have a SH4A SH7 <<
433 <<
434 config CPU_SUBTYPE_SH7770 <<
435 bool "Support SH7770 processor" <<
436 select CPU_SH4A <<
437 <<
438 config CPU_SUBTYPE_SH7780 <<
439 bool "Support SH7780 processor" <<
440 select CPU_SH4A <<
441 <<
442 config CPU_SUBTYPE_SH7785 <<
443 bool "Support SH7785 processor" <<
444 select CPU_SH4A <<
445 select CPU_SHX2 <<
446 select ARCH_SPARSEMEM_ENABLE <<
447 select SYS_SUPPORTS_NUMA <<
448 select PINCTRL <<
449 <<
450 config CPU_SUBTYPE_SH7786 <<
451 bool "Support SH7786 processor" <<
452 select CPU_SH4A <<
453 select CPU_SHX3 <<
454 select CPU_HAS_PTEAEX <<
455 select GENERIC_CLOCKEVENTS_BROADCAST i <<
456 select USB_OHCI_SH if USB_OHCI_HCD <<
457 select USB_EHCI_SH if USB_EHCI_HCD <<
458 select PINCTRL <<
459 <<
460 config CPU_SUBTYPE_SHX3 <<
461 bool "Support SH-X3 processor" <<
462 select CPU_SH4A <<
463 select CPU_SHX3 <<
464 select GENERIC_CLOCKEVENTS_BROADCAST i <<
465 select GPIOLIB <<
466 select PINCTRL <<
467 <<
468 # SH4AL-DSP Processor Support <<
469 <<
470 config CPU_SUBTYPE_SH7343 <<
471 bool "Support SH7343 processor" <<
472 select CPU_SH4AL_DSP <<
473 select ARCH_SHMOBILE <<
474 select SYS_SUPPORTS_SH_CMT <<
475 <<
476 config CPU_SUBTYPE_SH7722 <<
477 bool "Support SH7722 processor" <<
478 select CPU_SH4AL_DSP <<
479 select CPU_SHX2 <<
480 select ARCH_SHMOBILE <<
481 select ARCH_SPARSEMEM_ENABLE <<
482 select SYS_SUPPORTS_NUMA <<
483 select SYS_SUPPORTS_SH_CMT <<
484 select PINCTRL <<
485 <<
486 config CPU_SUBTYPE_SH7366 <<
487 bool "Support SH7366 processor" <<
488 select CPU_SH4AL_DSP <<
489 select CPU_SHX2 <<
490 select ARCH_SHMOBILE <<
491 select ARCH_SPARSEMEM_ENABLE <<
492 select SYS_SUPPORTS_NUMA <<
493 select SYS_SUPPORTS_SH_CMT <<
494 354
495 endchoice !! 355 source "drivers/pci/Kconfig"
496 356
497 source "arch/sh/mm/Kconfig" !! 357 config SUN_OPENPROMFS
498 !! 358 tristate "Openprom tree appears in /proc/openprom"
499 source "arch/sh/Kconfig.cpu" !! 359 help
500 !! 360 If you say Y, the OpenPROM device tree will be available as a
501 source "arch/sh/boards/Kconfig" !! 361 virtual file system, which you can mount to /proc/openprom by "mount
502 !! 362 -t openpromfs none /proc/openprom".
503 menu "Timer and clock configuration" <<
504 <<
505 config SH_PCLK_FREQ <<
506 int "Peripheral clock frequency (in Hz <<
507 depends on SH_CLK_CPG_LEGACY <<
508 default "31250000" if CPU_SUBTYPE_SH76 <<
509 default "33333333" if CPU_SUBTYPE_SH77 <<
510 CPU_SUBTYPE_SH77 <<
511 CPU_SUBTYPE_SH77 <<
512 CPU_SUBTYPE_SH72 <<
513 CPU_SUBTYPE_SH72 <<
514 CPU_SUBTYPE_SH72 <<
515 CPU_SUBTYPE_MXG <<
516 default "60000000" if CPU_SUBTYPE_SH77 <<
517 default "50000000" <<
518 help <<
519 This option is used to specify the p <<
520 This is necessary for determining th <<
521 platforms lacking an RTC. <<
522 363
523 config SH_CLK_CPG !! 364 To compile the /proc/openprom support as a module, choose M here: the
524 def_bool y !! 365 module will be called openpromfs. If unsure, choose M.
525 366
526 config SH_CLK_CPG_LEGACY !! 367 config SPARC32_COMPAT
527 depends on SH_CLK_CPG !! 368 bool "Kernel support for Linux/Sparc 32bit binary compatibility"
528 def_bool y if !CPU_SUBTYPE_SH7785 && ! !! 369 help
529 !CPU_SHX3 && !CPU_SUBTYP !! 370 This allows you to run 32-bit binaries on your Ultra.
530 !CPU_SUBTYPE_SH7734 && ! !! 371 Everybody wants this; say Y.
531 !CPU_SUBTYPE_SH7269 <<
532 372
533 endmenu !! 373 config COMPAT
>> 374 bool
>> 375 depends on SPARC32_COMPAT
>> 376 default y
534 377
535 menu "CPU Frequency scaling" !! 378 config UID16
536 source "drivers/cpufreq/Kconfig" !! 379 bool
537 endmenu !! 380 depends on SPARC32_COMPAT
>> 381 default y
538 382
539 source "arch/sh/drivers/Kconfig" !! 383 config BINFMT_ELF32
>> 384 tristate "Kernel support for 32-bit ELF binaries"
>> 385 depends on SPARC32_COMPAT
>> 386 help
>> 387 This allows you to run 32-bit Linux/ELF binaries on your Ultra.
>> 388 Everybody wants this; say Y.
>> 389
>> 390 config BINFMT_AOUT32
>> 391 bool "Kernel support for 32-bit (ie. SunOS) a.out binaries"
>> 392 depends on SPARC32_COMPAT
>> 393 help
>> 394 This allows you to run 32-bit a.out format binaries on your Ultra.
>> 395 If you want to run SunOS binaries (see SunOS binary emulation below)
>> 396 or other a.out binaries, say Y. If unsure, say N.
>> 397
>> 398 source "fs/Kconfig.binfmt"
>> 399
>> 400 config SUNOS_EMUL
>> 401 bool "SunOS binary emulation"
>> 402 help
>> 403 This allows you to run most SunOS binaries. If you want to do this,
>> 404 say Y here and place appropriate files in /usr/gnemul/sunos. See
>> 405 <http://www.ultralinux.org/faq.html> for more information. If you
>> 406 want to run SunOS binaries on an Ultra you must also say Y to
>> 407 "Kernel support for 32-bit a.out binaries" above.
>> 408
>> 409 config SOLARIS_EMUL
>> 410 tristate "Solaris binary emulation (EXPERIMENTAL)"
>> 411 depends on EXPERIMENTAL
>> 412 help
>> 413 This is experimental code which will enable you to run (many)
>> 414 Solaris binaries on your SPARC Linux machine.
>> 415
>> 416 To compile this code as a module, choose M here: the
>> 417 module will be called solaris.
>> 418
>> 419 source "drivers/parport/Kconfig"
>> 420
>> 421 config PRINTER
>> 422 tristate "Parallel printer support"
>> 423 depends on PARPORT
>> 424 ---help---
>> 425 If you intend to attach a printer to the parallel port of your Linux
>> 426 box (as opposed to using a serial printer; if the connector at the
>> 427 printer has 9 or 25 holes ["female"], then it's serial), say Y.
>> 428 Also read the Printing-HOWTO, available from
>> 429 <http://www.tldp.org/docs.html#howto>.
>> 430
>> 431 It is possible to share one parallel port among several devices
>> 432 (e.g. printer and ZIP drive) and it is safe to compile the
>> 433 corresponding drivers into the kernel.
>> 434 To compile this driver as a module, choose M here and read
>> 435 <file:Documentation/parport.txt>. The module will be called lp.
>> 436
>> 437 If you have several parallel ports, you can specify which ports to
>> 438 use with the "lp" kernel command line option. (Try "man bootparam"
>> 439 or see the documentation of your boot loader (lilo or loadlin) about
>> 440 how to pass options to the kernel at boot time.) The syntax of the
>> 441 "lp" command line option can be found in <file:drivers/char/lp.c>.
>> 442
>> 443 If you have more than 8 printers, you need to increase the LP_NO
>> 444 macro in lp.c and the PARPORT_MAX macro in parport.h.
>> 445
>> 446 config ENVCTRL
>> 447 tristate "SUNW, envctrl support"
>> 448 depends on PCI
>> 449 help
>> 450 Kernel support for temperature and fan monitoring on Sun SME
>> 451 machines.
>> 452
>> 453 To compile this driver as a module, choose M here: the
>> 454 module will be called envctrl.
>> 455
>> 456 config DISPLAY7SEG
>> 457 tristate "7-Segment Display support"
>> 458 depends on PCI
>> 459 ---help---
>> 460 This is the driver for the 7-segment display and LED present on
>> 461 Sun Microsystems CompactPCI models CP1400 and CP1500.
>> 462
>> 463 To compile this driver as a module, choose M here: the
>> 464 module will be called display7seg.
>> 465
>> 466 If you do not have a CompactPCI model CP1400 or CP1500, or
>> 467 another UltraSPARC-IIi-cEngine boardset with a 7-segment display,
>> 468 you should say N to this option.
>> 469
>> 470 config WATCHDOG_CP1XXX
>> 471 tristate "CP1XXX Hardware Watchdog support"
>> 472 depends on PCI
>> 473 ---help---
>> 474 This is the driver for the hardware watchdog timers present on
>> 475 Sun Microsystems CompactPCI models CP1400 and CP1500.
>> 476
>> 477 To compile this driver as a module, choose M here: the
>> 478 module will be called cpwatchdog.
>> 479
>> 480 If you do not have a CompactPCI model CP1400 or CP1500, or
>> 481 another UltraSPARC-IIi-cEngine boardset with hardware watchdog,
>> 482 you should say N to this option.
>> 483
>> 484 config WATCHDOG_RIO
>> 485 tristate "RIO Hardware Watchdog support"
>> 486 depends on PCI
>> 487 help
>> 488 Say Y here to support the hardware watchdog capability on Sun RIO
>> 489 machines. The watchdog timeout period is normally one minute but
>> 490 can be changed with a boot-time parameter.
540 491
541 endmenu 492 endmenu
542 493
543 menu "Kernel features" !! 494 source "drivers/base/Kconfig"
544 495
545 source "kernel/Kconfig.hz" !! 496 source "drivers/video/Kconfig"
546 497
547 config ARCH_SUPPORTS_KEXEC !! 498 source "drivers/serial/Kconfig"
548 def_bool MMU <<
549 499
550 config ARCH_SUPPORTS_CRASH_DUMP !! 500 source "drivers/sbus/char/Kconfig"
551 def_bool BROKEN_ON_SMP <<
552 501
553 config ARCH_SUPPORTS_KEXEC_JUMP !! 502 source "drivers/mtd/Kconfig"
554 def_bool y !! 503
>> 504
>> 505 menu "Block devices"
>> 506
>> 507 config BLK_DEV_FD
>> 508 bool "Normal floppy disk support"
>> 509 ---help---
>> 510 If you want to use the floppy disk drive(s) of your PC under Linux,
>> 511 say Y. Information about this driver, especially important for IBM
>> 512 Thinkpad users, is contained in <file:Documentation/floppy.txt>.
>> 513 That file also contains the location of the Floppy driver FAQ as
>> 514 well as location of the fdutils package used to configure additional
>> 515 parameters of the driver at run time.
>> 516
>> 517 To compile this driver as a module, choose M here: the
>> 518 module will be called floppy.
>> 519
>> 520 config BLK_DEV_LOOP
>> 521 tristate "Loopback device support"
>> 522 ---help---
>> 523 Saying Y here will allow you to use a regular file as a block
>> 524 device; you can then create a file system on that block device and
>> 525 mount it just as you would mount other block devices such as hard
>> 526 drive partitions, CD-ROM drives or floppy drives. The loop devices
>> 527 are block special device files with major number 7 and typically
>> 528 called /dev/loop0, /dev/loop1 etc.
>> 529
>> 530 This is useful if you want to check an ISO 9660 file system before
>> 531 burning the CD, or if you want to use floppy images without first
>> 532 writing them to floppy. Furthermore, some Linux distributions avoid
>> 533 the need for a dedicated Linux partition by keeping their complete
>> 534 root file system inside a DOS FAT file using this loop device
>> 535 driver.
>> 536
>> 537 The loop device driver can also be used to "hide" a file system in a
>> 538 disk partition, floppy, or regular file, either using encryption
>> 539 (scrambling the data) or steganography (hiding the data in the low
>> 540 bits of, say, a sound file). This is also safe if the file resides
>> 541 on a remote file server. If you want to do this, you will first have
>> 542 to acquire and install a kernel patch from
>> 543 <ftp://ftp.kerneli.org/pub/kerneli/>, and then you need to
>> 544 say Y to this option.
>> 545
>> 546 Note that alternative ways to use encrypted file systems are
>> 547 provided by the cfs package, which can be gotten from
>> 548 <ftp://ftp.kerneli.org/pub/kerneli/net-source/>, and the newer tcfs
>> 549 package, available at <http://tcfs.dia.unisa.it/>. You do not need
>> 550 to say Y here if you want to use one of these. However, using cfs
>> 551 requires saying Y to "NFS file system support" below while using
>> 552 tcfs requires applying a kernel patch. An alternative steganography
>> 553 solution is provided by StegFS, also available from
>> 554 <ftp://ftp.kerneli.org/pub/kerneli/net-source/>.
>> 555
>> 556 To use the loop device, you need the losetup utility and a recent
>> 557 version of the mount program, both contained in the util-linux
>> 558 package. The location and current version number of util-linux is
>> 559 contained in the file <file:Documentation/Changes>.
>> 560
>> 561 Note that this loop device has nothing to do with the loopback
>> 562 device used for network connections from the machine to itself.
>> 563
>> 564 To compile this driver as a module, choose M here: the
>> 565 module will be called loop.
>> 566
>> 567 Most users will answer N here.
>> 568
>> 569 config BLK_DEV_NBD
>> 570 tristate "Network block device support"
>> 571 depends on NET
>> 572 ---help---
>> 573 Saying Y here will allow your computer to be a client for network
>> 574 block devices, i.e. it will be able to use block devices exported by
>> 575 servers (mount file systems on them etc.). Communication between
>> 576 client and server works over TCP/IP networking, but to the client
>> 577 program this is hidden: it looks like a regular local file access to
>> 578 a block device special file such as /dev/nd0.
>> 579
>> 580 Network block devices also allows you to run a block-device in
>> 581 userland (making server and client physically the same computer,
>> 582 communicating using the loopback network device).
>> 583
>> 584 Read <file:Documentation/nbd.txt> for more information, especially
>> 585 about where to find the server code, which runs in user space and
>> 586 does not need special kernel support.
>> 587
>> 588 Note that this has nothing to do with the network file systems NFS
>> 589 or Coda; you can say N here even if you intend to use NFS or Coda.
>> 590
>> 591 To compile this driver as a module, choose M here: the
>> 592 module will be called nbd.
>> 593
>> 594 If unsure, say N.
>> 595
>> 596 source "drivers/md/Kconfig"
>> 597
>> 598 config BLK_DEV_RAM
>> 599 tristate "RAM disk support"
>> 600 ---help---
>> 601 Saying Y here will allow you to use a portion of your RAM memory as
>> 602 a block device, so that you can make file systems on it, read and
>> 603 write to it and do all the other things that you can do with normal
>> 604 block devices (such as hard drives). It is usually used to load and
>> 605 store a copy of a minimal root file system off of a floppy into RAM
>> 606 during the initial install of Linux.
>> 607
>> 608 Note that the kernel command line option "ramdisk=XX" is now
>> 609 obsolete. For details, read <file:Documentation/ramdisk.txt>.
>> 610
>> 611 To compile this driver as a module, choose M here: the
>> 612 module will be called rd.
>> 613
>> 614 Most normal users won't need the RAM disk functionality, and can
>> 615 thus say N here.
>> 616
>> 617 config BLK_DEV_RAM_SIZE
>> 618 int "Default RAM disk size"
>> 619 depends on BLK_DEV_RAM
>> 620 default "4096"
>> 621 help
>> 622 The default value is 4096. Only change this if you know what are
>> 623 you doing. If you are using IBM S/390, then set this to 8192.
>> 624
>> 625 config BLK_DEV_INITRD
>> 626 bool "Initial RAM disk (initrd) support"
>> 627 depends on BLK_DEV_RAM=y
>> 628 help
>> 629 The initial RAM disk is a RAM disk that is loaded by the boot loader
>> 630 (loadlin or lilo) and that is mounted as root before the normal boot
>> 631 procedure. It is typically used to load modules needed to mount the
>> 632 "real" root file system, etc. See <file:Documentation/initrd.txt>
>> 633 for details.
555 634
556 config PHYSICAL_START !! 635 endmenu
557 hex "Physical address where the kernel <<
558 default MEMORY_START <<
559 help <<
560 This gives the physical address wher <<
561 and is ordinarily the same as MEMORY <<
562 <<
563 Different values are primarily used <<
564 where the fail safe kernel needs to <<
565 than the panic-ed kernel. <<
566 636
567 config SMP <<
568 bool "Symmetric multi-processing suppo <<
569 depends on SYS_SUPPORTS_SMP <<
570 help <<
571 This enables support for systems wit <<
572 a system with only one CPU, say N. I <<
573 than one CPU, say Y. <<
574 637
575 If you say N here, the kernel will r !! 638 source "drivers/ide/Kconfig"
576 machines, but will use only one CPU <<
577 you say Y here, the kernel will run <<
578 uniprocessor machines. On a uniproce <<
579 will run faster if you say N here. <<
580 639
581 People using multiprocessor machines !! 640 source "drivers/scsi/Kconfig"
582 Y to "Enhanced Real Time Clock Suppo <<
583 641
584 See also <file:Documentation/admin-g !! 642 source "drivers/fc4/Kconfig"
585 available at <https://www.tldp.org/d <<
586 643
587 If you don't know what to do here, s !! 644 if PCI
>> 645 source "drivers/message/fusion/Kconfig"
>> 646 endif
588 647
589 config NR_CPUS !! 648 source "drivers/ieee1394/Kconfig"
590 int "Maximum number of CPUs (2-32)" <<
591 range 2 32 <<
592 depends on SMP <<
593 default "4" if CPU_SUBTYPE_SHX3 <<
594 default "2" <<
595 help <<
596 This allows you to specify the maxim <<
597 kernel will support. The maximum su <<
598 minimum value which makes sense is 2 <<
599 649
600 This is purely to save memory - each !! 650 source "net/Kconfig"
601 approximately eight kilobytes to the <<
602 651
603 config HOTPLUG_CPU !! 652 source "drivers/isdn/Kconfig"
604 bool "Support for hot-pluggable CPUs ( <<
605 depends on SMP <<
606 help <<
607 Say Y here to experiment with turnin <<
608 can be controlled through /sys/devic <<
609 653
610 config GUSA !! 654 source "drivers/telephony/Kconfig"
611 def_bool y <<
612 depends on !SMP <<
613 help <<
614 This enables support for gUSA (gener <<
615 This is the default implementation f <<
616 CPUs, and is used by the libc, among <<
617 655
618 For additional information, design i !! 656 # This one must be before the filesystem configs. -DaveM
619 in <http://lc.linux.or.jp/lc2002/pap <<
620 657
621 This should only be disabled for spe !! 658 menu "Unix 98 PTY support"
622 atomicity implementations exist. <<
623 659
624 config GUSA_RB !! 660 config UNIX98_PTYS
625 bool "Implement atomic operations by r !! 661 bool "Unix98 PTY support"
626 depends on GUSA && CPU_SH3 || (CPU_SH4 !! 662 ---help---
627 help !! 663 A pseudo terminal (PTY) is a software device consisting of two
628 Enabling this option will allow the !! 664 halves: a master and a slave. The slave device behaves identical to
629 atomic operations using a software i !! 665 a physical terminal; the master device is used by a process to
630 store-conditional (LLSC). On machine !! 666 read data from and write data to the slave, thereby emulating a
631 LLSC, this should be more efficient !! 667 terminal. Typical programs for the master side are telnet servers
632 disabling interrupts around the atom !! 668 and xterms.
633 669
634 config HW_PERF_EVENTS !! 670 Linux has traditionally used the BSD-like names /dev/ptyxx for
635 bool "Enable hardware performance coun !! 671 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
636 depends on PERF_EVENTS && CPU_HAS_PMU !! 672 has a number of problems. The GNU C library glibc 2.1 and later,
637 default y !! 673 however, supports the Unix98 naming standard: in order to acquire a
>> 674 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
>> 675 terminal is then made available to the process and the pseudo
>> 676 terminal slave can be accessed as /dev/pts/<number>. What was
>> 677 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
>> 678
>> 679 The entries in /dev/pts/ are created on the fly by a virtual
>> 680 file system; therefore, if you say Y here you should say Y to
>> 681 "/dev/pts file system for Unix98 PTYs" as well.
>> 682
>> 683 If you want to say Y here, you need to have the C library glibc 2.1
>> 684 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
>> 685 Read the instructions in <file:Documentation/Changes> pertaining to
>> 686 pseudo terminals. It's safe to say N.
>> 687
>> 688 config UNIX98_PTY_COUNT
>> 689 int "Maximum number of Unix98 PTYs in use (0-2048)"
>> 690 depends on UNIX98_PTYS
>> 691 default "256"
638 help 692 help
639 Enable hardware performance counter !! 693 The maximum number of Unix98 PTYs that can be used at any one time.
640 disabled, perf events will use softw !! 694 The default is 256, and should be enough for desktop systems. Server
>> 695 machines which support incoming telnet/rlogin/ssh connections and/or
>> 696 serve several X terminals may want to increase this: every incoming
>> 697 connection and every xterm uses up one PTY.
641 698
642 source "drivers/sh/Kconfig" !! 699 When not in use, each additional set of 256 PTYs occupy
>> 700 approximately 8 KB of kernel memory on 32-bit architectures.
643 701
644 endmenu 702 endmenu
645 703
646 menu "Boot options" <<
647 704
648 config USE_BUILTIN_DTB !! 705 menu "XFree86 DRI support"
649 bool "Use builtin DTB" !! 706
650 default n !! 707 config DRM
651 depends on SH_DEVICE_TREE !! 708 bool "Direct Rendering Manager (XFree86 DRI support)"
652 help <<
653 Link a device tree blob for particul <<
654 suppressing use of the DTB pointer p <<
655 This option should only be used with <<
656 not capable of providing a DTB to th <<
657 hardware without stable device tree <<
658 <<
659 config BUILTIN_DTB_SOURCE <<
660 string "Source file for builtin DTB" <<
661 default "" <<
662 depends on USE_BUILTIN_DTB <<
663 help <<
664 Base name (without suffix, relative <<
665 a DTS file that will be used to prod <<
666 kernel. <<
667 <<
668 config ZERO_PAGE_OFFSET <<
669 hex <<
670 default "0x00010000" if PAGE_SIZE_64KB <<
671 SH_7751_SOLUTI <<
672 default "0x00004000" if PAGE_SIZE_16KB <<
673 default "0x00002000" if PAGE_SIZE_8KB <<
674 default "0x00001000" <<
675 help <<
676 This sets the default offset of zero <<
677 <<
678 config BOOT_LINK_OFFSET <<
679 hex <<
680 default "0x00210000" if SH_SHMIN <<
681 default "0x00810000" if SH_7780_SOLUTI <<
682 default "0x009e0000" if SH_TITAN <<
683 default "0x01800000" if SH_SDK7780 <<
684 default "0x02000000" if SH_EDOSK7760 <<
685 default "0x00800000" <<
686 help 709 help
687 This option allows you to set the li !! 710 Kernel-level support for the Direct Rendering Infrastructure (DRI)
688 This can be useful if you are on a b !! 711 introduced in XFree86 4.0. If you say Y here, you need to select
689 memory. !! 712 the module that's right for your graphics card from the list below.
>> 713 These modules provide support for synchronization, security, and
>> 714 DMA transfers. Please see <http://dri.sourceforge.net/> for more
>> 715 details. You should also select and configure AGP
>> 716 (/dev/agpgart) support.
>> 717
>> 718 config DRM_FFB
>> 719 tristate "Creator/Creator3D"
>> 720 depends on DRM
>> 721 help
>> 722 Choose this option if you have one of Sun's Creator3D-based graphics
>> 723 and frame buffer cards. Product page at
>> 724 <http://www.sun.com/desktop/products/Graphics/creator3d.html>.
>> 725
>> 726 config DRM_TDFX
>> 727 tristate "3dfx Banshee/Voodoo3+"
>> 728 depends on DRM
>> 729 help
>> 730 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
>> 731 graphics card. If M is selected, the module will be called tdfx.
>> 732
>> 733 config DRM_R128
>> 734 tristate "ATI Rage 128"
>> 735 depends on DRM
>> 736 help
>> 737 Choose this option if you have an ATI Rage 128 graphics card. If M
>> 738 is selected, the module will be called r128. AGP support for
>> 739 this card is strongly suggested (unless you have a PCI version).
690 740
691 config ENTRY_OFFSET !! 741 endmenu
692 hex <<
693 default "0x00001000" if PAGE_SIZE_4KB <<
694 default "0x00002000" if PAGE_SIZE_8KB <<
695 default "0x00004000" if PAGE_SIZE_16KB <<
696 default "0x00010000" if PAGE_SIZE_64KB <<
697 default "0x00000000" <<
698 <<
699 config ROMIMAGE_MMCIF <<
700 bool "Include MMCIF loader in romImage <<
701 depends on CPU_SUBTYPE_SH7724 <<
702 help <<
703 Say Y here to include experimental M <<
704 romImage. With this enabled it is po <<
705 kernel image to an MMC card and boot <<
706 the reset vector. At reset the proce <<
707 first part of the romImage which in <<
708 image to RAM using the MMCIF hardwar <<
709 742
710 choice !! 743 source "drivers/input/Kconfig"
711 prompt "Kernel command line" <<
712 default CMDLINE_OVERWRITE <<
713 help <<
714 Setting this option allows the kerne <<
715 to be set. <<
716 744
717 config CMDLINE_OVERWRITE !! 745 source "drivers/i2c/Kconfig"
718 bool "Overwrite bootloader kernel argu !! 746
719 help !! 747 source "fs/Kconfig"
720 Given string will overwrite any argu !! 748
721 a bootloader. !! 749 source "drivers/media/Kconfig"
>> 750
>> 751 source "sound/Kconfig"
>> 752
>> 753 source "drivers/usb/Kconfig"
722 754
723 config CMDLINE_EXTEND !! 755
724 bool "Extend bootloader kernel argumen !! 756 menu "Watchdog"
>> 757
>> 758 config SOFT_WATCHDOG
>> 759 tristate "Software watchdog"
725 help 760 help
726 Given string will be concatenated wi !! 761 A software monitoring watchdog. This will fail to reboot your system
727 by a bootloader. !! 762 from some situations that the hardware watchdog will recover
>> 763 from. Equally it's a lot cheaper to install.
>> 764
>> 765 To compile this driver as a module, choose M here: the
>> 766 module will be called softdog.
>> 767
>> 768 endmenu
728 769
729 config CMDLINE_FROM_BOOTLOADER !! 770 source "arch/sparc64/oprofile/Kconfig"
730 bool "Use bootloader kernel arguments" !! 771
>> 772 menu "Kernel hacking"
>> 773
>> 774 config DEBUG_KERNEL
>> 775 bool "Kernel debugging"
731 help 776 help
732 Uses the command-line options passed !! 777 Say Y here if you are developing drivers or trying to debug and
>> 778 identify kernel problems.
733 779
734 endchoice !! 780 config DEBUG_SLAB
>> 781 bool "Debug memory allocations"
>> 782 depends on DEBUG_KERNEL
>> 783 help
>> 784 Say Y here to have the kernel do limited verification on memory
>> 785 allocation as well as poisoning memory on free to catch use of freed
>> 786 memory.
735 787
736 config CMDLINE !! 788 config MAGIC_SYSRQ
737 string "Kernel command line arguments !! 789 bool "Magic SysRq key"
738 depends on CMDLINE_OVERWRITE || CMDLIN !! 790 depends on DEBUG_KERNEL
739 default "console=ttySC1,115200" !! 791 help
>> 792 If you say Y here, you will have some control over the system even
>> 793 if the system crashes for example during kernel debugging (e.g., you
>> 794 will be able to flush the buffer cache to disk, reboot the system
>> 795 immediately or dump some status information). This is accomplished
>> 796 by pressing various keys while holding SysRq (Alt+PrintScreen). It
>> 797 also works on a serial console (on PC hardware at least), if you
>> 798 send a BREAK and then within 5 seconds a command keypress. The
>> 799 keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
>> 800 unless you really know what this hack does.
>> 801
>> 802 config DEBUG_SPINLOCK
>> 803 bool "Spinlock debugging"
>> 804 depends on DEBUG_KERNEL
>> 805 help
>> 806 Say Y here and build SMP to catch missing spinlock initialization
>> 807 and certain other kinds of spinlock errors commonly made. This is
>> 808 best used in conjunction with the NMI watchdog so that spinlock
>> 809 deadlocks are also debuggable.
>> 810
>> 811 # We have a custom atomic_dec_and_lock() implementation but it's not
>> 812 # compatible with spinlock debugging so we need to fall back on
>> 813 # the generic version in that case.
>> 814 config HAVE_DEC_LOCK
>> 815 bool
>> 816 depends on SMP && !DEBUG_SPINLOCK
>> 817 default y
740 818
741 endmenu !! 819 config DEBUG_SPINLOCK_SLEEP
>> 820 bool "Sleep-inside-spinlock checking"
>> 821 help
>> 822 If you say Y here, various routines which may sleep will become very
>> 823 noisy if they are called with a spinlock held.
742 824
743 menu "Bus options" !! 825 config DEBUG_BUGVERBOSE
>> 826 bool "Verbose BUG() reporting (adds 70K)"
>> 827 depends on DEBUG_KERNEL
>> 828 help
>> 829 Say Y here to make BUG() panics output the file name and line number
>> 830 of the BUG call as well as the EIP and oops trace. This aids
>> 831 debugging but costs about 70-100K of memory.
>> 832
>> 833 config DEBUG_DCFLUSH
>> 834 bool "D-cache flush debugging"
>> 835 depends on DEBUG_KERNEL
>> 836
>> 837 config DEBUG_INFO
>> 838 bool "Compile the kernel with debug info"
>> 839 depends on DEBUG_KERNEL
>> 840 help
>> 841 If you say Y here the resulting kernel image will include
>> 842 debugging info resulting in a larger kernel image.
>> 843 Say Y here only if you plan to use gdb to debug the kernel.
>> 844 If you don't debug the kernel, you can say N.
>> 845
>> 846 config STACK_DEBUG
>> 847 bool "Stack Overflow Detection Support"
744 848
745 config MAPLE !! 849 config MCOUNT
746 bool "Maple Bus support" !! 850 bool
747 depends on SH_DREAMCAST !! 851 depends on STACK_DEBUG
748 help !! 852 default y
749 The Maple Bus is SEGA's serial commun <<
750 on the Dreamcast. Without this bus su <<
751 get your Dreamcast keyboard etc to wo <<
752 probably want to say 'Y' here, unless <<
753 Dreamcast with a serial line terminal <<
754 connection. <<
755 853
756 endmenu 854 endmenu
757 855
758 menu "Power management options (EXPERIMENTAL)" !! 856 source "security/Kconfig"
759 857
760 source "kernel/power/Kconfig" !! 858 source "crypto/Kconfig"
761 859
762 source "drivers/cpuidle/Kconfig" !! 860 source "lib/Kconfig"
763 861
764 endmenu <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.