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