ia64/linux-2.6.18-xen.hg

annotate drivers/char/Kconfig @ 893:f994bfe9b93b

linux/blktap2: reduce TLB flush scope

c/s 885 added very coarse TLB flushing. Since these flushes always
follow single page updates, single page flushes (when available) are
sufficient.

Signed-off-by: Jan Beulich <jbeulich@novell.com>
author Keir Fraser <keir.fraser@citrix.com>
date Thu Jun 04 10:32:57 2009 +0100 (2009-06-04)
parents 099864f50909
children
rev   line source
ian@0 1 #
ian@0 2 # Character device configuration
ian@0 3 #
ian@0 4
ian@0 5 menu "Character devices"
ian@0 6
ian@0 7 config VT
ian@0 8 bool "Virtual terminal" if EMBEDDED
ian@0 9 select INPUT
ian@0 10 default y if !VIOCONS
ian@0 11 ---help---
ian@0 12 If you say Y here, you will get support for terminal devices with
ian@0 13 display and keyboard devices. These are called "virtual" because you
ian@0 14 can run several virtual terminals (also called virtual consoles) on
ian@0 15 one physical terminal. This is rather useful, for example one
ian@0 16 virtual terminal can collect system messages and warnings, another
ian@0 17 one can be used for a text-mode user session, and a third could run
ian@0 18 an X session, all in parallel. Switching between virtual terminals
ian@0 19 is done with certain key combinations, usually Alt-<function key>.
ian@0 20
ian@0 21 The setterm command ("man setterm") can be used to change the
ian@0 22 properties (such as colors or beeping) of a virtual terminal. The
ian@0 23 man page console_codes(4) ("man console_codes") contains the special
ian@0 24 character sequences that can be used to change those properties
ian@0 25 directly. The fonts used on virtual terminals can be changed with
ian@0 26 the setfont ("man setfont") command and the key bindings are defined
ian@0 27 with the loadkeys ("man loadkeys") command.
ian@0 28
ian@0 29 You need at least one virtual terminal device in order to make use
ian@0 30 of your keyboard and monitor. Therefore, only people configuring an
ian@0 31 embedded system would want to say N here in order to save some
ian@0 32 memory; the only way to log into such a system is then via a serial
ian@0 33 or network connection.
ian@0 34
ian@0 35 If unsure, say Y, or else you won't be able to do much with your new
ian@0 36 shiny Linux system :-)
ian@0 37
ian@0 38 config VT_CONSOLE
ian@0 39 bool "Support for console on virtual terminal" if EMBEDDED
ian@0 40 depends on VT
ian@0 41 default y
ian@0 42 ---help---
ian@0 43 The system console is the device which receives all kernel messages
ian@0 44 and warnings and which allows logins in single user mode. If you
ian@0 45 answer Y here, a virtual terminal (the device used to interact with
ian@0 46 a physical terminal) can be used as system console. This is the most
ian@0 47 common mode of operations, so you should say Y here unless you want
ian@0 48 the kernel messages be output only to a serial port (in which case
ian@0 49 you should say Y to "Console on serial port", below).
ian@0 50
ian@0 51 If you do say Y here, by default the currently visible virtual
ian@0 52 terminal (/dev/tty0) will be used as system console. You can change
ian@0 53 that with a kernel command line option such as "console=tty3" which
ian@0 54 would use the third virtual terminal as system console. (Try "man
ian@0 55 bootparam" or see the documentation of your boot loader (lilo or
ian@0 56 loadlin) about how to pass options to the kernel at boot time.)
ian@0 57
ian@0 58 If unsure, say Y.
ian@0 59
ian@0 60 config HW_CONSOLE
ian@0 61 bool
ian@0 62 depends on VT && !S390 && !UML
ian@0 63 default y
ian@0 64
ian@0 65 config VT_HW_CONSOLE_BINDING
ian@0 66 bool "Support for binding and unbinding console drivers"
ian@0 67 depends on HW_CONSOLE
ian@0 68 default n
ian@0 69 ---help---
ian@0 70 The virtual terminal is the device that interacts with the physical
ian@0 71 terminal through console drivers. On these systems, at least one
ian@0 72 console driver is loaded. In other configurations, additional console
ian@0 73 drivers may be enabled, such as the framebuffer console. If more than
ian@0 74 1 console driver is enabled, setting this to 'y' will allow you to
ian@0 75 select the console driver that will serve as the backend for the
ian@0 76 virtual terminals.
ian@0 77
ian@0 78 See <file:Documentation/console/console.txt> for more
ian@0 79 information. For framebuffer console users, please refer to
ian@0 80 <file:Documentation/fb/fbcon.txt>.
ian@0 81
ian@0 82 config SERIAL_NONSTANDARD
ian@0 83 bool "Non-standard serial port support"
ian@0 84 ---help---
ian@0 85 Say Y here if you have any non-standard serial boards -- boards
ian@0 86 which aren't supported using the standard "dumb" serial driver.
ian@0 87 This includes intelligent serial boards such as Cyclades,
ian@0 88 Digiboards, etc. These are usually used for systems that need many
ian@0 89 serial ports because they serve many terminals or dial-in
ian@0 90 connections.
ian@0 91
ian@0 92 Note that the answer to this question won't directly affect the
ian@0 93 kernel: saying N will just cause the configurator to skip all
ian@0 94 the questions about non-standard serial boards.
ian@0 95
ian@0 96 Most people can say N here.
ian@0 97
ian@0 98 config COMPUTONE
ian@0 99 tristate "Computone IntelliPort Plus serial support"
ian@0 100 depends on SERIAL_NONSTANDARD
ian@0 101 ---help---
ian@0 102 This driver supports the entire family of Intelliport II/Plus
ian@0 103 controllers with the exception of the MicroChannel controllers and
ian@0 104 products previous to the Intelliport II. These are multiport cards,
ian@0 105 which give you many serial ports. You would need something like this
ian@0 106 to connect more than two modems to your Linux box, for instance in
ian@0 107 order to become a dial-in server. If you have a card like that, say
ian@0 108 Y here and read <file:Documentation/computone.txt>.
ian@0 109
ian@0 110 To compile this driver as modules, choose M here: the
ian@0 111 modules will be called ip2 and ip2main.
ian@0 112
ian@0 113 config ROCKETPORT
ian@0 114 tristate "Comtrol RocketPort support"
ian@0 115 depends on SERIAL_NONSTANDARD
ian@0 116 help
ian@0 117 This driver supports Comtrol RocketPort and RocketModem PCI boards.
ian@0 118 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
ian@0 119 modems. For information about the RocketPort/RocketModem boards
ian@0 120 and this driver read <file:Documentation/rocket.txt>.
ian@0 121
ian@0 122 To compile this driver as a module, choose M here: the
ian@0 123 module will be called rocket.
ian@0 124
ian@0 125 If you want to compile this driver into the kernel, say Y here. If
ian@0 126 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
ian@0 127
ian@0 128 config CYCLADES
ian@0 129 tristate "Cyclades async mux support"
ian@0 130 depends on SERIAL_NONSTANDARD
ian@0 131 ---help---
ian@0 132 This driver supports Cyclades Z and Y multiserial boards.
ian@0 133 You would need something like this to connect more than two modems to
ian@0 134 your Linux box, for instance in order to become a dial-in server.
ian@0 135
ian@0 136 For information about the Cyclades-Z card, read
ian@0 137 <file:drivers/char/README.cycladesZ>.
ian@0 138
ian@0 139 To compile this driver as a module, choose M here: the
ian@0 140 module will be called cyclades.
ian@0 141
ian@0 142 If you haven't heard about it, it's safe to say N.
ian@0 143
ian@0 144 config CYZ_INTR
ian@0 145 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
ian@0 146 depends on EXPERIMENTAL && CYCLADES
ian@0 147 help
ian@0 148 The Cyclades-Z family of multiport cards allows 2 (two) driver op
ian@0 149 modes: polling and interrupt. In polling mode, the driver will check
ian@0 150 the status of the Cyclades-Z ports every certain amount of time
ian@0 151 (which is called polling cycle and is configurable). In interrupt
ian@0 152 mode, it will use an interrupt line (IRQ) in order to check the
ian@0 153 status of the Cyclades-Z ports. The default op mode is polling. If
ian@0 154 unsure, say N.
ian@0 155
ian@0 156 config DIGIEPCA
ian@0 157 tristate "Digiboard Intelligent Async Support"
ian@0 158 depends on SERIAL_NONSTANDARD
ian@0 159 ---help---
ian@0 160 This is a driver for Digi International's Xx, Xeve, and Xem series
ian@0 161 of cards which provide multiple serial ports. You would need
ian@0 162 something like this to connect more than two modems to your Linux
ian@0 163 box, for instance in order to become a dial-in server. This driver
ian@0 164 supports the original PC (ISA) boards as well as PCI, and EISA. If
ian@0 165 you have a card like this, say Y here and read the file
ian@0 166 <file:Documentation/digiepca.txt>.
ian@0 167
ian@0 168 To compile this driver as a module, choose M here: the
ian@0 169 module will be called epca.
ian@0 170
ian@0 171 config ESPSERIAL
ian@0 172 tristate "Hayes ESP serial port support"
ian@0 173 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
ian@0 174 help
ian@0 175 This is a driver which supports Hayes ESP serial ports. Both single
ian@0 176 port cards and multiport cards are supported. Make sure to read
ian@0 177 <file:Documentation/hayes-esp.txt>.
ian@0 178
ian@0 179 To compile this driver as a module, choose M here: the
ian@0 180 module will be called esp.
ian@0 181
ian@0 182 If unsure, say N.
ian@0 183
ian@0 184 config MOXA_INTELLIO
ian@0 185 tristate "Moxa Intellio support"
ian@0 186 depends on SERIAL_NONSTANDARD
ian@0 187 help
ian@0 188 Say Y here if you have a Moxa Intellio multiport serial card.
ian@0 189
ian@0 190 To compile this driver as a module, choose M here: the
ian@0 191 module will be called moxa.
ian@0 192
ian@0 193 config MOXA_SMARTIO
ian@0 194 tristate "Moxa SmartIO support"
ian@0 195 depends on SERIAL_NONSTANDARD
ian@0 196 help
ian@0 197 Say Y here if you have a Moxa SmartIO multiport serial card.
ian@0 198
ian@0 199 This driver can also be built as a module ( = code which can be
ian@0 200 inserted in and removed from the running kernel whenever you want).
ian@0 201 The module will be called mxser. If you want to do that, say M
ian@0 202 here.
ian@0 203
ian@0 204 config ISI
ian@0 205 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
ian@0 206 depends on SERIAL_NONSTANDARD
ian@0 207 select FW_LOADER
ian@0 208 help
ian@0 209 This is a driver for the Multi-Tech cards which provide several
ian@0 210 serial ports. The driver is experimental and can currently only be
ian@0 211 built as a module. The module will be called isicom.
ian@0 212 If you want to do that, choose M here.
ian@0 213
ian@0 214 config SYNCLINK
ian@0 215 tristate "Microgate SyncLink card support"
ian@0 216 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
ian@0 217 help
ian@0 218 Provides support for the SyncLink ISA and PCI multiprotocol serial
ian@0 219 adapters. These adapters support asynchronous and HDLC bit
ian@0 220 synchronous communication up to 10Mbps (PCI adapter).
ian@0 221
ian@0 222 This driver can only be built as a module ( = code which can be
ian@0 223 inserted in and removed from the running kernel whenever you want).
ian@0 224 The module will be called synclink. If you want to do that, say M
ian@0 225 here.
ian@0 226
ian@0 227 config SYNCLINKMP
ian@0 228 tristate "SyncLink Multiport support"
ian@0 229 depends on SERIAL_NONSTANDARD
ian@0 230 help
ian@0 231 Enable support for the SyncLink Multiport (2 or 4 ports)
ian@0 232 serial adapter, running asynchronous and HDLC communications up
ian@0 233 to 2.048Mbps. Each ports is independently selectable for
ian@0 234 RS-232, V.35, RS-449, RS-530, and X.21
ian@0 235
ian@0 236 This driver may be built as a module ( = code which can be
ian@0 237 inserted in and removed from the running kernel whenever you want).
ian@0 238 The module will be called synclinkmp. If you want to do that, say M
ian@0 239 here.
ian@0 240
ian@0 241 config SYNCLINK_GT
ian@0 242 tristate "SyncLink GT/AC support"
ian@0 243 depends on SERIAL_NONSTANDARD && PCI
ian@0 244 help
ian@0 245 Support for SyncLink GT and SyncLink AC families of
ian@0 246 synchronous and asynchronous serial adapters
ian@0 247 manufactured by Microgate Systems, Ltd. (www.microgate.com)
ian@0 248
ian@0 249 config N_HDLC
ian@0 250 tristate "HDLC line discipline support"
ian@0 251 depends on SERIAL_NONSTANDARD
ian@0 252 help
ian@0 253 Allows synchronous HDLC communications with tty device drivers that
ian@0 254 support synchronous HDLC such as the Microgate SyncLink adapter.
ian@0 255
ian@0 256 This driver can only be built as a module ( = code which can be
ian@0 257 inserted in and removed from the running kernel whenever you want).
ian@0 258 The module will be called n_hdlc. If you want to do that, say M
ian@0 259 here.
ian@0 260
ian@0 261 config RISCOM8
ian@0 262 tristate "SDL RISCom/8 card support"
ian@0 263 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
ian@0 264 help
ian@0 265 This is a driver for the SDL Communications RISCom/8 multiport card,
ian@0 266 which gives you many serial ports. You would need something like
ian@0 267 this to connect more than two modems to your Linux box, for instance
ian@0 268 in order to become a dial-in server. If you have a card like that,
ian@0 269 say Y here and read the file <file:Documentation/riscom8.txt>.
ian@0 270
ian@0 271 Also it's possible to say M here and compile this driver as kernel
ian@0 272 loadable module; the module will be called riscom8.
ian@0 273
ian@0 274 config SPECIALIX
ian@0 275 tristate "Specialix IO8+ card support"
ian@0 276 depends on SERIAL_NONSTANDARD
ian@0 277 help
ian@0 278 This is a driver for the Specialix IO8+ multiport card (both the
ian@0 279 ISA and the PCI version) which gives you many serial ports. You
ian@0 280 would need something like this to connect more than two modems to
ian@0 281 your Linux box, for instance in order to become a dial-in server.
ian@0 282
ian@0 283 If you have a card like that, say Y here and read the file
ian@0 284 <file:Documentation/specialix.txt>. Also it's possible to say M here
ian@0 285 and compile this driver as kernel loadable module which will be
ian@0 286 called specialix.
ian@0 287
ian@0 288 config SPECIALIX_RTSCTS
ian@0 289 bool "Specialix DTR/RTS pin is RTS"
ian@0 290 depends on SPECIALIX
ian@0 291 help
ian@0 292 The Specialix IO8+ card can only support either RTS or DTR. If you
ian@0 293 say N here, the driver will use the pin as "DTR" when the tty is in
ian@0 294 software handshake mode. If you say Y here or hardware handshake is
ian@0 295 on, it will always be RTS. Read the file
ian@0 296 <file:Documentation/specialix.txt> for more information.
ian@0 297
ian@0 298 config SX
ian@0 299 tristate "Specialix SX (and SI) card support"
ian@0 300 depends on SERIAL_NONSTANDARD
ian@0 301 help
ian@0 302 This is a driver for the SX and SI multiport serial cards.
ian@0 303 Please read the file <file:Documentation/sx.txt> for details.
ian@0 304
ian@0 305 This driver can only be built as a module ( = code which can be
ian@0 306 inserted in and removed from the running kernel whenever you want).
ian@0 307 The module will be called sx. If you want to do that, say M here.
ian@0 308
ian@0 309 config RIO
ian@0 310 tristate "Specialix RIO system support"
ian@0 311 depends on SERIAL_NONSTANDARD
ian@0 312 help
ian@0 313 This is a driver for the Specialix RIO, a smart serial card which
ian@0 314 drives an outboard box that can support up to 128 ports. Product
ian@0 315 information is at <http://www.perle.com/support/documentation.html#multiport>.
ian@0 316 There are both ISA and PCI versions.
ian@0 317
ian@0 318 config RIO_OLDPCI
ian@0 319 bool "Support really old RIO/PCI cards"
ian@0 320 depends on RIO
ian@0 321 help
ian@0 322 Older RIO PCI cards need some initialization-time configuration to
ian@0 323 determine the IRQ and some control addresses. If you have a RIO and
ian@0 324 this doesn't seem to work, try setting this to Y.
ian@0 325
ian@0 326 config STALDRV
ian@0 327 bool "Stallion multiport serial support"
ian@0 328 depends on SERIAL_NONSTANDARD
ian@0 329 help
ian@0 330 Stallion cards give you many serial ports. You would need something
ian@0 331 like this to connect more than two modems to your Linux box, for
ian@0 332 instance in order to become a dial-in server. If you say Y here,
ian@0 333 you will be asked for your specific card model in the next
ian@0 334 questions. Make sure to read <file:Documentation/stallion.txt> in
ian@0 335 this case. If you have never heard about all this, it's safe to
ian@0 336 say N.
ian@0 337
ian@0 338 config STALLION
ian@0 339 tristate "Stallion EasyIO or EC8/32 support"
ian@0 340 depends on STALDRV && BROKEN_ON_SMP
ian@0 341 help
ian@0 342 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
ian@0 343 card, then this is for you; say Y. Make sure to read
ian@0 344 <file:Documentation/stallion.txt>.
ian@0 345
ian@0 346 To compile this driver as a module, choose M here: the
ian@0 347 module will be called stallion.
ian@0 348
ian@0 349 config ISTALLION
ian@0 350 tristate "Stallion EC8/64, ONboard, Brumby support"
ian@0 351 depends on STALDRV && BROKEN_ON_SMP
ian@0 352 help
ian@0 353 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
ian@0 354 serial multiport card, say Y here. Make sure to read
ian@0 355 <file:Documentation/stallion.txt>.
ian@0 356
ian@0 357 To compile this driver as a module, choose M here: the
ian@0 358 module will be called istallion.
ian@0 359
ian@0 360 config AU1000_UART
ian@0 361 bool "Enable Au1000 UART Support"
ian@0 362 depends on SERIAL_NONSTANDARD && MIPS
ian@0 363 help
ian@0 364 If you have an Alchemy AU1000 processor (MIPS based) and you want
ian@0 365 to use serial ports, say Y. Otherwise, say N.
ian@0 366
ian@0 367 config AU1000_SERIAL_CONSOLE
ian@0 368 bool "Enable Au1000 serial console"
ian@0 369 depends on AU1000_UART
ian@0 370 help
ian@0 371 If you have an Alchemy AU1000 processor (MIPS based) and you want
ian@0 372 to use a console on a serial port, say Y. Otherwise, say N.
ian@0 373
ian@0 374 config QTRONIX_KEYBOARD
ian@0 375 bool "Enable Qtronix 990P Keyboard Support"
ian@0 376 depends on IT8712
ian@0 377 help
ian@0 378 Images of Qtronix keyboards are at
ian@0 379 <http://www.qtronix.com/keyboard.html>.
ian@0 380
ian@0 381 config IT8172_CIR
ian@0 382 bool
ian@0 383 depends on QTRONIX_KEYBOARD
ian@0 384 default y
ian@0 385
ian@0 386 config IT8172_SCR0
ian@0 387 bool "Enable Smart Card Reader 0 Support "
ian@0 388 depends on IT8712
ian@0 389 help
ian@0 390 Say Y here to support smart-card reader 0 (SCR0) on the Integrated
ian@0 391 Technology Express, Inc. ITE8172 SBC. Vendor page at
ian@0 392 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
ian@0 393 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
ian@0 394
ian@0 395 config IT8172_SCR1
ian@0 396 bool "Enable Smart Card Reader 1 Support "
ian@0 397 depends on IT8712
ian@0 398 help
ian@0 399 Say Y here to support smart-card reader 1 (SCR1) on the Integrated
ian@0 400 Technology Express, Inc. ITE8172 SBC. Vendor page at
ian@0 401 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
ian@0 402 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
ian@0 403
ian@0 404 config A2232
ian@0 405 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
ian@0 406 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
ian@0 407 ---help---
ian@0 408 This option supports the 2232 7-port serial card shipped with the
ian@0 409 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
ian@0 410 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
ian@0 411 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
ian@0 412 ports were connected with 8 pin DIN connectors on the card bracket,
ian@0 413 for which 8 pin to DB25 adapters were supplied. The card also had
ian@0 414 jumpers internally to toggle various pinning configurations.
ian@0 415
ian@0 416 This driver can be built as a module; but then "generic_serial"
ian@0 417 will also be built as a module. This has to be loaded before
ian@0 418 "ser_a2232". If you want to do this, answer M here.
ian@0 419
ian@0 420 config SGI_SNSC
ian@0 421 bool "SGI Altix system controller communication support"
ian@0 422 depends on (IA64_SGI_SN2 || IA64_GENERIC)
ian@0 423 help
ian@0 424 If you have an SGI Altix and you want to enable system
ian@0 425 controller communication from user space (you want this!),
ian@0 426 say Y. Otherwise, say N.
ian@0 427
ian@0 428 config SGI_TIOCX
ian@0 429 bool "SGI TIO CX driver support"
ian@0 430 depends on (IA64_SGI_SN2 || IA64_GENERIC)
ian@0 431 help
ian@0 432 If you have an SGI Altix and you have fpga devices attached
ian@0 433 to your TIO, say Y here, otherwise say N.
ian@0 434
ian@0 435 config SGI_MBCS
ian@0 436 tristate "SGI FPGA Core Services driver support"
ian@0 437 depends on SGI_TIOCX
ian@0 438 help
ian@0 439 If you have an SGI Altix with an attached SABrick
ian@0 440 say Y or M here, otherwise say N.
ian@0 441
ian@0 442 source "drivers/serial/Kconfig"
ian@0 443
ian@0 444 config UNIX98_PTYS
ian@0 445 bool "Unix98 PTY support" if EMBEDDED
ian@0 446 default y
ian@0 447 ---help---
ian@0 448 A pseudo terminal (PTY) is a software device consisting of two
ian@0 449 halves: a master and a slave. The slave device behaves identical to
ian@0 450 a physical terminal; the master device is used by a process to
ian@0 451 read data from and write data to the slave, thereby emulating a
ian@0 452 terminal. Typical programs for the master side are telnet servers
ian@0 453 and xterms.
ian@0 454
ian@0 455 Linux has traditionally used the BSD-like names /dev/ptyxx for
ian@0 456 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
ian@0 457 has a number of problems. The GNU C library glibc 2.1 and later,
ian@0 458 however, supports the Unix98 naming standard: in order to acquire a
ian@0 459 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
ian@0 460 terminal is then made available to the process and the pseudo
ian@0 461 terminal slave can be accessed as /dev/pts/<number>. What was
ian@0 462 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
ian@0 463
ian@0 464 All modern Linux systems use the Unix98 ptys. Say Y unless
ian@0 465 you're on an embedded system and want to conserve memory.
ian@0 466
ian@0 467 config LEGACY_PTYS
ian@0 468 bool "Legacy (BSD) PTY support"
ian@0 469 default y
ian@0 470 ---help---
ian@0 471 A pseudo terminal (PTY) is a software device consisting of two
ian@0 472 halves: a master and a slave. The slave device behaves identical to
ian@0 473 a physical terminal; the master device is used by a process to
ian@0 474 read data from and write data to the slave, thereby emulating a
ian@0 475 terminal. Typical programs for the master side are telnet servers
ian@0 476 and xterms.
ian@0 477
ian@0 478 Linux has traditionally used the BSD-like names /dev/ptyxx
ian@0 479 for masters and /dev/ttyxx for slaves of pseudo
ian@0 480 terminals. This scheme has a number of problems, including
ian@0 481 security. This option enables these legacy devices; on most
ian@0 482 systems, it is safe to say N.
ian@0 483
ian@0 484
ian@0 485 config LEGACY_PTY_COUNT
ian@0 486 int "Maximum number of legacy PTY in use"
ian@0 487 depends on LEGACY_PTYS
ian@0 488 range 1 256
ian@0 489 default "256"
ian@0 490 ---help---
ian@0 491 The maximum number of legacy PTYs that can be used at any one time.
ian@0 492 The default is 256, and should be more than enough. Embedded
ian@0 493 systems may want to reduce this to save memory.
ian@0 494
ian@0 495 When not in use, each legacy PTY occupies 12 bytes on 32-bit
ian@0 496 architectures and 24 bytes on 64-bit architectures.
ian@0 497
ian@0 498 config PRINTER
ian@0 499 tristate "Parallel printer support"
ian@0 500 depends on PARPORT
ian@0 501 ---help---
ian@0 502 If you intend to attach a printer to the parallel port of your Linux
ian@0 503 box (as opposed to using a serial printer; if the connector at the
ian@0 504 printer has 9 or 25 holes ["female"], then it's serial), say Y.
ian@0 505 Also read the Printing-HOWTO, available from
ian@0 506 <http://www.tldp.org/docs.html#howto>.
ian@0 507
ian@0 508 It is possible to share one parallel port among several devices
ian@0 509 (e.g. printer and ZIP drive) and it is safe to compile the
ian@0 510 corresponding drivers into the kernel.
ian@0 511
ian@0 512 To compile this driver as a module, choose M here and read
ian@0 513 <file:Documentation/parport.txt>. The module will be called lp.
ian@0 514
ian@0 515 If you have several parallel ports, you can specify which ports to
ian@0 516 use with the "lp" kernel command line option. (Try "man bootparam"
ian@0 517 or see the documentation of your boot loader (lilo or loadlin) about
ian@0 518 how to pass options to the kernel at boot time.) The syntax of the
ian@0 519 "lp" command line option can be found in <file:drivers/char/lp.c>.
ian@0 520
ian@0 521 If you have more than 8 printers, you need to increase the LP_NO
ian@0 522 macro in lp.c and the PARPORT_MAX macro in parport.h.
ian@0 523
ian@0 524 config LP_CONSOLE
ian@0 525 bool "Support for console on line printer"
ian@0 526 depends on PRINTER
ian@0 527 ---help---
ian@0 528 If you want kernel messages to be printed out as they occur, you
ian@0 529 can have a console on the printer. This option adds support for
ian@0 530 doing that; to actually get it to happen you need to pass the
ian@0 531 option "console=lp0" to the kernel at boot time.
ian@0 532
ian@0 533 If the printer is out of paper (or off, or unplugged, or too
ian@0 534 busy..) the kernel will stall until the printer is ready again.
ian@0 535 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
ian@0 536 can make the kernel continue when this happens,
ian@0 537 but it'll lose the kernel messages.
ian@0 538
ian@0 539 If unsure, say N.
ian@0 540
ian@0 541 config PPDEV
ian@0 542 tristate "Support for user-space parallel port device drivers"
ian@0 543 depends on PARPORT
ian@0 544 ---help---
ian@0 545 Saying Y to this adds support for /dev/parport device nodes. This
ian@0 546 is needed for programs that want portable access to the parallel
ian@0 547 port, for instance deviceid (which displays Plug-and-Play device
ian@0 548 IDs).
ian@0 549
ian@0 550 This is the parallel port equivalent of SCSI generic support (sg).
ian@0 551 It is safe to say N to this -- it is not needed for normal printing
ian@0 552 or parallel port CD-ROM/disk support.
ian@0 553
ian@0 554 To compile this driver as a module, choose M here: the
ian@0 555 module will be called ppdev.
ian@0 556
ian@0 557 If unsure, say N.
ian@0 558
ian@0 559 config TIPAR
ian@0 560 tristate "Texas Instruments parallel link cable support"
ian@0 561 depends on PARPORT
ian@0 562 ---help---
ian@0 563 If you own a Texas Instruments graphing calculator and use a
ian@0 564 parallel link cable, then you might be interested in this driver.
ian@0 565
ian@0 566 If you enable this driver, you will be able to communicate with
ian@0 567 your calculator through a set of device nodes under /dev. The
ian@0 568 main advantage of this driver is that you don't have to be root
ian@0 569 to use this precise link cable (depending on the permissions on
ian@0 570 the device nodes, though).
ian@0 571
ian@0 572 To compile this driver as a module, choose M here: the
ian@0 573 module will be called tipar.
ian@0 574
ian@0 575 If you don't know what a parallel link cable is or what a Texas
ian@0 576 Instruments graphing calculator is, then you probably don't need this
ian@0 577 driver.
ian@0 578
ian@0 579 If unsure, say N.
ian@0 580
ian@0 581 config HVC_DRIVER
ian@0 582 bool
ian@0 583 help
ian@0 584 Users of pSeries machines that want to utilize the hvc console front-end
ian@0 585 module for their backend console driver should select this option.
ian@0 586 It will automatically be selected if one of the back-end console drivers
ian@0 587 is selected.
ian@0 588
ian@0 589
ian@0 590 config HVC_CONSOLE
ian@0 591 bool "pSeries Hypervisor Virtual Console support"
ian@0 592 depends on PPC_PSERIES
ian@0 593 select HVC_DRIVER
ian@0 594 help
ian@0 595 pSeries machines when partitioned support a hypervisor virtual
ian@0 596 console. This driver allows each pSeries partition to have a console
ian@0 597 which is accessed via the HMC.
ian@0 598
ian@0 599 config HVC_RTAS
ian@0 600 bool "IBM RTAS Console support"
ian@0 601 depends on PPC_RTAS
ian@0 602 select HVC_DRIVER
ian@0 603 help
ian@0 604 IBM Console device driver which makes use of RTAS
ian@0 605
ian@0 606 config HVCS
ian@0 607 tristate "IBM Hypervisor Virtual Console Server support"
ian@0 608 depends on PPC_PSERIES
ian@0 609 help
ian@0 610 Partitionable IBM Power5 ppc64 machines allow hosting of
ian@0 611 firmware virtual consoles from one Linux partition by
ian@0 612 another Linux partition. This driver allows console data
ian@0 613 from Linux partitions to be accessed through TTY device
ian@0 614 interfaces in the device tree of a Linux partition running
ian@0 615 this driver.
ian@0 616
ian@0 617 To compile this driver as a module, choose M here: the
ian@0 618 module will be called hvcs.ko. Additionally, this module
ian@0 619 will depend on arch specific APIs exported from hvcserver.ko
ian@0 620 which will also be compiled when this driver is built as a
ian@0 621 module.
ian@0 622
ian@0 623 source "drivers/char/ipmi/Kconfig"
ian@0 624
ian@0 625 source "drivers/char/watchdog/Kconfig"
ian@0 626
ian@0 627 config DS1620
ian@0 628 tristate "NetWinder thermometer support"
ian@0 629 depends on ARCH_NETWINDER
ian@0 630 help
ian@0 631 Say Y here to include support for the thermal management hardware
ian@0 632 found in the NetWinder. This driver allows the user to control the
ian@0 633 temperature set points and to read the current temperature.
ian@0 634
ian@0 635 It is also possible to say M here to build it as a module (ds1620)
ian@0 636 It is recommended to be used on a NetWinder, but it is not a
ian@0 637 necessity.
ian@0 638
ian@0 639 config NWBUTTON
ian@0 640 tristate "NetWinder Button"
ian@0 641 depends on ARCH_NETWINDER
ian@0 642 ---help---
ian@0 643 If you say Y here and create a character device node /dev/nwbutton
ian@0 644 with major and minor numbers 10 and 158 ("man mknod"), then every
ian@0 645 time the orange button is pressed a number of times, the number of
ian@0 646 times the button was pressed will be written to that device.
ian@0 647
ian@0 648 This is most useful for applications, as yet unwritten, which
ian@0 649 perform actions based on how many times the button is pressed in a
ian@0 650 row.
ian@0 651
ian@0 652 Do not hold the button down for too long, as the driver does not
ian@0 653 alter the behaviour of the hardware reset circuitry attached to the
ian@0 654 button; it will still execute a hard reset if the button is held
ian@0 655 down for longer than approximately five seconds.
ian@0 656
ian@0 657 To compile this driver as a module, choose M here: the
ian@0 658 module will be called nwbutton.
ian@0 659
ian@0 660 Most people will answer Y to this question and "Reboot Using Button"
ian@0 661 below to be able to initiate a system shutdown from the button.
ian@0 662
ian@0 663 config NWBUTTON_REBOOT
ian@0 664 bool "Reboot Using Button"
ian@0 665 depends on NWBUTTON
ian@0 666 help
ian@0 667 If you say Y here, then you will be able to initiate a system
ian@0 668 shutdown and reboot by pressing the orange button a number of times.
ian@0 669 The number of presses to initiate the shutdown is two by default,
ian@0 670 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
ian@0 671 in nwbutton.h and recompiling the driver or, if you compile the
ian@0 672 driver as a module, you can specify the number of presses at load
ian@0 673 time with "insmod button reboot_count=<something>".
ian@0 674
ian@0 675 config NWFLASH
ian@0 676 tristate "NetWinder flash support"
ian@0 677 depends on ARCH_NETWINDER
ian@0 678 ---help---
ian@0 679 If you say Y here and create a character device /dev/flash with
ian@0 680 major 10 and minor 160 you can manipulate the flash ROM containing
ian@0 681 the NetWinder firmware. Be careful as accidentally overwriting the
ian@0 682 flash contents can render your computer unbootable. On no account
ian@0 683 allow random users access to this device. :-)
ian@0 684
ian@0 685 To compile this driver as a module, choose M here: the
ian@0 686 module will be called nwflash.
ian@0 687
ian@0 688 If you're not sure, say N.
ian@0 689
ian@0 690 source "drivers/char/hw_random/Kconfig"
ian@0 691
ian@0 692 config NVRAM
ian@0 693 tristate "/dev/nvram support"
ian@0 694 depends on ATARI || X86 || ARM || GENERIC_NVRAM
ian@0 695 ---help---
ian@0 696 If you say Y here and create a character special file /dev/nvram
ian@0 697 with major number 10 and minor number 144 using mknod ("man mknod"),
ian@0 698 you get read and write access to the extra bytes of non-volatile
ian@0 699 memory in the real time clock (RTC), which is contained in every PC
ian@0 700 and most Ataris. The actual number of bytes varies, depending on the
ian@0 701 nvram in the system, but is usually 114 (128-14 for the RTC).
ian@0 702
ian@0 703 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
ian@0 704 on Ataris. /dev/nvram may be used to view settings there, or to
ian@0 705 change them (with some utility). It could also be used to frequently
ian@0 706 save a few bits of very important data that may not be lost over
ian@0 707 power-off and for which writing to disk is too insecure. Note
ian@0 708 however that most NVRAM space in a PC belongs to the BIOS and you
ian@0 709 should NEVER idly tamper with it. See Ralf Brown's interrupt list
ian@0 710 for a guide to the use of CMOS bytes by your BIOS.
ian@0 711
ian@0 712 On Atari machines, /dev/nvram is always configured and does not need
ian@0 713 to be selected.
ian@0 714
ian@0 715 To compile this driver as a module, choose M here: the
ian@0 716 module will be called nvram.
ian@0 717
ian@0 718 config RTC
ian@0 719 tristate "Enhanced Real Time Clock Support"
ian@0 720 depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV && !ARM
ian@0 721 ---help---
ian@0 722 If you say Y here and create a character special file /dev/rtc with
ian@0 723 major number 10 and minor number 135 using mknod ("man mknod"), you
ian@0 724 will get access to the real time clock (or hardware clock) built
ian@0 725 into your computer.
ian@0 726
ian@0 727 Every PC has such a clock built in. It can be used to generate
ian@0 728 signals from as low as 1Hz up to 8192Hz, and can also be used
ian@0 729 as a 24 hour alarm. It reports status information via the file
ian@0 730 /proc/driver/rtc and its behaviour is set by various ioctls on
ian@0 731 /dev/rtc.
ian@0 732
ian@0 733 If you run Linux on a multiprocessor machine and said Y to
ian@0 734 "Symmetric Multi Processing" above, you should say Y here to read
ian@0 735 and set the RTC in an SMP compatible fashion.
ian@0 736
ian@0 737 If you think you have a use for such a device (such as periodic data
ian@0 738 sampling), then say Y here, and read <file:Documentation/rtc.txt>
ian@0 739 for details.
ian@0 740
ian@0 741 To compile this driver as a module, choose M here: the
ian@0 742 module will be called rtc.
ian@0 743
ian@0 744 config SGI_DS1286
ian@0 745 tristate "SGI DS1286 RTC support"
ian@0 746 depends on SGI_IP22
ian@0 747 help
ian@0 748 If you say Y here and create a character special file /dev/rtc with
ian@0 749 major number 10 and minor number 135 using mknod ("man mknod"), you
ian@0 750 will get access to the real time clock built into your computer.
ian@0 751 Every SGI has such a clock built in. It reports status information
ian@0 752 via the file /proc/rtc and its behaviour is set by various ioctls on
ian@0 753 /dev/rtc.
ian@0 754
ian@0 755 config SGI_IP27_RTC
ian@0 756 bool "SGI M48T35 RTC support"
ian@0 757 depends on SGI_IP27
ian@0 758 help
ian@0 759 If you say Y here and create a character special file /dev/rtc with
ian@0 760 major number 10 and minor number 135 using mknod ("man mknod"), you
ian@0 761 will get access to the real time clock built into your computer.
ian@0 762 Every SGI has such a clock built in. It reports status information
ian@0 763 via the file /proc/rtc and its behaviour is set by various ioctls on
ian@0 764 /dev/rtc.
ian@0 765
ian@0 766 config GEN_RTC
ian@0 767 tristate "Generic /dev/rtc emulation"
ian@0 768 depends on RTC!=y && !IA64 && !ARM && !M32R && !SPARC && !FRV
ian@0 769 ---help---
ian@0 770 If you say Y here and create a character special file /dev/rtc with
ian@0 771 major number 10 and minor number 135 using mknod ("man mknod"), you
ian@0 772 will get access to the real time clock (or hardware clock) built
ian@0 773 into your computer.
ian@0 774
ian@0 775 It reports status information via the file /proc/driver/rtc and its
ian@0 776 behaviour is set by various ioctls on /dev/rtc. If you enable the
ian@0 777 "extended RTC operation" below it will also provide an emulation
ian@0 778 for RTC_UIE which is required by some programs and may improve
ian@0 779 precision in some cases.
ian@0 780
ian@0 781 To compile this driver as a module, choose M here: the
ian@0 782 module will be called genrtc.
ian@0 783
ian@0 784 config GEN_RTC_X
ian@0 785 bool "Extended RTC operation"
ian@0 786 depends on GEN_RTC
ian@0 787 help
ian@0 788 Provides an emulation for RTC_UIE which is required by some programs
ian@0 789 and may improve precision of the generic RTC support in some cases.
ian@0 790
ian@0 791 config EFI_RTC
ian@0 792 bool "EFI Real Time Clock Services"
ian@0 793 depends on IA64
ian@0 794
ian@0 795 config DS1302
ian@0 796 tristate "DS1302 RTC support"
ian@0 797 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
ian@0 798 help
ian@0 799 If you say Y here and create a character special file /dev/rtc with
ian@0 800 major number 121 and minor number 0 using mknod ("man mknod"), you
ian@0 801 will get access to the real time clock (or hardware clock) built
ian@0 802 into your computer.
ian@0 803
ian@0 804 config S3C2410_RTC
ian@0 805 bool "S3C2410 RTC Driver"
ian@0 806 depends on ARCH_S3C2410
ian@0 807 help
ian@0 808 RTC (Realtime Clock) driver for the clock inbuilt into the
ian@0 809 Samsung S3C2410. This can provide periodic interrupt rates
ian@0 810 from 1Hz to 64Hz for user programs, and wakeup from Alarm.
ian@0 811
ian@0 812 config COBALT_LCD
ian@0 813 bool "Support for Cobalt LCD"
ian@0 814 depends on MIPS_COBALT
ian@0 815 help
ian@0 816 This option enables support for the LCD display and buttons found
ian@0 817 on Cobalt systems through a misc device.
ian@0 818
ian@0 819 config DTLK
ian@0 820 tristate "Double Talk PC internal speech card support"
ian@0 821 help
ian@0 822 This driver is for the DoubleTalk PC, a speech synthesizer
ian@0 823 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
ian@0 824 called the `internal DoubleTalk'.
ian@0 825
ian@0 826 To compile this driver as a module, choose M here: the
ian@0 827 module will be called dtlk.
ian@0 828
ian@0 829 config R3964
ian@0 830 tristate "Siemens R3964 line discipline"
ian@0 831 ---help---
ian@0 832 This driver allows synchronous communication with devices using the
ian@0 833 Siemens R3964 packet protocol. Unless you are dealing with special
ian@0 834 hardware like PLCs, you are unlikely to need this.
ian@0 835
ian@0 836 To compile this driver as a module, choose M here: the
ian@0 837 module will be called n_r3964.
ian@0 838
ian@0 839 If unsure, say N.
ian@0 840
ian@0 841 config APPLICOM
ian@0 842 tristate "Applicom intelligent fieldbus card support"
ian@0 843 depends on PCI
ian@0 844 ---help---
ian@0 845 This driver provides the kernel-side support for the intelligent
ian@0 846 fieldbus cards made by Applicom International. More information
ian@0 847 about these cards can be found on the WWW at the address
ian@0 848 <http://www.applicom-int.com/>, or by email from David Woodhouse
ian@0 849 <dwmw2@infradead.org>.
ian@0 850
ian@0 851 To compile this driver as a module, choose M here: the
ian@0 852 module will be called applicom.
ian@0 853
ian@0 854 If unsure, say N.
ian@0 855
ian@0 856 config SONYPI
ian@0 857 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
ian@0 858 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
ian@0 859 ---help---
ian@0 860 This driver enables access to the Sony Programmable I/O Control
ian@0 861 Device which can be found in many (all ?) Sony Vaio laptops.
ian@0 862
ian@0 863 If you have one of those laptops, read
ian@0 864 <file:Documentation/sonypi.txt>, and say Y or M here.
ian@0 865
ian@0 866 To compile this driver as a module, choose M here: the
ian@0 867 module will be called sonypi.
ian@0 868
ian@0 869 config TANBAC_TB0219
ian@0 870 tristate "TANBAC TB0219 base board support"
ian@0 871 depends TANBAC_TB022X
ian@0 872 select GPIO_VR41XX
ian@0 873
ian@0 874 menu "Ftape, the floppy tape device driver"
ian@0 875
ian@0 876 config FTAPE
ian@0 877 tristate "Ftape (QIC-80/Travan) support"
ian@0 878 depends on BROKEN_ON_SMP && (ALPHA || X86)
ian@0 879 ---help---
ian@0 880 If you have a tape drive that is connected to your floppy
ian@0 881 controller, say Y here.
ian@0 882
ian@0 883 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
ian@0 884 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
ian@0 885 controller of their own. These drives (and their companion
ian@0 886 controllers) are also supported if you say Y here.
ian@0 887
ian@0 888 If you have a special controller (such as the CMS FC-10, FC-20,
ian@0 889 Mountain Mach-II, or any controller that is based on the Intel 82078
ian@0 890 FDC like the high speed controllers by Seagate and Exabyte and
ian@0 891 Iomega's "Ditto Dash") you must configure it by selecting the
ian@0 892 appropriate entries from the "Floppy tape controllers" sub-menu
ian@0 893 below and possibly modify the default values for the IRQ and DMA
ian@0 894 channel and the IO base in ftape's configuration menu.
ian@0 895
ian@0 896 If you want to use your floppy tape drive on a PCI-bus based system,
ian@0 897 please read the file <file:drivers/char/ftape/README.PCI>.
ian@0 898
ian@0 899 The ftape kernel driver is also available as a runtime loadable
ian@0 900 module. To compile this driver as a module, choose M here: the
ian@0 901 module will be called ftape.
ian@0 902
ian@0 903 source "drivers/char/ftape/Kconfig"
ian@0 904
ian@0 905 endmenu
ian@0 906
ian@0 907 source "drivers/char/agp/Kconfig"
ian@0 908
ian@0 909 source "drivers/char/drm/Kconfig"
ian@0 910
ian@0 911 source "drivers/char/pcmcia/Kconfig"
ian@0 912
ian@0 913 config MWAVE
ian@0 914 tristate "ACP Modem (Mwave) support"
ian@0 915 depends on X86
ian@0 916 select SERIAL_8250
ian@0 917 ---help---
ian@0 918 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
ian@0 919 kernel driver and a user level application. Together these components
ian@0 920 support direct attachment to public switched telephone networks (PSTNs)
ian@0 921 and support selected world wide countries.
ian@0 922
ian@0 923 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
ian@0 924 600, and 770 that include on board ACP modem hardware.
ian@0 925
ian@0 926 The modem also supports the standard communications port interface
ian@0 927 (ttySx) and is compatible with the Hayes AT Command Set.
ian@0 928
ian@0 929 The user level application needed to use this driver can be found at
ian@0 930 the IBM Linux Technology Center (LTC) web site:
ian@0 931 <http://www.ibm.com/linux/ltc/>.
ian@0 932
ian@0 933 If you own one of the above IBM Thinkpads which has the Mwave chipset
ian@0 934 in it, say Y.
ian@0 935
ian@0 936 To compile this driver as a module, choose M here: the
ian@0 937 module will be called mwave.
ian@0 938
ian@0 939 config SCx200_GPIO
ian@0 940 tristate "NatSemi SCx200 GPIO Support"
ian@0 941 depends on SCx200
ian@0 942 select NSC_GPIO
ian@0 943 help
ian@0 944 Give userspace access to the GPIO pins on the National
ian@0 945 Semiconductor SCx200 processors.
ian@0 946
ian@0 947 If compiled as a module, it will be called scx200_gpio.
ian@0 948
ian@0 949 config PC8736x_GPIO
ian@0 950 tristate "NatSemi PC8736x GPIO Support"
ian@0 951 depends on X86
ian@0 952 default SCx200_GPIO # mostly N
ian@0 953 select NSC_GPIO # needed for support routines
ian@0 954 help
ian@0 955 Give userspace access to the GPIO pins on the National
ian@0 956 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
ian@0 957 has multiple functional units, inc several managed by
ian@0 958 hwmon/pc87360 driver. Tested with PC-87366
ian@0 959
ian@0 960 If compiled as a module, it will be called pc8736x_gpio.
ian@0 961
ian@0 962 config NSC_GPIO
ian@0 963 tristate "NatSemi Base GPIO Support"
ian@0 964 depends on X86_32
ian@0 965 # selected by SCx200_GPIO and PC8736x_GPIO
ian@0 966 # what about 2 selectors differing: m != y
ian@0 967 help
ian@0 968 Common support used (and needed) by scx200_gpio and
ian@0 969 pc8736x_gpio drivers. If those drivers are built as
ian@0 970 modules, this one will be too, named nsc_gpio
ian@0 971
ian@0 972 config CS5535_GPIO
ian@0 973 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
ian@0 974 depends on X86_32
ian@0 975 help
ian@0 976 Give userspace access to the GPIO pins on the AMD CS5535 and
ian@0 977 CS5536 Geode companion devices.
ian@0 978
ian@0 979 If compiled as a module, it will be called cs5535_gpio.
ian@0 980
ian@0 981 config GPIO_VR41XX
ian@0 982 tristate "NEC VR4100 series General-purpose I/O Unit support"
ian@0 983 depends on CPU_VR41XX
ian@0 984
ian@0 985 config RAW_DRIVER
ian@0 986 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
ian@0 987 help
ian@0 988 The raw driver permits block devices to be bound to /dev/raw/rawN.
ian@0 989 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
ian@0 990 See the raw(8) manpage for more details.
ian@0 991
ian@0 992 The raw driver is deprecated and will be removed soon.
ian@0 993 Applications should simply open the device (eg /dev/hda1)
ian@0 994 with the O_DIRECT flag.
ian@0 995
ian@0 996 config MAX_RAW_DEVS
ian@0 997 int "Maximum number of RAW devices to support (1-8192)"
ian@0 998 depends on RAW_DRIVER
ian@0 999 default "256"
ian@0 1000 help
ian@0 1001 The maximum number of RAW devices that are supported.
ian@0 1002 Default is 256. Increase this number in case you need lots of
ian@0 1003 raw devices.
ian@0 1004
ian@0 1005 config HPET
ian@0 1006 bool "HPET - High Precision Event Timer" if (X86 || IA64)
ian@0 1007 default n
keir@638 1008 depends on ACPI && !XEN
ian@0 1009 help
ian@0 1010 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
ian@0 1011 open selects one of the timers supported by the HPET. The timers are
ian@0 1012 non-periodioc and/or periodic.
ian@0 1013
ian@0 1014 config HPET_RTC_IRQ
ian@0 1015 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
ian@0 1016 default n
ian@0 1017 depends on HPET
ian@0 1018 help
ian@0 1019 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
ian@0 1020 is assumed the platform called hpet_alloc with the RTC IRQ values for
ian@0 1021 the HPET timers.
ian@0 1022
ian@0 1023 config HPET_MMAP
ian@0 1024 bool "Allow mmap of HPET"
ian@0 1025 default y
ian@0 1026 depends on HPET
ian@0 1027 help
ian@0 1028 If you say Y here, user applications will be able to mmap
ian@0 1029 the HPET registers.
ian@0 1030
ian@0 1031 In some hardware implementations, the page containing HPET
ian@0 1032 registers may also contain other things that shouldn't be
ian@0 1033 exposed to the user. If this applies to your hardware,
ian@0 1034 say N here.
ian@0 1035
ian@0 1036 config HANGCHECK_TIMER
ian@0 1037 tristate "Hangcheck timer"
ian@0 1038 depends on X86 || IA64 || PPC64
ian@0 1039 help
ian@0 1040 The hangcheck-timer module detects when the system has gone
ian@0 1041 out to lunch past a certain margin. It can reboot the system
ian@0 1042 or merely print a warning.
ian@0 1043
ian@0 1044 config MMTIMER
ian@0 1045 tristate "MMTIMER Memory mapped RTC for SGI Altix"
ian@0 1046 depends on IA64_GENERIC || IA64_SGI_SN2
ian@0 1047 default y
ian@0 1048 help
ian@0 1049 The mmtimer device allows direct userspace access to the
ian@0 1050 Altix system timer.
ian@0 1051
ian@0 1052 source "drivers/char/tpm/Kconfig"
ian@0 1053
ian@0 1054 config TELCLOCK
ian@0 1055 tristate "Telecom clock driver for MPBL0010 ATCA SBC"
ian@0 1056 depends on EXPERIMENTAL
ian@0 1057 default n
ian@0 1058 help
ian@0 1059 The telecom clock device is specific to the MPBL0010 ATCA computer and
ian@0 1060 allows direct userspace access to the configuration of the telecom clock
ian@0 1061 configuration settings. This device is used for hardware synchronization
ian@0 1062 across the ATCA backplane fabric. Upon loading, the driver exports a
ian@0 1063 sysfs directory, /sys/devices/platform/telco_clock, with a number of
ian@0 1064 files for controlling the behavior of this hardware.
ian@0 1065
ian@0 1066 endmenu
ian@0 1067