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 "Support for console on virtual terminal" if EMBEDDED
44 The system console is the device which receives all kernel messages
45 and warnings and which allows logins in single user mode. If you
46 answer Y here, a virtual terminal (the device used to interact with
47 a physical terminal) can be used as system console. This is the most
48 common mode of operations, so you should say Y here unless you want
49 the kernel messages be output only to a serial port (in which case
50 you should say Y to "Console on serial port", below).
52 If you do say Y here, by default the currently visible virtual
53 terminal (/dev/tty0) will be used as system console. You can change
54 that with a kernel command line option such as "console=tty3" which
55 would use the third virtual terminal as system console. (Try "man
56 bootparam" or see the documentation of your boot loader (lilo or
57 loadlin) about how to pass options to the kernel at boot time.)
63 depends on VT && !S390 && !UML
66 config VT_HW_CONSOLE_BINDING
67 bool "Support for binding and unbinding console drivers"
71 The virtual terminal is the device that interacts with the physical
72 terminal through console drivers. On these systems, at least one
73 console driver is loaded. In other configurations, additional console
74 drivers may be enabled, such as the framebuffer console. If more than
75 1 console driver is enabled, setting this to 'y' will allow you to
76 select the console driver that will serve as the backend for the
79 See <file:Documentation/console/console.txt> for more
80 information. For framebuffer console users, please refer to
81 <file:Documentation/fb/fbcon.txt>.
83 config SERIAL_NONSTANDARD
84 bool "Non-standard serial port support"
87 Say Y here if you have any non-standard serial boards -- boards
88 which aren't supported using the standard "dumb" serial driver.
89 This includes intelligent serial boards such as Cyclades,
90 Digiboards, etc. These are usually used for systems that need many
91 serial ports because they serve many terminals or dial-in
94 Note that the answer to this question won't directly affect the
95 kernel: saying N will just cause the configurator to skip all
96 the questions about non-standard serial boards.
98 Most people can say N here.
101 tristate "Computone IntelliPort Plus serial support"
102 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
104 This driver supports the entire family of Intelliport II/Plus
105 controllers with the exception of the MicroChannel controllers and
106 products previous to the Intelliport II. These are multiport cards,
107 which give you many serial ports. You would need something like this
108 to connect more than two modems to your Linux box, for instance in
109 order to become a dial-in server. If you have a card like that, say
110 Y here and read <file:Documentation/computone.txt>.
112 To compile this driver as modules, choose M here: the
113 modules will be called ip2 and ip2main.
116 tristate "Comtrol RocketPort support"
117 depends on SERIAL_NONSTANDARD
119 This driver supports Comtrol RocketPort and RocketModem PCI boards.
120 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
121 modems. For information about the RocketPort/RocketModem boards
122 and this driver read <file:Documentation/rocket.txt>.
124 To compile this driver as a module, choose M here: the
125 module will be called rocket.
127 If you want to compile this driver into the kernel, say Y here. If
128 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
131 tristate "Cyclades async mux support"
132 depends on SERIAL_NONSTANDARD && (PCI || ISA)
134 This driver supports Cyclades Z and Y multiserial boards.
135 You would need something like this to connect more than two modems to
136 your Linux box, for instance in order to become a dial-in server.
138 For information about the Cyclades-Z card, read
139 <file:drivers/char/README.cycladesZ>.
141 To compile this driver as a module, choose M here: the
142 module will be called cyclades.
144 If you haven't heard about it, it's safe to say N.
147 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
148 depends on EXPERIMENTAL && CYCLADES
150 The Cyclades-Z family of multiport cards allows 2 (two) driver op
151 modes: polling and interrupt. In polling mode, the driver will check
152 the status of the Cyclades-Z ports every certain amount of time
153 (which is called polling cycle and is configurable). In interrupt
154 mode, it will use an interrupt line (IRQ) in order to check the
155 status of the Cyclades-Z ports. The default op mode is polling. If
159 tristate "Digiboard Intelligent Async Support"
160 depends on SERIAL_NONSTANDARD
162 This is a driver for Digi International's Xx, Xeve, and Xem series
163 of cards which provide multiple serial ports. You would need
164 something like this to connect more than two modems to your Linux
165 box, for instance in order to become a dial-in server. This driver
166 supports the original PC (ISA) boards as well as PCI, and EISA. If
167 you have a card like this, say Y here and read the file
168 <file:Documentation/digiepca.txt>.
170 To compile this driver as a module, choose M here: the
171 module will be called epca.
174 tristate "Hayes ESP serial port support"
175 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
177 This is a driver which supports Hayes ESP serial ports. Both single
178 port cards and multiport cards are supported. Make sure to read
179 <file:Documentation/hayes-esp.txt>.
181 To compile this driver as a module, choose M here: the
182 module will be called esp.
187 tristate "Moxa Intellio support"
188 depends on SERIAL_NONSTANDARD
190 Say Y here if you have a Moxa Intellio multiport serial card.
192 To compile this driver as a module, choose M here: the
193 module will be called moxa.
196 tristate "Moxa SmartIO support (OBSOLETE)"
197 depends on SERIAL_NONSTANDARD
199 Say Y here if you have a Moxa SmartIO multiport serial card.
201 This driver can also be built as a module ( = code which can be
202 inserted in and removed from the running kernel whenever you want).
203 The module will be called mxser. If you want to do that, say M
206 config MOXA_SMARTIO_NEW
207 tristate "Moxa SmartIO support v. 2.0"
208 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
210 Say Y here if you have a Moxa SmartIO multiport serial card and/or
211 want to help develop a new version of this driver.
213 This is upgraded (1.9.1) driver from original Moxa drivers with
214 changes finally resulting in PCI probing.
216 This driver can also be built as a module. The module will be called
217 mxser_new. If you want to do that, say M here.
220 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
221 depends on SERIAL_NONSTANDARD && PCI
224 This is a driver for the Multi-Tech cards which provide several
225 serial ports. The driver is experimental and can currently only be
226 built as a module. The module will be called isicom.
227 If you want to do that, choose M here.
230 tristate "Microgate SyncLink card support"
231 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
233 Provides support for the SyncLink ISA and PCI multiprotocol serial
234 adapters. These adapters support asynchronous and HDLC bit
235 synchronous communication up to 10Mbps (PCI adapter).
237 This driver can only be built as a module ( = code which can be
238 inserted in and removed from the running kernel whenever you want).
239 The module will be called synclink. If you want to do that, say M
243 tristate "SyncLink Multiport support"
244 depends on SERIAL_NONSTANDARD
246 Enable support for the SyncLink Multiport (2 or 4 ports)
247 serial adapter, running asynchronous and HDLC communications up
248 to 2.048Mbps. Each ports is independently selectable for
249 RS-232, V.35, RS-449, RS-530, and X.21
251 This driver may be built as a module ( = code which can be
252 inserted in and removed from the running kernel whenever you want).
253 The module will be called synclinkmp. If you want to do that, say M
257 tristate "SyncLink GT/AC support"
258 depends on SERIAL_NONSTANDARD && PCI
260 Support for SyncLink GT and SyncLink AC families of
261 synchronous and asynchronous serial adapters
262 manufactured by Microgate Systems, Ltd. (www.microgate.com)
265 tristate "HDLC line discipline support"
266 depends on SERIAL_NONSTANDARD
268 Allows synchronous HDLC communications with tty device drivers that
269 support synchronous HDLC such as the Microgate SyncLink adapter.
271 This driver can only be built as a module ( = code which can be
272 inserted in and removed from the running kernel whenever you want).
273 The module will be called n_hdlc. If you want to do that, say M
277 tristate "SDL RISCom/8 card support"
278 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
280 This is a driver for the SDL Communications RISCom/8 multiport card,
281 which gives you many serial ports. You would need something like
282 this to connect more than two modems to your Linux box, for instance
283 in order to become a dial-in server. If you have a card like that,
284 say Y here and read the file <file:Documentation/riscom8.txt>.
286 Also it's possible to say M here and compile this driver as kernel
287 loadable module; the module will be called riscom8.
290 tristate "Specialix IO8+ card support"
291 depends on SERIAL_NONSTANDARD
293 This is a driver for the Specialix IO8+ multiport card (both the
294 ISA and the PCI version) which gives you many serial ports. You
295 would need something like this to connect more than two modems to
296 your Linux box, for instance in order to become a dial-in server.
298 If you have a card like that, say Y here and read the file
299 <file:Documentation/specialix.txt>. Also it's possible to say M here
300 and compile this driver as kernel loadable module which will be
303 config SPECIALIX_RTSCTS
304 bool "Specialix DTR/RTS pin is RTS"
307 The Specialix IO8+ card can only support either RTS or DTR. If you
308 say N here, the driver will use the pin as "DTR" when the tty is in
309 software handshake mode. If you say Y here or hardware handshake is
310 on, it will always be RTS. Read the file
311 <file:Documentation/specialix.txt> for more information.
314 tristate "Specialix SX (and SI) card support"
315 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
317 This is a driver for the SX and SI multiport serial cards.
318 Please read the file <file:Documentation/sx.txt> for details.
320 This driver can only be built as a module ( = code which can be
321 inserted in and removed from the running kernel whenever you want).
322 The module will be called sx. If you want to do that, say M here.
325 tristate "Specialix RIO system support"
326 depends on SERIAL_NONSTANDARD
328 This is a driver for the Specialix RIO, a smart serial card which
329 drives an outboard box that can support up to 128 ports. Product
330 information is at <http://www.perle.com/support/documentation.html#multiport>.
331 There are both ISA and PCI versions.
334 bool "Support really old RIO/PCI cards"
337 Older RIO PCI cards need some initialization-time configuration to
338 determine the IRQ and some control addresses. If you have a RIO and
339 this doesn't seem to work, try setting this to Y.
342 bool "Stallion multiport serial support"
343 depends on SERIAL_NONSTANDARD
345 Stallion cards give you many serial ports. You would need something
346 like this to connect more than two modems to your Linux box, for
347 instance in order to become a dial-in server. If you say Y here,
348 you will be asked for your specific card model in the next
349 questions. Make sure to read <file:Documentation/stallion.txt> in
350 this case. If you have never heard about all this, it's safe to
354 tristate "Stallion EasyIO or EC8/32 support"
355 depends on STALDRV && BROKEN_ON_SMP
357 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
358 card, then this is for you; say Y. Make sure to read
359 <file:Documentation/stallion.txt>.
361 To compile this driver as a module, choose M here: the
362 module will be called stallion.
365 tristate "Stallion EC8/64, ONboard, Brumby support"
366 depends on STALDRV && BROKEN_ON_SMP
368 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
369 serial multiport card, say Y here. Make sure to read
370 <file:Documentation/stallion.txt>.
372 To compile this driver as a module, choose M here: the
373 module will be called istallion.
376 bool "DECstation serial support"
377 depends on MACH_DECSTATION
380 This selects whether you want to be asked about drivers for
381 DECstation serial ports.
383 Note that the answer to this question won't directly affect the
384 kernel: saying N will just cause the configurator to skip all
385 the questions about DECstation serial ports.
387 config SERIAL_DEC_CONSOLE
388 bool "Support for console on a DECstation serial port"
389 depends on SERIAL_DEC
392 If you say Y here, it will be possible to use a serial port as the
393 system console (the system console is the device which receives all
394 kernel messages and warnings and which allows logins in single user
395 mode). Note that the firmware uses ttyS0 as the serial console on
396 the Maxine and ttyS2 on the others.
401 bool "Z85C30 Serial Support"
402 depends on SERIAL_DEC
405 Documentation on the Zilog 85C350 serial communications controller
406 is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>
409 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
410 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
412 This option supports the 2232 7-port serial card shipped with the
413 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
414 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
415 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
416 ports were connected with 8 pin DIN connectors on the card bracket,
417 for which 8 pin to DB25 adapters were supplied. The card also had
418 jumpers internally to toggle various pinning configurations.
420 This driver can be built as a module; but then "generic_serial"
421 will also be built as a module. This has to be loaded before
422 "ser_a2232". If you want to do this, answer M here.
425 bool "SGI Altix system controller communication support"
426 depends on (IA64_SGI_SN2 || IA64_GENERIC)
428 If you have an SGI Altix and you want to enable system
429 controller communication from user space (you want this!),
430 say Y. Otherwise, say N.
433 bool "SGI TIO CX driver support"
434 depends on (IA64_SGI_SN2 || IA64_GENERIC)
436 If you have an SGI Altix and you have fpga devices attached
437 to your TIO, say Y here, otherwise say N.
440 tristate "SGI FPGA Core Services driver support"
443 If you have an SGI Altix with an attached SABrick
444 say Y or M here, otherwise say N.
446 source "drivers/serial/Kconfig"
449 bool "Unix98 PTY support" if EMBEDDED
452 A pseudo terminal (PTY) is a software device consisting of two
453 halves: a master and a slave. The slave device behaves identical to
454 a physical terminal; the master device is used by a process to
455 read data from and write data to the slave, thereby emulating a
456 terminal. Typical programs for the master side are telnet servers
459 Linux has traditionally used the BSD-like names /dev/ptyxx for
460 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
461 has a number of problems. The GNU C library glibc 2.1 and later,
462 however, supports the Unix98 naming standard: in order to acquire a
463 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
464 terminal is then made available to the process and the pseudo
465 terminal slave can be accessed as /dev/pts/<number>. What was
466 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
468 All modern Linux systems use the Unix98 ptys. Say Y unless
469 you're on an embedded system and want to conserve memory.
472 bool "Legacy (BSD) PTY support"
475 A pseudo terminal (PTY) is a software device consisting of two
476 halves: a master and a slave. The slave device behaves identical to
477 a physical terminal; the master device is used by a process to
478 read data from and write data to the slave, thereby emulating a
479 terminal. Typical programs for the master side are telnet servers
482 Linux has traditionally used the BSD-like names /dev/ptyxx
483 for masters and /dev/ttyxx for slaves of pseudo
484 terminals. This scheme has a number of problems, including
485 security. This option enables these legacy devices; on most
486 systems, it is safe to say N.
489 config LEGACY_PTY_COUNT
490 int "Maximum number of legacy PTY in use"
491 depends on LEGACY_PTYS
495 The maximum number of legacy PTYs that can be used at any one time.
496 The default is 256, and should be more than enough. Embedded
497 systems may want to reduce this to save memory.
499 When not in use, each legacy PTY occupies 12 bytes on 32-bit
500 architectures and 24 bytes on 64-bit architectures.
503 tristate 'Total Impact briQ front panel driver'
506 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
507 tristate led and two switches. It is the size of a CDROM drive.
509 If you have such one and want anything showing on the VFD then you
512 To compile this driver as a module, choose M here: the
513 module will be called briq_panel.
515 It's safe to say N here.
518 tristate "Parallel printer support"
521 If you intend to attach a printer to the parallel port of your Linux
522 box (as opposed to using a serial printer; if the connector at the
523 printer has 9 or 25 holes ["female"], then it's serial), say Y.
524 Also read the Printing-HOWTO, available from
525 <http://www.tldp.org/docs.html#howto>.
527 It is possible to share one parallel port among several devices
528 (e.g. printer and ZIP drive) and it is safe to compile the
529 corresponding drivers into the kernel.
531 To compile this driver as a module, choose M here and read
532 <file:Documentation/parport.txt>. The module will be called lp.
534 If you have several parallel ports, you can specify which ports to
535 use with the "lp" kernel command line option. (Try "man bootparam"
536 or see the documentation of your boot loader (lilo or loadlin) about
537 how to pass options to the kernel at boot time.) The syntax of the
538 "lp" command line option can be found in <file:drivers/char/lp.c>.
540 If you have more than 8 printers, you need to increase the LP_NO
541 macro in lp.c and the PARPORT_MAX macro in parport.h.
544 bool "Support for console on line printer"
547 If you want kernel messages to be printed out as they occur, you
548 can have a console on the printer. This option adds support for
549 doing that; to actually get it to happen you need to pass the
550 option "console=lp0" to the kernel at boot time.
552 If the printer is out of paper (or off, or unplugged, or too
553 busy..) the kernel will stall until the printer is ready again.
554 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
555 can make the kernel continue when this happens,
556 but it'll lose the kernel messages.
561 tristate "Support for user-space parallel port device drivers"
564 Saying Y to this adds support for /dev/parport device nodes. This
565 is needed for programs that want portable access to the parallel
566 port, for instance deviceid (which displays Plug-and-Play device
569 This is the parallel port equivalent of SCSI generic support (sg).
570 It is safe to say N to this -- it is not needed for normal printing
571 or parallel port CD-ROM/disk support.
573 To compile this driver as a module, choose M here: the
574 module will be called ppdev.
579 tristate "Texas Instruments parallel link cable support"
582 If you own a Texas Instruments graphing calculator and use a
583 parallel link cable, then you might be interested in this driver.
585 If you enable this driver, you will be able to communicate with
586 your calculator through a set of device nodes under /dev. The
587 main advantage of this driver is that you don't have to be root
588 to use this precise link cable (depending on the permissions on
589 the device nodes, though).
591 To compile this driver as a module, choose M here: the
592 module will be called tipar.
594 If you don't know what a parallel link cable is or what a Texas
595 Instruments graphing calculator is, then you probably don't need this
603 Users of pSeries machines that want to utilize the hvc console front-end
604 module for their backend console driver should select this option.
605 It will automatically be selected if one of the back-end console drivers
610 bool "pSeries Hypervisor Virtual Console support"
611 depends on PPC_PSERIES
614 pSeries machines when partitioned support a hypervisor virtual
615 console. This driver allows each pSeries partition to have a console
616 which is accessed via the HMC.
619 bool "iSeries Hypervisor Virtual Console support"
620 depends on PPC_ISERIES
624 iSeries machines support a hypervisor virtual console.
627 bool "IBM RTAS Console support"
631 IBM Console device driver which makes use of RTAS
634 bool "Toshiba's Beat Hypervisor Console support"
635 depends on PPC_CELLEB
638 Toshiba's Cell Reference Set Beat Console device driver
641 tristate "IBM Hypervisor Virtual Console Server support"
642 depends on PPC_PSERIES
644 Partitionable IBM Power5 ppc64 machines allow hosting of
645 firmware virtual consoles from one Linux partition by
646 another Linux partition. This driver allows console data
647 from Linux partitions to be accessed through TTY device
648 interfaces in the device tree of a Linux partition running
651 To compile this driver as a module, choose M here: the
652 module will be called hvcs.ko. Additionally, this module
653 will depend on arch specific APIs exported from hvcserver.ko
654 which will also be compiled when this driver is built as a
657 source "drivers/char/ipmi/Kconfig"
659 source "drivers/char/watchdog/Kconfig"
662 tristate "NetWinder thermometer support"
663 depends on ARCH_NETWINDER
665 Say Y here to include support for the thermal management hardware
666 found in the NetWinder. This driver allows the user to control the
667 temperature set points and to read the current temperature.
669 It is also possible to say M here to build it as a module (ds1620)
670 It is recommended to be used on a NetWinder, but it is not a
674 tristate "NetWinder Button"
675 depends on ARCH_NETWINDER
677 If you say Y here and create a character device node /dev/nwbutton
678 with major and minor numbers 10 and 158 ("man mknod"), then every
679 time the orange button is pressed a number of times, the number of
680 times the button was pressed will be written to that device.
682 This is most useful for applications, as yet unwritten, which
683 perform actions based on how many times the button is pressed in a
686 Do not hold the button down for too long, as the driver does not
687 alter the behaviour of the hardware reset circuitry attached to the
688 button; it will still execute a hard reset if the button is held
689 down for longer than approximately five seconds.
691 To compile this driver as a module, choose M here: the
692 module will be called nwbutton.
694 Most people will answer Y to this question and "Reboot Using Button"
695 below to be able to initiate a system shutdown from the button.
697 config NWBUTTON_REBOOT
698 bool "Reboot Using Button"
701 If you say Y here, then you will be able to initiate a system
702 shutdown and reboot by pressing the orange button a number of times.
703 The number of presses to initiate the shutdown is two by default,
704 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
705 in nwbutton.h and recompiling the driver or, if you compile the
706 driver as a module, you can specify the number of presses at load
707 time with "insmod button reboot_count=<something>".
710 tristate "NetWinder flash support"
711 depends on ARCH_NETWINDER
713 If you say Y here and create a character device /dev/flash with
714 major 10 and minor 160 you can manipulate the flash ROM containing
715 the NetWinder firmware. Be careful as accidentally overwriting the
716 flash contents can render your computer unbootable. On no account
717 allow random users access to this device. :-)
719 To compile this driver as a module, choose M here: the
720 module will be called nwflash.
722 If you're not sure, say N.
724 source "drivers/char/hw_random/Kconfig"
727 tristate "/dev/nvram support"
728 depends on ATARI || X86 || ARM || GENERIC_NVRAM
730 If you say Y here and create a character special file /dev/nvram
731 with major number 10 and minor number 144 using mknod ("man mknod"),
732 you get read and write access to the extra bytes of non-volatile
733 memory in the real time clock (RTC), which is contained in every PC
734 and most Ataris. The actual number of bytes varies, depending on the
735 nvram in the system, but is usually 114 (128-14 for the RTC).
737 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
738 on Ataris. /dev/nvram may be used to view settings there, or to
739 change them (with some utility). It could also be used to frequently
740 save a few bits of very important data that may not be lost over
741 power-off and for which writing to disk is too insecure. Note
742 however that most NVRAM space in a PC belongs to the BIOS and you
743 should NEVER idly tamper with it. See Ralf Brown's interrupt list
744 for a guide to the use of CMOS bytes by your BIOS.
746 On Atari machines, /dev/nvram is always configured and does not need
749 To compile this driver as a module, choose M here: the
750 module will be called nvram.
753 tristate "Enhanced Real Time Clock Support"
754 depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV && !ARM && !SUPERH && !S390
756 If you say Y here and create a character special file /dev/rtc with
757 major number 10 and minor number 135 using mknod ("man mknod"), you
758 will get access to the real time clock (or hardware clock) built
761 Every PC has such a clock built in. It can be used to generate
762 signals from as low as 1Hz up to 8192Hz, and can also be used
763 as a 24 hour alarm. It reports status information via the file
764 /proc/driver/rtc and its behaviour is set by various ioctls on
767 If you run Linux on a multiprocessor machine and said Y to
768 "Symmetric Multi Processing" above, you should say Y here to read
769 and set the RTC in an SMP compatible fashion.
771 If you think you have a use for such a device (such as periodic data
772 sampling), then say Y here, and read <file:Documentation/rtc.txt>
775 To compile this driver as a module, choose M here: the
776 module will be called rtc.
779 tristate "SGI DS1286 RTC support"
782 If you say Y here and create a character special file /dev/rtc with
783 major number 10 and minor number 135 using mknod ("man mknod"), you
784 will get access to the real time clock built into your computer.
785 Every SGI has such a clock built in. It reports status information
786 via the file /proc/rtc and its behaviour is set by various ioctls on
790 bool "SGI M48T35 RTC support"
793 If you say Y here and create a character special file /dev/rtc with
794 major number 10 and minor number 135 using mknod ("man mknod"), you
795 will get access to the real time clock built into your computer.
796 Every SGI has such a clock built in. It reports status information
797 via the file /proc/rtc and its behaviour is set by various ioctls on
801 tristate "Generic /dev/rtc emulation"
802 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH
804 If you say Y here and create a character special file /dev/rtc with
805 major number 10 and minor number 135 using mknod ("man mknod"), you
806 will get access to the real time clock (or hardware clock) built
809 It reports status information via the file /proc/driver/rtc and its
810 behaviour is set by various ioctls on /dev/rtc. If you enable the
811 "extended RTC operation" below it will also provide an emulation
812 for RTC_UIE which is required by some programs and may improve
813 precision in some cases.
815 To compile this driver as a module, choose M here: the
816 module will be called genrtc.
819 bool "Extended RTC operation"
822 Provides an emulation for RTC_UIE which is required by some programs
823 and may improve precision of the generic RTC support in some cases.
826 bool "EFI Real Time Clock Services"
830 tristate "DS1302 RTC support"
831 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
833 If you say Y here and create a character special file /dev/rtc with
834 major number 121 and minor number 0 using mknod ("man mknod"), you
835 will get access to the real time clock (or hardware clock) built
839 bool "Support for Cobalt LCD"
840 depends on MIPS_COBALT
842 This option enables support for the LCD display and buttons found
843 on Cobalt systems through a misc device.
846 tristate "Double Talk PC internal speech card support"
849 This driver is for the DoubleTalk PC, a speech synthesizer
850 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
851 called the `internal DoubleTalk'.
853 To compile this driver as a module, choose M here: the
854 module will be called dtlk.
857 tristate "Siemens R3964 line discipline"
859 This driver allows synchronous communication with devices using the
860 Siemens R3964 packet protocol. Unless you are dealing with special
861 hardware like PLCs, you are unlikely to need this.
863 To compile this driver as a module, choose M here: the
864 module will be called n_r3964.
869 tristate "Applicom intelligent fieldbus card support"
872 This driver provides the kernel-side support for the intelligent
873 fieldbus cards made by Applicom International. More information
874 about these cards can be found on the WWW at the address
875 <http://www.applicom-int.com/>, or by email from David Woodhouse
876 <dwmw2@infradead.org>.
878 To compile this driver as a module, choose M here: the
879 module will be called applicom.
884 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
885 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
887 This driver enables access to the Sony Programmable I/O Control
888 Device which can be found in many (all ?) Sony Vaio laptops.
890 If you have one of those laptops, read
891 <file:Documentation/sonypi.txt>, and say Y or M here.
893 To compile this driver as a module, choose M here: the
894 module will be called sonypi.
897 tristate "TANBAC TB0219 GPIO support"
898 depends on TANBAC_TB022X
901 source "drivers/char/agp/Kconfig"
903 source "drivers/char/drm/Kconfig"
905 source "drivers/char/pcmcia/Kconfig"
908 tristate "ACP Modem (Mwave) support"
912 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
913 kernel driver and a user level application. Together these components
914 support direct attachment to public switched telephone networks (PSTNs)
915 and support selected world wide countries.
917 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
918 600, and 770 that include on board ACP modem hardware.
920 The modem also supports the standard communications port interface
921 (ttySx) and is compatible with the Hayes AT Command Set.
923 The user level application needed to use this driver can be found at
924 the IBM Linux Technology Center (LTC) web site:
925 <http://www.ibm.com/linux/ltc/>.
927 If you own one of the above IBM Thinkpads which has the Mwave chipset
930 To compile this driver as a module, choose M here: the
931 module will be called mwave.
934 tristate "NatSemi SCx200 GPIO Support"
938 Give userspace access to the GPIO pins on the National
939 Semiconductor SCx200 processors.
941 If compiled as a module, it will be called scx200_gpio.
944 tristate "NatSemi PC8736x GPIO Support"
946 default SCx200_GPIO # mostly N
947 select NSC_GPIO # needed for support routines
949 Give userspace access to the GPIO pins on the National
950 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
951 has multiple functional units, inc several managed by
952 hwmon/pc87360 driver. Tested with PC-87366
954 If compiled as a module, it will be called pc8736x_gpio.
957 tristate "NatSemi Base GPIO Support"
959 # selected by SCx200_GPIO and PC8736x_GPIO
960 # what about 2 selectors differing: m != y
962 Common support used (and needed) by scx200_gpio and
963 pc8736x_gpio drivers. If those drivers are built as
964 modules, this one will be too, named nsc_gpio
967 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
970 Give userspace access to the GPIO pins on the AMD CS5535 and
971 CS5536 Geode companion devices.
973 If compiled as a module, it will be called cs5535_gpio.
976 tristate "NEC VR4100 series General-purpose I/O Unit support"
977 depends on CPU_VR41XX
980 tristate "RAW driver (/dev/raw/rawN)"
983 The raw driver permits block devices to be bound to /dev/raw/rawN.
984 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
985 See the raw(8) manpage for more details.
987 Applications should preferably open the device (eg /dev/hda1)
988 with the O_DIRECT flag.
991 int "Maximum number of RAW devices to support (1-8192)"
992 depends on RAW_DRIVER
995 The maximum number of RAW devices that are supported.
996 Default is 256. Increase this number in case you need lots of
1000 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1004 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1005 open selects one of the timers supported by the HPET. The timers are
1006 non-periodic and/or periodic.
1009 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1013 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1014 is assumed the platform called hpet_alloc with the RTC IRQ values for
1018 bool "Allow mmap of HPET"
1022 If you say Y here, user applications will be able to mmap
1025 In some hardware implementations, the page containing HPET
1026 registers may also contain other things that shouldn't be
1027 exposed to the user. If this applies to your hardware,
1030 config HANGCHECK_TIMER
1031 tristate "Hangcheck timer"
1032 depends on X86 || IA64 || PPC64 || S390
1034 The hangcheck-timer module detects when the system has gone
1035 out to lunch past a certain margin. It can reboot the system
1036 or merely print a warning.
1039 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1040 depends on IA64_GENERIC || IA64_SGI_SN2
1043 The mmtimer device allows direct userspace access to the
1046 source "drivers/char/tpm/Kconfig"
1049 tristate "Telecom clock driver for ATCA SBC"
1050 depends on EXPERIMENTAL && X86
1053 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1054 ATCA computers and allows direct userspace access to the
1055 configuration of the telecom clock configuration settings. This
1056 device is used for hardware synchronization across the ATCA backplane
1057 fabric. Upon loading, the driver exports a sysfs directory,
1058 /sys/devices/platform/telco_clock, with a number of files for
1059 controlling the behavior of this hardware.
1064 depends on ISA || PCI
1067 source "drivers/s390/char/Kconfig"
git.openpandora.org / pandora-kernel.git / blob