Kconfig 3.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495
  1. menu "S/390 network device drivers"
  2. depends on NETDEVICES && S390
  3. config LCS
  4. tristate "Lan Channel Station Interface"
  5. depends on CCW && NETDEVICES && (NET_ETHERNET || TR || FDDI)
  6. help
  7. Select this option if you want to use LCS networking on IBM System z.
  8. This device driver supports Token Ring (IEEE 802.5),
  9. FDDI (IEEE 802.7) and Ethernet.
  10. To compile as a module, choose M. The module name is lcs.ko.
  11. If you do not know what it is, it's safe to choose Y.
  12. config CTCM
  13. tristate "CTC and MPC SNA device support"
  14. depends on CCW && NETDEVICES
  15. help
  16. Select this option if you want to use channel-to-channel
  17. point-to-point networking on IBM System z.
  18. This device driver supports real CTC coupling using ESCON.
  19. It also supports virtual CTCs when running under VM.
  20. This driver also supports channel-to-channel MPC SNA devices.
  21. MPC is an SNA protocol device used by Communication Server for Linux.
  22. To compile as a module, choose M. The module name is ctcm.ko.
  23. To compile into the kernel, choose Y.
  24. If you do not need any channel-to-channel connection, choose N.
  25. config NETIUCV
  26. tristate "IUCV network device support (VM only)"
  27. depends on IUCV && NETDEVICES
  28. help
  29. Select this option if you want to use inter-user communication
  30. vehicle networking under VM or VIF. It enables a fast communication
  31. link between VM guests. Using ifconfig a point-to-point connection
  32. can be established to the Linux on IBM System z
  33. running on the other VM guest. To compile as a module, choose M.
  34. The module name is netiucv.ko. If unsure, choose Y.
  35. config SMSGIUCV
  36. tristate "IUCV special message support (VM only)"
  37. depends on IUCV
  38. help
  39. Select this option if you want to be able to receive SMSG messages
  40. from other VM guest systems.
  41. config CLAW
  42. tristate "CLAW device support"
  43. depends on CCW && NETDEVICES
  44. help
  45. This driver supports channel attached CLAW devices.
  46. CLAW is Common Link Access for Workstation. Common devices
  47. that use CLAW are RS/6000s, Cisco Routers (CIP) and 3172 devices.
  48. To compile as a module, choose M. The module name is claw.ko.
  49. To compile into the kernel, choose Y.
  50. config QETH
  51. tristate "Gigabit Ethernet device support"
  52. depends on CCW && NETDEVICES && IP_MULTICAST && QDIO
  53. help
  54. This driver supports the IBM System z OSA Express adapters
  55. in QDIO mode (all media types), HiperSockets interfaces and VM GuestLAN
  56. interfaces in QDIO and HIPER mode.
  57. For details please refer to the documentation provided by IBM at
  58. <http://www.ibm.com/developerworks/linux/linux390>
  59. To compile this driver as a module, choose M.
  60. The module name is qeth.ko.
  61. config QETH_L2
  62. tristate "qeth layer 2 device support"
  63. depends on QETH
  64. help
  65. Select this option to be able to run qeth devices in layer 2 mode.
  66. To compile as a module, choose M. The module name is qeth_l2.ko.
  67. If unsure, choose y.
  68. config QETH_L3
  69. tristate "qeth layer 3 device support"
  70. depends on QETH
  71. help
  72. Select this option to be able to run qeth devices in layer 3 mode.
  73. To compile as a module choose M. The module name is qeth_l3.ko.
  74. If unsure, choose Y.
  75. config QETH_IPV6
  76. bool
  77. depends on (QETH_L3 = IPV6) || (QETH_L3 && IPV6 = 'y')
  78. default y
  79. config CCWGROUP
  80. tristate
  81. default (LCS || CTCM || QETH)
  82. endmenu