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 | |
abf3ea1b | 9 | depends on !S390 |
1da177e4 LT |
10 | 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 | ||
39 | config 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 | ||
61 | config HW_CONSOLE | |
62 | bool | |
63 | depends on VT && !S390 && !UML | |
64 | default y | |
65 | ||
13ae6645 AD |
66 | config 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 | ||
1da177e4 LT |
83 | config SERIAL_NONSTANDARD |
84 | bool "Non-standard serial port support" | |
eeca7a36 | 85 | depends on HAS_IOMEM |
1da177e4 LT |
86 | ---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 | ||
100 | config COMPUTONE | |
101 | tristate "Computone IntelliPort Plus serial support" | |
3b4709a6 | 102 | depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI) |
1da177e4 LT |
103 | ---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 | ||
115 | config ROCKETPORT | |
116 | tristate "Comtrol RocketPort support" | |
27d41718 | 117 | depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI) |
1da177e4 LT |
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 | ||
130 | config CYCLADES | |
131 | tristate "Cyclades async mux support" | |
cff9494f | 132 | depends on SERIAL_NONSTANDARD && (PCI || ISA) |
ee2077d9 | 133 | select FW_LOADER |
1da177e4 LT |
134 | ---help--- |
135 | This driver supports Cyclades Z and Y multiserial boards. | |
136 | You would need something like this to connect more than two modems to | |
137 | your Linux box, for instance in order to become a dial-in server. | |
138 | ||
139 | For information about the Cyclades-Z card, read | |
889c94a1 | 140 | <file:Documentation/README.cycladesZ>. |
1da177e4 LT |
141 | |
142 | To compile this driver as a module, choose M here: the | |
143 | module will be called cyclades. | |
144 | ||
145 | If you haven't heard about it, it's safe to say N. | |
146 | ||
147 | config CYZ_INTR | |
148 | bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)" | |
149 | depends on EXPERIMENTAL && CYCLADES | |
150 | help | |
151 | The Cyclades-Z family of multiport cards allows 2 (two) driver op | |
152 | modes: polling and interrupt. In polling mode, the driver will check | |
153 | the status of the Cyclades-Z ports every certain amount of time | |
154 | (which is called polling cycle and is configurable). In interrupt | |
155 | mode, it will use an interrupt line (IRQ) in order to check the | |
156 | status of the Cyclades-Z ports. The default op mode is polling. If | |
157 | unsure, say N. | |
158 | ||
159 | config DIGIEPCA | |
160 | tristate "Digiboard Intelligent Async Support" | |
27d41718 | 161 | depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI) |
1da177e4 LT |
162 | ---help--- |
163 | This is a driver for Digi International's Xx, Xeve, and Xem series | |
164 | of cards which provide multiple serial ports. You would need | |
165 | something like this to connect more than two modems to your Linux | |
166 | box, for instance in order to become a dial-in server. This driver | |
167 | supports the original PC (ISA) boards as well as PCI, and EISA. If | |
168 | you have a card like this, say Y here and read the file | |
169 | <file:Documentation/digiepca.txt>. | |
170 | ||
171 | To compile this driver as a module, choose M here: the | |
172 | module will be called epca. | |
173 | ||
174 | config ESPSERIAL | |
175 | tristate "Hayes ESP serial port support" | |
33f0f88f | 176 | depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API |
1da177e4 LT |
177 | help |
178 | This is a driver which supports Hayes ESP serial ports. Both single | |
179 | port cards and multiport cards are supported. Make sure to read | |
180 | <file:Documentation/hayes-esp.txt>. | |
181 | ||
182 | To compile this driver as a module, choose M here: the | |
183 | module will be called esp. | |
184 | ||
185 | If unsure, say N. | |
186 | ||
187 | config MOXA_INTELLIO | |
188 | tristate "Moxa Intellio support" | |
8a023674 | 189 | depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI) |
1da177e4 LT |
190 | help |
191 | Say Y here if you have a Moxa Intellio multiport serial card. | |
192 | ||
193 | To compile this driver as a module, choose M here: the | |
194 | module will be called moxa. | |
195 | ||
196 | config MOXA_SMARTIO | |
98c47ea2 | 197 | tristate "Moxa SmartIO support (OBSOLETE)" |
1d25240f | 198 | depends on SERIAL_NONSTANDARD |
1da177e4 LT |
199 | help |
200 | Say Y here if you have a Moxa SmartIO multiport serial card. | |
201 | ||
202 | This driver can also be built as a module ( = code which can be | |
203 | inserted in and removed from the running kernel whenever you want). | |
204 | The module will be called mxser. If you want to do that, say M | |
205 | here. | |
206 | ||
037ad48b | 207 | config MOXA_SMARTIO_NEW |
98c47ea2 | 208 | tristate "Moxa SmartIO support v. 2.0" |
fb0c9295 | 209 | depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA) |
037ad48b JS |
210 | help |
211 | Say Y here if you have a Moxa SmartIO multiport serial card and/or | |
212 | want to help develop a new version of this driver. | |
213 | ||
214 | This is upgraded (1.9.1) driver from original Moxa drivers with | |
215 | changes finally resulting in PCI probing. | |
216 | ||
037ad48b JS |
217 | This driver can also be built as a module. The module will be called |
218 | mxser_new. If you want to do that, say M here. | |
219 | ||
1da177e4 LT |
220 | config ISI |
221 | tristate "Multi-Tech multiport card support (EXPERIMENTAL)" | |
a3808ac1 | 222 | depends on SERIAL_NONSTANDARD && PCI |
5ff2a7e2 | 223 | select FW_LOADER |
1da177e4 LT |
224 | help |
225 | This is a driver for the Multi-Tech cards which provide several | |
226 | serial ports. The driver is experimental and can currently only be | |
227 | built as a module. The module will be called isicom. | |
228 | If you want to do that, choose M here. | |
229 | ||
230 | config SYNCLINK | |
231 | tristate "Microgate SyncLink card support" | |
a5532606 | 232 | depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API |
1da177e4 LT |
233 | help |
234 | Provides support for the SyncLink ISA and PCI multiprotocol serial | |
235 | adapters. These adapters support asynchronous and HDLC bit | |
236 | synchronous communication up to 10Mbps (PCI adapter). | |
237 | ||
238 | This driver can only be built as a module ( = code which can be | |
239 | inserted in and removed from the running kernel whenever you want). | |
240 | The module will be called synclink. If you want to do that, say M | |
241 | here. | |
242 | ||
243 | config SYNCLINKMP | |
244 | tristate "SyncLink Multiport support" | |
8a023674 | 245 | depends on SERIAL_NONSTANDARD && PCI |
1da177e4 LT |
246 | help |
247 | Enable support for the SyncLink Multiport (2 or 4 ports) | |
248 | serial adapter, running asynchronous and HDLC communications up | |
249 | to 2.048Mbps. Each ports is independently selectable for | |
250 | RS-232, V.35, RS-449, RS-530, and X.21 | |
251 | ||
252 | This driver may be built as a module ( = code which can be | |
253 | inserted in and removed from the running kernel whenever you want). | |
254 | The module will be called synclinkmp. If you want to do that, say M | |
255 | here. | |
256 | ||
705b6c7b PF |
257 | config SYNCLINK_GT |
258 | tristate "SyncLink GT/AC support" | |
8ef9cf31 | 259 | depends on SERIAL_NONSTANDARD && PCI |
705b6c7b PF |
260 | help |
261 | Support for SyncLink GT and SyncLink AC families of | |
262 | synchronous and asynchronous serial adapters | |
263 | manufactured by Microgate Systems, Ltd. (www.microgate.com) | |
264 | ||
1da177e4 LT |
265 | config N_HDLC |
266 | tristate "HDLC line discipline support" | |
267 | depends on SERIAL_NONSTANDARD | |
268 | help | |
269 | Allows synchronous HDLC communications with tty device drivers that | |
270 | support synchronous HDLC such as the Microgate SyncLink adapter. | |
271 | ||
272 | This driver can only be built as a module ( = code which can be | |
273 | inserted in and removed from the running kernel whenever you want). | |
274 | The module will be called n_hdlc. If you want to do that, say M | |
275 | here. | |
276 | ||
277 | config RISCOM8 | |
278 | tristate "SDL RISCom/8 card support" | |
279 | depends on SERIAL_NONSTANDARD && BROKEN_ON_SMP | |
280 | help | |
281 | This is a driver for the SDL Communications RISCom/8 multiport card, | |
282 | which gives you many serial ports. You would need something like | |
283 | this to connect more than two modems to your Linux box, for instance | |
284 | in order to become a dial-in server. If you have a card like that, | |
285 | say Y here and read the file <file:Documentation/riscom8.txt>. | |
286 | ||
287 | Also it's possible to say M here and compile this driver as kernel | |
288 | loadable module; the module will be called riscom8. | |
289 | ||
290 | config SPECIALIX | |
291 | tristate "Specialix IO8+ card support" | |
292 | depends on SERIAL_NONSTANDARD | |
293 | help | |
294 | This is a driver for the Specialix IO8+ multiport card (both the | |
295 | ISA and the PCI version) which gives you many serial ports. You | |
296 | would need something like this to connect more than two modems to | |
297 | your Linux box, for instance in order to become a dial-in server. | |
298 | ||
299 | If you have a card like that, say Y here and read the file | |
300 | <file:Documentation/specialix.txt>. Also it's possible to say M here | |
301 | and compile this driver as kernel loadable module which will be | |
302 | called specialix. | |
303 | ||
304 | config SPECIALIX_RTSCTS | |
305 | bool "Specialix DTR/RTS pin is RTS" | |
306 | depends on SPECIALIX | |
307 | help | |
308 | The Specialix IO8+ card can only support either RTS or DTR. If you | |
309 | say N here, the driver will use the pin as "DTR" when the tty is in | |
310 | software handshake mode. If you say Y here or hardware handshake is | |
311 | on, it will always be RTS. Read the file | |
312 | <file:Documentation/specialix.txt> for more information. | |
313 | ||
314 | config SX | |
315 | tristate "Specialix SX (and SI) card support" | |
3468a33e | 316 | depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA) |
1da177e4 LT |
317 | help |
318 | This is a driver for the SX and SI multiport serial cards. | |
319 | Please read the file <file:Documentation/sx.txt> for details. | |
320 | ||
321 | This driver can only be built as a module ( = code which can be | |
322 | inserted in and removed from the running kernel whenever you want). | |
323 | The module will be called sx. If you want to do that, say M here. | |
324 | ||
325 | config RIO | |
326 | tristate "Specialix RIO system support" | |
655fdeab | 327 | depends on SERIAL_NONSTANDARD |
1da177e4 LT |
328 | help |
329 | This is a driver for the Specialix RIO, a smart serial card which | |
330 | drives an outboard box that can support up to 128 ports. Product | |
331 | information is at <http://www.perle.com/support/documentation.html#multiport>. | |
332 | There are both ISA and PCI versions. | |
333 | ||
334 | config RIO_OLDPCI | |
335 | bool "Support really old RIO/PCI cards" | |
336 | depends on RIO | |
337 | help | |
338 | Older RIO PCI cards need some initialization-time configuration to | |
339 | determine the IRQ and some control addresses. If you have a RIO and | |
340 | this doesn't seem to work, try setting this to Y. | |
341 | ||
342 | config STALDRV | |
343 | bool "Stallion multiport serial support" | |
344 | depends on SERIAL_NONSTANDARD | |
345 | help | |
346 | Stallion cards give you many serial ports. You would need something | |
347 | like this to connect more than two modems to your Linux box, for | |
348 | instance in order to become a dial-in server. If you say Y here, | |
349 | you will be asked for your specific card model in the next | |
350 | questions. Make sure to read <file:Documentation/stallion.txt> in | |
351 | this case. If you have never heard about all this, it's safe to | |
352 | say N. | |
353 | ||
354 | config STALLION | |
355 | tristate "Stallion EasyIO or EC8/32 support" | |
27d41718 | 356 | depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI) |
1da177e4 LT |
357 | help |
358 | If you have an EasyIO or EasyConnection 8/32 multiport Stallion | |
359 | card, then this is for you; say Y. Make sure to read | |
360 | <file:Documentation/stallion.txt>. | |
361 | ||
362 | To compile this driver as a module, choose M here: the | |
363 | module will be called stallion. | |
364 | ||
365 | config ISTALLION | |
366 | tristate "Stallion EC8/64, ONboard, Brumby support" | |
27d41718 | 367 | depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI) |
1da177e4 LT |
368 | help |
369 | If you have an EasyConnection 8/64, ONboard, Brumby or Stallion | |
370 | serial multiport card, say Y here. Make sure to read | |
371 | <file:Documentation/stallion.txt>. | |
372 | ||
373 | To compile this driver as a module, choose M here: the | |
374 | module will be called istallion. | |
375 | ||
20fd1e3b FS |
376 | config NOZOMI |
377 | tristate "HSDPA Broadband Wireless Data Card - Globe Trotter" | |
378 | depends on PCI && EXPERIMENTAL | |
379 | help | |
380 | If you have a HSDPA driver Broadband Wireless Data Card - | |
381 | Globe Trotter PCMCIA card, say Y here. | |
382 | ||
383 | To compile this driver as a module, choose M here, the module | |
384 | will be called nozomi. | |
385 | ||
1da177e4 LT |
386 | config A2232 |
387 | tristate "Commodore A2232 serial support (EXPERIMENTAL)" | |
388 | depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP | |
389 | ---help--- | |
390 | This option supports the 2232 7-port serial card shipped with the | |
391 | Amiga 2000 and other Zorro-bus machines, dating from 1989. At | |
392 | a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip | |
393 | each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The | |
394 | ports were connected with 8 pin DIN connectors on the card bracket, | |
395 | for which 8 pin to DB25 adapters were supplied. The card also had | |
396 | jumpers internally to toggle various pinning configurations. | |
397 | ||
398 | This driver can be built as a module; but then "generic_serial" | |
399 | will also be built as a module. This has to be loaded before | |
400 | "ser_a2232". If you want to do this, answer M here. | |
401 | ||
402 | config SGI_SNSC | |
403 | bool "SGI Altix system controller communication support" | |
404 | depends on (IA64_SGI_SN2 || IA64_GENERIC) | |
405 | help | |
406 | If you have an SGI Altix and you want to enable system | |
407 | controller communication from user space (you want this!), | |
408 | say Y. Otherwise, say N. | |
409 | ||
e1e19747 BL |
410 | config SGI_TIOCX |
411 | bool "SGI TIO CX driver support" | |
412 | depends on (IA64_SGI_SN2 || IA64_GENERIC) | |
413 | help | |
414 | If you have an SGI Altix and you have fpga devices attached | |
415 | to your TIO, say Y here, otherwise say N. | |
416 | ||
417 | config SGI_MBCS | |
418 | tristate "SGI FPGA Core Services driver support" | |
ae40aae9 | 419 | depends on SGI_TIOCX |
e1e19747 BL |
420 | help |
421 | If you have an SGI Altix with an attached SABrick | |
422 | say Y or M here, otherwise say N. | |
423 | ||
1da177e4 LT |
424 | source "drivers/serial/Kconfig" |
425 | ||
426 | config UNIX98_PTYS | |
427 | bool "Unix98 PTY support" if EMBEDDED | |
428 | default y | |
429 | ---help--- | |
430 | A pseudo terminal (PTY) is a software device consisting of two | |
431 | halves: a master and a slave. The slave device behaves identical to | |
432 | a physical terminal; the master device is used by a process to | |
433 | read data from and write data to the slave, thereby emulating a | |
434 | terminal. Typical programs for the master side are telnet servers | |
435 | and xterms. | |
436 | ||
437 | Linux has traditionally used the BSD-like names /dev/ptyxx for | |
438 | masters and /dev/ttyxx for slaves of pseudo terminals. This scheme | |
439 | has a number of problems. The GNU C library glibc 2.1 and later, | |
440 | however, supports the Unix98 naming standard: in order to acquire a | |
441 | pseudo terminal, a process opens /dev/ptmx; the number of the pseudo | |
442 | terminal is then made available to the process and the pseudo | |
443 | terminal slave can be accessed as /dev/pts/<number>. What was | |
444 | traditionally /dev/ttyp2 will then be /dev/pts/2, for example. | |
445 | ||
446 | All modern Linux systems use the Unix98 ptys. Say Y unless | |
447 | you're on an embedded system and want to conserve memory. | |
448 | ||
449 | config LEGACY_PTYS | |
450 | bool "Legacy (BSD) PTY support" | |
451 | default y | |
452 | ---help--- | |
453 | A pseudo terminal (PTY) is a software device consisting of two | |
454 | halves: a master and a slave. The slave device behaves identical to | |
455 | a physical terminal; the master device is used by a process to | |
456 | read data from and write data to the slave, thereby emulating a | |
457 | terminal. Typical programs for the master side are telnet servers | |
458 | and xterms. | |
459 | ||
460 | Linux has traditionally used the BSD-like names /dev/ptyxx | |
461 | for masters and /dev/ttyxx for slaves of pseudo | |
462 | terminals. This scheme has a number of problems, including | |
463 | security. This option enables these legacy devices; on most | |
464 | systems, it is safe to say N. | |
465 | ||
466 | ||
467 | config LEGACY_PTY_COUNT | |
468 | int "Maximum number of legacy PTY in use" | |
469 | depends on LEGACY_PTYS | |
345ee839 | 470 | range 0 256 |
1da177e4 LT |
471 | default "256" |
472 | ---help--- | |
473 | The maximum number of legacy PTYs that can be used at any one time. | |
474 | The default is 256, and should be more than enough. Embedded | |
475 | systems may want to reduce this to save memory. | |
476 | ||
477 | When not in use, each legacy PTY occupies 12 bytes on 32-bit | |
478 | architectures and 24 bytes on 64-bit architectures. | |
479 | ||
a45b8395 BH |
480 | config BRIQ_PANEL |
481 | tristate 'Total Impact briQ front panel driver' | |
2818c5de | 482 | depends on PPC_CHRP |
a45b8395 BH |
483 | ---help--- |
484 | The briQ is a small footprint CHRP computer with a frontpanel VFD, a | |
485 | tristate led and two switches. It is the size of a CDROM drive. | |
486 | ||
487 | If you have such one and want anything showing on the VFD then you | |
488 | must answer Y here. | |
489 | ||
490 | To compile this driver as a module, choose M here: the | |
491 | module will be called briq_panel. | |
492 | ||
493 | It's safe to say N here. | |
494 | ||
1da177e4 LT |
495 | config PRINTER |
496 | tristate "Parallel printer support" | |
497 | depends on PARPORT | |
498 | ---help--- | |
499 | If you intend to attach a printer to the parallel port of your Linux | |
500 | box (as opposed to using a serial printer; if the connector at the | |
501 | printer has 9 or 25 holes ["female"], then it's serial), say Y. | |
502 | Also read the Printing-HOWTO, available from | |
503 | <http://www.tldp.org/docs.html#howto>. | |
504 | ||
505 | It is possible to share one parallel port among several devices | |
506 | (e.g. printer and ZIP drive) and it is safe to compile the | |
507 | corresponding drivers into the kernel. | |
508 | ||
509 | To compile this driver as a module, choose M here and read | |
510 | <file:Documentation/parport.txt>. The module will be called lp. | |
511 | ||
512 | If you have several parallel ports, you can specify which ports to | |
513 | use with the "lp" kernel command line option. (Try "man bootparam" | |
514 | or see the documentation of your boot loader (lilo or loadlin) about | |
515 | how to pass options to the kernel at boot time.) The syntax of the | |
516 | "lp" command line option can be found in <file:drivers/char/lp.c>. | |
517 | ||
518 | If you have more than 8 printers, you need to increase the LP_NO | |
519 | macro in lp.c and the PARPORT_MAX macro in parport.h. | |
520 | ||
521 | config LP_CONSOLE | |
522 | bool "Support for console on line printer" | |
523 | depends on PRINTER | |
524 | ---help--- | |
525 | If you want kernel messages to be printed out as they occur, you | |
526 | can have a console on the printer. This option adds support for | |
527 | doing that; to actually get it to happen you need to pass the | |
528 | option "console=lp0" to the kernel at boot time. | |
529 | ||
530 | If the printer is out of paper (or off, or unplugged, or too | |
531 | busy..) the kernel will stall until the printer is ready again. | |
532 | By defining CONSOLE_LP_STRICT to 0 (at your own risk) you | |
533 | can make the kernel continue when this happens, | |
534 | but it'll lose the kernel messages. | |
535 | ||
536 | If unsure, say N. | |
537 | ||
538 | config PPDEV | |
539 | tristate "Support for user-space parallel port device drivers" | |
540 | depends on PARPORT | |
541 | ---help--- | |
542 | Saying Y to this adds support for /dev/parport device nodes. This | |
543 | is needed for programs that want portable access to the parallel | |
544 | port, for instance deviceid (which displays Plug-and-Play device | |
545 | IDs). | |
546 | ||
547 | This is the parallel port equivalent of SCSI generic support (sg). | |
548 | It is safe to say N to this -- it is not needed for normal printing | |
549 | or parallel port CD-ROM/disk support. | |
550 | ||
551 | To compile this driver as a module, choose M here: the | |
552 | module will be called ppdev. | |
553 | ||
554 | If unsure, say N. | |
555 | ||
45d607ed RA |
556 | config HVC_DRIVER |
557 | bool | |
558 | help | |
3e6c6f63 | 559 | Generic "hypervisor virtual console" infrastructure for various |
2d1df815 | 560 | hypervisors (pSeries, iSeries, Xen, lguest). |
45d607ed RA |
561 | It will automatically be selected if one of the back-end console drivers |
562 | is selected. | |
563 | ||
564 | ||
1da177e4 LT |
565 | config HVC_CONSOLE |
566 | bool "pSeries Hypervisor Virtual Console support" | |
567 | depends on PPC_PSERIES | |
45d607ed | 568 | select HVC_DRIVER |
1da177e4 LT |
569 | help |
570 | pSeries machines when partitioned support a hypervisor virtual | |
571 | console. This driver allows each pSeries partition to have a console | |
572 | which is accessed via the HMC. | |
573 | ||
8bff05b0 SR |
574 | config HVC_ISERIES |
575 | bool "iSeries Hypervisor Virtual Console support" | |
b15f792f SR |
576 | depends on PPC_ISERIES |
577 | default y | |
8bff05b0 SR |
578 | select HVC_DRIVER |
579 | help | |
580 | iSeries machines support a hypervisor virtual console. | |
581 | ||
f4d1749e AB |
582 | config HVC_RTAS |
583 | bool "IBM RTAS Console support" | |
584 | depends on PPC_RTAS | |
585 | select HVC_DRIVER | |
586 | help | |
587 | IBM Console device driver which makes use of RTAS | |
588 | ||
3cdc20e5 IK |
589 | config HVC_BEAT |
590 | bool "Toshiba's Beat Hypervisor Console support" | |
591 | depends on PPC_CELLEB | |
592 | select HVC_DRIVER | |
593 | help | |
594 | Toshiba's Cell Reference Set Beat Console device driver | |
595 | ||
b536b4b9 JF |
596 | config HVC_XEN |
597 | bool "Xen Hypervisor Console support" | |
598 | depends on XEN | |
599 | select HVC_DRIVER | |
600 | default y | |
601 | help | |
602 | Xen virtual console device driver | |
603 | ||
31610434 RR |
604 | config VIRTIO_CONSOLE |
605 | bool | |
606 | select HVC_DRIVER | |
607 | ||
1da177e4 LT |
608 | config HVCS |
609 | tristate "IBM Hypervisor Virtual Console Server support" | |
610 | depends on PPC_PSERIES | |
611 | help | |
612 | Partitionable IBM Power5 ppc64 machines allow hosting of | |
613 | firmware virtual consoles from one Linux partition by | |
614 | another Linux partition. This driver allows console data | |
615 | from Linux partitions to be accessed through TTY device | |
616 | interfaces in the device tree of a Linux partition running | |
617 | this driver. | |
618 | ||
619 | To compile this driver as a module, choose M here: the | |
620 | module will be called hvcs.ko. Additionally, this module | |
621 | will depend on arch specific APIs exported from hvcserver.ko | |
622 | which will also be compiled when this driver is built as a | |
623 | module. | |
624 | ||
625 | source "drivers/char/ipmi/Kconfig" | |
626 | ||
1da177e4 LT |
627 | config DS1620 |
628 | tristate "NetWinder thermometer support" | |
629 | depends on ARCH_NETWINDER | |
630 | help | |
631 | Say Y here to include support for the thermal management hardware | |
632 | found in the NetWinder. This driver allows the user to control the | |
633 | temperature set points and to read the current temperature. | |
634 | ||
635 | It is also possible to say M here to build it as a module (ds1620) | |
636 | It is recommended to be used on a NetWinder, but it is not a | |
637 | necessity. | |
638 | ||
639 | config NWBUTTON | |
640 | tristate "NetWinder Button" | |
641 | depends on ARCH_NETWINDER | |
642 | ---help--- | |
643 | If you say Y here and create a character device node /dev/nwbutton | |
644 | with major and minor numbers 10 and 158 ("man mknod"), then every | |
645 | time the orange button is pressed a number of times, the number of | |
646 | times the button was pressed will be written to that device. | |
647 | ||
648 | This is most useful for applications, as yet unwritten, which | |
649 | perform actions based on how many times the button is pressed in a | |
650 | row. | |
651 | ||
652 | Do not hold the button down for too long, as the driver does not | |
653 | alter the behaviour of the hardware reset circuitry attached to the | |
654 | button; it will still execute a hard reset if the button is held | |
655 | down for longer than approximately five seconds. | |
656 | ||
657 | To compile this driver as a module, choose M here: the | |
658 | module will be called nwbutton. | |
659 | ||
660 | Most people will answer Y to this question and "Reboot Using Button" | |
661 | below to be able to initiate a system shutdown from the button. | |
662 | ||
663 | config NWBUTTON_REBOOT | |
664 | bool "Reboot Using Button" | |
665 | depends on NWBUTTON | |
666 | help | |
667 | If you say Y here, then you will be able to initiate a system | |
668 | shutdown and reboot by pressing the orange button a number of times. | |
669 | The number of presses to initiate the shutdown is two by default, | |
670 | but this can be altered by modifying the value of NUM_PRESSES_REBOOT | |
671 | in nwbutton.h and recompiling the driver or, if you compile the | |
672 | driver as a module, you can specify the number of presses at load | |
673 | time with "insmod button reboot_count=<something>". | |
674 | ||
675 | config NWFLASH | |
676 | tristate "NetWinder flash support" | |
677 | depends on ARCH_NETWINDER | |
678 | ---help--- | |
679 | If you say Y here and create a character device /dev/flash with | |
680 | major 10 and minor 160 you can manipulate the flash ROM containing | |
681 | the NetWinder firmware. Be careful as accidentally overwriting the | |
682 | flash contents can render your computer unbootable. On no account | |
683 | allow random users access to this device. :-) | |
684 | ||
685 | To compile this driver as a module, choose M here: the | |
686 | module will be called nwflash. | |
687 | ||
688 | If you're not sure, say N. | |
689 | ||
844dd05f MB |
690 | source "drivers/char/hw_random/Kconfig" |
691 | ||
1da177e4 LT |
692 | config NVRAM |
693 | tristate "/dev/nvram support" | |
0d078f6f | 694 | depends on ATARI || X86 || ARM || GENERIC_NVRAM |
1da177e4 LT |
695 | ---help--- |
696 | If you say Y here and create a character special file /dev/nvram | |
697 | with major number 10 and minor number 144 using mknod ("man mknod"), | |
698 | you get read and write access to the extra bytes of non-volatile | |
699 | memory in the real time clock (RTC), which is contained in every PC | |
700 | and most Ataris. The actual number of bytes varies, depending on the | |
701 | nvram in the system, but is usually 114 (128-14 for the RTC). | |
702 | ||
703 | This memory is conventionally called "CMOS RAM" on PCs and "NVRAM" | |
704 | on Ataris. /dev/nvram may be used to view settings there, or to | |
705 | change them (with some utility). It could also be used to frequently | |
706 | save a few bits of very important data that may not be lost over | |
707 | power-off and for which writing to disk is too insecure. Note | |
708 | however that most NVRAM space in a PC belongs to the BIOS and you | |
709 | should NEVER idly tamper with it. See Ralf Brown's interrupt list | |
710 | for a guide to the use of CMOS bytes by your BIOS. | |
711 | ||
712 | On Atari machines, /dev/nvram is always configured and does not need | |
713 | to be selected. | |
714 | ||
715 | To compile this driver as a module, choose M here: the | |
716 | module will be called nvram. | |
717 | ||
718 | config RTC | |
719 | tristate "Enhanced Real Time Clock Support" | |
2240598c | 720 | depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV && !ARM && !SUPERH && !S390 |
1da177e4 LT |
721 | ---help--- |
722 | If you say Y here and create a character special file /dev/rtc with | |
723 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
724 | will get access to the real time clock (or hardware clock) built | |
725 | into your computer. | |
726 | ||
727 | Every PC has such a clock built in. It can be used to generate | |
728 | signals from as low as 1Hz up to 8192Hz, and can also be used | |
729 | as a 24 hour alarm. It reports status information via the file | |
730 | /proc/driver/rtc and its behaviour is set by various ioctls on | |
731 | /dev/rtc. | |
732 | ||
733 | If you run Linux on a multiprocessor machine and said Y to | |
734 | "Symmetric Multi Processing" above, you should say Y here to read | |
735 | and set the RTC in an SMP compatible fashion. | |
736 | ||
737 | If you think you have a use for such a device (such as periodic data | |
738 | sampling), then say Y here, and read <file:Documentation/rtc.txt> | |
739 | for details. | |
740 | ||
741 | To compile this driver as a module, choose M here: the | |
742 | module will be called rtc. | |
743 | ||
2240598c AV |
744 | config JS_RTC |
745 | tristate "Enhanced Real Time Clock Support" | |
746 | depends on SPARC32 && PCI | |
747 | ---help--- | |
748 | If you say Y here and create a character special file /dev/rtc with | |
749 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
750 | will get access to the real time clock (or hardware clock) built | |
751 | into your computer. | |
752 | ||
753 | Every PC has such a clock built in. It can be used to generate | |
754 | signals from as low as 1Hz up to 8192Hz, and can also be used | |
755 | as a 24 hour alarm. It reports status information via the file | |
756 | /proc/driver/rtc and its behaviour is set by various ioctls on | |
757 | /dev/rtc. | |
758 | ||
759 | If you think you have a use for such a device (such as periodic data | |
760 | sampling), then say Y here, and read <file:Documentation/rtc.txt> | |
761 | for details. | |
762 | ||
763 | To compile this driver as a module, choose M here: the | |
764 | module will be called js-rtc. | |
765 | ||
1da177e4 LT |
766 | config SGI_DS1286 |
767 | tristate "SGI DS1286 RTC support" | |
768 | depends on SGI_IP22 | |
769 | help | |
770 | If you say Y here and create a character special file /dev/rtc with | |
771 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
772 | will get access to the real time clock built into your computer. | |
773 | Every SGI has such a clock built in. It reports status information | |
774 | via the file /proc/rtc and its behaviour is set by various ioctls on | |
775 | /dev/rtc. | |
776 | ||
777 | config SGI_IP27_RTC | |
778 | bool "SGI M48T35 RTC support" | |
779 | depends on SGI_IP27 | |
780 | help | |
781 | If you say Y here and create a character special file /dev/rtc with | |
782 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
783 | will get access to the real time clock built into your computer. | |
784 | Every SGI has such a clock built in. It reports status information | |
785 | via the file /proc/rtc and its behaviour is set by various ioctls on | |
786 | /dev/rtc. | |
787 | ||
788 | config GEN_RTC | |
789 | tristate "Generic /dev/rtc emulation" | |
fdc1f938 | 790 | depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH |
1da177e4 LT |
791 | ---help--- |
792 | If you say Y here and create a character special file /dev/rtc with | |
793 | major number 10 and minor number 135 using mknod ("man mknod"), you | |
794 | will get access to the real time clock (or hardware clock) built | |
795 | into your computer. | |
796 | ||
797 | It reports status information via the file /proc/driver/rtc and its | |
798 | behaviour is set by various ioctls on /dev/rtc. If you enable the | |
799 | "extended RTC operation" below it will also provide an emulation | |
800 | for RTC_UIE which is required by some programs and may improve | |
801 | precision in some cases. | |
802 | ||
803 | To compile this driver as a module, choose M here: the | |
804 | module will be called genrtc. | |
805 | ||
806 | config GEN_RTC_X | |
807 | bool "Extended RTC operation" | |
808 | depends on GEN_RTC | |
809 | help | |
810 | Provides an emulation for RTC_UIE which is required by some programs | |
811 | and may improve precision of the generic RTC support in some cases. | |
812 | ||
813 | config EFI_RTC | |
814 | bool "EFI Real Time Clock Services" | |
815 | depends on IA64 | |
816 | ||
817 | config DS1302 | |
818 | tristate "DS1302 RTC support" | |
819 | depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT) | |
820 | help | |
821 | If you say Y here and create a character special file /dev/rtc with | |
822 | major number 121 and minor number 0 using mknod ("man mknod"), you | |
823 | will get access to the real time clock (or hardware clock) built | |
824 | into your computer. | |
825 | ||
1da177e4 LT |
826 | config COBALT_LCD |
827 | bool "Support for Cobalt LCD" | |
828 | depends on MIPS_COBALT | |
829 | help | |
830 | This option enables support for the LCD display and buttons found | |
831 | on Cobalt systems through a misc device. | |
832 | ||
833 | config DTLK | |
834 | tristate "Double Talk PC internal speech card support" | |
eeca7a36 | 835 | depends on ISA |
1da177e4 LT |
836 | help |
837 | This driver is for the DoubleTalk PC, a speech synthesizer | |
838 | manufactured by RC Systems (<http://www.rcsys.com/>). It is also | |
839 | called the `internal DoubleTalk'. | |
840 | ||
841 | To compile this driver as a module, choose M here: the | |
842 | module will be called dtlk. | |
843 | ||
844 | config R3964 | |
845 | tristate "Siemens R3964 line discipline" | |
846 | ---help--- | |
847 | This driver allows synchronous communication with devices using the | |
848 | Siemens R3964 packet protocol. Unless you are dealing with special | |
849 | hardware like PLCs, you are unlikely to need this. | |
850 | ||
851 | To compile this driver as a module, choose M here: the | |
852 | module will be called n_r3964. | |
853 | ||
854 | If unsure, say N. | |
855 | ||
856 | config APPLICOM | |
857 | tristate "Applicom intelligent fieldbus card support" | |
858 | depends on PCI | |
859 | ---help--- | |
860 | This driver provides the kernel-side support for the intelligent | |
861 | fieldbus cards made by Applicom International. More information | |
862 | about these cards can be found on the WWW at the address | |
863 | <http://www.applicom-int.com/>, or by email from David Woodhouse | |
864 | <dwmw2@infradead.org>. | |
865 | ||
866 | To compile this driver as a module, choose M here: the | |
867 | module will be called applicom. | |
868 | ||
869 | If unsure, say N. | |
870 | ||
871 | config SONYPI | |
872 | tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)" | |
873 | depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT | |
874 | ---help--- | |
875 | This driver enables access to the Sony Programmable I/O Control | |
876 | Device which can be found in many (all ?) Sony Vaio laptops. | |
877 | ||
878 | If you have one of those laptops, read | |
879 | <file:Documentation/sonypi.txt>, and say Y or M here. | |
880 | ||
881 | To compile this driver as a module, choose M here: the | |
882 | module will be called sonypi. | |
883 | ||
09762516 YY |
884 | config GPIO_TB0219 |
885 | tristate "TANBAC TB0219 GPIO support" | |
bef1f402 | 886 | depends on TANBAC_TB022X |
584e1236 | 887 | select GPIO_VR41XX |
1da177e4 | 888 | |
1da177e4 LT |
889 | source "drivers/char/pcmcia/Kconfig" |
890 | ||
891 | config MWAVE | |
892 | tristate "ACP Modem (Mwave) support" | |
893 | depends on X86 | |
894 | select SERIAL_8250 | |
895 | ---help--- | |
896 | The ACP modem (Mwave) for Linux is a WinModem. It is composed of a | |
897 | kernel driver and a user level application. Together these components | |
898 | support direct attachment to public switched telephone networks (PSTNs) | |
899 | and support selected world wide countries. | |
900 | ||
901 | This version of the ACP Modem driver supports the IBM Thinkpad 600E, | |
902 | 600, and 770 that include on board ACP modem hardware. | |
903 | ||
904 | The modem also supports the standard communications port interface | |
905 | (ttySx) and is compatible with the Hayes AT Command Set. | |
906 | ||
907 | The user level application needed to use this driver can be found at | |
908 | the IBM Linux Technology Center (LTC) web site: | |
909 | <http://www.ibm.com/linux/ltc/>. | |
910 | ||
911 | If you own one of the above IBM Thinkpads which has the Mwave chipset | |
912 | in it, say Y. | |
913 | ||
914 | To compile this driver as a module, choose M here: the | |
915 | module will be called mwave. | |
916 | ||
917 | config SCx200_GPIO | |
918 | tristate "NatSemi SCx200 GPIO Support" | |
919 | depends on SCx200 | |
7a8e2a5e | 920 | select NSC_GPIO |
1da177e4 LT |
921 | help |
922 | Give userspace access to the GPIO pins on the National | |
923 | Semiconductor SCx200 processors. | |
924 | ||
925 | If compiled as a module, it will be called scx200_gpio. | |
926 | ||
7a8e2a5e JC |
927 | config PC8736x_GPIO |
928 | tristate "NatSemi PC8736x GPIO Support" | |
929 | depends on X86 | |
930 | default SCx200_GPIO # mostly N | |
931 | select NSC_GPIO # needed for support routines | |
932 | help | |
933 | Give userspace access to the GPIO pins on the National | |
934 | Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip | |
935 | has multiple functional units, inc several managed by | |
936 | hwmon/pc87360 driver. Tested with PC-87366 | |
937 | ||
938 | If compiled as a module, it will be called pc8736x_gpio. | |
939 | ||
940 | config NSC_GPIO | |
941 | tristate "NatSemi Base GPIO Support" | |
699352c3 | 942 | depends on X86_32 |
7a8e2a5e JC |
943 | # selected by SCx200_GPIO and PC8736x_GPIO |
944 | # what about 2 selectors differing: m != y | |
945 | help | |
946 | Common support used (and needed) by scx200_gpio and | |
947 | pc8736x_gpio drivers. If those drivers are built as | |
948 | modules, this one will be too, named nsc_gpio | |
949 | ||
e329113c BG |
950 | config CS5535_GPIO |
951 | tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)" | |
952 | depends on X86_32 | |
953 | help | |
954 | Give userspace access to the GPIO pins on the AMD CS5535 and | |
955 | CS5536 Geode companion devices. | |
956 | ||
957 | If compiled as a module, it will be called cs5535_gpio. | |
958 | ||
e400bae9 YY |
959 | config GPIO_VR41XX |
960 | tristate "NEC VR4100 series General-purpose I/O Unit support" | |
961 | depends on CPU_VR41XX | |
962 | ||
1da177e4 | 963 | config RAW_DRIVER |
abd4aa5a | 964 | tristate "RAW driver (/dev/raw/rawN)" |
9361401e | 965 | depends on BLOCK |
1da177e4 | 966 | help |
abd4aa5a DJ |
967 | The raw driver permits block devices to be bound to /dev/raw/rawN. |
968 | Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O. | |
1da177e4 LT |
969 | See the raw(8) manpage for more details. |
970 | ||
abd4aa5a | 971 | Applications should preferably open the device (eg /dev/hda1) |
1da177e4 LT |
972 | with the O_DIRECT flag. |
973 | ||
0de502aa AM |
974 | config MAX_RAW_DEVS |
975 | int "Maximum number of RAW devices to support (1-8192)" | |
976 | depends on RAW_DRIVER | |
977 | default "256" | |
978 | help | |
979 | The maximum number of RAW devices that are supported. | |
980 | Default is 256. Increase this number in case you need lots of | |
981 | raw devices. | |
982 | ||
1da177e4 LT |
983 | config HPET |
984 | bool "HPET - High Precision Event Timer" if (X86 || IA64) | |
985 | default n | |
986 | depends on ACPI | |
987 | help | |
988 | If you say Y here, you will have a miscdevice named "/dev/hpet/". Each | |
989 | open selects one of the timers supported by the HPET. The timers are | |
3cb2fccc | 990 | non-periodic and/or periodic. |
1da177e4 LT |
991 | |
992 | config HPET_RTC_IRQ | |
993 | bool "HPET Control RTC IRQ" if !HPET_EMULATE_RTC | |
994 | default n | |
995 | depends on HPET | |
996 | help | |
997 | If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It | |
998 | is assumed the platform called hpet_alloc with the RTC IRQ values for | |
999 | the HPET timers. | |
1000 | ||
1001 | config HPET_MMAP | |
1002 | bool "Allow mmap of HPET" | |
1003 | default y | |
1004 | depends on HPET | |
1005 | help | |
1006 | If you say Y here, user applications will be able to mmap | |
1007 | the HPET registers. | |
1008 | ||
1009 | In some hardware implementations, the page containing HPET | |
1010 | registers may also contain other things that shouldn't be | |
1011 | exposed to the user. If this applies to your hardware, | |
1012 | say N here. | |
1013 | ||
1da177e4 LT |
1014 | config HANGCHECK_TIMER |
1015 | tristate "Hangcheck timer" | |
abf3ea1b | 1016 | depends on X86 || IA64 || PPC64 || S390 |
1da177e4 LT |
1017 | help |
1018 | The hangcheck-timer module detects when the system has gone | |
1019 | out to lunch past a certain margin. It can reboot the system | |
1020 | or merely print a warning. | |
1021 | ||
1022 | config MMTIMER | |
1023 | tristate "MMTIMER Memory mapped RTC for SGI Altix" | |
1024 | depends on IA64_GENERIC || IA64_SGI_SN2 | |
1025 | default y | |
1026 | help | |
1027 | The mmtimer device allows direct userspace access to the | |
1028 | Altix system timer. | |
1029 | ||
1030 | source "drivers/char/tpm/Kconfig" | |
1031 | ||
1a80ba88 | 1032 | config TELCLOCK |
03154a27 | 1033 | tristate "Telecom clock driver for ATCA SBC" |
4d99bfac | 1034 | depends on EXPERIMENTAL && X86 |
1a80ba88 MG |
1035 | default n |
1036 | help | |
03154a27 MG |
1037 | The telecom clock device is specific to the MPCBL0010 and MPCBL0050 |
1038 | ATCA computers and allows direct userspace access to the | |
1039 | configuration of the telecom clock configuration settings. This | |
1040 | device is used for hardware synchronization across the ATCA backplane | |
1041 | fabric. Upon loading, the driver exports a sysfs directory, | |
1042 | /sys/devices/platform/telco_clock, with a number of files for | |
1043 | controlling the behavior of this hardware. | |
1a80ba88 | 1044 | |
4f911d64 RK |
1045 | config DEVPORT |
1046 | bool | |
1047 | depends on !M68K | |
1048 | depends on ISA || PCI | |
1049 | default y | |
1050 | ||
61d48c2c MS |
1051 | source "drivers/s390/char/Kconfig" |
1052 | ||
1da177e4 LT |
1053 | endmenu |
1054 |