Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | config CCW |
2 | bool | |
3 | default y | |
4 | ||
5 | source "drivers/block/Kconfig" | |
6 | ||
7 | source "drivers/md/Kconfig" | |
8 | ||
9 | ||
10 | menu "Character device drivers" | |
11 | ||
12 | config UNIX98_PTYS | |
13 | bool "Unix98 PTY support" | |
14 | ---help--- | |
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 | |
20 | and xterms. | |
21 | ||
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. | |
30 | ||
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. | |
34 | ||
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. | |
39 | ||
40 | config UNIX98_PTY_COUNT | |
41 | int "Maximum number of Unix98 PTYs in use (0-2048)" | |
42 | depends on UNIX98_PTYS | |
43 | default "256" | |
44 | help | |
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. | |
50 | ||
51 | When not in use, each additional set of 256 PTYs occupy | |
52 | approximately 8 KB of kernel memory on 32-bit architectures. | |
53 | ||
3633b047 JG |
54 | config HANGCHECK_TIMER |
55 | tristate "Hangcheck timer" | |
56 | help | |
57 | The hangcheck-timer module detects when the system has gone | |
58 | out to lunch past a certain margin. It can reboot the system | |
59 | or merely print a warning. | |
60 | ||
1da177e4 LT |
61 | source "drivers/char/watchdog/Kconfig" |
62 | ||
63 | comment "S/390 character device drivers" | |
64 | ||
65 | config TN3270 | |
66 | tristate "Support for locally attached 3270 terminals" | |
67 | help | |
68 | Include support for IBM 3270 terminals. | |
69 | ||
70 | config TN3270_TTY | |
71 | tristate "Support for tty input/output on 3270 terminals" | |
72 | depends on TN3270 | |
73 | help | |
74 | Include support for using an IBM 3270 terminal as a Linux tty. | |
75 | ||
76 | config TN3270_FS | |
77 | tristate "Support for fullscreen applications on 3270 terminals" | |
78 | depends on TN3270 | |
79 | help | |
80 | Include support for fullscreen applications on an IBM 3270 terminal. | |
81 | ||
82 | config TN3270_CONSOLE | |
83 | bool "Support for console on 3270 terminal" | |
84 | depends on TN3270=y && TN3270_TTY=y | |
85 | help | |
86 | Include support for using an IBM 3270 terminal as a Linux system | |
87 | console. Available only if 3270 support is compiled in statically. | |
88 | ||
89 | config TN3215 | |
90 | bool "Support for 3215 line mode terminal" | |
91 | help | |
92 | Include support for IBM 3215 line-mode terminals. | |
93 | ||
94 | config TN3215_CONSOLE | |
95 | bool "Support for console on 3215 line mode terminal" | |
96 | depends on TN3215 | |
97 | help | |
98 | Include support for using an IBM 3215 line-mode terminal as a | |
99 | Linux system console. | |
100 | ||
101 | config CCW_CONSOLE | |
102 | bool | |
103 | depends on TN3215_CONSOLE || TN3270_CONSOLE | |
104 | default y | |
105 | ||
1da177e4 LT |
106 | config SCLP_TTY |
107 | bool "Support for SCLP line mode terminal" | |
1da177e4 LT |
108 | help |
109 | Include support for IBM SCLP line-mode terminals. | |
110 | ||
111 | config SCLP_CONSOLE | |
112 | bool "Support for console on SCLP line mode terminal" | |
113 | depends on SCLP_TTY | |
114 | help | |
115 | Include support for using an IBM HWC line-mode terminal as the Linux | |
116 | system console. | |
117 | ||
118 | config SCLP_VT220_TTY | |
119 | bool "Support for SCLP VT220-compatible terminal" | |
1da177e4 LT |
120 | help |
121 | Include support for an IBM SCLP VT220-compatible terminal. | |
122 | ||
123 | config SCLP_VT220_CONSOLE | |
124 | bool "Support for console on SCLP VT220-compatible terminal" | |
125 | depends on SCLP_VT220_TTY | |
126 | help | |
127 | Include support for using an IBM SCLP VT220-compatible terminal as a | |
128 | Linux system console. | |
129 | ||
130 | config SCLP_CPI | |
131 | tristate "Control-Program Identification" | |
1da177e4 LT |
132 | help |
133 | This option enables the hardware console interface for system | |
134 | identification. This is commonly used for workload management and | |
135 | gives you a nice name for the system on the service element. | |
136 | Please select this option as a module since built-in operation is | |
137 | completely untested. | |
138 | You should only select this option if you know what you are doing, | |
139 | need this feature and intend to run your kernel in LPAR. | |
140 | ||
141 | config S390_TAPE | |
142 | tristate "S/390 tape device support" | |
143 | help | |
144 | Select this option if you want to access channel-attached tape | |
145 | devices on IBM S/390 or zSeries. | |
146 | If you select this option you will also want to select at | |
147 | least one of the tape interface options and one of the tape | |
148 | hardware options in order to access a tape device. | |
149 | This option is also available as a module. The module will be | |
150 | called tape390 and include all selected interfaces and | |
151 | hardware drivers. | |
152 | ||
153 | comment "S/390 tape interface support" | |
154 | depends on S390_TAPE | |
155 | ||
156 | config S390_TAPE_BLOCK | |
157 | bool "Support for tape block devices" | |
158 | depends on S390_TAPE | |
159 | help | |
160 | Select this option if you want to access your channel-attached tape | |
161 | devices using the block device interface. This interface is similar | |
162 | to CD-ROM devices on other platforms. The tapes can only be | |
163 | accessed read-only when using this interface. Have a look at | |
164 | <file:Documentation/s390/TAPE> for further information about creating | |
165 | volumes for and using this interface. It is safe to say "Y" here. | |
166 | ||
167 | comment "S/390 tape hardware support" | |
168 | depends on S390_TAPE | |
169 | ||
170 | config S390_TAPE_34XX | |
171 | tristate "Support for 3480/3490 tape hardware" | |
172 | depends on S390_TAPE | |
173 | help | |
174 | Select this option if you want to access IBM 3480/3490 magnetic | |
175 | tape subsystems and 100% compatibles. | |
176 | It is safe to say "Y" here. | |
177 | ||
b6cba4ee SB |
178 | config S390_TAPE_3590 |
179 | tristate "Support for 3590 tape hardware" | |
180 | depends on S390_TAPE | |
181 | help | |
182 | Select this option if you want to access IBM 3590 magnetic | |
183 | tape subsystems and 100% compatibles. | |
184 | It is safe to say "Y" here. | |
1da177e4 LT |
185 | |
186 | config VMLOGRDR | |
187 | tristate "Support for the z/VM recording system services (VM only)" | |
188 | depends on IUCV | |
189 | help | |
190 | Select this option if you want to be able to receive records collected | |
191 | by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or | |
192 | *SYMPTOM. | |
193 | This driver depends on the IUCV support driver. | |
194 | ||
6b979de3 CB |
195 | config VMCP |
196 | tristate "Support for the z/VM CP interface (VM only)" | |
197 | help | |
198 | Select this option if you want to be able to interact with the control | |
199 | program on z/VM | |
200 | ||
201 | ||
1da177e4 LT |
202 | config MONREADER |
203 | tristate "API for reading z/VM monitor service records" | |
204 | depends on IUCV | |
205 | help | |
206 | Character device driver for reading z/VM monitor service records | |
207 | ||
31b58088 MH |
208 | config MONWRITER |
209 | tristate "API for writing z/VM monitor service records" | |
210 | default "m" | |
211 | help | |
212 | Character device driver for writing z/VM monitor service records | |
213 | ||
1da177e4 LT |
214 | endmenu |
215 | ||
216 | menu "Cryptographic devices" | |
217 | ||
fe3a1be5 MS |
218 | config ZCRYPT |
219 | tristate "Support for PCI-attached cryptographic adapters" | |
220 | select ZCRYPT_MONOLITHIC if ZCRYPT="y" | |
221 | default "m" | |
222 | help | |
223 | Select this option if you want to use a PCI-attached cryptographic | |
224 | adapter like: | |
225 | + PCI Cryptographic Accelerator (PCICA) | |
226 | + PCI Cryptographic Coprocessor (PCICC) | |
227 | + PCI-X Cryptographic Coprocessor (PCIXCC) | |
228 | + Crypto Express2 Coprocessor (CEX2C) | |
229 | + Crypto Express2 Accelerator (CEX2A) | |
230 | ||
231 | config ZCRYPT_MONOLITHIC | |
232 | bool "Monolithic zcrypt module" | |
233 | depends on ZCRYPT="m" | |
234 | help | |
235 | Select this option if you want to have a single module z90crypt.ko | |
236 | that contains all parts of the crypto device driver (ap bus, | |
237 | request router and all the card drivers). | |
238 | ||
1da177e4 | 239 | endmenu |