2 # Character device configuration
5 menu "Character devices"
8 bool "Virtual terminal" if EMBEDDED
12 If you say Y here, you will get support for terminal devices with
13 display and keyboard devices. These are called "virtual" because you
14 can run several virtual terminals (also called virtual consoles) on
15 one physical terminal. This is rather useful, for example one
16 virtual terminal can collect system messages and warnings, another
17 one can be used for a text-mode user session, and a third could run
18 an X session, all in parallel. Switching between virtual terminals
19 is done with certain key combinations, usually Alt-<function key>.
21 The setterm command ("man setterm") can be used to change the
22 properties (such as colors or beeping) of a virtual terminal. The
23 man page console_codes(4) ("man console_codes") contains the special
24 character sequences that can be used to change those properties
25 directly. The fonts used on virtual terminals can be changed with
26 the setfont ("man setfont") command and the key bindings are defined
27 with the loadkeys ("man loadkeys") command.
29 You need at least one virtual terminal device in order to make use
30 of your keyboard and monitor. Therefore, only people configuring an
31 embedded system would want to say N here in order to save some
32 memory; the only way to log into such a system is then via a serial
33 or network connection.
35 If unsure, say Y, or else you won't be able to do much with your new
36 shiny Linux system :-)
39 bool "Support for console on virtual terminal" if EMBEDDED
43 The system console is the device which receives all kernel messages
44 and warnings and which allows logins in single user mode. If you
45 answer Y here, a virtual terminal (the device used to interact with
46 a physical terminal) can be used as system console. This is the most
47 common mode of operations, so you should say Y here unless you want
48 the kernel messages be output only to a serial port (in which case
49 you should say Y to "Console on serial port", below).
51 If you do say Y here, by default the currently visible virtual
52 terminal (/dev/tty0) will be used as system console. You can change
53 that with a kernel command line option such as "console=tty3" which
54 would use the third virtual terminal as system console. (Try "man
55 bootparam" or see the documentation of your boot loader (lilo or
56 loadlin) about how to pass options to the kernel at boot time.)
62 depends on VT && !S390 && !UML
65 config VT_HW_CONSOLE_BINDING
66 bool "Support for binding and unbinding console drivers"
70 The virtual terminal is the device that interacts with the physical
71 terminal through console drivers. On these systems, at least one
72 console driver is loaded. In other configurations, additional console
73 drivers may be enabled, such as the framebuffer console. If more than
74 1 console driver is enabled, setting this to 'y' will allow you to
75 select the console driver that will serve as the backend for the
78 See <file:Documentation/console/console.txt> for more
79 information. For framebuffer console users, please refer to
80 <file:Documentation/fb/fbcon.txt>.
82 config SERIAL_NONSTANDARD
83 bool "Non-standard serial port support"
85 Say Y here if you have any non-standard serial boards -- boards
86 which aren't supported using the standard "dumb" serial driver.
87 This includes intelligent serial boards such as Cyclades,
88 Digiboards, etc. These are usually used for systems that need many
89 serial ports because they serve many terminals or dial-in
92 Note that the answer to this question won't directly affect the
93 kernel: saying N will just cause the configurator to skip all
94 the questions about non-standard serial boards.
96 Most people can say N here.
99 tristate "Computone IntelliPort Plus serial support"
100 depends on SERIAL_NONSTANDARD
102 This driver supports the entire family of Intelliport II/Plus
103 controllers with the exception of the MicroChannel controllers and
104 products previous to the Intelliport II. These are multiport cards,
105 which give you many serial ports. You would need something like this
106 to connect more than two modems to your Linux box, for instance in
107 order to become a dial-in server. If you have a card like that, say
108 Y here and read <file:Documentation/computone.txt>.
110 To compile this driver as modules, choose M here: the
111 modules will be called ip2 and ip2main.
114 tristate "Comtrol RocketPort support"
115 depends on SERIAL_NONSTANDARD
117 This driver supports Comtrol RocketPort and RocketModem PCI boards.
118 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
119 modems. For information about the RocketPort/RocketModem boards
120 and this driver read <file:Documentation/rocket.txt>.
122 To compile this driver as a module, choose M here: the
123 module will be called rocket.
125 If you want to compile this driver into the kernel, say Y here. If
126 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
129 tristate "Cyclades async mux support"
130 depends on SERIAL_NONSTANDARD
132 This driver supports Cyclades Z and Y multiserial boards.
133 You would need something like this to connect more than two modems to
134 your Linux box, for instance in order to become a dial-in server.
136 For information about the Cyclades-Z card, read
137 <file:drivers/char/README.cycladesZ>.
139 To compile this driver as a module, choose M here: the
140 module will be called cyclades.
142 If you haven't heard about it, it's safe to say N.
145 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
146 depends on EXPERIMENTAL && CYCLADES
148 The Cyclades-Z family of multiport cards allows 2 (two) driver op
149 modes: polling and interrupt. In polling mode, the driver will check
150 the status of the Cyclades-Z ports every certain amount of time
151 (which is called polling cycle and is configurable). In interrupt
152 mode, it will use an interrupt line (IRQ) in order to check the
153 status of the Cyclades-Z ports. The default op mode is polling. If
157 tristate "Digiboard Intelligent Async Support"
158 depends on SERIAL_NONSTANDARD
160 This is a driver for Digi International's Xx, Xeve, and Xem series
161 of cards which provide multiple serial ports. You would need
162 something like this to connect more than two modems to your Linux
163 box, for instance in order to become a dial-in server. This driver
164 supports the original PC (ISA) boards as well as PCI, and EISA. If
165 you have a card like this, say Y here and read the file
166 <file:Documentation/digiepca.txt>.
168 To compile this driver as a module, choose M here: the
169 module will be called epca.
172 tristate "Hayes ESP serial port support"
173 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
175 This is a driver which supports Hayes ESP serial ports. Both single
176 port cards and multiport cards are supported. Make sure to read
177 <file:Documentation/hayes-esp.txt>.
179 To compile this driver as a module, choose M here: the
180 module will be called esp.
185 tristate "Moxa Intellio support"
186 depends on SERIAL_NONSTANDARD
188 Say Y here if you have a Moxa Intellio multiport serial card.
190 To compile this driver as a module, choose M here: the
191 module will be called moxa.
194 tristate "Moxa SmartIO support"
195 depends on SERIAL_NONSTANDARD
197 Say Y here if you have a Moxa SmartIO multiport serial card.
199 This driver can also be built as a module ( = code which can be
200 inserted in and removed from the running kernel whenever you want).
201 The module will be called mxser. If you want to do that, say M
205 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
206 depends on SERIAL_NONSTANDARD
209 This is a driver for the Multi-Tech cards which provide several
210 serial ports. The driver is experimental and can currently only be
211 built as a module. The module will be called isicom.
212 If you want to do that, choose M here.
215 tristate "Microgate SyncLink card support"
216 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
218 Provides support for the SyncLink ISA and PCI multiprotocol serial
219 adapters. These adapters support asynchronous and HDLC bit
220 synchronous communication up to 10Mbps (PCI adapter).
222 This driver can only be built as a module ( = code which can be
223 inserted in and removed from the running kernel whenever you want).
224 The module will be called synclink. If you want to do that, say M
228 tristate "SyncLink Multiport support"
229 depends on SERIAL_NONSTANDARD
231 Enable support for the SyncLink Multiport (2 or 4 ports)
232 serial adapter, running asynchronous and HDLC communications up
233 to 2.048Mbps. Each ports is independently selectable for
234 RS-232, V.35, RS-449, RS-530, and X.21
236 This driver may be built as a module ( = code which can be
237 inserted in and removed from the running kernel whenever you want).
238 The module will be called synclinkmp. If you want to do that, say M
242 tristate "SyncLink GT/AC support"
243 depends on SERIAL_NONSTANDARD && PCI
245 Support for SyncLink GT and SyncLink AC families of
246 synchronous and asynchronous serial adapters
247 manufactured by Microgate Systems, Ltd. (www.microgate.com)
250 tristate "HDLC line discipline support"
251 depends on SERIAL_NONSTANDARD
253 Allows synchronous HDLC communications with tty device drivers that
254 support synchronous HDLC such as the Microgate SyncLink adapter.
256 This driver can only be built as a module ( = code which can be
257 inserted in and removed from the running kernel whenever you want).
258 The module will be called n_hdlc. If you want to do that, say M
262 tristate "SDL RISCom/8 card support"
263 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
265 This is a driver for the SDL Communications RISCom/8 multiport card,
266 which gives you many serial ports. You would need something like
267 this to connect more than two modems to your Linux box, for instance
268 in order to become a dial-in server. If you have a card like that,
269 say Y here and read the file <file:Documentation/riscom8.txt>.
271 Also it's possible to say M here and compile this driver as kernel
272 loadable module; the module will be called riscom8.
275 tristate "Specialix IO8+ card support"
276 depends on SERIAL_NONSTANDARD
278 This is a driver for the Specialix IO8+ multiport card (both the
279 ISA and the PCI version) which gives you many serial ports. You
280 would need something like this to connect more than two modems to
281 your Linux box, for instance in order to become a dial-in server.
283 If you have a card like that, say Y here and read the file
284 <file:Documentation/specialix.txt>. Also it's possible to say M here
285 and compile this driver as kernel loadable module which will be
288 config SPECIALIX_RTSCTS
289 bool "Specialix DTR/RTS pin is RTS"
292 The Specialix IO8+ card can only support either RTS or DTR. If you
293 say N here, the driver will use the pin as "DTR" when the tty is in
294 software handshake mode. If you say Y here or hardware handshake is
295 on, it will always be RTS. Read the file
296 <file:Documentation/specialix.txt> for more information.
299 tristate "Specialix SX (and SI) card support"
300 depends on SERIAL_NONSTANDARD
302 This is a driver for the SX and SI multiport serial cards.
303 Please read the file <file:Documentation/sx.txt> for details.
305 This driver can only be built as a module ( = code which can be
306 inserted in and removed from the running kernel whenever you want).
307 The module will be called sx. If you want to do that, say M here.
310 tristate "Specialix RIO system support"
311 depends on SERIAL_NONSTANDARD
313 This is a driver for the Specialix RIO, a smart serial card which
314 drives an outboard box that can support up to 128 ports. Product
315 information is at <http://www.perle.com/support/documentation.html#multiport>.
316 There are both ISA and PCI versions.
319 bool "Support really old RIO/PCI cards"
322 Older RIO PCI cards need some initialization-time configuration to
323 determine the IRQ and some control addresses. If you have a RIO and
324 this doesn't seem to work, try setting this to Y.
327 bool "Stallion multiport serial support"
328 depends on SERIAL_NONSTANDARD
330 Stallion cards give you many serial ports. You would need something
331 like this to connect more than two modems to your Linux box, for
332 instance in order to become a dial-in server. If you say Y here,
333 you will be asked for your specific card model in the next
334 questions. Make sure to read <file:Documentation/stallion.txt> in
335 this case. If you have never heard about all this, it's safe to
339 tristate "Stallion EasyIO or EC8/32 support"
340 depends on STALDRV && BROKEN_ON_SMP
342 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
343 card, then this is for you; say Y. Make sure to read
344 <file:Documentation/stallion.txt>.
346 To compile this driver as a module, choose M here: the
347 module will be called stallion.
350 tristate "Stallion EC8/64, ONboard, Brumby support"
351 depends on STALDRV && BROKEN_ON_SMP
353 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
354 serial multiport card, say Y here. Make sure to read
355 <file:Documentation/stallion.txt>.
357 To compile this driver as a module, choose M here: the
358 module will be called istallion.
361 bool "Enable Au1000 UART Support"
362 depends on SERIAL_NONSTANDARD && MIPS
364 If you have an Alchemy AU1000 processor (MIPS based) and you want
365 to use serial ports, say Y. Otherwise, say N.
367 config AU1000_SERIAL_CONSOLE
368 bool "Enable Au1000 serial console"
369 depends on AU1000_UART
371 If you have an Alchemy AU1000 processor (MIPS based) and you want
372 to use a console on a serial port, say Y. Otherwise, say N.
374 config QTRONIX_KEYBOARD
375 bool "Enable Qtronix 990P Keyboard Support"
378 Images of Qtronix keyboards are at
379 <http://www.qtronix.com/keyboard.html>.
383 depends on QTRONIX_KEYBOARD
387 bool "Enable Smart Card Reader 0 Support "
390 Say Y here to support smart-card reader 0 (SCR0) on the Integrated
391 Technology Express, Inc. ITE8172 SBC. Vendor page at
392 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
393 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
396 bool "Enable Smart Card Reader 1 Support "
399 Say Y here to support smart-card reader 1 (SCR1) on the Integrated
400 Technology Express, Inc. ITE8172 SBC. Vendor page at
401 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
402 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
405 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
406 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
408 This option supports the 2232 7-port serial card shipped with the
409 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
410 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
411 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
412 ports were connected with 8 pin DIN connectors on the card bracket,
413 for which 8 pin to DB25 adapters were supplied. The card also had
414 jumpers internally to toggle various pinning configurations.
416 This driver can be built as a module; but then "generic_serial"
417 will also be built as a module. This has to be loaded before
418 "ser_a2232". If you want to do this, answer M here.
421 bool "SGI Altix system controller communication support"
422 depends on (IA64_SGI_SN2 || IA64_GENERIC)
424 If you have an SGI Altix and you want to enable system
425 controller communication from user space (you want this!),
426 say Y. Otherwise, say N.
429 bool "SGI TIO CX driver support"
430 depends on (IA64_SGI_SN2 || IA64_GENERIC)
432 If you have an SGI Altix and you have fpga devices attached
433 to your TIO, say Y here, otherwise say N.
436 tristate "SGI FPGA Core Services driver support"
439 If you have an SGI Altix with an attached SABrick
440 say Y or M here, otherwise say N.
442 source "drivers/serial/Kconfig"
445 bool "Unix98 PTY support" if EMBEDDED
448 A pseudo terminal (PTY) is a software device consisting of two
449 halves: a master and a slave. The slave device behaves identical to
450 a physical terminal; the master device is used by a process to
451 read data from and write data to the slave, thereby emulating a
452 terminal. Typical programs for the master side are telnet servers
455 Linux has traditionally used the BSD-like names /dev/ptyxx for
456 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
457 has a number of problems. The GNU C library glibc 2.1 and later,
458 however, supports the Unix98 naming standard: in order to acquire a
459 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
460 terminal is then made available to the process and the pseudo
461 terminal slave can be accessed as /dev/pts/<number>. What was
462 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
464 All modern Linux systems use the Unix98 ptys. Say Y unless
465 you're on an embedded system and want to conserve memory.
468 bool "Legacy (BSD) PTY support"
471 A pseudo terminal (PTY) is a software device consisting of two
472 halves: a master and a slave. The slave device behaves identical to
473 a physical terminal; the master device is used by a process to
474 read data from and write data to the slave, thereby emulating a
475 terminal. Typical programs for the master side are telnet servers
478 Linux has traditionally used the BSD-like names /dev/ptyxx
479 for masters and /dev/ttyxx for slaves of pseudo
480 terminals. This scheme has a number of problems, including
481 security. This option enables these legacy devices; on most
482 systems, it is safe to say N.
485 tristate "Crash Utility memory driver"
487 config LEGACY_PTY_COUNT
488 int "Maximum number of legacy PTY in use"
489 depends on LEGACY_PTYS
493 The maximum number of legacy PTYs that can be used at any one time.
494 The default is 256, and should be more than enough. Embedded
495 systems may want to reduce this to save memory.
497 When not in use, each legacy PTY occupies 12 bytes on 32-bit
498 architectures and 24 bytes on 64-bit architectures.
501 tristate "Parallel printer support"
504 If you intend to attach a printer to the parallel port of your Linux
505 box (as opposed to using a serial printer; if the connector at the
506 printer has 9 or 25 holes ["female"], then it's serial), say Y.
507 Also read the Printing-HOWTO, available from
508 <http://www.tldp.org/docs.html#howto>.
510 It is possible to share one parallel port among several devices
511 (e.g. printer and ZIP drive) and it is safe to compile the
512 corresponding drivers into the kernel.
514 To compile this driver as a module, choose M here and read
515 <file:Documentation/parport.txt>. The module will be called lp.
517 If you have several parallel ports, you can specify which ports to
518 use with the "lp" kernel command line option. (Try "man bootparam"
519 or see the documentation of your boot loader (lilo or loadlin) about
520 how to pass options to the kernel at boot time.) The syntax of the
521 "lp" command line option can be found in <file:drivers/char/lp.c>.
523 If you have more than 8 printers, you need to increase the LP_NO
524 macro in lp.c and the PARPORT_MAX macro in parport.h.
527 bool "Support for console on line printer"
530 If you want kernel messages to be printed out as they occur, you
531 can have a console on the printer. This option adds support for
532 doing that; to actually get it to happen you need to pass the
533 option "console=lp0" to the kernel at boot time.
535 If the printer is out of paper (or off, or unplugged, or too
536 busy..) the kernel will stall until the printer is ready again.
537 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
538 can make the kernel continue when this happens,
539 but it'll lose the kernel messages.
544 tristate "Support for user-space parallel port device drivers"
547 Saying Y to this adds support for /dev/parport device nodes. This
548 is needed for programs that want portable access to the parallel
549 port, for instance deviceid (which displays Plug-and-Play device
552 This is the parallel port equivalent of SCSI generic support (sg).
553 It is safe to say N to this -- it is not needed for normal printing
554 or parallel port CD-ROM/disk support.
556 To compile this driver as a module, choose M here: the
557 module will be called ppdev.
562 tristate "Texas Instruments parallel link cable support"
565 If you own a Texas Instruments graphing calculator and use a
566 parallel link cable, then you might be interested in this driver.
568 If you enable this driver, you will be able to communicate with
569 your calculator through a set of device nodes under /dev. The
570 main advantage of this driver is that you don't have to be root
571 to use this precise link cable (depending on the permissions on
572 the device nodes, though).
574 To compile this driver as a module, choose M here: the
575 module will be called tipar.
577 If you don't know what a parallel link cable is or what a Texas
578 Instruments graphing calculator is, then you probably don't need this
586 Users of pSeries machines that want to utilize the hvc console front-end
587 module for their backend console driver should select this option.
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 "IBM RTAS Console support"
606 IBM Console device driver which makes use of RTAS
609 tristate "IBM Hypervisor Virtual Console Server support"
610 depends on PPC_PSERIES
612 Partitionable IBM Power5 ppc64 machines allow hosting of
613 firmware virtual consoles from one Linux partition by
614 another Linux partition. This driver allows console data
615 from Linux partitions to be accessed through TTY device
616 interfaces in the device tree of a Linux partition running
619 To compile this driver as a module, choose M here: the
620 module will be called hvcs.ko. Additionally, this module
621 will depend on arch specific APIs exported from hvcserver.ko
622 which will also be compiled when this driver is built as a
625 source "drivers/char/ipmi/Kconfig"
627 source "drivers/char/watchdog/Kconfig"
630 tristate "NetWinder thermometer support"
631 depends on ARCH_NETWINDER
633 Say Y here to include support for the thermal management hardware
634 found in the NetWinder. This driver allows the user to control the
635 temperature set points and to read the current temperature.
637 It is also possible to say M here to build it as a module (ds1620)
638 It is recommended to be used on a NetWinder, but it is not a
642 tristate "NetWinder Button"
643 depends on ARCH_NETWINDER
645 If you say Y here and create a character device node /dev/nwbutton
646 with major and minor numbers 10 and 158 ("man mknod"), then every
647 time the orange button is pressed a number of times, the number of
648 times the button was pressed will be written to that device.
650 This is most useful for applications, as yet unwritten, which
651 perform actions based on how many times the button is pressed in a
654 Do not hold the button down for too long, as the driver does not
655 alter the behaviour of the hardware reset circuitry attached to the
656 button; it will still execute a hard reset if the button is held
657 down for longer than approximately five seconds.
659 To compile this driver as a module, choose M here: the
660 module will be called nwbutton.
662 Most people will answer Y to this question and "Reboot Using Button"
663 below to be able to initiate a system shutdown from the button.
665 config NWBUTTON_REBOOT
666 bool "Reboot Using Button"
669 If you say Y here, then you will be able to initiate a system
670 shutdown and reboot by pressing the orange button a number of times.
671 The number of presses to initiate the shutdown is two by default,
672 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
673 in nwbutton.h and recompiling the driver or, if you compile the
674 driver as a module, you can specify the number of presses at load
675 time with "insmod button reboot_count=<something>".
678 tristate "NetWinder flash support"
679 depends on ARCH_NETWINDER
681 If you say Y here and create a character device /dev/flash with
682 major 10 and minor 160 you can manipulate the flash ROM containing
683 the NetWinder firmware. Be careful as accidentally overwriting the
684 flash contents can render your computer unbootable. On no account
685 allow random users access to this device. :-)
687 To compile this driver as a module, choose M here: the
688 module will be called nwflash.
690 If you're not sure, say N.
692 source "drivers/char/hw_random/Kconfig"
695 tristate "/dev/nvram support"
696 depends on ATARI || X86 || ARM || GENERIC_NVRAM
698 If you say Y here and create a character special file /dev/nvram
699 with major number 10 and minor number 144 using mknod ("man mknod"),
700 you get read and write access to the extra bytes of non-volatile
701 memory in the real time clock (RTC), which is contained in every PC
702 and most Ataris. The actual number of bytes varies, depending on the
703 nvram in the system, but is usually 114 (128-14 for the RTC).
705 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
706 on Ataris. /dev/nvram may be used to view settings there, or to
707 change them (with some utility). It could also be used to frequently
708 save a few bits of very important data that may not be lost over
709 power-off and for which writing to disk is too insecure. Note
710 however that most NVRAM space in a PC belongs to the BIOS and you
711 should NEVER idly tamper with it. See Ralf Brown's interrupt list
712 for a guide to the use of CMOS bytes by your BIOS.
714 On Atari machines, /dev/nvram is always configured and does not need
717 To compile this driver as a module, choose M here: the
718 module will be called nvram.
721 tristate "Enhanced Real Time Clock Support"
722 depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV && !ARM
724 If you say Y here and create a character special file /dev/rtc with
725 major number 10 and minor number 135 using mknod ("man mknod"), you
726 will get access to the real time clock (or hardware clock) built
729 Every PC has such a clock built in. It can be used to generate
730 signals from as low as 1Hz up to 8192Hz, and can also be used
731 as a 24 hour alarm. It reports status information via the file
732 /proc/driver/rtc and its behaviour is set by various ioctls on
735 If you run Linux on a multiprocessor machine and said Y to
736 "Symmetric Multi Processing" above, you should say Y here to read
737 and set the RTC in an SMP compatible fashion.
739 If you think you have a use for such a device (such as periodic data
740 sampling), then say Y here, and read <file:Documentation/rtc.txt>
743 To compile this driver as a module, choose M here: the
744 module will be called rtc.
747 tristate "SGI DS1286 RTC support"
750 If you say Y here and create a character special file /dev/rtc with
751 major number 10 and minor number 135 using mknod ("man mknod"), you
752 will get access to the real time clock built into your computer.
753 Every SGI has such a clock built in. It reports status information
754 via the file /proc/rtc and its behaviour is set by various ioctls on
758 bool "SGI M48T35 RTC support"
761 If you say Y here and create a character special file /dev/rtc with
762 major number 10 and minor number 135 using mknod ("man mknod"), you
763 will get access to the real time clock built into your computer.
764 Every SGI has such a clock built in. It reports status information
765 via the file /proc/rtc and its behaviour is set by various ioctls on
769 tristate "Generic /dev/rtc emulation"
770 depends on RTC!=y && !IA64 && !ARM && !M32R && !SPARC && !FRV
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 It reports status information via the file /proc/driver/rtc and its
778 behaviour is set by various ioctls on /dev/rtc. If you enable the
779 "extended RTC operation" below it will also provide an emulation
780 for RTC_UIE which is required by some programs and may improve
781 precision in some cases.
783 To compile this driver as a module, choose M here: the
784 module will be called genrtc.
787 bool "Extended RTC operation"
790 Provides an emulation for RTC_UIE which is required by some programs
791 and may improve precision of the generic RTC support in some cases.
794 bool "EFI Real Time Clock Services"
798 tristate "DS1302 RTC support"
799 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
801 If you say Y here and create a character special file /dev/rtc with
802 major number 121 and minor number 0 using mknod ("man mknod"), you
803 will get access to the real time clock (or hardware clock) built
807 bool "S3C2410 RTC Driver"
808 depends on ARCH_S3C2410
810 RTC (Realtime Clock) driver for the clock inbuilt into the
811 Samsung S3C2410. This can provide periodic interrupt rates
812 from 1Hz to 64Hz for user programs, and wakeup from Alarm.
815 bool "Support for Cobalt LCD"
816 depends on MIPS_COBALT
818 This option enables support for the LCD display and buttons found
819 on Cobalt systems through a misc device.
822 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 base board support"
873 depends TANBAC_TB022X
876 menu "Ftape, the floppy tape device driver"
879 tristate "Ftape (QIC-80/Travan) support"
880 depends on BROKEN_ON_SMP && (ALPHA || X86)
882 If you have a tape drive that is connected to your floppy
883 controller, say Y here.
885 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
886 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
887 controller of their own. These drives (and their companion
888 controllers) are also supported if you say Y here.
890 If you have a special controller (such as the CMS FC-10, FC-20,
891 Mountain Mach-II, or any controller that is based on the Intel 82078
892 FDC like the high speed controllers by Seagate and Exabyte and
893 Iomega's "Ditto Dash") you must configure it by selecting the
894 appropriate entries from the "Floppy tape controllers" sub-menu
895 below and possibly modify the default values for the IRQ and DMA
896 channel and the IO base in ftape's configuration menu.
898 If you want to use your floppy tape drive on a PCI-bus based system,
899 please read the file <file:drivers/char/ftape/README.PCI>.
901 The ftape kernel driver is also available as a runtime loadable
902 module. To compile this driver as a module, choose M here: the
903 module will be called ftape.
905 source "drivers/char/ftape/Kconfig"
909 source "drivers/char/agp/Kconfig"
911 source "drivers/char/drm/Kconfig"
913 source "drivers/char/pcmcia/Kconfig"
916 tristate "ACP Modem (Mwave) support"
920 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
921 kernel driver and a user level application. Together these components
922 support direct attachment to public switched telephone networks (PSTNs)
923 and support selected world wide countries.
925 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
926 600, and 770 that include on board ACP modem hardware.
928 The modem also supports the standard communications port interface
929 (ttySx) and is compatible with the Hayes AT Command Set.
931 The user level application needed to use this driver can be found at
932 the IBM Linux Technology Center (LTC) web site:
933 <http://www.ibm.com/linux/ltc/>.
935 If you own one of the above IBM Thinkpads which has the Mwave chipset
938 To compile this driver as a module, choose M here: the
939 module will be called mwave.
942 tristate "NatSemi SCx200 GPIO Support"
946 Give userspace access to the GPIO pins on the National
947 Semiconductor SCx200 processors.
949 If compiled as a module, it will be called scx200_gpio.
952 tristate "NatSemi PC8736x GPIO Support"
954 default SCx200_GPIO # mostly N
955 select NSC_GPIO # needed for support routines
957 Give userspace access to the GPIO pins on the National
958 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
959 has multiple functional units, inc several managed by
960 hwmon/pc87360 driver. Tested with PC-87366
962 If compiled as a module, it will be called pc8736x_gpio.
965 tristate "NatSemi Base GPIO Support"
967 # selected by SCx200_GPIO and PC8736x_GPIO
968 # what about 2 selectors differing: m != y
970 Common support used (and needed) by scx200_gpio and
971 pc8736x_gpio drivers. If those drivers are built as
972 modules, this one will be too, named nsc_gpio
975 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
978 Give userspace access to the GPIO pins on the AMD CS5535 and
979 CS5536 Geode companion devices.
981 If compiled as a module, it will be called cs5535_gpio.
984 tristate "NEC VR4100 series General-purpose I/O Unit support"
985 depends on CPU_VR41XX
988 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
990 The raw driver permits block devices to be bound to /dev/raw/rawN.
991 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
992 See the raw(8) manpage for more details.
994 The raw driver is deprecated and will be removed soon.
995 Applications should simply open the device (eg /dev/hda1)
996 with the O_DIRECT flag.
999 int "Maximum number of RAW devices to support (1-8192)"
1000 depends on RAW_DRIVER
1003 The maximum number of RAW devices that are supported.
1004 Default is 256. Increase this number in case you need lots of
1008 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1012 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1013 open selects one of the timers supported by the HPET. The timers are
1014 non-periodioc and/or periodic.
1017 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1021 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1022 is assumed the platform called hpet_alloc with the RTC IRQ values for
1026 bool "Allow mmap of HPET"
1030 If you say Y here, user applications will be able to mmap
1033 In some hardware implementations, the page containing HPET
1034 registers may also contain other things that shouldn't be
1035 exposed to the user. If this applies to your hardware,
1038 config HANGCHECK_TIMER
1039 tristate "Hangcheck timer"
1040 depends on X86 || IA64 || PPC64
1042 The hangcheck-timer module detects when the system has gone
1043 out to lunch past a certain margin. It can reboot the system
1044 or merely print a warning.
1047 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1048 depends on IA64_GENERIC || IA64_SGI_SN2
1051 The mmtimer device allows direct userspace access to the
1054 source "drivers/char/tpm/Kconfig"
1057 tristate "Telecom clock driver for MPBL0010 ATCA SBC"
1058 depends on EXPERIMENTAL
1061 The telecom clock device is specific to the MPBL0010 ATCA computer and
1062 allows direct userspace access to the configuration of the telecom clock
1063 configuration settings. This device is used for hardware synchronization
1064 across the ATCA backplane fabric. Upon loading, the driver exports a
1065 sysfs directory, /sys/devices/platform/telco_clock, with a number of
1066 files for controlling the behavior of this hardware.