blob: ae89b9b88743462538ba6069b268a13642530045 [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001config CCW
2 bool
3 default y
4
5source "drivers/block/Kconfig"
6
7source "drivers/md/Kconfig"
8
9
10menu "Character device drivers"
11
12config 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
40config 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
Jan Glauber3633b042006-02-01 03:06:34 -080054config 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
Linus Torvalds1da177e2005-04-16 15:20:36 -070061source "drivers/char/watchdog/Kconfig"
62
63comment "S/390 character device drivers"
64
65config TN3270
66 tristate "Support for locally attached 3270 terminals"
67 help
68 Include support for IBM 3270 terminals.
69
70config 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
76config 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
82config 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
89config TN3215
90 bool "Support for 3215 line mode terminal"
91 help
92 Include support for IBM 3215 line-mode terminals.
93
94config 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
101config CCW_CONSOLE
102 bool
103 depends on TN3215_CONSOLE || TN3270_CONSOLE
104 default y
105
106config SCLP
107 bool "Support for SCLP"
108 help
109 Include support for the SCLP interface to the service element.
110
111config SCLP_TTY
112 bool "Support for SCLP line mode terminal"
113 depends on SCLP
114 help
115 Include support for IBM SCLP line-mode terminals.
116
117config SCLP_CONSOLE
118 bool "Support for console on SCLP line mode terminal"
119 depends on SCLP_TTY
120 help
121 Include support for using an IBM HWC line-mode terminal as the Linux
122 system console.
123
124config SCLP_VT220_TTY
125 bool "Support for SCLP VT220-compatible terminal"
126 depends on SCLP
127 help
128 Include support for an IBM SCLP VT220-compatible terminal.
129
130config SCLP_VT220_CONSOLE
131 bool "Support for console on SCLP VT220-compatible terminal"
132 depends on SCLP_VT220_TTY
133 help
134 Include support for using an IBM SCLP VT220-compatible terminal as a
135 Linux system console.
136
137config SCLP_CPI
138 tristate "Control-Program Identification"
139 depends on SCLP
140 help
141 This option enables the hardware console interface for system
142 identification. This is commonly used for workload management and
143 gives you a nice name for the system on the service element.
144 Please select this option as a module since built-in operation is
145 completely untested.
146 You should only select this option if you know what you are doing,
147 need this feature and intend to run your kernel in LPAR.
148
149config S390_TAPE
150 tristate "S/390 tape device support"
151 help
152 Select this option if you want to access channel-attached tape
153 devices on IBM S/390 or zSeries.
154 If you select this option you will also want to select at
155 least one of the tape interface options and one of the tape
156 hardware options in order to access a tape device.
157 This option is also available as a module. The module will be
158 called tape390 and include all selected interfaces and
159 hardware drivers.
160
161comment "S/390 tape interface support"
162 depends on S390_TAPE
163
164config S390_TAPE_BLOCK
165 bool "Support for tape block devices"
166 depends on S390_TAPE
167 help
168 Select this option if you want to access your channel-attached tape
169 devices using the block device interface. This interface is similar
170 to CD-ROM devices on other platforms. The tapes can only be
171 accessed read-only when using this interface. Have a look at
172 <file:Documentation/s390/TAPE> for further information about creating
173 volumes for and using this interface. It is safe to say "Y" here.
174
175comment "S/390 tape hardware support"
176 depends on S390_TAPE
177
178config S390_TAPE_34XX
179 tristate "Support for 3480/3490 tape hardware"
180 depends on S390_TAPE
181 help
182 Select this option if you want to access IBM 3480/3490 magnetic
183 tape subsystems and 100% compatibles.
184 It is safe to say "Y" here.
185
Stefan Baderb6cba4e2006-03-24 03:15:29 -0800186config S390_TAPE_3590
187 tristate "Support for 3590 tape hardware"
188 depends on S390_TAPE
189 help
190 Select this option if you want to access IBM 3590 magnetic
191 tape subsystems and 100% compatibles.
192 It is safe to say "Y" here.
Linus Torvalds1da177e2005-04-16 15:20:36 -0700193
194config VMLOGRDR
195 tristate "Support for the z/VM recording system services (VM only)"
196 depends on IUCV
197 help
198 Select this option if you want to be able to receive records collected
199 by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
200 *SYMPTOM.
201 This driver depends on the IUCV support driver.
202
Christian Borntraeger6b979de2005-06-25 14:55:32 -0700203config VMCP
204 tristate "Support for the z/VM CP interface (VM only)"
205 help
206 Select this option if you want to be able to interact with the control
207 program on z/VM
208
209
Linus Torvalds1da177e2005-04-16 15:20:36 -0700210config MONREADER
211 tristate "API for reading z/VM monitor service records"
212 depends on IUCV
213 help
214 Character device driver for reading z/VM monitor service records
215
Melissa Howland31b58082006-09-20 15:59:34 +0200216config MONWRITER
217 tristate "API for writing z/VM monitor service records"
218 default "m"
219 help
220 Character device driver for writing z/VM monitor service records
221
Linus Torvalds1da177e2005-04-16 15:20:36 -0700222endmenu
223
224menu "Cryptographic devices"
225
Martin Schwidefskyfe3a1be2006-09-20 15:58:34 +0200226config ZCRYPT
227 tristate "Support for PCI-attached cryptographic adapters"
228 select ZCRYPT_MONOLITHIC if ZCRYPT="y"
229 default "m"
230 help
231 Select this option if you want to use a PCI-attached cryptographic
232 adapter like:
233 + PCI Cryptographic Accelerator (PCICA)
234 + PCI Cryptographic Coprocessor (PCICC)
235 + PCI-X Cryptographic Coprocessor (PCIXCC)
236 + Crypto Express2 Coprocessor (CEX2C)
237 + Crypto Express2 Accelerator (CEX2A)
238
239config ZCRYPT_MONOLITHIC
240 bool "Monolithic zcrypt module"
241 depends on ZCRYPT="m"
242 help
243 Select this option if you want to have a single module z90crypt.ko
244 that contains all parts of the crypto device driver (ap bus,
245 request router and all the card drivers).
246
Linus Torvalds1da177e2005-04-16 15:20:36 -0700247endmenu