2 # Character device configuration
5 menu "Character devices"
8 bool "Virtual terminal" if EMBEDDED
13 If you say Y here, you will get support for terminal devices with
14 display and keyboard devices. These are called "virtual" because you
15 can run several virtual terminals (also called virtual consoles) on
16 one physical terminal. This is rather useful, for example one
17 virtual terminal can collect system messages and warnings, another
18 one can be used for a text-mode user session, and a third could run
19 an X session, all in parallel. Switching between virtual terminals
20 is done with certain key combinations, usually Alt-<function key>.
22 The setterm command ("man setterm") can be used to change the
23 properties (such as colors or beeping) of a virtual terminal. The
24 man page console_codes(4) ("man console_codes") contains the special
25 character sequences that can be used to change those properties
26 directly. The fonts used on virtual terminals can be changed with
27 the setfont ("man setfont") command and the key bindings are defined
28 with the loadkeys ("man loadkeys") command.
30 You need at least one virtual terminal device in order to make use
31 of your keyboard and monitor. Therefore, only people configuring an
32 embedded system would want to say N here in order to save some
33 memory; the only way to log into such a system is then via a serial
34 or network connection.
36 If unsure, say Y, or else you won't be able to do much with your new
37 shiny Linux system :-)
40 bool "Support for console on virtual terminal" if EMBEDDED
44 The system console is the device which receives all kernel messages
45 and warnings and which allows logins in single user mode. If you
46 answer Y here, a virtual terminal (the device used to interact with
47 a physical terminal) can be used as system console. This is the most
48 common mode of operations, so you should say Y here unless you want
49 the kernel messages be output only to a serial port (in which case
50 you should say Y to "Console on serial port", below).
52 If you do say Y here, by default the currently visible virtual
53 terminal (/dev/tty0) will be used as system console. You can change
54 that with a kernel command line option such as "console=tty3" which
55 would use the third virtual terminal as system console. (Try "man
56 bootparam" or see the documentation of your boot loader (lilo or
57 loadlin) about how to pass options to the kernel at boot time.)
63 depends on VT && !S390 && !UML
66 config VT_HW_CONSOLE_BINDING
67 bool "Support for binding and unbinding console drivers"
71 The virtual terminal is the device that interacts with the physical
72 terminal through console drivers. On these systems, at least one
73 console driver is loaded. In other configurations, additional console
74 drivers may be enabled, such as the framebuffer console. If more than
75 1 console driver is enabled, setting this to 'y' will allow you to
76 select the console driver that will serve as the backend for the
79 See <file:Documentation/console/console.txt> for more
80 information. For framebuffer console users, please refer to
81 <file:Documentation/fb/fbcon.txt>.
83 config SERIAL_NONSTANDARD
84 bool "Non-standard serial port support"
87 Say Y here if you have any non-standard serial boards -- boards
88 which aren't supported using the standard "dumb" serial driver.
89 This includes intelligent serial boards such as Cyclades,
90 Digiboards, etc. These are usually used for systems that need many
91 serial ports because they serve many terminals or dial-in
94 Note that the answer to this question won't directly affect the
95 kernel: saying N will just cause the configurator to skip all
96 the questions about non-standard serial boards.
98 Most people can say N here.
101 tristate "Computone IntelliPort Plus serial support"
102 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
104 This driver supports the entire family of Intelliport II/Plus
105 controllers with the exception of the MicroChannel controllers and
106 products previous to the Intelliport II. These are multiport cards,
107 which give you many serial ports. You would need something like this
108 to connect more than two modems to your Linux box, for instance in
109 order to become a dial-in server. If you have a card like that, say
110 Y here and read <file:Documentation/computone.txt>.
112 To compile this driver as modules, choose M here: the
113 modules will be called ip2 and ip2main.
116 tristate "Comtrol RocketPort support"
117 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
119 This driver supports Comtrol RocketPort and RocketModem PCI boards.
120 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
121 modems. For information about the RocketPort/RocketModem boards
122 and this driver read <file:Documentation/rocket.txt>.
124 To compile this driver as a module, choose M here: the
125 module will be called rocket.
127 If you want to compile this driver into the kernel, say Y here. If
128 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
131 tristate "Cyclades async mux support"
132 depends on SERIAL_NONSTANDARD && (PCI || ISA)
135 This driver supports Cyclades Z and Y multiserial boards.
136 You would need something like this to connect more than two modems to
137 your Linux box, for instance in order to become a dial-in server.
139 For information about the Cyclades-Z card, read
140 <file:Documentation/README.cycladesZ>.
142 To compile this driver as a module, choose M here: the
143 module will be called cyclades.
145 If you haven't heard about it, it's safe to say N.
148 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
149 depends on EXPERIMENTAL && CYCLADES
151 The Cyclades-Z family of multiport cards allows 2 (two) driver op
152 modes: polling and interrupt. In polling mode, the driver will check
153 the status of the Cyclades-Z ports every certain amount of time
154 (which is called polling cycle and is configurable). In interrupt
155 mode, it will use an interrupt line (IRQ) in order to check the
156 status of the Cyclades-Z ports. The default op mode is polling. If
160 tristate "Digiboard Intelligent Async Support"
161 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
163 This is a driver for Digi International's Xx, Xeve, and Xem series
164 of cards which provide multiple serial ports. You would need
165 something like this to connect more than two modems to your Linux
166 box, for instance in order to become a dial-in server. This driver
167 supports the original PC (ISA) boards as well as PCI, and EISA. If
168 you have a card like this, say Y here and read the file
169 <file:Documentation/digiepca.txt>.
171 To compile this driver as a module, choose M here: the
172 module will be called epca.
175 tristate "Hayes ESP serial port support"
176 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
178 This is a driver which supports Hayes ESP serial ports. Both single
179 port cards and multiport cards are supported. Make sure to read
180 <file:Documentation/hayes-esp.txt>.
182 To compile this driver as a module, choose M here: the
183 module will be called esp.
188 tristate "Moxa Intellio support"
189 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
191 Say Y here if you have a Moxa Intellio multiport serial card.
193 To compile this driver as a module, choose M here: the
194 module will be called moxa.
197 tristate "Moxa SmartIO support v. 2.0"
198 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
200 Say Y here if you have a Moxa SmartIO multiport serial card and/or
201 want to help develop a new version of this driver.
203 This is upgraded (1.9.1) driver from original Moxa drivers with
204 changes finally resulting in PCI probing.
206 This driver can also be built as a module. The module will be called
207 mxser. If you want to do that, say M here.
210 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
211 depends on SERIAL_NONSTANDARD && PCI
214 This is a driver for the Multi-Tech cards which provide several
215 serial ports. The driver is experimental and can currently only be
216 built as a module. The module will be called isicom.
217 If you want to do that, choose M here.
220 tristate "Microgate SyncLink card support"
221 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
223 Provides support for the SyncLink ISA and PCI multiprotocol serial
224 adapters. These adapters support asynchronous and HDLC bit
225 synchronous communication up to 10Mbps (PCI adapter).
227 This driver can only be built as a module ( = code which can be
228 inserted in and removed from the running kernel whenever you want).
229 The module will be called synclink. If you want to do that, say M
233 tristate "SyncLink Multiport support"
234 depends on SERIAL_NONSTANDARD && PCI
236 Enable support for the SyncLink Multiport (2 or 4 ports)
237 serial adapter, running asynchronous and HDLC communications up
238 to 2.048Mbps. Each ports is independently selectable for
239 RS-232, V.35, RS-449, RS-530, and X.21
241 This driver may be built as a module ( = code which can be
242 inserted in and removed from the running kernel whenever you want).
243 The module will be called synclinkmp. If you want to do that, say M
247 tristate "SyncLink GT/AC support"
248 depends on SERIAL_NONSTANDARD && PCI
250 Support for SyncLink GT and SyncLink AC families of
251 synchronous and asynchronous serial adapters
252 manufactured by Microgate Systems, Ltd. (www.microgate.com)
255 tristate "HDLC line discipline support"
256 depends on SERIAL_NONSTANDARD
258 Allows synchronous HDLC communications with tty device drivers that
259 support synchronous HDLC such as the Microgate SyncLink adapter.
261 This driver can only be built as a module ( = code which can be
262 inserted in and removed from the running kernel whenever you want).
263 The module will be called n_hdlc. If you want to do that, say M
267 tristate "SDL RISCom/8 card support"
268 depends on SERIAL_NONSTANDARD
270 This is a driver for the SDL Communications RISCom/8 multiport card,
271 which gives you many serial ports. You would need something like
272 this to connect more than two modems to your Linux box, for instance
273 in order to become a dial-in server. If you have a card like that,
274 say Y here and read the file <file:Documentation/riscom8.txt>.
276 Also it's possible to say M here and compile this driver as kernel
277 loadable module; the module will be called riscom8.
280 tristate "Specialix IO8+ card support"
281 depends on SERIAL_NONSTANDARD
283 This is a driver for the Specialix IO8+ multiport card (both the
284 ISA and the PCI version) which gives you many serial ports. You
285 would need something like this to connect more than two modems to
286 your Linux box, for instance in order to become a dial-in server.
288 If you have a card like that, say Y here and read the file
289 <file:Documentation/specialix.txt>. Also it's possible to say M here
290 and compile this driver as kernel loadable module which will be
293 config SPECIALIX_RTSCTS
294 bool "Specialix DTR/RTS pin is RTS"
297 The Specialix IO8+ card can only support either RTS or DTR. If you
298 say N here, the driver will use the pin as "DTR" when the tty is in
299 software handshake mode. If you say Y here or hardware handshake is
300 on, it will always be RTS. Read the file
301 <file:Documentation/specialix.txt> for more information.
304 tristate "Specialix SX (and SI) card support"
305 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
307 This is a driver for the SX and SI multiport serial cards.
308 Please read the file <file:Documentation/sx.txt> for details.
310 This driver can only be built as a module ( = code which can be
311 inserted in and removed from the running kernel whenever you want).
312 The module will be called sx. If you want to do that, say M here.
315 tristate "Specialix RIO system support"
316 depends on SERIAL_NONSTANDARD
318 This is a driver for the Specialix RIO, a smart serial card which
319 drives an outboard box that can support up to 128 ports. Product
320 information is at <http://www.perle.com/support/documentation.html#multiport>.
321 There are both ISA and PCI versions.
324 bool "Support really old RIO/PCI cards"
327 Older RIO PCI cards need some initialization-time configuration to
328 determine the IRQ and some control addresses. If you have a RIO and
329 this doesn't seem to work, try setting this to Y.
332 bool "Stallion multiport serial support"
333 depends on SERIAL_NONSTANDARD
335 Stallion cards give you many serial ports. You would need something
336 like this to connect more than two modems to your Linux box, for
337 instance in order to become a dial-in server. If you say Y here,
338 you will be asked for your specific card model in the next
339 questions. Make sure to read <file:Documentation/stallion.txt> in
340 this case. If you have never heard about all this, it's safe to
344 tristate "Stallion EasyIO or EC8/32 support"
345 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
347 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
348 card, then this is for you; say Y. Make sure to read
349 <file:Documentation/stallion.txt>.
351 To compile this driver as a module, choose M here: the
352 module will be called stallion.
355 tristate "Stallion EC8/64, ONboard, Brumby support"
356 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
358 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
359 serial multiport card, say Y here. Make sure to read
360 <file:Documentation/stallion.txt>.
362 To compile this driver as a module, choose M here: the
363 module will be called istallion.
366 tristate "HSDPA Broadband Wireless Data Card - Globe Trotter"
367 depends on PCI && EXPERIMENTAL
369 If you have a HSDPA driver Broadband Wireless Data Card -
370 Globe Trotter PCMCIA card, say Y here.
372 To compile this driver as a module, choose M here, the module
373 will be called nozomi.
376 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
377 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
379 This option supports the 2232 7-port serial card shipped with the
380 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
381 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
382 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
383 ports were connected with 8 pin DIN connectors on the card bracket,
384 for which 8 pin to DB25 adapters were supplied. The card also had
385 jumpers internally to toggle various pinning configurations.
387 This driver can be built as a module; but then "generic_serial"
388 will also be built as a module. This has to be loaded before
389 "ser_a2232". If you want to do this, answer M here.
392 bool "SGI Altix system controller communication support"
393 depends on (IA64_SGI_SN2 || IA64_GENERIC)
395 If you have an SGI Altix and you want to enable system
396 controller communication from user space (you want this!),
397 say Y. Otherwise, say N.
400 bool "SGI TIO CX driver support"
401 depends on (IA64_SGI_SN2 || IA64_GENERIC)
403 If you have an SGI Altix and you have fpga devices attached
404 to your TIO, say Y here, otherwise say N.
407 tristate "SGI FPGA Core Services driver support"
410 If you have an SGI Altix with an attached SABrick
411 say Y or M here, otherwise say N.
413 source "drivers/serial/Kconfig"
416 bool "Unix98 PTY support" if EMBEDDED
419 A pseudo terminal (PTY) is a software device consisting of two
420 halves: a master and a slave. The slave device behaves identical to
421 a physical terminal; the master device is used by a process to
422 read data from and write data to the slave, thereby emulating a
423 terminal. Typical programs for the master side are telnet servers
426 Linux has traditionally used the BSD-like names /dev/ptyxx for
427 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
428 has a number of problems. The GNU C library glibc 2.1 and later,
429 however, supports the Unix98 naming standard: in order to acquire a
430 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
431 terminal is then made available to the process and the pseudo
432 terminal slave can be accessed as /dev/pts/<number>. What was
433 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
435 All modern Linux systems use the Unix98 ptys. Say Y unless
436 you're on an embedded system and want to conserve memory.
439 bool "Legacy (BSD) PTY support"
442 A pseudo terminal (PTY) is a software device consisting of two
443 halves: a master and a slave. The slave device behaves identical to
444 a physical terminal; the master device is used by a process to
445 read data from and write data to the slave, thereby emulating a
446 terminal. Typical programs for the master side are telnet servers
449 Linux has traditionally used the BSD-like names /dev/ptyxx
450 for masters and /dev/ttyxx for slaves of pseudo
451 terminals. This scheme has a number of problems, including
452 security. This option enables these legacy devices; on most
453 systems, it is safe to say N.
456 config LEGACY_PTY_COUNT
457 int "Maximum number of legacy PTY in use"
458 depends on LEGACY_PTYS
462 The maximum number of legacy PTYs that can be used at any one time.
463 The default is 256, and should be more than enough. Embedded
464 systems may want to reduce this to save memory.
466 When not in use, each legacy PTY occupies 12 bytes on 32-bit
467 architectures and 24 bytes on 64-bit architectures.
470 tristate 'Total Impact briQ front panel driver'
473 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
474 tristate led and two switches. It is the size of a CDROM drive.
476 If you have such one and want anything showing on the VFD then you
479 To compile this driver as a module, choose M here: the
480 module will be called briq_panel.
482 It's safe to say N here.
485 tristate "Blackfin On-Chip OTP Memory Support"
486 depends on BLACKFIN && (BF52x || BF54x)
489 If you say Y here, you will get support for a character device
490 interface into the One Time Programmable memory pages that are
491 stored on the Blackfin processor. This will not get you access
492 to the secure memory pages however. You will need to write your
493 own secure code and reader for that.
495 To compile this driver as a module, choose M here: the module
496 will be called bfin-otp.
498 If unsure, it is safe to say Y.
500 config BFIN_OTP_WRITE_ENABLE
501 bool "Enable writing support of OTP pages"
505 If you say Y here, you will enable support for writing of the
506 OTP pages. This is dangerous by nature as you can only program
507 the pages once, so only enable this option when you actually
508 need it so as to not inadvertently clobber data.
513 tristate "Parallel printer support"
516 If you intend to attach a printer to the parallel port of your Linux
517 box (as opposed to using a serial printer; if the connector at the
518 printer has 9 or 25 holes ["female"], then it's serial), say Y.
519 Also read the Printing-HOWTO, available from
520 <http://www.tldp.org/docs.html#howto>.
522 It is possible to share one parallel port among several devices
523 (e.g. printer and ZIP drive) and it is safe to compile the
524 corresponding drivers into the kernel.
526 To compile this driver as a module, choose M here and read
527 <file:Documentation/parport.txt>. The module will be called lp.
529 If you have several parallel ports, you can specify which ports to
530 use with the "lp" kernel command line option. (Try "man bootparam"
531 or see the documentation of your boot loader (lilo or loadlin) about
532 how to pass options to the kernel at boot time.) The syntax of the
533 "lp" command line option can be found in <file:drivers/char/lp.c>.
535 If you have more than 8 printers, you need to increase the LP_NO
536 macro in lp.c and the PARPORT_MAX macro in parport.h.
539 bool "Support for console on line printer"
542 If you want kernel messages to be printed out as they occur, you
543 can have a console on the printer. This option adds support for
544 doing that; to actually get it to happen you need to pass the
545 option "console=lp0" to the kernel at boot time.
547 If the printer is out of paper (or off, or unplugged, or too
548 busy..) the kernel will stall until the printer is ready again.
549 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
550 can make the kernel continue when this happens,
551 but it'll lose the kernel messages.
556 tristate "Support for user-space parallel port device drivers"
559 Saying Y to this adds support for /dev/parport device nodes. This
560 is needed for programs that want portable access to the parallel
561 port, for instance deviceid (which displays Plug-and-Play device
564 This is the parallel port equivalent of SCSI generic support (sg).
565 It is safe to say N to this -- it is not needed for normal printing
566 or parallel port CD-ROM/disk support.
568 To compile this driver as a module, choose M here: the
569 module will be called ppdev.
576 Generic "hypervisor virtual console" infrastructure for various
577 hypervisors (pSeries, iSeries, Xen, lguest).
578 It will automatically be selected if one of the back-end console drivers
583 bool "pSeries Hypervisor Virtual Console support"
584 depends on PPC_PSERIES
587 pSeries machines when partitioned support a hypervisor virtual
588 console. This driver allows each pSeries partition to have a console
589 which is accessed via the HMC.
592 bool "iSeries Hypervisor Virtual Console support"
593 depends on PPC_ISERIES
597 iSeries machines support a hypervisor virtual console.
600 bool "IBM RTAS Console support"
604 IBM Console device driver which makes use of RTAS
607 bool "Toshiba's Beat Hypervisor Console support"
608 depends on PPC_CELLEB
611 Toshiba's Cell Reference Set Beat Console device driver
614 bool "Xen Hypervisor Console support"
619 Xen virtual console device driver
621 config VIRTIO_CONSOLE
626 tristate "IBM Hypervisor Virtual Console Server support"
627 depends on PPC_PSERIES
629 Partitionable IBM Power5 ppc64 machines allow hosting of
630 firmware virtual consoles from one Linux partition by
631 another Linux partition. This driver allows console data
632 from Linux partitions to be accessed through TTY device
633 interfaces in the device tree of a Linux partition running
636 To compile this driver as a module, choose M here: the
637 module will be called hvcs.ko. Additionally, this module
638 will depend on arch specific APIs exported from hvcserver.ko
639 which will also be compiled when this driver is built as a
642 source "drivers/char/ipmi/Kconfig"
645 tristate "NetWinder thermometer support"
646 depends on ARCH_NETWINDER
648 Say Y here to include support for the thermal management hardware
649 found in the NetWinder. This driver allows the user to control the
650 temperature set points and to read the current temperature.
652 It is also possible to say M here to build it as a module (ds1620)
653 It is recommended to be used on a NetWinder, but it is not a
657 tristate "NetWinder Button"
658 depends on ARCH_NETWINDER
660 If you say Y here and create a character device node /dev/nwbutton
661 with major and minor numbers 10 and 158 ("man mknod"), then every
662 time the orange button is pressed a number of times, the number of
663 times the button was pressed will be written to that device.
665 This is most useful for applications, as yet unwritten, which
666 perform actions based on how many times the button is pressed in a
669 Do not hold the button down for too long, as the driver does not
670 alter the behaviour of the hardware reset circuitry attached to the
671 button; it will still execute a hard reset if the button is held
672 down for longer than approximately five seconds.
674 To compile this driver as a module, choose M here: the
675 module will be called nwbutton.
677 Most people will answer Y to this question and "Reboot Using Button"
678 below to be able to initiate a system shutdown from the button.
680 config NWBUTTON_REBOOT
681 bool "Reboot Using Button"
684 If you say Y here, then you will be able to initiate a system
685 shutdown and reboot by pressing the orange button a number of times.
686 The number of presses to initiate the shutdown is two by default,
687 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
688 in nwbutton.h and recompiling the driver or, if you compile the
689 driver as a module, you can specify the number of presses at load
690 time with "insmod button reboot_count=<something>".
693 tristate "NetWinder flash support"
694 depends on ARCH_NETWINDER
696 If you say Y here and create a character device /dev/flash with
697 major 10 and minor 160 you can manipulate the flash ROM containing
698 the NetWinder firmware. Be careful as accidentally overwriting the
699 flash contents can render your computer unbootable. On no account
700 allow random users access to this device. :-)
702 To compile this driver as a module, choose M here: the
703 module will be called nwflash.
705 If you're not sure, say N.
707 source "drivers/char/hw_random/Kconfig"
710 tristate "/dev/nvram support"
711 depends on ATARI || X86 || ARM || GENERIC_NVRAM
713 If you say Y here and create a character special file /dev/nvram
714 with major number 10 and minor number 144 using mknod ("man mknod"),
715 you get read and write access to the extra bytes of non-volatile
716 memory in the real time clock (RTC), which is contained in every PC
717 and most Ataris. The actual number of bytes varies, depending on the
718 nvram in the system, but is usually 114 (128-14 for the RTC).
720 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
721 on Ataris. /dev/nvram may be used to view settings there, or to
722 change them (with some utility). It could also be used to frequently
723 save a few bits of very important data that may not be lost over
724 power-off and for which writing to disk is too insecure. Note
725 however that most NVRAM space in a PC belongs to the BIOS and you
726 should NEVER idly tamper with it. See Ralf Brown's interrupt list
727 for a guide to the use of CMOS bytes by your BIOS.
729 On Atari machines, /dev/nvram is always configured and does not need
732 To compile this driver as a module, choose M here: the
733 module will be called nvram.
736 # These legacy RTC drivers just cause too many conflicts with the generic
737 # RTC framework ... let's not even try to coexist any more.
742 tristate "Enhanced Real Time Clock Support"
743 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
744 && !ARM && !SUPERH && !S390 && !AVR32
746 If you say Y here and create a character special file /dev/rtc with
747 major number 10 and minor number 135 using mknod ("man mknod"), you
748 will get access to the real time clock (or hardware clock) built
751 Every PC has such a clock built in. It can be used to generate
752 signals from as low as 1Hz up to 8192Hz, and can also be used
753 as a 24 hour alarm. It reports status information via the file
754 /proc/driver/rtc and its behaviour is set by various ioctls on
757 If you run Linux on a multiprocessor machine and said Y to
758 "Symmetric Multi Processing" above, you should say Y here to read
759 and set the RTC in an SMP compatible fashion.
761 If you think you have a use for such a device (such as periodic data
762 sampling), then say Y here, and read <file:Documentation/rtc.txt>
765 To compile this driver as a module, choose M here: the
766 module will be called rtc.
769 tristate "Enhanced Real Time Clock Support"
770 depends on SPARC32 && PCI
772 If you say Y here and create a character special file /dev/rtc with
773 major number 10 and minor number 135 using mknod ("man mknod"), you
774 will get access to the real time clock (or hardware clock) built
777 Every PC has such a clock built in. It can be used to generate
778 signals from as low as 1Hz up to 8192Hz, and can also be used
779 as a 24 hour alarm. It reports status information via the file
780 /proc/driver/rtc and its behaviour is set by various ioctls on
783 If you think you have a use for such a device (such as periodic data
784 sampling), then say Y here, and read <file:Documentation/rtc.txt>
787 To compile this driver as a module, choose M here: the
788 module will be called js-rtc.
791 tristate "SGI DS1286 RTC support"
792 depends on SGI_HAS_DS1286
794 If you say Y here and create a character special file /dev/rtc with
795 major number 10 and minor number 135 using mknod ("man mknod"), you
796 will get access to the real time clock built into your computer.
797 Every SGI has such a clock built in. It reports status information
798 via the file /proc/rtc and its behaviour is set by various ioctls on
802 bool "SGI M48T35 RTC support"
805 If you say Y here and create a character special file /dev/rtc with
806 major number 10 and minor number 135 using mknod ("man mknod"), you
807 will get access to the real time clock built into your computer.
808 Every SGI has such a clock built in. It reports status information
809 via the file /proc/rtc and its behaviour is set by various ioctls on
813 tristate "Generic /dev/rtc emulation"
814 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32
816 If you say Y here and create a character special file /dev/rtc with
817 major number 10 and minor number 135 using mknod ("man mknod"), you
818 will get access to the real time clock (or hardware clock) built
821 It reports status information via the file /proc/driver/rtc and its
822 behaviour is set by various ioctls on /dev/rtc. If you enable the
823 "extended RTC operation" below it will also provide an emulation
824 for RTC_UIE which is required by some programs and may improve
825 precision in some cases.
827 To compile this driver as a module, choose M here: the
828 module will be called genrtc.
831 bool "Extended RTC operation"
834 Provides an emulation for RTC_UIE which is required by some programs
835 and may improve precision of the generic RTC support in some cases.
838 bool "EFI Real Time Clock Services"
842 tristate "DS1302 RTC support"
843 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
845 If you say Y here and create a character special file /dev/rtc with
846 major number 121 and minor number 0 using mknod ("man mknod"), you
847 will get access to the real time clock (or hardware clock) built
853 bool "Support for Cobalt LCD"
854 depends on MIPS_COBALT
856 This option enables support for the LCD display and buttons found
857 on Cobalt systems through a misc device.
860 tristate "Double Talk PC internal speech card support"
863 This driver is for the DoubleTalk PC, a speech synthesizer
864 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
865 called the `internal DoubleTalk'.
867 To compile this driver as a module, choose M here: the
868 module will be called dtlk.
871 tristate "Xilinx HWICAP Support"
872 depends on XILINX_VIRTEX
874 This option enables support for Xilinx Internal Configuration
875 Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
876 FPGA platforms to partially reconfigure the FPGA at runtime.
881 tristate "Siemens R3964 line discipline"
883 This driver allows synchronous communication with devices using the
884 Siemens R3964 packet protocol. Unless you are dealing with special
885 hardware like PLCs, you are unlikely to need this.
887 To compile this driver as a module, choose M here: the
888 module will be called n_r3964.
893 tristate "Applicom intelligent fieldbus card support"
896 This driver provides the kernel-side support for the intelligent
897 fieldbus cards made by Applicom International. More information
898 about these cards can be found on the WWW at the address
899 <http://www.applicom-int.com/>, or by email from David Woodhouse
900 <dwmw2@infradead.org>.
902 To compile this driver as a module, choose M here: the
903 module will be called applicom.
908 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
909 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
911 This driver enables access to the Sony Programmable I/O Control
912 Device which can be found in many (all ?) Sony Vaio laptops.
914 If you have one of those laptops, read
915 <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
917 To compile this driver as a module, choose M here: the
918 module will be called sonypi.
921 tristate "TANBAC TB0219 GPIO support"
922 depends on TANBAC_TB022X
925 source "drivers/char/pcmcia/Kconfig"
928 tristate "ACP Modem (Mwave) support"
932 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
933 kernel driver and a user level application. Together these components
934 support direct attachment to public switched telephone networks (PSTNs)
935 and support selected world wide countries.
937 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
938 600, and 770 that include on board ACP modem hardware.
940 The modem also supports the standard communications port interface
941 (ttySx) and is compatible with the Hayes AT Command Set.
943 The user level application needed to use this driver can be found at
944 the IBM Linux Technology Center (LTC) web site:
945 <http://www.ibm.com/linux/ltc/>.
947 If you own one of the above IBM Thinkpads which has the Mwave chipset
950 To compile this driver as a module, choose M here: the
951 module will be called mwave.
954 tristate "NatSemi SCx200 GPIO Support"
958 Give userspace access to the GPIO pins on the National
959 Semiconductor SCx200 processors.
961 If compiled as a module, it will be called scx200_gpio.
964 tristate "NatSemi PC8736x GPIO Support"
966 default SCx200_GPIO # mostly N
967 select NSC_GPIO # needed for support routines
969 Give userspace access to the GPIO pins on the National
970 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
971 has multiple functional units, inc several managed by
972 hwmon/pc87360 driver. Tested with PC-87366
974 If compiled as a module, it will be called pc8736x_gpio.
977 tristate "NatSemi Base GPIO Support"
979 # selected by SCx200_GPIO and PC8736x_GPIO
980 # what about 2 selectors differing: m != y
982 Common support used (and needed) by scx200_gpio and
983 pc8736x_gpio drivers. If those drivers are built as
984 modules, this one will be too, named nsc_gpio
987 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
990 Give userspace access to the GPIO pins on the AMD CS5535 and
991 CS5536 Geode companion devices.
993 If compiled as a module, it will be called cs5535_gpio.
996 tristate "NEC VR4100 series General-purpose I/O Unit support"
997 depends on CPU_VR41XX
1000 tristate "RAW driver (/dev/raw/rawN)"
1003 The raw driver permits block devices to be bound to /dev/raw/rawN.
1004 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
1005 See the raw(8) manpage for more details.
1007 Applications should preferably open the device (eg /dev/hda1)
1008 with the O_DIRECT flag.
1011 int "Maximum number of RAW devices to support (1-8192)"
1012 depends on RAW_DRIVER
1015 The maximum number of RAW devices that are supported.
1016 Default is 256. Increase this number in case you need lots of
1020 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1024 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1025 open selects one of the timers supported by the HPET. The timers are
1026 non-periodic and/or periodic.
1029 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1033 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1034 is assumed the platform called hpet_alloc with the RTC IRQ values for
1038 bool "Allow mmap of HPET"
1042 If you say Y here, user applications will be able to mmap
1045 In some hardware implementations, the page containing HPET
1046 registers may also contain other things that shouldn't be
1047 exposed to the user. If this applies to your hardware,
1050 config HANGCHECK_TIMER
1051 tristate "Hangcheck timer"
1052 depends on X86 || IA64 || PPC64 || S390
1054 The hangcheck-timer module detects when the system has gone
1055 out to lunch past a certain margin. It can reboot the system
1056 or merely print a warning.
1059 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1060 depends on IA64_GENERIC || IA64_SGI_SN2
1063 The mmtimer device allows direct userspace access to the
1066 source "drivers/char/tpm/Kconfig"
1069 tristate "Telecom clock driver for ATCA SBC"
1070 depends on EXPERIMENTAL && X86
1073 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1074 ATCA computers and allows direct userspace access to the
1075 configuration of the telecom clock configuration settings. This
1076 device is used for hardware synchronization across the ATCA backplane
1077 fabric. Upon loading, the driver exports a sysfs directory,
1078 /sys/devices/platform/telco_clock, with a number of files for
1079 controlling the behavior of this hardware.
1084 depends on ISA || PCI
1087 source "drivers/s390/char/Kconfig"
projects / linux-2.6-omap-h63xx.git / blob