Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # Character device configuration | |
3 | # | |
4 | ||
5 | menu "Character devices" | |
6 | ||
7 | config VT | |
8 | bool "Virtual terminal" if EMBEDDED | |
9 | select INPUT | |
10 | default y if !VIOCONS | |
11 | ---help--- | |
12 | If you say Y here, you will get support for terminal devices with | |
13 | display and keyboard devices. These are called "virtual" because you | |
14 | can run several virtual terminals (also called virtual consoles) on | |
15 | one physical terminal. This is rather useful, for example one | |
16 | virtual terminal can collect system messages and warnings, another | |
17 | one can be used for a text-mode user session, and a third could run | |
18 | an X session, all in parallel. Switching between virtual terminals | |
19 | is done with certain key combinations, usually Alt-<function key>. | |
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 | ||
38 | config VT_CONSOLE | |
39 | bool "Support for console on virtual terminal" if EMBEDDED | |
40 | depends on VT | |
41 | default y | |
42 | ---help--- | |
43 | The system console is the device which receives all kernel messages | |
44 | and warnings and which allows logins in single user mode. If you | |
45 | answer Y here, a virtual terminal (the device used to interact with | |
46 | a physical terminal) can be used as system console. This is the most | |
47 | common mode of operations, so you should say Y here unless you want | |
48 | the kernel messages be output only to a serial port (in which case | |
49 | you should say Y to "Console on serial port", below). | |
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 | ||
60 | config HW_CONSOLE | |
61 | bool | |
62 | depends on VT && !S390 && !UML | |
63 | default y | |
64 | ||
13ae6645 AD |
65 | config 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 | ||
1da177e4 LT |
82 | config 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 | ||
98 | config COMPUTONE | |
99 | tristate "Computone IntelliPort Plus serial support" | |
3b4709a6 | 100 | depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI) |
1da177e4 LT |
101 | ---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 | ||
113 | config 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 | ||
128 | config 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 | ||
144 | config 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 | ||
156 | config DIGIEPCA | |
157 | tristate "Digiboard Intelligent Async Support" | |
f2cf8e25 | 158 | depends on SERIAL_NONSTANDARD |
1da177e4 LT |
159 | ---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 | ||
171 | config ESPSERIAL | |
172 | tristate "Hayes ESP serial port support" | |
33f0f88f | 173 | depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API |
1da177e4 LT |
174 | 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 | ||
184 | config MOXA_INTELLIO | |
185 | tristate "Moxa Intellio support" | |
33f0f88f | 186 | depends on SERIAL_NONSTANDARD |
1da177e4 LT |
187 | 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 | ||
193 | config MOXA_SMARTIO | |
194 | tristate "Moxa SmartIO support" | |
1d25240f | 195 | depends on SERIAL_NONSTANDARD |
1da177e4 LT |
196 | 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 | ||
037ad48b JS |
204 | config MOXA_SMARTIO_NEW |
205 | tristate "Moxa SmartIO support v. 2.0 (EXPERIMENTAL)" | |
fb0c9295 | 206 | depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA) |
037ad48b JS |
207 | 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 | ||
1da177e4 LT |
219 | config ISI |
220 | tristate "Multi-Tech multiport card support (EXPERIMENTAL)" | |
a3808ac1 | 221 | depends on SERIAL_NONSTANDARD && PCI |
5ff2a7e2 | 222 | select FW_LOADER |
1da177e4 LT |
223 | 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 | ||
229 | config SYNCLINK | |
230 | tristate "Microgate SyncLink card support" | |
a5532606 | 231 | depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API |
1da177e4 LT |
232 | 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 | ||
242 | config SYNCLINKMP | |
243 | tristate "SyncLink Multiport support" | |
f91f4d92 | 244 | depends on SERIAL_NONSTANDARD |
1da177e4 LT |
245 | 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 | ||
705b6c7b PF |
256 | config SYNCLINK_GT |
257 | tristate "SyncLink GT/AC support" | |
8ef9cf31 | 258 | depends on SERIAL_NONSTANDARD && PCI |
705b6c7b PF |
259 | 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 | ||
1da177e4 LT |
264 | config 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 | ||
276 | config 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 | ||
289 | config 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 | ||
303 | config 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 | ||
313 | config SX | |
314 | tristate "Specialix SX (and SI) card support" | |
3468a33e | 315 | depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA) |
1da177e4 LT |
316 | 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 | ||
324 | config RIO | |
325 | tristate "Specialix RIO system support" | |
655fdeab | 326 | depends on SERIAL_NONSTANDARD |
1da177e4 LT |
327 | 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 | ||
333 | config 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 | ||
341 | config 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 | ||
353 | config 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 | ||
364 | config 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 | ||
375 | config 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 | ||
382 | config 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 | ||
1da177e4 LT |
389 | config A2232 |
390 | tristate "Commodore A2232 serial support (EXPERIMENTAL)" | |
391 | depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP | |
392 | ---help--- | |
393 | This option supports the 2232 7-port serial card shipped with the | |
394 | Amiga 2000 and other Zorro-bus machines, dating from 1989. At | |
395 | a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip | |
396 | each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The | |
397 | ports were connected with 8 pin DIN connectors on the card bracket, | |
398 | for which 8 pin to DB25 adapters were supplied. The card also had | |
399 | jumpers internally to toggle various pinning configurations. | |
400 | ||
401 | This driver can be built as a module; but then "generic_serial" | |
402 | will also be built as a module. This has to be loaded before | |
403 | "ser_a2232". If you want to do this, answer M here. | |
404 | ||
405 | config SGI_SNSC | |
406 | bool "SGI Altix system controller communication support" | |
407 | depends on (IA64_SGI_SN2 || IA64_GENERIC) | |
408 | help | |
409 | If you have an SGI Altix and you want to enable system | |
410 | controller communication from user space (you want this!), | |
411 | say Y. Otherwise, say N. | |
412 | ||
e1e19747 BL |
413 | config SGI_TIOCX |
414 | bool "SGI TIO CX driver support" | |
415 | depends on (IA64_SGI_SN2 || IA64_GENERIC) | |
416 | help | |
417 | If you have an SGI Altix and you have fpga devices attached | |
418 | to your TIO, say Y here, otherwise say N. | |
419 | ||
420 | config SGI_MBCS | |
421 | tristate "SGI FPGA Core Services driver support" | |
ae40aae9 | 422 | depends on SGI_TIOCX |
e1e19747 BL |
423 | help |
424 | If you have an SGI Altix with an attached SABrick | |
425 | say Y or M here, otherwise say N. | |
426 | ||
1da177e4 LT |
427 | source "drivers/serial/Kconfig" |
428 | ||
429 | config UNIX98_PTYS | |
430 | bool "Unix98 PTY support" if EMBEDDED | |
431 | default y | |
432 | ---help--- | |
433 | A pseudo terminal (PTY) is a software device consisting of two | |
434 | halves: a master and a slave. The slave device behaves identical to | |
435 | a physical terminal; the master device is used by a process to | |
436 | read data from and write data to the slave, thereby emulating a | |
437 | terminal. Typical programs for the master side are telnet servers | |
438 | and xterms. | |
439 | ||
440 | Linux has traditionally used the BSD-like names /dev/ptyxx for | |
441 | masters and /dev/ttyxx for slaves of pseudo terminals. This scheme | |
442 | has a number of problems. The GNU C library glibc 2.1 and later, | |
443 | however, supports the Unix98 naming standard: in order to acquire a | |
444 | pseudo terminal, a process opens /dev/ptmx; the number of the pseudo | |
445 | terminal is then made available to the process and the pseudo | |
446 | terminal slave can be accessed as /dev/pts/<number>. What was | |
447 | traditionally /dev/ttyp2 will then be /dev/pts/2, for example. | |
448 | ||
449 | All modern Linux systems use the Unix98 ptys. Say Y unless | |
450 | you're on an embedded system and want to conserve memory. | |
451 | ||
452 | config LEGACY_PTYS | |
453 | bool "Legacy (BSD) PTY support" | |
454 | default y | |
455 | ---help--- | |
456 | A pseudo terminal (PTY) is a software device consisting of two | |
457 | halves: a master and a slave. The slave device behaves identical to | |
458 | a physical terminal; the master device is used by a process to | |
459 | read data from and write data to the slave, thereby emulating a | |
460 | terminal. Typical programs for the master side are telnet servers | |
461 | and xterms. | |
462 | ||
463 | Linux has traditionally used the BSD-like names /dev/ptyxx | |
464 | for masters and /dev/ttyxx for slaves of pseudo | |
465 | terminals. This scheme has a number of problems, including | |
466 | security. This option enables these legacy devices; on most | |
467 | systems, it is safe to say N. | |
468 | ||
469 | ||
470 | config LEGACY_PTY_COUNT | |
471 | int "Maximum number of legacy PTY in use" | |
472 | depends on LEGACY_PTYS | |
473 | range 1 256 | |
474 | default "256" | |
475 | ---help--- | |
476 | The maximum number of legacy PTYs that can be used at any one time. | |
477 | The default is 256, and should be more than enough. Embedded | |
478 | systems may want to reduce this to save memory. | |
479 | ||
480 | When not in use, each legacy PTY occupies 12 bytes on 32-bit | |
481 | architectures and 24 bytes on 64-bit architectures. | |
482 | ||
a45b8395 BH |
483 | config BRIQ_PANEL |
484 | tristate 'Total Impact briQ front panel driver' | |
2818c5de | 485 | depends on PPC_CHRP |
a45b8395 BH |
486 | ---help--- |
487 | The briQ is a small footprint CHRP computer with a frontpanel VFD, a | |
488 | tristate led and two switches. It is the size of a CDROM drive. | |
489 | ||
490 | If you have such one and want anything showing on the VFD then you | |
491 | must answer Y here. | |
492 | ||
493 | To compile this driver as a module, choose M here: the | |
494 | module will be called briq_panel. | |
495 | ||
496 | It's safe to say N here. | |
497 | ||
1da177e4 LT |
498 | config PRINTER |
499 | tristate "Parallel printer support" | |
500 | depends on PARPORT | |
501 | ---help--- | |
502 | If you intend to attach a printer to the parallel port of your Linux | |
503 | box (as opposed to using a serial printer; if the connector at the | |
504 | printer has 9 or 25 holes ["female"], then it's serial), say Y. | |
505 | Also read the Printing-HOWTO, available from | |
506 | <http://www.tldp.org/docs.html#howto>. | |
507 | ||
508 | It is possible to share one parallel port among several devices | |
509 | (e.g. printer and ZIP drive) and it is safe to compile the | |
510 | corresponding drivers into the kernel. | |
511 | ||
512 | To compile this driver as a module, choose M here and read | |
513 | <file:Documentation/parport.txt>. The module will be called lp. | |
514 | ||
515 | If you have several parallel ports, you can specify which ports to | |
516 | use with the "lp" kernel command line option. (Try "man bootparam" | |
517 | or see the documentation of your boot loader (lilo or loadlin) about | |
518 | how to pass options to the kernel at boot time.) The syntax of the | |
519 | "lp" command line option can be found in <file:drivers/char/lp.c>. | |
520 | ||
521 | If you have more than 8 printers, you need to increase the LP_NO | |
522 | macro in lp.c and the PARPORT_MAX macro in parport.h. | |
523 | ||
524 | config LP_CONSOLE | |
525 | bool "Support for console on line printer" | |
526 | depends on PRINTER | |
527 | ---help--- | |
528 | If you want kernel messages to be printed out as they occur, you | |
529 | can have a console on the printer. This option adds support for | |
530 | doing that; to actually get it to happen you need to pass the | |
531 | option "console=lp0" to the kernel at boot time. | |
532 | ||
533 | If the printer is out of paper (or off, or unplugged, or too | |
534 | busy..) the kernel will stall until the printer is ready again. | |
535 | By defining CONSOLE_LP_STRICT to 0 (at your own risk) you | |
536 | can make the kernel continue when this happens, | |
537 | but it'll lose the kernel messages. | |
538 | ||
539 | If unsure, say N. | |
540 | ||
541 | config PPDEV | |
542 | tristate "Support for user-space parallel port device drivers" | |
543 | depends on PARPORT | |
544 | ---help--- | |
545 | Saying Y to this adds support for /dev/parport device nodes. This | |
546 | is needed for programs that want portable access to the parallel | |
547 | port, for instance deviceid (which displays Plug-and-Play device | |
548 | IDs). | |
549 | ||
550 | This is the parallel port equivalent of SCSI generic support (sg). | |
551 | It is safe to say N to this -- it is not needed for normal printing | |
552 | or parallel port CD-ROM/disk support. | |
553 | ||
554 | To compile this driver as a module, choose M here: the | |
555 | module will be called ppdev. | |
556 | ||
557 | If unsure, say N. | |
558 | ||
559 | config TIPAR | |
560 | tristate "Texas Instruments parallel link cable support" | |
561 | depends on PARPORT | |
562 | ---help--- | |
563 | If you own a Texas Instruments graphing calculator and use a | |
564 | parallel link cable, then you might be interested in this driver. | |
565 | ||
566 | If you enable this driver, you will be able to communicate with | |
567 | your calculator through a set of device nodes under /dev. The | |
568 | main advantage of this driver is that you don't have to be root | |
569 | to use this precise link cable (depending on the permissions on | |
570 | the device nodes, though). | |
571 | ||
572 | To compile this driver as a module, choose M here: the | |
573 | module will be called tipar. | |
574 | ||
575 | If you don't know what a parallel link cable is or what a Texas | |
576 | Instruments graphing calculator is, then you probably don't need this | |
577 | driver. | |
578 | ||
579 | If unsure, say N. | |
580 | ||
45d607ed RA |
581 | config HVC_DRIVER |
582 | bool | |
583 | help | |
584 | Users of pSeries machines that want to utilize the hvc console front-end | |
585 | module for their backend console driver should select this option. | |
586 | It will automatically be selected if one of the back-end console drivers | |
587 | is selected. | |
588 | ||
589 | ||
1da177e4 LT |
590 | config HVC_CONSOLE |
591 | bool "pSeries Hypervisor Virtual Console support" | |
592 | depends on PPC_PSERIES | |
45d607ed | 593 | select HVC_DRIVER |
1da177e4 LT |
594 | help |
595 | pSeries machines when partitioned support a hypervisor virtual | |
596 | console. This driver allows each pSeries partition to have a console | |
597 | which is accessed via the HMC. | |
598 | ||
8bff05b0 SR |
599 | config HVC_ISERIES |
600 | bool "iSeries Hypervisor Virtual Console support" | |
601 | depends on PPC_ISERIES && !VIOCONS | |
602 | select HVC_DRIVER | |
603 | help | |
604 | iSeries machines support a hypervisor virtual console. | |
605 | ||
f4d1749e AB |
606 | config HVC_RTAS |
607 | bool "IBM RTAS Console support" | |
608 | depends on PPC_RTAS | |
609 | select HVC_DRIVER | |
610 | help | |
611 | IBM Console device driver which makes use of RTAS | |
612 | ||
3cdc20e5 IK |
613 | config HVC_BEAT |
614 | bool "Toshiba's Beat Hypervisor Console support" | |
615 | depends on PPC_CELLEB | |
616 | select HVC_DRIVER | |
617 | help | |
618 | Toshiba's Cell Reference Set Beat Console device driver | |
619 | ||
1da177e4 LT |
620 | config HVCS |
621 | tristate "IBM Hypervisor Virtual Console Server support" | |
622 | depends on PPC_PSERIES | |
623 | help | |
624 | Partitionable IBM Power5 ppc64 machines allow hosting of | |
625 | firmware virtual consoles from one Linux partition by | |
626 | another Linux partition. This driver allows console data | |
627 | from Linux partitions to be accessed through TTY device | |
628 | interfaces in the device tree of a Linux partition running | |
629 | this driver. | |
630 | ||
631 | To compile this driver as a module, choose M here: the | |
632 | module will be called hvcs.ko. Additionally, this module | |
633 | will depend on arch specific APIs exported from hvcserver.ko | |
634 | which will also be compiled when this driver is built as a | |
635 | module. | |
636 | ||
637 | source "drivers/char/ipmi/Kconfig" | |
638 | ||
639 | source "drivers/char/watchdog/Kconfig" | |
640 | ||
641 | config DS1620 | |
642 | tristate "NetWinder thermometer support" | |
643 | depends on ARCH_NETWINDER | |
644 | help | |
645 | Say Y here to include support for the thermal management hardware | |
646 | found in the NetWinder. This driver allows the user to control the | |
647 | temperature set points and to read the current temperature. | |
648 | ||
649 | It is also possible to say M here to build it as a module (ds1620) | |
650 | It is recommended to be used on a NetWinder, but it is not a | |
651 | necessity. | |
652 | ||
653 | config NWBUTTON | |
654 | tristate "NetWinder Button" | |
655 | depends on ARCH_NETWINDER | |
656 | ---help--- | |
657 | If you say Y here and create a character device node /dev/nwbutton | |
658 | with major and minor numbers 10 and 158 ("man mknod"), then every | |
659 | time the orange button is pressed a number of times, the number of | |
660 | times the button was pressed will be written to that device. | |
661 | ||
662 | This is most useful for applications, as yet unwritten, which | |
663 | perform actions based on how many times the button is pressed in a | |
664 | row. | |
665 | ||
666 | Do not hold the button down for too long, as the driver does not | |
667 | alter the behaviour of the hardware reset circuitry attached to the | |
668 | button; it will still execute a hard reset if the button is held | |
669 | down for longer than approximately five seconds. | |
670 | ||
671 | To compile this driver as a module, choose M here: the | |
672 | module will be called nwbutton. | |
673 | ||
674 | Most people will answer Y to this question and "Reboot Using Button" | |
675 | below to be able to initiate a system shutdown from the button. | |
676 | ||
677 | config NWBUTTON_REBOOT | |
678 | bool "Reboot Using Button" | |
679 | depends on NWBUTTON | |
680 | help | |
681 | If you say Y here, then you will be able to initiate a system | |
682 | shutdown and reboot by pressing the orange button a number of times. | |
683 | The number of presses to initiate the shutdown is two by default, | |
684 | but this can be altered by modifying the value of NUM_PRESSES_REBOOT | |
685 | in nwbutton.h and recompiling the driver or, if you compile the | |
686 | driver as a module, you can specify the number of presses at load | |
687 | time with "insmod button reboot_count=<something>". | |
688 | ||
689 | config NWFLASH | |
690 | tristate "NetWinder flash support" | |
691 | depends on ARCH_NETWINDER | |
692 | ---help--- | |
693 | If you say Y here and create a character device /dev/flash with | |
694 | major 10 and minor 160 you can manipulate the flash ROM containing | |
695 | the NetWinder firmware. Be careful as accidentally overwriting the | |
696 | flash contents can render your computer unbootable. On no account | |
697 | allow random users access to this device. :-) | |
698 | ||
699 | To compile this driver as a module, choose M here: the | |
700 | module will be called nwflash. | |
701 | ||
702 | If you're not sure, say N. | |
703 | ||
844dd05f MB |
704 | source "drivers/char/hw_random/Kconfig" |
705 | ||
1da177e4 LT |
706 | config NVRAM |
707 | tristate "/dev/nvram support" | |
0d078f6f | 708 | depends on ATARI || X86 || ARM || GENERIC_NVRAM |
1da177e4 LT |
709 | ---help--- |
710 | If you say Y here and create a character special file /dev/nvram | |
711 | with major number 10 and minor number 144 using mknod ("man mknod"), | |
712 | you get read and write access to the extra bytes of non-volatile | |
713 | memory in the real time clock (RTC), which is contained in every PC | |
714 | and most Ataris. The actual number of bytes varies, depending on the | |
715 | nvram in the system, but is usually 114 (128-14 for the RTC). | |
716 | ||
717 | This memory is conventionally called "CMOS RAM" on PCs and "NVRAM" | |
718 | on Ataris. /dev/nvram may be used to view settings there, or to | |
719 | change them (with some utility). It could also be used to frequently | |
720 | save a few bits of very important data that may not be lost over | |
721 | power-off and for which writing to disk is too insecure. Note | |
722 | however that most NVRAM space in a PC belongs to the BIOS and you | |
723 | should NEVER idly tamper with it. See Ralf Brown's interrupt list | |
724 | for a guide to the use of CMOS bytes by your BIOS. | |
725 | ||
726 | On Atari machines, /dev/nvram is always configured and does not need | |
727 | to be selected. | |
728 | ||
729 | To compile this driver as a module, choose M here: the | |
730 | module will be called nvram. | |
731 | ||
732 | config RTC | |
733 | tristate "Enhanced Real Time Clock Support" | |
91550f71 | 734 | depends on !PPC && !PARISC && !IA64 && !M68K && (!SPARC || PCI) && !FRV && !ARM && !SUPERH |
1da177e4 LT |
735 | ---help--- |
736 | If you say Y here and create a character special file /dev/rtc with | |
737 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
738 | will get access to the real time clock (or hardware clock) built | |
739 | into your computer. | |
740 | ||
741 | Every PC has such a clock built in. It can be used to generate | |
742 | signals from as low as 1Hz up to 8192Hz, and can also be used | |
743 | as a 24 hour alarm. It reports status information via the file | |
744 | /proc/driver/rtc and its behaviour is set by various ioctls on | |
745 | /dev/rtc. | |
746 | ||
747 | If you run Linux on a multiprocessor machine and said Y to | |
748 | "Symmetric Multi Processing" above, you should say Y here to read | |
749 | and set the RTC in an SMP compatible fashion. | |
750 | ||
751 | If you think you have a use for such a device (such as periodic data | |
752 | sampling), then say Y here, and read <file:Documentation/rtc.txt> | |
753 | for details. | |
754 | ||
755 | To compile this driver as a module, choose M here: the | |
756 | module will be called rtc. | |
757 | ||
758 | config SGI_DS1286 | |
759 | tristate "SGI DS1286 RTC support" | |
760 | depends on SGI_IP22 | |
761 | help | |
762 | If you say Y here and create a character special file /dev/rtc with | |
763 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
764 | will get access to the real time clock built into your computer. | |
765 | Every SGI has such a clock built in. It reports status information | |
766 | via the file /proc/rtc and its behaviour is set by various ioctls on | |
767 | /dev/rtc. | |
768 | ||
769 | config SGI_IP27_RTC | |
770 | bool "SGI M48T35 RTC support" | |
771 | depends on SGI_IP27 | |
772 | help | |
773 | If you say Y here and create a character special file /dev/rtc with | |
774 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
775 | will get access to the real time clock built into your computer. | |
776 | Every SGI has such a clock built in. It reports status information | |
777 | via the file /proc/rtc and its behaviour is set by various ioctls on | |
778 | /dev/rtc. | |
779 | ||
780 | config GEN_RTC | |
781 | tristate "Generic /dev/rtc emulation" | |
2919b510 | 782 | depends on RTC!=y && !IA64 && !ARM && !M32R && !SPARC && !FRV |
1da177e4 LT |
783 | ---help--- |
784 | If you say Y here and create a character special file /dev/rtc with | |
785 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
786 | will get access to the real time clock (or hardware clock) built | |
787 | into your computer. | |
788 | ||
789 | It reports status information via the file /proc/driver/rtc and its | |
790 | behaviour is set by various ioctls on /dev/rtc. If you enable the | |
791 | "extended RTC operation" below it will also provide an emulation | |
792 | for RTC_UIE which is required by some programs and may improve | |
793 | precision in some cases. | |
794 | ||
795 | To compile this driver as a module, choose M here: the | |
796 | module will be called genrtc. | |
797 | ||
798 | config GEN_RTC_X | |
799 | bool "Extended RTC operation" | |
800 | depends on GEN_RTC | |
801 | help | |
802 | Provides an emulation for RTC_UIE which is required by some programs | |
803 | and may improve precision of the generic RTC support in some cases. | |
804 | ||
805 | config EFI_RTC | |
806 | bool "EFI Real Time Clock Services" | |
807 | depends on IA64 | |
808 | ||
809 | config DS1302 | |
810 | tristate "DS1302 RTC support" | |
811 | depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT) | |
812 | help | |
813 | If you say Y here and create a character special file /dev/rtc with | |
814 | major number 121 and minor number 0 using mknod ("man mknod"), you | |
815 | will get access to the real time clock (or hardware clock) built | |
816 | into your computer. | |
817 | ||
1da177e4 LT |
818 | config COBALT_LCD |
819 | bool "Support for Cobalt LCD" | |
820 | depends on MIPS_COBALT | |
821 | help | |
822 | This option enables support for the LCD display and buttons found | |
823 | on Cobalt systems through a misc device. | |
824 | ||
825 | config DTLK | |
826 | tristate "Double Talk PC internal speech card support" | |
827 | help | |
828 | This driver is for the DoubleTalk PC, a speech synthesizer | |
829 | manufactured by RC Systems (<http://www.rcsys.com/>). It is also | |
830 | called the `internal DoubleTalk'. | |
831 | ||
832 | To compile this driver as a module, choose M here: the | |
833 | module will be called dtlk. | |
834 | ||
835 | config R3964 | |
836 | tristate "Siemens R3964 line discipline" | |
837 | ---help--- | |
838 | This driver allows synchronous communication with devices using the | |
839 | Siemens R3964 packet protocol. Unless you are dealing with special | |
840 | hardware like PLCs, you are unlikely to need this. | |
841 | ||
842 | To compile this driver as a module, choose M here: the | |
843 | module will be called n_r3964. | |
844 | ||
845 | If unsure, say N. | |
846 | ||
847 | config APPLICOM | |
848 | tristate "Applicom intelligent fieldbus card support" | |
849 | depends on PCI | |
850 | ---help--- | |
851 | This driver provides the kernel-side support for the intelligent | |
852 | fieldbus cards made by Applicom International. More information | |
853 | about these cards can be found on the WWW at the address | |
854 | <http://www.applicom-int.com/>, or by email from David Woodhouse | |
855 | <dwmw2@infradead.org>. | |
856 | ||
857 | To compile this driver as a module, choose M here: the | |
858 | module will be called applicom. | |
859 | ||
860 | If unsure, say N. | |
861 | ||
862 | config SONYPI | |
863 | tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)" | |
864 | depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT | |
865 | ---help--- | |
866 | This driver enables access to the Sony Programmable I/O Control | |
867 | Device which can be found in many (all ?) Sony Vaio laptops. | |
868 | ||
869 | If you have one of those laptops, read | |
870 | <file:Documentation/sonypi.txt>, and say Y or M here. | |
871 | ||
872 | To compile this driver as a module, choose M here: the | |
873 | module will be called sonypi. | |
874 | ||
875 | config TANBAC_TB0219 | |
876 | tristate "TANBAC TB0219 base board support" | |
bef1f402 | 877 | depends on TANBAC_TB022X |
584e1236 | 878 | select GPIO_VR41XX |
1da177e4 | 879 | |
1da177e4 LT |
880 | source "drivers/char/agp/Kconfig" |
881 | ||
882 | source "drivers/char/drm/Kconfig" | |
883 | ||
884 | source "drivers/char/pcmcia/Kconfig" | |
885 | ||
886 | config MWAVE | |
887 | tristate "ACP Modem (Mwave) support" | |
888 | depends on X86 | |
889 | select SERIAL_8250 | |
890 | ---help--- | |
891 | The ACP modem (Mwave) for Linux is a WinModem. It is composed of a | |
892 | kernel driver and a user level application. Together these components | |
893 | support direct attachment to public switched telephone networks (PSTNs) | |
894 | and support selected world wide countries. | |
895 | ||
896 | This version of the ACP Modem driver supports the IBM Thinkpad 600E, | |
897 | 600, and 770 that include on board ACP modem hardware. | |
898 | ||
899 | The modem also supports the standard communications port interface | |
900 | (ttySx) and is compatible with the Hayes AT Command Set. | |
901 | ||
902 | The user level application needed to use this driver can be found at | |
903 | the IBM Linux Technology Center (LTC) web site: | |
904 | <http://www.ibm.com/linux/ltc/>. | |
905 | ||
906 | If you own one of the above IBM Thinkpads which has the Mwave chipset | |
907 | in it, say Y. | |
908 | ||
909 | To compile this driver as a module, choose M here: the | |
910 | module will be called mwave. | |
911 | ||
912 | config SCx200_GPIO | |
913 | tristate "NatSemi SCx200 GPIO Support" | |
914 | depends on SCx200 | |
7a8e2a5e | 915 | select NSC_GPIO |
1da177e4 LT |
916 | help |
917 | Give userspace access to the GPIO pins on the National | |
918 | Semiconductor SCx200 processors. | |
919 | ||
920 | If compiled as a module, it will be called scx200_gpio. | |
921 | ||
7a8e2a5e JC |
922 | config PC8736x_GPIO |
923 | tristate "NatSemi PC8736x GPIO Support" | |
924 | depends on X86 | |
925 | default SCx200_GPIO # mostly N | |
926 | select NSC_GPIO # needed for support routines | |
927 | help | |
928 | Give userspace access to the GPIO pins on the National | |
929 | Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip | |
930 | has multiple functional units, inc several managed by | |
931 | hwmon/pc87360 driver. Tested with PC-87366 | |
932 | ||
933 | If compiled as a module, it will be called pc8736x_gpio. | |
934 | ||
935 | config NSC_GPIO | |
936 | tristate "NatSemi Base GPIO Support" | |
699352c3 | 937 | depends on X86_32 |
7a8e2a5e JC |
938 | # selected by SCx200_GPIO and PC8736x_GPIO |
939 | # what about 2 selectors differing: m != y | |
940 | help | |
941 | Common support used (and needed) by scx200_gpio and | |
942 | pc8736x_gpio drivers. If those drivers are built as | |
943 | modules, this one will be too, named nsc_gpio | |
944 | ||
e329113c BG |
945 | config CS5535_GPIO |
946 | tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)" | |
947 | depends on X86_32 | |
948 | help | |
949 | Give userspace access to the GPIO pins on the AMD CS5535 and | |
950 | CS5536 Geode companion devices. | |
951 | ||
952 | If compiled as a module, it will be called cs5535_gpio. | |
953 | ||
e400bae9 YY |
954 | config GPIO_VR41XX |
955 | tristate "NEC VR4100 series General-purpose I/O Unit support" | |
956 | depends on CPU_VR41XX | |
957 | ||
1da177e4 LT |
958 | config RAW_DRIVER |
959 | tristate "RAW driver (/dev/raw/rawN) (OBSOLETE)" | |
9361401e | 960 | depends on BLOCK |
1da177e4 LT |
961 | help |
962 | The raw driver permits block devices to be bound to /dev/raw/rawN. | |
963 | Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O. | |
964 | See the raw(8) manpage for more details. | |
965 | ||
98e7f294 AB |
966 | The raw driver is deprecated and will be removed soon. |
967 | Applications should simply open the device (eg /dev/hda1) | |
1da177e4 LT |
968 | with the O_DIRECT flag. |
969 | ||
0de502aa AM |
970 | config MAX_RAW_DEVS |
971 | int "Maximum number of RAW devices to support (1-8192)" | |
972 | depends on RAW_DRIVER | |
973 | default "256" | |
974 | help | |
975 | The maximum number of RAW devices that are supported. | |
976 | Default is 256. Increase this number in case you need lots of | |
977 | raw devices. | |
978 | ||
1da177e4 LT |
979 | config HPET |
980 | bool "HPET - High Precision Event Timer" if (X86 || IA64) | |
981 | default n | |
982 | depends on ACPI | |
983 | help | |
984 | If you say Y here, you will have a miscdevice named "/dev/hpet/". Each | |
985 | open selects one of the timers supported by the HPET. The timers are | |
3cb2fccc | 986 | non-periodic and/or periodic. |
1da177e4 LT |
987 | |
988 | config HPET_RTC_IRQ | |
989 | bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC | |
990 | default n | |
991 | depends on HPET | |
992 | help | |
993 | If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It | |
994 | is assumed the platform called hpet_alloc with the RTC IRQ values for | |
995 | the HPET timers. | |
996 | ||
997 | config HPET_MMAP | |
998 | bool "Allow mmap of HPET" | |
999 | default y | |
1000 | depends on HPET | |
1001 | help | |
1002 | If you say Y here, user applications will be able to mmap | |
1003 | the HPET registers. | |
1004 | ||
1005 | In some hardware implementations, the page containing HPET | |
1006 | registers may also contain other things that shouldn't be | |
1007 | exposed to the user. If this applies to your hardware, | |
1008 | say N here. | |
1009 | ||
1da177e4 LT |
1010 | config HANGCHECK_TIMER |
1011 | tristate "Hangcheck timer" | |
3633b047 | 1012 | depends on X86 || IA64 || PPC64 |
1da177e4 LT |
1013 | help |
1014 | The hangcheck-timer module detects when the system has gone | |
1015 | out to lunch past a certain margin. It can reboot the system | |
1016 | or merely print a warning. | |
1017 | ||
1018 | config MMTIMER | |
1019 | tristate "MMTIMER Memory mapped RTC for SGI Altix" | |
1020 | depends on IA64_GENERIC || IA64_SGI_SN2 | |
1021 | default y | |
1022 | help | |
1023 | The mmtimer device allows direct userspace access to the | |
1024 | Altix system timer. | |
1025 | ||
1026 | source "drivers/char/tpm/Kconfig" | |
1027 | ||
1a80ba88 MG |
1028 | config TELCLOCK |
1029 | tristate "Telecom clock driver for MPBL0010 ATCA SBC" | |
4d99bfac | 1030 | depends on EXPERIMENTAL && X86 |
1a80ba88 MG |
1031 | default n |
1032 | help | |
1033 | The telecom clock device is specific to the MPBL0010 ATCA computer and | |
1034 | allows direct userspace access to the configuration of the telecom clock | |
1035 | configuration settings. This device is used for hardware synchronization | |
1036 | across the ATCA backplane fabric. Upon loading, the driver exports a | |
1037 | sysfs directory, /sys/devices/platform/telco_clock, with a number of | |
1038 | files for controlling the behavior of this hardware. | |
1039 | ||
1da177e4 LT |
1040 | endmenu |
1041 |