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 comment "S/390 character device drivers"
43 tristate "Support for locally attached 3270 terminals"
45 Include support for IBM 3270 terminals.
48 tristate "Support for tty input/output on 3270 terminals"
51 Include support for using an IBM 3270 terminal as a Linux tty.
54 tristate "Support for fullscreen applications on 3270 terminals"
57 Include support for fullscreen applications on an IBM 3270 terminal.
60 bool "Support for console on 3270 terminal"
61 depends on TN3270=y && TN3270_TTY=y
63 Include support for using an IBM 3270 terminal as a Linux system
64 console. Available only if 3270 support is compiled in statically.
67 bool "Support for 3215 line mode terminal"
69 Include support for IBM 3215 line-mode terminals.
72 bool "Support for console on 3215 line mode terminal"
75 Include support for using an IBM 3215 line-mode terminal as a
80 depends on TN3215_CONSOLE || TN3270_CONSOLE
84 bool "Support for SCLP"
86 Include support for the SCLP interface to the service element.
89 bool "Support for SCLP line mode terminal"
92 Include support for IBM SCLP line-mode terminals.
95 bool "Support for console on SCLP line mode terminal"
98 Include support for using an IBM HWC line-mode terminal as the Linux
101 config SCLP_VT220_TTY
102 bool "Support for SCLP VT220-compatible terminal"
105 Include support for an IBM SCLP VT220-compatible terminal.
107 config SCLP_VT220_CONSOLE
108 bool "Support for console on SCLP VT220-compatible terminal"
109 depends on SCLP_VT220_TTY
111 Include support for using an IBM SCLP VT220-compatible terminal as a
112 Linux system console.
115 tristate "Control-Program Identification"
118 This option enables the hardware console interface for system
119 identification. This is commonly used for workload management and
120 gives you a nice name for the system on the service element.
121 Please select this option as a module since built-in operation is
123 You should only select this option if you know what you are doing,
124 need this feature and intend to run your kernel in LPAR.
127 tristate "S/390 tape device support"
129 Select this option if you want to access channel-attached tape
130 devices on IBM S/390 or zSeries.
131 If you select this option you will also want to select at
132 least one of the tape interface options and one of the tape
133 hardware options in order to access a tape device.
134 This option is also available as a module. The module will be
135 called tape390 and include all selected interfaces and
138 comment "S/390 tape interface support"
141 config S390_TAPE_BLOCK
142 bool "Support for tape block devices"
145 Select this option if you want to access your channel-attached tape
146 devices using the block device interface. This interface is similar
147 to CD-ROM devices on other platforms. The tapes can only be
148 accessed read-only when using this interface. Have a look at
149 Documentation/s390/TAPE for further information about creating
150 volumes for and using this interface. It is safe to say "Y" here.
152 comment "S/390 tape hardware support"
155 config S390_TAPE_34XX
156 tristate "Support for 3480/3490 tape hardware"
159 Select this option if you want to access IBM 3480/3490 magnetic
160 tape subsystems and 100% compatibles.
161 It is safe to say "Y" here.
165 menu "Cryptographic devices"
168 tristate "Support for PCI-attached cryptographic adapters"
171 Select this option if you want to use a PCI-attached cryptographic
172 adapter like the PCI Cryptographic Accelerator (PCICA) or the PCI
173 Cryptographic Coprocessor (PCICC). This option is also available
174 as a module called z90crypt.ko.