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)
134 This driver supports Cyclades Z and Y multiserial boards.
135 You would need something like this to connect more than two modems to
136 your Linux box, for instance in order to become a dial-in server.
138 For information about the Cyclades-Z card, read
139 <file:drivers/char/README.cycladesZ>.
141 To compile this driver as a module, choose M here: the
142 module will be called cyclades.
144 If you haven't heard about it, it's safe to say N.
147 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
148 depends on EXPERIMENTAL && CYCLADES
150 The Cyclades-Z family of multiport cards allows 2 (two) driver op
151 modes: polling and interrupt. In polling mode, the driver will check
152 the status of the Cyclades-Z ports every certain amount of time
153 (which is called polling cycle and is configurable). In interrupt
154 mode, it will use an interrupt line (IRQ) in order to check the
155 status of the Cyclades-Z ports. The default op mode is polling. If
159 tristate "Digiboard Intelligent Async Support"
160 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
162 This is a driver for Digi International's Xx, Xeve, and Xem series
163 of cards which provide multiple serial ports. You would need
164 something like this to connect more than two modems to your Linux
165 box, for instance in order to become a dial-in server. This driver
166 supports the original PC (ISA) boards as well as PCI, and EISA. If
167 you have a card like this, say Y here and read the file
168 <file:Documentation/digiepca.txt>.
170 To compile this driver as a module, choose M here: the
171 module will be called epca.
174 tristate "Hayes ESP serial port support"
175 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
177 This is a driver which supports Hayes ESP serial ports. Both single
178 port cards and multiport cards are supported. Make sure to read
179 <file:Documentation/hayes-esp.txt>.
181 To compile this driver as a module, choose M here: the
182 module will be called esp.
187 tristate "Moxa Intellio support"
188 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
190 Say Y here if you have a Moxa Intellio multiport serial card.
192 To compile this driver as a module, choose M here: the
193 module will be called moxa.
196 tristate "Moxa SmartIO support (OBSOLETE)"
197 depends on SERIAL_NONSTANDARD
199 Say Y here if you have a Moxa SmartIO multiport serial card.
201 This driver can also be built as a module ( = code which can be
202 inserted in and removed from the running kernel whenever you want).
203 The module will be called mxser. If you want to do that, say M
206 config MOXA_SMARTIO_NEW
207 tristate "Moxa SmartIO support v. 2.0"
208 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
210 Say Y here if you have a Moxa SmartIO multiport serial card and/or
211 want to help develop a new version of this driver.
213 This is upgraded (1.9.1) driver from original Moxa drivers with
214 changes finally resulting in PCI probing.
216 This driver can also be built as a module. The module will be called
217 mxser_new. 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 && BROKEN_ON_SMP
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 "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 "Parallel printer support"
488 If you intend to attach a printer to the parallel port of your Linux
489 box (as opposed to using a serial printer; if the connector at the
490 printer has 9 or 25 holes ["female"], then it's serial), say Y.
491 Also read the Printing-HOWTO, available from
492 <http://www.tldp.org/docs.html#howto>.
494 It is possible to share one parallel port among several devices
495 (e.g. printer and ZIP drive) and it is safe to compile the
496 corresponding drivers into the kernel.
498 To compile this driver as a module, choose M here and read
499 <file:Documentation/parport.txt>. The module will be called lp.
501 If you have several parallel ports, you can specify which ports to
502 use with the "lp" kernel command line option. (Try "man bootparam"
503 or see the documentation of your boot loader (lilo or loadlin) about
504 how to pass options to the kernel at boot time.) The syntax of the
505 "lp" command line option can be found in <file:drivers/char/lp.c>.
507 If you have more than 8 printers, you need to increase the LP_NO
508 macro in lp.c and the PARPORT_MAX macro in parport.h.
511 bool "Support for console on line printer"
514 If you want kernel messages to be printed out as they occur, you
515 can have a console on the printer. This option adds support for
516 doing that; to actually get it to happen you need to pass the
517 option "console=lp0" to the kernel at boot time.
519 If the printer is out of paper (or off, or unplugged, or too
520 busy..) the kernel will stall until the printer is ready again.
521 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
522 can make the kernel continue when this happens,
523 but it'll lose the kernel messages.
528 tristate "Support for user-space parallel port device drivers"
531 Saying Y to this adds support for /dev/parport device nodes. This
532 is needed for programs that want portable access to the parallel
533 port, for instance deviceid (which displays Plug-and-Play device
536 This is the parallel port equivalent of SCSI generic support (sg).
537 It is safe to say N to this -- it is not needed for normal printing
538 or parallel port CD-ROM/disk support.
540 To compile this driver as a module, choose M here: the
541 module will be called ppdev.
546 tristate "Texas Instruments parallel link cable support"
549 If you own a Texas Instruments graphing calculator and use a
550 parallel link cable, then you might be interested in this driver.
552 If you enable this driver, you will be able to communicate with
553 your calculator through a set of device nodes under /dev. The
554 main advantage of this driver is that you don't have to be root
555 to use this precise link cable (depending on the permissions on
556 the device nodes, though).
558 To compile this driver as a module, choose M here: the
559 module will be called tipar.
561 If you don't know what a parallel link cable is or what a Texas
562 Instruments graphing calculator is, then you probably don't need this
570 Users of pSeries machines that want to utilize the hvc console front-end
571 module for their backend console driver should select this option.
572 It will automatically be selected if one of the back-end console drivers
577 bool "pSeries Hypervisor Virtual Console support"
578 depends on PPC_PSERIES
581 pSeries machines when partitioned support a hypervisor virtual
582 console. This driver allows each pSeries partition to have a console
583 which is accessed via the HMC.
586 bool "iSeries Hypervisor Virtual Console support"
587 depends on PPC_ISERIES
591 iSeries machines support a hypervisor virtual console.
594 bool "IBM RTAS Console support"
598 IBM Console device driver which makes use of RTAS
601 bool "Toshiba's Beat Hypervisor Console support"
602 depends on PPC_CELLEB
605 Toshiba's Cell Reference Set Beat Console device driver
608 bool "Xen Hypervisor Console support"
613 Xen virtual console device driver
616 tristate "IBM Hypervisor Virtual Console Server support"
617 depends on PPC_PSERIES
619 Partitionable IBM Power5 ppc64 machines allow hosting of
620 firmware virtual consoles from one Linux partition by
621 another Linux partition. This driver allows console data
622 from Linux partitions to be accessed through TTY device
623 interfaces in the device tree of a Linux partition running
626 To compile this driver as a module, choose M here: the
627 module will be called hvcs.ko. Additionally, this module
628 will depend on arch specific APIs exported from hvcserver.ko
629 which will also be compiled when this driver is built as a
632 source "drivers/char/ipmi/Kconfig"
634 source "drivers/char/watchdog/Kconfig"
637 tristate "NetWinder thermometer support"
638 depends on ARCH_NETWINDER
640 Say Y here to include support for the thermal management hardware
641 found in the NetWinder. This driver allows the user to control the
642 temperature set points and to read the current temperature.
644 It is also possible to say M here to build it as a module (ds1620)
645 It is recommended to be used on a NetWinder, but it is not a
649 tristate "NetWinder Button"
650 depends on ARCH_NETWINDER
652 If you say Y here and create a character device node /dev/nwbutton
653 with major and minor numbers 10 and 158 ("man mknod"), then every
654 time the orange button is pressed a number of times, the number of
655 times the button was pressed will be written to that device.
657 This is most useful for applications, as yet unwritten, which
658 perform actions based on how many times the button is pressed in a
661 Do not hold the button down for too long, as the driver does not
662 alter the behaviour of the hardware reset circuitry attached to the
663 button; it will still execute a hard reset if the button is held
664 down for longer than approximately five seconds.
666 To compile this driver as a module, choose M here: the
667 module will be called nwbutton.
669 Most people will answer Y to this question and "Reboot Using Button"
670 below to be able to initiate a system shutdown from the button.
672 config NWBUTTON_REBOOT
673 bool "Reboot Using Button"
676 If you say Y here, then you will be able to initiate a system
677 shutdown and reboot by pressing the orange button a number of times.
678 The number of presses to initiate the shutdown is two by default,
679 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
680 in nwbutton.h and recompiling the driver or, if you compile the
681 driver as a module, you can specify the number of presses at load
682 time with "insmod button reboot_count=<something>".
685 tristate "NetWinder flash support"
686 depends on ARCH_NETWINDER
688 If you say Y here and create a character device /dev/flash with
689 major 10 and minor 160 you can manipulate the flash ROM containing
690 the NetWinder firmware. Be careful as accidentally overwriting the
691 flash contents can render your computer unbootable. On no account
692 allow random users access to this device. :-)
694 To compile this driver as a module, choose M here: the
695 module will be called nwflash.
697 If you're not sure, say N.
699 source "drivers/char/hw_random/Kconfig"
702 tristate "/dev/nvram support"
703 depends on ATARI || X86 || ARM || GENERIC_NVRAM
705 If you say Y here and create a character special file /dev/nvram
706 with major number 10 and minor number 144 using mknod ("man mknod"),
707 you get read and write access to the extra bytes of non-volatile
708 memory in the real time clock (RTC), which is contained in every PC
709 and most Ataris. The actual number of bytes varies, depending on the
710 nvram in the system, but is usually 114 (128-14 for the RTC).
712 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
713 on Ataris. /dev/nvram may be used to view settings there, or to
714 change them (with some utility). It could also be used to frequently
715 save a few bits of very important data that may not be lost over
716 power-off and for which writing to disk is too insecure. Note
717 however that most NVRAM space in a PC belongs to the BIOS and you
718 should NEVER idly tamper with it. See Ralf Brown's interrupt list
719 for a guide to the use of CMOS bytes by your BIOS.
721 On Atari machines, /dev/nvram is always configured and does not need
724 To compile this driver as a module, choose M here: the
725 module will be called nvram.
728 tristate "Enhanced Real Time Clock Support"
729 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC64 && (!SPARC32 || PCI) && !FRV && !ARM && !SUPERH && !S390
731 If you say Y here and create a character special file /dev/rtc with
732 major number 10 and minor number 135 using mknod ("man mknod"), you
733 will get access to the real time clock (or hardware clock) built
736 Every PC has such a clock built in. It can be used to generate
737 signals from as low as 1Hz up to 8192Hz, and can also be used
738 as a 24 hour alarm. It reports status information via the file
739 /proc/driver/rtc and its behaviour is set by various ioctls on
742 If you run Linux on a multiprocessor machine and said Y to
743 "Symmetric Multi Processing" above, you should say Y here to read
744 and set the RTC in an SMP compatible fashion.
746 If you think you have a use for such a device (such as periodic data
747 sampling), then say Y here, and read <file:Documentation/rtc.txt>
750 To compile this driver as a module, choose M here: the
751 module will be called rtc.
754 tristate "SGI DS1286 RTC support"
757 If you say Y here and create a character special file /dev/rtc with
758 major number 10 and minor number 135 using mknod ("man mknod"), you
759 will get access to the real time clock built into your computer.
760 Every SGI has such a clock built in. It reports status information
761 via the file /proc/rtc and its behaviour is set by various ioctls on
765 bool "SGI M48T35 RTC support"
768 If you say Y here and create a character special file /dev/rtc with
769 major number 10 and minor number 135 using mknod ("man mknod"), you
770 will get access to the real time clock built into your computer.
771 Every SGI has such a clock built in. It reports status information
772 via the file /proc/rtc and its behaviour is set by various ioctls on
776 tristate "Generic /dev/rtc emulation"
777 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH
779 If you say Y here and create a character special file /dev/rtc with
780 major number 10 and minor number 135 using mknod ("man mknod"), you
781 will get access to the real time clock (or hardware clock) built
784 It reports status information via the file /proc/driver/rtc and its
785 behaviour is set by various ioctls on /dev/rtc. If you enable the
786 "extended RTC operation" below it will also provide an emulation
787 for RTC_UIE which is required by some programs and may improve
788 precision in some cases.
790 To compile this driver as a module, choose M here: the
791 module will be called genrtc.
794 bool "Extended RTC operation"
797 Provides an emulation for RTC_UIE which is required by some programs
798 and may improve precision of the generic RTC support in some cases.
801 bool "EFI Real Time Clock Services"
805 tristate "DS1302 RTC support"
806 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
808 If you say Y here and create a character special file /dev/rtc with
809 major number 121 and minor number 0 using mknod ("man mknod"), you
810 will get access to the real time clock (or hardware clock) built
814 bool "Support for Cobalt LCD"
815 depends on MIPS_COBALT
817 This option enables support for the LCD display and buttons found
818 on Cobalt systems through a misc device.
821 tristate "Double Talk PC internal speech card support"
824 This driver is for the DoubleTalk PC, a speech synthesizer
825 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
826 called the `internal DoubleTalk'.
828 To compile this driver as a module, choose M here: the
829 module will be called dtlk.
832 tristate "Siemens R3964 line discipline"
834 This driver allows synchronous communication with devices using the
835 Siemens R3964 packet protocol. Unless you are dealing with special
836 hardware like PLCs, you are unlikely to need this.
838 To compile this driver as a module, choose M here: the
839 module will be called n_r3964.
844 tristate "Applicom intelligent fieldbus card support"
847 This driver provides the kernel-side support for the intelligent
848 fieldbus cards made by Applicom International. More information
849 about these cards can be found on the WWW at the address
850 <http://www.applicom-int.com/>, or by email from David Woodhouse
851 <dwmw2@infradead.org>.
853 To compile this driver as a module, choose M here: the
854 module will be called applicom.
859 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
860 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
862 This driver enables access to the Sony Programmable I/O Control
863 Device which can be found in many (all ?) Sony Vaio laptops.
865 If you have one of those laptops, read
866 <file:Documentation/sonypi.txt>, and say Y or M here.
868 To compile this driver as a module, choose M here: the
869 module will be called sonypi.
872 tristate "TANBAC TB0219 GPIO support"
873 depends on TANBAC_TB022X
876 source "drivers/char/agp/Kconfig"
878 source "drivers/char/drm/Kconfig"
880 source "drivers/char/pcmcia/Kconfig"
883 tristate "ACP Modem (Mwave) support"
887 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
888 kernel driver and a user level application. Together these components
889 support direct attachment to public switched telephone networks (PSTNs)
890 and support selected world wide countries.
892 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
893 600, and 770 that include on board ACP modem hardware.
895 The modem also supports the standard communications port interface
896 (ttySx) and is compatible with the Hayes AT Command Set.
898 The user level application needed to use this driver can be found at
899 the IBM Linux Technology Center (LTC) web site:
900 <http://www.ibm.com/linux/ltc/>.
902 If you own one of the above IBM Thinkpads which has the Mwave chipset
905 To compile this driver as a module, choose M here: the
906 module will be called mwave.
909 tristate "NatSemi SCx200 GPIO Support"
913 Give userspace access to the GPIO pins on the National
914 Semiconductor SCx200 processors.
916 If compiled as a module, it will be called scx200_gpio.
919 tristate "NatSemi PC8736x GPIO Support"
921 default SCx200_GPIO # mostly N
922 select NSC_GPIO # needed for support routines
924 Give userspace access to the GPIO pins on the National
925 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
926 has multiple functional units, inc several managed by
927 hwmon/pc87360 driver. Tested with PC-87366
929 If compiled as a module, it will be called pc8736x_gpio.
932 tristate "NatSemi Base GPIO Support"
934 # selected by SCx200_GPIO and PC8736x_GPIO
935 # what about 2 selectors differing: m != y
937 Common support used (and needed) by scx200_gpio and
938 pc8736x_gpio drivers. If those drivers are built as
939 modules, this one will be too, named nsc_gpio
942 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
945 Give userspace access to the GPIO pins on the AMD CS5535 and
946 CS5536 Geode companion devices.
948 If compiled as a module, it will be called cs5535_gpio.
951 tristate "NEC VR4100 series General-purpose I/O Unit support"
952 depends on CPU_VR41XX
955 tristate "RAW driver (/dev/raw/rawN)"
958 The raw driver permits block devices to be bound to /dev/raw/rawN.
959 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
960 See the raw(8) manpage for more details.
962 Applications should preferably open the device (eg /dev/hda1)
963 with the O_DIRECT flag.
966 int "Maximum number of RAW devices to support (1-8192)"
967 depends on RAW_DRIVER
970 The maximum number of RAW devices that are supported.
971 Default is 256. Increase this number in case you need lots of
975 bool "HPET - High Precision Event Timer" if (X86 || IA64)
979 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
980 open selects one of the timers supported by the HPET. The timers are
981 non-periodic and/or periodic.
984 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
988 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
989 is assumed the platform called hpet_alloc with the RTC IRQ values for
993 bool "Allow mmap of HPET"
997 If you say Y here, user applications will be able to mmap
1000 In some hardware implementations, the page containing HPET
1001 registers may also contain other things that shouldn't be
1002 exposed to the user. If this applies to your hardware,
1005 config HANGCHECK_TIMER
1006 tristate "Hangcheck timer"
1007 depends on X86 || IA64 || PPC64 || S390
1009 The hangcheck-timer module detects when the system has gone
1010 out to lunch past a certain margin. It can reboot the system
1011 or merely print a warning.
1014 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1015 depends on IA64_GENERIC || IA64_SGI_SN2
1018 The mmtimer device allows direct userspace access to the
1021 source "drivers/char/tpm/Kconfig"
1024 tristate "Telecom clock driver for ATCA SBC"
1025 depends on EXPERIMENTAL && X86
1028 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1029 ATCA computers and allows direct userspace access to the
1030 configuration of the telecom clock configuration settings. This
1031 device is used for hardware synchronization across the ATCA backplane
1032 fabric. Upon loading, the driver exports a sysfs directory,
1033 /sys/devices/platform/telco_clock, with a number of files for
1034 controlling the behavior of this hardware.
1039 depends on ISA || PCI
1042 source "drivers/s390/char/Kconfig"
projects / linux-2.6 / blob