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