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