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 "S/390 tape device support"
89 Select this option if you want to access channel-attached tape
90 devices on IBM S/390 or zSeries.
91 If you select this option you will also want to select at
92 least one of the tape interface options and one of the tape
93 hardware options in order to access a tape device.
94 This option is also available as a module. The module will be
95 called tape390 and include all selected interfaces and
98 comment "S/390 tape interface support"
101 config S390_TAPE_BLOCK
102 bool "Support for tape block devices"
105 Select this option if you want to access your channel-attached tape
106 devices using the block device interface. This interface is similar
107 to CD-ROM devices on other platforms. The tapes can only be
108 accessed read-only when using this interface. Have a look at
109 <file:Documentation/s390/TAPE> for further information about creating
110 volumes for and using this interface. It is safe to say "Y" here.
112 comment "S/390 tape hardware support"
115 config S390_TAPE_34XX
116 tristate "Support for 3480/3490 tape hardware"
119 Select this option if you want to access IBM 3480/3490 magnetic
120 tape subsystems and 100% compatibles.
121 It is safe to say "Y" here.
123 config S390_TAPE_3590
124 tristate "Support for 3590 tape hardware"
127 Select this option if you want to access IBM 3590 magnetic
128 tape subsystems and 100% compatibles.
129 It is safe to say "Y" here.
132 tristate "Support for the z/VM recording system services (VM only)"
135 Select this option if you want to be able to receive records collected
136 by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
138 This driver depends on the IUCV support driver.
141 tristate "Support for the z/VM CP interface (VM only)"
144 Select this option if you want to be able to interact with the control
149 tristate "API for reading z/VM monitor service records"
152 Character device driver for reading z/VM monitor service records
155 tristate "API for writing z/VM monitor service records"
159 Character device driver for writing z/VM monitor service records
162 tristate "z/VM unit record device driver"
166 Character device driver for z/VM reader, puncher and printer.