2 bool "Enable TTY" if EXPERT
5 Allows you to remove TTY support which can save space, and
6 blocks features that require TTY from inclusion in the kernel.
7 TTY is required for any text terminals or serial port
8 communication. Most users should leave this enabled.
13 bool "Virtual terminal" if EXPERT
14 depends on !S390 && !UML
18 If you say Y here, you will get support for terminal devices with
19 display and keyboard devices. These are called "virtual" because you
20 can run several virtual terminals (also called virtual consoles) on
21 one physical terminal. This is rather useful, for example one
22 virtual terminal can collect system messages and warnings, another
23 one can be used for a text-mode user session, and a third could run
24 an X session, all in parallel. Switching between virtual terminals
25 is done with certain key combinations, usually Alt-<function key>.
27 The setterm command ("man setterm") can be used to change the
28 properties (such as colors or beeping) of a virtual terminal. The
29 man page console_codes(4) ("man console_codes") contains the special
30 character sequences that can be used to change those properties
31 directly. The fonts used on virtual terminals can be changed with
32 the setfont ("man setfont") command and the key bindings are defined
33 with the loadkeys ("man loadkeys") command.
35 You need at least one virtual terminal device in order to make use
36 of your keyboard and monitor. Therefore, only people configuring an
37 embedded system would want to say N here in order to save some
38 memory; the only way to log into such a system is then via a serial
39 or network connection.
41 If unsure, say Y, or else you won't be able to do much with your new
42 shiny Linux system :-)
44 config CONSOLE_TRANSLATIONS
47 bool "Enable character translations in console" if EXPERT
49 This enables support for font mapping and Unicode translation
53 bool "Support for console on virtual terminal" if EXPERT
57 The system console is the device which receives all kernel messages
58 and warnings and which allows logins in single user mode. If you
59 answer Y here, a virtual terminal (the device used to interact with
60 a physical terminal) can be used as system console. This is the most
61 common mode of operations, so you should say Y here unless you want
62 the kernel messages be output only to a serial port (in which case
63 you should say Y to "Console on serial port", below).
65 If you do say Y here, by default the currently visible virtual
66 terminal (/dev/tty0) will be used as system console. You can change
67 that with a kernel command line option such as "console=tty3" which
68 would use the third virtual terminal as system console. (Try "man
69 bootparam" or see the documentation of your boot loader (lilo or
70 loadlin) about how to pass options to the kernel at boot time.)
74 config VT_CONSOLE_SLEEP
76 depends on VT_CONSOLE && PM_SLEEP
83 config VT_HW_CONSOLE_BINDING
84 bool "Support for binding and unbinding console drivers"
88 The virtual terminal is the device that interacts with the physical
89 terminal through console drivers. On these systems, at least one
90 console driver is loaded. In other configurations, additional console
91 drivers may be enabled, such as the framebuffer console. If more than
92 1 console driver is enabled, setting this to 'y' will allow you to
93 select the console driver that will serve as the backend for the
96 See <file:Documentation/console/console.txt> for more
97 information. For framebuffer console users, please refer to
98 <file:Documentation/fb/fbcon.txt>.
101 bool "Unix98 PTY support" if EXPERT
104 A pseudo terminal (PTY) is a software device consisting of two
105 halves: a master and a slave. The slave device behaves identical to
106 a physical terminal; the master device is used by a process to
107 read data from and write data to the slave, thereby emulating a
108 terminal. Typical programs for the master side are telnet servers
111 Linux has traditionally used the BSD-like names /dev/ptyxx for
112 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
113 has a number of problems. The GNU C library glibc 2.1 and later,
114 however, supports the Unix98 naming standard: in order to acquire a
115 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
116 terminal is then made available to the process and the pseudo
117 terminal slave can be accessed as /dev/pts/<number>. What was
118 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
120 All modern Linux systems use the Unix98 ptys. Say Y unless
121 you're on an embedded system and want to conserve memory.
124 bool "Legacy (BSD) PTY support"
127 A pseudo terminal (PTY) is a software device consisting of two
128 halves: a master and a slave. The slave device behaves identical to
129 a physical terminal; the master device is used by a process to
130 read data from and write data to the slave, thereby emulating a
131 terminal. Typical programs for the master side are telnet servers
134 Linux has traditionally used the BSD-like names /dev/ptyxx
135 for masters and /dev/ttyxx for slaves of pseudo
136 terminals. This scheme has a number of problems, including
137 security. This option enables these legacy devices; on most
138 systems, it is safe to say N.
141 config LEGACY_PTY_COUNT
142 int "Maximum number of legacy PTY in use"
143 depends on LEGACY_PTYS
147 The maximum number of legacy PTYs that can be used at any one time.
148 The default is 256, and should be more than enough. Embedded
149 systems may want to reduce this to save memory.
151 When not in use, each legacy PTY occupies 12 bytes on 32-bit
152 architectures and 24 bytes on 64-bit architectures.
154 config BFIN_JTAG_COMM
155 tristate "Blackfin JTAG Communication"
158 Add support for emulating a TTY device over the Blackfin JTAG.
160 To compile this driver as a module, choose M here: the
161 module will be called bfin_jtag_comm.
163 config BFIN_JTAG_COMM_CONSOLE
164 bool "Console on Blackfin JTAG"
165 depends on BFIN_JTAG_COMM=y
167 config SERIAL_NONSTANDARD
168 bool "Non-standard serial port support"
171 Say Y here if you have any non-standard serial boards -- boards
172 which aren't supported using the standard "dumb" serial driver.
173 This includes intelligent serial boards such as Cyclades,
174 Digiboards, etc. These are usually used for systems that need many
175 serial ports because they serve many terminals or dial-in
178 Note that the answer to this question won't directly affect the
179 kernel: saying N will just cause the configurator to skip all
180 the questions about non-standard serial boards.
182 Most people can say N here.
185 tristate "Comtrol RocketPort support"
186 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
188 This driver supports Comtrol RocketPort and RocketModem PCI boards.
189 These boards provide 2, 4, 8, 16, or 32 high-speed serial ports or
190 modems. For information about the RocketPort/RocketModem boards
191 and this driver read <file:Documentation/serial/rocket.txt>.
193 To compile this driver as a module, choose M here: the
194 module will be called rocket.
196 If you want to compile this driver into the kernel, say Y here. If
197 you don't have a Comtrol RocketPort/RocketModem card installed, say N.
200 tristate "Cyclades async mux support"
201 depends on SERIAL_NONSTANDARD && (PCI || ISA)
204 This driver supports Cyclades Z and Y multiserial boards.
205 You would need something like this to connect more than two modems to
206 your Linux box, for instance in order to become a dial-in server.
208 For information about the Cyclades-Z card, read
209 <file:Documentation/serial/README.cycladesZ>.
211 To compile this driver as a module, choose M here: the
212 module will be called cyclades.
214 If you haven't heard about it, it's safe to say N.
217 bool "Cyclades-Z interrupt mode operation"
218 depends on CYCLADES && PCI
220 The Cyclades-Z family of multiport cards allows 2 (two) driver op
221 modes: polling and interrupt. In polling mode, the driver will check
222 the status of the Cyclades-Z ports every certain amount of time
223 (which is called polling cycle and is configurable). In interrupt
224 mode, it will use an interrupt line (IRQ) in order to check the
225 status of the Cyclades-Z ports. The default op mode is polling. If
229 tristate "Moxa Intellio support"
230 depends on SERIAL_NONSTANDARD && (ISA || EISA || PCI)
233 Say Y here if you have a Moxa Intellio multiport serial card.
235 To compile this driver as a module, choose M here: the
236 module will be called moxa.
239 tristate "Moxa SmartIO support v. 2.0"
240 depends on SERIAL_NONSTANDARD && (PCI || EISA || ISA)
242 Say Y here if you have a Moxa SmartIO multiport serial card and/or
243 want to help develop a new version of this driver.
245 This is upgraded (1.9.1) driver from original Moxa drivers with
246 changes finally resulting in PCI probing.
248 This driver can also be built as a module. The module will be called
249 mxser. If you want to do that, say M here.
252 tristate "Microgate SyncLink card support"
253 depends on SERIAL_NONSTANDARD && PCI && ISA_DMA_API
255 Provides support for the SyncLink ISA and PCI multiprotocol serial
256 adapters. These adapters support asynchronous and HDLC bit
257 synchronous communication up to 10Mbps (PCI adapter).
259 This driver can only be built as a module ( = code which can be
260 inserted in and removed from the running kernel whenever you want).
261 The module will be called synclink. If you want to do that, say M
265 tristate "SyncLink Multiport support"
266 depends on SERIAL_NONSTANDARD && PCI
268 Enable support for the SyncLink Multiport (2 or 4 ports)
269 serial adapter, running asynchronous and HDLC communications up
270 to 2.048Mbps. Each ports is independently selectable for
271 RS-232, V.35, RS-449, RS-530, and X.21
273 This driver may be built as a module ( = code which can be
274 inserted in and removed from the running kernel whenever you want).
275 The module will be called synclinkmp. If you want to do that, say M
279 tristate "SyncLink GT/AC support"
280 depends on SERIAL_NONSTANDARD && PCI
282 Support for SyncLink GT and SyncLink AC families of
283 synchronous and asynchronous serial adapters
284 manufactured by Microgate Systems, Ltd. (www.microgate.com)
287 tristate "HSDPA Broadband Wireless Data Card - Globe Trotter"
290 If you have a HSDPA driver Broadband Wireless Data Card -
291 Globe Trotter PCMCIA card, say Y here.
293 To compile this driver as a module, choose M here, the module
294 will be called nozomi.
297 tristate "Multi-Tech multiport card support"
298 depends on SERIAL_NONSTANDARD && PCI
301 This is a driver for the Multi-Tech cards which provide several
302 serial ports. The driver is experimental and can currently only be
303 built as a module. The module will be called isicom.
304 If you want to do that, choose M here.
307 tristate "HDLC line discipline support"
308 depends on SERIAL_NONSTANDARD
310 Allows synchronous HDLC communications with tty device drivers that
311 support synchronous HDLC such as the Microgate SyncLink adapter.
313 This driver can be built as a module ( = code which can be
314 inserted in and removed from the running kernel whenever you want).
315 The module will be called n_hdlc. If you want to do that, say M
319 tristate "GSM MUX line discipline support (EXPERIMENTAL)"
322 This line discipline provides support for the GSM MUX protocol and
323 presents the mux as a set of 61 individual tty devices.
326 tristate "Trace data router for MIPI P1149.7 cJTAG standard"
327 depends on TRACE_SINK
330 The trace router uses the Linux tty line discipline framework to
331 route trace data coming from a tty port (say UART for example) to
332 the trace sink line discipline driver and to another tty port (say
333 USB). This is part of a solution for the MIPI P1149.7, compact JTAG,
334 standard, which is for debugging mobile devices. The PTI driver in
335 drivers/misc/pti.c defines the majority of this MIPI solution.
337 You should select this driver if the target kernel is meant for
338 a mobile device containing a modem. Then you will need to select
339 "Trace data sink for MIPI P1149.7 cJTAG standard" line discipline
343 tristate "Trace data sink for MIPI P1149.7 cJTAG standard"
346 The trace sink uses the Linux line discipline framework to receive
347 trace data coming from the trace router line discipline driver
348 to a user-defined tty port target, like USB.
349 This is to provide a way to extract modem trace data on
350 devices that do not have a PTI HW module, or just need modem
351 trace data to come out of a different HW output port.
352 This is part of a solution for the P1149.7, compact JTAG, standard.
354 If you select this option, you need to select
355 "Trace data router for MIPI P1149.7 cJTAG standard".
357 config PPC_EPAPR_HV_BYTECHAN
358 bool "ePAPR hypervisor byte channel driver"
360 select EPAPR_PARAVIRT
362 This driver creates /dev entries for each ePAPR hypervisor byte
363 channel, thereby allowing applications to communicate with byte
364 channels as if they were serial ports.
366 config PPC_EARLY_DEBUG_EHV_BC
367 bool "Early console (udbg) support for ePAPR hypervisors"
368 depends on PPC_EPAPR_HV_BYTECHAN=y
370 Select this option to enable early console (a.k.a. "udbg") support
371 via an ePAPR byte channel. You also need to choose the byte channel
374 config PPC_EARLY_DEBUG_EHV_BC_HANDLE
375 int "Byte channel handle for early console (udbg)"
376 depends on PPC_EARLY_DEBUG_EHV_BC
379 If you want early console (udbg) output through a byte channel,
380 specify the handle of the byte channel to use.
382 For this to work, the byte channel driver must be compiled
383 in-kernel, not as a module.
385 Note that only one early console driver can be enabled, so don't
386 enable any others if you enable this one.
388 If the number you specify is not a valid byte channel handle, then
389 there simply will be no early console output. This is true also
390 if you don't boot under a hypervisor at all.
393 tristate "Goldfish TTY Driver"
396 select SERIAL_CORE_CONSOLE
398 Console and system TTY driver for the Goldfish virtual platform.
400 config GOLDFISH_TTY_EARLY_CONSOLE
402 default y if GOLDFISH_TTY=y
403 select SERIAL_EARLYCON
408 select SERIAL_NONSTANDARD
410 This enables a TTY on a Dash channel.
416 This enables a console on a Dash channel.
418 config MIPS_EJTAG_FDC_TTY
419 bool "MIPS EJTAG Fast Debug Channel TTY"
422 This enables a TTY and console on the MIPS EJTAG Fast Debug Channels,
423 if they are present. This can be useful when working with an EJTAG
424 probe which supports it, to get console output and a login prompt via
425 EJTAG without needing to connect a serial cable.
427 TTY devices are named e.g. ttyFDC3c2 (for FDC channel 2 of the FDC on
430 The console can be enabled with console=fdc1 (for FDC channel 1 on all
431 CPUs). Do not use the console unless there is a debug probe attached
432 to drain the FDC TX FIFO.
436 config MIPS_EJTAG_FDC_EARLYCON
437 bool "Early FDC console"
438 depends on MIPS_EJTAG_FDC_TTY
440 This registers a console on FDC channel 1 very early during boot (from
441 MIPS arch code). This is useful for bring-up and debugging early boot
444 Do not enable unless there is a debug probe attached to drain the FDC
449 config MIPS_EJTAG_FDC_KGDB
450 bool "Use KGDB over an FDC channel"
451 depends on MIPS_EJTAG_FDC_TTY && KGDB
454 This enables the use of KGDB over an FDC channel, allowing KGDB to be
455 used remotely or when a serial port isn't available.
457 config MIPS_EJTAG_FDC_KGDB_CHAN
458 int "KGDB FDC channel"
459 depends on MIPS_EJTAG_FDC_KGDB
463 FDC channel number to use for KGDB.
466 tristate "Sun Virtual Console Concentrator"
469 Support for Sun logical domain consoles.