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 && (ISA || EISA || PCI)
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 (OBSOLETE)"
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
204 config MOXA_SMARTIO_NEW
205 tristate "Moxa SmartIO support v. 2.0"
206 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
208 Say Y here if you have a Moxa SmartIO multiport serial card and/or
209 want to help develop a new version of this driver.
211 This is upgraded (1.9.1) driver from original Moxa drivers with
212 changes finally resulting in PCI probing.
214 Use at your own risk.
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
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
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
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 bool "Enable Au1000 UART Support"
377 depends on SERIAL_NONSTANDARD && MIPS
379 If you have an Alchemy AU1000 processor (MIPS based) and you want
380 to use serial ports, say Y. Otherwise, say N.
382 config AU1000_SERIAL_CONSOLE
383 bool "Enable Au1000 serial console"
384 depends on AU1000_UART
386 If you have an Alchemy AU1000 processor (MIPS based) and you want
387 to use a console on a serial port, say Y. Otherwise, say N.
390 bool "DECstation serial support"
391 depends on MACH_DECSTATION
394 This selects whether you want to be asked about drivers for
395 DECstation serial ports.
397 Note that the answer to this question won't directly affect the
398 kernel: saying N will just cause the configurator to skip all
399 the questions about DECstation serial ports.
401 config SERIAL_DEC_CONSOLE
402 bool "Support for console on a DECstation serial port"
403 depends on SERIAL_DEC
406 If you say Y here, it will be possible to use a serial port as the
407 system console (the system console is the device which receives all
408 kernel messages and warnings and which allows logins in single user
409 mode). Note that the firmware uses ttyS0 as the serial console on
410 the Maxine and ttyS2 on the others.
415 bool "Z85C30 Serial Support"
416 depends on SERIAL_DEC
419 Documentation on the Zilog 85C350 serial communications controller
420 is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>
423 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
424 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
426 This option supports the 2232 7-port serial card shipped with the
427 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
428 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
429 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
430 ports were connected with 8 pin DIN connectors on the card bracket,
431 for which 8 pin to DB25 adapters were supplied. The card also had
432 jumpers internally to toggle various pinning configurations.
434 This driver can be built as a module; but then "generic_serial"
435 will also be built as a module. This has to be loaded before
436 "ser_a2232". If you want to do this, answer M here.
439 bool "SGI Altix system controller communication support"
440 depends on (IA64_SGI_SN2 || IA64_GENERIC)
442 If you have an SGI Altix and you want to enable system
443 controller communication from user space (you want this!),
444 say Y. Otherwise, say N.
447 bool "SGI TIO CX driver support"
448 depends on (IA64_SGI_SN2 || IA64_GENERIC)
450 If you have an SGI Altix and you have fpga devices attached
451 to your TIO, say Y here, otherwise say N.
454 tristate "SGI FPGA Core Services driver support"
457 If you have an SGI Altix with an attached SABrick
458 say Y or M here, otherwise say N.
460 source "drivers/serial/Kconfig"
463 bool "Unix98 PTY support" if EMBEDDED
466 A pseudo terminal (PTY) is a software device consisting of two
467 halves: a master and a slave. The slave device behaves identical to
468 a physical terminal; the master device is used by a process to
469 read data from and write data to the slave, thereby emulating a
470 terminal. Typical programs for the master side are telnet servers
473 Linux has traditionally used the BSD-like names /dev/ptyxx for
474 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
475 has a number of problems. The GNU C library glibc 2.1 and later,
476 however, supports the Unix98 naming standard: in order to acquire a
477 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
478 terminal is then made available to the process and the pseudo
479 terminal slave can be accessed as /dev/pts/<number>. What was
480 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
482 All modern Linux systems use the Unix98 ptys. Say Y unless
483 you're on an embedded system and want to conserve memory.
486 bool "Legacy (BSD) PTY support"
489 A pseudo terminal (PTY) is a software device consisting of two
490 halves: a master and a slave. The slave device behaves identical to
491 a physical terminal; the master device is used by a process to
492 read data from and write data to the slave, thereby emulating a
493 terminal. Typical programs for the master side are telnet servers
496 Linux has traditionally used the BSD-like names /dev/ptyxx
497 for masters and /dev/ttyxx for slaves of pseudo
498 terminals. This scheme has a number of problems, including
499 security. This option enables these legacy devices; on most
500 systems, it is safe to say N.
503 config LEGACY_PTY_COUNT
504 int "Maximum number of legacy PTY in use"
505 depends on LEGACY_PTYS
509 The maximum number of legacy PTYs that can be used at any one time.
510 The default is 256, and should be more than enough. Embedded
511 systems may want to reduce this to save memory.
513 When not in use, each legacy PTY occupies 12 bytes on 32-bit
514 architectures and 24 bytes on 64-bit architectures.
517 tristate 'Total Impact briQ front panel driver'
520 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
521 tristate led and two switches. It is the size of a CDROM drive.
523 If you have such one and want anything showing on the VFD then you
526 To compile this driver as a module, choose M here: the
527 module will be called briq_panel.
529 It's safe to say N here.
532 tristate "Parallel printer support"
535 If you intend to attach a printer to the parallel port of your Linux
536 box (as opposed to using a serial printer; if the connector at the
537 printer has 9 or 25 holes ["female"], then it's serial), say Y.
538 Also read the Printing-HOWTO, available from
539 <http://www.tldp.org/docs.html#howto>.
541 It is possible to share one parallel port among several devices
542 (e.g. printer and ZIP drive) and it is safe to compile the
543 corresponding drivers into the kernel.
545 To compile this driver as a module, choose M here and read
546 <file:Documentation/parport.txt>. The module will be called lp.
548 If you have several parallel ports, you can specify which ports to
549 use with the "lp" kernel command line option. (Try "man bootparam"
550 or see the documentation of your boot loader (lilo or loadlin) about
551 how to pass options to the kernel at boot time.) The syntax of the
552 "lp" command line option can be found in <file:drivers/char/lp.c>.
554 If you have more than 8 printers, you need to increase the LP_NO
555 macro in lp.c and the PARPORT_MAX macro in parport.h.
558 bool "Support for console on line printer"
561 If you want kernel messages to be printed out as they occur, you
562 can have a console on the printer. This option adds support for
563 doing that; to actually get it to happen you need to pass the
564 option "console=lp0" to the kernel at boot time.
566 If the printer is out of paper (or off, or unplugged, or too
567 busy..) the kernel will stall until the printer is ready again.
568 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
569 can make the kernel continue when this happens,
570 but it'll lose the kernel messages.
575 tristate "Support for user-space parallel port device drivers"
578 Saying Y to this adds support for /dev/parport device nodes. This
579 is needed for programs that want portable access to the parallel
580 port, for instance deviceid (which displays Plug-and-Play device
583 This is the parallel port equivalent of SCSI generic support (sg).
584 It is safe to say N to this -- it is not needed for normal printing
585 or parallel port CD-ROM/disk support.
587 To compile this driver as a module, choose M here: the
588 module will be called ppdev.
593 tristate "Texas Instruments parallel link cable support"
596 If you own a Texas Instruments graphing calculator and use a
597 parallel link cable, then you might be interested in this driver.
599 If you enable this driver, you will be able to communicate with
600 your calculator through a set of device nodes under /dev. The
601 main advantage of this driver is that you don't have to be root
602 to use this precise link cable (depending on the permissions on
603 the device nodes, though).
605 To compile this driver as a module, choose M here: the
606 module will be called tipar.
608 If you don't know what a parallel link cable is or what a Texas
609 Instruments graphing calculator is, then you probably don't need this
617 Users of pSeries machines that want to utilize the hvc console front-end
618 module for their backend console driver should select this option.
619 It will automatically be selected if one of the back-end console drivers
624 bool "pSeries Hypervisor Virtual Console support"
625 depends on PPC_PSERIES
628 pSeries machines when partitioned support a hypervisor virtual
629 console. This driver allows each pSeries partition to have a console
630 which is accessed via the HMC.
633 bool "iSeries Hypervisor Virtual Console support"
634 depends on PPC_ISERIES && !VIOCONS
637 iSeries machines support a hypervisor virtual console.
640 bool "IBM RTAS Console support"
644 IBM Console device driver which makes use of RTAS
647 bool "Toshiba's Beat Hypervisor Console support"
648 depends on PPC_CELLEB
651 Toshiba's Cell Reference Set Beat Console device driver
654 tristate "IBM Hypervisor Virtual Console Server support"
655 depends on PPC_PSERIES
657 Partitionable IBM Power5 ppc64 machines allow hosting of
658 firmware virtual consoles from one Linux partition by
659 another Linux partition. This driver allows console data
660 from Linux partitions to be accessed through TTY device
661 interfaces in the device tree of a Linux partition running
664 To compile this driver as a module, choose M here: the
665 module will be called hvcs.ko. Additionally, this module
666 will depend on arch specific APIs exported from hvcserver.ko
667 which will also be compiled when this driver is built as a
670 source "drivers/char/ipmi/Kconfig"
672 source "drivers/char/watchdog/Kconfig"
675 tristate "NetWinder thermometer support"
676 depends on ARCH_NETWINDER
678 Say Y here to include support for the thermal management hardware
679 found in the NetWinder. This driver allows the user to control the
680 temperature set points and to read the current temperature.
682 It is also possible to say M here to build it as a module (ds1620)
683 It is recommended to be used on a NetWinder, but it is not a
687 tristate "NetWinder Button"
688 depends on ARCH_NETWINDER
690 If you say Y here and create a character device node /dev/nwbutton
691 with major and minor numbers 10 and 158 ("man mknod"), then every
692 time the orange button is pressed a number of times, the number of
693 times the button was pressed will be written to that device.
695 This is most useful for applications, as yet unwritten, which
696 perform actions based on how many times the button is pressed in a
699 Do not hold the button down for too long, as the driver does not
700 alter the behaviour of the hardware reset circuitry attached to the
701 button; it will still execute a hard reset if the button is held
702 down for longer than approximately five seconds.
704 To compile this driver as a module, choose M here: the
705 module will be called nwbutton.
707 Most people will answer Y to this question and "Reboot Using Button"
708 below to be able to initiate a system shutdown from the button.
710 config NWBUTTON_REBOOT
711 bool "Reboot Using Button"
714 If you say Y here, then you will be able to initiate a system
715 shutdown and reboot by pressing the orange button a number of times.
716 The number of presses to initiate the shutdown is two by default,
717 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
718 in nwbutton.h and recompiling the driver or, if you compile the
719 driver as a module, you can specify the number of presses at load
720 time with "insmod button reboot_count=<something>".
723 tristate "NetWinder flash support"
724 depends on ARCH_NETWINDER
726 If you say Y here and create a character device /dev/flash with
727 major 10 and minor 160 you can manipulate the flash ROM containing
728 the NetWinder firmware. Be careful as accidentally overwriting the
729 flash contents can render your computer unbootable. On no account
730 allow random users access to this device. :-)
732 To compile this driver as a module, choose M here: the
733 module will be called nwflash.
735 If you're not sure, say N.
737 source "drivers/char/hw_random/Kconfig"
740 tristate "/dev/nvram support"
741 depends on ATARI || X86 || ARM || GENERIC_NVRAM
743 If you say Y here and create a character special file /dev/nvram
744 with major number 10 and minor number 144 using mknod ("man mknod"),
745 you get read and write access to the extra bytes of non-volatile
746 memory in the real time clock (RTC), which is contained in every PC
747 and most Ataris. The actual number of bytes varies, depending on the
748 nvram in the system, but is usually 114 (128-14 for the RTC).
750 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
751 on Ataris. /dev/nvram may be used to view settings there, or to
752 change them (with some utility). It could also be used to frequently
753 save a few bits of very important data that may not be lost over
754 power-off and for which writing to disk is too insecure. Note
755 however that most NVRAM space in a PC belongs to the BIOS and you
756 should NEVER idly tamper with it. See Ralf Brown's interrupt list
757 for a guide to the use of CMOS bytes by your BIOS.
759 On Atari machines, /dev/nvram is always configured and does not need
762 To compile this driver as a module, choose M here: the
763 module will be called nvram.
766 tristate "Enhanced Real Time Clock Support"
767 depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV && !ARM && !SUPERH
769 If you say Y here and create a character special file /dev/rtc with
770 major number 10 and minor number 135 using mknod ("man mknod"), you
771 will get access to the real time clock (or hardware clock) built
774 Every PC has such a clock built in. It can be used to generate
775 signals from as low as 1Hz up to 8192Hz, and can also be used
776 as a 24 hour alarm. It reports status information via the file
777 /proc/driver/rtc and its behaviour is set by various ioctls on
780 If you run Linux on a multiprocessor machine and said Y to
781 "Symmetric Multi Processing" above, you should say Y here to read
782 and set the RTC in an SMP compatible fashion.
784 If you think you have a use for such a device (such as periodic data
785 sampling), then say Y here, and read <file:Documentation/rtc.txt>
788 To compile this driver as a module, choose M here: the
789 module will be called rtc.
792 tristate "SGI DS1286 RTC support"
795 If you say Y here and create a character special file /dev/rtc with
796 major number 10 and minor number 135 using mknod ("man mknod"), you
797 will get access to the real time clock built into your computer.
798 Every SGI has such a clock built in. It reports status information
799 via the file /proc/rtc and its behaviour is set by various ioctls on
803 bool "SGI M48T35 RTC support"
806 If you say Y here and create a character special file /dev/rtc with
807 major number 10 and minor number 135 using mknod ("man mknod"), you
808 will get access to the real time clock built into your computer.
809 Every SGI has such a clock built in. It reports status information
810 via the file /proc/rtc and its behaviour is set by various ioctls on
814 tristate "Generic /dev/rtc emulation"
815 depends on RTC!=y && !IA64 && !ARM && !M32R && !SPARC && !FRV
817 If you say Y here and create a character special file /dev/rtc with
818 major number 10 and minor number 135 using mknod ("man mknod"), you
819 will get access to the real time clock (or hardware clock) built
822 It reports status information via the file /proc/driver/rtc and its
823 behaviour is set by various ioctls on /dev/rtc. If you enable the
824 "extended RTC operation" below it will also provide an emulation
825 for RTC_UIE which is required by some programs and may improve
826 precision in some cases.
828 To compile this driver as a module, choose M here: the
829 module will be called genrtc.
832 bool "Extended RTC operation"
835 Provides an emulation for RTC_UIE which is required by some programs
836 and may improve precision of the generic RTC support in some cases.
839 bool "EFI Real Time Clock Services"
843 tristate "DS1302 RTC support"
844 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
846 If you say Y here and create a character special file /dev/rtc with
847 major number 121 and minor number 0 using mknod ("man mknod"), you
848 will get access to the real time clock (or hardware clock) built
852 bool "Support for Cobalt LCD"
853 depends on MIPS_COBALT
855 This option enables support for the LCD display and buttons found
856 on Cobalt systems through a misc device.
859 tristate "Double Talk PC internal speech card support"
861 This driver is for the DoubleTalk PC, a speech synthesizer
862 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
863 called the `internal DoubleTalk'.
865 To compile this driver as a module, choose M here: the
866 module will be called dtlk.
869 tristate "Siemens R3964 line discipline"
871 This driver allows synchronous communication with devices using the
872 Siemens R3964 packet protocol. Unless you are dealing with special
873 hardware like PLCs, you are unlikely to need this.
875 To compile this driver as a module, choose M here: the
876 module will be called n_r3964.
881 tristate "Applicom intelligent fieldbus card support"
884 This driver provides the kernel-side support for the intelligent
885 fieldbus cards made by Applicom International. More information
886 about these cards can be found on the WWW at the address
887 <http://www.applicom-int.com/>, or by email from David Woodhouse
888 <dwmw2@infradead.org>.
890 To compile this driver as a module, choose M here: the
891 module will be called applicom.
896 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
897 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
899 This driver enables access to the Sony Programmable I/O Control
900 Device which can be found in many (all ?) Sony Vaio laptops.
902 If you have one of those laptops, read
903 <file:Documentation/sonypi.txt>, and say Y or M here.
905 To compile this driver as a module, choose M here: the
906 module will be called sonypi.
909 tristate "TANBAC TB0219 base board support"
910 depends on TANBAC_TB022X
913 source "drivers/char/agp/Kconfig"
915 source "drivers/char/drm/Kconfig"
917 source "drivers/char/pcmcia/Kconfig"
920 tristate "ACP Modem (Mwave) support"
924 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
925 kernel driver and a user level application. Together these components
926 support direct attachment to public switched telephone networks (PSTNs)
927 and support selected world wide countries.
929 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
930 600, and 770 that include on board ACP modem hardware.
932 The modem also supports the standard communications port interface
933 (ttySx) and is compatible with the Hayes AT Command Set.
935 The user level application needed to use this driver can be found at
936 the IBM Linux Technology Center (LTC) web site:
937 <http://www.ibm.com/linux/ltc/>.
939 If you own one of the above IBM Thinkpads which has the Mwave chipset
942 To compile this driver as a module, choose M here: the
943 module will be called mwave.
946 tristate "NatSemi SCx200 GPIO Support"
950 Give userspace access to the GPIO pins on the National
951 Semiconductor SCx200 processors.
953 If compiled as a module, it will be called scx200_gpio.
956 tristate "NatSemi PC8736x GPIO Support"
958 default SCx200_GPIO # mostly N
959 select NSC_GPIO # needed for support routines
961 Give userspace access to the GPIO pins on the National
962 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
963 has multiple functional units, inc several managed by
964 hwmon/pc87360 driver. Tested with PC-87366
966 If compiled as a module, it will be called pc8736x_gpio.
969 tristate "NatSemi Base GPIO Support"
971 # selected by SCx200_GPIO and PC8736x_GPIO
972 # what about 2 selectors differing: m != y
974 Common support used (and needed) by scx200_gpio and
975 pc8736x_gpio drivers. If those drivers are built as
976 modules, this one will be too, named nsc_gpio
979 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
982 Give userspace access to the GPIO pins on the AMD CS5535 and
983 CS5536 Geode companion devices.
985 If compiled as a module, it will be called cs5535_gpio.
988 tristate "NEC VR4100 series General-purpose I/O Unit support"
989 depends on CPU_VR41XX
992 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
995 The raw driver permits block devices to be bound to /dev/raw/rawN.
996 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
997 See the raw(8) manpage for more details.
999 The raw driver is deprecated and will be removed soon.
1000 Applications should simply open the device (eg /dev/hda1)
1001 with the O_DIRECT flag.
1004 int "Maximum number of RAW devices to support (1-8192)"
1005 depends on RAW_DRIVER
1008 The maximum number of RAW devices that are supported.
1009 Default is 256. Increase this number in case you need lots of
1013 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1017 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1018 open selects one of the timers supported by the HPET. The timers are
1019 non-periodic and/or periodic.
1022 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1026 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1027 is assumed the platform called hpet_alloc with the RTC IRQ values for
1031 bool "Allow mmap of HPET"
1035 If you say Y here, user applications will be able to mmap
1038 In some hardware implementations, the page containing HPET
1039 registers may also contain other things that shouldn't be
1040 exposed to the user. If this applies to your hardware,
1043 config HANGCHECK_TIMER
1044 tristate "Hangcheck timer"
1045 depends on X86 || IA64 || PPC64
1047 The hangcheck-timer module detects when the system has gone
1048 out to lunch past a certain margin. It can reboot the system
1049 or merely print a warning.
1052 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1053 depends on IA64_GENERIC || IA64_SGI_SN2
1056 The mmtimer device allows direct userspace access to the
1059 source "drivers/char/tpm/Kconfig"
1062 tristate "Telecom clock driver for ATCA SBC"
1063 depends on EXPERIMENTAL && X86
1066 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1067 ATCA computers and allows direct userspace access to the
1068 configuration of the telecom clock configuration settings. This
1069 device is used for hardware synchronization across the ATCA backplane
1070 fabric. Upon loading, the driver exports a sysfs directory,
1071 /sys/devices/platform/telco_clock, with a number of files for
1072 controlling the behavior of this hardware.
projects / linux-2.6 / blob