2 # Character device configuration
5 menu "Character devices"
8 bool "Virtual terminal" if EMBEDDED
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>.
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.
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.
36 If unsure, say Y, or else you won't be able to do much with your new
37 shiny Linux system :-)
40 bool "Virtual console is Unicode by default"
44 If you say Y here, the virtual terminal will be in UTF-8 by default,
45 and the keyboard will run in unicode mode.
47 If you say N here, the virtual terminal will not be in UTF-8 by
48 default, and the keyboard will run in XLATE mode.
50 This can also be changed by passing 'default_utf8=<0|1>' on the
53 Historically, the kernel has defaulted to non-UTF8 and XLATE mode.
54 If unsure, say N here.
57 bool "Support for console on virtual terminal" if EMBEDDED
61 The system console is the device which receives all kernel messages
62 and warnings and which allows logins in single user mode. If you
63 answer Y here, a virtual terminal (the device used to interact with
64 a physical terminal) can be used as system console. This is the most
65 common mode of operations, so you should say Y here unless you want
66 the kernel messages be output only to a serial port (in which case
67 you should say Y to "Console on serial port", below).
69 If you do say Y here, by default the currently visible virtual
70 terminal (/dev/tty0) will be used as system console. You can change
71 that with a kernel command line option such as "console=tty3" which
72 would use the third virtual terminal as system console. (Try "man
73 bootparam" or see the documentation of your boot loader (lilo or
74 loadlin) about how to pass options to the kernel at boot time.)
80 depends on VT && !S390 && !UML
83 config VT_HW_CONSOLE_BINDING
84 bool "Support for binding and unbinding console drivers"
88 The virtual terminal is the device that interacts with the physical
89 terminal through console drivers. On these systems, at least one
90 console driver is loaded. In other configurations, additional console
91 drivers may be enabled, such as the framebuffer console. If more than
92 1 console driver is enabled, setting this to 'y' will allow you to
93 select the console driver that will serve as the backend for the
96 See <file:Documentation/console/console.txt> for more
97 information. For framebuffer console users, please refer to
98 <file:Documentation/fb/fbcon.txt>.
100 config SERIAL_NONSTANDARD
101 bool "Non-standard serial port support"
104 Say Y here if you have any non-standard serial boards -- boards
105 which aren't supported using the standard "dumb" serial driver.
106 This includes intelligent serial boards such as Cyclades,
107 Digiboards, etc. These are usually used for systems that need many
108 serial ports because they serve many terminals or dial-in
111 Note that the answer to this question won't directly affect the
112 kernel: saying N will just cause the configurator to skip all
113 the questions about non-standard serial boards.
115 Most people can say N here.
118 tristate "Computone IntelliPort Plus serial support"
119 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
121 This driver supports the entire family of Intelliport II/Plus
122 controllers with the exception of the MicroChannel controllers and
123 products previous to the Intelliport II. These are multiport cards,
124 which give you many serial ports. You would need something like this
125 to connect more than two modems to your Linux box, for instance in
126 order to become a dial-in server. If you have a card like that, say
127 Y here and read <file:Documentation/computone.txt>.
129 To compile this driver as modules, choose M here: the
130 modules will be called ip2 and ip2main.
133 tristate "Comtrol RocketPort support"
134 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
136 This driver supports Comtrol RocketPort and RocketModem PCI boards.
137 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
138 modems. For information about the RocketPort/RocketModem boards
139 and this driver read <file:Documentation/rocket.txt>.
141 To compile this driver as a module, choose M here: the
142 module will be called rocket.
144 If you want to compile this driver into the kernel, say Y here. If
145 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
148 tristate "Cyclades async mux support"
149 depends on SERIAL_NONSTANDARD && (PCI || ISA)
152 This driver supports Cyclades Z and Y multiserial boards.
153 You would need something like this to connect more than two modems to
154 your Linux box, for instance in order to become a dial-in server.
156 For information about the Cyclades-Z card, read
157 <file:drivers/char/README.cycladesZ>.
159 To compile this driver as a module, choose M here: the
160 module will be called cyclades.
162 If you haven't heard about it, it's safe to say N.
165 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
166 depends on EXPERIMENTAL && CYCLADES
168 The Cyclades-Z family of multiport cards allows 2 (two) driver op
169 modes: polling and interrupt. In polling mode, the driver will check
170 the status of the Cyclades-Z ports every certain amount of time
171 (which is called polling cycle and is configurable). In interrupt
172 mode, it will use an interrupt line (IRQ) in order to check the
173 status of the Cyclades-Z ports. The default op mode is polling. If
177 tristate "Digiboard Intelligent Async Support"
178 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
180 This is a driver for Digi International's Xx, Xeve, and Xem series
181 of cards which provide multiple serial ports. You would need
182 something like this to connect more than two modems to your Linux
183 box, for instance in order to become a dial-in server. This driver
184 supports the original PC (ISA) boards as well as PCI, and EISA. If
185 you have a card like this, say Y here and read the file
186 <file:Documentation/digiepca.txt>.
188 To compile this driver as a module, choose M here: the
189 module will be called epca.
192 tristate "Hayes ESP serial port support"
193 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
195 This is a driver which supports Hayes ESP serial ports. Both single
196 port cards and multiport cards are supported. Make sure to read
197 <file:Documentation/hayes-esp.txt>.
199 To compile this driver as a module, choose M here: the
200 module will be called esp.
205 tristate "Moxa Intellio support"
206 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
208 Say Y here if you have a Moxa Intellio multiport serial card.
210 To compile this driver as a module, choose M here: the
211 module will be called moxa.
214 tristate "Moxa SmartIO support (OBSOLETE)"
215 depends on SERIAL_NONSTANDARD
217 Say Y here if you have a Moxa SmartIO multiport serial card.
219 This driver can also be built as a module ( = code which can be
220 inserted in and removed from the running kernel whenever you want).
221 The module will be called mxser. If you want to do that, say M
224 config MOXA_SMARTIO_NEW
225 tristate "Moxa SmartIO support v. 2.0"
226 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
228 Say Y here if you have a Moxa SmartIO multiport serial card and/or
229 want to help develop a new version of this driver.
231 This is upgraded (1.9.1) driver from original Moxa drivers with
232 changes finally resulting in PCI probing.
234 This driver can also be built as a module. The module will be called
235 mxser_new. If you want to do that, say M here.
238 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
239 depends on SERIAL_NONSTANDARD && PCI
242 This is a driver for the Multi-Tech cards which provide several
243 serial ports. The driver is experimental and can currently only be
244 built as a module. The module will be called isicom.
245 If you want to do that, choose M here.
248 tristate "Microgate SyncLink card support"
249 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
251 Provides support for the SyncLink ISA and PCI multiprotocol serial
252 adapters. These adapters support asynchronous and HDLC bit
253 synchronous communication up to 10Mbps (PCI adapter).
255 This driver can only be built as a module ( = code which can be
256 inserted in and removed from the running kernel whenever you want).
257 The module will be called synclink. If you want to do that, say M
261 tristate "SyncLink Multiport support"
262 depends on SERIAL_NONSTANDARD && PCI
264 Enable support for the SyncLink Multiport (2 or 4 ports)
265 serial adapter, running asynchronous and HDLC communications up
266 to 2.048Mbps. Each ports is independently selectable for
267 RS-232, V.35, RS-449, RS-530, and X.21
269 This driver may be built as a module ( = code which can be
270 inserted in and removed from the running kernel whenever you want).
271 The module will be called synclinkmp. If you want to do that, say M
275 tristate "SyncLink GT/AC support"
276 depends on SERIAL_NONSTANDARD && PCI
278 Support for SyncLink GT and SyncLink AC families of
279 synchronous and asynchronous serial adapters
280 manufactured by Microgate Systems, Ltd. (www.microgate.com)
283 tristate "HDLC line discipline support"
284 depends on SERIAL_NONSTANDARD
286 Allows synchronous HDLC communications with tty device drivers that
287 support synchronous HDLC such as the Microgate SyncLink adapter.
289 This driver can only be built as a module ( = code which can be
290 inserted in and removed from the running kernel whenever you want).
291 The module will be called n_hdlc. If you want to do that, say M
295 tristate "SDL RISCom/8 card support"
296 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
298 This is a driver for the SDL Communications RISCom/8 multiport card,
299 which gives you many serial ports. You would need something like
300 this to connect more than two modems to your Linux box, for instance
301 in order to become a dial-in server. If you have a card like that,
302 say Y here and read the file <file:Documentation/riscom8.txt>.
304 Also it's possible to say M here and compile this driver as kernel
305 loadable module; the module will be called riscom8.
308 tristate "Specialix IO8+ card support"
309 depends on SERIAL_NONSTANDARD
311 This is a driver for the Specialix IO8+ multiport card (both the
312 ISA and the PCI version) which gives you many serial ports. You
313 would need something like this to connect more than two modems to
314 your Linux box, for instance in order to become a dial-in server.
316 If you have a card like that, say Y here and read the file
317 <file:Documentation/specialix.txt>. Also it's possible to say M here
318 and compile this driver as kernel loadable module which will be
321 config SPECIALIX_RTSCTS
322 bool "Specialix DTR/RTS pin is RTS"
325 The Specialix IO8+ card can only support either RTS or DTR. If you
326 say N here, the driver will use the pin as "DTR" when the tty is in
327 software handshake mode. If you say Y here or hardware handshake is
328 on, it will always be RTS. Read the file
329 <file:Documentation/specialix.txt> for more information.
332 tristate "Specialix SX (and SI) card support"
333 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
335 This is a driver for the SX and SI multiport serial cards.
336 Please read the file <file:Documentation/sx.txt> for details.
338 This driver can only be built as a module ( = code which can be
339 inserted in and removed from the running kernel whenever you want).
340 The module will be called sx. If you want to do that, say M here.
343 tristate "Specialix RIO system support"
344 depends on SERIAL_NONSTANDARD
346 This is a driver for the Specialix RIO, a smart serial card which
347 drives an outboard box that can support up to 128 ports. Product
348 information is at <http://www.perle.com/support/documentation.html#multiport>.
349 There are both ISA and PCI versions.
352 bool "Support really old RIO/PCI cards"
355 Older RIO PCI cards need some initialization-time configuration to
356 determine the IRQ and some control addresses. If you have a RIO and
357 this doesn't seem to work, try setting this to Y.
360 bool "Stallion multiport serial support"
361 depends on SERIAL_NONSTANDARD
363 Stallion cards give you many serial ports. You would need something
364 like this to connect more than two modems to your Linux box, for
365 instance in order to become a dial-in server. If you say Y here,
366 you will be asked for your specific card model in the next
367 questions. Make sure to read <file:Documentation/stallion.txt> in
368 this case. If you have never heard about all this, it's safe to
372 tristate "Stallion EasyIO or EC8/32 support"
373 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
375 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
376 card, then this is for you; say Y. Make sure to read
377 <file:Documentation/stallion.txt>.
379 To compile this driver as a module, choose M here: the
380 module will be called stallion.
383 tristate "Stallion EC8/64, ONboard, Brumby support"
384 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
386 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
387 serial multiport card, say Y here. Make sure to read
388 <file:Documentation/stallion.txt>.
390 To compile this driver as a module, choose M here: the
391 module will be called istallion.
394 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
395 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
397 This option supports the 2232 7-port serial card shipped with the
398 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
399 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
400 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
401 ports were connected with 8 pin DIN connectors on the card bracket,
402 for which 8 pin to DB25 adapters were supplied. The card also had
403 jumpers internally to toggle various pinning configurations.
405 This driver can be built as a module; but then "generic_serial"
406 will also be built as a module. This has to be loaded before
407 "ser_a2232". If you want to do this, answer M here.
410 bool "SGI Altix system controller communication support"
411 depends on (IA64_SGI_SN2 || IA64_GENERIC)
413 If you have an SGI Altix and you want to enable system
414 controller communication from user space (you want this!),
415 say Y. Otherwise, say N.
418 bool "SGI TIO CX driver support"
419 depends on (IA64_SGI_SN2 || IA64_GENERIC)
421 If you have an SGI Altix and you have fpga devices attached
422 to your TIO, say Y here, otherwise say N.
425 tristate "SGI FPGA Core Services driver support"
428 If you have an SGI Altix with an attached SABrick
429 say Y or M here, otherwise say N.
431 source "drivers/serial/Kconfig"
434 bool "Unix98 PTY support" if EMBEDDED
437 A pseudo terminal (PTY) is a software device consisting of two
438 halves: a master and a slave. The slave device behaves identical to
439 a physical terminal; the master device is used by a process to
440 read data from and write data to the slave, thereby emulating a
441 terminal. Typical programs for the master side are telnet servers
444 Linux has traditionally used the BSD-like names /dev/ptyxx for
445 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
446 has a number of problems. The GNU C library glibc 2.1 and later,
447 however, supports the Unix98 naming standard: in order to acquire a
448 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
449 terminal is then made available to the process and the pseudo
450 terminal slave can be accessed as /dev/pts/<number>. What was
451 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
453 All modern Linux systems use the Unix98 ptys. Say Y unless
454 you're on an embedded system and want to conserve memory.
457 bool "Legacy (BSD) PTY support"
460 A pseudo terminal (PTY) is a software device consisting of two
461 halves: a master and a slave. The slave device behaves identical to
462 a physical terminal; the master device is used by a process to
463 read data from and write data to the slave, thereby emulating a
464 terminal. Typical programs for the master side are telnet servers
467 Linux has traditionally used the BSD-like names /dev/ptyxx
468 for masters and /dev/ttyxx for slaves of pseudo
469 terminals. This scheme has a number of problems, including
470 security. This option enables these legacy devices; on most
471 systems, it is safe to say N.
474 config LEGACY_PTY_COUNT
475 int "Maximum number of legacy PTY in use"
476 depends on LEGACY_PTYS
480 The maximum number of legacy PTYs that can be used at any one time.
481 The default is 256, and should be more than enough. Embedded
482 systems may want to reduce this to save memory.
484 When not in use, each legacy PTY occupies 12 bytes on 32-bit
485 architectures and 24 bytes on 64-bit architectures.
488 tristate 'Total Impact briQ front panel driver'
491 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
492 tristate led and two switches. It is the size of a CDROM drive.
494 If you have such one and want anything showing on the VFD then you
497 To compile this driver as a module, choose M here: the
498 module will be called briq_panel.
500 It's safe to say N here.
503 tristate "Parallel printer support"
506 If you intend to attach a printer to the parallel port of your Linux
507 box (as opposed to using a serial printer; if the connector at the
508 printer has 9 or 25 holes ["female"], then it's serial), say Y.
509 Also read the Printing-HOWTO, available from
510 <http://www.tldp.org/docs.html#howto>.
512 It is possible to share one parallel port among several devices
513 (e.g. printer and ZIP drive) and it is safe to compile the
514 corresponding drivers into the kernel.
516 To compile this driver as a module, choose M here and read
517 <file:Documentation/parport.txt>. The module will be called lp.
519 If you have several parallel ports, you can specify which ports to
520 use with the "lp" kernel command line option. (Try "man bootparam"
521 or see the documentation of your boot loader (lilo or loadlin) about
522 how to pass options to the kernel at boot time.) The syntax of the
523 "lp" command line option can be found in <file:drivers/char/lp.c>.
525 If you have more than 8 printers, you need to increase the LP_NO
526 macro in lp.c and the PARPORT_MAX macro in parport.h.
529 bool "Support for console on line printer"
532 If you want kernel messages to be printed out as they occur, you
533 can have a console on the printer. This option adds support for
534 doing that; to actually get it to happen you need to pass the
535 option "console=lp0" to the kernel at boot time.
537 If the printer is out of paper (or off, or unplugged, or too
538 busy..) the kernel will stall until the printer is ready again.
539 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
540 can make the kernel continue when this happens,
541 but it'll lose the kernel messages.
546 tristate "Support for user-space parallel port device drivers"
549 Saying Y to this adds support for /dev/parport device nodes. This
550 is needed for programs that want portable access to the parallel
551 port, for instance deviceid (which displays Plug-and-Play device
554 This is the parallel port equivalent of SCSI generic support (sg).
555 It is safe to say N to this -- it is not needed for normal printing
556 or parallel port CD-ROM/disk support.
558 To compile this driver as a module, choose M here: the
559 module will be called ppdev.
564 tristate "Texas Instruments parallel link cable support"
567 If you own a Texas Instruments graphing calculator and use a
568 parallel link cable, then you might be interested in this driver.
570 If you enable this driver, you will be able to communicate with
571 your calculator through a set of device nodes under /dev. The
572 main advantage of this driver is that you don't have to be root
573 to use this precise link cable (depending on the permissions on
574 the device nodes, though).
576 To compile this driver as a module, choose M here: the
577 module will be called tipar.
579 If you don't know what a parallel link cable is or what a Texas
580 Instruments graphing calculator is, then you probably don't need this
588 Generic "hypervisor virtual console" infrastructure for various
589 hypervisors (pSeries, iSeries, Xen, lguest).
590 It will automatically be selected if one of the back-end console drivers
595 bool "pSeries Hypervisor Virtual Console support"
596 depends on PPC_PSERIES
599 pSeries machines when partitioned support a hypervisor virtual
600 console. This driver allows each pSeries partition to have a console
601 which is accessed via the HMC.
604 bool "iSeries Hypervisor Virtual Console support"
605 depends on PPC_ISERIES
609 iSeries machines support a hypervisor virtual console.
612 bool "IBM RTAS Console support"
616 IBM Console device driver which makes use of RTAS
619 bool "Toshiba's Beat Hypervisor Console support"
620 depends on PPC_CELLEB
623 Toshiba's Cell Reference Set Beat Console device driver
626 bool "Xen Hypervisor Console support"
631 Xen virtual console device driver
634 tristate "IBM Hypervisor Virtual Console Server support"
635 depends on PPC_PSERIES
637 Partitionable IBM Power5 ppc64 machines allow hosting of
638 firmware virtual consoles from one Linux partition by
639 another Linux partition. This driver allows console data
640 from Linux partitions to be accessed through TTY device
641 interfaces in the device tree of a Linux partition running
644 To compile this driver as a module, choose M here: the
645 module will be called hvcs.ko. Additionally, this module
646 will depend on arch specific APIs exported from hvcserver.ko
647 which will also be compiled when this driver is built as a
650 source "drivers/char/ipmi/Kconfig"
653 tristate "NetWinder thermometer support"
654 depends on ARCH_NETWINDER
656 Say Y here to include support for the thermal management hardware
657 found in the NetWinder. This driver allows the user to control the
658 temperature set points and to read the current temperature.
660 It is also possible to say M here to build it as a module (ds1620)
661 It is recommended to be used on a NetWinder, but it is not a
665 tristate "NetWinder Button"
666 depends on ARCH_NETWINDER
668 If you say Y here and create a character device node /dev/nwbutton
669 with major and minor numbers 10 and 158 ("man mknod"), then every
670 time the orange button is pressed a number of times, the number of
671 times the button was pressed will be written to that device.
673 This is most useful for applications, as yet unwritten, which
674 perform actions based on how many times the button is pressed in a
677 Do not hold the button down for too long, as the driver does not
678 alter the behaviour of the hardware reset circuitry attached to the
679 button; it will still execute a hard reset if the button is held
680 down for longer than approximately five seconds.
682 To compile this driver as a module, choose M here: the
683 module will be called nwbutton.
685 Most people will answer Y to this question and "Reboot Using Button"
686 below to be able to initiate a system shutdown from the button.
688 config NWBUTTON_REBOOT
689 bool "Reboot Using Button"
692 If you say Y here, then you will be able to initiate a system
693 shutdown and reboot by pressing the orange button a number of times.
694 The number of presses to initiate the shutdown is two by default,
695 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
696 in nwbutton.h and recompiling the driver or, if you compile the
697 driver as a module, you can specify the number of presses at load
698 time with "insmod button reboot_count=<something>".
701 tristate "NetWinder flash support"
702 depends on ARCH_NETWINDER
704 If you say Y here and create a character device /dev/flash with
705 major 10 and minor 160 you can manipulate the flash ROM containing
706 the NetWinder firmware. Be careful as accidentally overwriting the
707 flash contents can render your computer unbootable. On no account
708 allow random users access to this device. :-)
710 To compile this driver as a module, choose M here: the
711 module will be called nwflash.
713 If you're not sure, say N.
715 source "drivers/char/hw_random/Kconfig"
718 tristate "/dev/nvram support"
719 depends on ATARI || X86 || ARM || GENERIC_NVRAM
721 If you say Y here and create a character special file /dev/nvram
722 with major number 10 and minor number 144 using mknod ("man mknod"),
723 you get read and write access to the extra bytes of non-volatile
724 memory in the real time clock (RTC), which is contained in every PC
725 and most Ataris. The actual number of bytes varies, depending on the
726 nvram in the system, but is usually 114 (128-14 for the RTC).
728 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
729 on Ataris. /dev/nvram may be used to view settings there, or to
730 change them (with some utility). It could also be used to frequently
731 save a few bits of very important data that may not be lost over
732 power-off and for which writing to disk is too insecure. Note
733 however that most NVRAM space in a PC belongs to the BIOS and you
734 should NEVER idly tamper with it. See Ralf Brown's interrupt list
735 for a guide to the use of CMOS bytes by your BIOS.
737 On Atari machines, /dev/nvram is always configured and does not need
740 To compile this driver as a module, choose M here: the
741 module will be called nvram.
744 tristate "Enhanced Real Time Clock Support"
745 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV && !ARM && !SUPERH && !S390
747 If you say Y here and create a character special file /dev/rtc with
748 major number 10 and minor number 135 using mknod ("man mknod"), you
749 will get access to the real time clock (or hardware clock) built
752 Every PC has such a clock built in. It can be used to generate
753 signals from as low as 1Hz up to 8192Hz, and can also be used
754 as a 24 hour alarm. It reports status information via the file
755 /proc/driver/rtc and its behaviour is set by various ioctls on
758 If you run Linux on a multiprocessor machine and said Y to
759 "Symmetric Multi Processing" above, you should say Y here to read
760 and set the RTC in an SMP compatible fashion.
762 If you think you have a use for such a device (such as periodic data
763 sampling), then say Y here, and read <file:Documentation/rtc.txt>
766 To compile this driver as a module, choose M here: the
767 module will be called rtc.
770 tristate "Enhanced Real Time Clock Support"
771 depends on SPARC32 && PCI
773 If you say Y here and create a character special file /dev/rtc with
774 major number 10 and minor number 135 using mknod ("man mknod"), you
775 will get access to the real time clock (or hardware clock) built
778 Every PC has such a clock built in. It can be used to generate
779 signals from as low as 1Hz up to 8192Hz, and can also be used
780 as a 24 hour alarm. It reports status information via the file
781 /proc/driver/rtc and its behaviour is set by various ioctls on
784 If you think you have a use for such a device (such as periodic data
785 sampling), then say Y here, and read <file:Documentation/rtc.txt>
788 To compile this driver as a module, choose M here: the
789 module will be called js-rtc.
792 tristate "SGI DS1286 RTC support"
795 If you say Y here and create a character special file /dev/rtc with
796 major number 10 and minor number 135 using mknod ("man mknod"), you
797 will get access to the real time clock built into your computer.
798 Every SGI has such a clock built in. It reports status information
799 via the file /proc/rtc and its behaviour is set by various ioctls on
803 bool "SGI M48T35 RTC support"
806 If you say Y here and create a character special file /dev/rtc with
807 major number 10 and minor number 135 using mknod ("man mknod"), you
808 will get access to the real time clock built into your computer.
809 Every SGI has such a clock built in. It reports status information
810 via the file /proc/rtc and its behaviour is set by various ioctls on
814 tristate "Generic /dev/rtc emulation"
815 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH
817 If you say Y here and create a character special file /dev/rtc with
818 major number 10 and minor number 135 using mknod ("man mknod"), you
819 will get access to the real time clock (or hardware clock) built
822 It reports status information via the file /proc/driver/rtc and its
823 behaviour is set by various ioctls on /dev/rtc. If you enable the
824 "extended RTC operation" below it will also provide an emulation
825 for RTC_UIE which is required by some programs and may improve
826 precision in some cases.
828 To compile this driver as a module, choose M here: the
829 module will be called genrtc.
832 bool "Extended RTC operation"
835 Provides an emulation for RTC_UIE which is required by some programs
836 and may improve precision of the generic RTC support in some cases.
839 bool "EFI Real Time Clock Services"
843 tristate "DS1302 RTC support"
844 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
846 If you say Y here and create a character special file /dev/rtc with
847 major number 121 and minor number 0 using mknod ("man mknod"), you
848 will get access to the real time clock (or hardware clock) built
852 bool "Support for Cobalt LCD"
853 depends on MIPS_COBALT
855 This option enables support for the LCD display and buttons found
856 on Cobalt systems through a misc device.
859 tristate "Double Talk PC internal speech card support"
862 This driver is for the DoubleTalk PC, a speech synthesizer
863 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
864 called the `internal DoubleTalk'.
866 To compile this driver as a module, choose M here: the
867 module will be called dtlk.
870 tristate "Siemens R3964 line discipline"
872 This driver allows synchronous communication with devices using the
873 Siemens R3964 packet protocol. Unless you are dealing with special
874 hardware like PLCs, you are unlikely to need this.
876 To compile this driver as a module, choose M here: the
877 module will be called n_r3964.
882 tristate "Applicom intelligent fieldbus card support"
885 This driver provides the kernel-side support for the intelligent
886 fieldbus cards made by Applicom International. More information
887 about these cards can be found on the WWW at the address
888 <http://www.applicom-int.com/>, or by email from David Woodhouse
889 <dwmw2@infradead.org>.
891 To compile this driver as a module, choose M here: the
892 module will be called applicom.
897 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
898 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
900 This driver enables access to the Sony Programmable I/O Control
901 Device which can be found in many (all ?) Sony Vaio laptops.
903 If you have one of those laptops, read
904 <file:Documentation/sonypi.txt>, and say Y or M here.
906 To compile this driver as a module, choose M here: the
907 module will be called sonypi.
910 tristate "TANBAC TB0219 GPIO support"
911 depends on TANBAC_TB022X
914 source "drivers/char/pcmcia/Kconfig"
917 tristate "ACP Modem (Mwave) support"
921 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
922 kernel driver and a user level application. Together these components
923 support direct attachment to public switched telephone networks (PSTNs)
924 and support selected world wide countries.
926 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
927 600, and 770 that include on board ACP modem hardware.
929 The modem also supports the standard communications port interface
930 (ttySx) and is compatible with the Hayes AT Command Set.
932 The user level application needed to use this driver can be found at
933 the IBM Linux Technology Center (LTC) web site:
934 <http://www.ibm.com/linux/ltc/>.
936 If you own one of the above IBM Thinkpads which has the Mwave chipset
939 To compile this driver as a module, choose M here: the
940 module will be called mwave.
943 tristate "NatSemi SCx200 GPIO Support"
947 Give userspace access to the GPIO pins on the National
948 Semiconductor SCx200 processors.
950 If compiled as a module, it will be called scx200_gpio.
953 tristate "NatSemi PC8736x GPIO Support"
955 default SCx200_GPIO # mostly N
956 select NSC_GPIO # needed for support routines
958 Give userspace access to the GPIO pins on the National
959 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
960 has multiple functional units, inc several managed by
961 hwmon/pc87360 driver. Tested with PC-87366
963 If compiled as a module, it will be called pc8736x_gpio.
966 tristate "NatSemi Base GPIO Support"
968 # selected by SCx200_GPIO and PC8736x_GPIO
969 # what about 2 selectors differing: m != y
971 Common support used (and needed) by scx200_gpio and
972 pc8736x_gpio drivers. If those drivers are built as
973 modules, this one will be too, named nsc_gpio
976 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
979 Give userspace access to the GPIO pins on the AMD CS5535 and
980 CS5536 Geode companion devices.
982 If compiled as a module, it will be called cs5535_gpio.
985 tristate "NEC VR4100 series General-purpose I/O Unit support"
986 depends on CPU_VR41XX
989 tristate "RAW driver (/dev/raw/rawN)"
992 The raw driver permits block devices to be bound to /dev/raw/rawN.
993 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
994 See the raw(8) manpage for more details.
996 Applications should preferably open the device (eg /dev/hda1)
997 with the O_DIRECT flag.
1000 int "Maximum number of RAW devices to support (1-8192)"
1001 depends on RAW_DRIVER
1004 The maximum number of RAW devices that are supported.
1005 Default is 256. Increase this number in case you need lots of
1009 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1013 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1014 open selects one of the timers supported by the HPET. The timers are
1015 non-periodic and/or periodic.
1018 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1022 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1023 is assumed the platform called hpet_alloc with the RTC IRQ values for
1027 bool "Allow mmap of HPET"
1031 If you say Y here, user applications will be able to mmap
1034 In some hardware implementations, the page containing HPET
1035 registers may also contain other things that shouldn't be
1036 exposed to the user. If this applies to your hardware,
1039 config HANGCHECK_TIMER
1040 tristate "Hangcheck timer"
1041 depends on X86 || IA64 || PPC64 || S390
1043 The hangcheck-timer module detects when the system has gone
1044 out to lunch past a certain margin. It can reboot the system
1045 or merely print a warning.
1048 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1049 depends on IA64_GENERIC || IA64_SGI_SN2
1052 The mmtimer device allows direct userspace access to the
1055 source "drivers/char/tpm/Kconfig"
1058 tristate "Telecom clock driver for ATCA SBC"
1059 depends on EXPERIMENTAL && X86
1062 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1063 ATCA computers and allows direct userspace access to the
1064 configuration of the telecom clock configuration settings. This
1065 device is used for hardware synchronization across the ATCA backplane
1066 fabric. Upon loading, the driver exports a sysfs directory,
1067 /sys/devices/platform/telco_clock, with a number of files for
1068 controlling the behavior of this hardware.
1073 depends on ISA || PCI
1076 source "drivers/s390/char/Kconfig"
git.openpandora.org / pandora-kernel.git / blob