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