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>.
84 bool "/dev/kmem virtual device support"
87 Say Y here if you want to support the /dev/kmem device. The
88 /dev/kmem device is rarely used, but can be used for certain
89 kind of kernel debugging operations.
90 When in doubt, say "N".
92 config SERIAL_NONSTANDARD
93 bool "Non-standard serial port support"
96 Say Y here if you have any non-standard serial boards -- boards
97 which aren't supported using the standard "dumb" serial driver.
98 This includes intelligent serial boards such as Cyclades,
99 Digiboards, etc. These are usually used for systems that need many
100 serial ports because they serve many terminals or dial-in
103 Note that the answer to this question won't directly affect the
104 kernel: saying N will just cause the configurator to skip all
105 the questions about non-standard serial boards.
107 Most people can say N here.
110 tristate "Computone IntelliPort Plus serial support"
111 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
113 This driver supports the entire family of Intelliport II/Plus
114 controllers with the exception of the MicroChannel controllers and
115 products previous to the Intelliport II. These are multiport cards,
116 which give you many serial ports. You would need something like this
117 to connect more than two modems to your Linux box, for instance in
118 order to become a dial-in server. If you have a card like that, say
119 Y here and read <file:Documentation/computone.txt>.
121 To compile this driver as modules, choose M here: the
122 modules will be called ip2 and ip2main.
125 tristate "Comtrol RocketPort support"
126 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
128 This driver supports Comtrol RocketPort and RocketModem PCI boards.
129 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
130 modems. For information about the RocketPort/RocketModem boards
131 and this driver read <file:Documentation/rocket.txt>.
133 To compile this driver as a module, choose M here: the
134 module will be called rocket.
136 If you want to compile this driver into the kernel, say Y here. If
137 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
140 tristate "Cyclades async mux support"
141 depends on SERIAL_NONSTANDARD && (PCI || ISA)
144 This driver supports Cyclades Z and Y multiserial boards.
145 You would need something like this to connect more than two modems to
146 your Linux box, for instance in order to become a dial-in server.
148 For information about the Cyclades-Z card, read
149 <file:Documentation/README.cycladesZ>.
151 To compile this driver as a module, choose M here: the
152 module will be called cyclades.
154 If you haven't heard about it, it's safe to say N.
157 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
158 depends on EXPERIMENTAL && CYCLADES
160 The Cyclades-Z family of multiport cards allows 2 (two) driver op
161 modes: polling and interrupt. In polling mode, the driver will check
162 the status of the Cyclades-Z ports every certain amount of time
163 (which is called polling cycle and is configurable). In interrupt
164 mode, it will use an interrupt line (IRQ) in order to check the
165 status of the Cyclades-Z ports. The default op mode is polling. If
169 tristate "Digiboard Intelligent Async Support"
170 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
172 This is a driver for Digi International's Xx, Xeve, and Xem series
173 of cards which provide multiple serial ports. You would need
174 something like this to connect more than two modems to your Linux
175 box, for instance in order to become a dial-in server. This driver
176 supports the original PC (ISA) boards as well as PCI, and EISA. If
177 you have a card like this, say Y here and read the file
178 <file:Documentation/digiepca.txt>.
180 To compile this driver as a module, choose M here: the
181 module will be called epca.
184 tristate "Hayes ESP serial port support"
185 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
187 This is a driver which supports Hayes ESP serial ports. Both single
188 port cards and multiport cards are supported. Make sure to read
189 <file:Documentation/hayes-esp.txt>.
191 To compile this driver as a module, choose M here: the
192 module will be called esp.
197 tristate "Moxa Intellio support"
198 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
200 Say Y here if you have a Moxa Intellio multiport serial card.
202 To compile this driver as a module, choose M here: the
203 module will be called moxa.
206 tristate "Moxa SmartIO support v. 2.0"
207 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
209 Say Y here if you have a Moxa SmartIO multiport serial card and/or
210 want to help develop a new version of this driver.
212 This is upgraded (1.9.1) driver from original Moxa drivers with
213 changes finally resulting in PCI probing.
215 This driver can also be built as a module. The module will be called
216 mxser. If you want to do that, say M here.
219 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
220 depends on SERIAL_NONSTANDARD && PCI
223 This is a driver for the Multi-Tech cards which provide several
224 serial ports. The driver is experimental and can currently only be
225 built as a module. The module will be called isicom.
226 If you want to do that, choose M here.
229 tristate "Microgate SyncLink card support"
230 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
232 Provides support for the SyncLink ISA and PCI multiprotocol serial
233 adapters. These adapters support asynchronous and HDLC bit
234 synchronous communication up to 10Mbps (PCI adapter).
236 This driver can only be built as a module ( = code which can be
237 inserted in and removed from the running kernel whenever you want).
238 The module will be called synclink. If you want to do that, say M
242 tristate "SyncLink Multiport support"
243 depends on SERIAL_NONSTANDARD && PCI
245 Enable support for the SyncLink Multiport (2 or 4 ports)
246 serial adapter, running asynchronous and HDLC communications up
247 to 2.048Mbps. Each ports is independently selectable for
248 RS-232, V.35, RS-449, RS-530, and X.21
250 This driver may be built as a module ( = code which can be
251 inserted in and removed from the running kernel whenever you want).
252 The module will be called synclinkmp. If you want to do that, say M
256 tristate "SyncLink GT/AC support"
257 depends on SERIAL_NONSTANDARD && PCI
259 Support for SyncLink GT and SyncLink AC families of
260 synchronous and asynchronous serial adapters
261 manufactured by Microgate Systems, Ltd. (www.microgate.com)
264 tristate "HDLC line discipline support"
265 depends on SERIAL_NONSTANDARD
267 Allows synchronous HDLC communications with tty device drivers that
268 support synchronous HDLC such as the Microgate SyncLink adapter.
270 This driver can only be built as a module ( = code which can be
271 inserted in and removed from the running kernel whenever you want).
272 The module will be called n_hdlc. If you want to do that, say M
276 tristate "SDL RISCom/8 card support"
277 depends on SERIAL_NONSTANDARD
279 This is a driver for the SDL Communications RISCom/8 multiport card,
280 which gives you many serial ports. You would need something like
281 this to connect more than two modems to your Linux box, for instance
282 in order to become a dial-in server. If you have a card like that,
283 say Y here and read the file <file:Documentation/riscom8.txt>.
285 Also it's possible to say M here and compile this driver as kernel
286 loadable module; the module will be called riscom8.
289 tristate "Specialix IO8+ card support"
290 depends on SERIAL_NONSTANDARD
292 This is a driver for the Specialix IO8+ multiport card (both the
293 ISA and the PCI version) which gives you many serial ports. You
294 would need something like this to connect more than two modems to
295 your Linux box, for instance in order to become a dial-in server.
297 If you have a card like that, say Y here and read the file
298 <file:Documentation/specialix.txt>. Also it's possible to say M here
299 and compile this driver as kernel loadable module which will be
302 config SPECIALIX_RTSCTS
303 bool "Specialix DTR/RTS pin is RTS"
306 The Specialix IO8+ card can only support either RTS or DTR. If you
307 say N here, the driver will use the pin as "DTR" when the tty is in
308 software handshake mode. If you say Y here or hardware handshake is
309 on, it will always be RTS. Read the file
310 <file:Documentation/specialix.txt> for more information.
313 tristate "Specialix SX (and SI) card support"
314 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
316 This is a driver for the SX and SI multiport serial cards.
317 Please read the file <file:Documentation/sx.txt> for details.
319 This driver can only be built as a module ( = code which can be
320 inserted in and removed from the running kernel whenever you want).
321 The module will be called sx. If you want to do that, say M here.
324 tristate "Specialix RIO system support"
325 depends on SERIAL_NONSTANDARD
327 This is a driver for the Specialix RIO, a smart serial card which
328 drives an outboard box that can support up to 128 ports. Product
329 information is at <http://www.perle.com/support/documentation.html#multiport>.
330 There are both ISA and PCI versions.
333 bool "Support really old RIO/PCI cards"
336 Older RIO PCI cards need some initialization-time configuration to
337 determine the IRQ and some control addresses. If you have a RIO and
338 this doesn't seem to work, try setting this to Y.
341 bool "Stallion multiport serial support"
342 depends on SERIAL_NONSTANDARD
344 Stallion cards give you many serial ports. You would need something
345 like this to connect more than two modems to your Linux box, for
346 instance in order to become a dial-in server. If you say Y here,
347 you will be asked for your specific card model in the next
348 questions. Make sure to read <file:Documentation/stallion.txt> in
349 this case. If you have never heard about all this, it's safe to
353 tristate "Stallion EasyIO or EC8/32 support"
354 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
356 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
357 card, then this is for you; say Y. Make sure to read
358 <file:Documentation/stallion.txt>.
360 To compile this driver as a module, choose M here: the
361 module will be called stallion.
364 tristate "Stallion EC8/64, ONboard, Brumby support"
365 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
367 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
368 serial multiport card, say Y here. Make sure to read
369 <file:Documentation/stallion.txt>.
371 To compile this driver as a module, choose M here: the
372 module will be called istallion.
375 tristate "HSDPA Broadband Wireless Data Card - Globe Trotter"
376 depends on PCI && EXPERIMENTAL
378 If you have a HSDPA driver Broadband Wireless Data Card -
379 Globe Trotter PCMCIA card, say Y here.
381 To compile this driver as a module, choose M here, the module
382 will be called nozomi.
385 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
386 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
388 This option supports the 2232 7-port serial card shipped with the
389 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
390 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
391 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
392 ports were connected with 8 pin DIN connectors on the card bracket,
393 for which 8 pin to DB25 adapters were supplied. The card also had
394 jumpers internally to toggle various pinning configurations.
396 This driver can be built as a module; but then "generic_serial"
397 will also be built as a module. This has to be loaded before
398 "ser_a2232". If you want to do this, answer M here.
401 bool "SGI Altix system controller communication support"
402 depends on (IA64_SGI_SN2 || IA64_GENERIC)
404 If you have an SGI Altix and you want to enable system
405 controller communication from user space (you want this!),
406 say Y. Otherwise, say N.
409 bool "SGI TIO CX driver support"
410 depends on (IA64_SGI_SN2 || IA64_GENERIC)
412 If you have an SGI Altix and you have fpga devices attached
413 to your TIO, say Y here, otherwise say N.
416 tristate "SGI FPGA Core Services driver support"
419 If you have an SGI Altix with an attached SABrick
420 say Y or M here, otherwise say N.
422 source "drivers/serial/Kconfig"
425 bool "Unix98 PTY support" if EMBEDDED
428 A pseudo terminal (PTY) is a software device consisting of two
429 halves: a master and a slave. The slave device behaves identical to
430 a physical terminal; the master device is used by a process to
431 read data from and write data to the slave, thereby emulating a
432 terminal. Typical programs for the master side are telnet servers
435 Linux has traditionally used the BSD-like names /dev/ptyxx for
436 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
437 has a number of problems. The GNU C library glibc 2.1 and later,
438 however, supports the Unix98 naming standard: in order to acquire a
439 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
440 terminal is then made available to the process and the pseudo
441 terminal slave can be accessed as /dev/pts/<number>. What was
442 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
444 All modern Linux systems use the Unix98 ptys. Say Y unless
445 you're on an embedded system and want to conserve memory.
448 bool "Legacy (BSD) PTY support"
451 A pseudo terminal (PTY) is a software device consisting of two
452 halves: a master and a slave. The slave device behaves identical to
453 a physical terminal; the master device is used by a process to
454 read data from and write data to the slave, thereby emulating a
455 terminal. Typical programs for the master side are telnet servers
458 Linux has traditionally used the BSD-like names /dev/ptyxx
459 for masters and /dev/ttyxx for slaves of pseudo
460 terminals. This scheme has a number of problems, including
461 security. This option enables these legacy devices; on most
462 systems, it is safe to say N.
465 config LEGACY_PTY_COUNT
466 int "Maximum number of legacy PTY in use"
467 depends on LEGACY_PTYS
471 The maximum number of legacy PTYs that can be used at any one time.
472 The default is 256, and should be more than enough. Embedded
473 systems may want to reduce this to save memory.
475 When not in use, each legacy PTY occupies 12 bytes on 32-bit
476 architectures and 24 bytes on 64-bit architectures.
479 tristate 'Total Impact briQ front panel driver'
482 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
483 tristate led and two switches. It is the size of a CDROM drive.
485 If you have such one and want anything showing on the VFD then you
488 To compile this driver as a module, choose M here: the
489 module will be called briq_panel.
491 It's safe to say N here.
494 tristate "Blackfin On-Chip OTP Memory Support"
495 depends on BLACKFIN && (BF52x || BF54x)
498 If you say Y here, you will get support for a character device
499 interface into the One Time Programmable memory pages that are
500 stored on the Blackfin processor. This will not get you access
501 to the secure memory pages however. You will need to write your
502 own secure code and reader for that.
504 To compile this driver as a module, choose M here: the module
505 will be called bfin-otp.
507 If unsure, it is safe to say Y.
509 config BFIN_OTP_WRITE_ENABLE
510 bool "Enable writing support of OTP pages"
514 If you say Y here, you will enable support for writing of the
515 OTP pages. This is dangerous by nature as you can only program
516 the pages once, so only enable this option when you actually
517 need it so as to not inadvertently clobber data.
522 tristate "Parallel printer support"
525 If you intend to attach a printer to the parallel port of your Linux
526 box (as opposed to using a serial printer; if the connector at the
527 printer has 9 or 25 holes ["female"], then it's serial), say Y.
528 Also read the Printing-HOWTO, available from
529 <http://www.tldp.org/docs.html#howto>.
531 It is possible to share one parallel port among several devices
532 (e.g. printer and ZIP drive) and it is safe to compile the
533 corresponding drivers into the kernel.
535 To compile this driver as a module, choose M here and read
536 <file:Documentation/parport.txt>. The module will be called lp.
538 If you have several parallel ports, you can specify which ports to
539 use with the "lp" kernel command line option. (Try "man bootparam"
540 or see the documentation of your boot loader (lilo or loadlin) about
541 how to pass options to the kernel at boot time.) The syntax of the
542 "lp" command line option can be found in <file:drivers/char/lp.c>.
544 If you have more than 8 printers, you need to increase the LP_NO
545 macro in lp.c and the PARPORT_MAX macro in parport.h.
548 bool "Support for console on line printer"
551 If you want kernel messages to be printed out as they occur, you
552 can have a console on the printer. This option adds support for
553 doing that; to actually get it to happen you need to pass the
554 option "console=lp0" to the kernel at boot time.
556 If the printer is out of paper (or off, or unplugged, or too
557 busy..) the kernel will stall until the printer is ready again.
558 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
559 can make the kernel continue when this happens,
560 but it'll lose the kernel messages.
565 tristate "Support for user-space parallel port device drivers"
568 Saying Y to this adds support for /dev/parport device nodes. This
569 is needed for programs that want portable access to the parallel
570 port, for instance deviceid (which displays Plug-and-Play device
573 This is the parallel port equivalent of SCSI generic support (sg).
574 It is safe to say N to this -- it is not needed for normal printing
575 or parallel port CD-ROM/disk support.
577 To compile this driver as a module, choose M here: the
578 module will be called ppdev.
585 Generic "hypervisor virtual console" infrastructure for various
586 hypervisors (pSeries, iSeries, Xen, lguest).
587 It will automatically be selected if one of the back-end console drivers
592 bool "pSeries Hypervisor Virtual Console support"
593 depends on PPC_PSERIES
596 pSeries machines when partitioned support a hypervisor virtual
597 console. This driver allows each pSeries partition to have a console
598 which is accessed via the HMC.
601 bool "iSeries Hypervisor Virtual Console support"
602 depends on PPC_ISERIES
606 iSeries machines support a hypervisor virtual console.
609 bool "IBM RTAS Console support"
613 IBM Console device driver which makes use of RTAS
616 bool "Toshiba's Beat Hypervisor Console support"
617 depends on PPC_CELLEB
620 Toshiba's Cell Reference Set Beat Console device driver
623 bool "Xen Hypervisor Console support"
628 Xen virtual console device driver
630 config VIRTIO_CONSOLE
635 tristate "IBM Hypervisor Virtual Console Server support"
636 depends on PPC_PSERIES
638 Partitionable IBM Power5 ppc64 machines allow hosting of
639 firmware virtual consoles from one Linux partition by
640 another Linux partition. This driver allows console data
641 from Linux partitions to be accessed through TTY device
642 interfaces in the device tree of a Linux partition running
645 To compile this driver as a module, choose M here: the
646 module will be called hvcs.ko. Additionally, this module
647 will depend on arch specific APIs exported from hvcserver.ko
648 which will also be compiled when this driver is built as a
651 source "drivers/char/ipmi/Kconfig"
654 tristate "NetWinder thermometer support"
655 depends on ARCH_NETWINDER
657 Say Y here to include support for the thermal management hardware
658 found in the NetWinder. This driver allows the user to control the
659 temperature set points and to read the current temperature.
661 It is also possible to say M here to build it as a module (ds1620)
662 It is recommended to be used on a NetWinder, but it is not a
666 tristate "NetWinder Button"
667 depends on ARCH_NETWINDER
669 If you say Y here and create a character device node /dev/nwbutton
670 with major and minor numbers 10 and 158 ("man mknod"), then every
671 time the orange button is pressed a number of times, the number of
672 times the button was pressed will be written to that device.
674 This is most useful for applications, as yet unwritten, which
675 perform actions based on how many times the button is pressed in a
678 Do not hold the button down for too long, as the driver does not
679 alter the behaviour of the hardware reset circuitry attached to the
680 button; it will still execute a hard reset if the button is held
681 down for longer than approximately five seconds.
683 To compile this driver as a module, choose M here: the
684 module will be called nwbutton.
686 Most people will answer Y to this question and "Reboot Using Button"
687 below to be able to initiate a system shutdown from the button.
689 config NWBUTTON_REBOOT
690 bool "Reboot Using Button"
693 If you say Y here, then you will be able to initiate a system
694 shutdown and reboot by pressing the orange button a number of times.
695 The number of presses to initiate the shutdown is two by default,
696 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
697 in nwbutton.h and recompiling the driver or, if you compile the
698 driver as a module, you can specify the number of presses at load
699 time with "insmod button reboot_count=<something>".
702 tristate "NetWinder flash support"
703 depends on ARCH_NETWINDER
705 If you say Y here and create a character device /dev/flash with
706 major 10 and minor 160 you can manipulate the flash ROM containing
707 the NetWinder firmware. Be careful as accidentally overwriting the
708 flash contents can render your computer unbootable. On no account
709 allow random users access to this device. :-)
711 To compile this driver as a module, choose M here: the
712 module will be called nwflash.
714 If you're not sure, say N.
716 source "drivers/char/hw_random/Kconfig"
719 tristate "/dev/nvram support"
720 depends on ATARI || X86 || ARM || GENERIC_NVRAM
722 If you say Y here and create a character special file /dev/nvram
723 with major number 10 and minor number 144 using mknod ("man mknod"),
724 you get read and write access to the extra bytes of non-volatile
725 memory in the real time clock (RTC), which is contained in every PC
726 and most Ataris. The actual number of bytes varies, depending on the
727 nvram in the system, but is usually 114 (128-14 for the RTC).
729 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
730 on Ataris. /dev/nvram may be used to view settings there, or to
731 change them (with some utility). It could also be used to frequently
732 save a few bits of very important data that may not be lost over
733 power-off and for which writing to disk is too insecure. Note
734 however that most NVRAM space in a PC belongs to the BIOS and you
735 should NEVER idly tamper with it. See Ralf Brown's interrupt list
736 for a guide to the use of CMOS bytes by your BIOS.
738 On Atari machines, /dev/nvram is always configured and does not need
741 To compile this driver as a module, choose M here: the
742 module will be called nvram.
745 # These legacy RTC drivers just cause too many conflicts with the generic
746 # RTC framework ... let's not even try to coexist any more.
751 tristate "Enhanced Real Time Clock Support"
752 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
753 && !ARM && !SUPERH && !S390 && !AVR32
755 If you say Y here and create a character special file /dev/rtc with
756 major number 10 and minor number 135 using mknod ("man mknod"), you
757 will get access to the real time clock (or hardware clock) built
760 Every PC has such a clock built in. It can be used to generate
761 signals from as low as 1Hz up to 8192Hz, and can also be used
762 as a 24 hour alarm. It reports status information via the file
763 /proc/driver/rtc and its behaviour is set by various ioctls on
766 If you run Linux on a multiprocessor machine and said Y to
767 "Symmetric Multi Processing" above, you should say Y here to read
768 and set the RTC in an SMP compatible fashion.
770 If you think you have a use for such a device (such as periodic data
771 sampling), then say Y here, and read <file:Documentation/rtc.txt>
774 To compile this driver as a module, choose M here: the
775 module will be called rtc.
778 tristate "Enhanced Real Time Clock Support"
779 depends on SPARC32 && PCI
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 Every PC has such a clock built in. It can be used to generate
787 signals from as low as 1Hz up to 8192Hz, and can also be used
788 as a 24 hour alarm. It reports status information via the file
789 /proc/driver/rtc and its behaviour is set by various ioctls on
792 If you think you have a use for such a device (such as periodic data
793 sampling), then say Y here, and read <file:Documentation/rtc.txt>
796 To compile this driver as a module, choose M here: the
797 module will be called js-rtc.
800 tristate "SGI DS1286 RTC support"
801 depends on SGI_HAS_DS1286
803 If you say Y here and create a character special file /dev/rtc with
804 major number 10 and minor number 135 using mknod ("man mknod"), you
805 will get access to the real time clock built into your computer.
806 Every SGI has such a clock built in. It reports status information
807 via the file /proc/rtc and its behaviour is set by various ioctls on
811 bool "SGI M48T35 RTC support"
814 If you say Y here and create a character special file /dev/rtc with
815 major number 10 and minor number 135 using mknod ("man mknod"), you
816 will get access to the real time clock built into your computer.
817 Every SGI has such a clock built in. It reports status information
818 via the file /proc/rtc and its behaviour is set by various ioctls on
822 tristate "Generic /dev/rtc emulation"
823 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32
825 If you say Y here and create a character special file /dev/rtc with
826 major number 10 and minor number 135 using mknod ("man mknod"), you
827 will get access to the real time clock (or hardware clock) built
830 It reports status information via the file /proc/driver/rtc and its
831 behaviour is set by various ioctls on /dev/rtc. If you enable the
832 "extended RTC operation" below it will also provide an emulation
833 for RTC_UIE which is required by some programs and may improve
834 precision in some cases.
836 To compile this driver as a module, choose M here: the
837 module will be called genrtc.
840 bool "Extended RTC operation"
843 Provides an emulation for RTC_UIE which is required by some programs
844 and may improve precision of the generic RTC support in some cases.
847 bool "EFI Real Time Clock Services"
851 tristate "DS1302 RTC support"
852 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
854 If you say Y here and create a character special file /dev/rtc with
855 major number 121 and minor number 0 using mknod ("man mknod"), you
856 will get access to the real time clock (or hardware clock) built
862 bool "Support for Cobalt LCD"
863 depends on MIPS_COBALT
865 This option enables support for the LCD display and buttons found
866 on Cobalt systems through a misc device.
869 tristate "Double Talk PC internal speech card support"
872 This driver is for the DoubleTalk PC, a speech synthesizer
873 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
874 called the `internal DoubleTalk'.
876 To compile this driver as a module, choose M here: the
877 module will be called dtlk.
880 tristate "Xilinx HWICAP Support"
881 depends on XILINX_VIRTEX
883 This option enables support for Xilinx Internal Configuration
884 Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
885 FPGA platforms to partially reconfigure the FPGA at runtime.
890 tristate "Siemens R3964 line discipline"
892 This driver allows synchronous communication with devices using the
893 Siemens R3964 packet protocol. Unless you are dealing with special
894 hardware like PLCs, you are unlikely to need this.
896 To compile this driver as a module, choose M here: the
897 module will be called n_r3964.
902 tristate "Applicom intelligent fieldbus card support"
905 This driver provides the kernel-side support for the intelligent
906 fieldbus cards made by Applicom International. More information
907 about these cards can be found on the WWW at the address
908 <http://www.applicom-int.com/>, or by email from David Woodhouse
909 <dwmw2@infradead.org>.
911 To compile this driver as a module, choose M here: the
912 module will be called applicom.
917 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
918 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
920 This driver enables access to the Sony Programmable I/O Control
921 Device which can be found in many (all ?) Sony Vaio laptops.
923 If you have one of those laptops, read
924 <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
926 To compile this driver as a module, choose M here: the
927 module will be called sonypi.
930 tristate "TANBAC TB0219 GPIO support"
931 depends on TANBAC_TB022X
934 source "drivers/char/pcmcia/Kconfig"
937 tristate "ACP Modem (Mwave) support"
941 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
942 kernel driver and a user level application. Together these components
943 support direct attachment to public switched telephone networks (PSTNs)
944 and support selected world wide countries.
946 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
947 600, and 770 that include on board ACP modem hardware.
949 The modem also supports the standard communications port interface
950 (ttySx) and is compatible with the Hayes AT Command Set.
952 The user level application needed to use this driver can be found at
953 the IBM Linux Technology Center (LTC) web site:
954 <http://www.ibm.com/linux/ltc/>.
956 If you own one of the above IBM Thinkpads which has the Mwave chipset
959 To compile this driver as a module, choose M here: the
960 module will be called mwave.
963 tristate "NatSemi SCx200 GPIO Support"
967 Give userspace access to the GPIO pins on the National
968 Semiconductor SCx200 processors.
970 If compiled as a module, it will be called scx200_gpio.
973 tristate "NatSemi PC8736x GPIO Support"
975 default SCx200_GPIO # mostly N
976 select NSC_GPIO # needed for support routines
978 Give userspace access to the GPIO pins on the National
979 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
980 has multiple functional units, inc several managed by
981 hwmon/pc87360 driver. Tested with PC-87366
983 If compiled as a module, it will be called pc8736x_gpio.
986 tristate "NatSemi Base GPIO Support"
988 # selected by SCx200_GPIO and PC8736x_GPIO
989 # what about 2 selectors differing: m != y
991 Common support used (and needed) by scx200_gpio and
992 pc8736x_gpio drivers. If those drivers are built as
993 modules, this one will be too, named nsc_gpio
996 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
999 Give userspace access to the GPIO pins on the AMD CS5535 and
1000 CS5536 Geode companion devices.
1002 If compiled as a module, it will be called cs5535_gpio.
1005 tristate "NEC VR4100 series General-purpose I/O Unit support"
1006 depends on CPU_VR41XX
1009 tristate "RAW driver (/dev/raw/rawN)"
1012 The raw driver permits block devices to be bound to /dev/raw/rawN.
1013 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
1014 See the raw(8) manpage for more details.
1016 Applications should preferably open the device (eg /dev/hda1)
1017 with the O_DIRECT flag.
1020 int "Maximum number of RAW devices to support (1-8192)"
1021 depends on RAW_DRIVER
1024 The maximum number of RAW devices that are supported.
1025 Default is 256. Increase this number in case you need lots of
1029 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1033 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1034 open selects one of the timers supported by the HPET. The timers are
1035 non-periodic and/or periodic.
1038 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1042 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1043 is assumed the platform called hpet_alloc with the RTC IRQ values for
1047 bool "Allow mmap of HPET"
1051 If you say Y here, user applications will be able to mmap
1054 In some hardware implementations, the page containing HPET
1055 registers may also contain other things that shouldn't be
1056 exposed to the user. If this applies to your hardware,
1059 config HANGCHECK_TIMER
1060 tristate "Hangcheck timer"
1061 depends on X86 || IA64 || PPC64 || S390
1063 The hangcheck-timer module detects when the system has gone
1064 out to lunch past a certain margin. It can reboot the system
1065 or merely print a warning.
1068 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1069 depends on IA64_GENERIC || IA64_SGI_SN2
1072 The mmtimer device allows direct userspace access to the
1075 source "drivers/char/tpm/Kconfig"
1078 tristate "Telecom clock driver for ATCA SBC"
1079 depends on EXPERIMENTAL && X86
1082 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1083 ATCA computers and allows direct userspace access to the
1084 configuration of the telecom clock configuration settings. This
1085 device is used for hardware synchronization across the ATCA backplane
1086 fabric. Upon loading, the driver exports a sysfs directory,
1087 /sys/devices/platform/telco_clock, with a number of files for
1088 controlling the behavior of this hardware.
1093 depends on ISA || PCI
1096 source "drivers/s390/char/Kconfig"
git://ftp.safe.ca / safe / jmp / linux-2.6 / blob