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>.
84 bool "/dev/kmem virtual device support"
87 Say Y here if you want to support the /dev/kmem device. The
88 /dev/kmem device is rarely used, but can be used for certain
89 kind of kernel debugging operations.
90 When in doubt, say "N".
92 config SERIAL_NONSTANDARD
93 bool "Non-standard serial port support"
96 Say Y here if you have any non-standard serial boards -- boards
97 which aren't supported using the standard "dumb" serial driver.
98 This includes intelligent serial boards such as Cyclades,
99 Digiboards, etc. These are usually used for systems that need many
100 serial ports because they serve many terminals or dial-in
103 Note that the answer to this question won't directly affect the
104 kernel: saying N will just cause the configurator to skip all
105 the questions about non-standard serial boards.
107 Most people can say N here.
110 tristate "Computone IntelliPort Plus serial support"
111 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
113 This driver supports the entire family of Intelliport II/Plus
114 controllers with the exception of the MicroChannel controllers and
115 products previous to the Intelliport II. These are multiport cards,
116 which give you many serial ports. You would need something like this
117 to connect more than two modems to your Linux box, for instance in
118 order to become a dial-in server. If you have a card like that, say
119 Y here and read <file:Documentation/computone.txt>.
121 To compile this driver as module, choose M here: the
122 module will be called ip2.
125 tristate "Comtrol RocketPort support"
126 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
128 This driver supports Comtrol RocketPort and RocketModem PCI boards.
129 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
130 modems. For information about the RocketPort/RocketModem boards
131 and this driver read <file:Documentation/rocket.txt>.
133 To compile this driver as a module, choose M here: the
134 module will be called rocket.
136 If you want to compile this driver into the kernel, say Y here. If
137 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
140 tristate "Cyclades async mux support"
141 depends on SERIAL_NONSTANDARD && (PCI || ISA)
144 This driver supports Cyclades Z and Y multiserial boards.
145 You would need something like this to connect more than two modems to
146 your Linux box, for instance in order to become a dial-in server.
148 For information about the Cyclades-Z card, read
149 <file:Documentation/README.cycladesZ>.
151 To compile this driver as a module, choose M here: the
152 module will be called cyclades.
154 If you haven't heard about it, it's safe to say N.
157 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
158 depends on EXPERIMENTAL && CYCLADES
160 The Cyclades-Z family of multiport cards allows 2 (two) driver op
161 modes: polling and interrupt. In polling mode, the driver will check
162 the status of the Cyclades-Z ports every certain amount of time
163 (which is called polling cycle and is configurable). In interrupt
164 mode, it will use an interrupt line (IRQ) in order to check the
165 status of the Cyclades-Z ports. The default op mode is polling. If
169 tristate "Digiboard Intelligent Async Support"
170 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
172 This is a driver for Digi International's Xx, Xeve, and Xem series
173 of cards which provide multiple serial ports. You would need
174 something like this to connect more than two modems to your Linux
175 box, for instance in order to become a dial-in server. This driver
176 supports the original PC (ISA) boards as well as PCI, and EISA. If
177 you have a card like this, say Y here and read the file
178 <file:Documentation/digiepca.txt>.
180 To compile this driver as a module, choose M here: the
181 module will be called epca.
184 tristate "Hayes ESP serial port support"
185 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
187 This is a driver which supports Hayes ESP serial ports. Both single
188 port cards and multiport cards are supported. Make sure to read
189 <file:Documentation/hayes-esp.txt>.
191 To compile this driver as a module, choose M here: the
192 module will be called esp.
197 tristate "Moxa Intellio support"
198 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
201 Say Y here if you have a Moxa Intellio multiport serial card.
203 To compile this driver as a module, choose M here: the
204 module will be called moxa.
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 This driver can also be built as a module. The module will be called
217 mxser. If you want to do that, say M here.
220 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
221 depends on SERIAL_NONSTANDARD && PCI
224 This is a driver for the Multi-Tech cards which provide several
225 serial ports. The driver is experimental and can currently only be
226 built as a module. The module will be called isicom.
227 If you want to do that, choose M here.
230 tristate "Microgate SyncLink card support"
231 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
233 Provides support for the SyncLink ISA and PCI multiprotocol serial
234 adapters. These adapters support asynchronous and HDLC bit
235 synchronous communication up to 10Mbps (PCI adapter).
237 This driver can only be built as a module ( = code which can be
238 inserted in and removed from the running kernel whenever you want).
239 The module will be called synclink. If you want to do that, say M
243 tristate "SyncLink Multiport support"
244 depends on SERIAL_NONSTANDARD && PCI
246 Enable support for the SyncLink Multiport (2 or 4 ports)
247 serial adapter, running asynchronous and HDLC communications up
248 to 2.048Mbps. Each ports is independently selectable for
249 RS-232, V.35, RS-449, RS-530, and X.21
251 This driver may be built as a module ( = code which can be
252 inserted in and removed from the running kernel whenever you want).
253 The module will be called synclinkmp. If you want to do that, say M
257 tristate "SyncLink GT/AC support"
258 depends on SERIAL_NONSTANDARD && PCI
260 Support for SyncLink GT and SyncLink AC families of
261 synchronous and asynchronous serial adapters
262 manufactured by Microgate Systems, Ltd. (www.microgate.com)
265 tristate "HDLC line discipline support"
266 depends on SERIAL_NONSTANDARD
268 Allows synchronous HDLC communications with tty device drivers that
269 support synchronous HDLC such as the Microgate SyncLink adapter.
271 This driver can only be built as a module ( = code which can be
272 inserted in and removed from the running kernel whenever you want).
273 The module will be called n_hdlc. If you want to do that, say M
277 tristate "SDL RISCom/8 card support"
278 depends on SERIAL_NONSTANDARD
280 This is a driver for the SDL Communications RISCom/8 multiport card,
281 which gives you many serial ports. You would need something like
282 this to connect more than two modems to your Linux box, for instance
283 in order to become a dial-in server. If you have a card like that,
284 say Y here and read the file <file:Documentation/riscom8.txt>.
286 Also it's possible to say M here and compile this driver as kernel
287 loadable module; the module will be called riscom8.
290 tristate "Specialix IO8+ card support"
291 depends on SERIAL_NONSTANDARD
293 This is a driver for the Specialix IO8+ multiport card (both the
294 ISA and the PCI version) which gives you many serial ports. You
295 would need something like this to connect more than two modems to
296 your Linux box, for instance in order to become a dial-in server.
298 If you have a card like that, say Y here and read the file
299 <file:Documentation/specialix.txt>. Also it's possible to say M here
300 and compile this driver as kernel loadable module which will be
303 config SPECIALIX_RTSCTS
304 bool "Specialix DTR/RTS pin is RTS"
307 The Specialix IO8+ card can only support either RTS or DTR. If you
308 say N here, the driver will use the pin as "DTR" when the tty is in
309 software handshake mode. If you say Y here or hardware handshake is
310 on, it will always be RTS. Read the file
311 <file:Documentation/specialix.txt> for more information.
314 tristate "Specialix SX (and SI) card support"
315 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
317 This is a driver for the SX and SI multiport serial cards.
318 Please read the file <file:Documentation/sx.txt> for details.
320 This driver can only be built as a module ( = code which can be
321 inserted in and removed from the running kernel whenever you want).
322 The module will be called sx. If you want to do that, say M here.
325 tristate "Specialix RIO system support"
326 depends on SERIAL_NONSTANDARD
328 This is a driver for the Specialix RIO, a smart serial card which
329 drives an outboard box that can support up to 128 ports. Product
330 information is at <http://www.perle.com/support/documentation.html#multiport>.
331 There are both ISA and PCI versions.
334 bool "Support really old RIO/PCI cards"
337 Older RIO PCI cards need some initialization-time configuration to
338 determine the IRQ and some control addresses. If you have a RIO and
339 this doesn't seem to work, try setting this to Y.
342 bool "Stallion multiport serial support"
343 depends on SERIAL_NONSTANDARD
345 Stallion cards give you many serial ports. You would need something
346 like this to connect more than two modems to your Linux box, for
347 instance in order to become a dial-in server. If you say Y here,
348 you will be asked for your specific card model in the next
349 questions. Make sure to read <file:Documentation/stallion.txt> in
350 this case. If you have never heard about all this, it's safe to
354 tristate "Stallion EasyIO or EC8/32 support"
355 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
357 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
358 card, then this is for you; say Y. Make sure to read
359 <file:Documentation/stallion.txt>.
361 To compile this driver as a module, choose M here: the
362 module will be called stallion.
365 tristate "Stallion EC8/64, ONboard, Brumby support"
366 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
368 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
369 serial multiport card, say Y here. Make sure to read
370 <file:Documentation/stallion.txt>.
372 To compile this driver as a module, choose M here: the
373 module will be called istallion.
376 tristate "HSDPA Broadband Wireless Data Card - Globe Trotter"
377 depends on PCI && EXPERIMENTAL
379 If you have a HSDPA driver Broadband Wireless Data Card -
380 Globe Trotter PCMCIA card, say Y here.
382 To compile this driver as a module, choose M here, the module
383 will be called nozomi.
386 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
387 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
389 This option supports the 2232 7-port serial card shipped with the
390 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
391 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
392 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
393 ports were connected with 8 pin DIN connectors on the card bracket,
394 for which 8 pin to DB25 adapters were supplied. The card also had
395 jumpers internally to toggle various pinning configurations.
397 This driver can be built as a module; but then "generic_serial"
398 will also be built as a module. This has to be loaded before
399 "ser_a2232". If you want to do this, answer M here.
402 bool "SGI Altix system controller communication support"
403 depends on (IA64_SGI_SN2 || IA64_GENERIC)
405 If you have an SGI Altix and you want to enable system
406 controller communication from user space (you want this!),
407 say Y. Otherwise, say N.
410 bool "SGI TIO CX driver support"
411 depends on (IA64_SGI_SN2 || IA64_GENERIC)
413 If you have an SGI Altix and you have fpga devices attached
414 to your TIO, say Y here, otherwise say N.
417 tristate "SGI FPGA Core Services driver support"
420 If you have an SGI Altix with an attached SABrick
421 say Y or M here, otherwise say N.
423 source "drivers/serial/Kconfig"
426 bool "Unix98 PTY support" if EMBEDDED
429 A pseudo terminal (PTY) is a software device consisting of two
430 halves: a master and a slave. The slave device behaves identical to
431 a physical terminal; the master device is used by a process to
432 read data from and write data to the slave, thereby emulating a
433 terminal. Typical programs for the master side are telnet servers
436 Linux has traditionally used the BSD-like names /dev/ptyxx for
437 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
438 has a number of problems. The GNU C library glibc 2.1 and later,
439 however, supports the Unix98 naming standard: in order to acquire a
440 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
441 terminal is then made available to the process and the pseudo
442 terminal slave can be accessed as /dev/pts/<number>. What was
443 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
445 All modern Linux systems use the Unix98 ptys. Say Y unless
446 you're on an embedded system and want to conserve memory.
449 bool "Legacy (BSD) PTY support"
452 A pseudo terminal (PTY) is a software device consisting of two
453 halves: a master and a slave. The slave device behaves identical to
454 a physical terminal; the master device is used by a process to
455 read data from and write data to the slave, thereby emulating a
456 terminal. Typical programs for the master side are telnet servers
459 Linux has traditionally used the BSD-like names /dev/ptyxx
460 for masters and /dev/ttyxx for slaves of pseudo
461 terminals. This scheme has a number of problems, including
462 security. This option enables these legacy devices; on most
463 systems, it is safe to say N.
466 config LEGACY_PTY_COUNT
467 int "Maximum number of legacy PTY in use"
468 depends on LEGACY_PTYS
472 The maximum number of legacy PTYs that can be used at any one time.
473 The default is 256, and should be more than enough. Embedded
474 systems may want to reduce this to save memory.
476 When not in use, each legacy PTY occupies 12 bytes on 32-bit
477 architectures and 24 bytes on 64-bit architectures.
480 tristate 'Total Impact briQ front panel driver'
483 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
484 tristate led and two switches. It is the size of a CDROM drive.
486 If you have such one and want anything showing on the VFD then you
489 To compile this driver as a module, choose M here: the
490 module will be called briq_panel.
492 It's safe to say N here.
495 tristate "Blackfin On-Chip OTP Memory Support"
496 depends on BLACKFIN && (BF52x || BF54x)
499 If you say Y here, you will get support for a character device
500 interface into the One Time Programmable memory pages that are
501 stored on the Blackfin processor. This will not get you access
502 to the secure memory pages however. You will need to write your
503 own secure code and reader for that.
505 To compile this driver as a module, choose M here: the module
506 will be called bfin-otp.
508 If unsure, it is safe to say Y.
510 config BFIN_OTP_WRITE_ENABLE
511 bool "Enable writing support of OTP pages"
515 If you say Y here, you will enable support for writing of the
516 OTP pages. This is dangerous by nature as you can only program
517 the pages once, so only enable this option when you actually
518 need it so as to not inadvertently clobber data.
523 tristate "Parallel printer support"
526 If you intend to attach a printer to the parallel port of your Linux
527 box (as opposed to using a serial printer; if the connector at the
528 printer has 9 or 25 holes ["female"], then it's serial), say Y.
529 Also read the Printing-HOWTO, available from
530 <http://www.tldp.org/docs.html#howto>.
532 It is possible to share one parallel port among several devices
533 (e.g. printer and ZIP drive) and it is safe to compile the
534 corresponding drivers into the kernel.
536 To compile this driver as a module, choose M here and read
537 <file:Documentation/parport.txt>. The module will be called lp.
539 If you have several parallel ports, you can specify which ports to
540 use with the "lp" kernel command line option. (Try "man bootparam"
541 or see the documentation of your boot loader (lilo or loadlin) about
542 how to pass options to the kernel at boot time.) The syntax of the
543 "lp" command line option can be found in <file:drivers/char/lp.c>.
545 If you have more than 8 printers, you need to increase the LP_NO
546 macro in lp.c and the PARPORT_MAX macro in parport.h.
549 bool "Support for console on line printer"
552 If you want kernel messages to be printed out as they occur, you
553 can have a console on the printer. This option adds support for
554 doing that; to actually get it to happen you need to pass the
555 option "console=lp0" to the kernel at boot time.
557 If the printer is out of paper (or off, or unplugged, or too
558 busy..) the kernel will stall until the printer is ready again.
559 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
560 can make the kernel continue when this happens,
561 but it'll lose the kernel messages.
566 tristate "Support for user-space parallel port device drivers"
569 Saying Y to this adds support for /dev/parport device nodes. This
570 is needed for programs that want portable access to the parallel
571 port, for instance deviceid (which displays Plug-and-Play device
574 This is the parallel port equivalent of SCSI generic support (sg).
575 It is safe to say N to this -- it is not needed for normal printing
576 or parallel port CD-ROM/disk support.
578 To compile this driver as a module, choose M here: the
579 module will be called ppdev.
586 Generic "hypervisor virtual console" infrastructure for various
587 hypervisors (pSeries, iSeries, Xen, lguest).
588 It will automatically be selected if one of the back-end console drivers
593 bool "pSeries Hypervisor Virtual Console support"
594 depends on PPC_PSERIES
597 pSeries machines when partitioned support a hypervisor virtual
598 console. This driver allows each pSeries partition to have a console
599 which is accessed via the HMC.
602 bool "iSeries Hypervisor Virtual Console support"
603 depends on PPC_ISERIES
607 iSeries machines support a hypervisor virtual console.
610 bool "IBM RTAS Console support"
614 IBM Console device driver which makes use of RTAS
617 bool "Toshiba's Beat Hypervisor Console support"
618 depends on PPC_CELLEB
621 Toshiba's Cell Reference Set Beat Console device driver
624 bool "Xen Hypervisor Console support"
629 Xen virtual console device driver
631 config VIRTIO_CONSOLE
636 tristate "IBM Hypervisor Virtual Console Server support"
637 depends on PPC_PSERIES
639 Partitionable IBM Power5 ppc64 machines allow hosting of
640 firmware virtual consoles from one Linux partition by
641 another Linux partition. This driver allows console data
642 from Linux partitions to be accessed through TTY device
643 interfaces in the device tree of a Linux partition running
646 To compile this driver as a module, choose M here: the
647 module will be called hvcs.ko. Additionally, this module
648 will depend on arch specific APIs exported from hvcserver.ko
649 which will also be compiled when this driver is built as a
652 source "drivers/char/ipmi/Kconfig"
655 tristate "NetWinder thermometer support"
656 depends on ARCH_NETWINDER
658 Say Y here to include support for the thermal management hardware
659 found in the NetWinder. This driver allows the user to control the
660 temperature set points and to read the current temperature.
662 It is also possible to say M here to build it as a module (ds1620)
663 It is recommended to be used on a NetWinder, but it is not a
667 tristate "NetWinder Button"
668 depends on ARCH_NETWINDER
670 If you say Y here and create a character device node /dev/nwbutton
671 with major and minor numbers 10 and 158 ("man mknod"), then every
672 time the orange button is pressed a number of times, the number of
673 times the button was pressed will be written to that device.
675 This is most useful for applications, as yet unwritten, which
676 perform actions based on how many times the button is pressed in a
679 Do not hold the button down for too long, as the driver does not
680 alter the behaviour of the hardware reset circuitry attached to the
681 button; it will still execute a hard reset if the button is held
682 down for longer than approximately five seconds.
684 To compile this driver as a module, choose M here: the
685 module will be called nwbutton.
687 Most people will answer Y to this question and "Reboot Using Button"
688 below to be able to initiate a system shutdown from the button.
690 config NWBUTTON_REBOOT
691 bool "Reboot Using Button"
694 If you say Y here, then you will be able to initiate a system
695 shutdown and reboot by pressing the orange button a number of times.
696 The number of presses to initiate the shutdown is two by default,
697 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
698 in nwbutton.h and recompiling the driver or, if you compile the
699 driver as a module, you can specify the number of presses at load
700 time with "insmod button reboot_count=<something>".
703 tristate "NetWinder flash support"
704 depends on ARCH_NETWINDER
706 If you say Y here and create a character device /dev/flash with
707 major 10 and minor 160 you can manipulate the flash ROM containing
708 the NetWinder firmware. Be careful as accidentally overwriting the
709 flash contents can render your computer unbootable. On no account
710 allow random users access to this device. :-)
712 To compile this driver as a module, choose M here: the
713 module will be called nwflash.
715 If you're not sure, say N.
717 source "drivers/char/hw_random/Kconfig"
720 tristate "/dev/nvram support"
721 depends on ATARI || X86 || ARM || GENERIC_NVRAM
723 If you say Y here and create a character special file /dev/nvram
724 with major number 10 and minor number 144 using mknod ("man mknod"),
725 you get read and write access to the extra bytes of non-volatile
726 memory in the real time clock (RTC), which is contained in every PC
727 and most Ataris. The actual number of bytes varies, depending on the
728 nvram in the system, but is usually 114 (128-14 for the RTC).
730 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
731 on Ataris. /dev/nvram may be used to view settings there, or to
732 change them (with some utility). It could also be used to frequently
733 save a few bits of very important data that may not be lost over
734 power-off and for which writing to disk is too insecure. Note
735 however that most NVRAM space in a PC belongs to the BIOS and you
736 should NEVER idly tamper with it. See Ralf Brown's interrupt list
737 for a guide to the use of CMOS bytes by your BIOS.
739 On Atari machines, /dev/nvram is always configured and does not need
742 To compile this driver as a module, choose M here: the
743 module will be called nvram.
746 # These legacy RTC drivers just cause too many conflicts with the generic
747 # RTC framework ... let's not even try to coexist any more.
752 tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
753 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
754 && !ARM && !SUPERH && !S390 && !AVR32
756 If you say Y here and create a character special file /dev/rtc with
757 major number 10 and minor number 135 using mknod ("man mknod"), you
758 will get access to the real time clock (or hardware clock) built
761 Every PC has such a clock built in. It can be used to generate
762 signals from as low as 1Hz up to 8192Hz, and can also be used
763 as a 24 hour alarm. It reports status information via the file
764 /proc/driver/rtc and its behaviour is set by various ioctls on
767 If you run Linux on a multiprocessor machine and said Y to
768 "Symmetric Multi Processing" above, you should say Y here to read
769 and set the RTC in an SMP compatible fashion.
771 If you think you have a use for such a device (such as periodic data
772 sampling), then say Y here, and read <file:Documentation/rtc.txt>
775 To compile this driver as a module, choose M here: the
776 module will be called rtc.
779 tristate "Enhanced Real Time Clock Support"
780 depends on SPARC32 && PCI
782 If you say Y here and create a character special file /dev/rtc with
783 major number 10 and minor number 135 using mknod ("man mknod"), you
784 will get access to the real time clock (or hardware clock) built
787 Every PC has such a clock built in. It can be used to generate
788 signals from as low as 1Hz up to 8192Hz, and can also be used
789 as a 24 hour alarm. It reports status information via the file
790 /proc/driver/rtc and its behaviour is set by various ioctls on
793 If you think you have a use for such a device (such as periodic data
794 sampling), then say Y here, and read <file:Documentation/rtc.txt>
797 To compile this driver as a module, choose M here: the
798 module will be called js-rtc.
801 tristate "SGI DS1286 RTC support"
802 depends on SGI_HAS_DS1286
804 If you say Y here and create a character special file /dev/rtc with
805 major number 10 and minor number 135 using mknod ("man mknod"), you
806 will get access to the real time clock built into your computer.
807 Every SGI has such a clock built in. It reports status information
808 via the file /proc/rtc and its behaviour is set by various ioctls on
812 bool "SGI M48T35 RTC support"
815 If you say Y here and create a character special file /dev/rtc with
816 major number 10 and minor number 135 using mknod ("man mknod"), you
817 will get access to the real time clock built into your computer.
818 Every SGI has such a clock built in. It reports status information
819 via the file /proc/rtc and its behaviour is set by various ioctls on
823 tristate "Generic /dev/rtc emulation"
824 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32
826 If you say Y here and create a character special file /dev/rtc with
827 major number 10 and minor number 135 using mknod ("man mknod"), you
828 will get access to the real time clock (or hardware clock) built
831 It reports status information via the file /proc/driver/rtc and its
832 behaviour is set by various ioctls on /dev/rtc. If you enable the
833 "extended RTC operation" below it will also provide an emulation
834 for RTC_UIE which is required by some programs and may improve
835 precision in some cases.
837 To compile this driver as a module, choose M here: the
838 module will be called genrtc.
841 bool "Extended RTC operation"
844 Provides an emulation for RTC_UIE which is required by some programs
845 and may improve precision of the generic RTC support in some cases.
848 bool "EFI Real Time Clock Services"
852 tristate "DS1302 RTC support"
853 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
855 If you say Y here and create a character special file /dev/rtc with
856 major number 121 and minor number 0 using mknod ("man mknod"), you
857 will get access to the real time clock (or hardware clock) built
863 bool "Support for Cobalt LCD"
864 depends on MIPS_COBALT
866 This option enables support for the LCD display and buttons found
867 on Cobalt systems through a misc device.
870 tristate "Double Talk PC internal speech card support"
873 This driver is for the DoubleTalk PC, a speech synthesizer
874 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
875 called the `internal DoubleTalk'.
877 To compile this driver as a module, choose M here: the
878 module will be called dtlk.
881 tristate "Xilinx HWICAP Support"
882 depends on XILINX_VIRTEX
884 This option enables support for Xilinx Internal Configuration
885 Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
886 FPGA platforms to partially reconfigure the FPGA at runtime.
891 tristate "Siemens R3964 line discipline"
893 This driver allows synchronous communication with devices using the
894 Siemens R3964 packet protocol. Unless you are dealing with special
895 hardware like PLCs, you are unlikely to need this.
897 To compile this driver as a module, choose M here: the
898 module will be called n_r3964.
903 tristate "Applicom intelligent fieldbus card support"
906 This driver provides the kernel-side support for the intelligent
907 fieldbus cards made by Applicom International. More information
908 about these cards can be found on the WWW at the address
909 <http://www.applicom-int.com/>, or by email from David Woodhouse
910 <dwmw2@infradead.org>.
912 To compile this driver as a module, choose M here: the
913 module will be called applicom.
918 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
919 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
921 This driver enables access to the Sony Programmable I/O Control
922 Device which can be found in many (all ?) Sony Vaio laptops.
924 If you have one of those laptops, read
925 <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
927 To compile this driver as a module, choose M here: the
928 module will be called sonypi.
931 tristate "TANBAC TB0219 GPIO support"
932 depends on TANBAC_TB022X
935 source "drivers/char/pcmcia/Kconfig"
938 tristate "ACP Modem (Mwave) support"
942 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
943 kernel driver and a user level application. Together these components
944 support direct attachment to public switched telephone networks (PSTNs)
945 and support selected world wide countries.
947 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
948 600, and 770 that include on board ACP modem hardware.
950 The modem also supports the standard communications port interface
951 (ttySx) and is compatible with the Hayes AT Command Set.
953 The user level application needed to use this driver can be found at
954 the IBM Linux Technology Center (LTC) web site:
955 <http://www.ibm.com/linux/ltc/>.
957 If you own one of the above IBM Thinkpads which has the Mwave chipset
960 To compile this driver as a module, choose M here: the
961 module will be called mwave.
964 tristate "NatSemi SCx200 GPIO Support"
968 Give userspace access to the GPIO pins on the National
969 Semiconductor SCx200 processors.
971 If compiled as a module, it will be called scx200_gpio.
974 tristate "NatSemi PC8736x GPIO Support"
976 default SCx200_GPIO # mostly N
977 select NSC_GPIO # needed for support routines
979 Give userspace access to the GPIO pins on the National
980 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
981 has multiple functional units, inc several managed by
982 hwmon/pc87360 driver. Tested with PC-87366
984 If compiled as a module, it will be called pc8736x_gpio.
987 tristate "NatSemi Base GPIO Support"
989 # selected by SCx200_GPIO and PC8736x_GPIO
990 # what about 2 selectors differing: m != y
992 Common support used (and needed) by scx200_gpio and
993 pc8736x_gpio drivers. If those drivers are built as
994 modules, this one will be too, named nsc_gpio
997 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
1000 Give userspace access to the GPIO pins on the AMD CS5535 and
1001 CS5536 Geode companion devices.
1003 If compiled as a module, it will be called cs5535_gpio.
1006 tristate "NEC VR4100 series General-purpose I/O Unit support"
1007 depends on CPU_VR41XX
1010 tristate "RAW driver (/dev/raw/rawN)"
1013 The raw driver permits block devices to be bound to /dev/raw/rawN.
1014 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
1015 See the raw(8) manpage for more details.
1017 Applications should preferably open the device (eg /dev/hda1)
1018 with the O_DIRECT flag.
1021 int "Maximum number of RAW devices to support (1-8192)"
1022 depends on RAW_DRIVER
1025 The maximum number of RAW devices that are supported.
1026 Default is 256. Increase this number in case you need lots of
1030 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1034 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1035 open selects one of the timers supported by the HPET. The timers are
1036 non-periodic and/or periodic.
1040 default HPET_EMULATE_RTC
1041 depends on RTC && HPET
1043 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1044 is assumed the platform called hpet_alloc with the RTC IRQ values for
1048 bool "Allow mmap of HPET"
1052 If you say Y here, user applications will be able to mmap
1055 In some hardware implementations, the page containing HPET
1056 registers may also contain other things that shouldn't be
1057 exposed to the user. If this applies to your hardware,
1060 config HANGCHECK_TIMER
1061 tristate "Hangcheck timer"
1062 depends on X86 || IA64 || PPC64 || S390
1064 The hangcheck-timer module detects when the system has gone
1065 out to lunch past a certain margin. It can reboot the system
1066 or merely print a warning.
1069 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1070 depends on IA64_GENERIC || IA64_SGI_SN2
1073 The mmtimer device allows direct userspace access to the
1076 source "drivers/char/tpm/Kconfig"
1079 tristate "Telecom clock driver for ATCA SBC"
1080 depends on EXPERIMENTAL && X86
1083 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1084 ATCA computers and allows direct userspace access to the
1085 configuration of the telecom clock configuration settings. This
1086 device is used for hardware synchronization across the ATCA backplane
1087 fabric. Upon loading, the driver exports a sysfs directory,
1088 /sys/devices/platform/telco_clock, with a number of files for
1089 controlling the behavior of this hardware.
1094 depends on ISA || PCI
1097 source "drivers/s390/char/Kconfig"
projects / linux-2.6 / blob