1 comment "S/390 character device drivers"
5 tristate "Support for locally attached 3270 terminals"
8 Include support for IBM 3270 terminals.
11 tristate "Support for tty input/output on 3270 terminals"
14 Include support for using an IBM 3270 terminal as a Linux tty.
17 tristate "Support for fullscreen applications on 3270 terminals"
20 Include support for fullscreen applications on an IBM 3270 terminal.
23 bool "Support for console on 3270 terminal"
24 depends on TN3270=y && TN3270_TTY=y
26 Include support for using an IBM 3270 terminal as a Linux system
27 console. Available only if 3270 support is compiled in statically.
30 bool "Support for 3215 line mode terminal"
33 Include support for IBM 3215 line-mode terminals.
36 bool "Support for console on 3215 line mode terminal"
39 Include support for using an IBM 3215 line-mode terminal as a
44 depends on TN3215_CONSOLE || TN3270_CONSOLE
48 bool "Support for SCLP line mode terminal"
51 Include support for IBM SCLP line-mode terminals.
54 bool "Support for console on SCLP line mode terminal"
57 Include support for using an IBM HWC line-mode terminal as the Linux
61 bool "Support for SCLP VT220-compatible terminal"
64 Include support for an IBM SCLP VT220-compatible terminal.
66 config SCLP_VT220_CONSOLE
67 bool "Support for console on SCLP VT220-compatible terminal"
68 depends on SCLP_VT220_TTY
70 Include support for using an IBM SCLP VT220-compatible terminal as a
74 tristate "Control-Program Identification"
77 This option enables the hardware console interface for system
78 identification. This is commonly used for workload management and
79 gives you a nice name for the system on the service element.
80 Please select this option as a module since built-in operation is
82 You should only select this option if you know what you are doing,
83 need this feature and intend to run your kernel in LPAR.
86 tristate "Support for Call Home via Asynchronous SCLP Records"
89 This option enables the call home function, which is able to inform
90 the service element and connected organisations about a kernel panic.
91 You should only select this option if you know what you are doing,
92 want for inform other people about your kernel panics,
93 need this feature and intend to run your kernel in LPAR.
96 tristate "S/390 tape device support"
99 Select this option if you want to access channel-attached tape
100 devices on IBM S/390 or zSeries.
101 If you select this option you will also want to select at
102 least one of the tape interface options and one of the tape
103 hardware options in order to access a tape device.
104 This option is also available as a module. The module will be
105 called tape390 and include all selected interfaces and
108 comment "S/390 tape interface support"
111 config S390_TAPE_BLOCK
112 bool "Support for tape block devices"
113 depends on S390_TAPE && BLOCK
115 Select this option if you want to access your channel-attached tape
116 devices using the block device interface. This interface is similar
117 to CD-ROM devices on other platforms. The tapes can only be
118 accessed read-only when using this interface. Have a look at
119 <file:Documentation/s390/TAPE> for further information about creating
120 volumes for and using this interface. It is safe to say "Y" here.
122 comment "S/390 tape hardware support"
125 config S390_TAPE_34XX
126 tristate "Support for 3480/3490 tape hardware"
129 Select this option if you want to access IBM 3480/3490 magnetic
130 tape subsystems and 100% compatibles.
131 It is safe to say "Y" here.
133 config S390_TAPE_3590
134 tristate "Support for 3590 tape hardware"
137 Select this option if you want to access IBM 3590 magnetic
138 tape subsystems and 100% compatibles.
139 It is safe to say "Y" here.
142 tristate "Support for the z/VM recording system services (VM only)"
145 Select this option if you want to be able to receive records collected
146 by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
148 This driver depends on the IUCV support driver.
151 bool "Support for the z/VM CP interface"
154 Select this option if you want to be able to interact with the control
158 tristate "API for reading z/VM monitor service records"
161 Character device driver for reading z/VM monitor service records
164 tristate "API for writing z/VM monitor service records"
168 Character device driver for writing z/VM monitor service records
171 tristate "z/VM unit record device driver"
175 Character device driver for z/VM reader, puncher and printer.