drivers/s390/Kconfig

   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
  54 source "drivers/char/watchdog/Kconfig"
  55
  56 comment "S/390 character device drivers"
  57
  58 config TN3270
  59         tristate "Support for locally attached 3270 terminals"
  60         help
  61           Include support for IBM 3270 terminals.
  62
  63 config TN3270_TTY
  64         tristate "Support for tty input/output on 3270 terminals"
  65         depends on TN3270
  66         help
  67           Include support for using an IBM 3270 terminal as a Linux tty.
  68
  69 config TN3270_FS
  70         tristate "Support for fullscreen applications on 3270 terminals"
  71         depends on TN3270
  72         help
  73           Include support for fullscreen applications on an IBM 3270 terminal.
  74
  75 config TN3270_CONSOLE
  76         bool "Support for console on 3270 terminal"
  77         depends on TN3270=y && TN3270_TTY=y
  78         help
  79           Include support for using an IBM 3270 terminal as a Linux system
  80           console.  Available only if 3270 support is compiled in statically.
  81
  82 config TN3215
  83         bool "Support for 3215 line mode terminal"
  84         help
  85           Include support for IBM 3215 line-mode terminals.
  86
  87 config TN3215_CONSOLE
  88         bool "Support for console on 3215 line mode terminal"
  89         depends on TN3215
  90         help
  91           Include support for using an IBM 3215 line-mode terminal as a
  92           Linux system console.
  93
  94 config CCW_CONSOLE
  95         bool
  96         depends on TN3215_CONSOLE || TN3270_CONSOLE
  97         default y
  98
  99 config SCLP
 100         bool "Support for SCLP"
 101         help
 102           Include support for the SCLP interface to the service element.
 103
 104 config SCLP_TTY
 105         bool "Support for SCLP line mode terminal"
 106         depends on SCLP
 107         help
 108           Include support for IBM SCLP line-mode terminals.
 109
 110 config SCLP_CONSOLE
 111         bool "Support for console on SCLP line mode terminal"
 112         depends on SCLP_TTY
 113         help
 114           Include support for using an IBM HWC line-mode terminal as the Linux
 115           system console.
 116
 117 config SCLP_VT220_TTY
 118         bool "Support for SCLP VT220-compatible terminal"
 119         depends on SCLP
 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"
 132         depends on SCLP
 133         help
 134           This option enables the hardware console interface for system
 135           identification. This is commonly used for workload management and
 136           gives you a nice name for the system on the service element.
 137           Please select this option as a module since built-in operation is
 138           completely untested.
 139           You should only select this option if you know what you are doing,
 140           need this feature and intend to run your kernel in LPAR.
 141
 142 config S390_TAPE
 143         tristate "S/390 tape device support"
 144         help
 145           Select this option if you want to access channel-attached tape
 146           devices on IBM S/390 or zSeries.
 147           If you select this option you will also want to select at
 148           least one of the tape interface options and one of the tape
 149           hardware options in order to access a tape device.
 150           This option is also available as a module. The module will be
 151           called tape390 and include all selected interfaces and
 152           hardware drivers.
 153
 154 comment "S/390 tape interface support"
 155         depends on S390_TAPE
 156
 157 config S390_TAPE_BLOCK
 158         bool "Support for tape block devices"
 159         depends on S390_TAPE
 160         help
 161           Select this option if you want to access your channel-attached tape
 162           devices using the block device interface.  This interface is similar
 163           to CD-ROM devices on other platforms.  The tapes can only be
 164           accessed read-only when using this interface.  Have a look at
 165           <file:Documentation/s390/TAPE> for further information about creating
 166           volumes for and using this interface.  It is safe to say "Y" here.
 167
 168 comment "S/390 tape hardware support"
 169         depends on S390_TAPE
 170
 171 config S390_TAPE_34XX
 172         tristate "Support for 3480/3490 tape hardware"
 173         depends on S390_TAPE
 174         help
 175           Select this option if you want to access IBM 3480/3490 magnetic
 176           tape subsystems and 100% compatibles.
 177           It is safe to say "Y" here.
 178
 179
 180
 181 config VMLOGRDR
 182         tristate "Support for the z/VM recording system services (VM only)"
 183         depends on IUCV
 184         help
 185           Select this option if you want to be able to receive records collected
 186           by the z/VM recording system services, eg. from *LOGREC, *ACCOUNT or
 187           *SYMPTOM.
 188           This driver depends on the IUCV support driver.
 189
 190 config MONREADER
 191         tristate "API for reading z/VM monitor service records"
 192         depends on IUCV
 193         help
 194           Character device driver for reading z/VM monitor service records
 195
 196 endmenu
 197
 198 menu "Cryptographic devices"
 199
 200 config Z90CRYPT
 201         tristate "Support for PCI-attached cryptographic adapters"
 202         default "m"
 203         help
 204           Select this option if you want to use a PCI-attached cryptographic
 205           adapter like the PCI Cryptographic Accelerator (PCICA) or the PCI
 206           Cryptographic Coprocessor (PCICC).  This option is also available
 207           as a module called z90crypt.ko.
 208
 209 endmenu