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