2 # Character device configuration
5 menu "Character devices"
8 bool "Virtual terminal" if EMBEDDED
12 If you say Y here, you will get support for terminal devices with
13 display and keyboard devices. These are called "virtual" because you
14 can run several virtual terminals (also called virtual consoles) on
15 one physical terminal. This is rather useful, for example one
16 virtual terminal can collect system messages and warnings, another
17 one can be used for a text-mode user session, and a third could run
18 an X session, all in parallel. Switching between virtual terminals
19 is done with certain key combinations, usually Alt-<function key>.
21 The setterm command ("man setterm") can be used to change the
22 properties (such as colors or beeping) of a virtual terminal. The
23 man page console_codes(4) ("man console_codes") contains the special
24 character sequences that can be used to change those properties
25 directly. The fonts used on virtual terminals can be changed with
26 the setfont ("man setfont") command and the key bindings are defined
27 with the loadkeys ("man loadkeys") command.
29 You need at least one virtual terminal device in order to make use
30 of your keyboard and monitor. Therefore, only people configuring an
31 embedded system would want to say N here in order to save some
32 memory; the only way to log into such a system is then via a serial
33 or network connection.
35 If unsure, say Y, or else you won't be able to do much with your new
36 shiny Linux system :-)
39 bool "Support for console on virtual terminal" if EMBEDDED
43 The system console is the device which receives all kernel messages
44 and warnings and which allows logins in single user mode. If you
45 answer Y here, a virtual terminal (the device used to interact with
46 a physical terminal) can be used as system console. This is the most
47 common mode of operations, so you should say Y here unless you want
48 the kernel messages be output only to a serial port (in which case
49 you should say Y to "Console on serial port", below).
51 If you do say Y here, by default the currently visible virtual
52 terminal (/dev/tty0) will be used as system console. You can change
53 that with a kernel command line option such as "console=tty3" which
54 would use the third virtual terminal as system console. (Try "man
55 bootparam" or see the documentation of your boot loader (lilo or
56 loadlin) about how to pass options to the kernel at boot time.)
62 depends on VT && !S390 && !UM
65 config SERIAL_NONSTANDARD
66 bool "Non-standard serial port support"
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
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.
82 tristate "Computone IntelliPort Plus serial support"
83 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
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.
97 tristate "Comtrol RocketPort support"
98 depends on SERIAL_NONSTANDARD
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.
112 tristate "Cyclades async mux support"
113 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
115 This is a driver for a card that gives you many serial ports. You
116 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.
118 For information about the Cyclades-Z card, read
119 <file:drivers/char/README.cycladesZ>.
121 As of 1.3.9x kernels, this driver's minor numbers start at 0 instead
124 To compile this driver as a module, choose M here: the
125 module will be called cyclades.
127 If you haven't heard about it, it's safe to say N.
130 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
131 depends on EXPERIMENTAL && CYCLADES
133 The Cyclades-Z family of multiport cards allows 2 (two) driver op
134 modes: polling and interrupt. In polling mode, the driver will check
135 the status of the Cyclades-Z ports every certain amount of time
136 (which is called polling cycle and is configurable). In interrupt
137 mode, it will use an interrupt line (IRQ) in order to check the
138 status of the Cyclades-Z ports. The default op mode is polling. If
142 tristate "Digiboard Intelligent Async Support"
143 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
145 This is a driver for Digi International's Xx, Xeve, and Xem series
146 of cards which provide multiple serial ports. You would need
147 something like this to connect more than two modems to your Linux
148 box, for instance in order to become a dial-in server. This driver
149 supports the original PC (ISA) boards as well as PCI, and EISA. If
150 you have a card like this, say Y here and read the file
151 <file:Documentation/digiepca.txt>.
153 NOTE: There is another, separate driver for the Digiboard PC boards:
154 "Digiboard PC/Xx Support" below. You should (and can) only select
155 one of the two drivers.
157 To compile this driver as a module, choose M here: the
158 module will be called epca.
161 tristate "Digiboard PC/Xx Support"
162 depends on SERIAL_NONSTANDARD && DIGIEPCA=n && BROKEN_ON_SMP
164 This is a driver for the Digiboard PC/Xe, PC/Xi, and PC/Xeve cards
165 that give you many serial ports. You would need something like this
166 to connect more than two modems to your Linux box, for instance in
167 order to become a dial-in server. If you have a card like that, say
168 Y here and read the file <file:Documentation/digiboard.txt>.
170 To compile this driver as a module, choose M here: the
171 module will be called pcxx.
174 tristate "Hayes ESP serial port support"
175 depends on SERIAL_NONSTANDARD && ISA && BROKEN_ON_SMP
177 This is a driver which supports Hayes ESP serial ports. Both single
178 port cards and multiport cards are supported. Make sure to read
179 <file:Documentation/hayes-esp.txt>.
181 To compile this driver as a module, choose M here: the
182 module will be called esp.
187 tristate "Moxa Intellio support"
188 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
190 Say Y here if you have a Moxa Intellio multiport serial card.
192 To compile this driver as a module, choose M here: the
193 module will be called moxa.
196 tristate "Moxa SmartIO support"
197 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
199 Say Y here if you have a Moxa SmartIO multiport serial card.
201 This driver can also be built as a module ( = code which can be
202 inserted in and removed from the running kernel whenever you want).
203 The module will be called mxser. If you want to do that, say M
207 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
208 depends on SERIAL_NONSTANDARD && EXPERIMENTAL && BROKEN_ON_SMP && m
210 This is a driver for the Multi-Tech cards which provide several
211 serial ports. The driver is experimental and can currently only be
212 built as a module. The module will be called isicom.
213 If you want to do that, choose M here.
216 tristate "Microgate SyncLink card support"
217 depends on SERIAL_NONSTANDARD
219 Provides support for the SyncLink ISA and PCI multiprotocol serial
220 adapters. These adapters support asynchronous and HDLC bit
221 synchronous communication up to 10Mbps (PCI adapter).
223 This driver can only be built as a module ( = code which can be
224 inserted in and removed from the running kernel whenever you want).
225 The module will be called synclink. If you want to do that, say M
229 tristate "SyncLink Multiport support"
230 depends on SERIAL_NONSTANDARD
232 Enable support for the SyncLink Multiport (2 or 4 ports)
233 serial adapter, running asynchronous and HDLC communications up
234 to 2.048Mbps. Each ports is independently selectable for
235 RS-232, V.35, RS-449, RS-530, and X.21
237 This driver may be built as a module ( = code which can be
238 inserted in and removed from the running kernel whenever you want).
239 The module will be called synclinkmp. If you want to do that, say M
243 tristate "HDLC line discipline support"
244 depends on SERIAL_NONSTANDARD
246 Allows synchronous HDLC communications with tty device drivers that
247 support synchronous HDLC such as the Microgate SyncLink adapter.
249 This driver can only be built as a module ( = code which can be
250 inserted in and removed from the running kernel whenever you want).
251 The module will be called n_hdlc. If you want to do that, say M
255 tristate "SDL RISCom/8 card support"
256 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
258 This is a driver for the SDL Communications RISCom/8 multiport card,
259 which gives you many serial ports. You would need something like
260 this to connect more than two modems to your Linux box, for instance
261 in order to become a dial-in server. If you have a card like that,
262 say Y here and read the file <file:Documentation/riscom8.txt>.
264 Also it's possible to say M here and compile this driver as kernel
265 loadable module; the module will be called riscom8.
268 tristate "Specialix IO8+ card support"
269 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
271 This is a driver for the Specialix IO8+ multiport card (both the
272 ISA and the PCI version) which gives you many serial ports. You
273 would need something like this to connect more than two modems to
274 your Linux box, for instance in order to become a dial-in server.
276 If you have a card like that, say Y here and read the file
277 <file:Documentation/specialix.txt>. Also it's possible to say M here
278 and compile this driver as kernel loadable module which will be
281 config SPECIALIX_RTSCTS
282 bool "Specialix DTR/RTS pin is RTS"
285 The Specialix IO8+ card can only support either RTS or DTR. If you
286 say N here, the driver will use the pin as "DTR" when the tty is in
287 software handshake mode. If you say Y here or hardware handshake is
288 on, it will always be RTS. Read the file
289 <file:Documentation/specialix.txt> for more information.
292 tristate "Specialix SX (and SI) card support"
293 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
295 This is a driver for the SX and SI multiport serial cards.
296 Please read the file <file:Documentation/sx.txt> for details.
298 This driver can only be built as a module ( = code which can be
299 inserted in and removed from the running kernel whenever you want).
300 The module will be called sx. If you want to do that, say M here.
303 tristate "Specialix RIO system support"
304 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
306 This is a driver for the Specialix RIO, a smart serial card which
307 drives an outboard box that can support up to 128 ports. Product
308 information is at <http://www.sphinxcst.co.uk/perle/multi.htm>.
309 There are both ISA and PCI versions.
312 bool "Support really old RIO/PCI cards"
315 Older RIO PCI cards need some initialization-time configuration to
316 determine the IRQ and some control addresses. If you have a RIO and
317 this doesn't seem to work, try setting this to Y.
320 bool "Stallion multiport serial support"
321 depends on SERIAL_NONSTANDARD
323 Stallion cards give you many serial ports. You would need something
324 like this to connect more than two modems to your Linux box, for
325 instance in order to become a dial-in server. If you say Y here,
326 you will be asked for your specific card model in the next
327 questions. Make sure to read <file:Documentation/stallion.txt> in
328 this case. If you have never heard about all this, it's safe to
332 tristate "Stallion EasyIO or EC8/32 support"
333 depends on STALDRV && BROKEN_ON_SMP
335 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
336 card, then this is for you; say Y. 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 stallion.
343 tristate "Stallion EC8/64, ONboard, Brumby support"
344 depends on STALDRV && BROKEN_ON_SMP
346 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
347 serial multiport card, say Y here. Make sure to read
348 <file:Documentation/stallion.txt>.
350 To compile this driver as a module, choose M here: the
351 module will be called istallion.
354 bool "TMPTX3912/PR31700 serial port support"
355 depends on SERIAL_NONSTANDARD && MIPS && BROKEN_ON_SMP
357 The TX3912 is a Toshiba RISC processor based o the MIPS 3900 core;
358 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
359 Say Y here to enable kernel support for the on-board serial port.
361 config SERIAL_TX3912_CONSOLE
362 bool "Console on TMPTX3912/PR31700 serial port"
363 depends on SERIAL_TX3912
365 The TX3912 is a Toshiba RISC processor based o the MIPS 3900 core;
366 see <http://www.toshiba.com/taec/components/Generic/risc/tx3912.htm>.
367 Say Y here to direct console I/O to the on-board serial port.
370 bool "Enable Au1000 UART Support"
371 depends on SERIAL_NONSTANDARD && MIPS
373 If you have an Alchemy AU1000 processor (MIPS based) and you want
374 to use serial ports, say Y. Otherwise, say N.
377 bool "SGI Altix L1 serial support"
378 depends on SERIAL_NONSTANDARD && IA64
380 If you have an SGI Altix and you want to use the serial port
381 connected to the system controller (you want this!), say Y.
384 config SGI_L1_SERIAL_CONSOLE
385 bool "SGI Altix L1 serial console support"
386 depends on SGI_L1_SERIAL
388 If you have an SGI Altix and you would like to use the system
389 controller serial port as your console (you want this!),
390 say Y. Otherwise, say N.
392 config AU1000_SERIAL_CONSOLE
393 bool "Enable Au1000 serial console"
394 depends on AU1000_UART
396 If you have an Alchemy AU1000 processor (MIPS based) and you want
397 to use a console on a serial port, say Y. Otherwise, say N.
399 config QTRONIX_KEYBOARD
400 bool "Enable Qtronix 990P Keyboard Support"
403 Images of Qtronix keyboards are at
404 <http://www.qtronix.com/keyboard.html>.
408 depends on QTRONIX_KEYBOARD
412 bool "Enable Smart Card Reader 0 Support "
415 Say Y here to support smart-card reader 0 (SCR0) on the Integrated
416 Technology Express, Inc. ITE8172 SBC. Vendor page at
417 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
418 board at <http://www.mvista.com/allies/semiconductor/ite.html>.
421 bool "Enable Smart Card Reader 1 Support "
424 Say Y here to support smart-card reader 1 (SCR1) on the Integrated
425 Technology Express, Inc. ITE8172 SBC. Vendor page at
426 <http://www.ite.com.tw/ia/brief_it8172bsp.htm>; picture of the
427 board at <http://www.mvista.com/allies/semiconductor/ite.html>.
430 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
431 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
433 This option supports the 2232 7-port serial card shipped with the
434 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
435 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
436 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
437 ports were connected with 8 pin DIN connectors on the card bracket,
438 for which 8 pin to DB25 adapters were supplied. The card also had
439 jumpers internally to toggle various pinning configurations.
441 This driver can be built as a module; but then "generic_serial"
442 will also be built as a module. This has to be loaded before
443 "ser_a2232". If you want to do this, answer M here.
445 source "drivers/serial/Kconfig"
448 bool "Unix98 PTY support"
450 A pseudo terminal (PTY) is a software device consisting of two
451 halves: a master and a slave. The slave device behaves identical to
452 a physical terminal; the master device is used by a process to
453 read data from and write data to the slave, thereby emulating a
454 terminal. Typical programs for the master side are telnet servers
457 Linux has traditionally used the BSD-like names /dev/ptyxx for
458 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
459 has a number of problems. The GNU C library glibc 2.1 and later,
460 however, supports the Unix98 naming standard: in order to acquire a
461 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
462 terminal is then made available to the process and the pseudo
463 terminal slave can be accessed as /dev/pts/<number>. What was
464 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
466 The entries in /dev/pts/ are created on the fly by a virtual
467 file system; therefore, if you say Y here you should say Y to
468 "/dev/pts file system for Unix98 PTYs" as well.
470 If you want to say Y here, you need to have the C library glibc 2.1
471 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
472 Read the instructions in <file:Documentation/Changes> pertaining to
473 pseudo terminals. It's safe to say N.
475 config UNIX98_PTY_COUNT
476 int "Maximum number of Unix98 PTYs in use (0-2048)"
477 depends on UNIX98_PTYS
480 The maximum number of Unix98 PTYs that can be used at any one time.
481 The default is 256, and should be enough for desktop systems. Server
482 machines which support incoming telnet/rlogin/ssh connections and/or
483 serve several X terminals may want to increase this: every incoming
484 connection and every xterm uses up one PTY.
486 When not in use, each additional set of 256 PTYs occupy
487 approximately 8 KB of kernel memory on 32-bit architectures.
490 tristate "Parallel printer support"
493 If you intend to attach a printer to the parallel port of your Linux
494 box (as opposed to using a serial printer; if the connector at the
495 printer has 9 or 25 holes ["female"], then it's serial), say Y.
496 Also read the Printing-HOWTO, available from
497 <http://www.tldp.org/docs.html#howto>.
499 It is possible to share one parallel port among several devices
500 (e.g. printer and ZIP drive) and it is safe to compile the
501 corresponding drivers into the kernel.
503 To compile this driver as a module, choose M here and read
504 <file:Documentation/parport.txt>. The module will be called lp.
506 If you have several parallel ports, you can specify which ports to
507 use with the "lp" kernel command line option. (Try "man bootparam"
508 or see the documentation of your boot loader (lilo or loadlin) about
509 how to pass options to the kernel at boot time.) The syntax of the
510 "lp" command line option can be found in <file:drivers/char/lp.c>.
512 If you have more than 8 printers, you need to increase the LP_NO
513 macro in lp.c and the PARPORT_MAX macro in parport.h.
516 bool "Support for console on line printer"
519 If you want kernel messages to be printed out as they occur, you
520 can have a console on the printer. This option adds support for
521 doing that; to actually get it to happen you need to pass the
522 option "console=lp0" to the kernel at boot time.
524 If the printer is out of paper (or off, or unplugged, or too
525 busy..) the kernel will stall until the printer is ready again.
526 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
527 can make the kernel continue when this happens,
528 but it'll lose the kernel messages.
533 tristate "Support for user-space parallel port device drivers"
536 Saying Y to this adds support for /dev/parport device nodes. This
537 is needed for programs that want portable access to the parallel
538 port, for instance deviceid (which displays Plug-and-Play device
541 This is the parallel port equivalent of SCSI generic support (sg).
542 It is safe to say N to this -- it is not needed for normal printing
543 or parallel port CD-ROM/disk support.
545 To compile this driver as a module, choose M here: the
546 module will be called ppdev.
551 tristate "Texas Instruments parallel link cable support"
554 If you own a Texas Instruments graphing calculator and use a
555 parallel link cable, then you might be interested in this driver.
557 If you enable this driver, you will be able to communicate with
558 your calculator through a set of device nodes under /dev. The
559 main advantage of this driver is that you don't have to be root
560 to use this precise link cable (depending on the permissions on
561 the device nodes, though).
563 To compile this driver as a module, choose M here: the
564 module will be called tipar.
566 If you don't know what a parallel link cable is or what a Texas
567 Instruments graphing calculator is, then you probably don't need this
573 bool "pSeries Hypervisor Virtual Console support"
574 depends on PPC_PSERIES
576 pSeries machines when partitioned support a hypervisor virtual
577 console. This driver allows each pSeries partition to have a console
578 which is accessed via the HMC.
581 tristate "NEC PC-9800 old-style printer port support"
582 depends on X86_PC9800 && !PARPORT
584 If you intend to attach a printer to the parallel port of NEC PC-9801
585 /PC-9821 with OLD compatibility mode, Say Y.
587 config PC9800_OLDLP_CONSOLE
588 bool "Support for console on line printer"
589 depends on PC9800_OLDLP
592 source "drivers/char/lirc/Kconfig"
597 tristate "Bus Mouse Support"
599 Say Y here if your machine has a bus mouse as opposed to a serial
600 mouse. Most people have a regular serial MouseSystem or
601 Microsoft mouse (made by Logitech) that plugs into a COM port
602 (rectangular with 9 or 25 pins). These people say N here.
604 If you have a laptop, you either have to check the documentation or
605 experiment a bit to find out whether the trackball is a serial mouse
606 or not; it's best to say Y here for you.
608 This is the generic bus mouse driver code. If you have a bus mouse,
609 you will have to say Y here and also to the specific driver for your
612 To compile this driver as a module, choose M here: the
613 module will be called busmouse.
618 tristate "QIC-02 tape support"
620 If you have a non-SCSI tape drive like that, say Y.
622 To compile this driver as a module, choose M here: the
623 module will be called tpqic02.
626 bool "Do you want runtime configuration for QIC-02"
627 depends on QIC02_TAPE
629 You can either configure this driver once and for all by editing a
630 header file (<file:include/linux/tpqic02.h>), in which case you
631 should say N, or you can fetch a program via anonymous FTP which is
632 able to configure this driver during runtime. The program to do
633 this is called 'qic02conf' and it is part of the
634 tpqic02-support-X.Y.tar.gz support package.
636 If you want to use the qic02conf program, say Y.
638 comment "Edit configuration parameters in ./include/linux/tpqic02.h!"
639 depends on QIC02_TAPE && !QIC02_DYNCONF
641 comment "Setting runtime QIC-02 configuration is done with qic02conf"
642 depends on QIC02_TAPE && QIC02_DYNCONF
644 comment "from the tpqic02-support package. It is available at"
645 depends on QIC02_TAPE && QIC02_DYNCONF
647 comment "metalab.unc.edu or ftp://titus.cfw.com/pub/Linux/util/"
648 depends on QIC02_TAPE && QIC02_DYNCONF
650 source "drivers/char/ipmi/Kconfig"
652 source "drivers/char/watchdog/Kconfig"
655 tristate "NetWinder thermometer support"
656 depends on ARCH_NETWINDER
658 Say Y here to include support for the thermal management hardware
659 found in the NetWinder. This driver allows the user to control the
660 temperature set points and to read the current temperature.
662 It is also possible to say M here to build it as a module (ds1620)
663 It is recommended to be used on a NetWinder, but it is not a
667 tristate "NetWinder Button"
668 depends on ARCH_NETWINDER
670 If you say Y here and create a character device node /dev/nwbutton
671 with major and minor numbers 10 and 158 ("man mknod"), then every
672 time the orange button is pressed a number of times, the number of
673 times the button was pressed will be written to that device.
675 This is most useful for applications, as yet unwritten, which
676 perform actions based on how many times the button is pressed in a
679 Do not hold the button down for too long, as the driver does not
680 alter the behaviour of the hardware reset circuitry attached to the
681 button; it will still execute a hard reset if the button is held
682 down for longer than approximately five seconds.
684 To compile this driver as a module, choose M here: the
685 module will be called nwbutton.
687 Most people will answer Y to this question and "Reboot Using Button"
688 below to be able to initiate a system shutdown from the button.
690 config NWBUTTON_REBOOT
691 bool "Reboot Using Button"
694 If you say Y here, then you will be able to initiate a system
695 shutdown and reboot by pressing the orange button a number of times.
696 The number of presses to initiate the shutdown is two by default,
697 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
698 in nwbutton.h and recompiling the driver or, if you compile the
699 driver as a module, you can specify the number of presses at load
700 time with "insmod button reboot_count=<something>".
703 tristate "NetWinder flash support"
704 depends on ARCH_NETWINDER
706 If you say Y here and create a character device /dev/flash with
707 major 10 and minor 160 you can manipulate the flash ROM containing
708 the NetWinder firmware. Be careful as accidentally overwriting the
709 flash contents can render your computer unbootable. On no account
710 allow random users access to this device. :-)
712 To compile this driver as a module, choose M here: the
713 module will be called nwflash.
715 If you're not sure, say N.
718 tristate "Intel/AMD/VIA HW Random Number Generator support"
719 depends on (X86 || IA64) && PCI
721 This driver provides kernel-side support for the Random Number
722 Generator hardware found on Intel i8xx-based motherboards,
723 AMD 76x-based motherboards, and Via Nehemiah CPUs.
725 Provides a character driver, used to read() entropy data.
727 To compile this driver as a module, choose M here: the
728 module will be called hw_random.
733 tristate "/dev/nvram support"
735 If you say Y here and create a character special file /dev/nvram
736 with major number 10 and minor number 144 using mknod ("man mknod"),
737 you get read and write access to the extra bytes of non-volatile
738 memory in the real time clock (RTC), which is contained in every PC
739 and most Ataris. The actual number of bytes varies, depending on the
740 nvram in the system, but is usually 114 (128-14 for the RTC).
742 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
743 on Ataris. /dev/nvram may be used to view settings there, or to
744 change them (with some utility). It could also be used to frequently
745 save a few bits of very important data that may not be lost over
746 power-off and for which writing to disk is too insecure. Note
747 however that most NVRAM space in a PC belongs to the BIOS and you
748 should NEVER idly tamper with it. See Ralf Brown's interrupt list
749 for a guide to the use of CMOS bytes by your BIOS.
751 On Atari machines, /dev/nvram is always configured and does not need
754 To compile this driver as a module, choose M here: the
755 module will be called nvram.
758 tristate "Enhanced Real Time Clock Support"
759 depends on !PPC32 && !PARISC && !IA64 && !X86_PC9800
761 If you say Y here and create a character special file /dev/rtc with
762 major number 10 and minor number 135 using mknod ("man mknod"), you
763 will get access to the real time clock (or hardware clock) built
766 Every PC has such a clock built in. It can be used to generate
767 signals from as low as 1Hz up to 8192Hz, and can also be used
768 as a 24 hour alarm. It reports status information via the file
769 /proc/driver/rtc and its behaviour is set by various ioctls on
772 If you run Linux on a multiprocessor machine and said Y to
773 "Symmetric Multi Processing" above, you should say Y here to read
774 and set the RTC in an SMP compatible fashion.
776 If you think you have a use for such a device (such as periodic data
777 sampling), then say Y here, and read <file:Documentation/rtc.txt>
780 To compile this driver as a module, choose M here: the
781 module will be called rtc.
784 tristate "Generic /dev/rtc emulation"
787 If you say Y here and create a character special file /dev/rtc with
788 major number 10 and minor number 135 using mknod ("man mknod"), you
789 will get access to the real time clock (or hardware clock) built
792 It reports status information via the file /proc/driver/rtc and its
793 behaviour is set by various ioctls on /dev/rtc. If you enable the
794 "extended RTC operation" below it will also provide an emulation
795 for RTC_UIE which is required by some programs and may improve
796 precision in some cases.
798 To compile this driver as a module, choose M here: the
799 module will be called genrtc. To load the module automatically
800 add 'alias char-major-10-135 genrtc' to your /etc/modules.conf
803 bool "Extended RTC operation"
806 Provides an emulation for RTC_UIE which is required by some programs
807 and may improve precision of the generic RTC support in some cases.
810 bool "EFI Real Time Clock Services"
814 tristate "NEC PC-9800 Real Time Clock Support"
815 depends on X86_PC9800
818 If you say Y here and create a character special file /dev/rtc with
819 major number 10 and minor number 135 using mknod ("man mknod"), you
820 will get access to the real time clock (or hardware clock) built
823 bool "Tadpole ANA H8 Support (OBSOLETE)"
824 depends on OBSOLETE && ALPHA_BOOK1
826 The Hitachi H8/337 is a microcontroller used to deal with the power
827 and thermal environment. If you say Y here, you will be able to
828 communicate with it via a character special device.
833 tristate "Double Talk PC internal speech card support"
835 This driver is for the DoubleTalk PC, a speech synthesizer
836 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
837 called the `internal DoubleTalk'.
839 To compile this driver as a module, choose M here: the
840 module will be called dtlk.
843 tristate "Siemens R3964 line discipline"
845 This driver allows synchronous communication with devices using the
846 Siemens R3964 packet protocol. Unless you are dealing with special
847 hardware like PLCs, you are unlikely to need this.
849 To compile this driver as a module, choose M here: the
850 module will be called n_r3964.
855 tristate "Applicom intelligent fieldbus card support"
857 This driver provides the kernel-side support for the intelligent
858 fieldbus cards made by Applicom International. More information
859 about these cards can be found on the WWW at the address
860 <http://www.applicom-int.com/>, or by email from David Woodhouse
861 <dwmw2@infradead.org>.
863 To compile this driver as a module, choose M here: the
864 module will be called applicom.
869 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
870 depends on EXPERIMENTAL && X86 && PCI && !64BIT
872 This driver enables access to the Sony Programmable I/O Control
873 Device which can be found in many (all ?) Sony Vaio laptops.
875 If you have one of those laptops, read
876 <file:Documentation/sonypi.txt>, and say Y or M here.
878 To compile this driver as a module, choose M here: the
879 module will be called sonypi.
882 menu "Ftape, the floppy tape device driver"
885 tristate "Ftape (QIC-80/Travan) support"
886 depends on BROKEN_ON_SMP
888 If you have a tape drive that is connected to your floppy
889 controller, say Y here.
891 Some tape drives (like the Seagate "Tape Store 3200" or the Iomega
892 "Ditto 3200" or the Exabyte "Eagle TR-3") come with a "high speed"
893 controller of their own. These drives (and their companion
894 controllers) are also supported if you say Y here.
896 If you have a special controller (such as the CMS FC-10, FC-20,
897 Mountain Mach-II, or any controller that is based on the Intel 82078
898 FDC like the high speed controllers by Seagate and Exabyte and
899 Iomega's "Ditto Dash") you must configure it by selecting the
900 appropriate entries from the "Floppy tape controllers" sub-menu
901 below and possibly modify the default values for the IRQ and DMA
902 channel and the IO base in ftape's configuration menu.
904 If you want to use your floppy tape drive on a PCI-bus based system,
905 please read the file <file:drivers/char/ftape/README.PCI>.
907 The ftape kernel driver is also available as a runtime loadable
908 module. To compile this driver as a module, choose M here: the
909 module will be called ftape.
911 Note that the Ftape-HOWTO is out of date (sorry) and documents the
912 older version 2.08 of this software but still contains useful
913 information. There is a web page with more recent documentation at
914 <http://www.instmath.rwth-aachen.de/~heine/ftape/>. This page
915 always contains the latest release of the ftape driver and useful
916 information (backup software, ftape related patches and
917 documentation, FAQ). Note that the file system interface has
918 changed quite a bit compared to previous versions of ftape. Please
919 read <file:Documentation/ftape.txt>.
921 source "drivers/char/ftape/Kconfig"
925 source "drivers/char/agp/Kconfig"
927 source "drivers/char/drm/Kconfig"
929 source "drivers/char/pcmcia/Kconfig"
932 tristate "ACP Modem (Mwave) support"
936 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
937 kernel driver and a user level application. Together these components
938 support direct attachment to public switched telephone networks (PSTNs)
939 and support selected world wide countries.
941 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
942 600, and 770 that include on board ACP modem hardware.
944 The modem also supports the standard communications port interface
945 (ttySx) and is compatible with the Hayes AT Command Set.
947 The user level application needed to use this driver can be found at
948 the IBM Linux Technology Center (LTC) web site:
949 <http://www.ibm.com/linux/ltc/>.
951 If you own one of the above IBM Thinkpads which has the Mwave chipset
954 To compile this driver as a module, choose M here: the
955 module will be called mwave.
958 tristate "NatSemi SCx200 GPIO Support"
961 Give userspace access to the GPIO pins on the National
962 Semiconductor SCx200 processors.
964 If compiled as a module, it will be called scx200_gpio.
967 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
969 The raw driver permits block devices to be bound to /dev/raw/rawN.
970 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
971 See the raw(8) manpage for more details.
973 The raw driver is deprecated and may be removed from 2.7
974 kernels. Applications should simply open the device (eg /dev/hda1)
975 with the O_DIRECT flag.
978 int "Maximum number of RAW devices to support (1-8192)"
979 depends on RAW_DRIVER
982 The maximum number of RAW devices that are supported.
983 Default is 256. Increase this number in case you need lots of
986 config HANGCHECK_TIMER
987 tristate "Hangcheck timer"
988 depends on X86_64 || X86
990 The hangcheck-timer module detects when the system has gone
991 out to lunch past a certain margin. It can reboot the system
992 or merely print a warning.
projects / linux-flexiantxendom0-3.2.10.git / blob