| rjw | 1f88458 | 2022-01-06 17:20:42 +0800 | [diff] [blame^] | 1 | menu "S/390 network device drivers" |
| 2 | depends on NETDEVICES && S390 |
| 3 | |
| 4 | config LCS |
| 5 | def_tristate m |
| 6 | prompt "Lan Channel Station Interface" |
| 7 | depends on CCW && NETDEVICES && (ETHERNET || FDDI) |
| 8 | help |
| 9 | Select this option if you want to use LCS networking on IBM System z. |
| 10 | This device driver supports FDDI (IEEE 802.7) and Ethernet. |
| 11 | To compile as a module, choose M. The module name is lcs. |
| 12 | If you do not know what it is, it's safe to choose Y. |
| 13 | |
| 14 | config CTCM |
| 15 | def_tristate m |
| 16 | prompt "CTC and MPC SNA device support" |
| 17 | depends on CCW && NETDEVICES |
| 18 | help |
| 19 | Select this option if you want to use channel-to-channel |
| 20 | point-to-point networking on IBM System z. |
| 21 | This device driver supports real CTC coupling using ESCON. |
| 22 | It also supports virtual CTCs when running under VM. |
| 23 | This driver also supports channel-to-channel MPC SNA devices. |
| 24 | MPC is an SNA protocol device used by Communication Server for Linux. |
| 25 | To compile as a module, choose M. The module name is ctcm. |
| 26 | To compile into the kernel, choose Y. |
| 27 | If you do not need any channel-to-channel connection, choose N. |
| 28 | |
| 29 | config NETIUCV |
| 30 | def_tristate m |
| 31 | prompt "IUCV network device support (VM only)" |
| 32 | depends on IUCV && NETDEVICES |
| 33 | help |
| 34 | Select this option if you want to use inter-user communication |
| 35 | vehicle networking under VM or VIF. It enables a fast communication |
| 36 | link between VM guests. Using ifconfig a point-to-point connection |
| 37 | can be established to the Linux on IBM System z |
| 38 | running on the other VM guest. To compile as a module, choose M. |
| 39 | The module name is netiucv. If unsure, choose Y. |
| 40 | |
| 41 | config SMSGIUCV |
| 42 | def_tristate m |
| 43 | prompt "IUCV special message support (VM only)" |
| 44 | depends on IUCV |
| 45 | help |
| 46 | Select this option if you want to be able to receive SMSG messages |
| 47 | from other VM guest systems. |
| 48 | |
| 49 | config SMSGIUCV_EVENT |
| 50 | def_tristate m |
| 51 | prompt "Deliver IUCV special messages as uevents (VM only)" |
| 52 | depends on SMSGIUCV |
| 53 | help |
| 54 | Select this option to deliver CP special messages (SMSGs) as |
| 55 | uevents. The driver handles only those special messages that |
| 56 | start with "APP". |
| 57 | |
| 58 | To compile as a module, choose M. The module name is "smsgiucv_app". |
| 59 | |
| 60 | config QETH |
| 61 | def_tristate y |
| 62 | prompt "Gigabit Ethernet device support" |
| 63 | depends on CCW && NETDEVICES && IP_MULTICAST && QDIO && ETHERNET |
| 64 | help |
| 65 | This driver supports the IBM System z OSA Express adapters |
| 66 | in QDIO mode (all media types), HiperSockets interfaces and z/VM |
| 67 | virtual NICs for Guest LAN and VSWITCH. |
| 68 | |
| 69 | For details please refer to the documentation provided by IBM at |
| 70 | <http://www.ibm.com/developerworks/linux/linux390> |
| 71 | |
| 72 | To compile this driver as a module, choose M. |
| 73 | The module name is qeth. |
| 74 | |
| 75 | config QETH_L2 |
| 76 | def_tristate y |
| 77 | prompt "qeth layer 2 device support" |
| 78 | depends on QETH |
| 79 | help |
| 80 | Select this option to be able to run qeth devices in layer 2 mode. |
| 81 | To compile as a module, choose M. The module name is qeth_l2. |
| 82 | If unsure, choose y. |
| 83 | |
| 84 | config QETH_L3 |
| 85 | def_tristate y |
| 86 | prompt "qeth layer 3 device support" |
| 87 | depends on QETH |
| 88 | help |
| 89 | Select this option to be able to run qeth devices in layer 3 mode. |
| 90 | To compile as a module choose M. The module name is qeth_l3. |
| 91 | If unsure, choose Y. |
| 92 | |
| 93 | config QETH_IPV6 |
| 94 | def_bool y if (QETH_L3 = IPV6) || (QETH_L3 && IPV6 = 'y') |
| 95 | |
| 96 | config CCWGROUP |
| 97 | tristate |
| 98 | default (LCS || CTCM || QETH) |
| 99 | |
| 100 | endmenu |