5 source "drivers/block/Kconfig"
7 source "drivers/md/Kconfig"
10 menu "Character device drivers"
13 bool "Unix98 PTY support"
15 A pseudo terminal (PTY) is a software device consisting of two
16 halves: a master and a slave. The slave device behaves identical to
17 a physical terminal; the master device is used by a process to
18 read data from and write data to the slave, thereby emulating a
19 terminal. Typical programs for the master side are telnet servers
22 Linux has traditionally used the BSD-like names /dev/ptyxx for
23 masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
24 has a number of problems. The GNU C library glibc 2.1 and later,
25 however, supports the Unix98 naming standard: in order to acquire a
26 pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
27 terminal is then made available to the process and the pseudo
28 terminal slave can be accessed as /dev/pts/<number>. What was
29 traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
31 The entries in /dev/pts/ are created on the fly by a virtual
32 file system; therefore, if you say Y here you should say Y to
33 "/dev/pts file system for Unix98 PTYs" as well.
35 If you want to say Y here, you need to have the C library glibc 2.1
36 or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
37 Read the instructions in <file:Documentation/Changes> pertaining to
38 pseudo terminals. It's safe to say N.
40 config UNIX98_PTY_COUNT
41 int "Maximum number of Unix98 PTYs in use (0-2048)"
42 depends on UNIX98_PTYS
45 The maximum number of Unix98 PTYs that can be used at any one time.
46 The default is 256, and should be enough for desktop systems. Server
47 machines which support incoming telnet/rlogin/ssh connections and/or
48 serve several X terminals may want to increase this: every incoming
49 connection and every xterm uses up one PTY.
51 When not in use, each additional set of 256 PTYs occupy
52 approximately 8 KB of kernel memory on 32-bit architectures.
54 source "drivers/char/watchdog/Kconfig"
56 comment "S/390 character device drivers"
59 tristate "Support for locally attached 3270 terminals"
61 Include support for IBM 3270 terminals.
64 tristate "Support for tty input/output on 3270 terminals"
67 Include support for using an IBM 3270 terminal as a Linux tty.
70 tristate "Support for fullscreen applications on 3270 terminals"
73 Include support for fullscreen applications on an IBM 3270 terminal.
76 bool "Support for console on 3270 terminal"
77 depends on TN3270=y && TN3270_TTY=y
79 Include support for using an IBM 3270 terminal as a Linux system
80 console. Available only if 3270 support is compiled in statically.
83 bool "Support for 3215 line mode terminal"
85 Include support for IBM 3215 line-mode terminals.
88 bool "Support for console on 3215 line mode terminal"
91 Include support for using an IBM 3215 line-mode terminal as a
96 depends on TN3215_CONSOLE || TN3270_CONSOLE
100 bool "Support for SCLP"
102 Include support for the SCLP interface to the service element.
105 bool "Support for SCLP line mode terminal"
108 Include support for IBM SCLP line-mode terminals.
111 bool "Support for console on SCLP line mode terminal"
114 Include support for using an IBM HWC line-mode terminal as the Linux
117 config SCLP_VT220_TTY
118 bool "Support for SCLP VT220-compatible terminal"
121 Include support for an IBM SCLP VT220-compatible terminal.
123 config SCLP_VT220_CONSOLE
124 bool "Support for console on SCLP VT220-compatible terminal"
125 depends on SCLP_VT220_TTY
127 Include support for using an IBM SCLP VT220-compatible terminal as a
128 Linux system console.
131 tristate "Control-Program Identification"
134 This option enables the hardware console interface for system
135 identification. This is commonly used for workload management and
136 gives you a nice name for the system on the service element.
137 Please select this option as a module since built-in operation is
139 You should only select this option if you know what you are doing,
140 need this feature and intend to run your kernel in LPAR.
143 tristate "S/390 tape device support"
145 Select this option if you want to access channel-attached tape
146 devices on IBM S/390 or zSeries.
147 If you select this option you will also want to select at
148 least one of the tape interface options and one of the tape
149 hardware options in order to access a tape device.
150 This option is also available as a module. The module will be
151 called tape390 and include all selected interfaces and
154 comment "S/390 tape interface support"
157 config S390_TAPE_BLOCK
158 bool "Support for tape block devices"
161 Select this option if you want to access your channel-attached tape
162 devices using the block device interface. This interface is similar
163 to CD-ROM devices on other platforms. The tapes can only be
164 accessed read-only when using this interface. Have a look at
165 <file:Documentation/s390/TAPE> for further information about creating
166 volumes for and using this interface. It is safe to say "Y" here.
168 comment "S/390 tape hardware support"
171 config S390_TAPE_34XX
172 tristate "Support for 3480/3490 tape hardware"
175 Select this option if you want to access IBM 3480/3490 magnetic
176 tape subsystems and 100% compatibles.
177 It is safe to say "Y" here.
182 tristate "Support for the z/VM recording system services (VM only)"
185 Select this option if you want to be able to receive records collected
186 by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
188 This driver depends on the IUCV support driver.
191 tristate "Support for the z/VM CP interface (VM only)"
193 Select this option if you want to be able to interact with the control
198 tristate "API for reading z/VM monitor service records"
201 Character device driver for reading z/VM monitor service records
205 menu "Cryptographic devices"
208 tristate "Support for PCI-attached cryptographic adapters"
211 Select this option if you want to use a PCI-attached cryptographic
212 adapter like the PCI Cryptographic Accelerator (PCICA) or the PCI
213 Cryptographic Coprocessor (PCICC). This option is also available
214 as a module called z90crypt.ko.