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 :-)
39 config CONSOLE_TRANSLATIONS
42 bool "Enable character translations in console" if EMBEDDED
44 This enables support for font mapping and Unicode translation
48 bool "Support for console on virtual terminal" if EMBEDDED
52 The system console is the device which receives all kernel messages
53 and warnings and which allows logins in single user mode. If you
54 answer Y here, a virtual terminal (the device used to interact with
55 a physical terminal) can be used as system console. This is the most
56 common mode of operations, so you should say Y here unless you want
57 the kernel messages be output only to a serial port (in which case
58 you should say Y to "Console on serial port", below).
60 If you do say Y here, by default the currently visible virtual
61 terminal (/dev/tty0) will be used as system console. You can change
62 that with a kernel command line option such as "console=tty3" which
63 would use the third virtual terminal as system console. (Try "man
64 bootparam" or see the documentation of your boot loader (lilo or
65 loadlin) about how to pass options to the kernel at boot time.)
71 depends on VT && !S390 && !UML
74 config VT_HW_CONSOLE_BINDING
75 bool "Support for binding and unbinding console drivers"
79 The virtual terminal is the device that interacts with the physical
80 terminal through console drivers. On these systems, at least one
81 console driver is loaded. In other configurations, additional console
82 drivers may be enabled, such as the framebuffer console. If more than
83 1 console driver is enabled, setting this to 'y' will allow you to
84 select the console driver that will serve as the backend for the
87 See <file:Documentation/console/console.txt> for more
88 information. For framebuffer console users, please refer to
89 <file:Documentation/fb/fbcon.txt>.
92 bool "/dev/kmem virtual device support"
95 Say Y here if you want to support the /dev/kmem device. The
96 /dev/kmem device is rarely used, but can be used for certain
97 kind of kernel debugging operations.
98 When in doubt, say "N".
100 config SERIAL_NONSTANDARD
101 bool "Non-standard serial port support"
104 Say Y here if you have any non-standard serial boards -- boards
105 which aren't supported using the standard "dumb" serial driver.
106 This includes intelligent serial boards such as Cyclades,
107 Digiboards, etc. These are usually used for systems that need many
108 serial ports because they serve many terminals or dial-in
111 Note that the answer to this question won't directly affect the
112 kernel: saying N will just cause the configurator to skip all
113 the questions about non-standard serial boards.
115 Most people can say N here.
118 tristate "Computone IntelliPort Plus serial support"
119 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
121 This driver supports the entire family of Intelliport II/Plus
122 controllers with the exception of the MicroChannel controllers and
123 products previous to the Intelliport II. These are multiport cards,
124 which give you many serial ports. You would need something like this
125 to connect more than two modems to your Linux box, for instance in
126 order to become a dial-in server. If you have a card like that, say
127 Y here and read <file:Documentation/computone.txt>.
129 To compile this driver as module, choose M here: the
130 module will be called ip2.
133 tristate "Comtrol RocketPort support"
134 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
136 This driver supports Comtrol RocketPort and RocketModem PCI boards.
137 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
138 modems. For information about the RocketPort/RocketModem boards
139 and this driver read <file:Documentation/rocket.txt>.
141 To compile this driver as a module, choose M here: the
142 module will be called rocket.
144 If you want to compile this driver into the kernel, say Y here. If
145 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
148 tristate "Cyclades async mux support"
149 depends on SERIAL_NONSTANDARD && (PCI || ISA)
152 This driver supports Cyclades Z and Y multiserial boards.
153 You would need something like this to connect more than two modems to
154 your Linux box, for instance in order to become a dial-in server.
156 For information about the Cyclades-Z card, read
157 <file:Documentation/README.cycladesZ>.
159 To compile this driver as a module, choose M here: the
160 module will be called cyclades.
162 If you haven't heard about it, it's safe to say N.
165 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
166 depends on EXPERIMENTAL && CYCLADES
168 The Cyclades-Z family of multiport cards allows 2 (two) driver op
169 modes: polling and interrupt. In polling mode, the driver will check
170 the status of the Cyclades-Z ports every certain amount of time
171 (which is called polling cycle and is configurable). In interrupt
172 mode, it will use an interrupt line (IRQ) in order to check the
173 status of the Cyclades-Z ports. The default op mode is polling. If
177 tristate "Digiboard Intelligent Async Support"
178 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
180 This is a driver for Digi International's Xx, Xeve, and Xem series
181 of cards which provide multiple serial ports. You would need
182 something like this to connect more than two modems to your Linux
183 box, for instance in order to become a dial-in server. This driver
184 supports the original PC (ISA) boards as well as PCI, and EISA. If
185 you have a card like this, say Y here and read the file
186 <file:Documentation/digiepca.txt>.
188 To compile this driver as a module, choose M here: the
189 module will be called epca.
192 tristate "Hayes ESP serial port support"
193 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
195 This is a driver which supports Hayes ESP serial ports. Both single
196 port cards and multiport cards are supported. Make sure to read
197 <file:Documentation/hayes-esp.txt>.
199 To compile this driver as a module, choose M here: the
200 module will be called esp.
205 tristate "Moxa Intellio support"
206 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
209 Say Y here if you have a Moxa Intellio multiport serial card.
211 To compile this driver as a module, choose M here: the
212 module will be called moxa.
215 tristate "Moxa SmartIO support v. 2.0"
216 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
218 Say Y here if you have a Moxa SmartIO multiport serial card and/or
219 want to help develop a new version of this driver.
221 This is upgraded (1.9.1) driver from original Moxa drivers with
222 changes finally resulting in PCI probing.
224 This driver can also be built as a module. The module will be called
225 mxser. If you want to do that, say M here.
228 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
229 depends on SERIAL_NONSTANDARD && PCI
232 This is a driver for the Multi-Tech cards which provide several
233 serial ports. The driver is experimental and can currently only be
234 built as a module. The module will be called isicom.
235 If you want to do that, choose M here.
238 tristate "Microgate SyncLink card support"
239 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
241 Provides support for the SyncLink ISA and PCI multiprotocol serial
242 adapters. These adapters support asynchronous and HDLC bit
243 synchronous communication up to 10Mbps (PCI adapter).
245 This driver can only be built as a module ( = code which can be
246 inserted in and removed from the running kernel whenever you want).
247 The module will be called synclink. If you want to do that, say M
251 tristate "SyncLink Multiport support"
252 depends on SERIAL_NONSTANDARD && PCI
254 Enable support for the SyncLink Multiport (2 or 4 ports)
255 serial adapter, running asynchronous and HDLC communications up
256 to 2.048Mbps. Each ports is independently selectable for
257 RS-232, V.35, RS-449, RS-530, and X.21
259 This driver may be built as a module ( = code which can be
260 inserted in and removed from the running kernel whenever you want).
261 The module will be called synclinkmp. If you want to do that, say M
265 tristate "SyncLink GT/AC support"
266 depends on SERIAL_NONSTANDARD && PCI
268 Support for SyncLink GT and SyncLink AC families of
269 synchronous and asynchronous serial adapters
270 manufactured by Microgate Systems, Ltd. (www.microgate.com)
273 tristate "HDLC line discipline support"
274 depends on SERIAL_NONSTANDARD
276 Allows synchronous HDLC communications with tty device drivers that
277 support synchronous HDLC such as the Microgate SyncLink adapter.
279 This driver can only be built as a module ( = code which can be
280 inserted in and removed from the running kernel whenever you want).
281 The module will be called n_hdlc. If you want to do that, say M
285 tristate "SDL RISCom/8 card support"
286 depends on SERIAL_NONSTANDARD
288 This is a driver for the SDL Communications RISCom/8 multiport card,
289 which gives you many serial ports. You would need something like
290 this to connect more than two modems to your Linux box, for instance
291 in order to become a dial-in server. If you have a card like that,
292 say Y here and read the file <file:Documentation/riscom8.txt>.
294 Also it's possible to say M here and compile this driver as kernel
295 loadable module; the module will be called riscom8.
298 tristate "Specialix IO8+ card support"
299 depends on SERIAL_NONSTANDARD
301 This is a driver for the Specialix IO8+ multiport card (both the
302 ISA and the PCI version) which gives you many serial ports. You
303 would need something like this to connect more than two modems to
304 your Linux box, for instance in order to become a dial-in server.
306 If you have a card like that, say Y here and read the file
307 <file:Documentation/specialix.txt>. Also it's possible to say M here
308 and compile this driver as kernel loadable module which will be
312 tristate "Specialix SX (and SI) card support"
313 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
315 This is a driver for the SX and SI multiport serial cards.
316 Please read the file <file:Documentation/sx.txt> for details.
318 This driver can only be built as a module ( = code which can be
319 inserted in and removed from the running kernel whenever you want).
320 The module will be called sx. If you want to do that, say M here.
323 tristate "Specialix RIO system support"
324 depends on SERIAL_NONSTANDARD
326 This is a driver for the Specialix RIO, a smart serial card which
327 drives an outboard box that can support up to 128 ports. Product
328 information is at <http://www.perle.com/support/documentation.html#multiport>.
329 There are both ISA and PCI versions.
332 bool "Support really old RIO/PCI cards"
335 Older RIO PCI cards need some initialization-time configuration to
336 determine the IRQ and some control addresses. If you have a RIO and
337 this doesn't seem to work, try setting this to Y.
340 bool "Stallion multiport serial support"
341 depends on SERIAL_NONSTANDARD
343 Stallion cards give you many serial ports. You would need something
344 like this to connect more than two modems to your Linux box, for
345 instance in order to become a dial-in server. If you say Y here,
346 you will be asked for your specific card model in the next
347 questions. Make sure to read <file:Documentation/stallion.txt> in
348 this case. If you have never heard about all this, it's safe to
352 tristate "Stallion EasyIO or EC8/32 support"
353 depends on STALDRV && (ISA || EISA || PCI)
355 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
356 card, then this is for you; say Y. Make sure to read
357 <file:Documentation/stallion.txt>.
359 To compile this driver as a module, choose M here: the
360 module will be called stallion.
363 tristate "Stallion EC8/64, ONboard, Brumby support"
364 depends on STALDRV && (ISA || EISA || PCI)
366 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
367 serial multiport card, say Y here. Make sure to read
368 <file:Documentation/stallion.txt>.
370 To compile this driver as a module, choose M here: the
371 module will be called istallion.
374 tristate "HSDPA Broadband Wireless Data Card - Globe Trotter"
375 depends on PCI && EXPERIMENTAL
377 If you have a HSDPA driver Broadband Wireless Data Card -
378 Globe Trotter PCMCIA card, say Y here.
380 To compile this driver as a module, choose M here, the module
381 will be called nozomi.
384 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
385 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
387 This option supports the 2232 7-port serial card shipped with the
388 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
389 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
390 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
391 ports were connected with 8 pin DIN connectors on the card bracket,
392 for which 8 pin to DB25 adapters were supplied. The card also had
393 jumpers internally to toggle various pinning configurations.
395 This driver can be built as a module; but then "generic_serial"
396 will also be built as a module. This has to be loaded before
397 "ser_a2232". If you want to do this, answer M here.
400 bool "SGI Altix system controller communication support"
401 depends on (IA64_SGI_SN2 || IA64_GENERIC)
403 If you have an SGI Altix and you want to enable system
404 controller communication from user space (you want this!),
405 say Y. Otherwise, say N.
408 bool "SGI TIO CX driver support"
409 depends on (IA64_SGI_SN2 || IA64_GENERIC)
411 If you have an SGI Altix and you have fpga devices attached
412 to your TIO, say Y here, otherwise say N.
415 tristate "SGI FPGA Core Services driver support"
418 If you have an SGI Altix with an attached SABrick
419 say Y or M here, otherwise say N.
421 source "drivers/serial/Kconfig"
424 bool "Unix98 PTY support" if EMBEDDED
427 A pseudo terminal (PTY) is a software device consisting of two
428 halves: a master and a slave. The slave device behaves identical to
429 a physical terminal; the master device is used by a process to
430 read data from and write data to the slave, thereby emulating a
431 terminal. Typical programs for the master side are telnet servers
434 Linux has traditionally used the BSD-like names /dev/ptyxx for
435 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
436 has a number of problems. The GNU C library glibc 2.1 and later,
437 however, supports the Unix98 naming standard: in order to acquire a
438 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
439 terminal is then made available to the process and the pseudo
440 terminal slave can be accessed as /dev/pts/<number>. What was
441 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
443 All modern Linux systems use the Unix98 ptys. Say Y unless
444 you're on an embedded system and want to conserve memory.
447 bool "Legacy (BSD) PTY support"
450 A pseudo terminal (PTY) is a software device consisting of two
451 halves: a master and a slave. The slave device behaves identical to
452 a physical terminal; the master device is used by a process to
453 read data from and write data to the slave, thereby emulating a
454 terminal. Typical programs for the master side are telnet servers
457 Linux has traditionally used the BSD-like names /dev/ptyxx
458 for masters and /dev/ttyxx for slaves of pseudo
459 terminals. This scheme has a number of problems, including
460 security. This option enables these legacy devices; on most
461 systems, it is safe to say N.
464 config LEGACY_PTY_COUNT
465 int "Maximum number of legacy PTY in use"
466 depends on LEGACY_PTYS
470 The maximum number of legacy PTYs that can be used at any one time.
471 The default is 256, and should be more than enough. Embedded
472 systems may want to reduce this to save memory.
474 When not in use, each legacy PTY occupies 12 bytes on 32-bit
475 architectures and 24 bytes on 64-bit architectures.
478 tristate 'Total Impact briQ front panel driver'
481 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
482 tristate led and two switches. It is the size of a CDROM drive.
484 If you have such one and want anything showing on the VFD then you
487 To compile this driver as a module, choose M here: the
488 module will be called briq_panel.
490 It's safe to say N here.
493 tristate "Blackfin On-Chip OTP Memory Support"
494 depends on BLACKFIN && (BF52x || BF54x)
497 If you say Y here, you will get support for a character device
498 interface into the One Time Programmable memory pages that are
499 stored on the Blackfin processor. This will not get you access
500 to the secure memory pages however. You will need to write your
501 own secure code and reader for that.
503 To compile this driver as a module, choose M here: the module
504 will be called bfin-otp.
506 If unsure, it is safe to say Y.
508 config BFIN_OTP_WRITE_ENABLE
509 bool "Enable writing support of OTP pages"
513 If you say Y here, you will enable support for writing of the
514 OTP pages. This is dangerous by nature as you can only program
515 the pages once, so only enable this option when you actually
516 need it so as to not inadvertently clobber data.
521 tristate "Parallel printer support"
524 If you intend to attach a printer to the parallel port of your Linux
525 box (as opposed to using a serial printer; if the connector at the
526 printer has 9 or 25 holes ["female"], then it's serial), say Y.
527 Also read the Printing-HOWTO, available from
528 <http://www.tldp.org/docs.html#howto>.
530 It is possible to share one parallel port among several devices
531 (e.g. printer and ZIP drive) and it is safe to compile the
532 corresponding drivers into the kernel.
534 To compile this driver as a module, choose M here and read
535 <file:Documentation/parport.txt>. The module will be called lp.
537 If you have several parallel ports, you can specify which ports to
538 use with the "lp" kernel command line option. (Try "man bootparam"
539 or see the documentation of your boot loader (lilo or loadlin) about
540 how to pass options to the kernel at boot time.) The syntax of the
541 "lp" command line option can be found in <file:drivers/char/lp.c>.
543 If you have more than 8 printers, you need to increase the LP_NO
544 macro in lp.c and the PARPORT_MAX macro in parport.h.
547 bool "Support for console on line printer"
550 If you want kernel messages to be printed out as they occur, you
551 can have a console on the printer. This option adds support for
552 doing that; to actually get it to happen you need to pass the
553 option "console=lp0" to the kernel at boot time.
555 If the printer is out of paper (or off, or unplugged, or too
556 busy..) the kernel will stall until the printer is ready again.
557 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
558 can make the kernel continue when this happens,
559 but it'll lose the kernel messages.
564 tristate "Support for user-space parallel port device drivers"
567 Saying Y to this adds support for /dev/parport device nodes. This
568 is needed for programs that want portable access to the parallel
569 port, for instance deviceid (which displays Plug-and-Play device
572 This is the parallel port equivalent of SCSI generic support (sg).
573 It is safe to say N to this -- it is not needed for normal printing
574 or parallel port CD-ROM/disk support.
576 To compile this driver as a module, choose M here: the
577 module will be called ppdev.
584 Generic "hypervisor virtual console" infrastructure for various
585 hypervisors (pSeries, iSeries, Xen, lguest).
586 It will automatically be selected if one of the back-end console drivers
593 bool "pSeries Hypervisor Virtual Console support"
594 depends on PPC_PSERIES
598 pSeries machines when partitioned support a hypervisor virtual
599 console. This driver allows each pSeries partition to have a console
600 which is accessed via the HMC.
603 bool "iSeries Hypervisor Virtual Console support"
604 depends on PPC_ISERIES
609 iSeries machines support a hypervisor virtual console.
612 bool "IBM RTAS Console support"
616 IBM Console device driver which makes use of RTAS
619 bool "Toshiba's Beat Hypervisor Console support"
620 depends on PPC_CELLEB
623 Toshiba's Cell Reference Set Beat Console device driver
626 bool "Xen Hypervisor Console support"
632 Xen virtual console device driver
634 config VIRTIO_CONSOLE
635 tristate "Virtio console"
639 Virtio console for use with lguest and other hypervisors.
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
660 tristate "IBM POWER Barrier Synchronization Register support"
661 depends on PPC_PSERIES
663 This devices exposes a hardware mechanism for fast synchronization
664 of threads across a large system which avoids bouncing a cacheline
665 between several cores on a system
667 source "drivers/char/ipmi/Kconfig"
670 tristate "NetWinder thermometer support"
671 depends on ARCH_NETWINDER
673 Say Y here to include support for the thermal management hardware
674 found in the NetWinder. This driver allows the user to control the
675 temperature set points and to read the current temperature.
677 It is also possible to say M here to build it as a module (ds1620)
678 It is recommended to be used on a NetWinder, but it is not a
682 tristate "NetWinder Button"
683 depends on ARCH_NETWINDER
685 If you say Y here and create a character device node /dev/nwbutton
686 with major and minor numbers 10 and 158 ("man mknod"), then every
687 time the orange button is pressed a number of times, the number of
688 times the button was pressed will be written to that device.
690 This is most useful for applications, as yet unwritten, which
691 perform actions based on how many times the button is pressed in a
694 Do not hold the button down for too long, as the driver does not
695 alter the behaviour of the hardware reset circuitry attached to the
696 button; it will still execute a hard reset if the button is held
697 down for longer than approximately five seconds.
699 To compile this driver as a module, choose M here: the
700 module will be called nwbutton.
702 Most people will answer Y to this question and "Reboot Using Button"
703 below to be able to initiate a system shutdown from the button.
705 config NWBUTTON_REBOOT
706 bool "Reboot Using Button"
709 If you say Y here, then you will be able to initiate a system
710 shutdown and reboot by pressing the orange button a number of times.
711 The number of presses to initiate the shutdown is two by default,
712 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
713 in nwbutton.h and recompiling the driver or, if you compile the
714 driver as a module, you can specify the number of presses at load
715 time with "insmod button reboot_count=<something>".
718 tristate "NetWinder flash support"
719 depends on ARCH_NETWINDER
721 If you say Y here and create a character device /dev/flash with
722 major 10 and minor 160 you can manipulate the flash ROM containing
723 the NetWinder firmware. Be careful as accidentally overwriting the
724 flash contents can render your computer unbootable. On no account
725 allow random users access to this device. :-)
727 To compile this driver as a module, choose M here: the
728 module will be called nwflash.
730 If you're not sure, say N.
732 source "drivers/char/hw_random/Kconfig"
735 tristate "/dev/nvram support"
736 depends on ATARI || X86 || ARM || GENERIC_NVRAM
738 If you say Y here and create a character special file /dev/nvram
739 with major number 10 and minor number 144 using mknod ("man mknod"),
740 you get read and write access to the extra bytes of non-volatile
741 memory in the real time clock (RTC), which is contained in every PC
742 and most Ataris. The actual number of bytes varies, depending on the
743 nvram in the system, but is usually 114 (128-14 for the RTC).
745 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
746 on Ataris. /dev/nvram may be used to view settings there, or to
747 change them (with some utility). It could also be used to frequently
748 save a few bits of very important data that may not be lost over
749 power-off and for which writing to disk is too insecure. Note
750 however that most NVRAM space in a PC belongs to the BIOS and you
751 should NEVER idly tamper with it. See Ralf Brown's interrupt list
752 for a guide to the use of CMOS bytes by your BIOS.
754 On Atari machines, /dev/nvram is always configured and does not need
757 To compile this driver as a module, choose M here: the
758 module will be called nvram.
761 # These legacy RTC drivers just cause too many conflicts with the generic
762 # RTC framework ... let's not even try to coexist any more.
767 tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
768 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
769 && !ARM && !SUPERH && !S390 && !AVR32
771 If you say Y here and create a character special file /dev/rtc with
772 major number 10 and minor number 135 using mknod ("man mknod"), you
773 will get access to the real time clock (or hardware clock) built
776 Every PC has such a clock built in. It can be used to generate
777 signals from as low as 1Hz up to 8192Hz, and can also be used
778 as a 24 hour alarm. It reports status information via the file
779 /proc/driver/rtc and its behaviour is set by various ioctls on
782 If you run Linux on a multiprocessor machine and said Y to
783 "Symmetric Multi Processing" above, you should say Y here to read
784 and set the RTC in an SMP compatible fashion.
786 If you think you have a use for such a device (such as periodic data
787 sampling), then say Y here, and read <file:Documentation/rtc.txt>
790 To compile this driver as a module, choose M here: the
791 module will be called rtc.
794 tristate "Enhanced Real Time Clock Support"
795 depends on SPARC32 && PCI
797 If you say Y here and create a character special file /dev/rtc with
798 major number 10 and minor number 135 using mknod ("man mknod"), you
799 will get access to the real time clock (or hardware clock) built
802 Every PC has such a clock built in. It can be used to generate
803 signals from as low as 1Hz up to 8192Hz, and can also be used
804 as a 24 hour alarm. It reports status information via the file
805 /proc/driver/rtc and its behaviour is set by various ioctls on
808 If you think you have a use for such a device (such as periodic data
809 sampling), then say Y here, and read <file:Documentation/rtc.txt>
812 To compile this driver as a module, choose M here: the
813 module will be called js-rtc.
816 tristate "Generic /dev/rtc emulation"
817 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32
819 If you say Y here and create a character special file /dev/rtc with
820 major number 10 and minor number 135 using mknod ("man mknod"), you
821 will get access to the real time clock (or hardware clock) built
824 It reports status information via the file /proc/driver/rtc and its
825 behaviour is set by various ioctls on /dev/rtc. If you enable the
826 "extended RTC operation" below it will also provide an emulation
827 for RTC_UIE which is required by some programs and may improve
828 precision in some cases.
830 To compile this driver as a module, choose M here: the
831 module will be called genrtc.
834 bool "Extended RTC operation"
837 Provides an emulation for RTC_UIE which is required by some programs
838 and may improve precision of the generic RTC support in some cases.
841 bool "EFI Real Time Clock Services"
845 tristate "DS1302 RTC support"
846 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
848 If you say Y here and create a character special file /dev/rtc with
849 major number 121 and minor number 0 using mknod ("man mknod"), you
850 will get access to the real time clock (or hardware clock) built
856 tristate "Double Talk PC internal speech card support"
859 This driver is for the DoubleTalk PC, a speech synthesizer
860 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
861 called the `internal DoubleTalk'.
863 To compile this driver as a module, choose M here: the
864 module will be called dtlk.
867 tristate "Xilinx HWICAP Support"
868 depends on XILINX_VIRTEX
870 This option enables support for Xilinx Internal Configuration
871 Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
872 FPGA platforms to partially reconfigure the FPGA at runtime.
877 tristate "Siemens R3964 line discipline"
879 This driver allows synchronous communication with devices using the
880 Siemens R3964 packet protocol. Unless you are dealing with special
881 hardware like PLCs, you are unlikely to need this.
883 To compile this driver as a module, choose M here: the
884 module will be called n_r3964.
889 tristate "Applicom intelligent fieldbus card support"
892 This driver provides the kernel-side support for the intelligent
893 fieldbus cards made by Applicom International. More information
894 about these cards can be found on the WWW at the address
895 <http://www.applicom-int.com/>, or by email from David Woodhouse
896 <dwmw2@infradead.org>.
898 To compile this driver as a module, choose M here: the
899 module will be called applicom.
904 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
905 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
907 This driver enables access to the Sony Programmable I/O Control
908 Device which can be found in many (all ?) Sony Vaio laptops.
910 If you have one of those laptops, read
911 <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
913 To compile this driver as a module, choose M here: the
914 module will be called sonypi.
917 tristate "TANBAC TB0219 GPIO support"
918 depends on TANBAC_TB022X
921 source "drivers/char/pcmcia/Kconfig"
924 tristate "ACP Modem (Mwave) support"
928 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
929 kernel driver and a user level application. Together these components
930 support direct attachment to public switched telephone networks (PSTNs)
931 and support selected world wide countries.
933 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
934 600, and 770 that include on board ACP modem hardware.
936 The modem also supports the standard communications port interface
937 (ttySx) and is compatible with the Hayes AT Command Set.
939 The user level application needed to use this driver can be found at
940 the IBM Linux Technology Center (LTC) web site:
941 <http://www.ibm.com/linux/ltc/>.
943 If you own one of the above IBM Thinkpads which has the Mwave chipset
946 To compile this driver as a module, choose M here: the
947 module will be called mwave.
950 tristate "NatSemi SCx200 GPIO Support"
954 Give userspace access to the GPIO pins on the National
955 Semiconductor SCx200 processors.
957 If compiled as a module, it will be called scx200_gpio.
960 tristate "NatSemi PC8736x GPIO Support"
962 default SCx200_GPIO # mostly N
963 select NSC_GPIO # needed for support routines
965 Give userspace access to the GPIO pins on the National
966 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
967 has multiple functional units, inc several managed by
968 hwmon/pc87360 driver. Tested with PC-87366
970 If compiled as a module, it will be called pc8736x_gpio.
973 tristate "NatSemi Base GPIO Support"
975 # selected by SCx200_GPIO and PC8736x_GPIO
976 # what about 2 selectors differing: m != y
978 Common support used (and needed) by scx200_gpio and
979 pc8736x_gpio drivers. If those drivers are built as
980 modules, this one will be too, named nsc_gpio
983 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
986 Give userspace access to the GPIO pins on the AMD CS5535 and
987 CS5536 Geode companion devices.
989 If compiled as a module, it will be called cs5535_gpio.
992 tristate "NEC VR4100 series General-purpose I/O Unit support"
993 depends on CPU_VR41XX
996 tristate "RAW driver (/dev/raw/rawN)"
999 The raw driver permits block devices to be bound to /dev/raw/rawN.
1000 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
1001 See the raw(8) manpage for more details.
1003 Applications should preferably open the device (eg /dev/hda1)
1004 with the O_DIRECT flag.
1007 int "Maximum number of RAW devices to support (1-8192)"
1008 depends on RAW_DRIVER
1011 The maximum number of RAW devices that are supported.
1012 Default is 256. Increase this number in case you need lots of
1016 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1020 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1021 open selects one of the timers supported by the HPET. The timers are
1022 non-periodic and/or periodic.
1025 bool "Allow mmap of HPET"
1029 If you say Y here, user applications will be able to mmap
1032 In some hardware implementations, the page containing HPET
1033 registers may also contain other things that shouldn't be
1034 exposed to the user. If this applies to your hardware,
1037 config HANGCHECK_TIMER
1038 tristate "Hangcheck timer"
1039 depends on X86 || IA64 || PPC64 || S390
1041 The hangcheck-timer module detects when the system has gone
1042 out to lunch past a certain margin. It can reboot the system
1043 or merely print a warning.
1046 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1047 depends on IA64_GENERIC || IA64_SGI_SN2
1050 The mmtimer device allows direct userspace access to the
1053 source "drivers/char/tpm/Kconfig"
1056 tristate "Telecom clock driver for ATCA SBC"
1057 depends on EXPERIMENTAL && X86
1060 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1061 ATCA computers and allows direct userspace access to the
1062 configuration of the telecom clock configuration settings. This
1063 device is used for hardware synchronization across the ATCA backplane
1064 fabric. Upon loading, the driver exports a sysfs directory,
1065 /sys/devices/platform/telco_clock, with a number of files for
1066 controlling the behavior of this hardware.
1071 depends on ISA || PCI
1074 source "drivers/s390/char/Kconfig"
projects / linux-2.6 / blob