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