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>.
83 tristate "Moxa CPU MOXA ODM keypad support"
84 depends on ARCH_MOXART
86 Say Y here if you have any keypad support for Moxa CPU.
87 We are implement for MOXA ODM project.
90 tristate "Moxa CPU MOXA ODM LCM module WG12864C support"
91 depends on ARCH_MOXART
93 Say Y here if you have any LCM module WG12864C support for Moxa CPU.
94 We are implement for MOXA ODM project.
97 tristate "Moxa CPU MOXA ODM LCM module WG240128B support"
98 depends on ARCH_MOXART
100 Say Y here if you have any LCM module WG240128B support for Moxa CPU.
101 We are implement for MOXA ODM project.
104 tristate "Moxa CPU MOXA ODM LCM module WG12232C support"
105 depends on ARCH_MOXART
107 Say Y here if you have any LCM module WG12232C support for Moxa CPU.
108 We are implement for MOXA ODM project.
111 tristate "Moxa CPU MOXA ODM LCM module WG16080B support"
112 depends on ARCH_MOXART
114 Say Y here if you have any LCM module WG16080B support for Moxa CPU.
115 We are implement for MOXA ODM project.
118 tristate "Moxa CPU UC71XX GPIO support"
119 depends on ARCH_MOXART
121 Say Y here if you have any GPIO support for Moxa CPU.
122 We are implement for UC71XX project.
124 config SERIAL_NONSTANDARD
125 bool "Non-standard serial port support"
127 Say Y here if you have any non-standard serial boards -- boards
128 which aren't supported using the standard "dumb" serial driver.
129 This includes intelligent serial boards such as Cyclades,
130 Digiboards, etc. These are usually used for systems that need many
131 serial ports because they serve many terminals or dial-in
134 Note that the answer to this question won't directly affect the
135 kernel: saying N will just cause the configurator to skip all
136 the questions about non-standard serial boards.
138 Most people can say N here.
140 config NIOS_LCD_16207
141 bool "Nios LCD 16207 device support"
142 depends on NIOS || NIOS2
144 This driver supports the Nios LCD 16207 device.
147 bool "Nios PIO buttons support"
148 depends on ALTERA_STRATIX || ALTERA_STRATIX_PRO || ALTERA_CYCLONE || ALTERA_STRATIX_II
150 This driver takes the 4 user buttons on Altera's Nios Development Kit
151 as a source of input: users can input '1','2','4' or '8' by pressing
152 one of the 4 buttons. The device node is a character device with a
153 major of 62 and minor of 0. Users can view input using the following
156 where /dev/btn is the device node file.
159 tristate "Computone IntelliPort Plus serial support"
160 depends on SERIAL_NONSTANDARD
162 This driver supports the entire family of Intelliport II/Plus
163 controllers with the exception of the MicroChannel controllers and
164 products previous to the Intelliport II. These are multiport cards,
165 which give you many serial ports. You would need something like this
166 to connect more than two modems to your Linux box, for instance in
167 order to become a dial-in server. If you have a card like that, say
168 Y here and read <file:Documentation/computone.txt>.
170 To compile this driver as modules, choose M here: the
171 modules will be called ip2 and ip2main.
174 tristate "Comtrol RocketPort support"
175 depends on SERIAL_NONSTANDARD
177 This driver supports Comtrol RocketPort and RocketModem PCI boards.
178 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
179 modems. For information about the RocketPort/RocketModem boards
180 and this driver read <file:Documentation/rocket.txt>.
182 To compile this driver as a module, choose M here: the
183 module will be called rocket.
185 If you want to compile this driver into the kernel, say Y here. If
186 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
189 tristate "Cyclades async mux support"
190 depends on SERIAL_NONSTANDARD
192 This driver supports Cyclades Z and Y multiserial boards.
193 You would need something like this to connect more than two modems to
194 your Linux box, for instance in order to become a dial-in server.
196 For information about the Cyclades-Z card, read
197 <file:drivers/char/README.cycladesZ>.
199 To compile this driver as a module, choose M here: the
200 module will be called cyclades.
202 If you haven't heard about it, it's safe to say N.
205 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
206 depends on EXPERIMENTAL && CYCLADES
208 The Cyclades-Z family of multiport cards allows 2 (two) driver op
209 modes: polling and interrupt. In polling mode, the driver will check
210 the status of the Cyclades-Z ports every certain amount of time
211 (which is called polling cycle and is configurable). In interrupt
212 mode, it will use an interrupt line (IRQ) in order to check the
213 status of the Cyclades-Z ports. The default op mode is polling. If
217 tristate "Digiboard Intelligent Async Support"
218 depends on SERIAL_NONSTANDARD
220 This is a driver for Digi International's Xx, Xeve, and Xem series
221 of cards which provide multiple serial ports. You would need
222 something like this to connect more than two modems to your Linux
223 box, for instance in order to become a dial-in server. This driver
224 supports the original PC (ISA) boards as well as PCI, and EISA. If
225 you have a card like this, say Y here and read the file
226 <file:Documentation/digiepca.txt>.
228 To compile this driver as a module, choose M here: the
229 module will be called epca.
232 tristate "Hayes ESP serial port support"
233 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
235 This is a driver which supports Hayes ESP serial ports. Both single
236 port cards and multiport cards are supported. Make sure to read
237 <file:Documentation/hayes-esp.txt>.
239 To compile this driver as a module, choose M here: the
240 module will be called esp.
245 tristate "Moxa Intellio support"
246 depends on SERIAL_NONSTANDARD
248 Say Y here if you have a Moxa Intellio multiport serial card.
250 To compile this driver as a module, choose M here: the
251 module will be called moxa.
254 tristate "Moxa SmartIO support"
255 depends on SERIAL_NONSTANDARD
257 Say Y here if you have a Moxa SmartIO multiport serial card.
259 This driver can also be built as a module ( = code which can be
260 inserted in and removed from the running kernel whenever you want).
261 The module will be called mxser. If you want to do that, say M
265 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
266 depends on SERIAL_NONSTANDARD
269 This is a driver for the Multi-Tech cards which provide several
270 serial ports. The driver is experimental and can currently only be
271 built as a module. The module will be called isicom.
272 If you want to do that, choose M here.
275 tristate "Microgate SyncLink card support"
276 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
278 Provides support for the SyncLink ISA and PCI multiprotocol serial
279 adapters. These adapters support asynchronous and HDLC bit
280 synchronous communication up to 10Mbps (PCI adapter).
282 This driver can only be built as a module ( = code which can be
283 inserted in and removed from the running kernel whenever you want).
284 The module will be called synclink. If you want to do that, say M
288 tristate "SyncLink Multiport support"
289 depends on SERIAL_NONSTANDARD
291 Enable support for the SyncLink Multiport (2 or 4 ports)
292 serial adapter, running asynchronous and HDLC communications up
293 to 2.048Mbps. Each ports is independently selectable for
294 RS-232, V.35, RS-449, RS-530, and X.21
296 This driver may be built as a module ( = code which can be
297 inserted in and removed from the running kernel whenever you want).
298 The module will be called synclinkmp. If you want to do that, say M
302 tristate "SyncLink GT/AC support"
303 depends on SERIAL_NONSTANDARD && PCI
305 Support for SyncLink GT and SyncLink AC families of
306 synchronous and asynchronous serial adapters
307 manufactured by Microgate Systems, Ltd. (www.microgate.com)
310 tristate "HDLC line discipline support"
311 depends on SERIAL_NONSTANDARD
313 Allows synchronous HDLC communications with tty device drivers that
314 support synchronous HDLC such as the Microgate SyncLink adapter.
316 This driver can only be built as a module ( = code which can be
317 inserted in and removed from the running kernel whenever you want).
318 The module will be called n_hdlc. If you want to do that, say M
322 tristate "SDL RISCom/8 card support"
323 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
325 This is a driver for the SDL Communications RISCom/8 multiport card,
326 which gives you many serial ports. You would need something like
327 this to connect more than two modems to your Linux box, for instance
328 in order to become a dial-in server. If you have a card like that,
329 say Y here and read the file <file:Documentation/riscom8.txt>.
331 Also it's possible to say M here and compile this driver as kernel
332 loadable module; the module will be called riscom8.
335 tristate "Specialix IO8+ card support"
336 depends on SERIAL_NONSTANDARD
338 This is a driver for the Specialix IO8+ multiport card (both the
339 ISA and the PCI version) which gives you many serial ports. You
340 would need something like this to connect more than two modems to
341 your Linux box, for instance in order to become a dial-in server.
343 If you have a card like that, say Y here and read the file
344 <file:Documentation/specialix.txt>. Also it's possible to say M here
345 and compile this driver as kernel loadable module which will be
348 config SPECIALIX_RTSCTS
349 bool "Specialix DTR/RTS pin is RTS"
352 The Specialix IO8+ card can only support either RTS or DTR. If you
353 say N here, the driver will use the pin as "DTR" when the tty is in
354 software handshake mode. If you say Y here or hardware handshake is
355 on, it will always be RTS. Read the file
356 <file:Documentation/specialix.txt> for more information.
359 tristate "Specialix SX (and SI) card support"
360 depends on SERIAL_NONSTANDARD
362 This is a driver for the SX and SI multiport serial cards.
363 Please read the file <file:Documentation/sx.txt> for details.
365 This driver can only be built as a module ( = code which can be
366 inserted in and removed from the running kernel whenever you want).
367 The module will be called sx. If you want to do that, say M here.
370 tristate "Specialix RIO system support"
371 depends on SERIAL_NONSTANDARD
373 This is a driver for the Specialix RIO, a smart serial card which
374 drives an outboard box that can support up to 128 ports. Product
375 information is at <http://www.perle.com/support/documentation.html#multiport>.
376 There are both ISA and PCI versions.
379 bool "Support really old RIO/PCI cards"
382 Older RIO PCI cards need some initialization-time configuration to
383 determine the IRQ and some control addresses. If you have a RIO and
384 this doesn't seem to work, try setting this to Y.
387 bool "Stallion multiport serial support"
388 depends on SERIAL_NONSTANDARD
390 Stallion cards give you many serial ports. You would need something
391 like this to connect more than two modems to your Linux box, for
392 instance in order to become a dial-in server. If you say Y here,
393 you will be asked for your specific card model in the next
394 questions. Make sure to read <file:Documentation/stallion.txt> in
395 this case. If you have never heard about all this, it's safe to
399 tristate "Stallion EasyIO or EC8/32 support"
400 depends on STALDRV && BROKEN_ON_SMP
402 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
403 card, then this is for you; say Y. Make sure to read
404 <file:Documentation/stallion.txt>.
406 To compile this driver as a module, choose M here: the
407 module will be called stallion.
410 tristate "Stallion EC8/64, ONboard, Brumby support"
411 depends on STALDRV && BROKEN_ON_SMP
413 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
414 serial multiport card, say Y here. Make sure to read
415 <file:Documentation/stallion.txt>.
417 To compile this driver as a module, choose M here: the
418 module will be called istallion.
421 bool "Enable Au1000 UART Support"
422 depends on SERIAL_NONSTANDARD && MIPS
424 If you have an Alchemy AU1000 processor (MIPS based) and you want
425 to use serial ports, say Y. Otherwise, say N.
427 config AU1000_SERIAL_CONSOLE
428 bool "Enable Au1000 serial console"
429 depends on AU1000_UART
431 If you have an Alchemy AU1000 processor (MIPS based) and you want
432 to use a console on a serial port, say Y. Otherwise, say N.
435 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
436 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
438 This option supports the 2232 7-port serial card shipped with the
439 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
440 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
441 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
442 ports were connected with 8 pin DIN connectors on the card bracket,
443 for which 8 pin to DB25 adapters were supplied. The card also had
444 jumpers internally to toggle various pinning configurations.
446 This driver can be built as a module; but then "generic_serial"
447 will also be built as a module. This has to be loaded before
448 "ser_a2232". If you want to do this, answer M here.
451 bool "LED Manager support"
453 Enbale the LED manager driver.
456 bool "SnapGear Watchdog Support"
458 Support the SnapGear common watchdog driver.
463 Support the SnapGear common watchdog driver.
466 bool "Reset switch support"
468 Support the hardware reset switch.
471 bool "SGI Altix system controller communication support"
472 depends on (IA64_SGI_SN2 || IA64_GENERIC)
474 If you have an SGI Altix and you want to enable system
475 controller communication from user space (you want this!),
476 say Y. Otherwise, say N.
479 bool "SGI TIO CX driver support"
480 depends on (IA64_SGI_SN2 || IA64_GENERIC)
482 If you have an SGI Altix and you have fpga devices attached
483 to your TIO, say Y here, otherwise say N.
486 tristate "SGI FPGA Core Services driver support"
489 If you have an SGI Altix with an attached SABrick
490 say Y or M here, otherwise say N.
492 source "drivers/serial/Kconfig"
495 bool "Unix98 PTY support" if EMBEDDED
498 A pseudo terminal (PTY) is a software device consisting of two
499 halves: a master and a slave. The slave device behaves identical to
500 a physical terminal; the master device is used by a process to
501 read data from and write data to the slave, thereby emulating a
502 terminal. Typical programs for the master side are telnet servers
505 Linux has traditionally used the BSD-like names /dev/ptyxx for
506 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
507 has a number of problems. The GNU C library glibc 2.1 and later,
508 however, supports the Unix98 naming standard: in order to acquire a
509 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
510 terminal is then made available to the process and the pseudo
511 terminal slave can be accessed as /dev/pts/<number>. What was
512 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
514 All modern Linux systems use the Unix98 ptys. Say Y unless
515 you're on an embedded system and want to conserve memory.
518 bool "Legacy (BSD) PTY support"
521 A pseudo terminal (PTY) is a software device consisting of two
522 halves: a master and a slave. The slave device behaves identical to
523 a physical terminal; the master device is used by a process to
524 read data from and write data to the slave, thereby emulating a
525 terminal. Typical programs for the master side are telnet servers
528 Linux has traditionally used the BSD-like names /dev/ptyxx
529 for masters and /dev/ttyxx for slaves of pseudo
530 terminals. This scheme has a number of problems, including
531 security. This option enables these legacy devices; on most
532 systems, it is safe to say N.
535 config LEGACY_PTY_COUNT
536 int "Maximum number of legacy PTY in use"
537 depends on LEGACY_PTYS
541 The maximum number of legacy PTYs that can be used at any one time.
542 The default is 256, and should be more than enough. Embedded
543 systems may want to reduce this to save memory.
545 When not in use, each legacy PTY occupies 12 bytes on 32-bit
546 architectures and 24 bytes on 64-bit architectures.
549 tristate 'Total Impact briQ front panel driver'
552 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
553 tristate led and two switches. It is the size of a CDROM drive.
555 If you have such one and want anything showing on the VFD then you
558 To compile this driver as a module, choose M here: the
559 module will be called briq_panel.
561 It's safe to say N here.
564 tristate "Parallel printer support"
567 If you intend to attach a printer to the parallel port of your Linux
568 box (as opposed to using a serial printer; if the connector at the
569 printer has 9 or 25 holes ["female"], then it's serial), say Y.
570 Also read the Printing-HOWTO, available from
571 <http://www.tldp.org/docs.html#howto>.
573 It is possible to share one parallel port among several devices
574 (e.g. printer and ZIP drive) and it is safe to compile the
575 corresponding drivers into the kernel.
577 To compile this driver as a module, choose M here and read
578 <file:Documentation/parport.txt>. The module will be called lp.
580 If you have several parallel ports, you can specify which ports to
581 use with the "lp" kernel command line option. (Try "man bootparam"
582 or see the documentation of your boot loader (lilo or loadlin) about
583 how to pass options to the kernel at boot time.) The syntax of the
584 "lp" command line option can be found in <file:drivers/char/lp.c>.
586 If you have more than 8 printers, you need to increase the LP_NO
587 macro in lp.c and the PARPORT_MAX macro in parport.h.
590 bool "Support for console on line printer"
593 If you want kernel messages to be printed out as they occur, you
594 can have a console on the printer. This option adds support for
595 doing that; to actually get it to happen you need to pass the
596 option "console=lp0" to the kernel at boot time.
598 If the printer is out of paper (or off, or unplugged, or too
599 busy..) the kernel will stall until the printer is ready again.
600 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
601 can make the kernel continue when this happens,
602 but it'll lose the kernel messages.
607 tristate "Support for user-space parallel port device drivers"
610 Saying Y to this adds support for /dev/parport device nodes. This
611 is needed for programs that want portable access to the parallel
612 port, for instance deviceid (which displays Plug-and-Play device
615 This is the parallel port equivalent of SCSI generic support (sg).
616 It is safe to say N to this -- it is not needed for normal printing
617 or parallel port CD-ROM/disk support.
619 To compile this driver as a module, choose M here: the
620 module will be called ppdev.
625 tristate "Texas Instruments parallel link cable support"
628 If you own a Texas Instruments graphing calculator and use a
629 parallel link cable, then you might be interested in this driver.
631 If you enable this driver, you will be able to communicate with
632 your calculator through a set of device nodes under /dev. The
633 main advantage of this driver is that you don't have to be root
634 to use this precise link cable (depending on the permissions on
635 the device nodes, though).
637 To compile this driver as a module, choose M here: the
638 module will be called tipar.
640 If you don't know what a parallel link cable is or what a Texas
641 Instruments graphing calculator is, then you probably don't need this
649 Users of pSeries machines that want to utilize the hvc console front-end
650 module for their backend console driver should select this option.
651 It will automatically be selected if one of the back-end console drivers
656 bool "pSeries Hypervisor Virtual Console support"
657 depends on PPC_PSERIES
660 pSeries machines when partitioned support a hypervisor virtual
661 console. This driver allows each pSeries partition to have a console
662 which is accessed via the HMC.
665 bool "iSeries Hypervisor Virtual Console support"
666 depends on PPC_ISERIES && !VIOCONS
669 iSeries machines support a hypervisor virtual console.
672 bool "IBM RTAS Console support"
676 IBM Console device driver which makes use of RTAS
679 tristate "IBM Hypervisor Virtual Console Server support"
680 depends on PPC_PSERIES
682 Partitionable IBM Power5 ppc64 machines allow hosting of
683 firmware virtual consoles from one Linux partition by
684 another Linux partition. This driver allows console data
685 from Linux partitions to be accessed through TTY device
686 interfaces in the device tree of a Linux partition running
689 To compile this driver as a module, choose M here: the
690 module will be called hvcs.ko. Additionally, this module
691 will depend on arch specific APIs exported from hvcserver.ko
692 which will also be compiled when this driver is built as a
695 source "drivers/char/ipmi/Kconfig"
697 source "drivers/char/watchdog/Kconfig"
700 tristate "Coldfire Watchdog"
704 Watchdog for Coldfire processors. /dev/watchdog is not used
705 for this driver. A timer-interrupt is updating the watchdog instead.
708 tristate "NetWinder thermometer support"
709 depends on ARCH_NETWINDER
711 Say Y here to include support for the thermal management hardware
712 found in the NetWinder. This driver allows the user to control the
713 temperature set points and to read the current temperature.
715 It is also possible to say M here to build it as a module (ds1620)
716 It is recommended to be used on a NetWinder, but it is not a
720 tristate "NetWinder Button"
721 depends on ARCH_NETWINDER
723 If you say Y here and create a character device node /dev/nwbutton
724 with major and minor numbers 10 and 158 ("man mknod"), then every
725 time the orange button is pressed a number of times, the number of
726 times the button was pressed will be written to that device.
728 This is most useful for applications, as yet unwritten, which
729 perform actions based on how many times the button is pressed in a
732 Do not hold the button down for too long, as the driver does not
733 alter the behaviour of the hardware reset circuitry attached to the
734 button; it will still execute a hard reset if the button is held
735 down for longer than approximately five seconds.
737 To compile this driver as a module, choose M here: the
738 module will be called nwbutton.
740 Most people will answer Y to this question and "Reboot Using Button"
741 below to be able to initiate a system shutdown from the button.
743 config NWBUTTON_REBOOT
744 bool "Reboot Using Button"
747 If you say Y here, then you will be able to initiate a system
748 shutdown and reboot by pressing the orange button a number of times.
749 The number of presses to initiate the shutdown is two by default,
750 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
751 in nwbutton.h and recompiling the driver or, if you compile the
752 driver as a module, you can specify the number of presses at load
753 time with "insmod button reboot_count=<something>".
756 tristate "NetWinder flash support"
757 depends on ARCH_NETWINDER
759 If you say Y here and create a character device /dev/flash with
760 major 10 and minor 160 you can manipulate the flash ROM containing
761 the NetWinder firmware. Be careful as accidentally overwriting the
762 flash contents can render your computer unbootable. On no account
763 allow random users access to this device. :-)
765 To compile this driver as a module, choose M here: the
766 module will be called nwflash.
768 If you're not sure, say N.
770 source "drivers/char/hw_random/Kconfig"
773 tristate "/dev/nvram support"
774 depends on ATARI || X86 || ARM || GENERIC_NVRAM
776 If you say Y here and create a character special file /dev/nvram
777 with major number 10 and minor number 144 using mknod ("man mknod"),
778 you get read and write access to the extra bytes of non-volatile
779 memory in the real time clock (RTC), which is contained in every PC
780 and most Ataris. The actual number of bytes varies, depending on the
781 nvram in the system, but is usually 114 (128-14 for the RTC).
783 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
784 on Ataris. /dev/nvram may be used to view settings there, or to
785 change them (with some utility). It could also be used to frequently
786 save a few bits of very important data that may not be lost over
787 power-off and for which writing to disk is too insecure. Note
788 however that most NVRAM space in a PC belongs to the BIOS and you
789 should NEVER idly tamper with it. See Ralf Brown's interrupt list
790 for a guide to the use of CMOS bytes by your BIOS.
792 On Atari machines, /dev/nvram is always configured and does not need
795 To compile this driver as a module, choose M here: the
796 module will be called nvram.
799 tristate "Enhanced Real Time Clock Support"
800 depends on !PPC && !PARISC && !IA64 && !M68K
802 If you say Y here and create a character special file /dev/rtc with
803 major number 10 and minor number 135 using mknod ("man mknod"), you
804 will get access to the real time clock (or hardware clock) built
807 Every PC has such a clock built in. It can be used to generate
808 signals from as low as 1Hz up to 8192Hz, and can also be used
809 as a 24 hour alarm. It reports status information via the file
810 /proc/driver/rtc and its behaviour is set by various ioctls on
813 If you run Linux on a multiprocessor machine and said Y to
814 "Symmetric Multi Processing" above, you should say Y here to read
815 and set the RTC in an SMP compatible fashion.
817 If you think you have a use for such a device (such as periodic data
818 sampling), then say Y here, and read <file:Documentation/rtc.txt>
821 To compile this driver as a module, choose M here: the
822 module will be called rtc.
825 tristate "SGI DS1286 RTC support"
828 If you say Y here and create a character special file /dev/rtc with
829 major number 10 and minor number 135 using mknod ("man mknod"), you
830 will get access to the real time clock built into your computer.
831 Every SGI has such a clock built in. It reports status information
832 via the file /proc/rtc and its behaviour is set by various ioctls on
836 bool "SGI M48T35 RTC support"
839 If you say Y here and create a character special file /dev/rtc with
840 major number 10 and minor number 135 using mknod ("man mknod"), you
841 will get access to the real time clock built into your computer.
842 Every SGI has such a clock built in. It reports status information
843 via the file /proc/rtc and its behaviour is set by various ioctls on
847 tristate "Generic /dev/rtc emulation"
848 depends on RTC!=y && !IA64 && !ARM && !M32R && !SPARC && !FRV
850 If you say Y here and create a character special file /dev/rtc with
851 major number 10 and minor number 135 using mknod ("man mknod"), you
852 will get access to the real time clock (or hardware clock) built
855 It reports status information via the file /proc/driver/rtc and its
856 behaviour is set by various ioctls on /dev/rtc. If you enable the
857 "extended RTC operation" below it will also provide an emulation
858 for RTC_UIE which is required by some programs and may improve
859 precision in some cases.
861 To compile this driver as a module, choose M here: the
862 module will be called genrtc.
865 bool "Extended RTC operation"
868 Provides an emulation for RTC_UIE which is required by some programs
869 and may improve precision of the generic RTC support in some cases.
872 bool "EFI Real Time Clock Services"
876 tristate "DS1302 RTC support"
877 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
879 If you say Y here and create a character special file /dev/rtc with
880 major number 121 and minor number 0 using mknod ("man mknod"), you
881 will get access to the real time clock (or hardware clock) built
885 bool "Support for Cobalt LCD"
886 depends on MIPS_COBALT
888 This option enables support for the LCD display and buttons found
889 on Cobalt systems through a misc device.
892 tristate "Double Talk PC internal speech card support"
894 This driver is for the DoubleTalk PC, a speech synthesizer
895 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
896 called the `internal DoubleTalk'.
898 To compile this driver as a module, choose M here: the
899 module will be called dtlk.
902 tristate "Siemens R3964 line discipline"
904 This driver allows synchronous communication with devices using the
905 Siemens R3964 packet protocol. Unless you are dealing with special
906 hardware like PLCs, you are unlikely to need this.
908 To compile this driver as a module, choose M here: the
909 module will be called n_r3964.
914 tristate "Applicom intelligent fieldbus card support"
917 This driver provides the kernel-side support for the intelligent
918 fieldbus cards made by Applicom International. More information
919 about these cards can be found on the WWW at the address
920 <http://www.applicom-int.com/>, or by email from David Woodhouse
921 <dwmw2@infradead.org>.
923 To compile this driver as a module, choose M here: the
924 module will be called applicom.
929 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
930 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
932 This driver enables access to the Sony Programmable I/O Control
933 Device which can be found in many (all ?) Sony Vaio laptops.
935 If you have one of those laptops, read
936 <file:Documentation/sonypi.txt>, and say Y or M here.
938 To compile this driver as a module, choose M here: the
939 module will be called sonypi.
942 tristate "TANBAC TB0219 base board support"
943 depends TANBAC_TB022X
946 menu "Ftape, the floppy tape device driver"
949 tristate "Ftape (QIC-80/Travan) support"
950 depends on BROKEN_ON_SMP && (ALPHA || X86)
952 If you have a tape drive that is connected to your floppy
953 controller, say Y here.
955 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
956 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
957 controller of their own. These drives (and their companion
958 controllers) are also supported if you say Y here.
960 If you have a special controller (such as the CMS FC-10, FC-20,
961 Mountain Mach-II, or any controller that is based on the Intel 82078
962 FDC like the high speed controllers by Seagate and Exabyte and
963 Iomega's "Ditto Dash") you must configure it by selecting the
964 appropriate entries from the "Floppy tape controllers" sub-menu
965 below and possibly modify the default values for the IRQ and DMA
966 channel and the IO base in ftape's configuration menu.
968 If you want to use your floppy tape drive on a PCI-bus based system,
969 please read the file <file:drivers/char/ftape/README.PCI>.
971 The ftape kernel driver is also available as a runtime loadable
972 module. To compile this driver as a module, choose M here: the
973 module will be called ftape.
975 source "drivers/char/ftape/Kconfig"
979 source "drivers/char/agp/Kconfig"
981 source "drivers/char/drm/Kconfig"
983 source "drivers/char/pcmcia/Kconfig"
986 tristate "ACP Modem (Mwave) support"
990 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
991 kernel driver and a user level application. Together these components
992 support direct attachment to public switched telephone networks (PSTNs)
993 and support selected world wide countries.
995 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
996 600, and 770 that include on board ACP modem hardware.
998 The modem also supports the standard communications port interface
999 (ttySx) and is compatible with the Hayes AT Command Set.
1001 The user level application needed to use this driver can be found at
1002 the IBM Linux Technology Center (LTC) web site:
1003 <http://www.ibm.com/linux/ltc/>.
1005 If you own one of the above IBM Thinkpads which has the Mwave chipset
1008 To compile this driver as a module, choose M here: the
1009 module will be called mwave.
1012 tristate "NatSemi SCx200 GPIO Support"
1016 Give userspace access to the GPIO pins on the National
1017 Semiconductor SCx200 processors.
1019 If compiled as a module, it will be called scx200_gpio.
1022 tristate "NatSemi PC8736x GPIO Support"
1024 default SCx200_GPIO # mostly N
1025 select NSC_GPIO # needed for support routines
1027 Give userspace access to the GPIO pins on the National
1028 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
1029 has multiple functional units, inc several managed by
1030 hwmon/pc87360 driver. Tested with PC-87366
1032 If compiled as a module, it will be called pc8736x_gpio.
1035 tristate "NatSemi Base GPIO Support"
1037 # selected by SCx200_GPIO and PC8736x_GPIO
1038 # what about 2 selectors differing: m != y
1040 Common support used (and needed) by scx200_gpio and
1041 pc8736x_gpio drivers. If those drivers are built as
1042 modules, this one will be too, named nsc_gpio
1045 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
1048 Give userspace access to the GPIO pins on the AMD CS5535 and
1049 CS5536 Geode companion devices.
1051 If compiled as a module, it will be called cs5535_gpio.
1054 tristate "NEC VR4100 series General-purpose I/O Unit support"
1055 depends on CPU_VR41XX
1058 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
1061 The raw driver permits block devices to be bound to /dev/raw/rawN.
1062 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
1063 See the raw(8) manpage for more details.
1065 The raw driver is deprecated and will be removed soon.
1066 Applications should simply open the device (eg /dev/hda1)
1067 with the O_DIRECT flag.
1070 int "Maximum number of RAW devices to support (1-8192)"
1071 depends on RAW_DRIVER
1074 The maximum number of RAW devices that are supported.
1075 Default is 256. Increase this number in case you need lots of
1079 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1083 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1084 open selects one of the timers supported by the HPET. The timers are
1085 non-periodioc and/or periodic.
1088 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1092 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1093 is assumed the platform called hpet_alloc with the RTC IRQ values for
1097 bool "Allow mmap of HPET"
1101 If you say Y here, user applications will be able to mmap
1104 In some hardware implementations, the page containing HPET
1105 registers may also contain other things that shouldn't be
1106 exposed to the user. If this applies to your hardware,
1109 config HANGCHECK_TIMER
1110 tristate "Hangcheck timer"
1111 depends on X86 || IA64 || PPC64
1113 The hangcheck-timer module detects when the system has gone
1114 out to lunch past a certain margin. It can reboot the system
1115 or merely print a warning.
1118 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1119 depends on IA64_GENERIC || IA64_SGI_SN2
1122 The mmtimer device allows direct userspace access to the
1125 source "drivers/char/tpm/Kconfig"
1128 tristate "QSPI driver for Coldfire processors"
1131 Driver for Coldfire processors QSPI
1134 tristate "M41T11M6 Real Time Clock (RTC) support"
1136 Driver for the M41T11M6 Real Time Clock Chip.
1139 tristate "Telecom clock driver for MPBL0010 ATCA SBC"
1140 depends on EXPERIMENTAL && X86
1143 The telecom clock device is specific to the MPBL0010 ATCA computer and
1144 allows direct userspace access to the configuration of the telecom clock
1145 configuration settings. This device is used for hardware synchronization
1146 across the ATCA backplane fabric. Upon loading, the driver exports a
1147 sysfs directory, /sys/devices/platform/telco_clock, with a number of
1148 files for controlling the behavior of this hardware.