1 # SPDX-License-Identifier: GPL-2.0 !! 1 # $Id: config.in,v 1.113 2002/01/24 22:14:44 davem Exp $
2 # <<
3 # For a description of the syntax of this conf 2 # For a description of the syntax of this configuration file,
4 # see Documentation/kbuild/kconfig-language.rs !! 3 # see Documentation/kbuild/kconfig-language.txt.
5 # 4 #
6 5
7 config OPENRISC !! 6 mainmenu "Linux/SPARC Kernel Configuration"
8 def_bool y <<
9 select ARCH_32BIT_OFF_T <<
10 select ARCH_HAS_DMA_SET_UNCACHED <<
11 select ARCH_HAS_DMA_CLEAR_UNCACHED <<
12 select ARCH_HAS_SYNC_DMA_FOR_DEVICE <<
13 select COMMON_CLK <<
14 select OF <<
15 select OF_EARLY_FLATTREE <<
16 select IRQ_DOMAIN <<
17 select GPIOLIB <<
18 select HAVE_ARCH_TRACEHOOK <<
19 select SPARSE_IRQ <<
20 select GENERIC_IRQ_CHIP <<
21 select GENERIC_IRQ_PROBE <<
22 select GENERIC_IRQ_SHOW <<
23 select GENERIC_PCI_IOMAP <<
24 select GENERIC_IOREMAP <<
25 select GENERIC_CPU_DEVICES <<
26 select HAVE_PCI <<
27 select HAVE_UID16 <<
28 select HAVE_PAGE_SIZE_8KB <<
29 select GENERIC_ATOMIC64 <<
30 select GENERIC_CLOCKEVENTS_BROADCAST <<
31 select GENERIC_SMP_IDLE_THREAD <<
32 select MODULES_USE_ELF_RELA <<
33 select HAVE_DEBUG_STACKOVERFLOW <<
34 select OR1K_PIC <<
35 select CPU_NO_EFFICIENT_FFS if !OPENRI <<
36 select ARCH_USE_QUEUED_RWLOCKS <<
37 select OMPIC if SMP <<
38 select PCI_DOMAINS_GENERIC if PCI <<
39 select PCI_MSI if PCI <<
40 select ARCH_WANT_FRAME_POINTERS <<
41 select GENERIC_IRQ_MULTI_HANDLER <<
42 select MMU_GATHER_NO_RANGE if MMU <<
43 select TRACE_IRQFLAGS_SUPPORT <<
44 <<
45 config CPU_BIG_ENDIAN <<
46 def_bool y <<
47 7
48 config MMU 8 config MMU
49 def_bool y !! 9 bool
>> 10 default y
50 11
51 config GENERIC_HWEIGHT !! 12 config UID16
52 def_bool y !! 13 bool
>> 14 default y
53 15
54 config NO_IOPORT_MAP !! 16 config HIGHMEM
55 def_bool y !! 17 bool
>> 18 default y
56 19
57 # For now, use generic checksum functions !! 20 config GENERIC_ISA_DMA
58 #These can be reimplemented in assembly later !! 21 bool
59 config GENERIC_CSUM !! 22 default y
60 def_bool y <<
61 23
62 config STACKTRACE_SUPPORT !! 24 source "init/Kconfig"
63 def_bool y <<
64 25
65 config LOCKDEP_SUPPORT <<
66 def_bool y <<
67 26
68 menu "Processor type and features" !! 27 menu "General setup"
69 28
70 choice !! 29 config VT
71 prompt "Subarchitecture" !! 30 bool
72 default OR1K_1200 !! 31 default y
>> 32 ---help---
>> 33 If you say Y here, you will get support for terminal devices with
>> 34 display and keyboard devices. These are called "virtual" because you
>> 35 can run several virtual terminals (also called virtual consoles) on
>> 36 one physical terminal. This is rather useful, for example one
>> 37 virtual terminal can collect system messages and warnings, another
>> 38 one can be used for a text-mode user session, and a third could run
>> 39 an X session, all in parallel. Switching between virtual terminals
>> 40 is done with certain key combinations, usually Alt-<function key>.
>> 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.
73 55
74 config OR1K_1200 !! 56 If unsure, say Y, or else you won't be able to do much with your new
75 bool "OR1200" !! 57 shiny Linux system :-)
76 help <<
77 Generic OpenRISC 1200 architecture <<
78 58
79 endchoice !! 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.)
80 77
81 config DCACHE_WRITETHROUGH !! 78 If unsure, say Y.
82 bool "Have write through data caches" !! 79
83 default n !! 80 config HW_CONSOLE
84 help !! 81 bool
85 Select this if your implementation f !! 82 default y
86 Selecting 'N' here will allow the ke <<
87 caches at relevant times. Most OpenR <<
88 through data caches. <<
89 83
90 If unsure say N here !! 84 config SMP
>> 85 bool "Symmetric multi-processing support (does not work on sun4/sun4c)"
>> 86 ---help---
>> 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.
91 90
92 config OPENRISC_BUILTIN_DTB !! 91 If you say N here, the kernel will run on single and multiprocessor
93 string "Builtin DTB" !! 92 machines, but will use only one CPU of a multiprocessor machine. If
94 default "" !! 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>.
95 110
96 menu "Class II Instructions" !! 111 If you don't know what to do here, say N.
97 112
98 config OPENRISC_HAVE_INST_FF1 !! 113 config NR_CPUS
99 bool "Have instruction l.ff1" !! 114 int "Maximum number of CPUs (2-32)"
>> 115 depends on SMP
>> 116 default "32"
>> 117
>> 118 # Identify this as a Sparc32 build
>> 119 config SPARC32
>> 120 bool
100 default y 121 default y
101 help 122 help
102 Select this if your implementation h !! 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/>.
>> 130
>> 131 # Global things across all Sun machines.
>> 132 config ISA
>> 133 bool
>> 134 help
>> 135 ISA is found on Espresso only and is not supported currently.
>> 136 Say N
>> 137
>> 138 config EISA
>> 139 bool
>> 140 help
>> 141 EISA is not supported.
>> 142 Say N
>> 143
>> 144 config MCA
>> 145 bool
>> 146 help
>> 147 MCA is not supported.
>> 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>.
103 164
104 config OPENRISC_HAVE_INST_FL1 !! 165 To compile this driver as modules, choose M here: the
105 bool "Have instruction l.fl1" !! 166 modules will be called pcmcia_core and ds.
>> 167
>> 168 config SBUS
>> 169 bool
106 default y 170 default y
107 help <<
108 Select this if your implementation h <<
109 171
110 config OPENRISC_HAVE_INST_MUL !! 172 config SBUSCHAR
111 bool "Have instruction l.mul for hardw !! 173 bool
112 default y 174 default y
113 help <<
114 Select this if your implementation h <<
115 175
116 config OPENRISC_HAVE_INST_DIV !! 176 config SERIAL_CONSOLE
117 bool "Have instruction l.div for hardw !! 177 bool
118 default y 178 default y
119 help !! 179 ---help---
120 Select this if your implementation h !! 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
121 213
122 config OPENRISC_HAVE_INST_CMOV !! 214 config SUN_PM
123 bool "Have instruction l.cmov for cond !! 215 bool
124 default n !! 216 default y
125 help 217 help
126 This config enables gcc to generate !! 218 Enable power management and CPU standby features on supported
127 the kernel which in general will imp !! 219 SPARC platforms.
128 binary size. <<
129 220
130 Select this if your implementation h !! 221 config SUN4
131 l.cmov conistional move instruction. !! 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.)
132 227
133 Say N if you are unsure. !! 228 if !SUN4
134 229
135 config OPENRISC_HAVE_INST_ROR !! 230 config PCI
136 bool "Have instruction l.ror for rotat !! 231 bool "Support for PCI and PS/2 keyboard/mouse"
137 default n <<
138 help 232 help
139 This config enables gcc to generate !! 233 CONFIG_PCI is needed for all JavaStation's (including MrCoffee),
140 the kernel which in general will imp !! 234 CP-1200, JavaEngine-1, Corona, Red October, and Serengeti SGSC.
141 binary size. !! 235 All of these platforms are extremely obscure, so say N if unsure.
142 236
143 Select this if your implementation h !! 237 source "drivers/pci/Kconfig"
144 l.ror rotate right instruction. <<
145 238
146 Say N if you are unsure. !! 239 endif
147 240
148 config OPENRISC_HAVE_INST_RORI !! 241 config SUN_OPENPROMFS
149 bool "Have instruction l.rori for rota !! 242 tristate "Openprom tree appears in /proc/openprom"
150 default n <<
151 help 243 help
152 This config enables gcc to generate !! 244 If you say Y, the OpenPROM device tree will be available as a
153 the kernel which in general will imp !! 245 virtual file system, which you can mount to /proc/openprom by "mount
154 binary size. !! 246 -t openpromfs none /proc/openprom".
155 247
156 Select this if your implementation h !! 248 To compile the /proc/openprom support as a module, choose M here: the
157 l.rori rotate right with immediate i !! 249 module will be called openpromfs. If unsure, choose M.
158 250
159 Say N if you are unsure. !! 251 source "fs/Kconfig.binfmt"
160 252
161 config OPENRISC_HAVE_INST_SEXT !! 253 config SUNOS_EMUL
162 bool "Have instructions l.ext* for sig !! 254 bool "SunOS binary emulation"
163 default n <<
164 help 255 help
165 This config enables gcc to generate !! 256 This allows you to run most SunOS binaries. If you want to do this,
166 the kernel which in general will imp !! 257 say Y here and place appropriate files in /usr/gnemul/sunos. See
167 binary size. !! 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.
168 261
169 Select this if your implementation h !! 262 source "drivers/parport/Kconfig"
170 l.exths, l.extbs, l.exthz and l.extb <<
171 263
172 Say N if you are unsure. !! 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.
173 288
174 endmenu 289 endmenu
175 290
176 config NR_CPUS !! 291 source "drivers/base/Kconfig"
177 int "Maximum number of CPUs (2-32)" <<
178 range 2 32 <<
179 depends on SMP <<
180 default "2" <<
181 292
182 config SMP !! 293 source "drivers/video/Kconfig"
183 bool "Symmetric Multi-Processing suppo <<
184 help <<
185 This enables support for systems wit <<
186 a system with only one CPU, say N. I <<
187 than one CPU, say Y. <<
188 294
189 If you don't know what to do here, s !! 295 source "drivers/mtd/Kconfig"
190 296
191 config FPU !! 297 source "drivers/serial/Kconfig"
192 bool "FPU support" <<
193 default y <<
194 help <<
195 Say N here if you want to disable al <<
196 in the kernel and reduce binary size <<
197 298
198 If you don't know what to do here, s !! 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.
199 433
200 source "kernel/Kconfig.hz" !! 434 endmenu
201 435
202 config OPENRISC_NO_SPR_SR_DSX !! 436 # Don't frighten a common SBus user
203 bool "use SPR_SR_DSX software emulatio !! 437 if PCI
204 default y <<
205 help <<
206 SPR_SR_DSX bit is status register bi <<
207 the last exception has happened in d <<
208 438
209 OpenRISC architecture makes it optio !! 439 source "drivers/ide/Kconfig"
210 in hardware and the OR1200 does not <<
211 440
212 Say N here if you know that your Ope !! 441 endif
213 SPR_SR_DSX bit implemented. Say Y if <<
214 442
215 config OPENRISC_HAVE_SHADOW_GPRS !! 443 source "drivers/isdn/Kconfig"
216 bool "Support for shadow gpr files" if <<
217 default y if SMP <<
218 help <<
219 Say Y here if your OpenRISC processo <<
220 register files. They will in such ca <<
221 scratch reg storage on exception ent <<
222 444
223 On SMP systems, this feature is mand !! 445 source "drivers/scsi/Kconfig"
224 On a unicore system it's safe to say !! 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.
225 493
226 config CMDLINE !! 494 When not in use, each additional set of 256 PTYs occupy
227 string "Default kernel command string" !! 495 approximately 8 KB of kernel memory on 32-bit architectures.
228 default "" <<
229 help <<
230 On some architectures there is curre <<
231 to pass arguments to the kernel. For <<
232 supply some command-line options at <<
233 here. <<
234 496
235 menu "Debugging options" !! 497 endmenu
236 498
237 config JUMP_UPON_UNHANDLED_EXCEPTION !! 499 source "drivers/input/Kconfig"
238 bool "Try to die gracefully" <<
239 default y <<
240 help <<
241 Now this puts kernel into infinite l <<
242 your kernel crashes this doesn't hav <<
243 500
244 Say Y if you are unsure. !! 501 source "fs/Kconfig"
245 502
246 config OPENRISC_ESR_EXCEPTION_BUG_CHECK !! 503 source "sound/Kconfig"
247 bool "Check for possible ESR exception !! 504
248 default n !! 505 source "drivers/usb/Kconfig"
>> 506
>> 507 menu "Watchdog"
>> 508
>> 509 config SOFT_WATCHDOG
>> 510 tristate "Software watchdog"
249 help 511 help
250 This option enables some checks that !! 512 A software monitoring watchdog. This will fail to reboot your system
251 in kernel. !! 513 from some situations that the hardware watchdog will recover
>> 514 from. Equally it's a lot cheaper to install.
252 515
253 Say N if you are unsure. !! 516 To compile this driver as a module, choose M here: the
>> 517 module will be called softdog.
254 518
255 endmenu 519 endmenu
256 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
257 endmenu 556 endmenu
>> 557
>> 558 source "security/Kconfig"
>> 559
>> 560 source "crypto/Kconfig"
>> 561
>> 562 source "lib/Kconfig"
>> 563
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.