blob: a26d91743b24221b311c21a46c0d3d188325680a [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Character device configuration
3#
4
5menu "Character devices"
6
7config 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>.
20
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.
28
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.
34
35 If unsure, say Y, or else you won't be able to do much with your new
36 shiny Linux system :-)
37
38config 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).
50
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.)
57
58 If unsure, say Y.
59
60config HW_CONSOLE
61 bool
62 depends on VT && !S390 && !UML
63 default y
64
Antonino A. Daplas13ae6642006-06-26 00:27:12 -070065config VT_HW_CONSOLE_BINDING
66 bool "Support for binding and unbinding console drivers"
67 depends on HW_CONSOLE
68 default n
69 ---help---
70 The virtual terminal is the device that interacts with the physical
71 terminal through console drivers. On these systems, at least one
72 console driver is loaded. In other configurations, additional console
73 drivers may be enabled, such as the framebuffer console. If more than
74 1 console driver is enabled, setting this to 'y' will allow you to
75 select the console driver that will serve as the backend for the
76 virtual terminals.
77
78 See <file:Documentation/console/console.txt> for more
79 information. For framebuffer console users, please refer to
80 <file:Documentation/fb/fbcon.txt>.
81
Linus Torvalds1da177e2005-04-16 15:20:36 -070082config SERIAL_NONSTANDARD
83 bool "Non-standard serial port support"
84 ---help---
85 Say Y here if you have any non-standard serial boards -- boards
86 which aren't supported using the standard "dumb" serial driver.
87 This includes intelligent serial boards such as Cyclades,
88 Digiboards, etc. These are usually used for systems that need many
89 serial ports because they serve many terminals or dial-in
90 connections.
91
92 Note that the answer to this question won't directly affect the
93 kernel: saying N will just cause the configurator to skip all
94 the questions about non-standard serial boards.
95
96 Most people can say N here.
97
98config COMPUTONE
99 tristate "Computone IntelliPort Plus serial support"
Al Viro3b4709a2006-12-13 00:34:58 -0800100 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700101 ---help---
102 This driver supports the entire family of Intelliport II/Plus
103 controllers with the exception of the MicroChannel controllers and
104 products previous to the Intelliport II. These are multiport cards,
105 which give you many serial ports. You would need something like this
106 to connect more than two modems to your Linux box, for instance in
107 order to become a dial-in server. If you have a card like that, say
108 Y here and read <file:Documentation/computone.txt>.
109
110 To compile this driver as modules, choose M here: the
111 modules will be called ip2 and ip2main.
112
113config ROCKETPORT
114 tristate "Comtrol RocketPort support"
115 depends on SERIAL_NONSTANDARD
116 help
117 This driver supports Comtrol RocketPort and RocketModem PCI boards.
118 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
119 modems. For information about the RocketPort/RocketModem boards
120 and this driver read <file:Documentation/rocket.txt>.
121
122 To compile this driver as a module, choose M here: the
123 module will be called rocket.
124
125 If you want to compile this driver into the kernel, say Y here. If
126 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
127
128config CYCLADES
129 tristate "Cyclades async mux support"
130 depends on SERIAL_NONSTANDARD
131 ---help---
132 This driver supports Cyclades Z and Y multiserial boards.
133 You would need something like this to connect more than two modems to
134 your Linux box, for instance in order to become a dial-in server.
135
136 For information about the Cyclades-Z card, read
137 <file:drivers/char/README.cycladesZ>.
138
139 To compile this driver as a module, choose M here: the
140 module will be called cyclades.
141
142 If you haven't heard about it, it's safe to say N.
143
144config CYZ_INTR
145 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
146 depends on EXPERIMENTAL && CYCLADES
147 help
148 The Cyclades-Z family of multiport cards allows 2 (two) driver op
149 modes: polling and interrupt. In polling mode, the driver will check
150 the status of the Cyclades-Z ports every certain amount of time
151 (which is called polling cycle and is configurable). In interrupt
152 mode, it will use an interrupt line (IRQ) in order to check the
153 status of the Cyclades-Z ports. The default op mode is polling. If
154 unsure, say N.
155
156config DIGIEPCA
157 tristate "Digiboard Intelligent Async Support"
Alan Coxf2cf8e22005-09-06 15:16:44 -0700158 depends on SERIAL_NONSTANDARD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700159 ---help---
160 This is a driver for Digi International's Xx, Xeve, and Xem series
161 of cards which provide multiple serial ports. You would need
162 something like this to connect more than two modems to your Linux
163 box, for instance in order to become a dial-in server. This driver
164 supports the original PC (ISA) boards as well as PCI, and EISA. If
165 you have a card like this, say Y here and read the file
166 <file:Documentation/digiepca.txt>.
167
168 To compile this driver as a module, choose M here: the
169 module will be called epca.
170
171config ESPSERIAL
172 tristate "Hayes ESP serial port support"
Alan Cox33f0f882006-01-09 20:54:13 -0800173 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700174 help
175 This is a driver which supports Hayes ESP serial ports. Both single
176 port cards and multiport cards are supported. Make sure to read
177 <file:Documentation/hayes-esp.txt>.
178
179 To compile this driver as a module, choose M here: the
180 module will be called esp.
181
182 If unsure, say N.
183
184config MOXA_INTELLIO
185 tristate "Moxa Intellio support"
Alan Cox33f0f882006-01-09 20:54:13 -0800186 depends on SERIAL_NONSTANDARD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700187 help
188 Say Y here if you have a Moxa Intellio multiport serial card.
189
190 To compile this driver as a module, choose M here: the
191 module will be called moxa.
192
193config MOXA_SMARTIO
Jiri Slaby98c47ea2007-02-10 01:45:15 -0800194 tristate "Moxa SmartIO support (OBSOLETE)"
Al Viro1d252402005-09-05 23:30:15 -0700195 depends on SERIAL_NONSTANDARD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700196 help
197 Say Y here if you have a Moxa SmartIO multiport serial card.
198
199 This driver can also be built as a module ( = code which can be
200 inserted in and removed from the running kernel whenever you want).
201 The module will be called mxser. If you want to do that, say M
202 here.
203
Jiri Slaby037ad482006-12-08 02:38:11 -0800204config MOXA_SMARTIO_NEW
Jiri Slaby98c47ea2007-02-10 01:45:15 -0800205 tristate "Moxa SmartIO support v. 2.0"
Jiri Slabyfb0c9292006-12-13 00:34:19 -0800206 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
Jiri Slaby037ad482006-12-08 02:38:11 -0800207 help
208 Say Y here if you have a Moxa SmartIO multiport serial card and/or
209 want to help develop a new version of this driver.
210
211 This is upgraded (1.9.1) driver from original Moxa drivers with
212 changes finally resulting in PCI probing.
213
214 Use at your own risk.
215
216 This driver can also be built as a module. The module will be called
217 mxser_new. If you want to do that, say M here.
218
Linus Torvalds1da177e2005-04-16 15:20:36 -0700219config ISI
220 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
Randy Dunlapa3808ac2006-12-13 00:34:18 -0800221 depends on SERIAL_NONSTANDARD && PCI
maximilian attems5ff2a7e2006-03-26 01:37:35 -0800222 select FW_LOADER
Linus Torvalds1da177e2005-04-16 15:20:36 -0700223 help
224 This is a driver for the Multi-Tech cards which provide several
225 serial ports. The driver is experimental and can currently only be
226 built as a module. The module will be called isicom.
227 If you want to do that, choose M here.
228
229config SYNCLINK
230 tristate "Microgate SyncLink card support"
Al Viroa5532602005-05-04 05:39:42 +0100231 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700232 help
233 Provides support for the SyncLink ISA and PCI multiprotocol serial
234 adapters. These adapters support asynchronous and HDLC bit
235 synchronous communication up to 10Mbps (PCI adapter).
236
237 This driver can only 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 synclink. If you want to do that, say M
240 here.
241
242config SYNCLINKMP
243 tristate "SyncLink Multiport support"
viro@ZenIV.linux.org.ukf91f4d92005-09-09 17:02:51 +0100244 depends on SERIAL_NONSTANDARD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700245 help
246 Enable support for the SyncLink Multiport (2 or 4 ports)
247 serial adapter, running asynchronous and HDLC communications up
248 to 2.048Mbps. Each ports is independently selectable for
249 RS-232, V.35, RS-449, RS-530, and X.21
250
251 This driver may be built as a module ( = code which can be
252 inserted in and removed from the running kernel whenever you want).
253 The module will be called synclinkmp. If you want to do that, say M
254 here.
255
Paul Fulghum705b6c72006-01-08 01:02:06 -0800256config SYNCLINK_GT
257 tristate "SyncLink GT/AC support"
Al Viro8ef9cf32006-02-01 06:07:15 -0500258 depends on SERIAL_NONSTANDARD && PCI
Paul Fulghum705b6c72006-01-08 01:02:06 -0800259 help
260 Support for SyncLink GT and SyncLink AC families of
261 synchronous and asynchronous serial adapters
262 manufactured by Microgate Systems, Ltd. (www.microgate.com)
263
Linus Torvalds1da177e2005-04-16 15:20:36 -0700264config N_HDLC
265 tristate "HDLC line discipline support"
266 depends on SERIAL_NONSTANDARD
267 help
268 Allows synchronous HDLC communications with tty device drivers that
269 support synchronous HDLC such as the Microgate SyncLink adapter.
270
271 This driver can only be built as a module ( = code which can be
272 inserted in and removed from the running kernel whenever you want).
273 The module will be called n_hdlc. If you want to do that, say M
274 here.
275
276config RISCOM8
277 tristate "SDL RISCom/8 card support"
278 depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP
279 help
280 This is a driver for the SDL Communications RISCom/8 multiport card,
281 which gives you many serial ports. You would need something like
282 this to connect more than two modems to your Linux box, for instance
283 in order to become a dial-in server. If you have a card like that,
284 say Y here and read the file <file:Documentation/riscom8.txt>.
285
286 Also it's possible to say M here and compile this driver as kernel
287 loadable module; the module will be called riscom8.
288
289config SPECIALIX
290 tristate "Specialix IO8+ card support"
291 depends on SERIAL_NONSTANDARD
292 help
293 This is a driver for the Specialix IO8+ multiport card (both the
294 ISA and the PCI version) which gives you many serial ports. You
295 would need something like this to connect more than two modems to
296 your Linux box, for instance in order to become a dial-in server.
297
298 If you have a card like that, say Y here and read the file
299 <file:Documentation/specialix.txt>. Also it's possible to say M here
300 and compile this driver as kernel loadable module which will be
301 called specialix.
302
303config SPECIALIX_RTSCTS
304 bool "Specialix DTR/RTS pin is RTS"
305 depends on SPECIALIX
306 help
307 The Specialix IO8+ card can only support either RTS or DTR. If you
308 say N here, the driver will use the pin as "DTR" when the tty is in
309 software handshake mode. If you say Y here or hardware handshake is
310 on, it will always be RTS. Read the file
311 <file:Documentation/specialix.txt> for more information.
312
313config SX
314 tristate "Specialix SX (and SI) card support"
Jiri Slaby3468a332006-12-13 00:34:20 -0800315 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700316 help
317 This is a driver for the SX and SI multiport serial cards.
318 Please read the file <file:Documentation/sx.txt> for details.
319
320 This driver can only be built as a module ( = code which can be
321 inserted in and removed from the running kernel whenever you want).
322 The module will be called sx. If you want to do that, say M here.
323
324config RIO
325 tristate "Specialix RIO system support"
Alan Cox655fdea2006-05-15 09:44:26 -0700326 depends on SERIAL_NONSTANDARD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700327 help
328 This is a driver for the Specialix RIO, a smart serial card which
329 drives an outboard box that can support up to 128 ports. Product
330 information is at <http://www.perle.com/support/documentation.html#multiport>.
331 There are both ISA and PCI versions.
332
333config RIO_OLDPCI
334 bool "Support really old RIO/PCI cards"
335 depends on RIO
336 help
337 Older RIO PCI cards need some initialization-time configuration to
338 determine the IRQ and some control addresses. If you have a RIO and
339 this doesn't seem to work, try setting this to Y.
340
341config STALDRV
342 bool "Stallion multiport serial support"
343 depends on SERIAL_NONSTANDARD
344 help
345 Stallion cards give you many serial ports. You would need something
346 like this to connect more than two modems to your Linux box, for
347 instance in order to become a dial-in server. If you say Y here,
348 you will be asked for your specific card model in the next
349 questions. Make sure to read <file:Documentation/stallion.txt> in
350 this case. If you have never heard about all this, it's safe to
351 say N.
352
353config STALLION
354 tristate "Stallion EasyIO or EC8/32 support"
355 depends on STALDRV && BROKEN_ON_SMP
356 help
357 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
358 card, then this is for you; say Y. Make sure to read
359 <file:Documentation/stallion.txt>.
360
361 To compile this driver as a module, choose M here: the
362 module will be called stallion.
363
364config ISTALLION
365 tristate "Stallion EC8/64, ONboard, Brumby support"
366 depends on STALDRV && BROKEN_ON_SMP
367 help
368 If you have an EasyConnection 8/64, ONboard, Brumby or Stallion
369 serial multiport card, say Y here. Make sure to read
370 <file:Documentation/stallion.txt>.
371
372 To compile this driver as a module, choose M here: the
373 module will be called istallion.
374
375config AU1000_UART
376 bool "Enable Au1000 UART Support"
377 depends on SERIAL_NONSTANDARD && MIPS
378 help
379 If you have an Alchemy AU1000 processor (MIPS based) and you want
380 to use serial ports, say Y. Otherwise, say N.
381
382config AU1000_SERIAL_CONSOLE
383 bool "Enable Au1000 serial console"
384 depends on AU1000_UART
385 help
386 If you have an Alchemy AU1000 processor (MIPS based) and you want
387 to use a console on a serial port, say Y. Otherwise, say N.
388
Ralf Baechle96fac9d2007-03-29 01:20:34 -0700389config SERIAL_DEC
390 bool "DECstation serial support"
391 depends on MACH_DECSTATION
392 default y
393 help
394 This selects whether you want to be asked about drivers for
395 DECstation serial ports.
396
397 Note that the answer to this question won't directly affect the
398 kernel: saying N will just cause the configurator to skip all
399 the questions about DECstation serial ports.
400
401config SERIAL_DEC_CONSOLE
402 bool "Support for console on a DECstation serial port"
403 depends on SERIAL_DEC
404 default y
405 help
406 If you say Y here, it will be possible to use a serial port as the
407 system console (the system console is the device which receives all
408 kernel messages and warnings and which allows logins in single user
409 mode). Note that the firmware uses ttyS0 as the serial console on
410 the Maxine and ttyS2 on the others.
411
412 If unsure, say Y.
413
414config ZS
415 bool "Z85C30 Serial Support"
416 depends on SERIAL_DEC
417 default y
418 help
419 Documentation on the Zilog 85C350 serial communications controller
420 is downloadable at <http://www.zilog.com/pdfs/serial/z85c30.pdf>
421
Linus Torvalds1da177e2005-04-16 15:20:36 -0700422config A2232
423 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
424 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
425 ---help---
426 This option supports the 2232 7-port serial card shipped with the
427 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
428 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
429 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
430 ports were connected with 8 pin DIN connectors on the card bracket,
431 for which 8 pin to DB25 adapters were supplied. The card also had
432 jumpers internally to toggle various pinning configurations.
433
434 This driver can be built as a module; but then "generic_serial"
435 will also be built as a module. This has to be loaded before
436 "ser_a2232". If you want to do this, answer M here.
437
438config SGI_SNSC
439 bool "SGI Altix system controller communication support"
440 depends on (IA64_SGI_SN2 || IA64_GENERIC)
441 help
442 If you have an SGI Altix and you want to enable system
443 controller communication from user space (you want this!),
444 say Y. Otherwise, say N.
445
Bruce Losuree1e19742005-04-25 13:09:41 -0700446config SGI_TIOCX
447 bool "SGI TIO CX driver support"
448 depends on (IA64_SGI_SN2 || IA64_GENERIC)
449 help
450 If you have an SGI Altix and you have fpga devices attached
451 to your TIO, say Y here, otherwise say N.
452
453config SGI_MBCS
454 tristate "SGI FPGA Core Services driver support"
Bruce Losureae40aae2005-04-04 13:23:00 -0700455 depends on SGI_TIOCX
Bruce Losuree1e19742005-04-25 13:09:41 -0700456 help
457 If you have an SGI Altix with an attached SABrick
458 say Y or M here, otherwise say N.
459
Linus Torvalds1da177e2005-04-16 15:20:36 -0700460source "drivers/serial/Kconfig"
461
462config UNIX98_PTYS
463 bool "Unix98 PTY support" if EMBEDDED
464 default y
465 ---help---
466 A pseudo terminal (PTY) is a software device consisting of two
467 halves: a master and a slave. The slave device behaves identical to
468 a physical terminal; the master device is used by a process to
469 read data from and write data to the slave, thereby emulating a
470 terminal. Typical programs for the master side are telnet servers
471 and xterms.
472
473 Linux has traditionally used the BSD-like names /dev/ptyxx for
474 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
475 has a number of problems. The GNU C library glibc 2.1 and later,
476 however, supports the Unix98 naming standard: in order to acquire a
477 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
478 terminal is then made available to the process and the pseudo
479 terminal slave can be accessed as /dev/pts/<number>. What was
480 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
481
482 All modern Linux systems use the Unix98 ptys. Say Y unless
483 you're on an embedded system and want to conserve memory.
484
485config LEGACY_PTYS
486 bool "Legacy (BSD) PTY support"
487 default y
488 ---help---
489 A pseudo terminal (PTY) is a software device consisting of two
490 halves: a master and a slave. The slave device behaves identical to
491 a physical terminal; the master device is used by a process to
492 read data from and write data to the slave, thereby emulating a
493 terminal. Typical programs for the master side are telnet servers
494 and xterms.
495
496 Linux has traditionally used the BSD-like names /dev/ptyxx
497 for masters and /dev/ttyxx for slaves of pseudo
498 terminals. This scheme has a number of problems, including
499 security. This option enables these legacy devices; on most
500 systems, it is safe to say N.
501
502
503config LEGACY_PTY_COUNT
504 int "Maximum number of legacy PTY in use"
505 depends on LEGACY_PTYS
506 range 1 256
507 default "256"
508 ---help---
509 The maximum number of legacy PTYs that can be used at any one time.
510 The default is 256, and should be more than enough. Embedded
511 systems may want to reduce this to save memory.
512
513 When not in use, each legacy PTY occupies 12 bytes on 32-bit
514 architectures and 24 bytes on 64-bit architectures.
515
Benjamin Herrenschmidta45b8392006-07-04 15:06:20 +1000516config BRIQ_PANEL
517 tristate 'Total Impact briQ front panel driver'
Paul Mackerras2818c5d2006-08-25 15:08:21 +1000518 depends on PPC_CHRP
Benjamin Herrenschmidta45b8392006-07-04 15:06:20 +1000519 ---help---
520 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
521 tristate led and two switches. It is the size of a CDROM drive.
522
523 If you have such one and want anything showing on the VFD then you
524 must answer Y here.
525
526 To compile this driver as a module, choose M here: the
527 module will be called briq_panel.
528
529 It's safe to say N here.
530
Linus Torvalds1da177e2005-04-16 15:20:36 -0700531config PRINTER
532 tristate "Parallel printer support"
533 depends on PARPORT
534 ---help---
535 If you intend to attach a printer to the parallel port of your Linux
536 box (as opposed to using a serial printer; if the connector at the
537 printer has 9 or 25 holes ["female"], then it's serial), say Y.
538 Also read the Printing-HOWTO, available from
539 <http://www.tldp.org/docs.html#howto>.
540
541 It is possible to share one parallel port among several devices
542 (e.g. printer and ZIP drive) and it is safe to compile the
543 corresponding drivers into the kernel.
544
545 To compile this driver as a module, choose M here and read
546 <file:Documentation/parport.txt>. The module will be called lp.
547
548 If you have several parallel ports, you can specify which ports to
549 use with the "lp" kernel command line option. (Try "man bootparam"
550 or see the documentation of your boot loader (lilo or loadlin) about
551 how to pass options to the kernel at boot time.) The syntax of the
552 "lp" command line option can be found in <file:drivers/char/lp.c>.
553
554 If you have more than 8 printers, you need to increase the LP_NO
555 macro in lp.c and the PARPORT_MAX macro in parport.h.
556
557config LP_CONSOLE
558 bool "Support for console on line printer"
559 depends on PRINTER
560 ---help---
561 If you want kernel messages to be printed out as they occur, you
562 can have a console on the printer. This option adds support for
563 doing that; to actually get it to happen you need to pass the
564 option "console=lp0" to the kernel at boot time.
565
566 If the printer is out of paper (or off, or unplugged, or too
567 busy..) the kernel will stall until the printer is ready again.
568 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
569 can make the kernel continue when this happens,
570 but it'll lose the kernel messages.
571
572 If unsure, say N.
573
574config PPDEV
575 tristate "Support for user-space parallel port device drivers"
576 depends on PARPORT
577 ---help---
578 Saying Y to this adds support for /dev/parport device nodes. This
579 is needed for programs that want portable access to the parallel
580 port, for instance deviceid (which displays Plug-and-Play device
581 IDs).
582
583 This is the parallel port equivalent of SCSI generic support (sg).
584 It is safe to say N to this -- it is not needed for normal printing
585 or parallel port CD-ROM/disk support.
586
587 To compile this driver as a module, choose M here: the
588 module will be called ppdev.
589
590 If unsure, say N.
591
592config TIPAR
593 tristate "Texas Instruments parallel link cable support"
594 depends on PARPORT
595 ---help---
596 If you own a Texas Instruments graphing calculator and use a
597 parallel link cable, then you might be interested in this driver.
598
599 If you enable this driver, you will be able to communicate with
600 your calculator through a set of device nodes under /dev. The
601 main advantage of this driver is that you don't have to be root
602 to use this precise link cable (depending on the permissions on
603 the device nodes, though).
604
605 To compile this driver as a module, choose M here: the
606 module will be called tipar.
607
608 If you don't know what a parallel link cable is or what a Texas
609 Instruments graphing calculator is, then you probably don't need this
610 driver.
611
612 If unsure, say N.
613
Ryan S. Arnold45d607e2006-03-27 21:25:16 +0200614config HVC_DRIVER
615 bool
616 help
617 Users of pSeries machines that want to utilize the hvc console front-end
618 module for their backend console driver should select this option.
619 It will automatically be selected if one of the back-end console drivers
620 is selected.
621
622
Linus Torvalds1da177e2005-04-16 15:20:36 -0700623config HVC_CONSOLE
624 bool "pSeries Hypervisor Virtual Console support"
625 depends on PPC_PSERIES
Ryan S. Arnold45d607e2006-03-27 21:25:16 +0200626 select HVC_DRIVER
Linus Torvalds1da177e2005-04-16 15:20:36 -0700627 help
628 pSeries machines when partitioned support a hypervisor virtual
629 console. This driver allows each pSeries partition to have a console
630 which is accessed via the HMC.
631
Stephen Rothwell8bff05b2006-07-13 18:51:22 +1000632config HVC_ISERIES
633 bool "iSeries Hypervisor Virtual Console support"
634 depends on PPC_ISERIES && !VIOCONS
635 select HVC_DRIVER
636 help
637 iSeries machines support a hypervisor virtual console.
638
Arnd Bergmannf4d17492006-03-27 21:26:03 +0200639config HVC_RTAS
640 bool "IBM RTAS Console support"
641 depends on PPC_RTAS
642 select HVC_DRIVER
643 help
644 IBM Console device driver which makes use of RTAS
645
Ishizaki Kou3cdc20e2007-02-02 16:44:08 +0900646config HVC_BEAT
647 bool "Toshiba's Beat Hypervisor Console support"
648 depends on PPC_CELLEB
649 select HVC_DRIVER
650 help
651 Toshiba's Cell Reference Set Beat Console device driver
652
Linus Torvalds1da177e2005-04-16 15:20:36 -0700653config HVCS
654 tristate "IBM Hypervisor Virtual Console Server support"
655 depends on PPC_PSERIES
656 help
657 Partitionable IBM Power5 ppc64 machines allow hosting of
658 firmware virtual consoles from one Linux partition by
659 another Linux partition. This driver allows console data
660 from Linux partitions to be accessed through TTY device
661 interfaces in the device tree of a Linux partition running
662 this driver.
663
664 To compile this driver as a module, choose M here: the
665 module will be called hvcs.ko. Additionally, this module
666 will depend on arch specific APIs exported from hvcserver.ko
667 which will also be compiled when this driver is built as a
668 module.
669
670source "drivers/char/ipmi/Kconfig"
671
672source "drivers/char/watchdog/Kconfig"
673
674config DS1620
675 tristate "NetWinder thermometer support"
676 depends on ARCH_NETWINDER
677 help
678 Say Y here to include support for the thermal management hardware
679 found in the NetWinder. This driver allows the user to control the
680 temperature set points and to read the current temperature.
681
682 It is also possible to say M here to build it as a module (ds1620)
683 It is recommended to be used on a NetWinder, but it is not a
684 necessity.
685
686config NWBUTTON
687 tristate "NetWinder Button"
688 depends on ARCH_NETWINDER
689 ---help---
690 If you say Y here and create a character device node /dev/nwbutton
691 with major and minor numbers 10 and 158 ("man mknod"), then every
692 time the orange button is pressed a number of times, the number of
693 times the button was pressed will be written to that device.
694
695 This is most useful for applications, as yet unwritten, which
696 perform actions based on how many times the button is pressed in a
697 row.
698
699 Do not hold the button down for too long, as the driver does not
700 alter the behaviour of the hardware reset circuitry attached to the
701 button; it will still execute a hard reset if the button is held
702 down for longer than approximately five seconds.
703
704 To compile this driver as a module, choose M here: the
705 module will be called nwbutton.
706
707 Most people will answer Y to this question and "Reboot Using Button"
708 below to be able to initiate a system shutdown from the button.
709
710config NWBUTTON_REBOOT
711 bool "Reboot Using Button"
712 depends on NWBUTTON
713 help
714 If you say Y here, then you will be able to initiate a system
715 shutdown and reboot by pressing the orange button a number of times.
716 The number of presses to initiate the shutdown is two by default,
717 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
718 in nwbutton.h and recompiling the driver or, if you compile the
719 driver as a module, you can specify the number of presses at load
720 time with "insmod button reboot_count=<something>".
721
722config NWFLASH
723 tristate "NetWinder flash support"
724 depends on ARCH_NETWINDER
725 ---help---
726 If you say Y here and create a character device /dev/flash with
727 major 10 and minor 160 you can manipulate the flash ROM containing
728 the NetWinder firmware. Be careful as accidentally overwriting the
729 flash contents can render your computer unbootable. On no account
730 allow random users access to this device. :-)
731
732 To compile this driver as a module, choose M here: the
733 module will be called nwflash.
734
735 If you're not sure, say N.
736
Michael Buesch844dd052006-06-26 00:24:59 -0700737source "drivers/char/hw_random/Kconfig"
738
Linus Torvalds1da177e2005-04-16 15:20:36 -0700739config NVRAM
740 tristate "/dev/nvram support"
Brian Gerst0d078f62005-10-30 14:59:20 -0800741 depends on ATARI || X86 || ARM || GENERIC_NVRAM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700742 ---help---
743 If you say Y here and create a character special file /dev/nvram
744 with major number 10 and minor number 144 using mknod ("man mknod"),
745 you get read and write access to the extra bytes of non-volatile
746 memory in the real time clock (RTC), which is contained in every PC
747 and most Ataris. The actual number of bytes varies, depending on the
748 nvram in the system, but is usually 114 (128-14 for the RTC).
749
750 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
751 on Ataris. /dev/nvram may be used to view settings there, or to
752 change them (with some utility). It could also be used to frequently
753 save a few bits of very important data that may not be lost over
754 power-off and for which writing to disk is too insecure. Note
755 however that most NVRAM space in a PC belongs to the BIOS and you
756 should NEVER idly tamper with it. See Ralf Brown's interrupt list
757 for a guide to the use of CMOS bytes by your BIOS.
758
759 On Atari machines, /dev/nvram is always configured and does not need
760 to be selected.
761
762 To compile this driver as a module, choose M here: the
763 module will be called nvram.
764
765config RTC
766 tristate "Enhanced Real Time Clock Support"
Paul Mundt91550f72006-09-27 17:45:01 +0900767 depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV && !ARM && !SUPERH
Linus Torvalds1da177e2005-04-16 15:20:36 -0700768 ---help---
769 If you say Y here and create a character special file /dev/rtc with
770 major number 10 and minor number 135 using mknod ("man mknod"), you
771 will get access to the real time clock (or hardware clock) built
772 into your computer.
773
774 Every PC has such a clock built in. It can be used to generate
775 signals from as low as 1Hz up to 8192Hz, and can also be used
776 as a 24 hour alarm. It reports status information via the file
777 /proc/driver/rtc and its behaviour is set by various ioctls on
778 /dev/rtc.
779
780 If you run Linux on a multiprocessor machine and said Y to
781 "Symmetric Multi Processing" above, you should say Y here to read
782 and set the RTC in an SMP compatible fashion.
783
784 If you think you have a use for such a device (such as periodic data
785 sampling), then say Y here, and read <file:Documentation/rtc.txt>
786 for details.
787
788 To compile this driver as a module, choose M here: the
789 module will be called rtc.
790
791config SGI_DS1286
792 tristate "SGI DS1286 RTC support"
793 depends on SGI_IP22
794 help
795 If you say Y here and create a character special file /dev/rtc with
796 major number 10 and minor number 135 using mknod ("man mknod"), you
797 will get access to the real time clock built into your computer.
798 Every SGI has such a clock built in. It reports status information
799 via the file /proc/rtc and its behaviour is set by various ioctls on
800 /dev/rtc.
801
802config SGI_IP27_RTC
803 bool "SGI M48T35 RTC support"
804 depends on SGI_IP27
805 help
806 If you say Y here and create a character special file /dev/rtc with
807 major number 10 and minor number 135 using mknod ("man mknod"), you
808 will get access to the real time clock built into your computer.
809 Every SGI has such a clock built in. It reports status information
810 via the file /proc/rtc and its behaviour is set by various ioctls on
811 /dev/rtc.
812
813config GEN_RTC
814 tristate "Generic /dev/rtc emulation"
David Howells2919b512006-01-08 01:01:16 -0800815 depends on RTC!=y && !IA64 && !ARM && !M32R && !SPARC && !FRV
Linus Torvalds1da177e2005-04-16 15:20:36 -0700816 ---help---
817 If you say Y here and create a character special file /dev/rtc with
818 major number 10 and minor number 135 using mknod ("man mknod"), you
819 will get access to the real time clock (or hardware clock) built
820 into your computer.
821
822 It reports status information via the file /proc/driver/rtc and its
823 behaviour is set by various ioctls on /dev/rtc. If you enable the
824 "extended RTC operation" below it will also provide an emulation
825 for RTC_UIE which is required by some programs and may improve
826 precision in some cases.
827
828 To compile this driver as a module, choose M here: the
829 module will be called genrtc.
830
831config GEN_RTC_X
832 bool "Extended RTC operation"
833 depends on GEN_RTC
834 help
835 Provides an emulation for RTC_UIE which is required by some programs
836 and may improve precision of the generic RTC support in some cases.
837
838config EFI_RTC
839 bool "EFI Real Time Clock Services"
840 depends on IA64
841
842config DS1302
843 tristate "DS1302 RTC support"
844 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
845 help
846 If you say Y here and create a character special file /dev/rtc with
847 major number 121 and minor number 0 using mknod ("man mknod"), you
848 will get access to the real time clock (or hardware clock) built
849 into your computer.
850
Linus Torvalds1da177e2005-04-16 15:20:36 -0700851config COBALT_LCD
852 bool "Support for Cobalt LCD"
853 depends on MIPS_COBALT
854 help
855 This option enables support for the LCD display and buttons found
856 on Cobalt systems through a misc device.
857
858config DTLK
859 tristate "Double Talk PC internal speech card support"
860 help
861 This driver is for the DoubleTalk PC, a speech synthesizer
862 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
863 called the `internal DoubleTalk'.
864
865 To compile this driver as a module, choose M here: the
866 module will be called dtlk.
867
868config R3964
869 tristate "Siemens R3964 line discipline"
870 ---help---
871 This driver allows synchronous communication with devices using the
872 Siemens R3964 packet protocol. Unless you are dealing with special
873 hardware like PLCs, you are unlikely to need this.
874
875 To compile this driver as a module, choose M here: the
876 module will be called n_r3964.
877
878 If unsure, say N.
879
880config APPLICOM
881 tristate "Applicom intelligent fieldbus card support"
882 depends on PCI
883 ---help---
884 This driver provides the kernel-side support for the intelligent
885 fieldbus cards made by Applicom International. More information
886 about these cards can be found on the WWW at the address
887 <http://www.applicom-int.com/>, or by email from David Woodhouse
888 <dwmw2@infradead.org>.
889
890 To compile this driver as a module, choose M here: the
891 module will be called applicom.
892
893 If unsure, say N.
894
895config SONYPI
896 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
897 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
898 ---help---
899 This driver enables access to the Sony Programmable I/O Control
900 Device which can be found in many (all ?) Sony Vaio laptops.
901
902 If you have one of those laptops, read
903 <file:Documentation/sonypi.txt>, and say Y or M here.
904
905 To compile this driver as a module, choose M here: the
906 module will be called sonypi.
907
Yoichi Yuasa09762512007-05-06 14:51:58 -0700908config GPIO_TB0219
909 tristate "TANBAC TB0219 GPIO support"
Robert P. J. Daybef1f402006-12-12 20:04:19 +0100910 depends on TANBAC_TB022X
Yoichi Yuasa584e1232006-06-25 05:49:11 -0700911 select GPIO_VR41XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700912
Linus Torvalds1da177e2005-04-16 15:20:36 -0700913source "drivers/char/agp/Kconfig"
914
915source "drivers/char/drm/Kconfig"
916
917source "drivers/char/pcmcia/Kconfig"
918
919config MWAVE
920 tristate "ACP Modem (Mwave) support"
921 depends on X86
922 select SERIAL_8250
923 ---help---
924 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
925 kernel driver and a user level application. Together these components
926 support direct attachment to public switched telephone networks (PSTNs)
927 and support selected world wide countries.
928
929 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
930 600, and 770 that include on board ACP modem hardware.
931
932 The modem also supports the standard communications port interface
933 (ttySx) and is compatible with the Hayes AT Command Set.
934
935 The user level application needed to use this driver can be found at
936 the IBM Linux Technology Center (LTC) web site:
937 <http://www.ibm.com/linux/ltc/>.
938
939 If you own one of the above IBM Thinkpads which has the Mwave chipset
940 in it, say Y.
941
942 To compile this driver as a module, choose M here: the
943 module will be called mwave.
944
945config SCx200_GPIO
946 tristate "NatSemi SCx200 GPIO Support"
947 depends on SCx200
Jim Cromie7a8e2a52006-06-27 02:54:27 -0700948 select NSC_GPIO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700949 help
950 Give userspace access to the GPIO pins on the National
951 Semiconductor SCx200 processors.
952
953 If compiled as a module, it will be called scx200_gpio.
954
Jim Cromie7a8e2a52006-06-27 02:54:27 -0700955config PC8736x_GPIO
956 tristate "NatSemi PC8736x GPIO Support"
957 depends on X86
958 default SCx200_GPIO # mostly N
959 select NSC_GPIO # needed for support routines
960 help
961 Give userspace access to the GPIO pins on the National
962 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
963 has multiple functional units, inc several managed by
964 hwmon/pc87360 driver. Tested with PC-87366
965
966 If compiled as a module, it will be called pc8736x_gpio.
967
968config NSC_GPIO
969 tristate "NatSemi Base GPIO Support"
Dave Jones699352c2006-06-29 02:24:32 -0700970 depends on X86_32
Jim Cromie7a8e2a52006-06-27 02:54:27 -0700971 # selected by SCx200_GPIO and PC8736x_GPIO
972 # what about 2 selectors differing: m != y
973 help
974 Common support used (and needed) by scx200_gpio and
975 pc8736x_gpio drivers. If those drivers are built as
976 modules, this one will be too, named nsc_gpio
977
Ben Gardnere3291132006-01-09 20:51:29 -0800978config CS5535_GPIO
979 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
980 depends on X86_32
981 help
982 Give userspace access to the GPIO pins on the AMD CS5535 and
983 CS5536 Geode companion devices.
984
985 If compiled as a module, it will be called cs5535_gpio.
986
Yoichi Yuasae400bae2005-06-21 17:15:56 -0700987config GPIO_VR41XX
988 tristate "NEC VR4100 series General-purpose I/O Unit support"
989 depends on CPU_VR41XX
990
Linus Torvalds1da177e2005-04-16 15:20:36 -0700991config RAW_DRIVER
992 tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)"
David Howells93614012006-09-30 20:45:40 +0200993 depends on BLOCK
Linus Torvalds1da177e2005-04-16 15:20:36 -0700994 help
995 The raw driver permits block devices to be bound to /dev/raw/rawN.
996 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
997 See the raw(8) manpage for more details.
998
Adrian Bunk98e7f292005-06-25 14:59:37 -0700999 The raw driver is deprecated and will be removed soon.
1000 Applications should simply open the device (eg /dev/hda1)
Linus Torvalds1da177e2005-04-16 15:20:36 -07001001 with the O_DIRECT flag.
1002
Andrew Morton0de502a2005-12-12 00:37:41 -08001003config MAX_RAW_DEVS
1004 int "Maximum number of RAW devices to support (1-8192)"
1005 depends on RAW_DRIVER
1006 default "256"
1007 help
1008 The maximum number of RAW devices that are supported.
1009 Default is 256. Increase this number in case you need lots of
1010 raw devices.
1011
Linus Torvalds1da177e2005-04-16 15:20:36 -07001012config HPET
1013 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1014 default n
1015 depends on ACPI
1016 help
1017 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1018 open selects one of the timers supported by the HPET. The timers are
Matt LaPlante3cb2fcc2006-11-30 05:22:59 +01001019 non-periodic and/or periodic.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001020
1021config HPET_RTC_IRQ
1022 bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC
1023 default n
1024 depends on HPET
1025 help
1026 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1027 is assumed the platform called hpet_alloc with the RTC IRQ values for
1028 the HPET timers.
1029
1030config HPET_MMAP
1031 bool "Allow mmap of HPET"
1032 default y
1033 depends on HPET
1034 help
1035 If you say Y here, user applications will be able to mmap
1036 the HPET registers.
1037
1038 In some hardware implementations, the page containing HPET
1039 registers may also contain other things that shouldn't be
1040 exposed to the user. If this applies to your hardware,
1041 say N here.
1042
Linus Torvalds1da177e2005-04-16 15:20:36 -07001043config HANGCHECK_TIMER
1044 tristate "Hangcheck timer"
Jan Glauber3633b042006-02-01 03:06:34 -08001045 depends on X86 || IA64 || PPC64
Linus Torvalds1da177e2005-04-16 15:20:36 -07001046 help
1047 The hangcheck-timer module detects when the system has gone
1048 out to lunch past a certain margin. It can reboot the system
1049 or merely print a warning.
1050
1051config MMTIMER
1052 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1053 depends on IA64_GENERIC || IA64_SGI_SN2
1054 default y
1055 help
1056 The mmtimer device allows direct userspace access to the
1057 Altix system timer.
1058
1059source "drivers/char/tpm/Kconfig"
1060
Mark Gross1a80ba82005-10-30 15:02:55 -08001061config TELCLOCK
Mark Gross03154a22007-03-06 13:58:45 -08001062 tristate "Telecom clock driver for ATCA SBC"
Geert Uytterhoeven4d99bfa2006-10-16 19:59:43 +02001063 depends on EXPERIMENTAL && X86
Mark Gross1a80ba82005-10-30 15:02:55 -08001064 default n
1065 help
Mark Gross03154a22007-03-06 13:58:45 -08001066 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1067 ATCA computers and allows direct userspace access to the
1068 configuration of the telecom clock configuration settings. This
1069 device is used for hardware synchronization across the ATCA backplane
1070 fabric. Upon loading, the driver exports a sysfs directory,
1071 /sys/devices/platform/telco_clock, with a number of files for
1072 controlling the behavior of this hardware.
Mark Gross1a80ba82005-10-30 15:02:55 -08001073
Linus Torvalds1da177e2005-04-16 15:20:36 -07001074endmenu
1075