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

--- 16 unchanged lines hidden --- 		67
68
69comment "Gigabit Ethernet default settings"
70 depends on QETH
71
72config QETH_IPV6
73 bool "IPv6 support for gigabit ethernet"
74 depends on (QETH = IPV6) || (QETH && IPV6 = 'y')

--- 16 unchanged lines hidden ---