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 && (ISA || EISA || PCI)
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)
135 This driver supports Cyclades Z and Y multiserial boards.
136 You would need something like this to connect more than two modems to
137 your Linux box, for instance in order to become a dial-in server.
139 For information about the Cyclades-Z card, read
140 <file:drivers/char/README.cycladesZ>.
142 To compile this driver as a module, choose M here: the
143 module will be called cyclades.
145 If you haven't heard about it, it's safe to say N.
148 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
149 depends on EXPERIMENTAL && CYCLADES
151 The Cyclades-Z family of multiport cards allows 2 (two) driver op
152 modes: polling and interrupt. In polling mode, the driver will check
153 the status of the Cyclades-Z ports every certain amount of time
154 (which is called polling cycle and is configurable). In interrupt
155 mode, it will use an interrupt line (IRQ) in order to check the
156 status of the Cyclades-Z ports. The default op mode is polling. If
160 tristate "Digiboard Intelligent Async Support"
161 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
163 This is a driver for Digi International's Xx, Xeve, and Xem series
164 of cards which provide multiple serial ports. You would need
165 something like this to connect more than two modems to your Linux
166 box, for instance in order to become a dial-in server. This driver
167 supports the original PC (ISA) boards as well as PCI, and EISA. If
168 you have a card like this, say Y here and read the file
169 <file:Documentation/digiepca.txt>.
171 To compile this driver as a module, choose M here: the
172 module will be called epca.
175 tristate "Hayes ESP serial port support"
176 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
178 This is a driver which supports Hayes ESP serial ports. Both single
179 port cards and multiport cards are supported. Make sure to read
180 <file:Documentation/hayes-esp.txt>.
182 To compile this driver as a module, choose M here: the
183 module will be called esp.
188 tristate "Moxa Intellio support"
189 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
191 Say Y here if you have a Moxa Intellio multiport serial card.
193 To compile this driver as a module, choose M here: the
194 module will be called moxa.
197 tristate "Moxa SmartIO support (OBSOLETE)"
198 depends on SERIAL_NONSTANDARD
200 Say Y here if you have a Moxa SmartIO multiport serial card.
202 This driver can also be built as a module ( = code which can be
203 inserted in and removed from the running kernel whenever you want).
204 The module will be called mxser. If you want to do that, say M
207 config MOXA_SMARTIO_NEW
208 tristate "Moxa SmartIO support v. 2.0"
209 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
211 Say Y here if you have a Moxa SmartIO multiport serial card and/or
212 want to help develop a new version of this driver.
214 This is upgraded (1.9.1) driver from original Moxa drivers with
215 changes finally resulting in PCI probing.
217 This driver can also be built as a module. The module will be called
218 mxser_new. If you want to do that, say M here.
221 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
222 depends on SERIAL_NONSTANDARD && PCI
225 This is a driver for the Multi-Tech cards which provide several
226 serial ports. The driver is experimental and can currently only be
227 built as a module. The module will be called isicom.
228 If you want to do that, choose M here.
231 tristate "Microgate SyncLink card support"
232 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
234 Provides support for the SyncLink ISA and PCI multiprotocol serial
235 adapters. These adapters support asynchronous and HDLC bit
236 synchronous communication up to 10Mbps (PCI adapter).
238 This driver can only be built as a module ( = code which can be
239 inserted in and removed from the running kernel whenever you want).
240 The module will be called synclink. If you want to do that, say M
244 tristate "SyncLink Multiport support"
245 depends on SERIAL_NONSTANDARD && PCI
247 Enable support for the SyncLink Multiport (2 or 4 ports)
248 serial adapter, running asynchronous and HDLC communications up
249 to 2.048Mbps. Each ports is independently selectable for
250 RS-232, V.35, RS-449, RS-530, and X.21
252 This driver may be built as a module ( = code which can be
253 inserted in and removed from the running kernel whenever you want).
254 The module will be called synclinkmp. If you want to do that, say M
258 tristate "SyncLink GT/AC support"
259 depends on SERIAL_NONSTANDARD && PCI
261 Support for SyncLink GT and SyncLink AC families of
262 synchronous and asynchronous serial adapters
263 manufactured by Microgate Systems, Ltd. (www.microgate.com)
266 tristate "HDLC line discipline support"
267 depends on SERIAL_NONSTANDARD
269 Allows synchronous HDLC communications with tty device drivers that
270 support synchronous HDLC such as the Microgate SyncLink adapter.
272 This driver can only be built as a module ( = code which can be
273 inserted in and removed from the running kernel whenever you want).
274 The module will be called n_hdlc. If you want to do that, say M
278 tristate "SDL RISCom/8 card support"
279 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
281 This is a driver for the SDL Communications RISCom/8 multiport card,
282 which gives you many serial ports. You would need something like
283 this to connect more than two modems to your Linux box, for instance
284 in order to become a dial-in server. If you have a card like that,
285 say Y here and read the file <file:Documentation/riscom8.txt>.
287 Also it's possible to say M here and compile this driver as kernel
288 loadable module; the module will be called riscom8.
291 tristate "Specialix IO8+ card support"
292 depends on SERIAL_NONSTANDARD
294 This is a driver for the Specialix IO8+ multiport card (both the
295 ISA and the PCI version) which gives you many serial ports. You
296 would need something like this to connect more than two modems to
297 your Linux box, for instance in order to become a dial-in server.
299 If you have a card like that, say Y here and read the file
300 <file:Documentation/specialix.txt>. Also it's possible to say M here
301 and compile this driver as kernel loadable module which will be
304 config SPECIALIX_RTSCTS
305 bool "Specialix DTR/RTS pin is RTS"
308 The Specialix IO8+ card can only support either RTS or DTR. If you
309 say N here, the driver will use the pin as "DTR" when the tty is in
310 software handshake mode. If you say Y here or hardware handshake is
311 on, it will always be RTS. Read the file
312 <file:Documentation/specialix.txt> for more information.
315 tristate "Specialix SX (and SI) card support"
316 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
318 This is a driver for the SX and SI multiport serial cards.
319 Please read the file <file:Documentation/sx.txt> for details.
321 This driver can only be built as a module ( = code which can be
322 inserted in and removed from the running kernel whenever you want).
323 The module will be called sx. If you want to do that, say M here.
326 tristate "Specialix RIO system support"
327 depends on SERIAL_NONSTANDARD
329 This is a driver for the Specialix RIO, a smart serial card which
330 drives an outboard box that can support up to 128 ports. Product
331 information is at <http://www.perle.com/support/documentation.html#multiport>.
332 There are both ISA and PCI versions.
335 bool "Support really old RIO/PCI cards"
338 Older RIO PCI cards need some initialization-time configuration to
339 determine the IRQ and some control addresses. If you have a RIO and
340 this doesn't seem to work, try setting this to Y.
343 bool "Stallion multiport serial support"
344 depends on SERIAL_NONSTANDARD
346 Stallion cards give you many serial ports. You would need something
347 like this to connect more than two modems to your Linux box, for
348 instance in order to become a dial-in server. If you say Y here,
349 you will be asked for your specific card model in the next
350 questions. Make sure to read <file:Documentation/stallion.txt> in
351 this case. If you have never heard about all this, it's safe to
355 tristate "Stallion EasyIO or EC8/32 support"
356 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
358 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
359 card, then this is for you; say Y. Make sure to read
360 <file:Documentation/stallion.txt>.
362 To compile this driver as a module, choose M here: the
363 module will be called stallion.
366 tristate "Stallion EC8/64, ONboard, Brumby support"
367 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
369 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
370 serial multiport card, say Y here. Make sure to read
371 <file:Documentation/stallion.txt>.
373 To compile this driver as a module, choose M here: the
374 module will be called istallion.
377 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
378 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
380 This option supports the 2232 7-port serial card shipped with the
381 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
382 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
383 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
384 ports were connected with 8 pin DIN connectors on the card bracket,
385 for which 8 pin to DB25 adapters were supplied. The card also had
386 jumpers internally to toggle various pinning configurations.
388 This driver can be built as a module; but then "generic_serial"
389 will also be built as a module. This has to be loaded before
390 "ser_a2232". If you want to do this, answer M here.
393 bool "SGI Altix system controller communication support"
394 depends on (IA64_SGI_SN2 || IA64_GENERIC)
396 If you have an SGI Altix and you want to enable system
397 controller communication from user space (you want this!),
398 say Y. Otherwise, say N.
401 bool "SGI TIO CX driver support"
402 depends on (IA64_SGI_SN2 || IA64_GENERIC)
404 If you have an SGI Altix and you have fpga devices attached
405 to your TIO, say Y here, otherwise say N.
408 tristate "SGI FPGA Core Services driver support"
411 If you have an SGI Altix with an attached SABrick
412 say Y or M here, otherwise say N.
414 source "drivers/serial/Kconfig"
417 bool "Unix98 PTY support" if EMBEDDED
420 A pseudo terminal (PTY) is a software device consisting of two
421 halves: a master and a slave. The slave device behaves identical to
422 a physical terminal; the master device is used by a process to
423 read data from and write data to the slave, thereby emulating a
424 terminal. Typical programs for the master side are telnet servers
427 Linux has traditionally used the BSD-like names /dev/ptyxx for
428 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
429 has a number of problems. The GNU C library glibc 2.1 and later,
430 however, supports the Unix98 naming standard: in order to acquire a
431 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
432 terminal is then made available to the process and the pseudo
433 terminal slave can be accessed as /dev/pts/<number>. What was
434 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
436 All modern Linux systems use the Unix98 ptys. Say Y unless
437 you're on an embedded system and want to conserve memory.
440 bool "Legacy (BSD) PTY support"
443 A pseudo terminal (PTY) is a software device consisting of two
444 halves: a master and a slave. The slave device behaves identical to
445 a physical terminal; the master device is used by a process to
446 read data from and write data to the slave, thereby emulating a
447 terminal. Typical programs for the master side are telnet servers
450 Linux has traditionally used the BSD-like names /dev/ptyxx
451 for masters and /dev/ttyxx for slaves of pseudo
452 terminals. This scheme has a number of problems, including
453 security. This option enables these legacy devices; on most
454 systems, it is safe to say N.
457 config LEGACY_PTY_COUNT
458 int "Maximum number of legacy PTY in use"
459 depends on LEGACY_PTYS
463 The maximum number of legacy PTYs that can be used at any one time.
464 The default is 256, and should be more than enough. Embedded
465 systems may want to reduce this to save memory.
467 When not in use, each legacy PTY occupies 12 bytes on 32-bit
468 architectures and 24 bytes on 64-bit architectures.
471 tristate 'Total Impact briQ front panel driver'
474 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
475 tristate led and two switches. It is the size of a CDROM drive.
477 If you have such one and want anything showing on the VFD then you
480 To compile this driver as a module, choose M here: the
481 module will be called briq_panel.
483 It's safe to say N here.
486 tristate "Parallel printer support"
489 If you intend to attach a printer to the parallel port of your Linux
490 box (as opposed to using a serial printer; if the connector at the
491 printer has 9 or 25 holes ["female"], then it's serial), say Y.
492 Also read the Printing-HOWTO, available from
493 <http://www.tldp.org/docs.html#howto>.
495 It is possible to share one parallel port among several devices
496 (e.g. printer and ZIP drive) and it is safe to compile the
497 corresponding drivers into the kernel.
499 To compile this driver as a module, choose M here and read
500 <file:Documentation/parport.txt>. The module will be called lp.
502 If you have several parallel ports, you can specify which ports to
503 use with the "lp" kernel command line option. (Try "man bootparam"
504 or see the documentation of your boot loader (lilo or loadlin) about
505 how to pass options to the kernel at boot time.) The syntax of the
506 "lp" command line option can be found in <file:drivers/char/lp.c>.
508 If you have more than 8 printers, you need to increase the LP_NO
509 macro in lp.c and the PARPORT_MAX macro in parport.h.
512 bool "Support for console on line printer"
515 If you want kernel messages to be printed out as they occur, you
516 can have a console on the printer. This option adds support for
517 doing that; to actually get it to happen you need to pass the
518 option "console=lp0" to the kernel at boot time.
520 If the printer is out of paper (or off, or unplugged, or too
521 busy..) the kernel will stall until the printer is ready again.
522 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
523 can make the kernel continue when this happens,
524 but it'll lose the kernel messages.
529 tristate "Support for user-space parallel port device drivers"
532 Saying Y to this adds support for /dev/parport device nodes. This
533 is needed for programs that want portable access to the parallel
534 port, for instance deviceid (which displays Plug-and-Play device
537 This is the parallel port equivalent of SCSI generic support (sg).
538 It is safe to say N to this -- it is not needed for normal printing
539 or parallel port CD-ROM/disk support.
541 To compile this driver as a module, choose M here: the
542 module will be called ppdev.
547 tristate "Texas Instruments parallel link cable support"
550 If you own a Texas Instruments graphing calculator and use a
551 parallel link cable, then you might be interested in this driver.
553 If you enable this driver, you will be able to communicate with
554 your calculator through a set of device nodes under /dev. The
555 main advantage of this driver is that you don't have to be root
556 to use this precise link cable (depending on the permissions on
557 the device nodes, though).
559 To compile this driver as a module, choose M here: the
560 module will be called tipar.
562 If you don't know what a parallel link cable is or what a Texas
563 Instruments graphing calculator is, then you probably don't need this
571 Users of pSeries machines that want to utilize the hvc console front-end
572 module for their backend console driver should select this option.
573 It will automatically be selected if one of the back-end console drivers
578 bool "pSeries Hypervisor Virtual Console support"
579 depends on PPC_PSERIES
582 pSeries machines when partitioned support a hypervisor virtual
583 console. This driver allows each pSeries partition to have a console
584 which is accessed via the HMC.
587 bool "iSeries Hypervisor Virtual Console support"
588 depends on PPC_ISERIES
592 iSeries machines support a hypervisor virtual console.
595 bool "IBM RTAS Console support"
599 IBM Console device driver which makes use of RTAS
602 bool "Toshiba's Beat Hypervisor Console support"
603 depends on PPC_CELLEB
606 Toshiba's Cell Reference Set Beat Console device driver
609 bool "Xen Hypervisor Console support"
614 Xen virtual console device driver
617 tristate "IBM Hypervisor Virtual Console Server support"
618 depends on PPC_PSERIES
620 Partitionable IBM Power5 ppc64 machines allow hosting of
621 firmware virtual consoles from one Linux partition by
622 another Linux partition. This driver allows console data
623 from Linux partitions to be accessed through TTY device
624 interfaces in the device tree of a Linux partition running
627 To compile this driver as a module, choose M here: the
628 module will be called hvcs.ko. Additionally, this module
629 will depend on arch specific APIs exported from hvcserver.ko
630 which will also be compiled when this driver is built as a
633 source "drivers/char/ipmi/Kconfig"
635 source "drivers/char/watchdog/Kconfig"
638 tristate "NetWinder thermometer support"
639 depends on ARCH_NETWINDER
641 Say Y here to include support for the thermal management hardware
642 found in the NetWinder. This driver allows the user to control the
643 temperature set points and to read the current temperature.
645 It is also possible to say M here to build it as a module (ds1620)
646 It is recommended to be used on a NetWinder, but it is not a
650 tristate "NetWinder Button"
651 depends on ARCH_NETWINDER
653 If you say Y here and create a character device node /dev/nwbutton
654 with major and minor numbers 10 and 158 ("man mknod"), then every
655 time the orange button is pressed a number of times, the number of
656 times the button was pressed will be written to that device.
658 This is most useful for applications, as yet unwritten, which
659 perform actions based on how many times the button is pressed in a
662 Do not hold the button down for too long, as the driver does not
663 alter the behaviour of the hardware reset circuitry attached to the
664 button; it will still execute a hard reset if the button is held
665 down for longer than approximately five seconds.
667 To compile this driver as a module, choose M here: the
668 module will be called nwbutton.
670 Most people will answer Y to this question and "Reboot Using Button"
671 below to be able to initiate a system shutdown from the button.
673 config NWBUTTON_REBOOT
674 bool "Reboot Using Button"
677 If you say Y here, then you will be able to initiate a system
678 shutdown and reboot by pressing the orange button a number of times.
679 The number of presses to initiate the shutdown is two by default,
680 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
681 in nwbutton.h and recompiling the driver or, if you compile the
682 driver as a module, you can specify the number of presses at load
683 time with "insmod button reboot_count=<something>".
686 tristate "NetWinder flash support"
687 depends on ARCH_NETWINDER
689 If you say Y here and create a character device /dev/flash with
690 major 10 and minor 160 you can manipulate the flash ROM containing
691 the NetWinder firmware. Be careful as accidentally overwriting the
692 flash contents can render your computer unbootable. On no account
693 allow random users access to this device. :-)
695 To compile this driver as a module, choose M here: the
696 module will be called nwflash.
698 If you're not sure, say N.
700 source "drivers/char/hw_random/Kconfig"
703 tristate "/dev/nvram support"
704 depends on ATARI || X86 || ARM || GENERIC_NVRAM
706 If you say Y here and create a character special file /dev/nvram
707 with major number 10 and minor number 144 using mknod ("man mknod"),
708 you get read and write access to the extra bytes of non-volatile
709 memory in the real time clock (RTC), which is contained in every PC
710 and most Ataris. The actual number of bytes varies, depending on the
711 nvram in the system, but is usually 114 (128-14 for the RTC).
713 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
714 on Ataris. /dev/nvram may be used to view settings there, or to
715 change them (with some utility). It could also be used to frequently
716 save a few bits of very important data that may not be lost over
717 power-off and for which writing to disk is too insecure. Note
718 however that most NVRAM space in a PC belongs to the BIOS and you
719 should NEVER idly tamper with it. See Ralf Brown's interrupt list
720 for a guide to the use of CMOS bytes by your BIOS.
722 On Atari machines, /dev/nvram is always configured and does not need
725 To compile this driver as a module, choose M here: the
726 module will be called nvram.
729 tristate "Enhanced Real Time Clock Support"
730 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV && !ARM && !SUPERH && !S390
732 If you say Y here and create a character special file /dev/rtc with
733 major number 10 and minor number 135 using mknod ("man mknod"), you
734 will get access to the real time clock (or hardware clock) built
737 Every PC has such a clock built in. It can be used to generate
738 signals from as low as 1Hz up to 8192Hz, and can also be used
739 as a 24 hour alarm. It reports status information via the file
740 /proc/driver/rtc and its behaviour is set by various ioctls on
743 If you run Linux on a multiprocessor machine and said Y to
744 "Symmetric Multi Processing" above, you should say Y here to read
745 and set the RTC in an SMP compatible fashion.
747 If you think you have a use for such a device (such as periodic data
748 sampling), then say Y here, and read <file:Documentation/rtc.txt>
751 To compile this driver as a module, choose M here: the
752 module will be called rtc.
755 tristate "Enhanced Real Time Clock Support"
756 depends on SPARC32 && PCI
758 If you say Y here and create a character special file /dev/rtc with
759 major number 10 and minor number 135 using mknod ("man mknod"), you
760 will get access to the real time clock (or hardware clock) built
763 Every PC has such a clock built in. It can be used to generate
764 signals from as low as 1Hz up to 8192Hz, and can also be used
765 as a 24 hour alarm. It reports status information via the file
766 /proc/driver/rtc and its behaviour is set by various ioctls on
769 If you think you have a use for such a device (such as periodic data
770 sampling), then say Y here, and read <file:Documentation/rtc.txt>
773 To compile this driver as a module, choose M here: the
774 module will be called js-rtc.
777 tristate "SGI DS1286 RTC support"
780 If you say Y here and create a character special file /dev/rtc with
781 major number 10 and minor number 135 using mknod ("man mknod"), you
782 will get access to the real time clock built into your computer.
783 Every SGI has such a clock built in. It reports status information
784 via the file /proc/rtc and its behaviour is set by various ioctls on
788 bool "SGI M48T35 RTC support"
791 If you say Y here and create a character special file /dev/rtc with
792 major number 10 and minor number 135 using mknod ("man mknod"), you
793 will get access to the real time clock built into your computer.
794 Every SGI has such a clock built in. It reports status information
795 via the file /proc/rtc and its behaviour is set by various ioctls on
799 tristate "Generic /dev/rtc emulation"
800 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH
802 If you say Y here and create a character special file /dev/rtc with
803 major number 10 and minor number 135 using mknod ("man mknod"), you
804 will get access to the real time clock (or hardware clock) built
807 It reports status information via the file /proc/driver/rtc and its
808 behaviour is set by various ioctls on /dev/rtc. If you enable the
809 "extended RTC operation" below it will also provide an emulation
810 for RTC_UIE which is required by some programs and may improve
811 precision in some cases.
813 To compile this driver as a module, choose M here: the
814 module will be called genrtc.
817 bool "Extended RTC operation"
820 Provides an emulation for RTC_UIE which is required by some programs
821 and may improve precision of the generic RTC support in some cases.
824 bool "EFI Real Time Clock Services"
828 tristate "DS1302 RTC support"
829 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
831 If you say Y here and create a character special file /dev/rtc with
832 major number 121 and minor number 0 using mknod ("man mknod"), you
833 will get access to the real time clock (or hardware clock) built
837 bool "Support for Cobalt LCD"
838 depends on MIPS_COBALT
840 This option enables support for the LCD display and buttons found
841 on Cobalt systems through a misc device.
844 tristate "Double Talk PC internal speech card support"
847 This driver is for the DoubleTalk PC, a speech synthesizer
848 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
849 called the `internal DoubleTalk'.
851 To compile this driver as a module, choose M here: the
852 module will be called dtlk.
855 tristate "Siemens R3964 line discipline"
857 This driver allows synchronous communication with devices using the
858 Siemens R3964 packet protocol. Unless you are dealing with special
859 hardware like PLCs, you are unlikely to need this.
861 To compile this driver as a module, choose M here: the
862 module will be called n_r3964.
867 tristate "Applicom intelligent fieldbus card support"
870 This driver provides the kernel-side support for the intelligent
871 fieldbus cards made by Applicom International. More information
872 about these cards can be found on the WWW at the address
873 <http://www.applicom-int.com/>, or by email from David Woodhouse
874 <dwmw2@infradead.org>.
876 To compile this driver as a module, choose M here: the
877 module will be called applicom.
882 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
883 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
885 This driver enables access to the Sony Programmable I/O Control
886 Device which can be found in many (all ?) Sony Vaio laptops.
888 If you have one of those laptops, read
889 <file:Documentation/sonypi.txt>, and say Y or M here.
891 To compile this driver as a module, choose M here: the
892 module will be called sonypi.
895 tristate "TANBAC TB0219 GPIO support"
896 depends on TANBAC_TB022X
899 source "drivers/char/agp/Kconfig"
901 source "drivers/char/drm/Kconfig"
903 source "drivers/char/pcmcia/Kconfig"
906 tristate "ACP Modem (Mwave) support"
910 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
911 kernel driver and a user level application. Together these components
912 support direct attachment to public switched telephone networks (PSTNs)
913 and support selected world wide countries.
915 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
916 600, and 770 that include on board ACP modem hardware.
918 The modem also supports the standard communications port interface
919 (ttySx) and is compatible with the Hayes AT Command Set.
921 The user level application needed to use this driver can be found at
922 the IBM Linux Technology Center (LTC) web site:
923 <http://www.ibm.com/linux/ltc/>.
925 If you own one of the above IBM Thinkpads which has the Mwave chipset
928 To compile this driver as a module, choose M here: the
929 module will be called mwave.
932 tristate "NatSemi SCx200 GPIO Support"
936 Give userspace access to the GPIO pins on the National
937 Semiconductor SCx200 processors.
939 If compiled as a module, it will be called scx200_gpio.
942 tristate "NatSemi PC8736x GPIO Support"
944 default SCx200_GPIO # mostly N
945 select NSC_GPIO # needed for support routines
947 Give userspace access to the GPIO pins on the National
948 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
949 has multiple functional units, inc several managed by
950 hwmon/pc87360 driver. Tested with PC-87366
952 If compiled as a module, it will be called pc8736x_gpio.
955 tristate "NatSemi Base GPIO Support"
957 # selected by SCx200_GPIO and PC8736x_GPIO
958 # what about 2 selectors differing: m != y
960 Common support used (and needed) by scx200_gpio and
961 pc8736x_gpio drivers. If those drivers are built as
962 modules, this one will be too, named nsc_gpio
965 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
968 Give userspace access to the GPIO pins on the AMD CS5535 and
969 CS5536 Geode companion devices.
971 If compiled as a module, it will be called cs5535_gpio.
974 tristate "NEC VR4100 series General-purpose I/O Unit support"
975 depends on CPU_VR41XX
978 tristate "RAW driver (/dev/raw/rawN)"
981 The raw driver permits block devices to be bound to /dev/raw/rawN.
982 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
983 See the raw(8) manpage for more details.
985 Applications should preferably open the device (eg /dev/hda1)
986 with the O_DIRECT flag.
989 int "Maximum number of RAW devices to support (1-8192)"
990 depends on RAW_DRIVER
993 The maximum number of RAW devices that are supported.
994 Default is 256. Increase this number in case you need lots of
998 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1002 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1003 open selects one of the timers supported by the HPET. The timers are
1004 non-periodic and/or periodic.
1007 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1011 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1012 is assumed the platform called hpet_alloc with the RTC IRQ values for
1016 bool "Allow mmap of HPET"
1020 If you say Y here, user applications will be able to mmap
1023 In some hardware implementations, the page containing HPET
1024 registers may also contain other things that shouldn't be
1025 exposed to the user. If this applies to your hardware,
1028 config HANGCHECK_TIMER
1029 tristate "Hangcheck timer"
1030 depends on X86 || IA64 || PPC64 || S390
1032 The hangcheck-timer module detects when the system has gone
1033 out to lunch past a certain margin. It can reboot the system
1034 or merely print a warning.
1037 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1038 depends on IA64_GENERIC || IA64_SGI_SN2
1041 The mmtimer device allows direct userspace access to the
1044 source "drivers/char/tpm/Kconfig"
1047 tristate "Telecom clock driver for ATCA SBC"
1048 depends on EXPERIMENTAL && X86
1051 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1052 ATCA computers and allows direct userspace access to the
1053 configuration of the telecom clock configuration settings. This
1054 device is used for hardware synchronization across the ATCA backplane
1055 fabric. Upon loading, the driver exports a sysfs directory,
1056 /sys/devices/platform/telco_clock, with a number of files for
1057 controlling the behavior of this hardware.
1062 depends on ISA || PCI
1065 source "drivers/s390/char/Kconfig"
projects / linux-2.6 / blob