2 # Character device configuration
5 menu "Character devices"
8 bool "Virtual terminal" if EMBEDDED
12 If you say Y here, you will get support for terminal devices with
13 display and keyboard devices. These are called "virtual" because you
14 can run several virtual terminals (also called virtual consoles) on
15 one physical terminal. This is rather useful, for example one
16 virtual terminal can collect system messages and warnings, another
17 one can be used for a text-mode user session, and a third could run
18 an X session, all in parallel. Switching between virtual terminals
19 is done with certain key combinations, usually Alt-<function key>.
21 The setterm command ("man setterm") can be used to change the
22 properties (such as colors or beeping) of a virtual terminal. The
23 man page console_codes(4) ("man console_codes") contains the special
24 character sequences that can be used to change those properties
25 directly. The fonts used on virtual terminals can be changed with
26 the setfont ("man setfont") command and the key bindings are defined
27 with the loadkeys ("man loadkeys") command.
29 You need at least one virtual terminal device in order to make use
30 of your keyboard and monitor. Therefore, only people configuring an
31 embedded system would want to say N here in order to save some
32 memory; the only way to log into such a system is then via a serial
33 or network connection.
35 If unsure, say Y, or else you won't be able to do much with your new
36 shiny Linux system :-)
39 bool "Support for console on virtual terminal" if EMBEDDED
43 The system console is the device which receives all kernel messages
44 and warnings and which allows logins in single user mode. If you
45 answer Y here, a virtual terminal (the device used to interact with
46 a physical terminal) can be used as system console. This is the most
47 common mode of operations, so you should say Y here unless you want
48 the kernel messages be output only to a serial port (in which case
49 you should say Y to "Console on serial port", below).
51 If you do say Y here, by default the currently visible virtual
52 terminal (/dev/tty0) will be used as system console. You can change
53 that with a kernel command line option such as "console=tty3" which
54 would use the third virtual terminal as system console. (Try "man
55 bootparam" or see the documentation of your boot loader (lilo or
56 loadlin) about how to pass options to the kernel at boot time.)
62 depends on VT && !S390 && !UML
65 config VT_HW_CONSOLE_BINDING
66 bool "Support for binding and unbinding console drivers"
70 The virtual terminal is the device that interacts with the physical
71 terminal through console drivers. On these systems, at least one
72 console driver is loaded. In other configurations, additional console
73 drivers may be enabled, such as the framebuffer console. If more than
74 1 console driver is enabled, setting this to 'y' will allow you to
75 select the console driver that will serve as the backend for the
78 See <file:Documentation/console/console.txt> for more
79 information. For framebuffer console users, please refer to
80 <file:Documentation/fb/fbcon.txt>.
82 config SERIAL_NONSTANDARD
83 bool "Non-standard serial port support"
85 Say Y here if you have any non-standard serial boards -- boards
86 which aren't supported using the standard "dumb" serial driver.
87 This includes intelligent serial boards such as Cyclades,
88 Digiboards, etc. These are usually used for systems that need many
89 serial ports because they serve many terminals or dial-in
92 Note that the answer to this question won't directly affect the
93 kernel: saying N will just cause the configurator to skip all
94 the questions about non-standard serial boards.
96 Most people can say N here.
99 tristate "Computone IntelliPort Plus serial support"
100 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
102 This driver supports the entire family of Intelliport II/Plus
103 controllers with the exception of the MicroChannel controllers and
104 products previous to the Intelliport II. These are multiport cards,
105 which give you many serial ports. You would need something like this
106 to connect more than two modems to your Linux box, for instance in
107 order to become a dial-in server. If you have a card like that, say
108 Y here and read <file:Documentation/computone.txt>.
110 To compile this driver as modules, choose M here: the
111 modules will be called ip2 and ip2main.
114 tristate "Comtrol RocketPort support"
115 depends on SERIAL_NONSTANDARD
117 This driver supports Comtrol RocketPort and RocketModem PCI boards.
118 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
119 modems. For information about the RocketPort/RocketModem boards
120 and this driver read <file:Documentation/rocket.txt>.
122 To compile this driver as a module, choose M here: the
123 module will be called rocket.
125 If you want to compile this driver into the kernel, say Y here. If
126 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
129 tristate "Cyclades async mux support"
130 depends on SERIAL_NONSTANDARD
132 This driver supports Cyclades Z and Y multiserial boards.
133 You would need something like this to connect more than two modems to
134 your Linux box, for instance in order to become a dial-in server.
136 For information about the Cyclades-Z card, read
137 <file:drivers/char/README.cycladesZ>.
139 To compile this driver as a module, choose M here: the
140 module will be called cyclades.
142 If you haven't heard about it, it's safe to say N.
145 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
146 depends on EXPERIMENTAL && CYCLADES
148 The Cyclades-Z family of multiport cards allows 2 (two) driver op
149 modes: polling and interrupt. In polling mode, the driver will check
150 the status of the Cyclades-Z ports every certain amount of time
151 (which is called polling cycle and is configurable). In interrupt
152 mode, it will use an interrupt line (IRQ) in order to check the
153 status of the Cyclades-Z ports. The default op mode is polling. If
157 tristate "Digiboard Intelligent Async Support"
158 depends on SERIAL_NONSTANDARD
160 This is a driver for Digi International's Xx, Xeve, and Xem series
161 of cards which provide multiple serial ports. You would need
162 something like this to connect more than two modems to your Linux
163 box, for instance in order to become a dial-in server. This driver
164 supports the original PC (ISA) boards as well as PCI, and EISA. If
165 you have a card like this, say Y here and read the file
166 <file:Documentation/digiepca.txt>.
168 To compile this driver as a module, choose M here: the
169 module will be called epca.
172 tristate "Hayes ESP serial port support"
173 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
175 This is a driver which supports Hayes ESP serial ports. Both single
176 port cards and multiport cards are supported. Make sure to read
177 <file:Documentation/hayes-esp.txt>.
179 To compile this driver as a module, choose M here: the
180 module will be called esp.
185 tristate "Moxa Intellio support"
186 depends on SERIAL_NONSTANDARD
188 Say Y here if you have a Moxa Intellio multiport serial card.
190 To compile this driver as a module, choose M here: the
191 module will be called moxa.
194 tristate "Moxa SmartIO support"
195 depends on SERIAL_NONSTANDARD
197 Say Y here if you have a Moxa SmartIO multiport serial card.
199 This driver can also be built as a module ( = code which can be
200 inserted in and removed from the running kernel whenever you want).
201 The module will be called mxser. If you want to do that, say M
204 config MOXA_SMARTIO_NEW
205 tristate "Moxa SmartIO support v. 2.0 (EXPERIMENTAL)"
206 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
208 Say Y here if you have a Moxa SmartIO multiport serial card and/or
209 want to help develop a new version of this driver.
211 This is upgraded (1.9.1) driver from original Moxa drivers with
212 changes finally resulting in PCI probing.
214 Use at your own risk.
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 "Enable Au1000 UART Support"
377 depends on SERIAL_NONSTANDARD && MIPS
379 If you have an Alchemy AU1000 processor (MIPS based) and you want
380 to use serial ports, say Y. Otherwise, say N.
382 config AU1000_SERIAL_CONSOLE
383 bool "Enable Au1000 serial console"
384 depends on AU1000_UART
386 If you have an Alchemy AU1000 processor (MIPS based) and you want
387 to use a console on a serial port, say Y. Otherwise, say N.
390 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
391 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
393 This option supports the 2232 7-port serial card shipped with the
394 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
395 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
396 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
397 ports were connected with 8 pin DIN connectors on the card bracket,
398 for which 8 pin to DB25 adapters were supplied. The card also had
399 jumpers internally to toggle various pinning configurations.
401 This driver can be built as a module; but then "generic_serial"
402 will also be built as a module. This has to be loaded before
403 "ser_a2232". If you want to do this, answer M here.
406 bool "SGI Altix system controller communication support"
407 depends on (IA64_SGI_SN2 || IA64_GENERIC)
409 If you have an SGI Altix and you want to enable system
410 controller communication from user space (you want this!),
411 say Y. Otherwise, say N.
414 bool "SGI TIO CX driver support"
415 depends on (IA64_SGI_SN2 || IA64_GENERIC)
417 If you have an SGI Altix and you have fpga devices attached
418 to your TIO, say Y here, otherwise say N.
421 tristate "SGI FPGA Core Services driver support"
424 If you have an SGI Altix with an attached SABrick
425 say Y or M here, otherwise say N.
427 source "drivers/serial/Kconfig"
430 bool "Unix98 PTY support" if EMBEDDED
433 A pseudo terminal (PTY) is a software device consisting of two
434 halves: a master and a slave. The slave device behaves identical to
435 a physical terminal; the master device is used by a process to
436 read data from and write data to the slave, thereby emulating a
437 terminal. Typical programs for the master side are telnet servers
440 Linux has traditionally used the BSD-like names /dev/ptyxx for
441 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
442 has a number of problems. The GNU C library glibc 2.1 and later,
443 however, supports the Unix98 naming standard: in order to acquire a
444 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
445 terminal is then made available to the process and the pseudo
446 terminal slave can be accessed as /dev/pts/<number>. What was
447 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
449 All modern Linux systems use the Unix98 ptys. Say Y unless
450 you're on an embedded system and want to conserve memory.
453 bool "Legacy (BSD) PTY support"
456 A pseudo terminal (PTY) is a software device consisting of two
457 halves: a master and a slave. The slave device behaves identical to
458 a physical terminal; the master device is used by a process to
459 read data from and write data to the slave, thereby emulating a
460 terminal. Typical programs for the master side are telnet servers
463 Linux has traditionally used the BSD-like names /dev/ptyxx
464 for masters and /dev/ttyxx for slaves of pseudo
465 terminals. This scheme has a number of problems, including
466 security. This option enables these legacy devices; on most
467 systems, it is safe to say N.
470 tristate "Crash Utility memory driver"
472 config LEGACY_PTY_COUNT
473 int "Maximum number of legacy PTY in use"
474 depends on LEGACY_PTYS
478 The maximum number of legacy PTYs that can be used at any one time.
479 The default is 256, and should be more than enough. Embedded
480 systems may want to reduce this to save memory.
482 When not in use, each legacy PTY occupies 12 bytes on 32-bit
483 architectures and 24 bytes on 64-bit architectures.
486 tristate 'Total Impact briQ front panel driver'
489 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
490 tristate led and two switches. It is the size of a CDROM drive.
492 If you have such one and want anything showing on the VFD then you
495 To compile this driver as a module, choose M here: the
496 module will be called briq_panel.
498 It's safe to say N here.
501 tristate "Parallel printer support"
504 If you intend to attach a printer to the parallel port of your Linux
505 box (as opposed to using a serial printer; if the connector at the
506 printer has 9 or 25 holes ["female"], then it's serial), say Y.
507 Also read the Printing-HOWTO, available from
508 <http://www.tldp.org/docs.html#howto>.
510 It is possible to share one parallel port among several devices
511 (e.g. printer and ZIP drive) and it is safe to compile the
512 corresponding drivers into the kernel.
514 To compile this driver as a module, choose M here and read
515 <file:Documentation/parport.txt>. The module will be called lp.
517 If you have several parallel ports, you can specify which ports to
518 use with the "lp" kernel command line option. (Try "man bootparam"
519 or see the documentation of your boot loader (lilo or loadlin) about
520 how to pass options to the kernel at boot time.) The syntax of the
521 "lp" command line option can be found in <file:drivers/char/lp.c>.
523 If you have more than 8 printers, you need to increase the LP_NO
524 macro in lp.c and the PARPORT_MAX macro in parport.h.
527 bool "Support for console on line printer"
530 If you want kernel messages to be printed out as they occur, you
531 can have a console on the printer. This option adds support for
532 doing that; to actually get it to happen you need to pass the
533 option "console=lp0" to the kernel at boot time.
535 If the printer is out of paper (or off, or unplugged, or too
536 busy..) the kernel will stall until the printer is ready again.
537 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
538 can make the kernel continue when this happens,
539 but it'll lose the kernel messages.
544 tristate "Support for user-space parallel port device drivers"
547 Saying Y to this adds support for /dev/parport device nodes. This
548 is needed for programs that want portable access to the parallel
549 port, for instance deviceid (which displays Plug-and-Play device
552 This is the parallel port equivalent of SCSI generic support (sg).
553 It is safe to say N to this -- it is not needed for normal printing
554 or parallel port CD-ROM/disk support.
556 To compile this driver as a module, choose M here: the
557 module will be called ppdev.
562 tristate "Texas Instruments parallel link cable support"
565 If you own a Texas Instruments graphing calculator and use a
566 parallel link cable, then you might be interested in this driver.
568 If you enable this driver, you will be able to communicate with
569 your calculator through a set of device nodes under /dev. The
570 main advantage of this driver is that you don't have to be root
571 to use this precise link cable (depending on the permissions on
572 the device nodes, though).
574 To compile this driver as a module, choose M here: the
575 module will be called tipar.
577 If you don't know what a parallel link cable is or what a Texas
578 Instruments graphing calculator is, then you probably don't need this
586 Users of pSeries machines that want to utilize the hvc console front-end
587 module for their backend console driver should select this option.
588 It will automatically be selected if one of the back-end console drivers
593 bool "pSeries Hypervisor Virtual Console support"
594 depends on PPC_PSERIES
597 pSeries machines when partitioned support a hypervisor virtual
598 console. This driver allows each pSeries partition to have a console
599 which is accessed via the HMC.
602 bool "iSeries Hypervisor Virtual Console support"
603 depends on PPC_ISERIES && !VIOCONS
606 iSeries machines support a hypervisor virtual console.
609 bool "IBM RTAS Console support"
613 IBM Console device driver which makes use of RTAS
616 tristate "IBM Hypervisor Virtual Console Server support"
617 depends on PPC_PSERIES
619 Partitionable IBM Power5 ppc64 machines allow hosting of
620 firmware virtual consoles from one Linux partition by
621 another Linux partition. This driver allows console data
622 from Linux partitions to be accessed through TTY device
623 interfaces in the device tree of a Linux partition running
626 To compile this driver as a module, choose M here: the
627 module will be called hvcs.ko. Additionally, this module
628 will depend on arch specific APIs exported from hvcserver.ko
629 which will also be compiled when this driver is built as a
632 source "drivers/char/ipmi/Kconfig"
634 source "drivers/char/watchdog/Kconfig"
637 tristate "NetWinder thermometer support"
638 depends on ARCH_NETWINDER
640 Say Y here to include support for the thermal management hardware
641 found in the NetWinder. This driver allows the user to control the
642 temperature set points and to read the current temperature.
644 It is also possible to say M here to build it as a module (ds1620)
645 It is recommended to be used on a NetWinder, but it is not a
649 tristate "NetWinder Button"
650 depends on ARCH_NETWINDER
652 If you say Y here and create a character device node /dev/nwbutton
653 with major and minor numbers 10 and 158 ("man mknod"), then every
654 time the orange button is pressed a number of times, the number of
655 times the button was pressed will be written to that device.
657 This is most useful for applications, as yet unwritten, which
658 perform actions based on how many times the button is pressed in a
661 Do not hold the button down for too long, as the driver does not
662 alter the behaviour of the hardware reset circuitry attached to the
663 button; it will still execute a hard reset if the button is held
664 down for longer than approximately five seconds.
666 To compile this driver as a module, choose M here: the
667 module will be called nwbutton.
669 Most people will answer Y to this question and "Reboot Using Button"
670 below to be able to initiate a system shutdown from the button.
672 config NWBUTTON_REBOOT
673 bool "Reboot Using Button"
676 If you say Y here, then you will be able to initiate a system
677 shutdown and reboot by pressing the orange button a number of times.
678 The number of presses to initiate the shutdown is two by default,
679 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
680 in nwbutton.h and recompiling the driver or, if you compile the
681 driver as a module, you can specify the number of presses at load
682 time with "insmod button reboot_count=<something>".
685 tristate "NetWinder flash support"
686 depends on ARCH_NETWINDER
688 If you say Y here and create a character device /dev/flash with
689 major 10 and minor 160 you can manipulate the flash ROM containing
690 the NetWinder firmware. Be careful as accidentally overwriting the
691 flash contents can render your computer unbootable. On no account
692 allow random users access to this device. :-)
694 To compile this driver as a module, choose M here: the
695 module will be called nwflash.
697 If you're not sure, say N.
699 source "drivers/char/hw_random/Kconfig"
702 tristate "/dev/nvram support"
703 depends on ATARI || X86 || ARM || GENERIC_NVRAM
705 If you say Y here and create a character special file /dev/nvram
706 with major number 10 and minor number 144 using mknod ("man mknod"),
707 you get read and write access to the extra bytes of non-volatile
708 memory in the real time clock (RTC), which is contained in every PC
709 and most Ataris. The actual number of bytes varies, depending on the
710 nvram in the system, but is usually 114 (128-14 for the RTC).
712 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
713 on Ataris. /dev/nvram may be used to view settings there, or to
714 change them (with some utility). It could also be used to frequently
715 save a few bits of very important data that may not be lost over
716 power-off and for which writing to disk is too insecure. Note
717 however that most NVRAM space in a PC belongs to the BIOS and you
718 should NEVER idly tamper with it. See Ralf Brown's interrupt list
719 for a guide to the use of CMOS bytes by your BIOS.
721 On Atari machines, /dev/nvram is always configured and does not need
724 To compile this driver as a module, choose M here: the
725 module will be called nvram.
728 tristate "Enhanced Real Time Clock Support"
729 depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV && !ARM && !SUPERH
731 If you say Y here and create a character special file /dev/rtc with
732 major number 10 and minor number 135 using mknod ("man mknod"), you
733 will get access to the real time clock (or hardware clock) built
736 Every PC has such a clock built in. It can be used to generate
737 signals from as low as 1Hz up to 8192Hz, and can also be used
738 as a 24 hour alarm. It reports status information via the file
739 /proc/driver/rtc and its behaviour is set by various ioctls on
742 If you run Linux on a multiprocessor machine and said Y to
743 "Symmetric Multi Processing" above, you should say Y here to read
744 and set the RTC in an SMP compatible fashion.
746 If you think you have a use for such a device (such as periodic data
747 sampling), then say Y here, and read <file:Documentation/rtc.txt>
750 To compile this driver as a module, choose M here: the
751 module will be called rtc.
754 tristate "SGI DS1286 RTC support"
757 If you say Y here and create a character special file /dev/rtc with
758 major number 10 and minor number 135 using mknod ("man mknod"), you
759 will get access to the real time clock built into your computer.
760 Every SGI has such a clock built in. It reports status information
761 via the file /proc/rtc and its behaviour is set by various ioctls on
765 bool "SGI M48T35 RTC support"
768 If you say Y here and create a character special file /dev/rtc with
769 major number 10 and minor number 135 using mknod ("man mknod"), you
770 will get access to the real time clock built into your computer.
771 Every SGI has such a clock built in. It reports status information
772 via the file /proc/rtc and its behaviour is set by various ioctls on
776 tristate "Generic /dev/rtc emulation"
777 depends on RTC!=y && !IA64 && !ARM && !M32R && !SPARC && !FRV
779 If you say Y here and create a character special file /dev/rtc with
780 major number 10 and minor number 135 using mknod ("man mknod"), you
781 will get access to the real time clock (or hardware clock) built
784 It reports status information via the file /proc/driver/rtc and its
785 behaviour is set by various ioctls on /dev/rtc. If you enable the
786 "extended RTC operation" below it will also provide an emulation
787 for RTC_UIE which is required by some programs and may improve
788 precision in some cases.
790 To compile this driver as a module, choose M here: the
791 module will be called genrtc.
794 bool "Extended RTC operation"
797 Provides an emulation for RTC_UIE which is required by some programs
798 and may improve precision of the generic RTC support in some cases.
801 bool "EFI Real Time Clock Services"
805 tristate "DS1302 RTC support"
806 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
808 If you say Y here and create a character special file /dev/rtc with
809 major number 121 and minor number 0 using mknod ("man mknod"), you
810 will get access to the real time clock (or hardware clock) built
814 bool "Support for Cobalt LCD"
815 depends on MIPS_COBALT
817 This option enables support for the LCD display and buttons found
818 on Cobalt systems through a misc device.
821 tristate "Double Talk PC internal speech card support"
823 This driver is for the DoubleTalk PC, a speech synthesizer
824 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
825 called the `internal DoubleTalk'.
827 To compile this driver as a module, choose M here: the
828 module will be called dtlk.
831 tristate "Siemens R3964 line discipline"
833 This driver allows synchronous communication with devices using the
834 Siemens R3964 packet protocol. Unless you are dealing with special
835 hardware like PLCs, you are unlikely to need this.
837 To compile this driver as a module, choose M here: the
838 module will be called n_r3964.
843 tristate "Applicom intelligent fieldbus card support"
846 This driver provides the kernel-side support for the intelligent
847 fieldbus cards made by Applicom International. More information
848 about these cards can be found on the WWW at the address
849 <http://www.applicom-int.com/>, or by email from David Woodhouse
850 <dwmw2@infradead.org>.
852 To compile this driver as a module, choose M here: the
853 module will be called applicom.
858 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
859 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
861 This driver enables access to the Sony Programmable I/O Control
862 Device which can be found in many (all ?) Sony Vaio laptops.
864 If you have one of those laptops, read
865 <file:Documentation/sonypi.txt>, and say Y or M here.
867 To compile this driver as a module, choose M here: the
868 module will be called sonypi.
871 tristate "TANBAC TB0219 base board support"
872 depends on TANBAC_TB022X
875 source "drivers/char/agp/Kconfig"
877 source "drivers/char/drm/Kconfig"
879 source "drivers/char/pcmcia/Kconfig"
882 tristate "ACP Modem (Mwave) support"
886 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
887 kernel driver and a user level application. Together these components
888 support direct attachment to public switched telephone networks (PSTNs)
889 and support selected world wide countries.
891 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
892 600, and 770 that include on board ACP modem hardware.
894 The modem also supports the standard communications port interface
895 (ttySx) and is compatible with the Hayes AT Command Set.
897 The user level application needed to use this driver can be found at
898 the IBM Linux Technology Center (LTC) web site:
899 <http://www.ibm.com/linux/ltc/>.
901 If you own one of the above IBM Thinkpads which has the Mwave chipset
904 To compile this driver as a module, choose M here: the
905 module will be called mwave.
908 tristate "NatSemi SCx200 GPIO Support"
912 Give userspace access to the GPIO pins on the National
913 Semiconductor SCx200 processors.
915 If compiled as a module, it will be called scx200_gpio.
918 tristate "NatSemi PC8736x GPIO Support"
920 default SCx200_GPIO # mostly N
921 select NSC_GPIO # needed for support routines
923 Give userspace access to the GPIO pins on the National
924 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
925 has multiple functional units, inc several managed by
926 hwmon/pc87360 driver. Tested with PC-87366
928 If compiled as a module, it will be called pc8736x_gpio.
931 tristate "NatSemi Base GPIO Support"
933 # selected by SCx200_GPIO and PC8736x_GPIO
934 # what about 2 selectors differing: m != y
936 Common support used (and needed) by scx200_gpio and
937 pc8736x_gpio drivers. If those drivers are built as
938 modules, this one will be too, named nsc_gpio
941 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
944 Give userspace access to the GPIO pins on the AMD CS5535 and
945 CS5536 Geode companion devices.
947 If compiled as a module, it will be called cs5535_gpio.
950 tristate "NEC VR4100 series General-purpose I/O Unit support"
951 depends on CPU_VR41XX
954 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
957 The raw driver permits block devices to be bound to /dev/raw/rawN.
958 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
959 See the raw(8) manpage for more details.
961 The raw driver is deprecated and will be removed soon.
962 Applications should simply open the device (eg /dev/hda1)
963 with the O_DIRECT flag.
966 int "Maximum number of RAW devices to support (1-8192)"
967 depends on RAW_DRIVER
970 The maximum number of RAW devices that are supported.
971 Default is 256. Increase this number in case you need lots of
975 bool "HPET - High Precision Event Timer" if (X86 || IA64)
979 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
980 open selects one of the timers supported by the HPET. The timers are
981 non-periodic and/or periodic.
984 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
988 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
989 is assumed the platform called hpet_alloc with the RTC IRQ values for
993 bool "Allow mmap of HPET"
997 If you say Y here, user applications will be able to mmap
1000 In some hardware implementations, the page containing HPET
1001 registers may also contain other things that shouldn't be
1002 exposed to the user. If this applies to your hardware,
1005 config HANGCHECK_TIMER
1006 tristate "Hangcheck timer"
1007 depends on X86 || IA64 || PPC64
1009 The hangcheck-timer module detects when the system has gone
1010 out to lunch past a certain margin. It can reboot the system
1011 or merely print a warning.
1014 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1015 depends on IA64_GENERIC || IA64_SGI_SN2
1018 The mmtimer device allows direct userspace access to the
1021 source "drivers/char/tpm/Kconfig"
1024 tristate "Telecom clock driver for MPBL0010 ATCA SBC"
1025 depends on EXPERIMENTAL && X86
1028 The telecom clock device is specific to the MPBL0010 ATCA computer and
1029 allows direct userspace access to the configuration of the telecom clock
1030 configuration settings. This device is used for hardware synchronization
1031 across the ATCA backplane fabric. Upon loading, the driver exports a
1032 sysfs directory, /sys/devices/platform/telco_clock, with a number of
1033 files for controlling the behavior of this hardware.
git://git.onelab.eu / linux-2.6.git / blob