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