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 config LEGACY_PTY_COUNT
471 int "Maximum number of legacy PTY in use"
472 depends on LEGACY_PTYS
476 The maximum number of legacy PTYs that can be used at any one time.
477 The default is 256, and should be more than enough. Embedded
478 systems may want to reduce this to save memory.
480 When not in use, each legacy PTY occupies 12 bytes on 32-bit
481 architectures and 24 bytes on 64-bit architectures.
484 tristate 'Total Impact briQ front panel driver'
487 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
488 tristate led and two switches. It is the size of a CDROM drive.
490 If you have such one and want anything showing on the VFD then you
493 To compile this driver as a module, choose M here: the
494 module will be called briq_panel.
496 It's safe to say N here.
499 tristate "Parallel printer support"
502 If you intend to attach a printer to the parallel port of your Linux
503 box (as opposed to using a serial printer; if the connector at the
504 printer has 9 or 25 holes ["female"], then it's serial), say Y.
505 Also read the Printing-HOWTO, available from
506 <http://www.tldp.org/docs.html#howto>.
508 It is possible to share one parallel port among several devices
509 (e.g. printer and ZIP drive) and it is safe to compile the
510 corresponding drivers into the kernel.
512 To compile this driver as a module, choose M here and read
513 <file:Documentation/parport.txt>. The module will be called lp.
515 If you have several parallel ports, you can specify which ports to
516 use with the "lp" kernel command line option. (Try "man bootparam"
517 or see the documentation of your boot loader (lilo or loadlin) about
518 how to pass options to the kernel at boot time.) The syntax of the
519 "lp" command line option can be found in <file:drivers/char/lp.c>.
521 If you have more than 8 printers, you need to increase the LP_NO
522 macro in lp.c and the PARPORT_MAX macro in parport.h.
525 bool "Support for console on line printer"
528 If you want kernel messages to be printed out as they occur, you
529 can have a console on the printer. This option adds support for
530 doing that; to actually get it to happen you need to pass the
531 option "console=lp0" to the kernel at boot time.
533 If the printer is out of paper (or off, or unplugged, or too
534 busy..) the kernel will stall until the printer is ready again.
535 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
536 can make the kernel continue when this happens,
537 but it'll lose the kernel messages.
542 tristate "Support for user-space parallel port device drivers"
545 Saying Y to this adds support for /dev/parport device nodes. This
546 is needed for programs that want portable access to the parallel
547 port, for instance deviceid (which displays Plug-and-Play device
550 This is the parallel port equivalent of SCSI generic support (sg).
551 It is safe to say N to this -- it is not needed for normal printing
552 or parallel port CD-ROM/disk support.
554 To compile this driver as a module, choose M here: the
555 module will be called ppdev.
560 tristate "Texas Instruments parallel link cable support"
563 If you own a Texas Instruments graphing calculator and use a
564 parallel link cable, then you might be interested in this driver.
566 If you enable this driver, you will be able to communicate with
567 your calculator through a set of device nodes under /dev. The
568 main advantage of this driver is that you don't have to be root
569 to use this precise link cable (depending on the permissions on
570 the device nodes, though).
572 To compile this driver as a module, choose M here: the
573 module will be called tipar.
575 If you don't know what a parallel link cable is or what a Texas
576 Instruments graphing calculator is, then you probably don't need this
584 Users of pSeries machines that want to utilize the hvc console front-end
585 module for their backend console driver should select this option.
586 It will automatically be selected if one of the back-end console drivers
591 bool "pSeries Hypervisor Virtual Console support"
592 depends on PPC_PSERIES
595 pSeries machines when partitioned support a hypervisor virtual
596 console. This driver allows each pSeries partition to have a console
597 which is accessed via the HMC.
600 bool "iSeries Hypervisor Virtual Console support"
601 depends on PPC_ISERIES && !VIOCONS
604 iSeries machines support a hypervisor virtual console.
607 bool "IBM RTAS Console support"
611 IBM Console device driver which makes use of RTAS
614 tristate "IBM Hypervisor Virtual Console Server support"
615 depends on PPC_PSERIES
617 Partitionable IBM Power5 ppc64 machines allow hosting of
618 firmware virtual consoles from one Linux partition by
619 another Linux partition. This driver allows console data
620 from Linux partitions to be accessed through TTY device
621 interfaces in the device tree of a Linux partition running
624 To compile this driver as a module, choose M here: the
625 module will be called hvcs.ko. Additionally, this module
626 will depend on arch specific APIs exported from hvcserver.ko
627 which will also be compiled when this driver is built as a
630 source "drivers/char/ipmi/Kconfig"
632 source "drivers/char/watchdog/Kconfig"
635 tristate "NetWinder thermometer support"
636 depends on ARCH_NETWINDER
638 Say Y here to include support for the thermal management hardware
639 found in the NetWinder. This driver allows the user to control the
640 temperature set points and to read the current temperature.
642 It is also possible to say M here to build it as a module (ds1620)
643 It is recommended to be used on a NetWinder, but it is not a
647 tristate "NetWinder Button"
648 depends on ARCH_NETWINDER
650 If you say Y here and create a character device node /dev/nwbutton
651 with major and minor numbers 10 and 158 ("man mknod"), then every
652 time the orange button is pressed a number of times, the number of
653 times the button was pressed will be written to that device.
655 This is most useful for applications, as yet unwritten, which
656 perform actions based on how many times the button is pressed in a
659 Do not hold the button down for too long, as the driver does not
660 alter the behaviour of the hardware reset circuitry attached to the
661 button; it will still execute a hard reset if the button is held
662 down for longer than approximately five seconds.
664 To compile this driver as a module, choose M here: the
665 module will be called nwbutton.
667 Most people will answer Y to this question and "Reboot Using Button"
668 below to be able to initiate a system shutdown from the button.
670 config NWBUTTON_REBOOT
671 bool "Reboot Using Button"
674 If you say Y here, then you will be able to initiate a system
675 shutdown and reboot by pressing the orange button a number of times.
676 The number of presses to initiate the shutdown is two by default,
677 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
678 in nwbutton.h and recompiling the driver or, if you compile the
679 driver as a module, you can specify the number of presses at load
680 time with "insmod button reboot_count=<something>".
683 tristate "NetWinder flash support"
684 depends on ARCH_NETWINDER
686 If you say Y here and create a character device /dev/flash with
687 major 10 and minor 160 you can manipulate the flash ROM containing
688 the NetWinder firmware. Be careful as accidentally overwriting the
689 flash contents can render your computer unbootable. On no account
690 allow random users access to this device. :-)
692 To compile this driver as a module, choose M here: the
693 module will be called nwflash.
695 If you're not sure, say N.
697 source "drivers/char/hw_random/Kconfig"
700 tristate "/dev/nvram support"
701 depends on ATARI || X86 || ARM || GENERIC_NVRAM
703 If you say Y here and create a character special file /dev/nvram
704 with major number 10 and minor number 144 using mknod ("man mknod"),
705 you get read and write access to the extra bytes of non-volatile
706 memory in the real time clock (RTC), which is contained in every PC
707 and most Ataris. The actual number of bytes varies, depending on the
708 nvram in the system, but is usually 114 (128-14 for the RTC).
710 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
711 on Ataris. /dev/nvram may be used to view settings there, or to
712 change them (with some utility). It could also be used to frequently
713 save a few bits of very important data that may not be lost over
714 power-off and for which writing to disk is too insecure. Note
715 however that most NVRAM space in a PC belongs to the BIOS and you
716 should NEVER idly tamper with it. See Ralf Brown's interrupt list
717 for a guide to the use of CMOS bytes by your BIOS.
719 On Atari machines, /dev/nvram is always configured and does not need
722 To compile this driver as a module, choose M here: the
723 module will be called nvram.
726 tristate "Enhanced Real Time Clock Support"
727 depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV && !ARM && !SUPERH
729 If you say Y here and create a character special file /dev/rtc with
730 major number 10 and minor number 135 using mknod ("man mknod"), you
731 will get access to the real time clock (or hardware clock) built
734 Every PC has such a clock built in. It can be used to generate
735 signals from as low as 1Hz up to 8192Hz, and can also be used
736 as a 24 hour alarm. It reports status information via the file
737 /proc/driver/rtc and its behaviour is set by various ioctls on
740 If you run Linux on a multiprocessor machine and said Y to
741 "Symmetric Multi Processing" above, you should say Y here to read
742 and set the RTC in an SMP compatible fashion.
744 If you think you have a use for such a device (such as periodic data
745 sampling), then say Y here, and read <file:Documentation/rtc.txt>
748 To compile this driver as a module, choose M here: the
749 module will be called rtc.
752 tristate "SGI DS1286 RTC support"
755 If you say Y here and create a character special file /dev/rtc with
756 major number 10 and minor number 135 using mknod ("man mknod"), you
757 will get access to the real time clock built into your computer.
758 Every SGI has such a clock built in. It reports status information
759 via the file /proc/rtc and its behaviour is set by various ioctls on
763 bool "SGI M48T35 RTC support"
766 If you say Y here and create a character special file /dev/rtc with
767 major number 10 and minor number 135 using mknod ("man mknod"), you
768 will get access to the real time clock built into your computer.
769 Every SGI has such a clock built in. It reports status information
770 via the file /proc/rtc and its behaviour is set by various ioctls on
774 tristate "Generic /dev/rtc emulation"
775 depends on RTC!=y && !IA64 && !ARM && !M32R && !SPARC && !FRV
777 If you say Y here and create a character special file /dev/rtc with
778 major number 10 and minor number 135 using mknod ("man mknod"), you
779 will get access to the real time clock (or hardware clock) built
782 It reports status information via the file /proc/driver/rtc and its
783 behaviour is set by various ioctls on /dev/rtc. If you enable the
784 "extended RTC operation" below it will also provide an emulation
785 for RTC_UIE which is required by some programs and may improve
786 precision in some cases.
788 To compile this driver as a module, choose M here: the
789 module will be called genrtc.
792 bool "Extended RTC operation"
795 Provides an emulation for RTC_UIE which is required by some programs
796 and may improve precision of the generic RTC support in some cases.
799 bool "EFI Real Time Clock Services"
803 tristate "DS1302 RTC support"
804 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
806 If you say Y here and create a character special file /dev/rtc with
807 major number 121 and minor number 0 using mknod ("man mknod"), you
808 will get access to the real time clock (or hardware clock) built
812 bool "Support for Cobalt LCD"
813 depends on MIPS_COBALT
815 This option enables support for the LCD display and buttons found
816 on Cobalt systems through a misc device.
819 tristate "Double Talk PC internal speech card support"
821 This driver is for the DoubleTalk PC, a speech synthesizer
822 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
823 called the `internal DoubleTalk'.
825 To compile this driver as a module, choose M here: the
826 module will be called dtlk.
829 tristate "Siemens R3964 line discipline"
831 This driver allows synchronous communication with devices using the
832 Siemens R3964 packet protocol. Unless you are dealing with special
833 hardware like PLCs, you are unlikely to need this.
835 To compile this driver as a module, choose M here: the
836 module will be called n_r3964.
841 tristate "Applicom intelligent fieldbus card support"
844 This driver provides the kernel-side support for the intelligent
845 fieldbus cards made by Applicom International. More information
846 about these cards can be found on the WWW at the address
847 <http://www.applicom-int.com/>, or by email from David Woodhouse
848 <dwmw2@infradead.org>.
850 To compile this driver as a module, choose M here: the
851 module will be called applicom.
856 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
857 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
859 This driver enables access to the Sony Programmable I/O Control
860 Device which can be found in many (all ?) Sony Vaio laptops.
862 If you have one of those laptops, read
863 <file:Documentation/sonypi.txt>, and say Y or M here.
865 To compile this driver as a module, choose M here: the
866 module will be called sonypi.
869 tristate "TANBAC TB0219 base board support"
870 depends on TANBAC_TB022X
873 source "drivers/char/agp/Kconfig"
875 source "drivers/char/drm/Kconfig"
877 source "drivers/char/pcmcia/Kconfig"
880 tristate "ACP Modem (Mwave) support"
884 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
885 kernel driver and a user level application. Together these components
886 support direct attachment to public switched telephone networks (PSTNs)
887 and support selected world wide countries.
889 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
890 600, and 770 that include on board ACP modem hardware.
892 The modem also supports the standard communications port interface
893 (ttySx) and is compatible with the Hayes AT Command Set.
895 The user level application needed to use this driver can be found at
896 the IBM Linux Technology Center (LTC) web site:
897 <http://www.ibm.com/linux/ltc/>.
899 If you own one of the above IBM Thinkpads which has the Mwave chipset
902 To compile this driver as a module, choose M here: the
903 module will be called mwave.
906 tristate "NatSemi SCx200 GPIO Support"
910 Give userspace access to the GPIO pins on the National
911 Semiconductor SCx200 processors.
913 If compiled as a module, it will be called scx200_gpio.
916 tristate "NatSemi PC8736x GPIO Support"
918 default SCx200_GPIO # mostly N
919 select NSC_GPIO # needed for support routines
921 Give userspace access to the GPIO pins on the National
922 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
923 has multiple functional units, inc several managed by
924 hwmon/pc87360 driver. Tested with PC-87366
926 If compiled as a module, it will be called pc8736x_gpio.
929 tristate "NatSemi Base GPIO Support"
931 # selected by SCx200_GPIO and PC8736x_GPIO
932 # what about 2 selectors differing: m != y
934 Common support used (and needed) by scx200_gpio and
935 pc8736x_gpio drivers. If those drivers are built as
936 modules, this one will be too, named nsc_gpio
939 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
942 Give userspace access to the GPIO pins on the AMD CS5535 and
943 CS5536 Geode companion devices.
945 If compiled as a module, it will be called cs5535_gpio.
948 tristate "NEC VR4100 series General-purpose I/O Unit support"
949 depends on CPU_VR41XX
952 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
955 The raw driver permits block devices to be bound to /dev/raw/rawN.
956 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
957 See the raw(8) manpage for more details.
959 The raw driver is deprecated and will be removed soon.
960 Applications should simply open the device (eg /dev/hda1)
961 with the O_DIRECT flag.
964 int "Maximum number of RAW devices to support (1-8192)"
965 depends on RAW_DRIVER
968 The maximum number of RAW devices that are supported.
969 Default is 256. Increase this number in case you need lots of
973 bool "HPET - High Precision Event Timer" if (X86 || IA64)
977 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
978 open selects one of the timers supported by the HPET. The timers are
979 non-periodic and/or periodic.
982 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
986 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
987 is assumed the platform called hpet_alloc with the RTC IRQ values for
991 bool "Allow mmap of HPET"
995 If you say Y here, user applications will be able to mmap
998 In some hardware implementations, the page containing HPET
999 registers may also contain other things that shouldn't be
1000 exposed to the user. If this applies to your hardware,
1003 config HANGCHECK_TIMER
1004 tristate "Hangcheck timer"
1005 depends on X86 || IA64 || PPC64
1007 The hangcheck-timer module detects when the system has gone
1008 out to lunch past a certain margin. It can reboot the system
1009 or merely print a warning.
1012 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1013 depends on IA64_GENERIC || IA64_SGI_SN2
1016 The mmtimer device allows direct userspace access to the
1019 source "drivers/char/tpm/Kconfig"
1022 tristate "Telecom clock driver for MPBL0010 ATCA SBC"
1023 depends on EXPERIMENTAL && X86
1026 The telecom clock device is specific to the MPBL0010 ATCA computer and
1027 allows direct userspace access to the configuration of the telecom clock
1028 configuration settings. This device is used for hardware synchronization
1029 across the ATCA backplane fabric. Upon loading, the driver exports a
1030 sysfs directory, /sys/devices/platform/telco_clock, with a number of
1031 files for controlling the behavior of this hardware.
projects / linux-2.6 / blob