| blob | dd7e6901c575b8d0d36dc22b17a820371ed95ec8 |
1 #
2 # Character device configuration
3 #
5 menu "Character devices"
7 config VT
8 bool "Virtual terminal" if EMBEDDED
9 select INPUT
10 default y if !VIOCONS
11 ---help---
12 If you say Y here, you will get support for terminal devices with
13 display and keyboard devices. These are called "virtual" because you
14 can run several virtual terminals (also called virtual consoles) on
15 one physical terminal. This is rather useful, for example one
16 virtual terminal can collect system messages and warnings, another
17 one can be used for a text-mode user session, and a third could run
18 an X session, all in parallel. Switching between virtual terminals
19 is done with certain key combinations, usually Alt-<function key>.
21 The setterm command ("man setterm") can be used to change the
22 properties (such as colors or beeping) of a virtual terminal. The
23 man page console_codes(4) ("man console_codes") contains the special
24 character sequences that can be used to change those properties
25 directly. The fonts used on virtual terminals can be changed with
26 the setfont ("man setfont") command and the key bindings are defined
27 with the loadkeys ("man loadkeys") command.
29 You need at least one virtual terminal device in order to make use
30 of your keyboard and monitor. Therefore, only people configuring an
31 embedded system would want to say N here in order to save some
32 memory; the only way to log into such a system is then via a serial
33 or network connection.
35 If unsure, say Y, or else you won't be able to do much with your new
36 shiny Linux system :-)
38 config VT_CONSOLE
39 bool "Support for console on virtual terminal" if EMBEDDED
40 depends on VT
41 default y
42 ---help---
43 The system console is the device which receives all kernel messages
44 and warnings and which allows logins in single user mode. If you
45 answer Y here, a virtual terminal (the device used to interact with
46 a physical terminal) can be used as system console. This is the most
47 common mode of operations, so you should say Y here unless you want
48 the kernel messages be output only to a serial port (in which case
49 you should say Y to "Console on serial port", below).
51 If you do say Y here, by default the currently visible virtual
52 terminal (/dev/tty0) will be used as system console. You can change
53 that with a kernel command line option such as "console=tty3" which
54 would use the third virtual terminal as system console. (Try "man
55 bootparam" or see the documentation of your boot loader (lilo or
56 loadlin) about how to pass options to the kernel at boot time.)
58 If unsure, say Y.
60 config HW_CONSOLE
61 bool
62 depends on VT && !S390 && !UML
63 default y
65 config SERIAL_NONSTANDARD
66 bool "Non-standard serial port support"
67 ---help---
68 Say Y here if you have any non-standard serial boards -- boards
69 which aren't supported using the standard "dumb" serial driver.
70 This includes intelligent serial boards such as Cyclades,
71 Digiboards, etc. These are usually used for systems that need many
72 serial ports because they serve many terminals or dial-in
73 connections.
75 Note that the answer to this question won't directly affect the
76 kernel: saying N will just cause the configurator to skip all
77 the questions about non-standard serial boards.
79 Most people can say N here.
81 config COMPUTONE
82 tristate "Computone IntelliPort Plus serial support"
83 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
84 ---help---
85 This driver supports the entire family of Intelliport II/Plus
86 controllers with the exception of the MicroChannel controllers and
87 products previous to the Intelliport II. These are multiport cards,
88 which give you many serial ports. You would need something like this
89 to connect more than two modems to your Linux box, for instance in
90 order to become a dial-in server. If you have a card like that, say
91 Y here and read <file:Documentation/computone.txt>.
93 To compile this driver as modules, choose M here: the
94 modules will be called ip2 and ip2main.
96 config ROCKETPORT
97 tristate "Comtrol RocketPort support"
98 depends on SERIAL_NONSTANDARD
99 help
100 This driver supports Comtrol RocketPort and RocketModem PCI boards.
101 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
102 modems. For information about the RocketPort/RocketModem boards
103 and this driver read <file:Documentation/rocket.txt>.
105 To compile this driver as a module, choose M here: the
106 module will be called rocket.
108 If you want to compile this driver into the kernel, say Y here. If
109 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
111 config CYCLADES
112 tristate "Cyclades async mux support"
113 depends on SERIAL_NONSTANDARD
114 ---help---
115 This driver supports Cyclades Z and Y multiserial boards.
116 You would need something like this to connect more than two modems to
117 your Linux box, for instance in order to become a dial-in server.
119 For information about the Cyclades-Z card, read
120 <file:drivers/char/README.cycladesZ>.
122 To compile this driver as a module, choose M here: the
123 module will be called cyclades.
125 If you haven't heard about it, it's safe to say N.
127 config CYZ_INTR
128 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
129 depends on EXPERIMENTAL && CYCLADES
130 help
131 The Cyclades-Z family of multiport cards allows 2 (two) driver op
132 modes: polling and interrupt. In polling mode, the driver will check
133 the status of the Cyclades-Z ports every certain amount of time
134 (which is called polling cycle and is configurable). In interrupt
135 mode, it will use an interrupt line (IRQ) in order to check the
136 status of the Cyclades-Z ports. The default op mode is polling. If
137 unsure, say N.
139 config DIGIEPCA
140 tristate "Digiboard Intelligent Async Support"
141 depends on SERIAL_NONSTANDARD
142 ---help---
143 This is a driver for Digi International's Xx, Xeve, and Xem series
144 of cards which provide multiple serial ports. You would need
145 something like this to connect more than two modems to your Linux
146 box, for instance in order to become a dial-in server. This driver
147 supports the original PC (ISA) boards as well as PCI, and EISA. If
148 you have a card like this, say Y here and read the file
149 <file:Documentation/digiepca.txt>.
151 To compile this driver as a module, choose M here: the
152 module will be called epca.
154 config ESPSERIAL
155 tristate "Hayes ESP serial port support"
156 depends on SERIAL_NONSTANDARD && ISA && BROKEN_ON_SMP && ISA_DMA_API
157 help
158 This is a driver which supports Hayes ESP serial ports. Both single
159 port cards and multiport cards are supported. Make sure to read
160 <file:Documentation/hayes-esp.txt>.
162 To compile this driver as a module, choose M here: the
163 module will be called esp.
165 If unsure, say N.
167 config MOXA_INTELLIO
168 tristate "Moxa Intellio support"
169 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
170 help
171 Say Y here if you have a Moxa Intellio multiport serial card.
173 To compile this driver as a module, choose M here: the
174 module will be called moxa.
176 config MOXA_SMARTIO
177 tristate "Moxa SmartIO support"
178 depends on SERIAL_NONSTANDARD
179 help
180 Say Y here if you have a Moxa SmartIO multiport serial card.
182 This driver can also be built as a module ( = code which can be
183 inserted in and removed from the running kernel whenever you want).
184 The module will be called mxser. If you want to do that, say M
185 here.
187 config ISI
188 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
189 depends on SERIAL_NONSTANDARD
190 help
191 This is a driver for the Multi-Tech cards which provide several
192 serial ports. The driver is experimental and can currently only be
193 built as a module. The module will be called isicom.
194 If you want to do that, choose M here.
196 config SYNCLINK
197 tristate "Microgate SyncLink card support"
198 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
199 help
200 Provides support for the SyncLink ISA and PCI multiprotocol serial
201 adapters. These adapters support asynchronous and HDLC bit
202 synchronous communication up to 10Mbps (PCI adapter).
204 This driver can only be built as a module ( = code which can be
205 inserted in and removed from the running kernel whenever you want).
206 The module will be called synclink. If you want to do that, say M
207 here.
209 config SYNCLINKMP
210 tristate "SyncLink Multiport support"
211 depends on SERIAL_NONSTANDARD
212 help
213 Enable support for the SyncLink Multiport (2 or 4 ports)
214 serial adapter, running asynchronous and HDLC communications up
215 to 2.048Mbps. Each ports is independently selectable for
216 RS-232, V.35, RS-449, RS-530, and X.21
218 This driver may be built as a module ( = code which can be
219 inserted in and removed from the running kernel whenever you want).
220 The module will be called synclinkmp. If you want to do that, say M
221 here.
223 config SYNCLINK_GT
224 tristate "SyncLink GT/AC support"
225 depends on SERIAL_NONSTANDARD
226 help
227 Support for SyncLink GT and SyncLink AC families of
228 synchronous and asynchronous serial adapters
229 manufactured by Microgate Systems, Ltd. (www.microgate.com)
231 config N_HDLC
232 tristate "HDLC line discipline support"
233 depends on SERIAL_NONSTANDARD
234 help
235 Allows synchronous HDLC communications with tty device drivers that
236 support synchronous HDLC such as the Microgate SyncLink adapter.
238 This driver can only be built as a module ( = code which can be
239 inserted in and removed from the running kernel whenever you want).
240 The module will be called n_hdlc. If you want to do that, say M
241 here.
243 config RISCOM8
244 tristate "SDL RISCom/8 card support"
245 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
246 help
247 This is a driver for the SDL Communications RISCom/8 multiport card,
248 which gives you many serial ports. You would need something like
249 this to connect more than two modems to your Linux box, for instance
250 in order to become a dial-in server. If you have a card like that,
251 say Y here and read the file <file:Documentation/riscom8.txt>.
253 Also it's possible to say M here and compile this driver as kernel
254 loadable module; the module will be called riscom8.
256 config SPECIALIX
257 tristate "Specialix IO8+ card support"
258 depends on SERIAL_NONSTANDARD
259 help
260 This is a driver for the Specialix IO8+ multiport card (both the
261 ISA and the PCI version) which gives you many serial ports. You
262 would need something like this to connect more than two modems to
263 your Linux box, for instance in order to become a dial-in server.
265 If you have a card like that, say Y here and read the file
266 <file:Documentation/specialix.txt>. Also it's possible to say M here
267 and compile this driver as kernel loadable module which will be
268 called specialix.
270 config SPECIALIX_RTSCTS
271 bool "Specialix DTR/RTS pin is RTS"
272 depends on SPECIALIX
273 help
274 The Specialix IO8+ card can only support either RTS or DTR. If you
275 say N here, the driver will use the pin as "DTR" when the tty is in
276 software handshake mode. If you say Y here or hardware handshake is
277 on, it will always be RTS. Read the file
278 <file:Documentation/specialix.txt> for more information.
280 config SX
281 tristate "Specialix SX (and SI) card support"
282 depends on SERIAL_NONSTANDARD
283 help
284 This is a driver for the SX and SI multiport serial cards.
285 Please read the file <file:Documentation/sx.txt> for details.
287 This driver can only be built as a module ( = code which can be
288 inserted in and removed from the running kernel whenever you want).
289 The module will be called sx. If you want to do that, say M here.
291 config RIO
292 tristate "Specialix RIO system support"
293 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
294 help
295 This is a driver for the Specialix RIO, a smart serial card which
296 drives an outboard box that can support up to 128 ports. Product
297 information is at <http://www.perle.com/support/documentation.html#multiport>.
298 There are both ISA and PCI versions.
300 config RIO_OLDPCI
301 bool "Support really old RIO/PCI cards"
302 depends on RIO
303 help
304 Older RIO PCI cards need some initialization-time configuration to
305 determine the IRQ and some control addresses. If you have a RIO and
306 this doesn't seem to work, try setting this to Y.
308 config STALDRV
309 bool "Stallion multiport serial support"
310 depends on SERIAL_NONSTANDARD
311 help
312 Stallion cards give you many serial ports. You would need something
313 like this to connect more than two modems to your Linux box, for
314 instance in order to become a dial-in server. If you say Y here,
315 you will be asked for your specific card model in the next
316 questions. Make sure to read <file:Documentation/stallion.txt> in
317 this case. If you have never heard about all this, it's safe to
318 say N.
320 config STALLION
321 tristate "Stallion EasyIO or EC8/32 support"
322 depends on STALDRV && BROKEN_ON_SMP
323 help
324 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
325 card, then this is for you; say Y. Make sure to read
326 <file:Documentation/stallion.txt>.
328 To compile this driver as a module, choose M here: the
329 module will be called stallion.
331 config ISTALLION
332 tristate "Stallion EC8/64, ONboard, Brumby support"
333 depends on STALDRV && BROKEN_ON_SMP
334 help
335 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
336 serial multiport card, say Y here. Make sure to read
337 <file:Documentation/stallion.txt>.
339 To compile this driver as a module, choose M here: the
340 module will be called istallion.
342 config AU1000_UART
343 bool "Enable Au1000 UART Support"
344 depends on SERIAL_NONSTANDARD && MIPS
345 help
346 If you have an Alchemy AU1000 processor (MIPS based) and you want
347 to use serial ports, say Y. Otherwise, say N.
349 config AU1000_SERIAL_CONSOLE
350 bool "Enable Au1000 serial console"
351 depends on AU1000_UART
352 help
353 If you have an Alchemy AU1000 processor (MIPS based) and you want
354 to use a console on a serial port, say Y. Otherwise, say N.
356 config QTRONIX_KEYBOARD
357 bool "Enable Qtronix 990P Keyboard Support"
358 depends on IT8712
359 help
360 Images of Qtronix keyboards are at
361 <http://www.qtronix.com/keyboard.html>.
363 config IT8172_CIR
364 bool
365 depends on QTRONIX_KEYBOARD
366 default y
368 config IT8172_SCR0
369 bool "Enable Smart Card Reader 0 Support "
370 depends on IT8712
371 help
372 Say Y here to support smart-card reader 0 (SCR0) on the Integrated
373 Technology Express, Inc. ITE8172 SBC. Vendor page at
374 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
375 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
377 config IT8172_SCR1
378 bool "Enable Smart Card Reader 1 Support "
379 depends on IT8712
380 help
381 Say Y here to support smart-card reader 1 (SCR1) on the Integrated
382 Technology Express, Inc. ITE8172 SBC. Vendor page at
383 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
384 board at <http://www.mvista.com/partners/semiconductor/ite.html>.
386 config A2232
387 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
388 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
389 ---help---
390 This option supports the 2232 7-port serial card shipped with the
391 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
392 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
393 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
394 ports were connected with 8 pin DIN connectors on the card bracket,
395 for which 8 pin to DB25 adapters were supplied. The card also had
396 jumpers internally to toggle various pinning configurations.
398 This driver can be built as a module; but then "generic_serial"
399 will also be built as a module. This has to be loaded before
400 "ser_a2232". If you want to do this, answer M here.
402 config SGI_SNSC
403 bool "SGI Altix system controller communication support"
404 depends on (IA64_SGI_SN2 || IA64_GENERIC)
405 help
406 If you have an SGI Altix and you want to enable system
407 controller communication from user space (you want this!),
408 say Y. Otherwise, say N.
410 config SGI_TIOCX
411 bool "SGI TIO CX driver support"
412 depends on (IA64_SGI_SN2 || IA64_GENERIC)
413 help
414 If you have an SGI Altix and you have fpga devices attached
415 to your TIO, say Y here, otherwise say N.
417 config SGI_MBCS
418 tristate "SGI FPGA Core Services driver support"
419 depends on SGI_TIOCX
420 help
421 If you have an SGI Altix with an attached SABrick
422 say Y or M here, otherwise say N.
424 source "drivers/serial/Kconfig"
426 config UNIX98_PTYS
427 bool "Unix98 PTY support" if EMBEDDED
428 default y
429 ---help---
430 A pseudo terminal (PTY) is a software device consisting of two
431 halves: a master and a slave. The slave device behaves identical to
432 a physical terminal; the master device is used by a process to
433 read data from and write data to the slave, thereby emulating a
434 terminal. Typical programs for the master side are telnet servers
435 and xterms.
437 Linux has traditionally used the BSD-like names /dev/ptyxx for
438 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
439 has a number of problems. The GNU C library glibc 2.1 and later,
440 however, supports the Unix98 naming standard: in order to acquire a
441 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
442 terminal is then made available to the process and the pseudo
443 terminal slave can be accessed as /dev/pts/<number>. What was
444 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
446 All modern Linux systems use the Unix98 ptys. Say Y unless
447 you're on an embedded system and want to conserve memory.
449 config LEGACY_PTYS
450 bool "Legacy (BSD) PTY support"
451 default y
452 ---help---
453 A pseudo terminal (PTY) is a software device consisting of two
454 halves: a master and a slave. The slave device behaves identical to
455 a physical terminal; the master device is used by a process to
456 read data from and write data to the slave, thereby emulating a
457 terminal. Typical programs for the master side are telnet servers
458 and xterms.
460 Linux has traditionally used the BSD-like names /dev/ptyxx
461 for masters and /dev/ttyxx for slaves of pseudo
462 terminals. This scheme has a number of problems, including
463 security. This option enables these legacy devices; on most
464 systems, it is safe to say N.
467 config LEGACY_PTY_COUNT
468 int "Maximum number of legacy PTY in use"
469 depends on LEGACY_PTYS
470 range 1 256
471 default "256"
472 ---help---
473 The maximum number of legacy PTYs that can be used at any one time.
474 The default is 256, and should be more than enough. Embedded
475 systems may want to reduce this to save memory.
477 When not in use, each legacy PTY occupies 12 bytes on 32-bit
478 architectures and 24 bytes on 64-bit architectures.
480 config PRINTER
481 tristate "Parallel printer support"
482 depends on PARPORT
483 ---help---
484 If you intend to attach a printer to the parallel port of your Linux
485 box (as opposed to using a serial printer; if the connector at the
486 printer has 9 or 25 holes ["female"], then it's serial), say Y.
487 Also read the Printing-HOWTO, available from
488 <http://www.tldp.org/docs.html#howto>.
490 It is possible to share one parallel port among several devices
491 (e.g. printer and ZIP drive) and it is safe to compile the
492 corresponding drivers into the kernel.
494 To compile this driver as a module, choose M here and read
495 <file:Documentation/parport.txt>. The module will be called lp.
497 If you have several parallel ports, you can specify which ports to
498 use with the "lp" kernel command line option. (Try "man bootparam"
499 or see the documentation of your boot loader (lilo or loadlin) about
500 how to pass options to the kernel at boot time.) The syntax of the
501 "lp" command line option can be found in <file:drivers/char/lp.c>.
503 If you have more than 8 printers, you need to increase the LP_NO
504 macro in lp.c and the PARPORT_MAX macro in parport.h.
506 config LP_CONSOLE
507 bool "Support for console on line printer"
508 depends on PRINTER
509 ---help---
510 If you want kernel messages to be printed out as they occur, you
511 can have a console on the printer. This option adds support for
512 doing that; to actually get it to happen you need to pass the
513 option "console=lp0" to the kernel at boot time.
515 If the printer is out of paper (or off, or unplugged, or too
516 busy..) the kernel will stall until the printer is ready again.
517 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
518 can make the kernel continue when this happens,
519 but it'll lose the kernel messages.
521 If unsure, say N.
523 config PPDEV
524 tristate "Support for user-space parallel port device drivers"
525 depends on PARPORT
526 ---help---
527 Saying Y to this adds support for /dev/parport device nodes. This
528 is needed for programs that want portable access to the parallel
529 port, for instance deviceid (which displays Plug-and-Play device
530 IDs).
532 This is the parallel port equivalent of SCSI generic support (sg).
533 It is safe to say N to this -- it is not needed for normal printing
534 or parallel port CD-ROM/disk support.
536 To compile this driver as a module, choose M here: the
537 module will be called ppdev.
539 If unsure, say N.
541 config TIPAR
542 tristate "Texas Instruments parallel link cable support"
543 depends on PARPORT
544 ---help---
545 If you own a Texas Instruments graphing calculator and use a
546 parallel link cable, then you might be interested in this driver.
548 If you enable this driver, you will be able to communicate with
549 your calculator through a set of device nodes under /dev. The
550 main advantage of this driver is that you don't have to be root
551 to use this precise link cable (depending on the permissions on
552 the device nodes, though).
554 To compile this driver as a module, choose M here: the
555 module will be called tipar.
557 If you don't know what a parallel link cable is or what a Texas
558 Instruments graphing calculator is, then you probably don't need this
559 driver.
561 If unsure, say N.
563 config HVC_CONSOLE
564 bool "pSeries Hypervisor Virtual Console support"
565 depends on PPC_PSERIES
566 help
567 pSeries machines when partitioned support a hypervisor virtual
568 console. This driver allows each pSeries partition to have a console
569 which is accessed via the HMC.
571 config HVCS
572 tristate "IBM Hypervisor Virtual Console Server support"
573 depends on PPC_PSERIES
574 help
575 Partitionable IBM Power5 ppc64 machines allow hosting of
576 firmware virtual consoles from one Linux partition by
577 another Linux partition. This driver allows console data
578 from Linux partitions to be accessed through TTY device
579 interfaces in the device tree of a Linux partition running
580 this driver.
582 To compile this driver as a module, choose M here: the
583 module will be called hvcs.ko. Additionally, this module
584 will depend on arch specific APIs exported from hvcserver.ko
585 which will also be compiled when this driver is built as a
586 module.
588 source "drivers/char/ipmi/Kconfig"
590 source "drivers/char/watchdog/Kconfig"
592 config DS1620
593 tristate "NetWinder thermometer support"
594 depends on ARCH_NETWINDER
595 help
596 Say Y here to include support for the thermal management hardware
597 found in the NetWinder. This driver allows the user to control the
598 temperature set points and to read the current temperature.
600 It is also possible to say M here to build it as a module (ds1620)
601 It is recommended to be used on a NetWinder, but it is not a
602 necessity.
604 config NWBUTTON
605 tristate "NetWinder Button"
606 depends on ARCH_NETWINDER
607 ---help---
608 If you say Y here and create a character device node /dev/nwbutton
609 with major and minor numbers 10 and 158 ("man mknod"), then every
610 time the orange button is pressed a number of times, the number of
611 times the button was pressed will be written to that device.
613 This is most useful for applications, as yet unwritten, which
614 perform actions based on how many times the button is pressed in a
615 row.
617 Do not hold the button down for too long, as the driver does not
618 alter the behaviour of the hardware reset circuitry attached to the
619 button; it will still execute a hard reset if the button is held
620 down for longer than approximately five seconds.
622 To compile this driver as a module, choose M here: the
623 module will be called nwbutton.
625 Most people will answer Y to this question and "Reboot Using Button"
626 below to be able to initiate a system shutdown from the button.
628 config NWBUTTON_REBOOT
629 bool "Reboot Using Button"
630 depends on NWBUTTON
631 help
632 If you say Y here, then you will be able to initiate a system
633 shutdown and reboot by pressing the orange button a number of times.
634 The number of presses to initiate the shutdown is two by default,
635 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
636 in nwbutton.h and recompiling the driver or, if you compile the
637 driver as a module, you can specify the number of presses at load
638 time with "insmod button reboot_count=<something>".
640 config NWFLASH
641 tristate "NetWinder flash support"
642 depends on ARCH_NETWINDER
643 ---help---
644 If you say Y here and create a character device /dev/flash with
645 major 10 and minor 160 you can manipulate the flash ROM containing
646 the NetWinder firmware. Be careful as accidentally overwriting the
647 flash contents can render your computer unbootable. On no account
648 allow random users access to this device. :-)
650 To compile this driver as a module, choose M here: the
651 module will be called nwflash.
653 If you're not sure, say N.
655 config HW_RANDOM
656 tristate "Intel/AMD/VIA HW Random Number Generator support"
657 depends on (X86 || IA64) && PCI
658 ---help---
659 This driver provides kernel-side support for the Random Number
660 Generator hardware found on Intel i8xx-based motherboards,
661 AMD 76x-based motherboards, and Via Nehemiah CPUs.
663 Provides a character driver, used to read() entropy data.
665 To compile this driver as a module, choose M here: the
666 module will be called hw_random.
668 If unsure, say N.
670 config NVRAM
671 tristate "/dev/nvram support"
672 depends on ATARI || X86 || ARM || GENERIC_NVRAM
673 ---help---
674 If you say Y here and create a character special file /dev/nvram
675 with major number 10 and minor number 144 using mknod ("man mknod"),
676 you get read and write access to the extra bytes of non-volatile
677 memory in the real time clock (RTC), which is contained in every PC
678 and most Ataris. The actual number of bytes varies, depending on the
679 nvram in the system, but is usually 114 (128-14 for the RTC).
681 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
682 on Ataris. /dev/nvram may be used to view settings there, or to
683 change them (with some utility). It could also be used to frequently
684 save a few bits of very important data that may not be lost over
685 power-off and for which writing to disk is too insecure. Note
686 however that most NVRAM space in a PC belongs to the BIOS and you
687 should NEVER idly tamper with it. See Ralf Brown's interrupt list
688 for a guide to the use of CMOS bytes by your BIOS.
690 On Atari machines, /dev/nvram is always configured and does not need
691 to be selected.
693 To compile this driver as a module, choose M here: the
694 module will be called nvram.
696 config RTC
697 tristate "Enhanced Real Time Clock Support"
698 depends on !PPC32 && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV
699 ---help---
700 If you say Y here and create a character special file /dev/rtc with
701 major number 10 and minor number 135 using mknod ("man mknod"), you
702 will get access to the real time clock (or hardware clock) built
703 into your computer.
705 Every PC has such a clock built in. It can be used to generate
706 signals from as low as 1Hz up to 8192Hz, and can also be used
707 as a 24 hour alarm. It reports status information via the file
708 /proc/driver/rtc and its behaviour is set by various ioctls on
709 /dev/rtc.
711 If you run Linux on a multiprocessor machine and said Y to
712 "Symmetric Multi Processing" above, you should say Y here to read
713 and set the RTC in an SMP compatible fashion.
715 If you think you have a use for such a device (such as periodic data
716 sampling), then say Y here, and read <file:Documentation/rtc.txt>
717 for details.
719 To compile this driver as a module, choose M here: the
720 module will be called rtc.
722 config SGI_DS1286
723 tristate "SGI DS1286 RTC support"
724 depends on SGI_IP22
725 help
726 If you say Y here and create a character special file /dev/rtc with
727 major number 10 and minor number 135 using mknod ("man mknod"), you
728 will get access to the real time clock built into your computer.
729 Every SGI has such a clock built in. It reports status information
730 via the file /proc/rtc and its behaviour is set by various ioctls on
731 /dev/rtc.
733 config SGI_IP27_RTC
734 bool "SGI M48T35 RTC support"
735 depends on SGI_IP27
736 help
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 built into your computer.
740 Every SGI has such a clock built in. It reports status information
741 via the file /proc/rtc and its behaviour is set by various ioctls on
742 /dev/rtc.
744 config GEN_RTC
745 tristate "Generic /dev/rtc emulation"
746 depends on RTC!=y && !IA64 && !ARM && !M32R && !SPARC && !FRV
747 ---help---
748 If you say Y here and create a character special file /dev/rtc with
749 major number 10 and minor number 135 using mknod ("man mknod"), you
750 will get access to the real time clock (or hardware clock) built
751 into your computer.
753 It reports status information via the file /proc/driver/rtc and its
754 behaviour is set by various ioctls on /dev/rtc. If you enable the
755 "extended RTC operation" below it will also provide an emulation
756 for RTC_UIE which is required by some programs and may improve
757 precision in some cases.
759 To compile this driver as a module, choose M here: the
760 module will be called genrtc.
762 config GEN_RTC_X
763 bool "Extended RTC operation"
764 depends on GEN_RTC
765 help
766 Provides an emulation for RTC_UIE which is required by some programs
767 and may improve precision of the generic RTC support in some cases.
769 config EFI_RTC
770 bool "EFI Real Time Clock Services"
771 depends on IA64
773 config DS1302
774 tristate "DS1302 RTC support"
775 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
776 help
777 If you say Y here and create a character special file /dev/rtc with
778 major number 121 and minor number 0 using mknod ("man mknod"), you
779 will get access to the real time clock (or hardware clock) built
780 into your computer.
782 config S3C2410_RTC
783 bool "S3C2410 RTC Driver"
784 depends on ARCH_S3C2410
785 help
786 RTC (Realtime Clock) driver for the clock inbuilt into the
787 Samsung S3C2410. This can provide periodic interrupt rates
788 from 1Hz to 64Hz for user programs, and wakeup from Alarm.
790 config RTC_VR41XX
791 tristate "NEC VR4100 series Real Time Clock Support"
792 depends on CPU_VR41XX
794 config COBALT_LCD
795 bool "Support for Cobalt LCD"
796 depends on MIPS_COBALT
797 help
798 This option enables support for the LCD display and buttons found
799 on Cobalt systems through a misc device.
801 config DTLK
802 tristate "Double Talk PC internal speech card support"
803 help
804 This driver is for the DoubleTalk PC, a speech synthesizer
805 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
806 called the `internal DoubleTalk'.
808 To compile this driver as a module, choose M here: the
809 module will be called dtlk.
811 config R3964
812 tristate "Siemens R3964 line discipline"
813 ---help---
814 This driver allows synchronous communication with devices using the
815 Siemens R3964 packet protocol. Unless you are dealing with special
816 hardware like PLCs, you are unlikely to need this.
818 To compile this driver as a module, choose M here: the
819 module will be called n_r3964.
821 If unsure, say N.
823 config APPLICOM
824 tristate "Applicom intelligent fieldbus card support"
825 depends on PCI
826 ---help---
827 This driver provides the kernel-side support for the intelligent
828 fieldbus cards made by Applicom International. More information
829 about these cards can be found on the WWW at the address
830 <http://www.applicom-int.com/>, or by email from David Woodhouse
831 <dwmw2@infradead.org>.
833 To compile this driver as a module, choose M here: the
834 module will be called applicom.
836 If unsure, say N.
838 config SONYPI
839 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
840 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
841 ---help---
842 This driver enables access to the Sony Programmable I/O Control
843 Device which can be found in many (all ?) Sony Vaio laptops.
845 If you have one of those laptops, read
846 <file:Documentation/sonypi.txt>, and say Y or M here.
848 To compile this driver as a module, choose M here: the
849 module will be called sonypi.
851 config TANBAC_TB0219
852 tristate "TANBAC TB0219 base board support"
853 depends TANBAC_TB022X
855 menu "Ftape, the floppy tape device driver"
857 config FTAPE
858 tristate "Ftape (QIC-80/Travan) support"
859 depends on BROKEN_ON_SMP && (ALPHA || X86)
860 ---help---
861 If you have a tape drive that is connected to your floppy
862 controller, say Y here.
864 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
865 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
866 controller of their own. These drives (and their companion
867 controllers) are also supported if you say Y here.
869 If you have a special controller (such as the CMS FC-10, FC-20,
870 Mountain Mach-II, or any controller that is based on the Intel 82078
871 FDC like the high speed controllers by Seagate and Exabyte and
872 Iomega's "Ditto Dash") you must configure it by selecting the
873 appropriate entries from the "Floppy tape controllers" sub-menu
874 below and possibly modify the default values for the IRQ and DMA
875 channel and the IO base in ftape's configuration menu.
877 If you want to use your floppy tape drive on a PCI-bus based system,
878 please read the file <file:drivers/char/ftape/README.PCI>.
880 The ftape kernel driver is also available as a runtime loadable
881 module. To compile this driver as a module, choose M here: the
882 module will be called ftape.
884 Note that the Ftape-HOWTO is out of date (sorry) and documents the
885 older version 2.08 of this software but still contains useful
886 information. There is a web page with more recent documentation at
887 <http://www.instmath.rwth-aachen.de/~heine/ftape/>. This page
888 always contains the latest release of the ftape driver and useful
889 information (backup software, ftape related patches and
890 documentation, FAQ). Note that the file system interface has
891 changed quite a bit compared to previous versions of ftape. Please
892 read <file:Documentation/ftape.txt>.
894 source "drivers/char/ftape/Kconfig"
896 endmenu
898 source "drivers/char/agp/Kconfig"
900 source "drivers/char/drm/Kconfig"
902 source "drivers/char/pcmcia/Kconfig"
904 config MWAVE
905 tristate "ACP Modem (Mwave) support"
906 depends on X86
907 select SERIAL_8250
908 ---help---
909 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
910 kernel driver and a user level application. Together these components
911 support direct attachment to public switched telephone networks (PSTNs)
912 and support selected world wide countries.
914 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
915 600, and 770 that include on board ACP modem hardware.
917 The modem also supports the standard communications port interface
918 (ttySx) and is compatible with the Hayes AT Command Set.
920 The user level application needed to use this driver can be found at
921 the IBM Linux Technology Center (LTC) web site:
922 <http://www.ibm.com/linux/ltc/>.
924 If you own one of the above IBM Thinkpads which has the Mwave chipset
925 in it, say Y.
927 To compile this driver as a module, choose M here: the
928 module will be called mwave.
930 config SCx200_GPIO
931 tristate "NatSemi SCx200 GPIO Support"
932 depends on SCx200
933 help
934 Give userspace access to the GPIO pins on the National
935 Semiconductor SCx200 processors.
937 If compiled as a module, it will be called scx200_gpio.
939 config GPIO_VR41XX
940 tristate "NEC VR4100 series General-purpose I/O Unit support"
941 depends on CPU_VR41XX
943 config RAW_DRIVER
944 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
945 help
946 The raw driver permits block devices to be bound to /dev/raw/rawN.
947 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
948 See the raw(8) manpage for more details.
950 The raw driver is deprecated and will be removed soon.
951 Applications should simply open the device (eg /dev/hda1)
952 with the O_DIRECT flag.
954 config MAX_RAW_DEVS
955 int "Maximum number of RAW devices to support (1-8192)"
956 depends on RAW_DRIVER
957 default "256"
958 help
959 The maximum number of RAW devices that are supported.
960 Default is 256. Increase this number in case you need lots of
961 raw devices.
963 config HPET
964 bool "HPET - High Precision Event Timer" if (X86 || IA64)
965 default n
966 depends on ACPI
967 help
968 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
969 open selects one of the timers supported by the HPET. The timers are
970 non-periodioc and/or periodic.
972 config HPET_RTC_IRQ
973 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
974 default n
975 depends on HPET
976 help
977 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
978 is assumed the platform called hpet_alloc with the RTC IRQ values for
979 the HPET timers.
981 config HPET_MMAP
982 bool "Allow mmap of HPET"
983 default y
984 depends on HPET
985 help
986 If you say Y here, user applications will be able to mmap
987 the HPET registers.
989 In some hardware implementations, the page containing HPET
990 registers may also contain other things that shouldn't be
991 exposed to the user. If this applies to your hardware,
992 say N here.
994 config HANGCHECK_TIMER
995 tristate "Hangcheck timer"
996 depends on X86 || IA64 || PPC64 || S390
997 help
998 The hangcheck-timer module detects when the system has gone
999 out to lunch past a certain margin. It can reboot the system
1000 or merely print a warning.
1002 config MMTIMER
1003 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1004 depends on IA64_GENERIC || IA64_SGI_SN2
1005 default y
1006 help
1007 The mmtimer device allows direct userspace access to the
1008 Altix system timer.
1010 source "drivers/char/tpm/Kconfig"
1012 config TELCLOCK
1013 tristate "Telecom clock driver for MPBL0010 ATCA SBC"
1014 depends on EXPERIMENTAL
1015 default n
1016 help
1017 The telecom clock device is specific to the MPBL0010 ATCA computer and
1018 allows direct userspace access to the configuration of the telecom clock
1019 configuration settings. This device is used for hardware synchronization
1020 across the ATCA backplane fabric. Upon loading, the driver exports a
1021 sysfs directory, /sys/devices/platform/telco_clock, with a number of
1022 files for controlling the behavior of this hardware.
1024 endmenu