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 comment "S/390 character device drivers"
57 tristate "Support for locally attached 3270 tubes"
59 Include support for IBM 3270 line-mode terminals.
62 bool "Support for console on 3270 line mode terminal"
65 Include support for using an IBM 3270 line-mode terminal as a Linux
66 system console. Available only if 3270 support is compiled in
70 bool "Support for 3215 line mode terminal"
72 Include support for IBM 3215 line-mode terminals.
75 bool "Support for console on 3215 line mode terminal"
78 Include support for using an IBM 3215 line-mode terminal as a
83 depends on TN3215_CONSOLE || TN3270_CONSOLE
87 bool "Support for SCLP"
89 Include support for the SCLP interface to the service element.
92 bool "Support for SCLP line mode terminal"
95 Include support for IBM SCLP line-mode terminals.
98 bool "Support for console on SCLP line mode terminal"
101 Include support for using an IBM HWC line-mode terminal as the Linux
104 config SCLP_VT220_TTY
105 bool "Support for SCLP VT220-compatible terminal"
108 Include support for an IBM SCLP VT220-compatible terminal.
110 config SCLP_VT220_CONSOLE
111 bool "Support for console on SCLP VT220-compatible terminal"
112 depends on SCLP_VT220_TTY
114 Include support for using an IBM SCLP VT220-compatible terminal as a
115 Linux system console.
118 tristate "Control-Program Identification"
121 This option enables the hardware console interface for system
122 identification. This is commonly used for workload management and
123 gives you a nice name for the system on the service element.
124 Please select this option as a module since built-in operation is
126 You should only select this option if you know what you are doing,
127 need this feature and intend to run your kernel in LPAR.
130 tristate "S/390 tape device support"
132 Select this option if you want to access channel-attached tape
133 devices on IBM S/390 or zSeries.
134 If you select this option you will also want to select at
135 least one of the tape interface options and one of the tape
136 hardware options in order to access a tape device.
137 This option is also available as a module. The module will be
138 called tape390 and include all selected interfaces and
141 comment "S/390 tape interface support"
144 config S390_TAPE_BLOCK
145 bool "Support for tape block devices"
148 Select this option if you want to access your channel-attached tape
149 devices using the block device interface. This interface is similar
150 to CD-ROM devices on other platforms. The tapes can only be
151 accessed read-only when using this interface. Have a look at
152 Documentation/s390/TAPE for further information about creating
153 volumes for and using this interface. It is safe to say "Y" here.
155 comment "S/390 tape hardware support"
158 config S390_TAPE_34XX
159 tristate "Support for 3480/3490 tape hardware"
162 Select this option if you want to access IBM 3480/3490 magnetic
163 tape subsystems and 100% compatibles.
164 It is safe to say "Y" here.
168 menu "Cryptographic devices"
171 tristate "Support for PCI-attached cryptographic adapters"
174 Select this option if you want to use a PCI-attached cryptographic
175 adapter like the PCI Cryptographic Accelerator (PCICA) or the PCI
176 Cryptographic Coprocessor (PCICC). This option is also available
177 as a module called z90crypt.ko.