1 # SPDX-License-Identifier: GPL-2.0-only !! 1 # $Id: config.in,v 1.158 2002/01/24 22:14:44 davem Exp $
2 config MICROBLAZE !! 2 # For a description of the syntax of this configuration file,
>> 3 # see the Configure script.
>> 4 #
>> 5
>> 6 mainmenu "Linux/UltraSPARC Kernel Configuration"
>> 7
>> 8 config 64BIT
3 def_bool y 9 def_bool y
4 select ARCH_32BIT_OFF_T <<
5 select ARCH_NO_SWAP <<
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_MIGHT_HAVE_PC_PARPORT <<
11 select ARCH_WANT_IPC_PARSE_VERSION <<
12 select BUILDTIME_TABLE_SORT <<
13 select TIMER_OF <<
14 select CLONE_BACKWARDS3 <<
15 select COMMON_CLK <<
16 select DMA_DIRECT_REMAP <<
17 select GENERIC_ATOMIC64 <<
18 select GENERIC_CPU_DEVICES <<
19 select GENERIC_IDLE_POLL_SETUP <<
20 select GENERIC_IRQ_PROBE <<
21 select GENERIC_IRQ_SHOW <<
22 select GENERIC_PCI_IOMAP <<
23 select GENERIC_SCHED_CLOCK <<
24 select HAS_IOPORT if PCI <<
25 select HAVE_ARCH_HASH <<
26 select HAVE_ARCH_KGDB <<
27 select HAVE_ARCH_SECCOMP <<
28 select HAVE_DEBUG_KMEMLEAK <<
29 select HAVE_DMA_CONTIGUOUS <<
30 select HAVE_DYNAMIC_FTRACE <<
31 select HAVE_FTRACE_MCOUNT_RECORD <<
32 select HAVE_FUNCTION_GRAPH_TRACER <<
33 select HAVE_FUNCTION_TRACER <<
34 select HAVE_PAGE_SIZE_4KB <<
35 select HAVE_PCI <<
36 select IRQ_DOMAIN <<
37 select XILINX_INTC <<
38 select MODULES_USE_ELF_RELA <<
39 select OF <<
40 select OF_EARLY_FLATTREE <<
41 select PCI_DOMAINS_GENERIC if PCI <<
42 select PCI_SYSCALL if PCI <<
43 select CPU_NO_EFFICIENT_FFS <<
44 select MMU_GATHER_NO_RANGE <<
45 select SPARSE_IRQ <<
46 select ZONE_DMA <<
47 select TRACE_IRQFLAGS_SUPPORT <<
48 select GENERIC_IRQ_MULTI_HANDLER <<
49 10
50 # Endianness selection !! 11 config MMU
51 choice !! 12 bool
52 prompt "Endianness selection" !! 13 default y
53 default CPU_LITTLE_ENDIAN !! 14
>> 15 source "init/Kconfig"
>> 16
>> 17
>> 18 menu "General setup"
>> 19
>> 20 config BBC_I2C
>> 21 tristate "UltraSPARC-III bootbus i2c controller driver"
>> 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.
>> 30
>> 31 config VT
>> 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.
>> 83
>> 84 config HW_CONSOLE
>> 85 bool
>> 86 default y
>> 87
>> 88 config SMP
>> 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.
>> 94
>> 95 If you say N here, the kernel will run on single and multiprocessor
>> 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.
>> 109
>> 110 See also the <file:Documentation/smp.tex>,
>> 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.
>> 125
>> 126 Say Y here if you are building a kernel for a desktop, embedded
>> 127 or real-time system. Say N if you are unsure.
>> 128
>> 129 config NR_CPUS
>> 130 int "Maximum number of CPUs (2-64)"
>> 131 depends on SMP
>> 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.
>> 152
>> 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
54 help 168 help
55 microblaze architectures can be conf !! 169 This adds the CPUFreq driver for UltraSPARC-IIe processors.
56 big endian formats. Be sure to selec !! 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
>> 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.
>> 205
>> 206 # Global things across all Sun machines.
>> 207 config RWSEM_GENERIC_SPINLOCK
>> 208 bool
>> 209
>> 210 config RWSEM_XCHGADD_ALGORITHM
>> 211 bool
>> 212 default y
>> 213
>> 214 choice
>> 215 prompt "SPARC64 Huge TLB Page Size"
>> 216 depends on HUGETLB_PAGE
>> 217 default HUGETLB_PAGE_SIZE_4MB
57 218
58 config CPU_BIG_ENDIAN !! 219 config HUGETLB_PAGE_SIZE_4MB
59 bool "Big endian" !! 220 bool "4MB"
60 221
61 config CPU_LITTLE_ENDIAN !! 222 config HUGETLB_PAGE_SIZE_512K
62 bool "Little endian" !! 223 bool "512K"
>> 224
>> 225 config HUGETLB_PAGE_SIZE_64K
>> 226 bool "64K"
63 227
64 endchoice 228 endchoice
65 229
66 config ARCH_HAS_ILOG2_U32 !! 230 config GENERIC_ISA_DMA
67 def_bool n !! 231 bool
>> 232 default y
68 233
69 config ARCH_HAS_ILOG2_U64 !! 234 config ISA
70 def_bool n !! 235 bool
>> 236 help
>> 237 Find out whether you have ISA slots on your motherboard. ISA is the
>> 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.
71 242
72 config GENERIC_HWEIGHT !! 243 config ISAPNP
73 def_bool y !! 244 bool
>> 245 help
>> 246 Say Y here if you would like support for ISA Plug and Play devices.
>> 247 Some information is in <file:Documentation/isapnp.txt>.
74 248
75 config GENERIC_CALIBRATE_DELAY !! 249 To compile this driver as a module, choose M here: the
76 def_bool y !! 250 module will be called isapnp.
77 251
78 config GENERIC_CSUM !! 252 If unsure, say Y.
79 def_bool y <<
80 253
81 config STACKTRACE_SUPPORT !! 254 config EISA
82 def_bool y !! 255 bool
>> 256 ---help---
>> 257 The Extended Industry Standard Architecture (EISA) bus was
>> 258 developed as an open alternative to the IBM MicroChannel bus.
83 259
84 config LOCKDEP_SUPPORT !! 260 The EISA bus provided some of the features of the IBM MicroChannel
85 def_bool y !! 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.
86 264
87 source "arch/microblaze/Kconfig.platform" !! 265 Say Y here if you are building a kernel for an EISA-based machine.
88 266
89 menu "Processor type and features" !! 267 Otherwise, say N.
90 268
91 source "kernel/Kconfig.hz" !! 269 config MCA
>> 270 bool
>> 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.
>> 286
>> 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
>> 296 bool
>> 297 default y
>> 298
>> 299 config SBUSCHAR
>> 300 bool
>> 301 default y
>> 302
>> 303 config SUN_AUXIO
>> 304 bool
>> 305 default y
>> 306
>> 307 config SUN_IO
>> 308 bool
>> 309 default y
92 310
93 config MMU !! 311 config PCI
94 def_bool y !! 312 bool "PCI support"
>> 313 help
>> 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.
>> 337
>> 338 Every PC has such a clock built in. It can be used to generate
>> 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.
>> 343
>> 344 If you run Linux on a multiprocessor machine and said Y to
>> 345 "Symmetric Multi Processing" above, you should say Y here to read
>> 346 and set the RTC in an SMP compatible fashion.
>> 347
>> 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.
>> 351
>> 352 To compile this driver as a module, choose M here: the
>> 353 module will be called rtc.
>> 354
>> 355 source "drivers/pci/Kconfig"
95 356
96 comment "Boot options" !! 357 config SUN_OPENPROMFS
>> 358 tristate "Openprom tree appears in /proc/openprom"
>> 359 help
>> 360 If you say Y, the OpenPROM device tree will be available as a
>> 361 virtual file system, which you can mount to /proc/openprom by "mount
>> 362 -t openpromfs none /proc/openprom".
>> 363
>> 364 To compile the /proc/openprom support as a module, choose M here: the
>> 365 module will be called openpromfs. If unsure, choose M.
>> 366
>> 367 config SPARC32_COMPAT
>> 368 bool "Kernel support for Linux/Sparc 32bit binary compatibility"
>> 369 help
>> 370 This allows you to run 32-bit binaries on your Ultra.
>> 371 Everybody wants this; say Y.
>> 372
>> 373 config COMPAT
>> 374 bool
>> 375 depends on SPARC32_COMPAT
>> 376 default y
>> 377
>> 378 config UID16
>> 379 bool
>> 380 depends on SPARC32_COMPAT
>> 381 default y
>> 382
>> 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.
97 397
98 config CMDLINE_BOOL !! 398 source "fs/Kconfig.binfmt"
99 bool "Default bootloader kernel argume <<
100 399
101 config CMDLINE !! 400 config SUNOS_EMUL
102 string "Default kernel command string" !! 401 bool "SunOS binary emulation"
103 depends on CMDLINE_BOOL !! 402 help
104 default "console=ttyUL0,115200" !! 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
105 help 412 help
106 On some architectures there is curre !! 413 This is experimental code which will enable you to run (many)
107 to pass arguments to the kernel. For !! 414 Solaris binaries on your SPARC Linux machine.
108 supply some command-line options at !! 415
109 here. !! 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.
110 455
111 config CMDLINE_FORCE !! 456 config DISPLAY7SEG
112 bool "Force default kernel command str !! 457 tristate "7-Segment Display support"
113 depends on CMDLINE_BOOL !! 458 depends on PCI
114 default n !! 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
115 help 487 help
116 Set this to have arguments from the !! 488 Say Y here to support the hardware watchdog capability on Sun RIO
117 override those passed by the boot lo !! 489 machines. The watchdog timeout period is normally one minute but
>> 490 can be changed with a boot-time parameter.
118 491
119 endmenu 492 endmenu
120 493
121 menu "Kernel features" !! 494 source "drivers/base/Kconfig"
122 495
123 config NR_CPUS !! 496 source "drivers/video/Kconfig"
124 int !! 497
125 default "1" !! 498 source "drivers/serial/Kconfig"
126 499
127 config ADVANCED_OPTIONS !! 500 source "drivers/sbus/char/Kconfig"
128 bool "Prompt for advanced kernel confi !! 501
>> 502 source "drivers/mtd/Kconfig"
>> 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"
129 help 621 help
130 This option will enable prompting fo !! 622 The default value is 4096. Only change this if you know what are
131 configuration options. These option !! 623 you doing. If you are using IBM S/390, then set this to 8192.
132 work if they are set incorrectly, bu !! 624
133 aspects of kernel memory management. !! 625 config BLK_DEV_INITRD
134 !! 626 bool "Initial RAM disk (initrd) support"
135 Unless you know what you are doing, !! 627 depends on BLK_DEV_RAM=y
136 !! 628 help
137 comment "Default settings for advanced configu !! 629 The initial RAM disk is a RAM disk that is loaded by the boot loader
138 depends on !ADVANCED_OPTIONS !! 630 (loadlin or lilo) and that is mounted as root before the normal boot
139 !! 631 procedure. It is typically used to load modules needed to mount the
140 config HIGHMEM !! 632 "real" root file system, etc. See <file:Documentation/initrd.txt>
141 bool "High memory support" !! 633 for details.
142 select KMAP_LOCAL !! 634
143 help !! 635 endmenu
144 The address space of Microblaze proc !! 636
145 and it has to accommodate user addre !! 637
146 space as well as some memory mapped !! 638 source "drivers/ide/Kconfig"
147 have a large amount of physical memo !! 639
148 memory can be "permanently mapped" b !! 640 source "drivers/scsi/Kconfig"
149 memory that is not permanently mappe !! 641
150 !! 642 source "drivers/fc4/Kconfig"
151 If unsure, say n. !! 643
152 !! 644 if PCI
153 config LOWMEM_SIZE_BOOL !! 645 source "drivers/message/fusion/Kconfig"
154 bool "Set maximum low memory" !! 646 endif
155 depends on ADVANCED_OPTIONS !! 647
156 help !! 648 source "drivers/ieee1394/Kconfig"
157 This option allows you to set the ma <<
158 will be used as "low memory", that i <<
159 access directly, without having to s <<
160 This can be useful in optimizing the <<
161 memory. <<
162 649
163 Say N here unless you know what you !! 650 source "net/Kconfig"
164 651
165 config LOWMEM_SIZE !! 652 source "drivers/isdn/Kconfig"
166 hex "Maximum low memory size (in bytes <<
167 default "0x30000000" <<
168 653
169 config MANUAL_RESET_VECTOR !! 654 source "drivers/telephony/Kconfig"
170 hex "Microblaze reset vector address s !! 655
171 default "0x0" !! 656 # This one must be before the filesystem configs. -DaveM
>> 657
>> 658 menu "Unix 98 PTY support"
>> 659
>> 660 config UNIX98_PTYS
>> 661 bool "Unix98 PTY support"
>> 662 ---help---
>> 663 A pseudo terminal (PTY) is a software device consisting of two
>> 664 halves: a master and a slave. The slave device behaves identical to
>> 665 a physical terminal; the master device is used by a process to
>> 666 read data from and write data to the slave, thereby emulating a
>> 667 terminal. Typical programs for the master side are telnet servers
>> 668 and xterms.
>> 669
>> 670 Linux has traditionally used the BSD-like names /dev/ptyxx for
>> 671 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
>> 672 has a number of problems. The GNU C library glibc 2.1 and later,
>> 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"
172 help 692 help
173 Set this option to have the kernel o !! 693 The maximum number of Unix98 PTYs that can be used at any one time.
174 If zero, no change will be made to t !! 694 The default is 256, and should be enough for desktop systems. Server
175 address 0x0. !! 695 machines which support incoming telnet/rlogin/ssh connections and/or
176 If non-zero, a jump instruction to t !! 696 serve several X terminals may want to increase this: every incoming
177 to the reset vector at address 0x0. !! 697 connection and every xterm uses up one PTY.
178 If you are unsure, set it to default <<
179 698
180 config KERNEL_START_BOOL !! 699 When not in use, each additional set of 256 PTYs occupy
181 bool "Set custom kernel base address" !! 700 approximately 8 KB of kernel memory on 32-bit architectures.
182 depends on ADVANCED_OPTIONS !! 701
>> 702 endmenu
>> 703
>> 704
>> 705 menu "XFree86 DRI support"
>> 706
>> 707 config DRM
>> 708 bool "Direct Rendering Manager (XFree86 DRI support)"
>> 709 help
>> 710 Kernel-level support for the Direct Rendering Infrastructure (DRI)
>> 711 introduced in XFree86 4.0. If you say Y here, you need to select
>> 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
183 help 729 help
184 This option allows you to set the ke !! 730 Choose this option if you have a 3dfx Banshee or Voodoo3 (or later),
185 the kernel will map low memory (the !! 731 graphics card. If M is selected, the module will be called tdfx.
186 this address). This can be useful i <<
187 layout of the system. <<
188 732
189 Say N here unless you know what you !! 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).
>> 740
>> 741 endmenu
>> 742
>> 743 source "drivers/input/Kconfig"
>> 744
>> 745 source "drivers/i2c/Kconfig"
>> 746
>> 747 source "fs/Kconfig"
>> 748
>> 749 source "drivers/media/Kconfig"
190 750
191 config KERNEL_START !! 751 source "sound/Kconfig"
192 hex "Virtual address of kernel base" i <<
193 default "0xc0000000" <<
194 752
195 config TASK_SIZE_BOOL !! 753 source "drivers/usb/Kconfig"
196 bool "Set custom user task size" !! 754
197 depends on ADVANCED_OPTIONS !! 755
>> 756 menu "Watchdog"
>> 757
>> 758 config SOFT_WATCHDOG
>> 759 tristate "Software watchdog"
198 help 760 help
199 This option allows you to set the am !! 761 A software monitoring watchdog. This will fail to reboot your system
200 allocated to user tasks. This can b !! 762 from some situations that the hardware watchdog will recover
201 virtual memory layout of the system. !! 763 from. Equally it's a lot cheaper to install.
202 764
203 Say N here unless you know what you !! 765 To compile this driver as a module, choose M here: the
>> 766 module will be called softdog.
204 767
205 config TASK_SIZE !! 768 endmenu
206 hex "Size of user task space" if TASK_ <<
207 default "0x80000000" <<
208 769
209 config MB_MANAGER !! 770 source "arch/sparc64/oprofile/Kconfig"
210 bool "Support for Microblaze Manager" !! 771
211 depends on ADVANCED_OPTIONS !! 772 menu "Kernel hacking"
>> 773
>> 774 config DEBUG_KERNEL
>> 775 bool "Kernel debugging"
212 help 776 help
213 This option enables API for configur !! 777 Say Y here if you are developing drivers or trying to debug and
214 control register, which is consumed !! 778 identify kernel problems.
215 block the break. <<
216 779
217 Say N here unless you know what you !! 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.
>> 787
>> 788 config MAGIC_SYSRQ
>> 789 bool "Magic SysRq key"
>> 790 depends on DEBUG_KERNEL
>> 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
>> 818
>> 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.
>> 824
>> 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"
>> 848
>> 849 config MCOUNT
>> 850 bool
>> 851 depends on STACK_DEBUG
>> 852 default y
218 853
219 endmenu 854 endmenu
>> 855
>> 856 source "security/Kconfig"
>> 857
>> 858 source "crypto/Kconfig"
>> 859
>> 860 source "lib/Kconfig"
>> 861
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.