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