blob: 2d854bb9373e46ca465ab36411089f7810944203 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Character device configuration
3#
4
5menu "Character devices"
6
7config VT
8 bool "Virtual terminal" if EMBEDDED
Martin Schwidefskyabf3ea12007-05-10 15:45:59 +02009 depends on !S390
Linus Torvalds1da177e2005-04-16 15:20:36 -070010 select INPUT
11 default y if !VIOCONS
12 ---help---
13 If you say Y here, you will get support for terminal devices with
14 display and keyboard devices. These are called "virtual" because you
15 can run several virtual terminals (also called virtual consoles) on
16 one physical terminal. This is rather useful, for example one
17 virtual terminal can collect system messages and warnings, another
18 one can be used for a text-mode user session, and a third could run
19 an X session, all in parallel. Switching between virtual terminals
20 is done with certain key combinations, usually Alt-<function key>.
21
22 The setterm command ("man setterm") can be used to change the
23 properties (such as colors or beeping) of a virtual terminal. The
24 man page console_codes(4) ("man console_codes") contains the special
25 character sequences that can be used to change those properties
26 directly. The fonts used on virtual terminals can be changed with
27 the setfont ("man setfont") command and the key bindings are defined
28 with the loadkeys ("man loadkeys") command.
29
30 You need at least one virtual terminal device in order to make use
31 of your keyboard and monitor. Therefore, only people configuring an
32 embedded system would want to say N here in order to save some
33 memory; the only way to log into such a system is then via a serial
34 or network connection.
35
36 If unsure, say Y, or else you won't be able to do much with your new
37 shiny Linux system :-)
38
39config VT_CONSOLE
40 bool "Support for console on virtual terminal" if EMBEDDED
41 depends on VT
42 default y
43 ---help---
44 The system console is the device which receives all kernel messages
45 and warnings and which allows logins in single user mode. If you
46 answer Y here, a virtual terminal (the device used to interact with
47 a physical terminal) can be used as system console. This is the most
48 common mode of operations, so you should say Y here unless you want
49 the kernel messages be output only to a serial port (in which case
50 you should say Y to "Console on serial port", below).
51
52 If you do say Y here, by default the currently visible virtual
53 terminal (/dev/tty0) will be used as system console. You can change
54 that with a kernel command line option such as "console=tty3" which
55 would use the third virtual terminal as system console. (Try "man
56 bootparam" or see the documentation of your boot loader (lilo or
57 loadlin) about how to pass options to the kernel at boot time.)
58
59 If unsure, say Y.
60
61config HW_CONSOLE
62 bool
63 depends on VT && !S390 && !UML
64 default y
65
Antonino A. Daplas13ae6642006-06-26 00:27:12 -070066config VT_HW_CONSOLE_BINDING
67 bool "Support for binding and unbinding console drivers"
68 depends on HW_CONSOLE
69 default n
70 ---help---
71 The virtual terminal is the device that interacts with the physical
72 terminal through console drivers. On these systems, at least one
73 console driver is loaded. In other configurations, additional console
74 drivers may be enabled, such as the framebuffer console. If more than
75 1 console driver is enabled, setting this to 'y' will allow you to
76 select the console driver that will serve as the backend for the
77 virtual terminals.
78
79 See <file:Documentation/console/console.txt> for more
80 information. For framebuffer console users, please refer to
81 <file:Documentation/fb/fbcon.txt>.
82
Arjan van de Venb781ecb2008-04-29 00:58:34 -070083config DEVKMEM
84 bool "/dev/kmem virtual device support"
85 default y
86 help
87 Say Y here if you want to support the /dev/kmem device. The
88 /dev/kmem device is rarely used, but can be used for certain
89 kind of kernel debugging operations.
90 When in doubt, say "N".
91
Linus Torvalds1da177e2005-04-16 15:20:36 -070092config SERIAL_NONSTANDARD
93 bool "Non-standard serial port support"
Martin Schwidefskyeeca7a32007-05-10 15:45:56 +020094 depends on HAS_IOMEM
Linus Torvalds1da177e2005-04-16 15:20:36 -070095 ---help---
96 Say Y here if you have any non-standard serial boards -- boards
97 which aren't supported using the standard "dumb" serial driver.
98 This includes intelligent serial boards such as Cyclades,
99 Digiboards, etc. These are usually used for systems that need many
100 serial ports because they serve many terminals or dial-in
101 connections.
102
103 Note that the answer to this question won't directly affect the
104 kernel: saying N will just cause the configurator to skip all
105 the questions about non-standard serial boards.
106
107 Most people can say N here.
108
109config COMPUTONE
110 tristate "Computone IntelliPort Plus serial support"
Al Viro3b4709a2006-12-13 00:34:58 -0800111 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700112 ---help---
113 This driver supports the entire family of Intelliport II/Plus
114 controllers with the exception of the MicroChannel controllers and
115 products previous to the Intelliport II. These are multiport cards,
116 which give you many serial ports. You would need something like this
117 to connect more than two modems to your Linux box, for instance in
118 order to become a dial-in server. If you have a card like that, say
119 Y here and read <file:Documentation/computone.txt>.
120
Roland.Kletzing33dda512008-06-05 22:46:04 -0700121 To compile this driver as module, choose M here: the
122 module will be called ip2.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700123
124config ROCKETPORT
125 tristate "Comtrol RocketPort support"
Al Viro27d41712007-07-17 08:49:35 +0100126 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700127 help
128 This driver supports Comtrol RocketPort and RocketModem PCI boards.
129 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
130 modems. For information about the RocketPort/RocketModem boards
131 and this driver read <file:Documentation/rocket.txt>.
132
133 To compile this driver as a module, choose M here: the
134 module will be called rocket.
135
136 If you want to compile this driver into the kernel, say Y here. If
137 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
138
139config CYCLADES
140 tristate "Cyclades async mux support"
Jiri Slabycff94942007-05-08 00:36:36 -0700141 depends on SERIAL_NONSTANDARD && (PCI || ISA)
Jiri Slabyee2077d2007-07-26 10:41:17 -0700142 select FW_LOADER
Linus Torvalds1da177e2005-04-16 15:20:36 -0700143 ---help---
144 This driver supports Cyclades Z and Y multiserial boards.
145 You would need something like this to connect more than two modems to
146 your Linux box, for instance in order to become a dial-in server.
147
148 For information about the Cyclades-Z card, read
Johann Felix Soden889c94a2008-01-20 14:41:18 +0100149 <file:Documentation/README.cycladesZ>.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700150
151 To compile this driver as a module, choose M here: the
152 module will be called cyclades.
153
154 If you haven't heard about it, it's safe to say N.
155
156config CYZ_INTR
157 bool "Cyclades-Z interrupt mode operation (EXPERIMENTAL)"
158 depends on EXPERIMENTAL && CYCLADES
159 help
160 The Cyclades-Z family of multiport cards allows 2 (two) driver op
161 modes: polling and interrupt. In polling mode, the driver will check
162 the status of the Cyclades-Z ports every certain amount of time
163 (which is called polling cycle and is configurable). In interrupt
164 mode, it will use an interrupt line (IRQ) in order to check the
165 status of the Cyclades-Z ports. The default op mode is polling. If
166 unsure, say N.
167
168config DIGIEPCA
169 tristate "Digiboard Intelligent Async Support"
Al Viro27d41712007-07-17 08:49:35 +0100170 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700171 ---help---
172 This is a driver for Digi International's Xx, Xeve, and Xem series
173 of cards which provide multiple serial ports. You would need
174 something like this to connect more than two modems to your Linux
175 box, for instance in order to become a dial-in server. This driver
176 supports the original PC (ISA) boards as well as PCI, and EISA. If
177 you have a card like this, say Y here and read the file
178 <file:Documentation/digiepca.txt>.
179
180 To compile this driver as a module, choose M here: the
181 module will be called epca.
182
183config ESPSERIAL
184 tristate "Hayes ESP serial port support"
Alan Cox33f0f882006-01-09 20:54:13 -0800185 depends on SERIAL_NONSTANDARD && ISA && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700186 help
187 This is a driver which supports Hayes ESP serial ports. Both single
188 port cards and multiport cards are supported. Make sure to read
189 <file:Documentation/hayes-esp.txt>.
190
191 To compile this driver as a module, choose M here: the
192 module will be called esp.
193
194 If unsure, say N.
195
196config MOXA_INTELLIO
197 tristate "Moxa Intellio support"
Al Viro8a023672007-07-20 00:24:22 +0100198 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
Jiri Slaby49209162008-05-14 16:05:53 -0700199 select FW_LOADER
Linus Torvalds1da177e2005-04-16 15:20:36 -0700200 help
201 Say Y here if you have a Moxa Intellio multiport serial card.
202
203 To compile this driver as a module, choose M here: the
204 module will be called moxa.
205
206config MOXA_SMARTIO
Jiri Slaby98c47ea2007-02-10 01:45:15 -0800207 tristate "Moxa SmartIO support v. 2.0"
Jiri Slabyfb0c9292006-12-13 00:34:19 -0800208 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
Jiri Slaby037ad482006-12-08 02:38:11 -0800209 help
210 Say Y here if you have a Moxa SmartIO multiport serial card and/or
211 want to help develop a new version of this driver.
212
213 This is upgraded (1.9.1) driver from original Moxa drivers with
214 changes finally resulting in PCI probing.
215
Jiri Slaby037ad482006-12-08 02:38:11 -0800216 This driver can also be built as a module. The module will be called
Jiri Slaby1c456072008-02-07 00:16:46 -0800217 mxser. If you want to do that, say M here.
Jiri Slaby037ad482006-12-08 02:38:11 -0800218
Linus Torvalds1da177e2005-04-16 15:20:36 -0700219config ISI
220 tristate "Multi-Tech multiport card support (EXPERIMENTAL)"
Randy Dunlapa3808ac2006-12-13 00:34:18 -0800221 depends on SERIAL_NONSTANDARD && PCI
maximilian attems5ff2a7e2006-03-26 01:37:35 -0800222 select FW_LOADER
Linus Torvalds1da177e2005-04-16 15:20:36 -0700223 help
224 This is a driver for the Multi-Tech cards which provide several
225 serial ports. The driver is experimental and can currently only be
226 built as a module. The module will be called isicom.
227 If you want to do that, choose M here.
228
229config SYNCLINK
230 tristate "Microgate SyncLink card support"
Al Viroa5532602005-05-04 05:39:42 +0100231 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
Linus Torvalds1da177e2005-04-16 15:20:36 -0700232 help
233 Provides support for the SyncLink ISA and PCI multiprotocol serial
234 adapters. These adapters support asynchronous and HDLC bit
235 synchronous communication up to 10Mbps (PCI adapter).
236
237 This driver can only be built as a module ( = code which can be
238 inserted in and removed from the running kernel whenever you want).
239 The module will be called synclink. If you want to do that, say M
240 here.
241
242config SYNCLINKMP
243 tristate "SyncLink Multiport support"
Al Viro8a023672007-07-20 00:24:22 +0100244 depends on SERIAL_NONSTANDARD && PCI
Linus Torvalds1da177e2005-04-16 15:20:36 -0700245 help
246 Enable support for the SyncLink Multiport (2 or 4 ports)
247 serial adapter, running asynchronous and HDLC communications up
248 to 2.048Mbps. Each ports is independently selectable for
249 RS-232, V.35, RS-449, RS-530, and X.21
250
251 This driver may be built as a module ( = code which can be
252 inserted in and removed from the running kernel whenever you want).
253 The module will be called synclinkmp. If you want to do that, say M
254 here.
255
Paul Fulghum705b6c72006-01-08 01:02:06 -0800256config SYNCLINK_GT
257 tristate "SyncLink GT/AC support"
Al Viro8ef9cf32006-02-01 06:07:15 -0500258 depends on SERIAL_NONSTANDARD && PCI
Paul Fulghum705b6c72006-01-08 01:02:06 -0800259 help
260 Support for SyncLink GT and SyncLink AC families of
261 synchronous and asynchronous serial adapters
262 manufactured by Microgate Systems, Ltd. (www.microgate.com)
263
Linus Torvalds1da177e2005-04-16 15:20:36 -0700264config N_HDLC
265 tristate "HDLC line discipline support"
266 depends on SERIAL_NONSTANDARD
267 help
268 Allows synchronous HDLC communications with tty device drivers that
269 support synchronous HDLC such as the Microgate SyncLink adapter.
270
271 This driver can only be built as a module ( = code which can be
272 inserted in and removed from the running kernel whenever you want).
273 The module will be called n_hdlc. If you want to do that, say M
274 here.
275
276config RISCOM8
277 tristate "SDL RISCom/8 card support"
Jeff Garzikd9afa432008-02-06 01:36:11 -0800278 depends on SERIAL_NONSTANDARD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700279 help
280 This is a driver for the SDL Communications RISCom/8 multiport card,
281 which gives you many serial ports. You would need something like
282 this to connect more than two modems to your Linux box, for instance
283 in order to become a dial-in server. If you have a card like that,
284 say Y here and read the file <file:Documentation/riscom8.txt>.
285
286 Also it's possible to say M here and compile this driver as kernel
287 loadable module; the module will be called riscom8.
288
289config SPECIALIX
290 tristate "Specialix IO8+ card support"
291 depends on SERIAL_NONSTANDARD
292 help
293 This is a driver for the Specialix IO8+ multiport card (both the
294 ISA and the PCI version) which gives you many serial ports. You
295 would need something like this to connect more than two modems to
296 your Linux box, for instance in order to become a dial-in server.
297
298 If you have a card like that, say Y here and read the file
299 <file:Documentation/specialix.txt>. Also it's possible to say M here
300 and compile this driver as kernel loadable module which will be
301 called specialix.
302
303config SPECIALIX_RTSCTS
304 bool "Specialix DTR/RTS pin is RTS"
305 depends on SPECIALIX
306 help
307 The Specialix IO8+ card can only support either RTS or DTR. If you
308 say N here, the driver will use the pin as "DTR" when the tty is in
309 software handshake mode. If you say Y here or hardware handshake is
310 on, it will always be RTS. Read the file
311 <file:Documentation/specialix.txt> for more information.
312
313config SX
314 tristate "Specialix SX (and SI) card support"
Jiri Slaby3468a332006-12-13 00:34:20 -0800315 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700316 help
317 This is a driver for the SX and SI multiport serial cards.
318 Please read the file <file:Documentation/sx.txt> for details.
319
320 This driver can only be built as a module ( = code which can be
321 inserted in and removed from the running kernel whenever you want).
322 The module will be called sx. If you want to do that, say M here.
323
324config RIO
325 tristate "Specialix RIO system support"
Alan Cox655fdea2006-05-15 09:44:26 -0700326 depends on SERIAL_NONSTANDARD
Linus Torvalds1da177e2005-04-16 15:20:36 -0700327 help
328 This is a driver for the Specialix RIO, a smart serial card which
329 drives an outboard box that can support up to 128 ports. Product
330 information is at <http://www.perle.com/support/documentation.html#multiport>.
331 There are both ISA and PCI versions.
332
333config RIO_OLDPCI
334 bool "Support really old RIO/PCI cards"
335 depends on RIO
336 help
337 Older RIO PCI cards need some initialization-time configuration to
338 determine the IRQ and some control addresses. If you have a RIO and
339 this doesn't seem to work, try setting this to Y.
340
341config STALDRV
342 bool "Stallion multiport serial support"
343 depends on SERIAL_NONSTANDARD
344 help
345 Stallion cards give you many serial ports. You would need something
346 like this to connect more than two modems to your Linux box, for
347 instance in order to become a dial-in server. If you say Y here,
348 you will be asked for your specific card model in the next
349 questions. Make sure to read <file:Documentation/stallion.txt> in
350 this case. If you have never heard about all this, it's safe to
351 say N.
352
353config STALLION
354 tristate "Stallion EasyIO or EC8/32 support"
Al Viro27d41712007-07-17 08:49:35 +0100355 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700356 help
357 If you have an EasyIO or EasyConnection 8/32 multiport Stallion
358 card, then this is for you; say Y. Make sure to read
359 <file:Documentation/stallion.txt>.
360
361 To compile this driver as a module, choose M here: the
362 module will be called stallion.
363
364config ISTALLION
365 tristate "Stallion EC8/64, ONboard, Brumby support"
Al Viro27d41712007-07-17 08:49:35 +0100366 depends on STALDRV && BROKEN_ON_SMP && (ISA || EISA || PCI)
Linus Torvalds1da177e2005-04-16 15:20:36 -0700367 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
Frank Seidel20fd1e32007-11-09 14:49:23 +0100375config NOZOMI
376 tristate "HSDPA Broadband Wireless Data Card - Globe Trotter"
377 depends on PCI && EXPERIMENTAL
378 help
379 If you have a HSDPA driver Broadband Wireless Data Card -
380 Globe Trotter PCMCIA card, say Y here.
381
382 To compile this driver as a module, choose M here, the module
383 will be called nozomi.
384
Linus Torvalds1da177e2005-04-16 15:20:36 -0700385config A2232
386 tristate "Commodore A2232 serial support (EXPERIMENTAL)"
387 depends on EXPERIMENTAL && ZORRO && BROKEN_ON_SMP
388 ---help---
389 This option supports the 2232 7-port serial card shipped with the
390 Amiga 2000 and other Zorro-bus machines, dating from 1989. At
391 a max of 19,200 bps, the ports are served by a 6551 ACIA UART chip
392 each, plus a 8520 CIA, and a master 6502 CPU and buffer as well. The
393 ports were connected with 8 pin DIN connectors on the card bracket,
394 for which 8 pin to DB25 adapters were supplied. The card also had
395 jumpers internally to toggle various pinning configurations.
396
397 This driver can be built as a module; but then "generic_serial"
398 will also be built as a module. This has to be loaded before
399 "ser_a2232". If you want to do this, answer M here.
400
401config SGI_SNSC
402 bool "SGI Altix system controller communication support"
403 depends on (IA64_SGI_SN2 || IA64_GENERIC)
404 help
405 If you have an SGI Altix and you want to enable system
406 controller communication from user space (you want this!),
407 say Y. Otherwise, say N.
408
Bruce Losuree1e19742005-04-25 13:09:41 -0700409config SGI_TIOCX
410 bool "SGI TIO CX driver support"
411 depends on (IA64_SGI_SN2 || IA64_GENERIC)
412 help
413 If you have an SGI Altix and you have fpga devices attached
414 to your TIO, say Y here, otherwise say N.
415
416config SGI_MBCS
417 tristate "SGI FPGA Core Services driver support"
Bruce Losureae40aae2005-04-04 13:23:00 -0700418 depends on SGI_TIOCX
Bruce Losuree1e19742005-04-25 13:09:41 -0700419 help
420 If you have an SGI Altix with an attached SABrick
421 say Y or M here, otherwise say N.
422
Linus Torvalds1da177e2005-04-16 15:20:36 -0700423source "drivers/serial/Kconfig"
424
425config UNIX98_PTYS
426 bool "Unix98 PTY support" if EMBEDDED
427 default y
428 ---help---
429 A pseudo terminal (PTY) is a software device consisting of two
430 halves: a master and a slave. The slave device behaves identical to
431 a physical terminal; the master device is used by a process to
432 read data from and write data to the slave, thereby emulating a
433 terminal. Typical programs for the master side are telnet servers
434 and xterms.
435
436 Linux has traditionally used the BSD-like names /dev/ptyxx for
437 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
438 has a number of problems. The GNU C library glibc 2.1 and later,
439 however, supports the Unix98 naming standard: in order to acquire a
440 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
441 terminal is then made available to the process and the pseudo
442 terminal slave can be accessed as /dev/pts/<number>. What was
443 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
444
445 All modern Linux systems use the Unix98 ptys. Say Y unless
446 you're on an embedded system and want to conserve memory.
447
448config LEGACY_PTYS
449 bool "Legacy (BSD) PTY support"
450 default y
451 ---help---
452 A pseudo terminal (PTY) is a software device consisting of two
453 halves: a master and a slave. The slave device behaves identical to
454 a physical terminal; the master device is used by a process to
455 read data from and write data to the slave, thereby emulating a
456 terminal. Typical programs for the master side are telnet servers
457 and xterms.
458
459 Linux has traditionally used the BSD-like names /dev/ptyxx
460 for masters and /dev/ttyxx for slaves of pseudo
461 terminals. This scheme has a number of problems, including
462 security. This option enables these legacy devices; on most
463 systems, it is safe to say N.
464
465
466config LEGACY_PTY_COUNT
467 int "Maximum number of legacy PTY in use"
468 depends on LEGACY_PTYS
Kay Sievers345ee832007-11-14 23:39:42 +0100469 range 0 256
Linus Torvalds1da177e2005-04-16 15:20:36 -0700470 default "256"
471 ---help---
472 The maximum number of legacy PTYs that can be used at any one time.
473 The default is 256, and should be more than enough. Embedded
474 systems may want to reduce this to save memory.
475
476 When not in use, each legacy PTY occupies 12 bytes on 32-bit
477 architectures and 24 bytes on 64-bit architectures.
478
Benjamin Herrenschmidta45b8392006-07-04 15:06:20 +1000479config BRIQ_PANEL
480 tristate 'Total Impact briQ front panel driver'
Paul Mackerras2818c5d2006-08-25 15:08:21 +1000481 depends on PPC_CHRP
Benjamin Herrenschmidta45b8392006-07-04 15:06:20 +1000482 ---help---
483 The briQ is a small footprint CHRP computer with a frontpanel VFD, a
484 tristate led and two switches. It is the size of a CDROM drive.
485
486 If you have such one and want anything showing on the VFD then you
487 must answer Y here.
488
489 To compile this driver as a module, choose M here: the
490 module will be called briq_panel.
491
492 It's safe to say N here.
493
Mike Frysinger2dc63a82008-04-25 08:04:56 +0800494config BFIN_OTP
495 tristate "Blackfin On-Chip OTP Memory Support"
496 depends on BLACKFIN && (BF52x || BF54x)
497 default y
498 help
499 If you say Y here, you will get support for a character device
500 interface into the One Time Programmable memory pages that are
501 stored on the Blackfin processor. This will not get you access
502 to the secure memory pages however. You will need to write your
503 own secure code and reader for that.
504
505 To compile this driver as a module, choose M here: the module
506 will be called bfin-otp.
507
508 If unsure, it is safe to say Y.
509
510config BFIN_OTP_WRITE_ENABLE
511 bool "Enable writing support of OTP pages"
512 depends on BFIN_OTP
513 default n
514 help
515 If you say Y here, you will enable support for writing of the
516 OTP pages. This is dangerous by nature as you can only program
517 the pages once, so only enable this option when you actually
518 need it so as to not inadvertently clobber data.
519
520 If unsure, say N.
521
Linus Torvalds1da177e2005-04-16 15:20:36 -0700522config PRINTER
523 tristate "Parallel printer support"
524 depends on PARPORT
525 ---help---
526 If you intend to attach a printer to the parallel port of your Linux
527 box (as opposed to using a serial printer; if the connector at the
528 printer has 9 or 25 holes ["female"], then it's serial), say Y.
529 Also read the Printing-HOWTO, available from
530 <http://www.tldp.org/docs.html#howto>.
531
532 It is possible to share one parallel port among several devices
533 (e.g. printer and ZIP drive) and it is safe to compile the
534 corresponding drivers into the kernel.
535
536 To compile this driver as a module, choose M here and read
537 <file:Documentation/parport.txt>. The module will be called lp.
538
539 If you have several parallel ports, you can specify which ports to
540 use with the "lp" kernel command line option. (Try "man bootparam"
541 or see the documentation of your boot loader (lilo or loadlin) about
542 how to pass options to the kernel at boot time.) The syntax of the
543 "lp" command line option can be found in <file:drivers/char/lp.c>.
544
545 If you have more than 8 printers, you need to increase the LP_NO
546 macro in lp.c and the PARPORT_MAX macro in parport.h.
547
548config LP_CONSOLE
549 bool "Support for console on line printer"
550 depends on PRINTER
551 ---help---
552 If you want kernel messages to be printed out as they occur, you
553 can have a console on the printer. This option adds support for
554 doing that; to actually get it to happen you need to pass the
555 option "console=lp0" to the kernel at boot time.
556
557 If the printer is out of paper (or off, or unplugged, or too
558 busy..) the kernel will stall until the printer is ready again.
559 By defining CONSOLE_LP_STRICT to 0 (at your own risk) you
560 can make the kernel continue when this happens,
561 but it'll lose the kernel messages.
562
563 If unsure, say N.
564
565config PPDEV
566 tristate "Support for user-space parallel port device drivers"
567 depends on PARPORT
568 ---help---
569 Saying Y to this adds support for /dev/parport device nodes. This
570 is needed for programs that want portable access to the parallel
571 port, for instance deviceid (which displays Plug-and-Play device
572 IDs).
573
574 This is the parallel port equivalent of SCSI generic support (sg).
575 It is safe to say N to this -- it is not needed for normal printing
576 or parallel port CD-ROM/disk support.
577
578 To compile this driver as a module, choose M here: the
579 module will be called ppdev.
580
581 If unsure, say N.
582
Ryan S. Arnold45d607e2006-03-27 21:25:16 +0200583config HVC_DRIVER
584 bool
585 help
Rusty Russell3e6c6f62007-10-16 23:30:13 -0700586 Generic "hypervisor virtual console" infrastructure for various
Rusty Russell2d1df812007-10-16 23:30:14 -0700587 hypervisors (pSeries, iSeries, Xen, lguest).
Ryan S. Arnold45d607e2006-03-27 21:25:16 +0200588 It will automatically be selected if one of the back-end console drivers
589 is selected.
590
591
Linus Torvalds1da177e2005-04-16 15:20:36 -0700592config HVC_CONSOLE
593 bool "pSeries Hypervisor Virtual Console support"
594 depends on PPC_PSERIES
Ryan S. Arnold45d607e2006-03-27 21:25:16 +0200595 select HVC_DRIVER
Linus Torvalds1da177e2005-04-16 15:20:36 -0700596 help
597 pSeries machines when partitioned support a hypervisor virtual
598 console. This driver allows each pSeries partition to have a console
599 which is accessed via the HMC.
600
Stephen Rothwell8bff05b2006-07-13 18:51:22 +1000601config HVC_ISERIES
602 bool "iSeries Hypervisor Virtual Console support"
Stephen Rothwellb15f7922007-05-08 15:05:31 +1000603 depends on PPC_ISERIES
604 default y
Stephen Rothwell8bff05b2006-07-13 18:51:22 +1000605 select HVC_DRIVER
606 help
607 iSeries machines support a hypervisor virtual console.
608
Arnd Bergmannf4d17492006-03-27 21:26:03 +0200609config HVC_RTAS
610 bool "IBM RTAS Console support"
611 depends on PPC_RTAS
612 select HVC_DRIVER
613 help
614 IBM Console device driver which makes use of RTAS
615
Ishizaki Kou3cdc20e2007-02-02 16:44:08 +0900616config HVC_BEAT
617 bool "Toshiba's Beat Hypervisor Console support"
618 depends on PPC_CELLEB
619 select HVC_DRIVER
620 help
621 Toshiba's Cell Reference Set Beat Console device driver
622
Jeremy Fitzhardingeb536b4b2007-07-17 18:37:06 -0700623config HVC_XEN
624 bool "Xen Hypervisor Console support"
625 depends on XEN
626 select HVC_DRIVER
627 default y
628 help
629 Xen virtual console device driver
630
Rusty Russell31610432007-10-22 11:03:39 +1000631config VIRTIO_CONSOLE
632 bool
633 select HVC_DRIVER
634
Linus Torvalds1da177e2005-04-16 15:20:36 -0700635config HVCS
636 tristate "IBM Hypervisor Virtual Console Server support"
637 depends on PPC_PSERIES
638 help
639 Partitionable IBM Power5 ppc64 machines allow hosting of
640 firmware virtual consoles from one Linux partition by
641 another Linux partition. This driver allows console data
642 from Linux partitions to be accessed through TTY device
643 interfaces in the device tree of a Linux partition running
644 this driver.
645
646 To compile this driver as a module, choose M here: the
647 module will be called hvcs.ko. Additionally, this module
648 will depend on arch specific APIs exported from hvcserver.ko
649 which will also be compiled when this driver is built as a
650 module.
651
652source "drivers/char/ipmi/Kconfig"
653
Linus Torvalds1da177e2005-04-16 15:20:36 -0700654config DS1620
655 tristate "NetWinder thermometer support"
656 depends on ARCH_NETWINDER
657 help
658 Say Y here to include support for the thermal management hardware
659 found in the NetWinder. This driver allows the user to control the
660 temperature set points and to read the current temperature.
661
662 It is also possible to say M here to build it as a module (ds1620)
663 It is recommended to be used on a NetWinder, but it is not a
664 necessity.
665
666config NWBUTTON
667 tristate "NetWinder Button"
668 depends on ARCH_NETWINDER
669 ---help---
670 If you say Y here and create a character device node /dev/nwbutton
671 with major and minor numbers 10 and 158 ("man mknod"), then every
672 time the orange button is pressed a number of times, the number of
673 times the button was pressed will be written to that device.
674
675 This is most useful for applications, as yet unwritten, which
676 perform actions based on how many times the button is pressed in a
677 row.
678
679 Do not hold the button down for too long, as the driver does not
680 alter the behaviour of the hardware reset circuitry attached to the
681 button; it will still execute a hard reset if the button is held
682 down for longer than approximately five seconds.
683
684 To compile this driver as a module, choose M here: the
685 module will be called nwbutton.
686
687 Most people will answer Y to this question and "Reboot Using Button"
688 below to be able to initiate a system shutdown from the button.
689
690config NWBUTTON_REBOOT
691 bool "Reboot Using Button"
692 depends on NWBUTTON
693 help
694 If you say Y here, then you will be able to initiate a system
695 shutdown and reboot by pressing the orange button a number of times.
696 The number of presses to initiate the shutdown is two by default,
697 but this can be altered by modifying the value of NUM_PRESSES_REBOOT
698 in nwbutton.h and recompiling the driver or, if you compile the
699 driver as a module, you can specify the number of presses at load
700 time with "insmod button reboot_count=<something>".
701
702config NWFLASH
703 tristate "NetWinder flash support"
704 depends on ARCH_NETWINDER
705 ---help---
706 If you say Y here and create a character device /dev/flash with
707 major 10 and minor 160 you can manipulate the flash ROM containing
708 the NetWinder firmware. Be careful as accidentally overwriting the
709 flash contents can render your computer unbootable. On no account
710 allow random users access to this device. :-)
711
712 To compile this driver as a module, choose M here: the
713 module will be called nwflash.
714
715 If you're not sure, say N.
716
Michael Buesch844dd052006-06-26 00:24:59 -0700717source "drivers/char/hw_random/Kconfig"
718
Linus Torvalds1da177e2005-04-16 15:20:36 -0700719config NVRAM
720 tristate "/dev/nvram support"
Brian Gerst0d078f62005-10-30 14:59:20 -0800721 depends on ATARI || X86 || ARM || GENERIC_NVRAM
Linus Torvalds1da177e2005-04-16 15:20:36 -0700722 ---help---
723 If you say Y here and create a character special file /dev/nvram
724 with major number 10 and minor number 144 using mknod ("man mknod"),
725 you get read and write access to the extra bytes of non-volatile
726 memory in the real time clock (RTC), which is contained in every PC
727 and most Ataris. The actual number of bytes varies, depending on the
728 nvram in the system, but is usually 114 (128-14 for the RTC).
729
730 This memory is conventionally called "CMOS RAM" on PCs and "NVRAM"
731 on Ataris. /dev/nvram may be used to view settings there, or to
732 change them (with some utility). It could also be used to frequently
733 save a few bits of very important data that may not be lost over
734 power-off and for which writing to disk is too insecure. Note
735 however that most NVRAM space in a PC belongs to the BIOS and you
736 should NEVER idly tamper with it. See Ralf Brown's interrupt list
737 for a guide to the use of CMOS bytes by your BIOS.
738
739 On Atari machines, /dev/nvram is always configured and does not need
740 to be selected.
741
742 To compile this driver as a module, choose M here: the
743 module will be called nvram.
744
David Brownellc7500902008-04-28 02:11:52 -0700745#
746# These legacy RTC drivers just cause too many conflicts with the generic
747# RTC framework ... let's not even try to coexist any more.
748#
749if RTC_LIB=n
750
Linus Torvalds1da177e2005-04-16 15:20:36 -0700751config RTC
David Brownelle6d2bb22008-06-12 15:21:55 -0700752 tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
David Brownellc7500902008-04-28 02:11:52 -0700753 depends on !PPC && !PARISC && !IA64 && !M68K && !SPARC && !FRV \
754 && !ARM && !SUPERH && !S390 && !AVR32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700755 ---help---
756 If you say Y here and create a character special file /dev/rtc with
757 major number 10 and minor number 135 using mknod ("man mknod"), you
758 will get access to the real time clock (or hardware clock) built
759 into your computer.
760
761 Every PC has such a clock built in. It can be used to generate
762 signals from as low as 1Hz up to 8192Hz, and can also be used
763 as a 24 hour alarm. It reports status information via the file
764 /proc/driver/rtc and its behaviour is set by various ioctls on
765 /dev/rtc.
766
767 If you run Linux on a multiprocessor machine and said Y to
768 "Symmetric Multi Processing" above, you should say Y here to read
769 and set the RTC in an SMP compatible fashion.
770
771 If you think you have a use for such a device (such as periodic data
772 sampling), then say Y here, and read <file:Documentation/rtc.txt>
773 for details.
774
775 To compile this driver as a module, choose M here: the
776 module will be called rtc.
777
Al Viro22405982007-07-22 00:37:48 -0700778config JS_RTC
779 tristate "Enhanced Real Time Clock Support"
780 depends on SPARC32 && PCI
781 ---help---
782 If you say Y here and create a character special file /dev/rtc with
783 major number 10 and minor number 135 using mknod ("man mknod"), you
784 will get access to the real time clock (or hardware clock) built
785 into your computer.
786
787 Every PC has such a clock built in. It can be used to generate
788 signals from as low as 1Hz up to 8192Hz, and can also be used
789 as a 24 hour alarm. It reports status information via the file
790 /proc/driver/rtc and its behaviour is set by various ioctls on
791 /dev/rtc.
792
793 If you think you have a use for such a device (such as periodic data
794 sampling), then say Y here, and read <file:Documentation/rtc.txt>
795 for details.
796
797 To compile this driver as a module, choose M here: the
798 module will be called js-rtc.
799
Linus Torvalds1da177e2005-04-16 15:20:36 -0700800config SGI_DS1286
801 tristate "SGI DS1286 RTC support"
Thomas Bogendoerferf5d3f302008-02-06 01:37:26 -0800802 depends on SGI_HAS_DS1286
Linus Torvalds1da177e2005-04-16 15:20:36 -0700803 help
804 If you say Y here and create a character special file /dev/rtc with
805 major number 10 and minor number 135 using mknod ("man mknod"), you
806 will get access to the real time clock built into your computer.
807 Every SGI has such a clock built in. It reports status information
808 via the file /proc/rtc and its behaviour is set by various ioctls on
809 /dev/rtc.
810
811config SGI_IP27_RTC
812 bool "SGI M48T35 RTC support"
813 depends on SGI_IP27
814 help
815 If you say Y here and create a character special file /dev/rtc with
816 major number 10 and minor number 135 using mknod ("man mknod"), you
817 will get access to the real time clock built into your computer.
818 Every SGI has such a clock built in. It reports status information
819 via the file /proc/rtc and its behaviour is set by various ioctls on
820 /dev/rtc.
821
822config GEN_RTC
823 tristate "Generic /dev/rtc emulation"
Adrian Bunkcc65d902008-04-14 17:16:44 +0300824 depends on RTC!=y && !IA64 && !ARM && !M32R && !MIPS && !SPARC && !FRV && !S390 && !SUPERH && !AVR32
Linus Torvalds1da177e2005-04-16 15:20:36 -0700825 ---help---
826 If you say Y here and create a character special file /dev/rtc with
827 major number 10 and minor number 135 using mknod ("man mknod"), you
828 will get access to the real time clock (or hardware clock) built
829 into your computer.
830
831 It reports status information via the file /proc/driver/rtc and its
832 behaviour is set by various ioctls on /dev/rtc. If you enable the
833 "extended RTC operation" below it will also provide an emulation
834 for RTC_UIE which is required by some programs and may improve
835 precision in some cases.
836
837 To compile this driver as a module, choose M here: the
838 module will be called genrtc.
839
840config GEN_RTC_X
841 bool "Extended RTC operation"
842 depends on GEN_RTC
843 help
844 Provides an emulation for RTC_UIE which is required by some programs
845 and may improve precision of the generic RTC support in some cases.
846
847config EFI_RTC
848 bool "EFI Real Time Clock Services"
849 depends on IA64
850
851config DS1302
852 tristate "DS1302 RTC support"
853 depends on M32R && (PLAT_M32700UT || PLAT_OPSPUT)
854 help
855 If you say Y here and create a character special file /dev/rtc with
856 major number 121 and minor number 0 using mknod ("man mknod"), you
857 will get access to the real time clock (or hardware clock) built
858 into your computer.
859
David Brownellc7500902008-04-28 02:11:52 -0700860endif # RTC_LIB
861
Linus Torvalds1da177e2005-04-16 15:20:36 -0700862config COBALT_LCD
863 bool "Support for Cobalt LCD"
864 depends on MIPS_COBALT
865 help
866 This option enables support for the LCD display and buttons found
867 on Cobalt systems through a misc device.
868
869config DTLK
870 tristate "Double Talk PC internal speech card support"
Martin Schwidefskyeeca7a32007-05-10 15:45:56 +0200871 depends on ISA
Linus Torvalds1da177e2005-04-16 15:20:36 -0700872 help
873 This driver is for the DoubleTalk PC, a speech synthesizer
874 manufactured by RC Systems (<http://www.rcsys.com/>). It is also
875 called the `internal DoubleTalk'.
876
877 To compile this driver as a module, choose M here: the
878 module will be called dtlk.
879
Stephen Neuendorfferef141a02008-02-06 04:24:09 +1100880config XILINX_HWICAP
881 tristate "Xilinx HWICAP Support"
882 depends on XILINX_VIRTEX
883 help
884 This option enables support for Xilinx Internal Configuration
885 Access Port (ICAP) driver. The ICAP is used on Xilinx Virtex
886 FPGA platforms to partially reconfigure the FPGA at runtime.
887
888 If unsure, say N.
889
Linus Torvalds1da177e2005-04-16 15:20:36 -0700890config R3964
891 tristate "Siemens R3964 line discipline"
892 ---help---
893 This driver allows synchronous communication with devices using the
894 Siemens R3964 packet protocol. Unless you are dealing with special
895 hardware like PLCs, you are unlikely to need this.
896
897 To compile this driver as a module, choose M here: the
898 module will be called n_r3964.
899
900 If unsure, say N.
901
902config APPLICOM
903 tristate "Applicom intelligent fieldbus card support"
904 depends on PCI
905 ---help---
906 This driver provides the kernel-side support for the intelligent
907 fieldbus cards made by Applicom International. More information
908 about these cards can be found on the WWW at the address
909 <http://www.applicom-int.com/>, or by email from David Woodhouse
910 <dwmw2@infradead.org>.
911
912 To compile this driver as a module, choose M here: the
913 module will be called applicom.
914
915 If unsure, say N.
916
917config SONYPI
918 tristate "Sony Vaio Programmable I/O Control Device support (EXPERIMENTAL)"
919 depends on EXPERIMENTAL && X86 && PCI && INPUT && !64BIT
920 ---help---
921 This driver enables access to the Sony Programmable I/O Control
922 Device which can be found in many (all ?) Sony Vaio laptops.
923
924 If you have one of those laptops, read
Carlos Corbacho018a6512008-02-09 01:32:19 +0000925 <file:Documentation/laptops/sonypi.txt>, and say Y or M here.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700926
927 To compile this driver as a module, choose M here: the
928 module will be called sonypi.
929
Yoichi Yuasa09762512007-05-06 14:51:58 -0700930config GPIO_TB0219
931 tristate "TANBAC TB0219 GPIO support"
Robert P. J. Daybef1f402006-12-12 20:04:19 +0100932 depends on TANBAC_TB022X
Yoichi Yuasa584e1232006-06-25 05:49:11 -0700933 select GPIO_VR41XX
Linus Torvalds1da177e2005-04-16 15:20:36 -0700934
Linus Torvalds1da177e2005-04-16 15:20:36 -0700935source "drivers/char/pcmcia/Kconfig"
936
937config MWAVE
938 tristate "ACP Modem (Mwave) support"
939 depends on X86
940 select SERIAL_8250
941 ---help---
942 The ACP modem (Mwave) for Linux is a WinModem. It is composed of a
943 kernel driver and a user level application. Together these components
944 support direct attachment to public switched telephone networks (PSTNs)
945 and support selected world wide countries.
946
947 This version of the ACP Modem driver supports the IBM Thinkpad 600E,
948 600, and 770 that include on board ACP modem hardware.
949
950 The modem also supports the standard communications port interface
951 (ttySx) and is compatible with the Hayes AT Command Set.
952
953 The user level application needed to use this driver can be found at
954 the IBM Linux Technology Center (LTC) web site:
955 <http://www.ibm.com/linux/ltc/>.
956
957 If you own one of the above IBM Thinkpads which has the Mwave chipset
958 in it, say Y.
959
960 To compile this driver as a module, choose M here: the
961 module will be called mwave.
962
963config SCx200_GPIO
964 tristate "NatSemi SCx200 GPIO Support"
965 depends on SCx200
Jim Cromie7a8e2a52006-06-27 02:54:27 -0700966 select NSC_GPIO
Linus Torvalds1da177e2005-04-16 15:20:36 -0700967 help
968 Give userspace access to the GPIO pins on the National
969 Semiconductor SCx200 processors.
970
971 If compiled as a module, it will be called scx200_gpio.
972
Jim Cromie7a8e2a52006-06-27 02:54:27 -0700973config PC8736x_GPIO
974 tristate "NatSemi PC8736x GPIO Support"
975 depends on X86
976 default SCx200_GPIO # mostly N
977 select NSC_GPIO # needed for support routines
978 help
979 Give userspace access to the GPIO pins on the National
980 Semiconductor PC-8736x (x=[03456]) SuperIO chip. The chip
981 has multiple functional units, inc several managed by
982 hwmon/pc87360 driver. Tested with PC-87366
983
984 If compiled as a module, it will be called pc8736x_gpio.
985
986config NSC_GPIO
987 tristate "NatSemi Base GPIO Support"
Dave Jones699352c2006-06-29 02:24:32 -0700988 depends on X86_32
Jim Cromie7a8e2a52006-06-27 02:54:27 -0700989 # selected by SCx200_GPIO and PC8736x_GPIO
990 # what about 2 selectors differing: m != y
991 help
992 Common support used (and needed) by scx200_gpio and
993 pc8736x_gpio drivers. If those drivers are built as
994 modules, this one will be too, named nsc_gpio
995
Ben Gardnere3291132006-01-09 20:51:29 -0800996config CS5535_GPIO
997 tristate "AMD CS5535/CS5536 GPIO (Geode Companion Device)"
998 depends on X86_32
999 help
1000 Give userspace access to the GPIO pins on the AMD CS5535 and
1001 CS5536 Geode companion devices.
1002
1003 If compiled as a module, it will be called cs5535_gpio.
1004
Yoichi Yuasae400bae2005-06-21 17:15:56 -07001005config GPIO_VR41XX
1006 tristate "NEC VR4100 series General-purpose I/O Unit support"
1007 depends on CPU_VR41XX
1008
Linus Torvalds1da177e2005-04-16 15:20:36 -07001009config RAW_DRIVER
Dave Jonesabd4aa52007-07-15 23:40:49 -07001010 tristate "RAW driver (/dev/raw/rawN)"
David Howells93614012006-09-30 20:45:40 +02001011 depends on BLOCK
Linus Torvalds1da177e2005-04-16 15:20:36 -07001012 help
Dave Jonesabd4aa52007-07-15 23:40:49 -07001013 The raw driver permits block devices to be bound to /dev/raw/rawN.
1014 Once bound, I/O against /dev/raw/rawN uses efficient zero-copy I/O.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001015 See the raw(8) manpage for more details.
1016
Dave Jonesabd4aa52007-07-15 23:40:49 -07001017 Applications should preferably open the device (eg /dev/hda1)
Linus Torvalds1da177e2005-04-16 15:20:36 -07001018 with the O_DIRECT flag.
1019
Andrew Morton0de502a2005-12-12 00:37:41 -08001020config MAX_RAW_DEVS
1021 int "Maximum number of RAW devices to support (1-8192)"
1022 depends on RAW_DRIVER
1023 default "256"
1024 help
1025 The maximum number of RAW devices that are supported.
1026 Default is 256. Increase this number in case you need lots of
1027 raw devices.
1028
Linus Torvalds1da177e2005-04-16 15:20:36 -07001029config HPET
1030 bool "HPET - High Precision Event Timer" if (X86 || IA64)
1031 default n
1032 depends on ACPI
1033 help
1034 If you say Y here, you will have a miscdevice named "/dev/hpet/". Each
1035 open selects one of the timers supported by the HPET. The timers are
Matt LaPlante3cb2fcc2006-11-30 05:22:59 +01001036 non-periodic and/or periodic.
Linus Torvalds1da177e2005-04-16 15:20:36 -07001037
1038config HPET_RTC_IRQ
David Brownelle6d2bb22008-06-12 15:21:55 -07001039 bool
1040 default HPET_EMULATE_RTC
1041 depends on RTC && HPET
Linus Torvalds1da177e2005-04-16 15:20:36 -07001042 help
1043 If you say Y here, you will disable RTC_IRQ in drivers/char/rtc.c. It
1044 is assumed the platform called hpet_alloc with the RTC IRQ values for
1045 the HPET timers.
1046
1047config HPET_MMAP
1048 bool "Allow mmap of HPET"
1049 default y
1050 depends on HPET
1051 help
1052 If you say Y here, user applications will be able to mmap
1053 the HPET registers.
1054
1055 In some hardware implementations, the page containing HPET
1056 registers may also contain other things that shouldn't be
1057 exposed to the user. If this applies to your hardware,
1058 say N here.
1059
Linus Torvalds1da177e2005-04-16 15:20:36 -07001060config HANGCHECK_TIMER
1061 tristate "Hangcheck timer"
Martin Schwidefskyabf3ea12007-05-10 15:45:59 +02001062 depends on X86 || IA64 || PPC64 || S390
Linus Torvalds1da177e2005-04-16 15:20:36 -07001063 help
1064 The hangcheck-timer module detects when the system has gone
1065 out to lunch past a certain margin. It can reboot the system
1066 or merely print a warning.
1067
1068config MMTIMER
1069 tristate "MMTIMER Memory mapped RTC for SGI Altix"
1070 depends on IA64_GENERIC || IA64_SGI_SN2
1071 default y
1072 help
1073 The mmtimer device allows direct userspace access to the
1074 Altix system timer.
1075
1076source "drivers/char/tpm/Kconfig"
1077
Mark Gross1a80ba82005-10-30 15:02:55 -08001078config TELCLOCK
Mark Gross03154a22007-03-06 13:58:45 -08001079 tristate "Telecom clock driver for ATCA SBC"
Geert Uytterhoeven4d99bfa2006-10-16 19:59:43 +02001080 depends on EXPERIMENTAL && X86
Mark Gross1a80ba82005-10-30 15:02:55 -08001081 default n
1082 help
Mark Gross03154a22007-03-06 13:58:45 -08001083 The telecom clock device is specific to the MPCBL0010 and MPCBL0050
1084 ATCA computers and allows direct userspace access to the
1085 configuration of the telecom clock configuration settings. This
1086 device is used for hardware synchronization across the ATCA backplane
1087 fabric. Upon loading, the driver exports a sysfs directory,
1088 /sys/devices/platform/telco_clock, with a number of files for
1089 controlling the behavior of this hardware.
Mark Gross1a80ba82005-10-30 15:02:55 -08001090
Russell King4f911d62007-05-08 00:28:17 -07001091config DEVPORT
1092 bool
1093 depends on !M68K
1094 depends on ISA || PCI
1095 default y
1096
Martin Schwidefsky61d48c22007-05-10 15:46:00 +02001097source "drivers/s390/char/Kconfig"
1098
Linus Torvalds1da177e2005-04-16 15:20:36 -07001099endmenu
1100