2 # Character device configuration
5 menu "Character devices"
8 bool "Virtual terminal" if EMBEDDED
13 If you say Y here, you will get support for terminal devices with
14 display and keyboard devices. These are called "virtual" because you
15 can run several virtual terminals (also called virtual consoles) on
16 one physical terminal. This is rather useful, for example one
17 virtual terminal can collect system messages and warnings, another
18 one can be used for a text-mode user session, and a third could run
19 an X session, all in parallel. Switching between virtual terminals
20 is done with certain key combinations, usually Alt-<function key>.
22 The setterm command ("man setterm") can be used to change the
23 properties (such as colors or beeping) of a virtual terminal. The
24 man page console_codes(4) ("man console_codes") contains the special
25 character sequences that can be used to change those properties
26 directly. The fonts used on virtual terminals can be changed with
27 the setfont ("man setfont") command and the key bindings are defined
28 with the loadkeys ("man loadkeys") command.
30 You need at least one virtual terminal device in order to make use
31 of your keyboard and monitor. Therefore, only people configuring an
32 embedded system would want to say N here in order to save some
33 memory; the only way to log into such a system is then via a serial
34 or network connection.
36 If unsure, say Y, or else you won't be able to do much with your new
37 shiny Linux system :-)
40 bool "Support for console on virtual terminal" if EMBEDDED
44 The system console is the device which receives all kernel messages
45 and warnings and which allows logins in single user mode. If you
46 answer Y here, a virtual terminal (the device used to interact with
47 a physical terminal) can be used as system console. This is the most
48 common mode of operations, so you should say Y here unless you want
49 the kernel messages be output only to a serial port (in which case
50 you should say Y to "Console on serial port", below).
52 If you do say Y here, by default the currently visible virtual
53 terminal (/dev/tty0) will be used as system console. You can change
54 that with a kernel command line option such as "console=tty3" which
55 would use the third virtual terminal as system console. (Try "man
56 bootparam" or see the documentation of your boot loader (lilo or
57 loadlin) about how to pass options to the kernel at boot time.)
63 depends on VT && !S390 && !UML
66 config VT_HW_CONSOLE_BINDING
67 bool "Support for binding and unbinding console drivers"
71 The virtual terminal is the device that interacts with the physical
72 terminal through console drivers. On these systems, at least one
73 console driver is loaded. In other configurations, additional console
74 drivers may be enabled, such as the framebuffer console. If more than
75 1 console driver is enabled, setting this to 'y' will allow you to
76 select the console driver that will serve as the backend for the
79 See <file:Documentation/console/console.txt> for more
80 information. For framebuffer console users, please refer to
81 <file:Documentation/fb/fbcon.txt>.
83 config SERIAL_NONSTANDARD
84 bool "Non-standard serial port support"
87 Say Y here if you have any non-standard serial boards -- boards
88 which aren't supported using the standard "dumb" serial driver.
89 This includes intelligent serial boards such as Cyclades,
90 Digiboards, etc. These are usually used for systems that need many
91 serial ports because they serve many terminals or dial-in
94 Note that the answer to this question won't directly affect the
95 kernel: saying N will just cause the configurator to skip all
96 the questions about non-standard serial boards.
98 Most people can say N here.
101 tristate "Computone IntelliPort Plus serial support"
102 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
104 This driver supports the entire family of Intelliport II/Plus
105 controllers with the exception of the MicroChannel controllers and
106 products previous to the Intelliport II. These are multiport cards,
107 which give you many serial ports. You would need something like this
108 to connect more than two modems to your Linux box, for instance in
109 order to become a dial-in server. If you have a card like that, say
110 Y here and read <file:Documentation/computone.txt>.
112 To compile this driver as modules, choose M here: the
113 modules will be called ip2 and ip2main.
116 tristate "Comtrol RocketPort support"
117 depends on SERIAL_NONSTANDARD
119 This driver supports Comtrol RocketPort and RocketModem PCI boards.
120 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
121 modems. For information about the RocketPort/RocketModem boards
122 and this driver read <file:Documentation/rocket.txt>.
124 To compile this driver as a module, choose M here: the
125 module will be called rocket.
127 If you want to compile this driver into the kernel, say Y here. If
128 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
131 tristate "Cyclades async mux support"
132 depends on SERIAL_NONSTANDARD && (PCI || ISA)
134 This driver supports Cyclades Z and Y multiserial boards.
135 You would need something like this to connect more than two modems to
136 your Linux box, for instance in order to become a dial-in server.
138 For information about the Cyclades-Z card, read
139 <file:drivers/char/README.cycladesZ>.
141 To compile this driver as a module, choose M here: the
142 module will be called cyclades.
144 If you haven't heard about it, it's safe to say N.
147 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
148 depends on EXPERIMENTAL && CYCLADES
150 The Cyclades-Z family of multiport cards allows 2 (two) driver op
151 modes: polling and interrupt. In polling mode, the driver will check
152 the status of the Cyclades-Z ports every certain amount of time
153 (which is called polling cycle and is configurable). In interrupt
154 mode, it will use an interrupt line (IRQ) in order to check the
155 status of the Cyclades-Z ports. The default op mode is polling. If
159 tristate "Digiboard Intelligent Async Support"
160 depends on SERIAL_NONSTANDARD
162 This is a driver for Digi International's Xx, Xeve, and Xem series
163 of cards which provide multiple serial ports. You would need
164 something like this to connect more than two modems to your Linux
165 box, for instance in order to become a dial-in server. This driver
166 supports the original PC (ISA) boards as well as PCI, and EISA. If
167 you have a card like this, say Y here and read the file
168 <file:Documentation/digiepca.txt>.
170 To compile this driver as a module, choose M here: the
171 module will be called epca.
174 tristate "Hayes ESP serial port support"
175 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
177 This is a driver which supports Hayes ESP serial ports. Both single
178 port cards and multiport cards are supported. Make sure to read
179 <file:Documentation/hayes-esp.txt>.
181 To compile this driver as a module, choose M here: the
182 module will be called esp.
187 tristate "Moxa Intellio support"
188 depends on SERIAL_NONSTANDARD
190 Say Y here if you have a Moxa Intellio multiport serial card.
192 To compile this driver as a module, choose M here: the
193 module will be called moxa.
196 tristate "Moxa SmartIO support (OBSOLETE)"
197 depends on SERIAL_NONSTANDARD
199 Say Y here if you have a Moxa SmartIO multiport serial card.
201 This driver can also be built as a module ( = code which can be
202 inserted in and removed from the running kernel whenever you want).
203 The module will be called mxser. If you want to do that, say M
206 config MOXA_SMARTIO_NEW
207 tristate "Moxa SmartIO support v. 2.0"
208 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
210 Say Y here if you have a Moxa SmartIO multiport serial card and/or
211 want to help develop a new version of this driver.
213 This is upgraded (1.9.1) driver from original Moxa drivers with
214 changes finally resulting in PCI probing.
216 Use at your own risk.
218 This driver can also be built as a module. The module will be called
219 mxser_new. If you want to do that, say M here.
222 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
223 depends on SERIAL_NONSTANDARD && PCI
226 This is a driver for the Multi-Tech cards which provide several
227 serial ports. The driver is experimental and can currently only be
228 built as a module. The module will be called isicom.
229 If you want to do that, choose M here.
232 tristate "Microgate SyncLink card support"
233 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
235 Provides support for the SyncLink ISA and PCI multiprotocol serial
236 adapters. These adapters support asynchronous and HDLC bit
237 synchronous communication up to 10Mbps (PCI adapter).
239 This driver can only be built as a module ( = code which can be
240 inserted in and removed from the running kernel whenever you want).
241 The module will be called synclink. If you want to do that, say M
245 tristate "SyncLink Multiport support"
246 depends on SERIAL_NONSTANDARD
248 Enable support for the SyncLink Multiport (2 or 4 ports)
249 serial adapter, running asynchronous and HDLC communications up
250 to 2.048Mbps. Each ports is independently selectable for
251 RS-232, V.35, RS-449, RS-530, and X.21
253 This driver may be built as a module ( = code which can be
254 inserted in and removed from the running kernel whenever you want).
255 The module will be called synclinkmp. If you want to do that, say M
259 tristate "SyncLink GT/AC support"
260 depends on SERIAL_NONSTANDARD && PCI
262 Support for SyncLink GT and SyncLink AC families of
263 synchronous and asynchronous serial adapters
264 manufactured by Microgate Systems, Ltd. (www.microgate.com)
267 tristate "HDLC line discipline support"
268 depends on SERIAL_NONSTANDARD
270 Allows synchronous HDLC communications with tty device drivers that
271 support synchronous HDLC such as the Microgate SyncLink adapter.
273 This driver can only be built as a module ( = code which can be
274 inserted in and removed from the running kernel whenever you want).
275 The module will be called n_hdlc. If you want to do that, say M
279 tristate "SDL RISCom/8 card support"
280 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
282 This is a driver for the SDL Communications RISCom/8 multiport card,
283 which gives you many serial ports. You would need something like
284 this to connect more than two modems to your Linux box, for instance
285 in order to become a dial-in server. If you have a card like that,
286 say Y here and read the file <file:Documentation/riscom8.txt>.
288 Also it's possible to say M here and compile this driver as kernel
289 loadable module; the module will be called riscom8.
292 tristate "Specialix IO8+ card support"
293 depends on SERIAL_NONSTANDARD
295 This is a driver for the Specialix IO8+ multiport card (both the
296 ISA and the PCI version) which gives you many serial ports. You
297 would need something like this to connect more than two modems to
298 your Linux box, for instance in order to become a dial-in server.
300 If you have a card like that, say Y here and read the file
301 <file:Documentation/specialix.txt>. Also it's possible to say M here
302 and compile this driver as kernel loadable module which will be
305 config SPECIALIX_RTSCTS
306 bool "Specialix DTR/RTS pin is RTS"
309 The Specialix IO8+ card can only support either RTS or DTR. If you
310 say N here, the driver will use the pin as "DTR" when the tty is in
311 software handshake mode. If you say Y here or hardware handshake is
312 on, it will always be RTS. Read the file
313 <file:Documentation/specialix.txt> for more information.
316 tristate "Specialix SX (and SI) card support"
317 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
319 This is a driver for the SX and SI multiport serial cards.
320 Please read the file <file:Documentation/sx.txt> for details.
322 This driver can only be built as a module ( = code which can be
323 inserted in and removed from the running kernel whenever you want).
324 The module will be called sx. If you want to do that, say M here.
327 tristate "Specialix RIO system support"
328 depends on SERIAL_NONSTANDARD
330 This is a driver for the Specialix RIO, a smart serial card which
331 drives an outboard box that can support up to 128 ports. Product
332 information is at <http://www.perle.com/support/documentation.html#multiport>.
333 There are both ISA and PCI versions.
336 bool "Support really old RIO/PCI cards"
339 Older RIO PCI cards need some initialization-time configuration to
340 determine the IRQ and some control addresses. If you have a RIO and
341 this doesn't seem to work, try setting this to Y.
344 bool "Stallion multiport serial support"
345 depends on SERIAL_NONSTANDARD
347 Stallion cards give you many serial ports. You would need something
348 like this to connect more than two modems to your Linux box, for
349 instance in order to become a dial-in server. If you say Y here,
350 you will be asked for your specific card model in the next
351 questions. Make sure to read <file:Documentation/stallion.txt> in
352 this case. If you have never heard about all this, it's safe to
356 tristate "Stallion EasyIO or EC8/32 support"
357 depends on STALDRV && BROKEN_ON_SMP
359 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
360 card, then this is for you; say Y. Make sure to read
361 <file:Documentation/stallion.txt>.
363 To compile this driver as a module, choose M here: the
364 module will be called stallion.
367 tristate "Stallion EC8/64, ONboard, Brumby support"
368 depends on STALDRV && BROKEN_ON_SMP
370 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
371 serial multiport card, say Y here. Make sure to read
372 <file:Documentation/stallion.txt>.
374 To compile this driver as a module, choose M here: the
375 module will be called istallion.
378 bool "DECstation serial support"
379 depends on MACH_DECSTATION
382 This selects whether you want to be asked about drivers for
383 DECstation serial ports.
385 Note that the answer to this question won't directly affect the
386 kernel: saying N will just cause the configurator to skip all
387 the questions about DECstation serial ports.
389 config SERIAL_DEC_CONSOLE
390 bool "Support for console on a DECstation serial port"
391 depends on SERIAL_DEC
394 If you say Y here, it will be possible to use a serial port as the
395 system console (the system console is the device which receives all
396 kernel messages and warnings and which allows logins in single user
397 mode). Note that the firmware uses ttyS0 as the serial console on
398 the Maxine and ttyS2 on the others.
403 bool "Z85C30 Serial Support"
404 depends on SERIAL_DEC
407 Documentation on the Zilog 85C350 serial communications controller
408 is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>
411 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
412 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
414 This option supports the 2232 7-port serial card shipped with the
415 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
416 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
417 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
418 ports were connected with 8 pin DIN connectors on the card bracket,
419 for which 8 pin to DB25 adapters were supplied. The card also had
420 jumpers internally to toggle various pinning configurations.
422 This driver can be built as a module; but then "generic_serial"
423 will also be built as a module. This has to be loaded before
424 "ser_a2232". If you want to do this, answer M here.
427 bool "SGI Altix system controller communication support"
428 depends on (IA64_SGI_SN2 || IA64_GENERIC)
430 If you have an SGI Altix and you want to enable system
431 controller communication from user space (you want this!),
432 say Y. Otherwise, say N.
435 bool "SGI TIO CX driver support"
436 depends on (IA64_SGI_SN2 || IA64_GENERIC)
438 If you have an SGI Altix and you have fpga devices attached
439 to your TIO, say Y here, otherwise say N.
442 tristate "SGI FPGA Core Services driver support"
445 If you have an SGI Altix with an attached SABrick
446 say Y or M here, otherwise say N.
448 source "drivers/serial/Kconfig"
451 bool "Unix98 PTY support" if EMBEDDED
454 A pseudo terminal (PTY) is a software device consisting of two
455 halves: a master and a slave. The slave device behaves identical to
456 a physical terminal; the master device is used by a process to
457 read data from and write data to the slave, thereby emulating a
458 terminal. Typical programs for the master side are telnet servers
461 Linux has traditionally used the BSD-like names /dev/ptyxx for
462 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
463 has a number of problems. The GNU C library glibc 2.1 and later,
464 however, supports the Unix98 naming standard: in order to acquire a
465 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
466 terminal is then made available to the process and the pseudo
467 terminal slave can be accessed as /dev/pts/<number>. What was
468 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
470 All modern Linux systems use the Unix98 ptys. Say Y unless
471 you're on an embedded system and want to conserve memory.
474 bool "Legacy (BSD) PTY support"
477 A pseudo terminal (PTY) is a software device consisting of two
478 halves: a master and a slave. The slave device behaves identical to
479 a physical terminal; the master device is used by a process to
480 read data from and write data to the slave, thereby emulating a
481 terminal. Typical programs for the master side are telnet servers
484 Linux has traditionally used the BSD-like names /dev/ptyxx
485 for masters and /dev/ttyxx for slaves of pseudo
486 terminals. This scheme has a number of problems, including
487 security. This option enables these legacy devices; on most
488 systems, it is safe to say N.
491 config LEGACY_PTY_COUNT
492 int "Maximum number of legacy PTY in use"
493 depends on LEGACY_PTYS
497 The maximum number of legacy PTYs that can be used at any one time.
498 The default is 256, and should be more than enough. Embedded
499 systems may want to reduce this to save memory.
501 When not in use, each legacy PTY occupies 12 bytes on 32-bit
502 architectures and 24 bytes on 64-bit architectures.
505 tristate 'Total Impact briQ front panel driver'
508 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
509 tristate led and two switches. It is the size of a CDROM drive.
511 If you have such one and want anything showing on the VFD then you
514 To compile this driver as a module, choose M here: the
515 module will be called briq_panel.
517 It's safe to say N here.
520 tristate "Parallel printer support"
523 If you intend to attach a printer to the parallel port of your Linux
524 box (as opposed to using a serial printer; if the connector at the
525 printer has 9 or 25 holes ["female"], then it's serial), say Y.
526 Also read the Printing-HOWTO, available from
527 <http://www.tldp.org/docs.html#howto>.
529 It is possible to share one parallel port among several devices
530 (e.g. printer and ZIP drive) and it is safe to compile the
531 corresponding drivers into the kernel.
533 To compile this driver as a module, choose M here and read
534 <file:Documentation/parport.txt>. The module will be called lp.
536 If you have several parallel ports, you can specify which ports to
537 use with the "lp" kernel command line option. (Try "man bootparam"
538 or see the documentation of your boot loader (lilo or loadlin) about
539 how to pass options to the kernel at boot time.) The syntax of the
540 "lp" command line option can be found in <file:drivers/char/lp.c>.
542 If you have more than 8 printers, you need to increase the LP_NO
543 macro in lp.c and the PARPORT_MAX macro in parport.h.
546 bool "Support for console on line printer"
549 If you want kernel messages to be printed out as they occur, you
550 can have a console on the printer. This option adds support for
551 doing that; to actually get it to happen you need to pass the
552 option "console=lp0" to the kernel at boot time.
554 If the printer is out of paper (or off, or unplugged, or too
555 busy..) the kernel will stall until the printer is ready again.
556 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
557 can make the kernel continue when this happens,
558 but it'll lose the kernel messages.
563 tristate "Support for user-space parallel port device drivers"
566 Saying Y to this adds support for /dev/parport device nodes. This
567 is needed for programs that want portable access to the parallel
568 port, for instance deviceid (which displays Plug-and-Play device
571 This is the parallel port equivalent of SCSI generic support (sg).
572 It is safe to say N to this -- it is not needed for normal printing
573 or parallel port CD-ROM/disk support.
575 To compile this driver as a module, choose M here: the
576 module will be called ppdev.
581 tristate "Texas Instruments parallel link cable support"
584 If you own a Texas Instruments graphing calculator and use a
585 parallel link cable, then you might be interested in this driver.
587 If you enable this driver, you will be able to communicate with
588 your calculator through a set of device nodes under /dev. The
589 main advantage of this driver is that you don't have to be root
590 to use this precise link cable (depending on the permissions on
591 the device nodes, though).
593 To compile this driver as a module, choose M here: the
594 module will be called tipar.
596 If you don't know what a parallel link cable is or what a Texas
597 Instruments graphing calculator is, then you probably don't need this
605 Users of pSeries machines that want to utilize the hvc console front-end
606 module for their backend console driver should select this option.
607 It will automatically be selected if one of the back-end console drivers
612 bool "pSeries Hypervisor Virtual Console support"
613 depends on PPC_PSERIES
616 pSeries machines when partitioned support a hypervisor virtual
617 console. This driver allows each pSeries partition to have a console
618 which is accessed via the HMC.
621 bool "iSeries Hypervisor Virtual Console support"
622 depends on PPC_ISERIES
626 iSeries machines support a hypervisor virtual console.
629 bool "IBM RTAS Console support"
633 IBM Console device driver which makes use of RTAS
636 bool "Toshiba's Beat Hypervisor Console support"
637 depends on PPC_CELLEB
640 Toshiba's Cell Reference Set Beat Console device driver
643 tristate "IBM Hypervisor Virtual Console Server support"
644 depends on PPC_PSERIES
646 Partitionable IBM Power5 ppc64 machines allow hosting of
647 firmware virtual consoles from one Linux partition by
648 another Linux partition. This driver allows console data
649 from Linux partitions to be accessed through TTY device
650 interfaces in the device tree of a Linux partition running
653 To compile this driver as a module, choose M here: the
654 module will be called hvcs.ko. Additionally, this module
655 will depend on arch specific APIs exported from hvcserver.ko
656 which will also be compiled when this driver is built as a
659 source "drivers/char/ipmi/Kconfig"
661 source "drivers/char/watchdog/Kconfig"
664 tristate "NetWinder thermometer support"
665 depends on ARCH_NETWINDER
667 Say Y here to include support for the thermal management hardware
668 found in the NetWinder. This driver allows the user to control the
669 temperature set points and to read the current temperature.
671 It is also possible to say M here to build it as a module (ds1620)
672 It is recommended to be used on a NetWinder, but it is not a
676 tristate "NetWinder Button"
677 depends on ARCH_NETWINDER
679 If you say Y here and create a character device node /dev/nwbutton
680 with major and minor numbers 10 and 158 ("man mknod"), then every
681 time the orange button is pressed a number of times, the number of
682 times the button was pressed will be written to that device.
684 This is most useful for applications, as yet unwritten, which
685 perform actions based on how many times the button is pressed in a
688 Do not hold the button down for too long, as the driver does not
689 alter the behaviour of the hardware reset circuitry attached to the
690 button; it will still execute a hard reset if the button is held
691 down for longer than approximately five seconds.
693 To compile this driver as a module, choose M here: the
694 module will be called nwbutton.
696 Most people will answer Y to this question and "Reboot Using Button"
697 below to be able to initiate a system shutdown from the button.
699 config NWBUTTON_REBOOT
700 bool "Reboot Using Button"
703 If you say Y here, then you will be able to initiate a system
704 shutdown and reboot by pressing the orange button a number of times.
705 The number of presses to initiate the shutdown is two by default,
706 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
707 in nwbutton.h and recompiling the driver or, if you compile the
708 driver as a module, you can specify the number of presses at load
709 time with "insmod button reboot_count=<something>".
712 tristate "NetWinder flash support"
713 depends on ARCH_NETWINDER
715 If you say Y here and create a character device /dev/flash with
716 major 10 and minor 160 you can manipulate the flash ROM containing
717 the NetWinder firmware. Be careful as accidentally overwriting the
718 flash contents can render your computer unbootable. On no account
719 allow random users access to this device. :-)
721 To compile this driver as a module, choose M here: the
722 module will be called nwflash.
724 If you're not sure, say N.
726 source "drivers/char/hw_random/Kconfig"
729 tristate "/dev/nvram support"
730 depends on ATARI || X86 || ARM || GENERIC_NVRAM
732 If you say Y here and create a character special file /dev/nvram
733 with major number 10 and minor number 144 using mknod ("man mknod"),
734 you get read and write access to the extra bytes of non-volatile
735 memory in the real time clock (RTC), which is contained in every PC
736 and most Ataris. The actual number of bytes varies, depending on the
737 nvram in the system, but is usually 114 (128-14 for the RTC).
739 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
740 on Ataris. /dev/nvram may be used to view settings there, or to
741 change them (with some utility). It could also be used to frequently
742 save a few bits of very important data that may not be lost over
743 power-off and for which writing to disk is too insecure. Note
744 however that most NVRAM space in a PC belongs to the BIOS and you
745 should NEVER idly tamper with it. See Ralf Brown's interrupt list
746 for a guide to the use of CMOS bytes by your BIOS.
748 On Atari machines, /dev/nvram is always configured and does not need
751 To compile this driver as a module, choose M here: the
752 module will be called nvram.
755 tristate "Enhanced Real Time Clock Support"
756 depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV && !ARM && !SUPERH && !S390
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 run Linux on a multiprocessor machine and said Y to
770 "Symmetric Multi Processing" above, you should say Y here to read
771 and set the RTC in an SMP compatible fashion.
773 If you think you have a use for such a device (such as periodic data
774 sampling), then say Y here, and read <file:Documentation/rtc.txt>
777 To compile this driver as a module, choose M here: the
778 module will be called rtc.
781 tristate "SGI DS1286 RTC support"
784 If you say Y here and create a character special file /dev/rtc with
785 major number 10 and minor number 135 using mknod ("man mknod"), you
786 will get access to the real time clock built into your computer.
787 Every SGI has such a clock built in. It reports status information
788 via the file /proc/rtc and its behaviour is set by various ioctls on
792 bool "SGI M48T35 RTC support"
795 If you say Y here and create a character special file /dev/rtc with
796 major number 10 and minor number 135 using mknod ("man mknod"), you
797 will get access to the real time clock built into your computer.
798 Every SGI has such a clock built in. It reports status information
799 via the file /proc/rtc and its behaviour is set by various ioctls on
803 tristate "Generic /dev/rtc emulation"
804 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH
806 If you say Y here and create a character special file /dev/rtc with
807 major number 10 and minor number 135 using mknod ("man mknod"), you
808 will get access to the real time clock (or hardware clock) built
811 It reports status information via the file /proc/driver/rtc and its
812 behaviour is set by various ioctls on /dev/rtc. If you enable the
813 "extended RTC operation" below it will also provide an emulation
814 for RTC_UIE which is required by some programs and may improve
815 precision in some cases.
817 To compile this driver as a module, choose M here: the
818 module will be called genrtc.
821 bool "Extended RTC operation"
824 Provides an emulation for RTC_UIE which is required by some programs
825 and may improve precision of the generic RTC support in some cases.
828 bool "EFI Real Time Clock Services"
832 tristate "DS1302 RTC support"
833 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
835 If you say Y here and create a character special file /dev/rtc with
836 major number 121 and minor number 0 using mknod ("man mknod"), you
837 will get access to the real time clock (or hardware clock) built
841 bool "Support for Cobalt LCD"
842 depends on MIPS_COBALT
844 This option enables support for the LCD display and buttons found
845 on Cobalt systems through a misc device.
848 tristate "Double Talk PC internal speech card support"
851 This driver is for the DoubleTalk PC, a speech synthesizer
852 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
853 called the `internal DoubleTalk'.
855 To compile this driver as a module, choose M here: the
856 module will be called dtlk.
859 tristate "Siemens R3964 line discipline"
861 This driver allows synchronous communication with devices using the
862 Siemens R3964 packet protocol. Unless you are dealing with special
863 hardware like PLCs, you are unlikely to need this.
865 To compile this driver as a module, choose M here: the
866 module will be called n_r3964.
871 tristate "Applicom intelligent fieldbus card support"
874 This driver provides the kernel-side support for the intelligent
875 fieldbus cards made by Applicom International. More information
876 about these cards can be found on the WWW at the address
877 <http://www.applicom-int.com/>, or by email from David Woodhouse
878 <dwmw2@infradead.org>.
880 To compile this driver as a module, choose M here: the
881 module will be called applicom.
886 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
887 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
889 This driver enables access to the Sony Programmable I/O Control
890 Device which can be found in many (all ?) Sony Vaio laptops.
892 If you have one of those laptops, read
893 <file:Documentation/sonypi.txt>, and say Y or M here.
895 To compile this driver as a module, choose M here: the
896 module will be called sonypi.
899 tristate "TANBAC TB0219 GPIO support"
900 depends on TANBAC_TB022X
903 source "drivers/char/agp/Kconfig"
905 source "drivers/char/drm/Kconfig"
907 source "drivers/char/pcmcia/Kconfig"
910 tristate "ACP Modem (Mwave) support"
914 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
915 kernel driver and a user level application. Together these components
916 support direct attachment to public switched telephone networks (PSTNs)
917 and support selected world wide countries.
919 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
920 600, and 770 that include on board ACP modem hardware.
922 The modem also supports the standard communications port interface
923 (ttySx) and is compatible with the Hayes AT Command Set.
925 The user level application needed to use this driver can be found at
926 the IBM Linux Technology Center (LTC) web site:
927 <http://www.ibm.com/linux/ltc/>.
929 If you own one of the above IBM Thinkpads which has the Mwave chipset
932 To compile this driver as a module, choose M here: the
933 module will be called mwave.
936 tristate "NatSemi SCx200 GPIO Support"
940 Give userspace access to the GPIO pins on the National
941 Semiconductor SCx200 processors.
943 If compiled as a module, it will be called scx200_gpio.
946 tristate "NatSemi PC8736x GPIO Support"
948 default SCx200_GPIO # mostly N
949 select NSC_GPIO # needed for support routines
951 Give userspace access to the GPIO pins on the National
952 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
953 has multiple functional units, inc several managed by
954 hwmon/pc87360 driver. Tested with PC-87366
956 If compiled as a module, it will be called pc8736x_gpio.
959 tristate "NatSemi Base GPIO Support"
961 # selected by SCx200_GPIO and PC8736x_GPIO
962 # what about 2 selectors differing: m != y
964 Common support used (and needed) by scx200_gpio and
965 pc8736x_gpio drivers. If those drivers are built as
966 modules, this one will be too, named nsc_gpio
969 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
972 Give userspace access to the GPIO pins on the AMD CS5535 and
973 CS5536 Geode companion devices.
975 If compiled as a module, it will be called cs5535_gpio.
978 tristate "NEC VR4100 series General-purpose I/O Unit support"
979 depends on CPU_VR41XX
982 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
985 The raw driver permits block devices to be bound to /dev/raw/rawN.
986 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
987 See the raw(8) manpage for more details.
989 The raw driver is deprecated and will be removed soon.
990 Applications should simply open the device (eg /dev/hda1)
991 with the O_DIRECT flag.
994 int "Maximum number of RAW devices to support (1-8192)"
995 depends on RAW_DRIVER
998 The maximum number of RAW devices that are supported.
999 Default is 256. Increase this number in case you need lots of
1003 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1007 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1008 open selects one of the timers supported by the HPET. The timers are
1009 non-periodic and/or periodic.
1012 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1016 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1017 is assumed the platform called hpet_alloc with the RTC IRQ values for
1021 bool "Allow mmap of HPET"
1025 If you say Y here, user applications will be able to mmap
1028 In some hardware implementations, the page containing HPET
1029 registers may also contain other things that shouldn't be
1030 exposed to the user. If this applies to your hardware,
1033 config HANGCHECK_TIMER
1034 tristate "Hangcheck timer"
1035 depends on X86 || IA64 || PPC64 || S390
1037 The hangcheck-timer module detects when the system has gone
1038 out to lunch past a certain margin. It can reboot the system
1039 or merely print a warning.
1042 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1043 depends on IA64_GENERIC || IA64_SGI_SN2
1046 The mmtimer device allows direct userspace access to the
1049 source "drivers/char/tpm/Kconfig"
1052 tristate "Telecom clock driver for ATCA SBC"
1053 depends on EXPERIMENTAL && X86
1056 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1057 ATCA computers and allows direct userspace access to the
1058 configuration of the telecom clock configuration settings. This
1059 device is used for hardware synchronization across the ATCA backplane
1060 fabric. Upon loading, the driver exports a sysfs directory,
1061 /sys/devices/platform/telco_clock, with a number of files for
1062 controlling the behavior of this hardware.
1067 depends on ISA || PCI
1070 source "drivers/s390/char/Kconfig"
projects / linux-2.6-omap-h63xx.git / blob