Andrew Scull | b4b6d4a | 2019-01-02 15:54:55 +0000 | [diff] [blame^] | 1 | # SPDX-License-Identifier: GPL-2.0 |
| 2 | comment "S/390 character device drivers" |
| 3 | depends on S390 |
| 4 | |
| 5 | config TN3270 |
| 6 | def_tristate y |
| 7 | prompt "Support for locally attached 3270 terminals" |
| 8 | depends on CCW |
| 9 | help |
| 10 | Include support for IBM 3270 terminals. |
| 11 | |
| 12 | config TN3270_TTY |
| 13 | def_tristate y |
| 14 | prompt "Support for tty input/output on 3270 terminals" |
| 15 | depends on TN3270 && TTY |
| 16 | help |
| 17 | Include support for using an IBM 3270 terminal as a Linux tty. |
| 18 | |
| 19 | config TN3270_FS |
| 20 | def_tristate m |
| 21 | prompt "Support for fullscreen applications on 3270 terminals" |
| 22 | depends on TN3270 |
| 23 | help |
| 24 | Include support for fullscreen applications on an IBM 3270 terminal. |
| 25 | |
| 26 | config TN3270_CONSOLE |
| 27 | def_bool y |
| 28 | prompt "Support for console on 3270 terminal" |
| 29 | depends on TN3270=y && TN3270_TTY=y |
| 30 | help |
| 31 | Include support for using an IBM 3270 terminal as a Linux system |
| 32 | console. Available only if 3270 support is compiled in statically. |
| 33 | |
| 34 | config TN3215 |
| 35 | def_bool y |
| 36 | prompt "Support for 3215 line mode terminal" |
| 37 | depends on CCW && TTY |
| 38 | help |
| 39 | Include support for IBM 3215 line-mode terminals. |
| 40 | |
| 41 | config TN3215_CONSOLE |
| 42 | def_bool y |
| 43 | prompt "Support for console on 3215 line mode terminal" |
| 44 | depends on TN3215 |
| 45 | help |
| 46 | Include support for using an IBM 3215 line-mode terminal as a |
| 47 | Linux system console. |
| 48 | |
| 49 | config CCW_CONSOLE |
| 50 | def_bool y if TN3215_CONSOLE || TN3270_CONSOLE |
| 51 | |
| 52 | config SCLP_TTY |
| 53 | def_bool y |
| 54 | prompt "Support for SCLP line mode terminal" |
| 55 | depends on S390 && TTY |
| 56 | help |
| 57 | Include support for IBM SCLP line-mode terminals. |
| 58 | |
| 59 | config SCLP_CONSOLE |
| 60 | def_bool y |
| 61 | prompt "Support for console on SCLP line mode terminal" |
| 62 | depends on SCLP_TTY |
| 63 | help |
| 64 | Include support for using an IBM HWC line-mode terminal as the Linux |
| 65 | system console. |
| 66 | |
| 67 | config SCLP_VT220_TTY |
| 68 | def_bool y |
| 69 | prompt "Support for SCLP VT220-compatible terminal" |
| 70 | depends on S390 && TTY |
| 71 | help |
| 72 | Include support for an IBM SCLP VT220-compatible terminal. |
| 73 | |
| 74 | config SCLP_VT220_CONSOLE |
| 75 | def_bool y |
| 76 | prompt "Support for console on SCLP VT220-compatible terminal" |
| 77 | depends on SCLP_VT220_TTY |
| 78 | help |
| 79 | Include support for using an IBM SCLP VT220-compatible terminal as a |
| 80 | Linux system console. |
| 81 | |
| 82 | config SCLP_ASYNC |
| 83 | def_tristate m |
| 84 | prompt "Support for Call Home via Asynchronous SCLP Records" |
| 85 | depends on S390 |
| 86 | help |
| 87 | This option enables the call home function, which is able to inform |
| 88 | the service element and connected organisations about a kernel panic. |
| 89 | You should only select this option if you know what you are doing, |
| 90 | want for inform other people about your kernel panics, |
| 91 | need this feature and intend to run your kernel in LPAR. |
| 92 | |
| 93 | config SCLP_ASYNC_ID |
| 94 | string "Component ID for Call Home" |
| 95 | depends on SCLP_ASYNC |
| 96 | default "000000000" |
| 97 | help |
| 98 | The Component ID for Call Home is used to identify the correct |
| 99 | problem reporting queue the call home records should be sent to. |
| 100 | |
| 101 | If your are unsure, please use the default value "000000000". |
| 102 | |
| 103 | config HMC_DRV |
| 104 | def_tristate m |
| 105 | prompt "Support for file transfers from HMC drive CD/DVD-ROM" |
| 106 | depends on S390 |
| 107 | select CRC16 |
| 108 | help |
| 109 | This option enables support for file transfers from a Hardware |
| 110 | Management Console (HMC) drive CD/DVD-ROM. It is available as a |
| 111 | module, called 'hmcdrv', and also as kernel built-in. There is one |
| 112 | optional parameter for this module: cachesize=N, which modifies the |
| 113 | transfer cache size from it's default value 0.5MB to N bytes. If N |
| 114 | is zero, then no caching is performed. |
| 115 | |
| 116 | config SCLP_OFB |
| 117 | def_bool n |
| 118 | prompt "Support for Open-for-Business SCLP Event" |
| 119 | depends on S390 |
| 120 | help |
| 121 | This option enables the Open-for-Business interface to the s390 |
| 122 | Service Element. |
| 123 | |
| 124 | config S390_TAPE |
| 125 | def_tristate m |
| 126 | prompt "S/390 tape device support" |
| 127 | depends on CCW |
| 128 | help |
| 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 |
| 136 | hardware drivers. |
| 137 | |
| 138 | comment "S/390 tape hardware support" |
| 139 | depends on S390_TAPE |
| 140 | |
| 141 | config S390_TAPE_34XX |
| 142 | def_tristate m |
| 143 | prompt "Support for 3480/3490 tape hardware" |
| 144 | depends on S390_TAPE |
| 145 | help |
| 146 | Select this option if you want to access IBM 3480/3490 magnetic |
| 147 | tape subsystems and 100% compatibles. |
| 148 | It is safe to say "Y" here. |
| 149 | |
| 150 | config S390_TAPE_3590 |
| 151 | def_tristate m |
| 152 | prompt "Support for 3590 tape hardware" |
| 153 | depends on S390_TAPE |
| 154 | help |
| 155 | Select this option if you want to access IBM 3590 magnetic |
| 156 | tape subsystems and 100% compatibles. |
| 157 | It is safe to say "Y" here. |
| 158 | |
| 159 | config VMLOGRDR |
| 160 | def_tristate m |
| 161 | prompt "Support for the z/VM recording system services (VM only)" |
| 162 | depends on IUCV |
| 163 | help |
| 164 | Select this option if you want to be able to receive records collected |
| 165 | by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or |
| 166 | *SYMPTOM. |
| 167 | This driver depends on the IUCV support driver. |
| 168 | |
| 169 | config VMCP |
| 170 | def_bool y |
| 171 | prompt "Support for the z/VM CP interface" |
| 172 | depends on S390 |
| 173 | select CMA |
| 174 | help |
| 175 | Select this option if you want to be able to interact with the control |
| 176 | program on z/VM |
| 177 | |
| 178 | config VMCP_CMA_SIZE |
| 179 | int "Memory in MiB reserved for z/VM CP interface" |
| 180 | default "4" |
| 181 | depends on VMCP |
| 182 | help |
| 183 | Specify the default amount of memory in MiB reserved for the z/VM CP |
| 184 | interface. If needed this memory is used for large contiguous memory |
| 185 | allocations. The default can be changed with the kernel command line |
| 186 | parameter "vmcp_cma". |
| 187 | |
| 188 | config MONREADER |
| 189 | def_tristate m |
| 190 | prompt "API for reading z/VM monitor service records" |
| 191 | depends on IUCV |
| 192 | help |
| 193 | Character device driver for reading z/VM monitor service records |
| 194 | |
| 195 | config MONWRITER |
| 196 | def_tristate m |
| 197 | prompt "API for writing z/VM monitor service records" |
| 198 | depends on S390 |
| 199 | help |
| 200 | Character device driver for writing z/VM monitor service records |
| 201 | |
| 202 | config S390_VMUR |
| 203 | def_tristate m |
| 204 | prompt "z/VM unit record device driver" |
| 205 | depends on S390 |
| 206 | help |
| 207 | Character device driver for z/VM reader, puncher and printer. |
| 208 | |