2 # Character device configuration
5 menu "Character devices"
7 source "drivers/tty/Kconfig"
10 bool "/dev/kmem virtual device support"
13 Say Y here if you want to support the /dev/kmem device. The
14 /dev/kmem device is rarely used, but can be used for certain
15 kind of kernel debugging operations.
16 When in doubt, say "N".
19 tristate "Blackfin JTAG Communication"
22 Add support for emulating a TTY device over the Blackfin JTAG.
24 To compile this driver as a module, choose M here: the
25 module will be called bfin_jtag_comm.
27 config BFIN_JTAG_COMM_CONSOLE
28 bool "Console on Blackfin JTAG"
29 depends on BFIN_JTAG_COMM=y
31 config SERIAL_NONSTANDARD
32 bool "Non-standard serial port support"
35 Say Y here if you have any non-standard serial boards -- boards
36 which aren't supported using the standard "dumb" serial driver.
37 This includes intelligent serial boards such as Cyclades,
38 Digiboards, etc. These are usually used for systems that need many
39 serial ports because they serve many terminals or dial-in
42 Note that the answer to this question won't directly affect the
43 kernel: saying N will just cause the configurator to skip all
44 the questions about non-standard serial boards.
46 Most people can say N here.
49 tristate "Computone IntelliPort Plus serial support"
50 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
52 This driver supports the entire family of Intelliport II/Plus
53 controllers with the exception of the MicroChannel controllers and
54 products previous to the Intelliport II. These are multiport cards,
55 which give you many serial ports. You would need something like this
56 to connect more than two modems to your Linux box, for instance in
57 order to become a dial-in server. If you have a card like that, say
58 Y here and read <file:Documentation/serial/computone.txt>.
60 To compile this driver as module, choose M here: the
61 module will be called ip2.
64 tristate "Comtrol RocketPort support"
65 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
67 This driver supports Comtrol RocketPort and RocketModem PCI boards.
68 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
69 modems. For information about the RocketPort/RocketModem boards
70 and this driver read <file:Documentation/serial/rocket.txt>.
72 To compile this driver as a module, choose M here: the
73 module will be called rocket.
75 If you want to compile this driver into the kernel, say Y here. If
76 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
79 tristate "Cyclades async mux support"
80 depends on SERIAL_NONSTANDARD && (PCI || ISA)
83 This driver supports Cyclades Z and Y multiserial boards.
84 You would need something like this to connect more than two modems to
85 your Linux box, for instance in order to become a dial-in server.
87 For information about the Cyclades-Z card, read
88 <file:Documentation/serial/README.cycladesZ>.
90 To compile this driver as a module, choose M here: the
91 module will be called cyclades.
93 If you haven't heard about it, it's safe to say N.
96 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
97 depends on EXPERIMENTAL && CYCLADES
99 The Cyclades-Z family of multiport cards allows 2 (two) driver op
100 modes: polling and interrupt. In polling mode, the driver will check
101 the status of the Cyclades-Z ports every certain amount of time
102 (which is called polling cycle and is configurable). In interrupt
103 mode, it will use an interrupt line (IRQ) in order to check the
104 status of the Cyclades-Z ports. The default op mode is polling. If
108 tristate "Digiboard Intelligent Async Support"
109 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
111 This is a driver for Digi International's Xx, Xeve, and Xem series
112 of cards which provide multiple serial ports. You would need
113 something like this to connect more than two modems to your Linux
114 box, for instance in order to become a dial-in server. This driver
115 supports the original PC (ISA) boards as well as PCI, and EISA. If
116 you have a card like this, say Y here and read the file
117 <file:Documentation/serial/digiepca.txt>.
119 To compile this driver as a module, choose M here: the
120 module will be called epca.
123 tristate "Moxa Intellio support"
124 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
127 Say Y here if you have a Moxa Intellio multiport serial card.
129 To compile this driver as a module, choose M here: the
130 module will be called moxa.
133 tristate "Moxa SmartIO support v. 2.0"
134 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
136 Say Y here if you have a Moxa SmartIO multiport serial card and/or
137 want to help develop a new version of this driver.
139 This is upgraded (1.9.1) driver from original Moxa drivers with
140 changes finally resulting in PCI probing.
142 This driver can also be built as a module. The module will be called
143 mxser. If you want to do that, say M here.
146 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
147 depends on SERIAL_NONSTANDARD && PCI
150 This is a driver for the Multi-Tech cards which provide several
151 serial ports. The driver is experimental and can currently only be
152 built as a module. The module will be called isicom.
153 If you want to do that, choose M here.
156 tristate "Microgate SyncLink card support"
157 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
159 Provides support for the SyncLink ISA and PCI multiprotocol serial
160 adapters. These adapters support asynchronous and HDLC bit
161 synchronous communication up to 10Mbps (PCI adapter).
163 This driver can only be built as a module ( = code which can be
164 inserted in and removed from the running kernel whenever you want).
165 The module will be called synclink. If you want to do that, say M
169 tristate "SyncLink Multiport support"
170 depends on SERIAL_NONSTANDARD && PCI
172 Enable support for the SyncLink Multiport (2 or 4 ports)
173 serial adapter, running asynchronous and HDLC communications up
174 to 2.048Mbps. Each ports is independently selectable for
175 RS-232, V.35, RS-449, RS-530, and X.21
177 This driver may be built as a module ( = code which can be
178 inserted in and removed from the running kernel whenever you want).
179 The module will be called synclinkmp. If you want to do that, say M
183 tristate "SyncLink GT/AC support"
184 depends on SERIAL_NONSTANDARD && PCI
186 Support for SyncLink GT and SyncLink AC families of
187 synchronous and asynchronous serial adapters
188 manufactured by Microgate Systems, Ltd. (www.microgate.com)
191 tristate "HDLC line discipline support"
192 depends on SERIAL_NONSTANDARD
194 Allows synchronous HDLC communications with tty device drivers that
195 support synchronous HDLC such as the Microgate SyncLink adapter.
197 This driver can be built as a module ( = code which can be
198 inserted in and removed from the running kernel whenever you want).
199 The module will be called n_hdlc. If you want to do that, say M
203 tristate "GSM MUX line discipline support (EXPERIMENTAL)"
204 depends on EXPERIMENTAL
207 This line discipline provides support for the GSM MUX protocol and
208 presents the mux as a set of 61 individual tty devices.
211 tristate "SDL RISCom/8 card support"
212 depends on SERIAL_NONSTANDARD
214 This is a driver for the SDL Communications RISCom/8 multiport card,
215 which gives you many serial ports. You would need something like
216 this to connect more than two modems to your Linux box, for instance
217 in order to become a dial-in server. If you have a card like that,
218 say Y here and read the file <file:Documentation/serial/riscom8.txt>.
220 Also it's possible to say M here and compile this driver as kernel
221 loadable module; the module will be called riscom8.
224 tristate "Specialix IO8+ card support"
225 depends on SERIAL_NONSTANDARD
227 This is a driver for the Specialix IO8+ multiport card (both the
228 ISA and the PCI version) which gives you many serial ports. You
229 would need something like this to connect more than two modems to
230 your Linux box, for instance in order to become a dial-in server.
232 If you have a card like that, say Y here and read the file
233 <file:Documentation/serial/specialix.txt>. Also it's possible to say
234 M here and compile this driver as kernel loadable module which will be
238 tristate "Specialix SX (and SI) card support"
239 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA) && BROKEN
241 This is a driver for the SX and SI multiport serial cards.
242 Please read the file <file:Documentation/serial/sx.txt> for details.
244 This driver can only be built as a module ( = code which can be
245 inserted in and removed from the running kernel whenever you want).
246 The module will be called sx. If you want to do that, say M here.
249 tristate "Specialix RIO system support"
250 depends on SERIAL_NONSTANDARD && BROKEN
252 This is a driver for the Specialix RIO, a smart serial card which
253 drives an outboard box that can support up to 128 ports. Product
254 information is at <http://www.perle.com/support/documentation.html#multiport>.
255 There are both ISA and PCI versions.
258 bool "Support really old RIO/PCI cards"
261 Older RIO PCI cards need some initialization-time configuration to
262 determine the IRQ and some control addresses. If you have a RIO and
263 this doesn't seem to work, try setting this to Y.
266 bool "Stallion multiport serial support"
267 depends on SERIAL_NONSTANDARD
269 Stallion cards give you many serial ports. You would need something
270 like this to connect more than two modems to your Linux box, for
271 instance in order to become a dial-in server. If you say Y here,
272 you will be asked for your specific card model in the next
273 questions. Make sure to read <file:Documentation/serial/stallion.txt>
274 in this case. If you have never heard about all this, it's safe to
278 tristate "Stallion EasyIO or EC8/32 support"
279 depends on STALDRV && (ISA || EISA || PCI)
281 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
282 card, then this is for you; say Y. Make sure to read
283 <file:Documentation/serial/stallion.txt>.
285 To compile this driver as a module, choose M here: the
286 module will be called stallion.
289 tristate "Stallion EC8/64, ONboard, Brumby support"
290 depends on STALDRV && (ISA || EISA || PCI)
292 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
293 serial multiport card, say Y here. Make sure to read
294 <file:Documentation/serial/stallion.txt>.
296 To compile this driver as a module, choose M here: the
297 module will be called istallion.
300 tristate "HSDPA Broadband Wireless Data Card - Globe Trotter"
301 depends on PCI && EXPERIMENTAL
303 If you have a HSDPA driver Broadband Wireless Data Card -
304 Globe Trotter PCMCIA card, say Y here.
306 To compile this driver as a module, choose M here, the module
307 will be called nozomi.
310 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
311 depends on EXPERIMENTAL && ZORRO && BROKEN
313 This option supports the 2232 7-port serial card shipped with the
314 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
315 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
316 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
317 ports were connected with 8 pin DIN connectors on the card bracket,
318 for which 8 pin to DB25 adapters were supplied. The card also had
319 jumpers internally to toggle various pinning configurations.
321 This driver can be built as a module; but then "generic_serial"
322 will also be built as a module. This has to be loaded before
323 "ser_a2232". If you want to do this, answer M here.
326 bool "SGI Altix system controller communication support"
327 depends on (IA64_SGI_SN2 || IA64_GENERIC)
329 If you have an SGI Altix and you want to enable system
330 controller communication from user space (you want this!),
331 say Y. Otherwise, say N.
334 bool "SGI TIO CX driver support"
335 depends on (IA64_SGI_SN2 || IA64_GENERIC)
337 If you have an SGI Altix and you have fpga devices attached
338 to your TIO, say Y here, otherwise say N.
341 tristate "SGI FPGA Core Services driver support"
344 If you have an SGI Altix with an attached SABrick
345 say Y or M here, otherwise say N.
347 source "drivers/tty/serial/Kconfig"
350 bool "TTY driver to output user messages via printk"
354 If you say Y here, the support for writing user messages (i.e.
355 console messages) via printk is available.
357 The feature is useful to inline user messages with kernel
359 In order to use this feature, you should output user messages
360 to /dev/ttyprintk or redirect console to this TTY.
365 tristate 'Total Impact briQ front panel driver'
368 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
369 tristate led and two switches. It is the size of a CDROM drive.
371 If you have such one and want anything showing on the VFD then you
374 To compile this driver as a module, choose M here: the
375 module will be called briq_panel.
377 It's safe to say N here.
380 tristate "Blackfin On-Chip OTP Memory Support"
381 depends on BLACKFIN && (BF51x || BF52x || BF54x)
384 If you say Y here, you will get support for a character device
385 interface into the One Time Programmable memory pages that are
386 stored on the Blackfin processor. This will not get you access
387 to the secure memory pages however. You will need to write your
388 own secure code and reader for that.
390 To compile this driver as a module, choose M here: the module
391 will be called bfin-otp.
393 If unsure, it is safe to say Y.
395 config BFIN_OTP_WRITE_ENABLE
396 bool "Enable writing support of OTP pages"
400 If you say Y here, you will enable support for writing of the
401 OTP pages. This is dangerous by nature as you can only program
402 the pages once, so only enable this option when you actually
403 need it so as to not inadvertently clobber data.
408 tristate "Parallel printer support"
411 If you intend to attach a printer to the parallel port of your Linux
412 box (as opposed to using a serial printer; if the connector at the
413 printer has 9 or 25 holes ["female"], then it's serial), say Y.
414 Also read the Printing-HOWTO, available from
415 <http://www.tldp.org/docs.html#howto>.
417 It is possible to share one parallel port among several devices
418 (e.g. printer and ZIP drive) and it is safe to compile the
419 corresponding drivers into the kernel.
421 To compile this driver as a module, choose M here and read
422 <file:Documentation/parport.txt>. The module will be called lp.
424 If you have several parallel ports, you can specify which ports to
425 use with the "lp" kernel command line option. (Try "man bootparam"
426 or see the documentation of your boot loader (lilo or loadlin) about
427 how to pass options to the kernel at boot time.) The syntax of the
428 "lp" command line option can be found in <file:drivers/char/lp.c>.
430 If you have more than 8 printers, you need to increase the LP_NO
431 macro in lp.c and the PARPORT_MAX macro in parport.h.
434 bool "Support for console on line printer"
437 If you want kernel messages to be printed out as they occur, you
438 can have a console on the printer. This option adds support for
439 doing that; to actually get it to happen you need to pass the
440 option "console=lp0" to the kernel at boot time.
442 If the printer is out of paper (or off, or unplugged, or too
443 busy..) the kernel will stall until the printer is ready again.
444 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
445 can make the kernel continue when this happens,
446 but it'll lose the kernel messages.
451 tristate "Support for user-space parallel port device drivers"
454 Saying Y to this adds support for /dev/parport device nodes. This
455 is needed for programs that want portable access to the parallel
456 port, for instance deviceid (which displays Plug-and-Play device
459 This is the parallel port equivalent of SCSI generic support (sg).
460 It is safe to say N to this -- it is not needed for normal printing
461 or parallel port CD-ROM/disk support.
463 To compile this driver as a module, choose M here: the
464 module will be called ppdev.
468 source "drivers/tty/hvc/Kconfig"
470 config VIRTIO_CONSOLE
471 tristate "Virtio console"
475 Virtio console for use with lguest and other hypervisors.
477 Also serves as a general-purpose serial device for data
478 transfer between the guest and host. Character devices at
479 /dev/vportNpn will be created when corresponding ports are
480 found, where N is the device number and n is the port number
481 within that device. If specified by the host, a sysfs
482 attribute called 'name' will be populated with a name for
483 the port which can be used by udev scripts to create a
484 symlink to the device.
487 tristate "IBM POWER Barrier Synchronization Register support"
488 depends on PPC_PSERIES
490 This devices exposes a hardware mechanism for fast synchronization
491 of threads across a large system which avoids bouncing a cacheline
492 between several cores on a system
494 source "drivers/char/ipmi/Kconfig"
497 tristate "NetWinder thermometer support"
498 depends on ARCH_NETWINDER
500 Say Y here to include support for the thermal management hardware
501 found in the NetWinder. This driver allows the user to control the
502 temperature set points and to read the current temperature.
504 It is also possible to say M here to build it as a module (ds1620)
505 It is recommended to be used on a NetWinder, but it is not a
509 tristate "NetWinder Button"
510 depends on ARCH_NETWINDER
512 If you say Y here and create a character device node /dev/nwbutton
513 with major and minor numbers 10 and 158 ("man mknod"), then every
514 time the orange button is pressed a number of times, the number of
515 times the button was pressed will be written to that device.
517 This is most useful for applications, as yet unwritten, which
518 perform actions based on how many times the button is pressed in a
521 Do not hold the button down for too long, as the driver does not
522 alter the behaviour of the hardware reset circuitry attached to the
523 button; it will still execute a hard reset if the button is held
524 down for longer than approximately five seconds.
526 To compile this driver as a module, choose M here: the
527 module will be called nwbutton.
529 Most people will answer Y to this question and "Reboot Using Button"
530 below to be able to initiate a system shutdown from the button.
532 config NWBUTTON_REBOOT
533 bool "Reboot Using Button"
536 If you say Y here, then you will be able to initiate a system
537 shutdown and reboot by pressing the orange button a number of times.
538 The number of presses to initiate the shutdown is two by default,
539 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
540 in nwbutton.h and recompiling the driver or, if you compile the
541 driver as a module, you can specify the number of presses at load
542 time with "insmod button reboot_count=<something>".
545 tristate "NetWinder flash support"
546 depends on ARCH_NETWINDER
548 If you say Y here and create a character device /dev/flash with
549 major 10 and minor 160 you can manipulate the flash ROM containing
550 the NetWinder firmware. Be careful as accidentally overwriting the
551 flash contents can render your computer unbootable. On no account
552 allow random users access to this device. :-)
554 To compile this driver as a module, choose M here: the
555 module will be called nwflash.
557 If you're not sure, say N.
559 source "drivers/char/hw_random/Kconfig"
562 tristate "/dev/nvram support"
563 depends on ATARI || X86 || (ARM && RTC_DRV_CMOS) || GENERIC_NVRAM
565 If you say Y here and create a character special file /dev/nvram
566 with major number 10 and minor number 144 using mknod ("man mknod"),
567 you get read and write access to the extra bytes of non-volatile
568 memory in the real time clock (RTC), which is contained in every PC
569 and most Ataris. The actual number of bytes varies, depending on the
570 nvram in the system, but is usually 114 (128-14 for the RTC).
572 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
573 on Ataris. /dev/nvram may be used to view settings there, or to
574 change them (with some utility). It could also be used to frequently
575 save a few bits of very important data that may not be lost over
576 power-off and for which writing to disk is too insecure. Note
577 however that most NVRAM space in a PC belongs to the BIOS and you
578 should NEVER idly tamper with it. See Ralf Brown's interrupt list
579 for a guide to the use of CMOS bytes by your BIOS.
581 On Atari machines, /dev/nvram is always configured and does not need
584 To compile this driver as a module, choose M here: the
585 module will be called nvram.
588 # These legacy RTC drivers just cause too many conflicts with the generic
589 # RTC framework ... let's not even try to coexist any more.
594 tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
595 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
596 && !ARM && !SUPERH && !S390 && !AVR32 && !BLACKFIN
598 If you say Y here and create a character special file /dev/rtc with
599 major number 10 and minor number 135 using mknod ("man mknod"), you
600 will get access to the real time clock (or hardware clock) built
603 Every PC has such a clock built in. It can be used to generate
604 signals from as low as 1Hz up to 8192Hz, and can also be used
605 as a 24 hour alarm. It reports status information via the file
606 /proc/driver/rtc and its behaviour is set by various ioctls on
609 If you run Linux on a multiprocessor machine and said Y to
610 "Symmetric Multi Processing" above, you should say Y here to read
611 and set the RTC in an SMP compatible fashion.
613 If you think you have a use for such a device (such as periodic data
614 sampling), then say Y here, and read <file:Documentation/rtc.txt>
617 To compile this driver as a module, choose M here: the
618 module will be called rtc.
621 tristate "Enhanced Real Time Clock Support"
622 depends on SPARC32 && PCI
624 If you say Y here and create a character special file /dev/rtc with
625 major number 10 and minor number 135 using mknod ("man mknod"), you
626 will get access to the real time clock (or hardware clock) built
629 Every PC has such a clock built in. It can be used to generate
630 signals from as low as 1Hz up to 8192Hz, and can also be used
631 as a 24 hour alarm. It reports status information via the file
632 /proc/driver/rtc and its behaviour is set by various ioctls on
635 If you think you have a use for such a device (such as periodic data
636 sampling), then say Y here, and read <file:Documentation/rtc.txt>
639 To compile this driver as a module, choose M here: the
640 module will be called js-rtc.
643 tristate "Generic /dev/rtc emulation"
644 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32 && !BLACKFIN
646 If you say Y here and create a character special file /dev/rtc with
647 major number 10 and minor number 135 using mknod ("man mknod"), you
648 will get access to the real time clock (or hardware clock) built
651 It reports status information via the file /proc/driver/rtc and its
652 behaviour is set by various ioctls on /dev/rtc. If you enable the
653 "extended RTC operation" below it will also provide an emulation
654 for RTC_UIE which is required by some programs and may improve
655 precision in some cases.
657 To compile this driver as a module, choose M here: the
658 module will be called genrtc.
661 bool "Extended RTC operation"
664 Provides an emulation for RTC_UIE which is required by some programs
665 and may improve precision of the generic RTC support in some cases.
668 bool "EFI Real Time Clock Services"
672 tristate "DS1302 RTC support"
673 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
675 If you say Y here and create a character special file /dev/rtc with
676 major number 121 and minor number 0 using mknod ("man mknod"), you
677 will get access to the real time clock (or hardware clock) built
683 tristate "Double Talk PC internal speech card support"
686 This driver is for the DoubleTalk PC, a speech synthesizer
687 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
688 called the `internal DoubleTalk'.
690 To compile this driver as a module, choose M here: the
691 module will be called dtlk.
694 tristate "Xilinx HWICAP Support"
695 depends on XILINX_VIRTEX || MICROBLAZE
697 This option enables support for Xilinx Internal Configuration
698 Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
699 FPGA platforms to partially reconfigure the FPGA at runtime.
704 tristate "Siemens R3964 line discipline"
706 This driver allows synchronous communication with devices using the
707 Siemens R3964 packet protocol. Unless you are dealing with special
708 hardware like PLCs, you are unlikely to need this.
710 To compile this driver as a module, choose M here: the
711 module will be called n_r3964.
716 tristate "Applicom intelligent fieldbus card support"
719 This driver provides the kernel-side support for the intelligent
720 fieldbus cards made by Applicom International. More information
721 about these cards can be found on the WWW at the address
722 <http://www.applicom-int.com/>, or by email from David Woodhouse
723 <dwmw2@infradead.org>.
725 To compile this driver as a module, choose M here: the
726 module will be called applicom.
731 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
732 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
734 This driver enables access to the Sony Programmable I/O Control
735 Device which can be found in many (all ?) Sony Vaio laptops.
737 If you have one of those laptops, read
738 <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
740 To compile this driver as a module, choose M here: the
741 module will be called sonypi.
744 tristate "TANBAC TB0219 GPIO support"
745 depends on TANBAC_TB022X
748 source "drivers/char/pcmcia/Kconfig"
751 tristate "ACP Modem (Mwave) support"
755 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
756 kernel driver and a user level application. Together these components
757 support direct attachment to public switched telephone networks (PSTNs)
758 and support selected world wide countries.
760 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
761 600, and 770 that include on board ACP modem hardware.
763 The modem also supports the standard communications port interface
764 (ttySx) and is compatible with the Hayes AT Command Set.
766 The user level application needed to use this driver can be found at
767 the IBM Linux Technology Center (LTC) web site:
768 <http://www.ibm.com/linux/ltc/>.
770 If you own one of the above IBM Thinkpads which has the Mwave chipset
773 To compile this driver as a module, choose M here: the
774 module will be called mwave.
777 tristate "NatSemi SCx200 GPIO Support"
781 Give userspace access to the GPIO pins on the National
782 Semiconductor SCx200 processors.
784 If compiled as a module, it will be called scx200_gpio.
787 tristate "NatSemi PC8736x GPIO Support"
789 default SCx200_GPIO # mostly N
790 select NSC_GPIO # needed for support routines
792 Give userspace access to the GPIO pins on the National
793 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
794 has multiple functional units, inc several managed by
795 hwmon/pc87360 driver. Tested with PC-87366
797 If compiled as a module, it will be called pc8736x_gpio.
800 tristate "NatSemi Base GPIO Support"
802 # selected by SCx200_GPIO and PC8736x_GPIO
803 # what about 2 selectors differing: m != y
805 Common support used (and needed) by scx200_gpio and
806 pc8736x_gpio drivers. If those drivers are built as
807 modules, this one will be too, named nsc_gpio
810 tristate "RAW driver (/dev/raw/rawN)"
813 The raw driver permits block devices to be bound to /dev/raw/rawN.
814 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
815 See the raw(8) manpage for more details.
817 Applications should preferably open the device (eg /dev/hda1)
818 with the O_DIRECT flag.
821 int "Maximum number of RAW devices to support (1-8192)"
822 depends on RAW_DRIVER
825 The maximum number of RAW devices that are supported.
826 Default is 256. Increase this number in case you need lots of
830 bool "HPET - High Precision Event Timer" if (X86 || IA64)
834 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
835 open selects one of the timers supported by the HPET. The timers are
836 non-periodic and/or periodic.
839 bool "Allow mmap of HPET"
843 If you say Y here, user applications will be able to mmap
846 In some hardware implementations, the page containing HPET
847 registers may also contain other things that shouldn't be
848 exposed to the user. If this applies to your hardware,
851 config HANGCHECK_TIMER
852 tristate "Hangcheck timer"
853 depends on X86 || IA64 || PPC64 || S390
855 The hangcheck-timer module detects when the system has gone
856 out to lunch past a certain margin. It can reboot the system
857 or merely print a warning.
860 tristate "MMTIMER Memory mapped RTC for SGI Altix"
861 depends on IA64_GENERIC || IA64_SGI_SN2
864 The mmtimer device allows direct userspace access to the
868 tristate "UV_MMTIMER Memory mapped RTC for SGI UV"
872 The uv_mmtimer device allows direct userspace access to the
875 source "drivers/char/tpm/Kconfig"
878 tristate "Telecom clock driver for ATCA SBC"
879 depends on EXPERIMENTAL && X86
882 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
883 ATCA computers and allows direct userspace access to the
884 configuration of the telecom clock configuration settings. This
885 device is used for hardware synchronization across the ATCA backplane
886 fabric. Upon loading, the driver exports a sysfs directory,
887 /sys/devices/platform/telco_clock, with a number of files for
888 controlling the behavior of this hardware.
893 depends on ISA || PCI
896 source "drivers/s390/char/Kconfig"
899 tristate "Log panic/oops to a RAM buffer"
903 This enables panic and oops messages to be logged to a circular
904 buffer in RAM where it can be read back at some later point.