Doug / smarc-fsl-linux-kernel

1

2

#

2

#

3

# Network device configuration

3

# Network device configuration

4

#

4

#

5

6

menuconfig NETDEVICES

6

menuconfig NETDEVICES

7

default y if UML

7

default y if UML

8

depends on NET

8

depends on NET

9

bool "Network device support"

9

bool "Network device support"

10

---help---

10

---help---

11

You can say N here if you don't intend to connect your Linux box to

11

You can say N here if you don't intend to connect your Linux box to

12

any other computer at all.

12

any other computer at all.

13

14

You'll have to say Y if your computer contains a network card that

14

You'll have to say Y if your computer contains a network card that

15

you want to use under Linux. If you are going to run SLIP or PPP over

15

you want to use under Linux. If you are going to run SLIP or PPP over

16

telephone line or null modem cable you need say Y here. Connecting

16

telephone line or null modem cable you need say Y here. Connecting

17

two machines with parallel ports using PLIP needs this, as well as

17

two machines with parallel ports using PLIP needs this, as well as

18

AX.25/KISS for sending Internet traffic over amateur radio links.

18

AX.25/KISS for sending Internet traffic over amateur radio links.

19

20

See also "The Linux Network Administrator's Guide" by Olaf Kirch and

20

See also "The Linux Network Administrator's Guide" by Olaf Kirch and

21

Terry Dawson. Available at <http://www.tldp.org/guides.html>.

21

Terry Dawson. Available at <http://www.tldp.org/guides.html>.

22

23

If unsure, say Y.

23

If unsure, say Y.

24

25

# All the following symbols are dependent on NETDEVICES - do not repeat

25

# All the following symbols are dependent on NETDEVICES - do not repeat

26

# that for each of the symbols.

26

# that for each of the symbols.

27

if NETDEVICES

27

if NETDEVICES

28

29

config NETDEVICES_MULTIQUEUE

29

config NETDEVICES_MULTIQUEUE

30

bool "Netdevice multiple hardware queue support"

30

bool "Netdevice multiple hardware queue support"

31

---help---

31

---help---

32

Say Y here if you want to allow the network stack to use multiple

32

Say Y here if you want to allow the network stack to use multiple

33

hardware TX queues on an ethernet device.

33

hardware TX queues on an ethernet device.

34

35

Most people will say N here.

35

Most people will say N here.

36

37

config IFB

37

config IFB

38

tristate "Intermediate Functional Block support"

38

tristate "Intermediate Functional Block support"

39

depends on NET_CLS_ACT

39

depends on NET_CLS_ACT

40

---help---

40

---help---

41

This is an intermediate driver that allows sharing of

41

This is an intermediate driver that allows sharing of

42

resources.

42

resources.

43

To compile this driver as a module, choose M here: the module

43

To compile this driver as a module, choose M here: the module

44

will be called ifb. If you want to use more than one ifb

44

will be called ifb. If you want to use more than one ifb

45

device at a time, you need to compile this driver as a module.

45

device at a time, you need to compile this driver as a module.

46

Instead of 'ifb', the devices will then be called 'ifb0',

46

Instead of 'ifb', the devices will then be called 'ifb0',

47

'ifb1' etc.

47

'ifb1' etc.

48

Look at the iproute2 documentation directory for usage etc

48

Look at the iproute2 documentation directory for usage etc

49

50

config DUMMY

50

config DUMMY

51

tristate "Dummy net driver support"

51

tristate "Dummy net driver support"

52

---help---

52

---help---

53

This is essentially a bit-bucket device (i.e. traffic you send to

53

This is essentially a bit-bucket device (i.e. traffic you send to

54

this device is consigned into oblivion) with a configurable IP

54

this device is consigned into oblivion) with a configurable IP

55

address. It is most commonly used in order to make your currently

55

address. It is most commonly used in order to make your currently

56

inactive SLIP address seem like a real address for local programs.

56

inactive SLIP address seem like a real address for local programs.

57

If you use SLIP or PPP, you might want to say Y here. Since this

57

If you use SLIP or PPP, you might want to say Y here. Since this

58

thing often comes in handy, the default is Y. It won't enlarge your

58

thing often comes in handy, the default is Y. It won't enlarge your

59

kernel either. What a deal. Read about it in the Network

59

kernel either. What a deal. Read about it in the Network

60

Administrator's Guide, available from

60

Administrator's Guide, available from

61

<http://www.tldp.org/docs.html#guide>.

61

<http://www.tldp.org/docs.html#guide>.

62

63

To compile this driver as a module, choose M here: the module

63

To compile this driver as a module, choose M here: the module

64

will be called dummy. If you want to use more than one dummy

64

will be called dummy. If you want to use more than one dummy

65

device at a time, you need to compile this driver as a module.

65

device at a time, you need to compile this driver as a module.

66

Instead of 'dummy', the devices will then be called 'dummy0',

66

Instead of 'dummy', the devices will then be called 'dummy0',

67

'dummy1' etc.

67

'dummy1' etc.

68

69

config BONDING

69

config BONDING

70

tristate "Bonding driver support"

70

tristate "Bonding driver support"

71

depends on INET

71

depends on INET

72

---help---

72

---help---

73

Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet

73

Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet

74

Channels together. This is called 'Etherchannel' by Cisco,

74

Channels together. This is called 'Etherchannel' by Cisco,

75

'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.

75

'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.

76

77

The driver supports multiple bonding modes to allow for both high

77

The driver supports multiple bonding modes to allow for both high

78

performance and high availability operation.

78

performance and high availability operation.

79

80

Refer to <file:Documentation/networking/bonding.txt> for more

80

Refer to <file:Documentation/networking/bonding.txt> for more

81

information.

81

information.

82

83

To compile this driver as a module, choose M here: the module

83

To compile this driver as a module, choose M here: the module

84

will be called bonding.

84

will be called bonding.

85

86

config MACVLAN

86

config MACVLAN

87

tristate "MAC-VLAN support (EXPERIMENTAL)"

87

tristate "MAC-VLAN support (EXPERIMENTAL)"

88

depends on EXPERIMENTAL

88

depends on EXPERIMENTAL

89

---help---

89

---help---

90

This allows one to create virtual interfaces that map packets to

90

This allows one to create virtual interfaces that map packets to

91

or from specific MAC addresses to a particular interface.

91

or from specific MAC addresses to a particular interface.

92

93

Macvlan devices can be added using the "ip" command from the

93

Macvlan devices can be added using the "ip" command from the

94

iproute2 package starting with the iproute2-2.6.23 release:

94

iproute2 package starting with the iproute2-2.6.23 release:

95

96

"ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"

96

"ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"

97

98

To compile this driver as a module, choose M here: the module

98

To compile this driver as a module, choose M here: the module

99

will be called macvlan.

99

will be called macvlan.

100

101

config EQUALIZER

101

config EQUALIZER

102

tristate "EQL (serial line load balancing) support"

102

tristate "EQL (serial line load balancing) support"

103

---help---

103

---help---

104

If you have two serial connections to some other computer (this

104

If you have two serial connections to some other computer (this

105

usually requires two modems and two telephone lines) and you use

105

usually requires two modems and two telephone lines) and you use

106

SLIP (the protocol for sending Internet traffic over telephone

106

SLIP (the protocol for sending Internet traffic over telephone

107

lines) or PPP (a better SLIP) on them, you can make them behave like

107

lines) or PPP (a better SLIP) on them, you can make them behave like

108

one double speed connection using this driver. Naturally, this has

108

one double speed connection using this driver. Naturally, this has

109

to be supported at the other end as well, either with a similar EQL

109

to be supported at the other end as well, either with a similar EQL

110

Linux driver or with a Livingston Portmaster 2e.

110

Linux driver or with a Livingston Portmaster 2e.

111

112

Say Y if you want this and read

112

Say Y if you want this and read

113

<file:Documentation/networking/eql.txt>. You may also want to read

113

<file:Documentation/networking/eql.txt>. You may also want to read

114

section 6.2 of the NET-3-HOWTO, available from

114

section 6.2 of the NET-3-HOWTO, available from

115

<http://www.tldp.org/docs.html#howto>.

115

<http://www.tldp.org/docs.html#howto>.

116

117

To compile this driver as a module, choose M here: the module

117

To compile this driver as a module, choose M here: the module

118

will be called eql. If unsure, say N.

118

will be called eql. If unsure, say N.

119

120

config TUN

120

config TUN

121

tristate "Universal TUN/TAP device driver support"

121

tristate "Universal TUN/TAP device driver support"

122

select CRC32

122

select CRC32

123

---help---

123

---help---

124

TUN/TAP provides packet reception and transmission for user space

124

TUN/TAP provides packet reception and transmission for user space

125

programs. It can be viewed as a simple Point-to-Point or Ethernet

125

programs. It can be viewed as a simple Point-to-Point or Ethernet

126

device, which instead of receiving packets from a physical media,

126

device, which instead of receiving packets from a physical media,

127

receives them from user space program and instead of sending packets

127

receives them from user space program and instead of sending packets

128

via physical media writes them to the user space program.

128

via physical media writes them to the user space program.

129

130

When a program opens /dev/net/tun, driver creates and registers

130

When a program opens /dev/net/tun, driver creates and registers

131

corresponding net device tunX or tapX. After a program closed above

131

corresponding net device tunX or tapX. After a program closed above

132

devices, driver will automatically delete tunXX or tapXX device and

132

devices, driver will automatically delete tunXX or tapXX device and

133

all routes corresponding to it.

133

all routes corresponding to it.

134

135

Please read <file:Documentation/networking/tuntap.txt> for more

135

Please read <file:Documentation/networking/tuntap.txt> for more

136

information.

136

information.

137

138

To compile this driver as a module, choose M here: the module

138

To compile this driver as a module, choose M here: the module

139

will be called tun.

139

will be called tun.

140

141

If you don't know what to use this for, you don't need it.

141

If you don't know what to use this for, you don't need it.

142

143

config VETH

143

config VETH

144

tristate "Virtual ethernet pair device"

144

tristate "Virtual ethernet pair device"

145

---help---

145

---help---

146

This device is a local ethernet tunnel. Devices are created in pairs.

146

This device is a local ethernet tunnel. Devices are created in pairs.

147

When one end receives the packet it appears on its pair and vice

147

When one end receives the packet it appears on its pair and vice

148

versa.

148

versa.

149

150

config NET_SB1000

150

config NET_SB1000

151

tristate "General Instruments Surfboard 1000"

151

tristate "General Instruments Surfboard 1000"

152

depends on PNP

152

depends on PNP

153

---help---

153

---help---

154

This is a driver for the General Instrument (also known as

154

This is a driver for the General Instrument (also known as

155

NextLevel) SURFboard 1000 internal

155

NextLevel) SURFboard 1000 internal

156

cable modem. This is an ISA card which is used by a number of cable

156

cable modem. This is an ISA card which is used by a number of cable

157

TV companies to provide cable modem access. It's a one-way

157

TV companies to provide cable modem access. It's a one-way

158

downstream-only cable modem, meaning that your upstream net link is

158

downstream-only cable modem, meaning that your upstream net link is

159

provided by your regular phone modem.

159

provided by your regular phone modem.

160

161

At present this driver only compiles as a module, so say M here if

161

At present this driver only compiles as a module, so say M here if

162

you have this card. The module will be called sb1000. Then read

162

you have this card. The module will be called sb1000. Then read

163

<file:Documentation/networking/README.sb1000> for information on how

163

<file:Documentation/networking/README.sb1000> for information on how

164

to use this module, as it needs special ppp scripts for establishing

164

to use this module, as it needs special ppp scripts for establishing

165

a connection. Further documentation and the necessary scripts can be

165

a connection. Further documentation and the necessary scripts can be

166

found at:

166

found at:

167

168

<http://www.jacksonville.net/~fventuri/>

168

<http://www.jacksonville.net/~fventuri/>

169

<http://home.adelphia.net/~siglercm/sb1000.html>

169

<http://home.adelphia.net/~siglercm/sb1000.html>

170

<http://linuxpower.cx/~cable/>

170

<http://linuxpower.cx/~cable/>

171

172

If you don't have this card, of course say N.

172

If you don't have this card, of course say N.

173

174

source "drivers/net/arcnet/Kconfig"

174

source "drivers/net/arcnet/Kconfig"

175

176

source "drivers/net/phy/Kconfig"

176

source "drivers/net/phy/Kconfig"

177

178

#

178

#

179

# Ethernet

179

# Ethernet

180

#

180

#

181

182

menuconfig NET_ETHERNET

182

menuconfig NET_ETHERNET

183

bool "Ethernet (10 or 100Mbit)"

183

bool "Ethernet (10 or 100Mbit)"

184

depends on !UML

184

depends on !UML

185

---help---

185

---help---

186

Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common

186

Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common

187

type of Local Area Network (LAN) in universities and companies.

187

type of Local Area Network (LAN) in universities and companies.

188

189

Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over

189

Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over

190

coaxial cable, linking computers in a chain), 10BASE-T or twisted

190

coaxial cable, linking computers in a chain), 10BASE-T or twisted

191

pair (10 Mbps over twisted pair cable, linking computers to central

191

pair (10 Mbps over twisted pair cable, linking computers to central

192

hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),

192

hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),

193

100BASE-TX (100 Mbps over two twisted pair cables, using hubs),

193

100BASE-TX (100 Mbps over two twisted pair cables, using hubs),

194

100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair

194

100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair

195

cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)

195

cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)

196

[the 100BASE varieties are also known as Fast Ethernet], and Gigabit

196

[the 100BASE varieties are also known as Fast Ethernet], and Gigabit

197

Ethernet (1 Gbps over optical fiber or short copper links).

197

Ethernet (1 Gbps over optical fiber or short copper links).

198

199

If your Linux machine will be connected to an Ethernet and you have

199

If your Linux machine will be connected to an Ethernet and you have

200

an Ethernet network interface card (NIC) installed in your computer,

200

an Ethernet network interface card (NIC) installed in your computer,

201

say Y here and read the Ethernet-HOWTO, available from

201

say Y here and read the Ethernet-HOWTO, available from

202

<http://www.tldp.org/docs.html#howto>. You will then also have

202

<http://www.tldp.org/docs.html#howto>. You will then also have

203

to say Y to the driver for your particular NIC.

203

to say Y to the driver for your particular NIC.

204

205

Note that the answer to this question won't directly affect the

205

Note that the answer to this question won't directly affect the

206

kernel: saying N will just cause the configurator to skip all

206

kernel: saying N will just cause the configurator to skip all

207

the questions about Ethernet network cards. If unsure, say N.

207

the questions about Ethernet network cards. If unsure, say N.

208

209

if NET_ETHERNET

209

if NET_ETHERNET

210

211

config MII

211

config MII

212

tristate "Generic Media Independent Interface device support"

212

tristate "Generic Media Independent Interface device support"

213

help

213

help

214

Most ethernet controllers have MII transceiver either as an external

214

Most ethernet controllers have MII transceiver either as an external

215

or internal device. It is safe to say Y or M here even if your

215

or internal device. It is safe to say Y or M here even if your

216

ethernet card lack MII.

216

ethernet card lack MII.

217

218

config MACB

218

config MACB

219

tristate "Atmel MACB support"

219

tristate "Atmel MACB support"

220

depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91CAP9

220

depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91CAP9

221

select PHYLIB

221

select PHYLIB

222

help

222

help

223

The Atmel MACB ethernet interface is found on many AT32 and AT91

223

The Atmel MACB ethernet interface is found on many AT32 and AT91

224

parts. Say Y to include support for the MACB chip.

224

parts. Say Y to include support for the MACB chip.

225

226

To compile this driver as a module, choose M here: the module

226

To compile this driver as a module, choose M here: the module

227

will be called macb.

227

will be called macb.

228

229

source "drivers/net/arm/Kconfig"

229

source "drivers/net/arm/Kconfig"

230

231

config AX88796

231

config AX88796

232

tristate "ASIX AX88796 NE2000 clone support"

232

tristate "ASIX AX88796 NE2000 clone support"

233

depends on ARM || MIPS || SUPERH

233

depends on ARM || MIPS || SUPERH

234

select CRC32

234

select CRC32

235

select MII

235

select MII

236

help

236

help

237

AX88796 driver, using platform bus to provide

237

AX88796 driver, using platform bus to provide

238

chip detection and resources

238

chip detection and resources

239

240

config AX88796_93CX6

240

config AX88796_93CX6

241

bool "ASIX AX88796 external 93CX6 eeprom support"

241

bool "ASIX AX88796 external 93CX6 eeprom support"

242

depends on AX88796

242

depends on AX88796

243

select EEPROM_93CX6

243

select EEPROM_93CX6

244

help

244

help

245

Select this if your platform comes with an external 93CX6 eeprom.

245

Select this if your platform comes with an external 93CX6 eeprom.

246

247

config MACE

247

config MACE

248

tristate "MACE (Power Mac ethernet) support"

248

tristate "MACE (Power Mac ethernet) support"

249

depends on PPC_PMAC && PPC32

249

depends on PPC_PMAC && PPC32

250

select CRC32

250

select CRC32

251

help

251

help

252

Power Macintoshes and clones with Ethernet built-in on the

252

Power Macintoshes and clones with Ethernet built-in on the

253

motherboard will usually use a MACE (Medium Access Control for

253

motherboard will usually use a MACE (Medium Access Control for

254

Ethernet) interface. Say Y to include support for the MACE chip.

254

Ethernet) interface. Say Y to include support for the MACE chip.

255

256

To compile this driver as a module, choose M here: the module

256

To compile this driver as a module, choose M here: the module

257

will be called mace.

257

will be called mace.

258

259

config MACE_AAUI_PORT

259

config MACE_AAUI_PORT

260

bool "Use AAUI port instead of TP by default"

260

bool "Use AAUI port instead of TP by default"

261

depends on MACE

261

depends on MACE

262

help

262

help

263

Some Apple machines (notably the Apple Network Server) which use the

263

Some Apple machines (notably the Apple Network Server) which use the

264

MACE ethernet chip have an Apple AUI port (small 15-pin connector),

264

MACE ethernet chip have an Apple AUI port (small 15-pin connector),

265

instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say

265

instead of an 8-pin RJ45 connector for twisted-pair ethernet. Say

266

Y here if you have such a machine. If unsure, say N.

266

Y here if you have such a machine. If unsure, say N.

267

The driver will default to AAUI on ANS anyway, and if you use it as

267

The driver will default to AAUI on ANS anyway, and if you use it as

268

a module, you can provide the port_aaui=0|1 to force the driver.

268

a module, you can provide the port_aaui=0|1 to force the driver.

269

270

config BMAC

270

config BMAC

271

tristate "BMAC (G3 ethernet) support"

271

tristate "BMAC (G3 ethernet) support"

272

depends on PPC_PMAC && PPC32

272

depends on PPC_PMAC && PPC32

273

select CRC32

273

select CRC32

274

help

274

help

275

Say Y for support of BMAC Ethernet interfaces. These are used on G3

275

Say Y for support of BMAC Ethernet interfaces. These are used on G3

276

computers.

276

computers.

277

278

To compile this driver as a module, choose M here: the module

278

To compile this driver as a module, choose M here: the module

279

will be called bmac.

279

will be called bmac.

280

281

config ARIADNE

281

config ARIADNE

282

tristate "Ariadne support"

282

tristate "Ariadne support"

283

depends on ZORRO

283

depends on ZORRO

284

help

284

help

285

If you have a Village Tronic Ariadne Ethernet adapter, say Y.

285

If you have a Village Tronic Ariadne Ethernet adapter, say Y.

286

Otherwise, say N.

286

Otherwise, say N.

287

288

To compile this driver as a module, choose M here: the module

288

To compile this driver as a module, choose M here: the module

289

will be called ariadne.

289

will be called ariadne.

290

291

config A2065

291

config A2065

292

tristate "A2065 support"

292

tristate "A2065 support"

293

depends on ZORRO

293

depends on ZORRO

294

select CRC32

294

select CRC32

295

help

295

help

296

If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,

296

If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,

297

say N.

297

say N.

298

299

To compile this driver as a module, choose M here: the module

299

To compile this driver as a module, choose M here: the module

300

will be called a2065.

300

will be called a2065.

301

302

config HYDRA

302

config HYDRA

303

tristate "Hydra support"

303

tristate "Hydra support"

304

depends on ZORRO

304

depends on ZORRO

305

select CRC32

305

select CRC32

306

help

306

help

307

If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.

307

If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.

308

309

To compile this driver as a module, choose M here: the module

309

To compile this driver as a module, choose M here: the module

310

will be called hydra.

310

will be called hydra.

311

312

config ZORRO8390

312

config ZORRO8390

313

tristate "Zorro NS8390-based Ethernet support"

313

tristate "Zorro NS8390-based Ethernet support"

314

depends on ZORRO

314

depends on ZORRO

315

select CRC32

315

select CRC32

316

help

316

help

317

This driver is for Zorro Ethernet cards using an NS8390-compatible

317

This driver is for Zorro Ethernet cards using an NS8390-compatible

318

chipset, like the Village Tronic Ariadne II and the Individual

318

chipset, like the Village Tronic Ariadne II and the Individual

319

Computers X-Surf Ethernet cards. If you have such a card, say Y.

319

Computers X-Surf Ethernet cards. If you have such a card, say Y.

320

Otherwise, say N.

320

Otherwise, say N.

321

322

To compile this driver as a module, choose M here: the module

322

To compile this driver as a module, choose M here: the module

323

will be called zorro8390.

323

will be called zorro8390.

324

325

config APNE

325

config APNE

326

tristate "PCMCIA NE2000 support"

326

tristate "PCMCIA NE2000 support"

327

depends on AMIGA_PCMCIA

327

depends on AMIGA_PCMCIA

328

select CRC32

328

select CRC32

329

help

329

help

330

If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,

330

If you have a PCMCIA NE2000 compatible adapter, say Y. Otherwise,

331

say N.

331

say N.

332

333

To compile this driver as a module, choose M here: the module

333

To compile this driver as a module, choose M here: the module

334

will be called apne.

334

will be called apne.

335

336

config APOLLO_ELPLUS

336

config APOLLO_ELPLUS

337

tristate "Apollo 3c505 support"

337

tristate "Apollo 3c505 support"

338

depends on APOLLO

338

depends on APOLLO

339

help

339

help

340

Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.

340

Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.

341

If you don't have one made for Apollos, you can use one from a PC,

341

If you don't have one made for Apollos, you can use one from a PC,

342

except that your Apollo won't be able to boot from it (because the

342

except that your Apollo won't be able to boot from it (because the

343

code in the ROM will be for a PC).

343

code in the ROM will be for a PC).

344

345

config MAC8390

345

config MAC8390

346

bool "Macintosh NS 8390 based ethernet cards"

346

bool "Macintosh NS 8390 based ethernet cards"

347

depends on MAC

347

depends on MAC

348

select CRC32

348

select CRC32

349

help

349

help

350

If you want to include a driver to support Nubus or LC-PDS

350

If you want to include a driver to support Nubus or LC-PDS

351

Ethernet cards using an NS8390 chipset or its equivalent, say Y

351

Ethernet cards using an NS8390 chipset or its equivalent, say Y

352

and read the Ethernet-HOWTO, available from

352

and read the Ethernet-HOWTO, available from

353

<http://www.tldp.org/docs.html#howto>.

353

<http://www.tldp.org/docs.html#howto>.

354

355

config MAC89x0

355

config MAC89x0

356

tristate "Macintosh CS89x0 based ethernet cards"

356

tristate "Macintosh CS89x0 based ethernet cards"

357

depends on MAC

357

depends on MAC

358

---help---

358

---help---

359

Support for CS89x0 chipset based Ethernet cards. If you have a

359

Support for CS89x0 chipset based Ethernet cards. If you have a

360

Nubus or LC-PDS network (Ethernet) card of this type, say Y and

360

Nubus or LC-PDS network (Ethernet) card of this type, say Y and

361

read the Ethernet-HOWTO, available from

361

read the Ethernet-HOWTO, available from

362

<http://www.tldp.org/docs.html#howto>.

362

<http://www.tldp.org/docs.html#howto>.

363

364

To compile this driver as a module, choose M here. This module will

364

To compile this driver as a module, choose M here. This module will

365

be called mac89x0.

365

be called mac89x0.

366

367

config MACSONIC

367

config MACSONIC

368

tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"

368

tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"

369

depends on MAC

369

depends on MAC

370

---help---

370

---help---

371

Support for NatSemi SONIC based Ethernet devices. This includes

371

Support for NatSemi SONIC based Ethernet devices. This includes

372

the onboard Ethernet in many Quadras as well as some LC-PDS,

372

the onboard Ethernet in many Quadras as well as some LC-PDS,

373

a few Nubus and all known Comm Slot Ethernet cards. If you have

373

a few Nubus and all known Comm Slot Ethernet cards. If you have

374

one of these say Y and read the Ethernet-HOWTO, available from

374

one of these say Y and read the Ethernet-HOWTO, available from

375

<http://www.tldp.org/docs.html#howto>.

375

<http://www.tldp.org/docs.html#howto>.

376

377

To compile this driver as a module, choose M here. This module will

377

To compile this driver as a module, choose M here. This module will

378

be called macsonic.

378

be called macsonic.

379

380

config MACMACE

380

config MACMACE

381

bool "Macintosh (AV) onboard MACE ethernet"

381

bool "Macintosh (AV) onboard MACE ethernet"

382

depends on MAC

382

depends on MAC

383

select CRC32

383

select CRC32

384

help

384

help

385

Support for the onboard AMD 79C940 MACE Ethernet controller used in

385

Support for the onboard AMD 79C940 MACE Ethernet controller used in

386

the 660AV and 840AV Macintosh. If you have one of these Macintoshes

386

the 660AV and 840AV Macintosh. If you have one of these Macintoshes

387

say Y and read the Ethernet-HOWTO, available from

387

say Y and read the Ethernet-HOWTO, available from

388

<http://www.tldp.org/docs.html#howto>.

388

<http://www.tldp.org/docs.html#howto>.

389

390

config MVME147_NET

390

config MVME147_NET

391

tristate "MVME147 (Lance) Ethernet support"

391

tristate "MVME147 (Lance) Ethernet support"

392

depends on MVME147

392

depends on MVME147

393

select CRC32

393

select CRC32

394

help

394

help

395

Support for the on-board Ethernet interface on the Motorola MVME147

395

Support for the on-board Ethernet interface on the Motorola MVME147

396

single-board computer. Say Y here to include the

396

single-board computer. Say Y here to include the

397

driver for this chip in your kernel.

397

driver for this chip in your kernel.

398

To compile this driver as a module, choose M here.

398

To compile this driver as a module, choose M here.

399

400

config MVME16x_NET

400

config MVME16x_NET

401

tristate "MVME16x Ethernet support"

401

tristate "MVME16x Ethernet support"

402

depends on MVME16x

402

depends on MVME16x

403

help

403

help

404

This is the driver for the Ethernet interface on the Motorola

404

This is the driver for the Ethernet interface on the Motorola

405

MVME162, 166, 167, 172 and 177 boards. Say Y here to include the

405

MVME162, 166, 167, 172 and 177 boards. Say Y here to include the

406

driver for this chip in your kernel.

406

driver for this chip in your kernel.

407

To compile this driver as a module, choose M here.

407

To compile this driver as a module, choose M here.

408

409

config BVME6000_NET

409

config BVME6000_NET

410

tristate "BVME6000 Ethernet support"

410

tristate "BVME6000 Ethernet support"

411

depends on BVME6000

411

depends on BVME6000

412

help

412

help

413

This is the driver for the Ethernet interface on BVME4000 and

413

This is the driver for the Ethernet interface on BVME4000 and

414

BVME6000 VME boards. Say Y here to include the driver for this chip

414

BVME6000 VME boards. Say Y here to include the driver for this chip

415

in your kernel.

415

in your kernel.

416

To compile this driver as a module, choose M here.

416

To compile this driver as a module, choose M here.

417

418

config ATARILANCE

418

config ATARILANCE

419

tristate "Atari Lance support"

419

tristate "Atari Lance support"

420

depends on ATARI

420

depends on ATARI

421

help

421

help

422

Say Y to include support for several Atari Ethernet adapters based

422

Say Y to include support for several Atari Ethernet adapters based

423

on the AMD Lance chipset: RieblCard (with or without battery), or

423

on the AMD Lance chipset: RieblCard (with or without battery), or

424

PAMCard VME (also the version by Rhotron, with different addresses).

424

PAMCard VME (also the version by Rhotron, with different addresses).

425

426

config SUN3LANCE

426

config SUN3LANCE

427

tristate "Sun3/Sun3x on-board LANCE support"

427

tristate "Sun3/Sun3x on-board LANCE support"

428

depends on SUN3 || SUN3X

428

depends on SUN3 || SUN3X

429

help

429

help

430

Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)

430

Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)

431

featured an AMD Lance 10Mbit Ethernet controller on board; say Y

431

featured an AMD Lance 10Mbit Ethernet controller on board; say Y

432

here to compile in the Linux driver for this and enable Ethernet.

432

here to compile in the Linux driver for this and enable Ethernet.

433

General Linux information on the Sun 3 and 3x series (now

433

General Linux information on the Sun 3 and 3x series (now

434

discontinued) is at

434

discontinued) is at

435

<http://www.angelfire.com/ca2/tech68k/sun3.html>.

435

<http://www.angelfire.com/ca2/tech68k/sun3.html>.

436

437

If you're not building a kernel for a Sun 3, say N.

437

If you're not building a kernel for a Sun 3, say N.

438

439

config SUN3_82586

439

config SUN3_82586

440

bool "Sun3 on-board Intel 82586 support"

440

bool "Sun3 on-board Intel 82586 support"

441

depends on SUN3

441

depends on SUN3

442

help

442

help

443

This driver enables support for the on-board Intel 82586 based

443

This driver enables support for the on-board Intel 82586 based

444

Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note

444

Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards. Note

445

that this driver does not support 82586-based adapters on additional

445

that this driver does not support 82586-based adapters on additional

446

VME boards.

446

VME boards.

447

448

config HPLANCE

448

config HPLANCE

449

bool "HP on-board LANCE support"

449

bool "HP on-board LANCE support"

450

depends on DIO

450

depends on DIO

451

select CRC32

451

select CRC32

452

help

452

help

453

If you want to use the builtin "LANCE" Ethernet controller on an

453

If you want to use the builtin "LANCE" Ethernet controller on an

454

HP300 machine, say Y here.

454

HP300 machine, say Y here.

455

456

config LASI_82596

456

config LASI_82596

457

tristate "Lasi ethernet"

457

tristate "Lasi ethernet"

458

depends on GSC

458

depends on GSC

459

help

459

help

460

Say Y here to support the builtin Intel 82596 ethernet controller

460

Say Y here to support the builtin Intel 82596 ethernet controller

461

found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.

461

found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.

462

463

config SNI_82596

463

config SNI_82596

464

tristate "SNI RM ethernet"

464

tristate "SNI RM ethernet"

465

depends on NET_ETHERNET && SNI_RM

465

depends on NET_ETHERNET && SNI_RM

466

help

466

help

467

Say Y here to support the on-board Intel 82596 ethernet controller

467

Say Y here to support the on-board Intel 82596 ethernet controller

468

built into SNI RM machines.

468

built into SNI RM machines.

469

470

config KORINA

470

config KORINA

471

tristate "Korina (IDT RC32434) Ethernet support"

471

tristate "Korina (IDT RC32434) Ethernet support"

472

depends on NET_ETHERNET && MIKROTIK_RB532

472

depends on NET_ETHERNET && MIKROTIK_RB532

473

help

473

help

474

If you have a Mikrotik RouterBoard 500 or IDT RC32434

474

If you have a Mikrotik RouterBoard 500 or IDT RC32434

475

based system say Y. Otherwise say N.

475

based system say Y. Otherwise say N.

476

477

config MIPS_JAZZ_SONIC

477

config MIPS_JAZZ_SONIC

478

tristate "MIPS JAZZ onboard SONIC Ethernet support"

478

tristate "MIPS JAZZ onboard SONIC Ethernet support"

479

depends on MACH_JAZZ

479

depends on MACH_JAZZ

480

help

480

help

481

This is the driver for the onboard card of MIPS Magnum 4000,

481

This is the driver for the onboard card of MIPS Magnum 4000,

482

Acer PICA, Olivetti M700-10 and a few other identical OEM systems.

482

Acer PICA, Olivetti M700-10 and a few other identical OEM systems.

483

484

config MIPS_AU1X00_ENET

484

config MIPS_AU1X00_ENET

485

bool "MIPS AU1000 Ethernet support"

485

bool "MIPS AU1000 Ethernet support"

486

depends on SOC_AU1X00

486

depends on SOC_AU1X00

487

select PHYLIB

487

select PHYLIB

488

select CRC32

488

select CRC32

489

help

489

help

490

If you have an Alchemy Semi AU1X00 based system

490

If you have an Alchemy Semi AU1X00 based system

491

say Y. Otherwise, say N.

491

say Y. Otherwise, say N.

492

493

config SGI_IOC3_ETH

493

config SGI_IOC3_ETH

494

bool "SGI IOC3 Ethernet"

494

bool "SGI IOC3 Ethernet"

495

depends on PCI && SGI_IP27

495

depends on PCI && SGI_IP27

496

select CRC32

496

select CRC32

497

select MII

497

select MII

498

help

498

help

499

If you have a network (Ethernet) card of this type, say Y and read

499

If you have a network (Ethernet) card of this type, say Y and read

500

the Ethernet-HOWTO, available from

500

the Ethernet-HOWTO, available from

501

<http://www.tldp.org/docs.html#howto>.

501

<http://www.tldp.org/docs.html#howto>.

502

503

config MIPS_SIM_NET

503

config MIPS_SIM_NET

504

tristate "MIPS simulator Network device"

504

tristate "MIPS simulator Network device"

505

depends on MIPS_SIM

505

depends on MIPS_SIM

506

help

506

help

507

The MIPSNET device is a simple Ethernet network device which is

507

The MIPSNET device is a simple Ethernet network device which is

508

emulated by the MIPS Simulator.

508

emulated by the MIPS Simulator.

509

If you are not using a MIPSsim or are unsure, say N.

509

If you are not using a MIPSsim or are unsure, say N.

510

511

config SGI_O2MACE_ETH

511

config SGI_O2MACE_ETH

512

tristate "SGI O2 MACE Fast Ethernet support"

512

tristate "SGI O2 MACE Fast Ethernet support"

513

depends on SGI_IP32=y

513

depends on SGI_IP32=y

514

515

config STNIC

515

config STNIC

516

tristate "National DP83902AV support"

516

tristate "National DP83902AV support"

517

depends on SUPERH

517

depends on SUPERH

518

select CRC32

518

select CRC32

519

help

519

help

520

Support for cards based on the National Semiconductor DP83902AV

520

Support for cards based on the National Semiconductor DP83902AV

521

ST-NIC Serial Network Interface Controller for Twisted Pair. This

521

ST-NIC Serial Network Interface Controller for Twisted Pair. This

522

is a 10Mbit/sec Ethernet controller. Product overview and specs at

522

is a 10Mbit/sec Ethernet controller. Product overview and specs at

523

<http://www.national.com/pf/DP/DP83902A.html>.

523

<http://www.national.com/pf/DP/DP83902A.html>.

524

525

If unsure, say N.

525

If unsure, say N.

526

527

config SH_ETH

527

config SH_ETH

528

tristate "Renesas SuperH Ethernet support"

528

tristate "Renesas SuperH Ethernet support"

529

depends on SUPERH && \

529

depends on SUPERH && \

530

(CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712)

530

(CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712)

531

select CRC32

531

select CRC32

532

select MII

532

select MII

533

select MDIO_BITBANG

533

select MDIO_BITBANG

534

select PHYLIB

534

select PHYLIB

535

help

535

help

536

Renesas SuperH Ethernet device driver.

536

Renesas SuperH Ethernet device driver.

537

This driver support SH7710 and SH7712.

537

This driver support SH7710 and SH7712.

538

539

config SUNLANCE

539

config SUNLANCE

540

tristate "Sun LANCE support"

540

tristate "Sun LANCE support"

541

depends on SBUS

541

depends on SBUS

542

select CRC32

542

select CRC32

543

help

543

help

544

This driver supports the "le" interface present on all 32-bit Sparc

544

This driver supports the "le" interface present on all 32-bit Sparc

545

systems, on some older Ultra systems and as an Sbus option. These

545

systems, on some older Ultra systems and as an Sbus option. These

546

cards are based on the AMD Lance chipset, which is better known

546

cards are based on the AMD Lance chipset, which is better known

547

via the NE2100 cards.

547

via the NE2100 cards.

548

549

To compile this driver as a module, choose M here: the module

549

To compile this driver as a module, choose M here: the module

550

will be called sunlance.

550

will be called sunlance.

551

552

config HAPPYMEAL

552

config HAPPYMEAL

553

tristate "Sun Happy Meal 10/100baseT support"

553

tristate "Sun Happy Meal 10/100baseT support"

554

depends on SBUS || PCI

554

depends on SBUS || PCI

555

select CRC32

555

select CRC32

556

help

556

help

557

This driver supports the "hme" interface present on most Ultra

557

This driver supports the "hme" interface present on most Ultra

558

systems and as an option on older Sbus systems. This driver supports

558

systems and as an option on older Sbus systems. This driver supports

559

both PCI and Sbus devices. This driver also supports the "qfe" quad

559

both PCI and Sbus devices. This driver also supports the "qfe" quad

560

100baseT device available in both PCI and Sbus configurations.

560

100baseT device available in both PCI and Sbus configurations.

561

562

To compile this driver as a module, choose M here: the module

562

To compile this driver as a module, choose M here: the module

563

will be called sunhme.

563

will be called sunhme.

564

565

config SUNBMAC

565

config SUNBMAC

566

tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"

566

tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"

567

depends on SBUS && EXPERIMENTAL

567

depends on SBUS && EXPERIMENTAL

568

select CRC32

568

select CRC32

569

help

569

help

570

This driver supports the "be" interface available as an Sbus option.

570

This driver supports the "be" interface available as an Sbus option.

571

This is Sun's older 100baseT Ethernet device.

571

This is Sun's older 100baseT Ethernet device.

572

573

To compile this driver as a module, choose M here: the module

573

To compile this driver as a module, choose M here: the module

574

will be called sunbmac.

574

will be called sunbmac.

575

576

config SUNQE

576

config SUNQE

577

tristate "Sun QuadEthernet support"

577

tristate "Sun QuadEthernet support"

578

depends on SBUS

578

depends on SBUS

579

select CRC32

579

select CRC32

580

help

580

help

581

This driver supports the "qe" 10baseT Ethernet device, available as

581

This driver supports the "qe" 10baseT Ethernet device, available as

582

an Sbus option. Note that this is not the same as Quad FastEthernet

582

an Sbus option. Note that this is not the same as Quad FastEthernet

583

"qfe" which is supported by the Happy Meal driver instead.

583

"qfe" which is supported by the Happy Meal driver instead.

584

585

To compile this driver as a module, choose M here: the module

585

To compile this driver as a module, choose M here: the module

586

will be called sunqe.

586

will be called sunqe.

587

588

config SUNGEM

588

config SUNGEM

589

tristate "Sun GEM support"

589

tristate "Sun GEM support"

590

depends on PCI

590

depends on PCI

591

select CRC32

591

select CRC32

592

help

592

help

593

Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also

593

Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0. See also

594

<http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.

594

<http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.

595

596

config CASSINI

596

config CASSINI

597

tristate "Sun Cassini support"

597

tristate "Sun Cassini support"

598

depends on PCI

598

depends on PCI

599

select CRC32

599

select CRC32

600

help

600

help

601

Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also

601

Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also

602

<http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>

602

<http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>

603

604

config SUNVNET

604

config SUNVNET

605

tristate "Sun Virtual Network support"

605

tristate "Sun Virtual Network support"

606

depends on SUN_LDOMS

606

depends on SUN_LDOMS

607

help

607

help

608

Support for virtual network devices under Sun Logical Domains.

608

Support for virtual network devices under Sun Logical Domains.

609

610

config NET_VENDOR_3COM

610

config NET_VENDOR_3COM

611

bool "3COM cards"

611

bool "3COM cards"

612

depends on ISA || EISA || MCA || PCI

612

depends on ISA || EISA || MCA || PCI

613

help

613

help

614

If you have a network (Ethernet) card belonging to this class, say Y

614

If you have a network (Ethernet) card belonging to this class, say Y

615

and read the Ethernet-HOWTO, available from

615

and read the Ethernet-HOWTO, available from

616

<http://www.tldp.org/docs.html#howto>.

616

<http://www.tldp.org/docs.html#howto>.

617

618

Note that the answer to this question doesn't directly affect the

618

Note that the answer to this question doesn't directly affect the

619

kernel: saying N will just cause the configurator to skip all

619

kernel: saying N will just cause the configurator to skip all

620

the questions about 3COM cards. If you say Y, you will be asked for

620

the questions about 3COM cards. If you say Y, you will be asked for

621

your specific card in the following questions.

621

your specific card in the following questions.

622

623

config EL1

623

config EL1

624

tristate "3c501 \"EtherLink\" support"

624

tristate "3c501 \"EtherLink\" support"

625

depends on NET_VENDOR_3COM && ISA

625

depends on NET_VENDOR_3COM && ISA

626

---help---

626

---help---

627

If you have a network (Ethernet) card of this type, say Y and read

627

If you have a network (Ethernet) card of this type, say Y and read

628

the Ethernet-HOWTO, available from

628

the Ethernet-HOWTO, available from

629

<http://www.tldp.org/docs.html#howto>. Also, consider buying a

629

<http://www.tldp.org/docs.html#howto>. Also, consider buying a

630

new card, since the 3c501 is slow, broken, and obsolete: you will

630

new card, since the 3c501 is slow, broken, and obsolete: you will

631

have problems. Some people suggest to ping ("man ping") a nearby

631

have problems. Some people suggest to ping ("man ping") a nearby

632

machine every minute ("man cron") when using this card.

632

machine every minute ("man cron") when using this card.

633

634

To compile this driver as a module, choose M here. The module

634

To compile this driver as a module, choose M here. The module

635

will be called 3c501.

635

will be called 3c501.

636

637

config EL2

637

config EL2

638

tristate "3c503 \"EtherLink II\" support"

638

tristate "3c503 \"EtherLink II\" support"

639

depends on NET_VENDOR_3COM && ISA

639

depends on NET_VENDOR_3COM && ISA

640

select CRC32

640

select CRC32

641

help

641

help

642

If you have a network (Ethernet) card of this type, say Y and read

642

If you have a network (Ethernet) card of this type, say Y and read

643

the Ethernet-HOWTO, available from

643

the Ethernet-HOWTO, available from

644

<http://www.tldp.org/docs.html#howto>.

644

<http://www.tldp.org/docs.html#howto>.

645

646

To compile this driver as a module, choose M here. The module

646

To compile this driver as a module, choose M here. The module

647

will be called 3c503.

647

will be called 3c503.

648

649

config ELPLUS

649

config ELPLUS

650

tristate "3c505 \"EtherLink Plus\" support"

650

tristate "3c505 \"EtherLink Plus\" support"

651

depends on NET_VENDOR_3COM && ISA && ISA_DMA_API

651

depends on NET_VENDOR_3COM && ISA && ISA_DMA_API

652

---help---

652

---help---

653

Information about this network (Ethernet) card can be found in

653

Information about this network (Ethernet) card can be found in

654

<file:Documentation/networking/3c505.txt>. If you have a card of

654

<file:Documentation/networking/3c505.txt>. If you have a card of

655

this type, say Y and read the Ethernet-HOWTO, available from

655

this type, say Y and read the Ethernet-HOWTO, available from

656

<http://www.tldp.org/docs.html#howto>.

656

<http://www.tldp.org/docs.html#howto>.

657

658

To compile this driver as a module, choose M here. The module

658

To compile this driver as a module, choose M here. The module

659

will be called 3c505.

659

will be called 3c505.

660

661

config EL16

661

config EL16

662

tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"

662

tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"

663

depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL

663

depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL

664

help

664

help

665

If you have a network (Ethernet) card of this type, say Y and read

665

If you have a network (Ethernet) card of this type, say Y and read

666

the Ethernet-HOWTO, available from

666

the Ethernet-HOWTO, available from

667

<http://www.tldp.org/docs.html#howto>.

667

<http://www.tldp.org/docs.html#howto>.

668

669

To compile this driver as a module, choose M here. The module

669

To compile this driver as a module, choose M here. The module

670

will be called 3c507.

670

will be called 3c507.

671

672

config EL3

672

config EL3

673

tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"

673

tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"

674

depends on NET_VENDOR_3COM && (ISA || EISA || MCA)

674

depends on NET_VENDOR_3COM && (ISA || EISA || MCA)

675

---help---

675

---help---

676

If you have a network (Ethernet) card belonging to the 3Com

676

If you have a network (Ethernet) card belonging to the 3Com

677

EtherLinkIII series, say Y and read the Ethernet-HOWTO, available

677

EtherLinkIII series, say Y and read the Ethernet-HOWTO, available

678

from <http://www.tldp.org/docs.html#howto>.

678

from <http://www.tldp.org/docs.html#howto>.

679

680

If your card is not working you may need to use the DOS

680

If your card is not working you may need to use the DOS

681

setup disk to disable Plug & Play mode, and to select the default

681

setup disk to disable Plug & Play mode, and to select the default

682

media type.

682

media type.

683

684

To compile this driver as a module, choose M here. The module

684

To compile this driver as a module, choose M here. The module

685

will be called 3c509.

685

will be called 3c509.

686

687

config 3C515

687

config 3C515

688

tristate "3c515 ISA \"Fast EtherLink\""

688

tristate "3c515 ISA \"Fast EtherLink\""

689

depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API

689

depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API

690

help

690

help

691

If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet

691

If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet

692

network card, say Y and read the Ethernet-HOWTO, available from

692

network card, say Y and read the Ethernet-HOWTO, available from

693

<http://www.tldp.org/docs.html#howto>.

693

<http://www.tldp.org/docs.html#howto>.

694

695

To compile this driver as a module, choose M here. The module

695

To compile this driver as a module, choose M here. The module

696

will be called 3c515.

696

will be called 3c515.

697

698

config ELMC

698

config ELMC

699

tristate "3c523 \"EtherLink/MC\" support"

699

tristate "3c523 \"EtherLink/MC\" support"

700

depends on NET_VENDOR_3COM && MCA_LEGACY

700

depends on NET_VENDOR_3COM && MCA_LEGACY

701

help

701

help

702

If you have a network (Ethernet) card of this type, say Y and read

702

If you have a network (Ethernet) card of this type, say Y and read

703

the Ethernet-HOWTO, available from

703

the Ethernet-HOWTO, available from

704

<http://www.tldp.org/docs.html#howto>.

704

<http://www.tldp.org/docs.html#howto>.

705

706

To compile this driver as a module, choose M here. The module

706

To compile this driver as a module, choose M here. The module

707

will be called 3c523.

707

will be called 3c523.

708

709

config ELMC_II

709

config ELMC_II

710

tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"

710

tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"

711

depends on NET_VENDOR_3COM && MCA && MCA_LEGACY

711

depends on NET_VENDOR_3COM && MCA && MCA_LEGACY

712

help

712

help

713

If you have a network (Ethernet) card of this type, say Y and read

713

If you have a network (Ethernet) card of this type, say Y and read

714

the Ethernet-HOWTO, available from

714

the Ethernet-HOWTO, available from

715

<http://www.tldp.org/docs.html#howto>.

715

<http://www.tldp.org/docs.html#howto>.

716

717

To compile this driver as a module, choose M here. The module

717

To compile this driver as a module, choose M here. The module

718

will be called 3c527.

718

will be called 3c527.

719

720

config VORTEX

720

config VORTEX

721

tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"

721

tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"

722

depends on NET_VENDOR_3COM && (PCI || EISA)

722

depends on NET_VENDOR_3COM && (PCI || EISA)

723

select MII

723

select MII

724

---help---

724

---help---

725

This option enables driver support for a large number of 10Mbps and

725

This option enables driver support for a large number of 10Mbps and

726

10/100Mbps EISA, PCI and PCMCIA 3Com network cards:

726

10/100Mbps EISA, PCI and PCMCIA 3Com network cards:

727

728

"Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI

728

"Vortex" (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI

729

"Boomerang" (EtherLink XL 3c900 or 3c905) PCI

729

"Boomerang" (EtherLink XL 3c900 or 3c905) PCI

730

"Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus

730

"Cyclone" (3c540/3c900/3c905/3c980/3c575/3c656) PCI and Cardbus

731

"Tornado" (3c905) PCI

731

"Tornado" (3c905) PCI

732

"Hurricane" (3c555/3cSOHO) PCI

732

"Hurricane" (3c555/3cSOHO) PCI

733

734

If you have such a card, say Y and read the Ethernet-HOWTO,

734

If you have such a card, say Y and read the Ethernet-HOWTO,

735

available from <http://www.tldp.org/docs.html#howto>. More

735

available from <http://www.tldp.org/docs.html#howto>. More

736

specific information is in

736

specific information is in

737

<file:Documentation/networking/vortex.txt> and in the comments at

737

<file:Documentation/networking/vortex.txt> and in the comments at

738

the beginning of <file:drivers/net/3c59x.c>.

738

the beginning of <file:drivers/net/3c59x.c>.

739

740

To compile this support as a module, choose M here.

740

To compile this support as a module, choose M here.

741

742

config TYPHOON

742

config TYPHOON

743

tristate "3cr990 series \"Typhoon\" support"

743

tristate "3cr990 series \"Typhoon\" support"

744

depends on NET_VENDOR_3COM && PCI

744

depends on NET_VENDOR_3COM && PCI

745

select CRC32

745

select CRC32

746

---help---

746

---help---

747

This option enables driver support for the 3cr990 series of cards:

747

This option enables driver support for the 3cr990 series of cards:

748

749

3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,

749

3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,

750

3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,

750

3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,

751

3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR

751

3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR

752

753

If you have a network (Ethernet) card of this type, say Y and read

753

If you have a network (Ethernet) card of this type, say Y and read

754

the Ethernet-HOWTO, available from

754

the Ethernet-HOWTO, available from

755

<http://www.tldp.org/docs.html#howto>.

755

<http://www.tldp.org/docs.html#howto>.

756

757

To compile this driver as a module, choose M here. The module

757

To compile this driver as a module, choose M here. The module

758

will be called typhoon.

758

will be called typhoon.

759

760

config LANCE

760

config LANCE

761

tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"

761

tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"

762

depends on ISA && ISA_DMA_API

762

depends on ISA && ISA_DMA_API

763

help

763

help

764

If you have a network (Ethernet) card of this type, say Y and read

764

If you have a network (Ethernet) card of this type, say Y and read

765

the Ethernet-HOWTO, available from

765

the Ethernet-HOWTO, available from

766

<http://www.tldp.org/docs.html#howto>. Some LinkSys cards are

766

<http://www.tldp.org/docs.html#howto>. Some LinkSys cards are

767

of this type.

767

of this type.

768

769

To compile this driver as a module, choose M here: the module

769

To compile this driver as a module, choose M here: the module

770

will be called lance. This is recommended.

770

will be called lance. This is recommended.

771

772

config NET_VENDOR_SMC

772

config NET_VENDOR_SMC

773

bool "Western Digital/SMC cards"

773

bool "Western Digital/SMC cards"

774

depends on ISA || MCA || EISA || MAC

774

depends on ISA || MCA || EISA || MAC

775

help

775

help

776

If you have a network (Ethernet) card belonging to this class, say Y

776

If you have a network (Ethernet) card belonging to this class, say Y

777

and read the Ethernet-HOWTO, available from

777

and read the Ethernet-HOWTO, available from

778

<http://www.tldp.org/docs.html#howto>.

778

<http://www.tldp.org/docs.html#howto>.

779

780

Note that the answer to this question doesn't directly affect the

780

Note that the answer to this question doesn't directly affect the

781

kernel: saying N will just cause the configurator to skip all

781

kernel: saying N will just cause the configurator to skip all

782

the questions about Western Digital cards. If you say Y, you will be

782

the questions about Western Digital cards. If you say Y, you will be

783

asked for your specific card in the following questions.

783

asked for your specific card in the following questions.

784

785

config WD80x3

785

config WD80x3

786

tristate "WD80*3 support"

786

tristate "WD80*3 support"

787

depends on NET_VENDOR_SMC && ISA

787

depends on NET_VENDOR_SMC && ISA

788

select CRC32

788

select CRC32

789

help

789

help

790

If you have a network (Ethernet) card of this type, say Y and read

790

If you have a network (Ethernet) card of this type, say Y and read

791

the Ethernet-HOWTO, available from

791

the Ethernet-HOWTO, available from

792

<http://www.tldp.org/docs.html#howto>.

792

<http://www.tldp.org/docs.html#howto>.

793

794

To compile this driver as a module, choose M here. The module

794

To compile this driver as a module, choose M here. The module

795

will be called wd.

795

will be called wd.

796

797

config ULTRAMCA

797

config ULTRAMCA

798

tristate "SMC Ultra MCA support"

798

tristate "SMC Ultra MCA support"

799

depends on NET_VENDOR_SMC && MCA

799

depends on NET_VENDOR_SMC && MCA

800

select CRC32

800

select CRC32

801

help

801

help

802

If you have a network (Ethernet) card of this type and are running

802

If you have a network (Ethernet) card of this type and are running

803

an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,

803

an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,

804

available from <http://www.tldp.org/docs.html#howto>.

804

available from <http://www.tldp.org/docs.html#howto>.

805

806

To compile this driver as a module, choose M here. The module

806

To compile this driver as a module, choose M here. The module

807

will be called smc-mca.

807

will be called smc-mca.

808

809

config ULTRA

809

config ULTRA

810

tristate "SMC Ultra support"

810

tristate "SMC Ultra support"

811

depends on NET_VENDOR_SMC && ISA

811

depends on NET_VENDOR_SMC && ISA

812

select CRC32

812

select CRC32

813

---help---

813

---help---

814

If you have a network (Ethernet) card of this type, say Y and read

814

If you have a network (Ethernet) card of this type, say Y and read

815

the Ethernet-HOWTO, available from

815

the Ethernet-HOWTO, available from

816

<http://www.tldp.org/docs.html#howto>.

816

<http://www.tldp.org/docs.html#howto>.

817

818

Important: There have been many reports that, with some motherboards

818

Important: There have been many reports that, with some motherboards

819

mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,

819

mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,

820

such as some BusLogic models) causes corruption problems with many

820

such as some BusLogic models) causes corruption problems with many

821

operating systems. The Linux smc-ultra driver has a work-around for

821

operating systems. The Linux smc-ultra driver has a work-around for

822

this but keep it in mind if you have such a SCSI card and have

822

this but keep it in mind if you have such a SCSI card and have

823

problems.

823

problems.

824

825

To compile this driver as a module, choose M here. The module

825

To compile this driver as a module, choose M here. The module

826

will be called smc-ultra.

826

will be called smc-ultra.

827

828

config ULTRA32

828

config ULTRA32

829

tristate "SMC Ultra32 EISA support"

829

tristate "SMC Ultra32 EISA support"

830

depends on NET_VENDOR_SMC && EISA

830

depends on NET_VENDOR_SMC && EISA

831

select CRC32

831

select CRC32

832

help

832

help

833

If you have a network (Ethernet) card of this type, say Y and read

833

If you have a network (Ethernet) card of this type, say Y and read

834

the Ethernet-HOWTO, available from

834

the Ethernet-HOWTO, available from

835

<http://www.tldp.org/docs.html#howto>.

835

<http://www.tldp.org/docs.html#howto>.

836

837

To compile this driver as a module, choose M here. The module

837

To compile this driver as a module, choose M here. The module

838

will be called smc-ultra32.

838

will be called smc-ultra32.

839

840

config BFIN_MAC

840

config BFIN_MAC

841

tristate "Blackfin 527/536/537 on-chip mac support"

841

tristate "Blackfin 527/536/537 on-chip mac support"

842

depends on NET_ETHERNET && (BF527 || BF537 || BF536)

842

depends on NET_ETHERNET && (BF527 || BF537 || BF536)

843

select CRC32

843

select CRC32

844

select MII

844

select MII

845

select PHYLIB

845

select PHYLIB

846

select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE

846

select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE

847

help

847

help

848

This is the driver for blackfin on-chip mac device. Say Y if you want it

848

This is the driver for blackfin on-chip mac device. Say Y if you want it

849

compiled into the kernel. This driver is also available as a module

849

compiled into the kernel. This driver is also available as a module

850

( = code which can be inserted in and removed from the running kernel

850

( = code which can be inserted in and removed from the running kernel

851

whenever you want). The module will be called bfin_mac.

851

whenever you want). The module will be called bfin_mac.

852

853

config BFIN_MAC_USE_L1

853

config BFIN_MAC_USE_L1

854

bool "Use L1 memory for rx/tx packets"

854

bool "Use L1 memory for rx/tx packets"

855

depends on BFIN_MAC && (BF527 || BF537)

855

depends on BFIN_MAC && (BF527 || BF537)

856

default y

856

default y

857

help

857

help

858

To get maximum network performance, you should use L1 memory as rx/tx buffers.

858

To get maximum network performance, you should use L1 memory as rx/tx buffers.

859

Say N here if you want to reserve L1 memory for other uses.

859

Say N here if you want to reserve L1 memory for other uses.

860

861

config BFIN_TX_DESC_NUM

861

config BFIN_TX_DESC_NUM

862

int "Number of transmit buffer packets"

862

int "Number of transmit buffer packets"

863

depends on BFIN_MAC

863

depends on BFIN_MAC

864

range 6 10 if BFIN_MAC_USE_L1

864

range 6 10 if BFIN_MAC_USE_L1

865

range 10 100

865

range 10 100

866

default "10"

866

default "10"

867

help

867

help

868

Set the number of buffer packets used in driver.

868

Set the number of buffer packets used in driver.

869

870

config BFIN_RX_DESC_NUM

870

config BFIN_RX_DESC_NUM

871

int "Number of receive buffer packets"

871

int "Number of receive buffer packets"

872

depends on BFIN_MAC

872

depends on BFIN_MAC

873

range 20 100 if BFIN_MAC_USE_L1

873

range 20 100 if BFIN_MAC_USE_L1

874

range 20 800

874

range 20 800

875

default "20"

875

default "20"

876

help

876

help

877

Set the number of buffer packets used in driver.

877

Set the number of buffer packets used in driver.

878

879

config BFIN_MAC_RMII

879

config BFIN_MAC_RMII

880

bool "RMII PHY Interface (EXPERIMENTAL)"

880

bool "RMII PHY Interface (EXPERIMENTAL)"

881

depends on BFIN_MAC && EXPERIMENTAL

881

depends on BFIN_MAC && EXPERIMENTAL

882

default y if BFIN527_EZKIT

882

default y if BFIN527_EZKIT

883

default n if BFIN537_STAMP

883

default n if BFIN537_STAMP

884

help

884

help

885

Use Reduced PHY MII Interface

885

Use Reduced PHY MII Interface

886

887

config SMC9194

887

config SMC9194

888

tristate "SMC 9194 support"

888

tristate "SMC 9194 support"

889

depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)

889

depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)

890

select CRC32

890

select CRC32

891

---help---

891

---help---

892

This is support for the SMC9xxx based Ethernet cards. Choose this

892

This is support for the SMC9xxx based Ethernet cards. Choose this

893

option if you have a DELL laptop with the docking station, or

893

option if you have a DELL laptop with the docking station, or

894

another SMC9192/9194 based chipset. Say Y if you want it compiled

894

another SMC9192/9194 based chipset. Say Y if you want it compiled

895

into the kernel, and read the file

895

into the kernel, and read the file

896

<file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,

896

<file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,

897

available from <http://www.tldp.org/docs.html#howto>.

897

available from <http://www.tldp.org/docs.html#howto>.

898

899

To compile this driver as a module, choose M here. The module

899

To compile this driver as a module, choose M here. The module

900

will be called smc9194.

900

will be called smc9194.

901

902

config SMC91X

902

config SMC91X

903

tristate "SMC 91C9x/91C1xxx support"

903

tristate "SMC 91C9x/91C1xxx support"

904

select CRC32

904

select CRC32

905

select MII

905

select MII

906

depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \

906

depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \

907

SOC_AU1X00 || BLACKFIN || MN10300

907

SOC_AU1X00 || BLACKFIN || MN10300

908

help

908

help

909

This is a driver for SMC's 91x series of Ethernet chipsets,

909

This is a driver for SMC's 91x series of Ethernet chipsets,

910

including the SMC91C94 and the SMC91C111. Say Y if you want it

910

including the SMC91C94 and the SMC91C111. Say Y if you want it

911

compiled into the kernel, and read the file

911

compiled into the kernel, and read the file

912

<file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,

912

<file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,

913

available from <http://www.linuxdoc.org/docs.html#howto>.

913

available from <http://www.linuxdoc.org/docs.html#howto>.

914

915

This driver is also available as a module ( = code which can be

915

This driver is also available as a module ( = code which can be

916

inserted in and removed from the running kernel whenever you want).

916

inserted in and removed from the running kernel whenever you want).

917

The module will be called smc91x. If you want to compile it as a

917

The module will be called smc91x. If you want to compile it as a

918

module, say M here and read <file:Documentation/kbuild/modules.txt>.

918

module, say M here and read <file:Documentation/kbuild/modules.txt>.

919

920

config NET_NETX

920

config NET_NETX

921

tristate "NetX Ethernet support"

921

tristate "NetX Ethernet support"

922

select MII

922

select MII

923

depends on ARCH_NETX

923

depends on ARCH_NETX

924

help

924

help

925

This is support for the Hilscher netX builtin Ethernet ports

925

This is support for the Hilscher netX builtin Ethernet ports

926

927

To compile this driver as a module, choose M here. The module

927

To compile this driver as a module, choose M here. The module

928

will be called netx-eth.

928

will be called netx-eth.

929

930

config DM9000

930

config DM9000

931

tristate "DM9000 support"

931

tristate "DM9000 support"

932

depends on ARM || BLACKFIN || MIPS

932

depends on ARM || BLACKFIN || MIPS

933

select CRC32

933

select CRC32

934

select MII

934

select MII

935

---help---

935

---help---

936

Support for DM9000 chipset.

936

Support for DM9000 chipset.

937

938

To compile this driver as a module, choose M here. The module

938

To compile this driver as a module, choose M here. The module

939

will be called dm9000.

939

will be called dm9000.

940

941

config DM9000_DEBUGLEVEL

941

config DM9000_DEBUGLEVEL

942

int "DM9000 maximum debug level"

942

int "DM9000 maximum debug level"

943

depends on DM9000

943

depends on DM9000

944

default 4

944

default 4

945

help

945

help

946

The maximum level of debugging code compiled into the DM9000

946

The maximum level of debugging code compiled into the DM9000

947

driver.

947

driver.

948

949

config DM9000_FORCE_SIMPLE_PHY_POLL

949

config DM9000_FORCE_SIMPLE_PHY_POLL

950

bool "Force simple NSR based PHY polling"

950

bool "Force simple NSR based PHY polling"

951

depends on DM9000

951

depends on DM9000

952

---help---

952

---help---

953

This configuration forces the DM9000 to use the NSR's LinkStatus

953

This configuration forces the DM9000 to use the NSR's LinkStatus

954

bit to determine if the link is up or down instead of the more

954

bit to determine if the link is up or down instead of the more

955

costly MII PHY reads. Note, this will not work if the chip is

955

costly MII PHY reads. Note, this will not work if the chip is

956

operating with an external PHY.

956

operating with an external PHY.

957

958

config ENC28J60

958

config ENC28J60

959

tristate "ENC28J60 support"

959

tristate "ENC28J60 support"

960

depends on EXPERIMENTAL && SPI && NET_ETHERNET

960

depends on EXPERIMENTAL && SPI && NET_ETHERNET

961

select CRC32

961

select CRC32

962

---help---

962

---help---

963

Support for the Microchip EN28J60 ethernet chip.

963

Support for the Microchip EN28J60 ethernet chip.

964

965

To compile this driver as a module, choose M here. The module will be

965

To compile this driver as a module, choose M here. The module will be

966

called enc28j60.

966

called enc28j60.

967

968

config ENC28J60_WRITEVERIFY

968

config ENC28J60_WRITEVERIFY

969

bool "Enable write verify"

969

bool "Enable write verify"

970

depends on ENC28J60

970

depends on ENC28J60

971

---help---

971

---help---

972

Enable the verify after the buffer write useful for debugging purpose.

972

Enable the verify after the buffer write useful for debugging purpose.

973

If unsure, say N.

973

If unsure, say N.

974

975

config SMC911X

975

config SMC911X

976

tristate "SMSC LAN911[5678] support"

976

tristate "SMSC LAN911[5678] support"

977

select CRC32

977

select CRC32

978

select MII

978

select MII

979

depends on ARCH_PXA || SUPERH

979

depends on ARCH_PXA || SUPERH

980

help

980

help

981

This is a driver for SMSC's LAN911x series of Ethernet chipsets

981

This is a driver for SMSC's LAN911x series of Ethernet chipsets

982

including the new LAN9115, LAN9116, LAN9117, and LAN9118.

982

including the new LAN9115, LAN9116, LAN9117, and LAN9118.

983

Say Y if you want it compiled into the kernel,

983

Say Y if you want it compiled into the kernel,

984

and read the Ethernet-HOWTO, available from

984

and read the Ethernet-HOWTO, available from

985

<http://www.linuxdoc.org/docs.html#howto>.

985

<http://www.linuxdoc.org/docs.html#howto>.

986

987

This driver is also available as a module. The module will be

987

This driver is also available as a module. The module will be

988

called smc911x. If you want to compile it as a module, say M

988

called smc911x. If you want to compile it as a module, say M

989

here and read <file:Documentation/kbuild/modules.txt>

989

here and read <file:Documentation/kbuild/modules.txt>

990

991

config NET_VENDOR_RACAL

991

config NET_VENDOR_RACAL

992

bool "Racal-Interlan (Micom) NI cards"

992

bool "Racal-Interlan (Micom) NI cards"

993

depends on ISA

993

depends on ISA

994

help

994

help

995

If you have a network (Ethernet) card belonging to this class, such

995

If you have a network (Ethernet) card belonging to this class, such

996

as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,

996

as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,

997

available from <http://www.tldp.org/docs.html#howto>.

997

available from <http://www.tldp.org/docs.html#howto>.

998

999

Note that the answer to this question doesn't directly affect the

999

Note that the answer to this question doesn't directly affect the

1000

kernel: saying N will just cause the configurator to skip all

1000

kernel: saying N will just cause the configurator to skip all

1001

the questions about NI cards. If you say Y, you will be asked for

1001

the questions about NI cards. If you say Y, you will be asked for

1002

your specific card in the following questions.

1002

your specific card in the following questions.

1003

1004

config NI5010

1004

config NI5010

1005

tristate "NI5010 support (EXPERIMENTAL)"

1005

tristate "NI5010 support (EXPERIMENTAL)"

1006

depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP

1006

depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP

1007

---help---

1007

---help---

1008

If you have a network (Ethernet) card of this type, say Y and read

1008

If you have a network (Ethernet) card of this type, say Y and read

1009

the Ethernet-HOWTO, available from

1009

the Ethernet-HOWTO, available from

1010

<http://www.tldp.org/docs.html#howto>. Note that this is still

1010

<http://www.tldp.org/docs.html#howto>. Note that this is still

1011

experimental code.

1011

experimental code.

1012

1013

To compile this driver as a module, choose M here. The module

1013

To compile this driver as a module, choose M here. The module

1014

will be called ni5010.

1014

will be called ni5010.

1015

1016

config NI52

1016

config NI52

1017

tristate "NI5210 support"

1017

tristate "NI5210 support"

1018

depends on NET_VENDOR_RACAL && ISA

1018

depends on NET_VENDOR_RACAL && ISA

1019

help

1019

help

1020

If you have a network (Ethernet) card of this type, say Y and read

1020

If you have a network (Ethernet) card of this type, say Y and read

1021

the Ethernet-HOWTO, available from

1021

the Ethernet-HOWTO, available from

1022

<http://www.tldp.org/docs.html#howto>.

1022

<http://www.tldp.org/docs.html#howto>.

1023

1024

To compile this driver as a module, choose M here. The module

1024

To compile this driver as a module, choose M here. The module

1025

will be called ni52.

1025

will be called ni52.

1026

1027

config NI65

1027

config NI65

1028

tristate "NI6510 support"

1028

tristate "NI6510 support"

1029

depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API

1029

depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API

1030

help

1030

help

1031

If you have a network (Ethernet) card of this type, say Y and read

1031

If you have a network (Ethernet) card of this type, say Y and read

1032

the Ethernet-HOWTO, available from

1032

the Ethernet-HOWTO, available from

1033

<http://www.tldp.org/docs.html#howto>.

1033

<http://www.tldp.org/docs.html#howto>.

1034

1035

To compile this driver as a module, choose M here. The module

1035

To compile this driver as a module, choose M here. The module

1036

will be called ni65.

1036

will be called ni65.

1037

1038

source "drivers/net/tulip/Kconfig"

1038

source "drivers/net/tulip/Kconfig"

1039

1040

config AT1700

1040

config AT1700

1041

tristate "AT1700/1720 support (EXPERIMENTAL)"

1041

tristate "AT1700/1720 support (EXPERIMENTAL)"

1042

depends on (ISA || MCA_LEGACY) && EXPERIMENTAL

1042

depends on (ISA || MCA_LEGACY) && EXPERIMENTAL

1043

select CRC32

1043

select CRC32

1044

---help---

1044

---help---

1045

If you have a network (Ethernet) card of this type, say Y and read

1045

If you have a network (Ethernet) card of this type, say Y and read

1046

the Ethernet-HOWTO, available from

1046

the Ethernet-HOWTO, available from

1047

<http://www.tldp.org/docs.html#howto>.

1047

<http://www.tldp.org/docs.html#howto>.

1048

1049

To compile this driver as a module, choose M here. The module

1049

To compile this driver as a module, choose M here. The module

1050

will be called at1700.

1050

will be called at1700.

1051

1052

config DEPCA

1052

config DEPCA

1053

tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"

1053

tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"

1054

depends on ISA || EISA || MCA

1054

depends on ISA || EISA || MCA

1055

select CRC32

1055

select CRC32

1056

---help---

1056

---help---

1057

If you have a network (Ethernet) card of this type, say Y and read

1057

If you have a network (Ethernet) card of this type, say Y and read

1058

the Ethernet-HOWTO, available from

1058

the Ethernet-HOWTO, available from

1059

<http://www.tldp.org/docs.html#howto> as well as

1059

<http://www.tldp.org/docs.html#howto> as well as

1060

<file:drivers/net/depca.c>.

1060

<file:drivers/net/depca.c>.

1061

1062

To compile this driver as a module, choose M here. The module

1062

To compile this driver as a module, choose M here. The module

1063

will be called depca.

1063

will be called depca.

1064

1065

config HP100

1065

config HP100

1066

tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"

1066

tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"

1067

depends on ISA || EISA || PCI

1067

depends on ISA || EISA || PCI

1068

help

1068

help

1069

If you have a network (Ethernet) card of this type, say Y and read

1069

If you have a network (Ethernet) card of this type, say Y and read

1070

the Ethernet-HOWTO, available from

1070

the Ethernet-HOWTO, available from

1071

<http://www.tldp.org/docs.html#howto>.

1071

<http://www.tldp.org/docs.html#howto>.

1072

1073

To compile this driver as a module, choose M here. The module

1073

To compile this driver as a module, choose M here. The module

1074

will be called hp100.

1074

will be called hp100.

1075

1076

config NET_ISA

1076

config NET_ISA

1077

bool "Other ISA cards"

1077

bool "Other ISA cards"

1078

depends on ISA

1078

depends on ISA

1079

---help---

1079

---help---

1080

If your network (Ethernet) card hasn't been mentioned yet and its

1080

If your network (Ethernet) card hasn't been mentioned yet and its

1081

bus system (that's the way the cards talks to the other components

1081

bus system (that's the way the cards talks to the other components

1082

of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.

1082

of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.

1083

Make sure you know the name of your card. Read the Ethernet-HOWTO,

1083

Make sure you know the name of your card. Read the Ethernet-HOWTO,

1084

available from <http://www.tldp.org/docs.html#howto>.

1084

available from <http://www.tldp.org/docs.html#howto>.

1085

1086

If unsure, say Y.

1086

If unsure, say Y.

1087

1088

Note that the answer to this question doesn't directly affect the

1088

Note that the answer to this question doesn't directly affect the

1089

kernel: saying N will just cause the configurator to skip all

1089

kernel: saying N will just cause the configurator to skip all

1090

the remaining ISA network card questions. If you say Y, you will be

1090

the remaining ISA network card questions. If you say Y, you will be

1091

asked for your specific card in the following questions.

1091

asked for your specific card in the following questions.

1092

1093

config E2100

1093

config E2100

1094

tristate "Cabletron E21xx support"

1094

tristate "Cabletron E21xx support"

1095

depends on NET_ISA

1095

depends on NET_ISA

1096

select CRC32

1096

select CRC32

1097

help

1097

help

1098

If you have a network (Ethernet) card of this type, say Y and read

1098

If you have a network (Ethernet) card of this type, say Y and read

1099

the Ethernet-HOWTO, available from

1099

the Ethernet-HOWTO, available from

1100

<http://www.tldp.org/docs.html#howto>.

1100

<http://www.tldp.org/docs.html#howto>.

1101

1102

To compile this driver as a module, choose M here. The module

1102

To compile this driver as a module, choose M here. The module

1103

will be called e2100.

1103

will be called e2100.

1104

1105

config EWRK3

1105

config EWRK3

1106

tristate "EtherWORKS 3 (DE203, DE204, DE205) support"

1106

tristate "EtherWORKS 3 (DE203, DE204, DE205) support"

1107

depends on NET_ISA

1107

depends on NET_ISA

1108

select CRC32

1108

select CRC32

1109

---help---

1109

---help---

1110

This driver supports the DE203, DE204 and DE205 network (Ethernet)

1110

This driver supports the DE203, DE204 and DE205 network (Ethernet)

1111

cards. If this is for you, say Y and read

1111

cards. If this is for you, say Y and read

1112

<file:Documentation/networking/ewrk3.txt> in the kernel source as

1112

<file:Documentation/networking/ewrk3.txt> in the kernel source as

1113

well as the Ethernet-HOWTO, available from

1113

well as the Ethernet-HOWTO, available from

1114

<http://www.tldp.org/docs.html#howto>.

1114

<http://www.tldp.org/docs.html#howto>.

1115

1116

To compile this driver as a module, choose M here. The module

1116

To compile this driver as a module, choose M here. The module

1117

will be called ewrk3.

1117

will be called ewrk3.

1118

1119

config EEXPRESS

1119

config EEXPRESS

1120

tristate "EtherExpress 16 support"

1120

tristate "EtherExpress 16 support"

1121

depends on NET_ISA

1121

depends on NET_ISA

1122

---help---

1122

---help---

1123

If you have an EtherExpress16 network (Ethernet) card, say Y and

1123

If you have an EtherExpress16 network (Ethernet) card, say Y and

1124

read the Ethernet-HOWTO, available from

1124

read the Ethernet-HOWTO, available from

1125

<http://www.tldp.org/docs.html#howto>. Note that the Intel

1125

<http://www.tldp.org/docs.html#howto>. Note that the Intel

1126

EtherExpress16 card used to be regarded as a very poor choice

1126

EtherExpress16 card used to be regarded as a very poor choice

1127

because the driver was very unreliable. We now have a new driver

1127

because the driver was very unreliable. We now have a new driver

1128

that should do better.

1128

that should do better.

1129

1130

To compile this driver as a module, choose M here. The module

1130

To compile this driver as a module, choose M here. The module

1131

will be called eexpress.

1131

will be called eexpress.

1132

1133

config EEXPRESS_PRO

1133

config EEXPRESS_PRO

1134

tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"

1134

tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"

1135

depends on NET_ISA

1135

depends on NET_ISA

1136

---help---

1136

---help---

1137

If you have a network (Ethernet) card of this type, say Y. This

1137

If you have a network (Ethernet) card of this type, say Y. This

1138

driver supports Intel i82595{FX,TX} based boards. Note however

1138

driver supports Intel i82595{FX,TX} based boards. Note however

1139

that the EtherExpress PRO/100 Ethernet card has its own separate

1139

that the EtherExpress PRO/100 Ethernet card has its own separate

1140

driver. Please read the Ethernet-HOWTO, available from

1140

driver. Please read the Ethernet-HOWTO, available from

1141

<http://www.tldp.org/docs.html#howto>.

1141

<http://www.tldp.org/docs.html#howto>.

1142

1143

To compile this driver as a module, choose M here. The module

1143

To compile this driver as a module, choose M here. The module

1144

will be called eepro.

1144

will be called eepro.

1145

1146

config HPLAN_PLUS

1146

config HPLAN_PLUS

1147

tristate "HP PCLAN+ (27247B and 27252A) support"

1147

tristate "HP PCLAN+ (27247B and 27252A) support"

1148

depends on NET_ISA

1148

depends on NET_ISA

1149

select CRC32

1149

select CRC32

1150

help

1150

help

1151

If you have a network (Ethernet) card of this type, say Y and read

1151

If you have a network (Ethernet) card of this type, say Y and read

1152

the Ethernet-HOWTO, available from

1152

the Ethernet-HOWTO, available from

1153

<http://www.tldp.org/docs.html#howto>.

1153

<http://www.tldp.org/docs.html#howto>.

1154

1155

To compile this driver as a module, choose M here. The module

1155

To compile this driver as a module, choose M here. The module

1156

will be called hp-plus.

1156

will be called hp-plus.

1157

1158

config HPLAN

1158

config HPLAN

1159

tristate "HP PCLAN (27245 and other 27xxx series) support"

1159

tristate "HP PCLAN (27245 and other 27xxx series) support"

1160

depends on NET_ISA

1160

depends on NET_ISA

1161

select CRC32

1161

select CRC32

1162

help

1162

help

1163

If you have a network (Ethernet) card of this type, say Y and read

1163

If you have a network (Ethernet) card of this type, say Y and read

1164

the Ethernet-HOWTO, available from

1164

the Ethernet-HOWTO, available from

1165

<http://www.tldp.org/docs.html#howto>.

1165

<http://www.tldp.org/docs.html#howto>.

1166

1167

To compile this driver as a module, choose M here. The module

1167

To compile this driver as a module, choose M here. The module

1168

will be called hp.

1168

will be called hp.

1169

1170

config LP486E

1170

config LP486E

1171

tristate "LP486E on board Ethernet"

1171

tristate "LP486E on board Ethernet"

1172

depends on NET_ISA

1172

depends on NET_ISA

1173

help

1173

help

1174

Say Y here to support the 82596-based on-board Ethernet controller

1174

Say Y here to support the 82596-based on-board Ethernet controller

1175

for the Panther motherboard, which is one of the two shipped in the

1175

for the Panther motherboard, which is one of the two shipped in the

1176

Intel Professional Workstation.

1176

Intel Professional Workstation.

1177

1178

config ETH16I

1178

config ETH16I

1179

tristate "ICL EtherTeam 16i/32 support"

1179

tristate "ICL EtherTeam 16i/32 support"

1180

depends on NET_ISA

1180

depends on NET_ISA

1181

help

1181

help

1182

If you have a network (Ethernet) card of this type, say Y and read

1182

If you have a network (Ethernet) card of this type, say Y and read

1183

the Ethernet-HOWTO, available from

1183

the Ethernet-HOWTO, available from

1184

<http://www.tldp.org/docs.html#howto>.

1184

<http://www.tldp.org/docs.html#howto>.

1185

1186

To compile this driver as a module, choose M here. The module

1186

To compile this driver as a module, choose M here. The module

1187

will be called eth16i.

1187

will be called eth16i.

1188

1189

config NE2000

1189

config NE2000

1190

tristate "NE2000/NE1000 support"

1190

tristate "NE2000/NE1000 support"

1191

depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938

1191

depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938

1192

select CRC32

1192

select CRC32

1193

---help---

1193

---help---

1194

If you have a network (Ethernet) card of this type, say Y and read

1194

If you have a network (Ethernet) card of this type, say Y and read

1195

the Ethernet-HOWTO, available from

1195

the Ethernet-HOWTO, available from

1196

<http://www.tldp.org/docs.html#howto>. Many Ethernet cards

1196

<http://www.tldp.org/docs.html#howto>. Many Ethernet cards

1197

without a specific driver are compatible with NE2000.

1197

without a specific driver are compatible with NE2000.

1198

1199

If you have a PCI NE2000 card however, say N here and Y to "PCI

1199

If you have a PCI NE2000 card however, say N here and Y to "PCI

1200

NE2000 and clone support" under "EISA, VLB, PCI and on board

1200

NE2000 and clone support" under "EISA, VLB, PCI and on board

1201

controllers" below. If you have a NE2000 card and are running on

1201

controllers" below. If you have a NE2000 card and are running on

1202

an MCA system (a bus system used on some IBM PS/2 computers and

1202

an MCA system (a bus system used on some IBM PS/2 computers and

1203

laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",

1203

laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",

1204

below.

1204

below.

1205

1206

To compile this driver as a module, choose M here. The module

1206

To compile this driver as a module, choose M here. The module

1207

will be called ne.

1207

will be called ne.

1208

1209

config ZNET

1209

config ZNET

1210

tristate "Zenith Z-Note support (EXPERIMENTAL)"

1210

tristate "Zenith Z-Note support (EXPERIMENTAL)"

1211

depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API

1211

depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API

1212

help

1212

help

1213

The Zenith Z-Note notebook computer has a built-in network

1213

The Zenith Z-Note notebook computer has a built-in network

1214

(Ethernet) card, and this is the Linux driver for it. Note that the

1214

(Ethernet) card, and this is the Linux driver for it. Note that the

1215

IBM Thinkpad 300 is compatible with the Z-Note and is also supported

1215

IBM Thinkpad 300 is compatible with the Z-Note and is also supported

1216

by this driver. Read the Ethernet-HOWTO, available from

1216

by this driver. Read the Ethernet-HOWTO, available from

1217

<http://www.tldp.org/docs.html#howto>.

1217

<http://www.tldp.org/docs.html#howto>.

1218

1219

config SEEQ8005

1219

config SEEQ8005

1220

tristate "SEEQ8005 support (EXPERIMENTAL)"

1220

tristate "SEEQ8005 support (EXPERIMENTAL)"

1221

depends on NET_ISA && EXPERIMENTAL

1221

depends on NET_ISA && EXPERIMENTAL

1222

help

1222

help

1223

This is a driver for the SEEQ 8005 network (Ethernet) card. If this

1223

This is a driver for the SEEQ 8005 network (Ethernet) card. If this

1224

is for you, read the Ethernet-HOWTO, available from

1224

is for you, read the Ethernet-HOWTO, available from

1225

<http://www.tldp.org/docs.html#howto>.

1225

<http://www.tldp.org/docs.html#howto>.

1226

1227

To compile this driver as a module, choose M here. The module

1227

To compile this driver as a module, choose M here. The module

1228

will be called seeq8005.

1228

will be called seeq8005.

1229

1230

config NE2_MCA

1230

config NE2_MCA

1231

tristate "NE/2 (ne2000 MCA version) support"

1231

tristate "NE/2 (ne2000 MCA version) support"

1232

depends on MCA_LEGACY

1232

depends on MCA_LEGACY

1233

select CRC32

1233

select CRC32

1234

help

1234

help

1235

If you have a network (Ethernet) card of this type, say Y and read

1235

If you have a network (Ethernet) card of this type, say Y and read

1236

the Ethernet-HOWTO, available from

1236

the Ethernet-HOWTO, available from

1237

<http://www.tldp.org/docs.html#howto>.

1237

<http://www.tldp.org/docs.html#howto>.

1238

1239

To compile this driver as a module, choose M here. The module

1239

To compile this driver as a module, choose M here. The module

1240

will be called ne2.

1240

will be called ne2.

1241

1242

config IBMLANA

1242

config IBMLANA

1243

tristate "IBM LAN Adapter/A support"

1243

tristate "IBM LAN Adapter/A support"

1244

depends on MCA

1244

depends on MCA

1245

---help---

1245

---help---

1246

This is a Micro Channel Ethernet adapter. You need to set

1246

This is a Micro Channel Ethernet adapter. You need to set

1247

CONFIG_MCA to use this driver. It is both available as an in-kernel

1247

CONFIG_MCA to use this driver. It is both available as an in-kernel

1248

driver and as a module.

1248

driver and as a module.

1249

1250

To compile this driver as a module, choose M here. The only

1250

To compile this driver as a module, choose M here. The only

1251

currently supported card is the IBM LAN Adapter/A for Ethernet. It

1251

currently supported card is the IBM LAN Adapter/A for Ethernet. It

1252

will both support 16K and 32K memory windows, however a 32K window

1252

will both support 16K and 32K memory windows, however a 32K window

1253

gives a better security against packet losses. Usage of multiple

1253

gives a better security against packet losses. Usage of multiple

1254

boards with this driver should be possible, but has not been tested

1254

boards with this driver should be possible, but has not been tested

1255

up to now due to lack of hardware.

1255

up to now due to lack of hardware.

1256

1257

config IBMVETH

1257

config IBMVETH

1258

tristate "IBM LAN Virtual Ethernet support"

1258

tristate "IBM LAN Virtual Ethernet support"

1259

depends on PPC_PSERIES

1259

depends on PPC_PSERIES

1260

---help---

1260

---help---

1261

This driver supports virtual ethernet adapters on newer IBM iSeries

1261

This driver supports virtual ethernet adapters on newer IBM iSeries

1262

and pSeries systems.

1262

and pSeries systems.

1263

1264

To compile this driver as a module, choose M here. The module will

1264

To compile this driver as a module, choose M here. The module will

1265

be called ibmveth.

1265

be called ibmveth.

1266

1267

source "drivers/net/ibm_newemac/Kconfig"

1267

source "drivers/net/ibm_newemac/Kconfig"

1268

1269

config NET_PCI

1269

config NET_PCI

1270

bool "EISA, VLB, PCI and on board controllers"

1270

bool "EISA, VLB, PCI and on board controllers"

1271

depends on ISA || EISA || PCI

1271

depends on ISA || EISA || PCI

1272

help

1272

help

1273

This is another class of network cards which attach directly to the

1273

This is another class of network cards which attach directly to the

1274

bus. If you have one of those, say Y and read the Ethernet-HOWTO,

1274

bus. If you have one of those, say Y and read the Ethernet-HOWTO,

1275

available from <http://www.tldp.org/docs.html#howto>.

1275

available from <http://www.tldp.org/docs.html#howto>.

1276

1277

Note that the answer to this question doesn't directly affect the

1277

Note that the answer to this question doesn't directly affect the

1278

kernel: saying N will just cause the configurator to skip all

1278

kernel: saying N will just cause the configurator to skip all

1279

the questions about this class of network cards. If you say Y, you

1279

the questions about this class of network cards. If you say Y, you

1280

will be asked for your specific card in the following questions. If

1280

will be asked for your specific card in the following questions. If

1281

you are unsure, say Y.

1281

you are unsure, say Y.

1282

1283

config PCNET32

1283

config PCNET32

1284

tristate "AMD PCnet32 PCI support"

1284

tristate "AMD PCnet32 PCI support"

1285

depends on NET_PCI && PCI

1285

depends on NET_PCI && PCI

1286

select CRC32

1286

select CRC32

1287

select MII

1287

select MII

1288

help

1288

help

1289

If you have a PCnet32 or PCnetPCI based network (Ethernet) card,

1289

If you have a PCnet32 or PCnetPCI based network (Ethernet) card,

1290

answer Y here and read the Ethernet-HOWTO, available from

1290

answer Y here and read the Ethernet-HOWTO, available from

1291

<http://www.tldp.org/docs.html#howto>.

1291

<http://www.tldp.org/docs.html#howto>.

1292

1293

To compile this driver as a module, choose M here. The module

1293

To compile this driver as a module, choose M here. The module

1294

will be called pcnet32.

1294

will be called pcnet32.

1295

1296

config AMD8111_ETH

1296

config AMD8111_ETH

1297

tristate "AMD 8111 (new PCI lance) support"

1297

tristate "AMD 8111 (new PCI lance) support"

1298

depends on NET_PCI && PCI

1298

depends on NET_PCI && PCI

1299

select CRC32

1299

select CRC32

1300

select MII

1300

select MII

1301

help

1301

help

1302

If you have an AMD 8111-based PCI lance ethernet card,

1302

If you have an AMD 8111-based PCI lance ethernet card,

1303

answer Y here and read the Ethernet-HOWTO, available from

1303

answer Y here and read the Ethernet-HOWTO, available from

1304

<http://www.tldp.org/docs.html#howto>.

1304

<http://www.tldp.org/docs.html#howto>.

1305

1306

To compile this driver as a module, choose M here. The module

1306

To compile this driver as a module, choose M here. The module

1307

will be called amd8111e.

1307

will be called amd8111e.

1308

1309

config AMD8111E_NAPI

1309

config AMD8111E_NAPI

1310

bool "Use RX polling (NAPI)"

1310

bool "Use RX polling (NAPI)"

1311

depends on AMD8111_ETH

1311

depends on AMD8111_ETH

1312

help

1312

help

1313

NAPI is a new driver API designed to reduce CPU and interrupt load

1313

NAPI is a new driver API designed to reduce CPU and interrupt load

1314

when the driver is receiving lots of packets from the card. It is

1314

when the driver is receiving lots of packets from the card. It is

1315

still somewhat experimental and thus not yet enabled by default.

1315

still somewhat experimental and thus not yet enabled by default.

1316

1317

If your estimated Rx load is 10kpps or more, or if the card will be

1317

If your estimated Rx load is 10kpps or more, or if the card will be

1318

deployed on potentially unfriendly networks (e.g. in a firewall),

1318

deployed on potentially unfriendly networks (e.g. in a firewall),

1319

then say Y here.

1319

then say Y here.

1320

1321

If in doubt, say N.

1321

If in doubt, say N.

1322

1323

config ADAPTEC_STARFIRE

1323

config ADAPTEC_STARFIRE

1324

tristate "Adaptec Starfire/DuraLAN support"

1324

tristate "Adaptec Starfire/DuraLAN support"

1325

depends on NET_PCI && PCI

1325

depends on NET_PCI && PCI

1326

select CRC32

1326

select CRC32

1327

select MII

1327

select MII

1328

help

1328

help

1329

Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network

1329

Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network

1330

adapter. The DuraLAN chip is used on the 64 bit PCI boards from

1330

adapter. The DuraLAN chip is used on the 64 bit PCI boards from

1331

Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip

1331

Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip

1332

driver.

1332

driver.

1333

1334

To compile this driver as a module, choose M here: the module

1334

To compile this driver as a module, choose M here: the module

1335

will be called starfire. This is recommended.

1335

will be called starfire. This is recommended.

1336

1337

config ADAPTEC_STARFIRE_NAPI

1337

config ADAPTEC_STARFIRE_NAPI

1338

bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"

1338

bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"

1339

depends on ADAPTEC_STARFIRE && EXPERIMENTAL

1339

depends on ADAPTEC_STARFIRE && EXPERIMENTAL

1340

help

1340

help

1341

NAPI is a new driver API designed to reduce CPU and interrupt load

1341

NAPI is a new driver API designed to reduce CPU and interrupt load

1342

when the driver is receiving lots of packets from the card. It is

1342

when the driver is receiving lots of packets from the card. It is

1343

still somewhat experimental and thus not yet enabled by default.

1343

still somewhat experimental and thus not yet enabled by default.

1344

1345

If your estimated Rx load is 10kpps or more, or if the card will be

1345

If your estimated Rx load is 10kpps or more, or if the card will be

1346

deployed on potentially unfriendly networks (e.g. in a firewall),

1346

deployed on potentially unfriendly networks (e.g. in a firewall),

1347

then say Y here.

1347

then say Y here.

1348

1349

If in doubt, say N.

1349

If in doubt, say N.

1350

1351

config AC3200

1351

config AC3200

1352

tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"

1352

tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"

1353

depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL

1353

depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL

1354

select CRC32

1354

select CRC32

1355

help

1355

help

1356

If you have a network (Ethernet) card of this type, say Y and read

1356

If you have a network (Ethernet) card of this type, say Y and read

1357

the Ethernet-HOWTO, available from

1357

the Ethernet-HOWTO, available from

1358

<http://www.tldp.org/docs.html#howto>.

1358

<http://www.tldp.org/docs.html#howto>.

1359

1360

To compile this driver as a module, choose M here. The module

1360

To compile this driver as a module, choose M here. The module

1361

will be called ac3200.

1361

will be called ac3200.

1362

1363

config APRICOT

1363

config APRICOT

1364

tristate "Apricot Xen-II on board Ethernet"

1364

tristate "Apricot Xen-II on board Ethernet"

1365

depends on NET_PCI && ISA

1365

depends on NET_PCI && ISA

1366

help

1366

help

1367

If you have a network (Ethernet) controller of this type, say Y and

1367

If you have a network (Ethernet) controller of this type, say Y and

1368

read the Ethernet-HOWTO, available from

1368

read the Ethernet-HOWTO, available from

1369

<http://www.tldp.org/docs.html#howto>.

1369

<http://www.tldp.org/docs.html#howto>.

1370

1371

To compile this driver as a module, choose M here. The module

1371

To compile this driver as a module, choose M here. The module

1372

will be called apricot.

1372

will be called apricot.

1373

1374

config B44

1374

config B44

1375

tristate "Broadcom 440x/47xx ethernet support"

1375

tristate "Broadcom 440x/47xx ethernet support"

1376

depends on SSB_POSSIBLE && HAS_DMA

1376

depends on SSB_POSSIBLE && HAS_DMA

1377

select SSB

1377

select SSB

1378

select MII

1378

select MII

1379

help

1379

help

1380

If you have a network (Ethernet) controller of this type, say Y

1380

If you have a network (Ethernet) controller of this type, say Y

1381

or M and read the Ethernet-HOWTO, available from

1381

or M and read the Ethernet-HOWTO, available from

1382

<http://www.tldp.org/docs.html#howto>.

1382

<http://www.tldp.org/docs.html#howto>.

1383

1384

To compile this driver as a module, choose M here. The module

1384

To compile this driver as a module, choose M here. The module

1385

will be called b44.

1385

will be called b44.

1386

1387

# Auto-select SSB PCI-HOST support, if possible

1387

# Auto-select SSB PCI-HOST support, if possible

1388

config B44_PCI_AUTOSELECT

1388

config B44_PCI_AUTOSELECT

1389

bool

1389

bool

1390

depends on B44 && SSB_PCIHOST_POSSIBLE

1390

depends on B44 && SSB_PCIHOST_POSSIBLE

1391

select SSB_PCIHOST

1391

select SSB_PCIHOST

1392

default y

1392

default y

1393

1394

# Auto-select SSB PCICORE driver, if possible

1394

# Auto-select SSB PCICORE driver, if possible

1395

config B44_PCICORE_AUTOSELECT

1395

config B44_PCICORE_AUTOSELECT

1396

bool

1396

bool

1397

depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE

1397

depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE

1398

select SSB_DRIVER_PCICORE

1398

select SSB_DRIVER_PCICORE

1399

default y

1399

default y

1400

1401

config B44_PCI

1401

config B44_PCI

1402

bool

1402

bool

1403

depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT

1403

depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT

1404

default y

1404

default y

1405

1406

config FORCEDETH

1406

config FORCEDETH

1407

tristate "nForce Ethernet support"

1407

tristate "nForce Ethernet support"

1408

depends on NET_PCI && PCI

1408

depends on NET_PCI && PCI

1409

help

1409

help

1410

If you have a network (Ethernet) controller of this type, say Y and

1410

If you have a network (Ethernet) controller of this type, say Y and

1411

read the Ethernet-HOWTO, available from

1411

read the Ethernet-HOWTO, available from

1412

<http://www.tldp.org/docs.html#howto>.

1412

<http://www.tldp.org/docs.html#howto>.

1413

1414

To compile this driver as a module, choose M here. The module

1414

To compile this driver as a module, choose M here. The module

1415

will be called forcedeth.

1415

will be called forcedeth.

1416

1417

config FORCEDETH_NAPI

1417

config FORCEDETH_NAPI

1418

bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"

1418

bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"

1419

depends on FORCEDETH && EXPERIMENTAL

1419

depends on FORCEDETH && EXPERIMENTAL

1420

help

1420

help

1421

NAPI is a new driver API designed to reduce CPU and interrupt load

1421

NAPI is a new driver API designed to reduce CPU and interrupt load

1422

when the driver is receiving lots of packets from the card. It is

1422

when the driver is receiving lots of packets from the card. It is

1423

still somewhat experimental and thus not yet enabled by default.

1423

still somewhat experimental and thus not yet enabled by default.

1424

1425

If your estimated Rx load is 10kpps or more, or if the card will be

1425

If your estimated Rx load is 10kpps or more, or if the card will be

1426

deployed on potentially unfriendly networks (e.g. in a firewall),

1426

deployed on potentially unfriendly networks (e.g. in a firewall),

1427

then say Y here.

1427

then say Y here.

1428

1429

If in doubt, say N.

1429

If in doubt, say N.

1430

1431

config CS89x0

1431

config CS89x0

1432

tristate "CS89x0 support"

1432

tristate "CS89x0 support"

1433

depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)

1433

depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)

1434

---help---

1434

---help---

1435

Support for CS89x0 chipset based Ethernet cards. If you have a

1435

Support for CS89x0 chipset based Ethernet cards. If you have a

1436

network (Ethernet) card of this type, say Y and read the

1436

network (Ethernet) card of this type, say Y and read the

1437

Ethernet-HOWTO, available from

1437

Ethernet-HOWTO, available from

1438

<http://www.tldp.org/docs.html#howto> as well as

1438

<http://www.tldp.org/docs.html#howto> as well as

1439

<file:Documentation/networking/cs89x0.txt>.

1439

<file:Documentation/networking/cs89x0.txt>.

1440

1441

To compile this driver as a module, choose M here. The module

1441

To compile this driver as a module, choose M here. The module

1442

will be called cs89x0.

1442

will be called cs89x0.

1443

1444

config TC35815

1444

config TC35815

1445

tristate "TOSHIBA TC35815 Ethernet support"

1445

tristate "TOSHIBA TC35815 Ethernet support"

1446

depends on NET_PCI && PCI && MIPS

1446

depends on NET_PCI && PCI && MIPS

1447

select PHYLIB

1447

select PHYLIB

1448

1449

config EEPRO100

1449

config EEPRO100

1450

tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"

1450

tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"

1451

depends on NET_PCI && PCI

1451

depends on NET_PCI && PCI

1452

select MII

1452

select MII

1453

help

1453

help

1454

If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)

1454

If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)

1455

card, say Y and read the Ethernet-HOWTO, available from

1455

card, say Y and read the Ethernet-HOWTO, available from

1456

<http://www.tldp.org/docs.html#howto>.

1456

<http://www.tldp.org/docs.html#howto>.

1457

1458

To compile this driver as a module, choose M here. The module

1458

To compile this driver as a module, choose M here. The module

1459

will be called eepro100.

1459

will be called eepro100.

1460

1461

1462

config E100

1462

config E100

1463

tristate "Intel(R) PRO/100+ support"

1463

tristate "Intel(R) PRO/100+ support"

1464

depends on NET_PCI && PCI

1464

depends on NET_PCI && PCI

1465

select MII

1465

select MII

1466

---help---

1466

---help---

1467

This driver supports Intel(R) PRO/100 family of adapters.

1467

This driver supports Intel(R) PRO/100 family of adapters.

1468

To verify that your adapter is supported, find the board ID number

1468

To verify that your adapter is supported, find the board ID number

1469

on the adapter. Look for a label that has a barcode and a number

1469

on the adapter. Look for a label that has a barcode and a number

1470

in the format 123456-001 (six digits hyphen three digits).

1470

in the format 123456-001 (six digits hyphen three digits).

1471

1472

Use the above information and the Adapter & Driver ID Guide at:

1472

Use the above information and the Adapter & Driver ID Guide at:

1473

1474

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

1474

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

1475

1476

to identify the adapter.

1476

to identify the adapter.

1477

1478

For the latest Intel PRO/100 network driver for Linux, see:

1478

For the latest Intel PRO/100 network driver for Linux, see:

1479

1480

<http://appsr.intel.com/scripts-df/support_intel.asp>

1480

<http://appsr.intel.com/scripts-df/support_intel.asp>

1481

1482

More specific information on configuring the driver is in

1482

More specific information on configuring the driver is in

1483

<file:Documentation/networking/e100.txt>.

1483

<file:Documentation/networking/e100.txt>.

1484

1485

To compile this driver as a module, choose M here. The module

1485

To compile this driver as a module, choose M here. The module

1486

will be called e100.

1486

will be called e100.

1487

1488

config LNE390

1488

config LNE390

1489

tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"

1489

tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"

1490

depends on NET_PCI && EISA && EXPERIMENTAL

1490

depends on NET_PCI && EISA && EXPERIMENTAL

1491

select CRC32

1491

select CRC32

1492

help

1492

help

1493

If you have a network (Ethernet) card of this type, say Y and read

1493

If you have a network (Ethernet) card of this type, say Y and read

1494

the Ethernet-HOWTO, available from

1494

the Ethernet-HOWTO, available from

1495

<http://www.tldp.org/docs.html#howto>.

1495

<http://www.tldp.org/docs.html#howto>.

1496

1497

To compile this driver as a module, choose M here. The module

1497

To compile this driver as a module, choose M here. The module

1498

will be called lne390.

1498

will be called lne390.

1499

1500

config FEALNX

1500

config FEALNX

1501

tristate "Myson MTD-8xx PCI Ethernet support"

1501

tristate "Myson MTD-8xx PCI Ethernet support"

1502

depends on NET_PCI && PCI

1502

depends on NET_PCI && PCI

1503

select CRC32

1503

select CRC32

1504

select MII

1504

select MII

1505

help

1505

help

1506

Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet

1506

Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet

1507

cards. Specifications and data at

1507

cards. Specifications and data at

1508

<http://www.myson.com.hk/mtd/datasheet/>.

1508

<http://www.myson.com.hk/mtd/datasheet/>.

1509

1510

config NATSEMI

1510

config NATSEMI

1511

tristate "National Semiconductor DP8381x series PCI Ethernet support"

1511

tristate "National Semiconductor DP8381x series PCI Ethernet support"

1512

depends on NET_PCI && PCI

1512

depends on NET_PCI && PCI

1513

select CRC32

1513

select CRC32

1514

help

1514

help

1515

This driver is for the National Semiconductor DP83810 series,

1515

This driver is for the National Semiconductor DP83810 series,

1516

which is used in cards from PureData, NetGear, Linksys

1516

which is used in cards from PureData, NetGear, Linksys

1517

and others, including the 83815 chip.

1517

and others, including the 83815 chip.

1518

More specific information and updates are available from

1518

More specific information and updates are available from

1519

<http://www.scyld.com/network/natsemi.html>.

1519

<http://www.scyld.com/network/natsemi.html>.

1520

1521

config NE2K_PCI

1521

config NE2K_PCI

1522

tristate "PCI NE2000 and clones support (see help)"

1522

tristate "PCI NE2000 and clones support (see help)"

1523

depends on NET_PCI && PCI

1523

depends on NET_PCI && PCI

1524

select CRC32

1524

select CRC32

1525

---help---

1525

---help---

1526

This driver is for NE2000 compatible PCI cards. It will not work

1526

This driver is for NE2000 compatible PCI cards. It will not work

1527

with ISA NE2000 cards (they have their own driver, "NE2000/NE1000

1527

with ISA NE2000 cards (they have their own driver, "NE2000/NE1000

1528

support" below). If you have a PCI NE2000 network (Ethernet) card,

1528

support" below). If you have a PCI NE2000 network (Ethernet) card,

1529

say Y and read the Ethernet-HOWTO, available from

1529

say Y and read the Ethernet-HOWTO, available from

1530

<http://www.tldp.org/docs.html#howto>.

1530

<http://www.tldp.org/docs.html#howto>.

1531

1532

This driver also works for the following NE2000 clone cards:

1532

This driver also works for the following NE2000 clone cards:

1533

RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2

1533

RealTek RTL-8029 Winbond 89C940 Compex RL2000 KTI ET32P2

1534

NetVin NV5000SC Via 86C926 SureCom NE34 Winbond

1534

NetVin NV5000SC Via 86C926 SureCom NE34 Winbond

1535

Holtek HT80232 Holtek HT80229

1535

Holtek HT80232 Holtek HT80229

1536

1537

To compile this driver as a module, choose M here. The module

1537

To compile this driver as a module, choose M here. The module

1538

will be called ne2k-pci.

1538

will be called ne2k-pci.

1539

1540

config NE3210

1540

config NE3210

1541

tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"

1541

tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"

1542

depends on NET_PCI && EISA && EXPERIMENTAL

1542

depends on NET_PCI && EISA && EXPERIMENTAL

1543

select CRC32

1543

select CRC32

1544

---help---

1544

---help---

1545

If you have a network (Ethernet) card of this type, say Y and read

1545

If you have a network (Ethernet) card of this type, say Y and read

1546

the Ethernet-HOWTO, available from

1546

the Ethernet-HOWTO, available from

1547

<http://www.tldp.org/docs.html#howto>. Note that this driver

1547

<http://www.tldp.org/docs.html#howto>. Note that this driver

1548

will NOT WORK for NE3200 cards as they are completely different.

1548

will NOT WORK for NE3200 cards as they are completely different.

1549

1550

To compile this driver as a module, choose M here. The module

1550

To compile this driver as a module, choose M here. The module

1551

will be called ne3210.

1551

will be called ne3210.

1552

1553

config ES3210

1553

config ES3210

1554

tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"

1554

tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"

1555

depends on NET_PCI && EISA && EXPERIMENTAL

1555

depends on NET_PCI && EISA && EXPERIMENTAL

1556

select CRC32

1556

select CRC32

1557

help

1557

help

1558

If you have a network (Ethernet) card of this type, say Y and read

1558

If you have a network (Ethernet) card of this type, say Y and read

1559

the Ethernet-HOWTO, available from

1559

the Ethernet-HOWTO, available from

1560

<http://www.tldp.org/docs.html#howto>.

1560

<http://www.tldp.org/docs.html#howto>.

1561

1562

To compile this driver as a module, choose M here. The module

1562

To compile this driver as a module, choose M here. The module

1563

will be called es3210.

1563

will be called es3210.

1564

1565

config 8139CP

1565

config 8139CP

1566

tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"

1566

tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"

1567

depends on NET_PCI && PCI && EXPERIMENTAL

1567

depends on NET_PCI && PCI && EXPERIMENTAL

1568

select CRC32

1568

select CRC32

1569

select MII

1569

select MII

1570

help

1570

help

1571

This is a driver for the Fast Ethernet PCI network cards based on

1571

This is a driver for the Fast Ethernet PCI network cards based on

1572

the RTL8139C+ chips. If you have one of those, say Y and read

1572

the RTL8139C+ chips. If you have one of those, say Y and read

1573

the Ethernet-HOWTO, available from

1573

the Ethernet-HOWTO, available from

1574

<http://www.tldp.org/docs.html#howto>.

1574

<http://www.tldp.org/docs.html#howto>.

1575

1576

To compile this driver as a module, choose M here: the module

1576

To compile this driver as a module, choose M here: the module

1577

will be called 8139cp. This is recommended.

1577

will be called 8139cp. This is recommended.

1578

1579

config 8139TOO

1579

config 8139TOO

1580

tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"

1580

tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"

1581

depends on NET_PCI && PCI

1581

depends on NET_PCI && PCI

1582

select CRC32

1582

select CRC32

1583

select MII

1583

select MII

1584

---help---

1584

---help---

1585

This is a driver for the Fast Ethernet PCI network cards based on

1585

This is a driver for the Fast Ethernet PCI network cards based on

1586

the RTL 8129/8130/8139 chips. If you have one of those, say Y and

1586

the RTL 8129/8130/8139 chips. If you have one of those, say Y and

1587

read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.

1587

read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.

1588

1589

To compile this driver as a module, choose M here: the module

1589

To compile this driver as a module, choose M here: the module

1590

will be called 8139too. This is recommended.

1590

will be called 8139too. This is recommended.

1591

1592

config 8139TOO_PIO

1592

config 8139TOO_PIO

1593

bool "Use PIO instead of MMIO"

1593

bool "Use PIO instead of MMIO"

1594

default y

1594

default y

1595

depends on 8139TOO

1595

depends on 8139TOO

1596

help

1596

help

1597

This instructs the driver to use programmed I/O ports (PIO) instead

1597

This instructs the driver to use programmed I/O ports (PIO) instead

1598

of PCI shared memory (MMIO). This can possibly solve some problems

1598

of PCI shared memory (MMIO). This can possibly solve some problems

1599

in case your mainboard has memory consistency issues. If unsure,

1599

in case your mainboard has memory consistency issues. If unsure,

1600

say N.

1600

say N.

1601

1602

config 8139TOO_TUNE_TWISTER

1602

config 8139TOO_TUNE_TWISTER

1603

bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"

1603

bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"

1604

depends on 8139TOO

1604

depends on 8139TOO

1605

help

1605

help

1606

This implements a function which might come in handy in case you

1606

This implements a function which might come in handy in case you

1607

are using low quality on long cabling. It is required for RealTek

1607

are using low quality on long cabling. It is required for RealTek

1608

RTL-8139 revision K boards, and totally unused otherwise. It tries

1608

RTL-8139 revision K boards, and totally unused otherwise. It tries

1609

to match the transceiver to the cable characteristics. This is

1609

to match the transceiver to the cable characteristics. This is

1610

experimental since hardly documented by the manufacturer.

1610

experimental since hardly documented by the manufacturer.

1611

If unsure, say Y.

1611

If unsure, say Y.

1612

1613

config 8139TOO_8129

1613

config 8139TOO_8129

1614

bool "Support for older RTL-8129/8130 boards"

1614

bool "Support for older RTL-8129/8130 boards"

1615

depends on 8139TOO

1615

depends on 8139TOO

1616

help

1616

help

1617

This enables support for the older and uncommon RTL-8129 and

1617

This enables support for the older and uncommon RTL-8129 and

1618

RTL-8130 chips, which support MII via an external transceiver,

1618

RTL-8130 chips, which support MII via an external transceiver,

1619

instead of an internal one. Disabling this option will save some

1619

instead of an internal one. Disabling this option will save some

1620

memory by making the code size smaller. If unsure, say Y.

1620

memory by making the code size smaller. If unsure, say Y.

1621

1622

config 8139_OLD_RX_RESET

1622

config 8139_OLD_RX_RESET

1623

bool "Use older RX-reset method"

1623

bool "Use older RX-reset method"

1624

depends on 8139TOO

1624

depends on 8139TOO

1625

help

1625

help

1626

The 8139too driver was recently updated to contain a more rapid

1626

The 8139too driver was recently updated to contain a more rapid

1627

reset sequence, in the face of severe receive errors. This "new"

1627

reset sequence, in the face of severe receive errors. This "new"

1628

RX-reset method should be adequate for all boards. But if you

1628

RX-reset method should be adequate for all boards. But if you

1629

experience problems, you can enable this option to restore the

1629

experience problems, you can enable this option to restore the

1630

old RX-reset behavior. If unsure, say N.

1630

old RX-reset behavior. If unsure, say N.

1631

1632

config R6040

1632

config R6040

1633

tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"

1633

tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"

1634

depends on NET_PCI && PCI

1634

depends on NET_PCI && PCI

1635

select CRC32

1635

select CRC32

1636

select MII

1636

select MII

1637

help

1637

help

1638

This is a driver for the R6040 Fast Ethernet MACs found in the

1638

This is a driver for the R6040 Fast Ethernet MACs found in the

1639

the RDC R-321x System-on-chips.

1639

the RDC R-321x System-on-chips.

1640

1641

To compile this driver as a module, choose M here: the module

1641

To compile this driver as a module, choose M here: the module

1642

will be called r6040. This is recommended.

1642

will be called r6040. This is recommended.

1643

1644

config SIS900

1644

config SIS900

1645

tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"

1645

tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"

1646

depends on NET_PCI && PCI

1646

depends on NET_PCI && PCI

1647

select CRC32

1647

select CRC32

1648

select MII

1648

select MII

1649

---help---

1649

---help---

1650

This is a driver for the Fast Ethernet PCI network cards based on

1650

This is a driver for the Fast Ethernet PCI network cards based on

1651

the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in

1651

the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in

1652

SiS 630 and SiS 540 chipsets.

1652

SiS 630 and SiS 540 chipsets.

1653

1654

This driver also supports AMD 79C901 HomePNA so that you can use

1654

This driver also supports AMD 79C901 HomePNA so that you can use

1655

your phone line as a network cable.

1655

your phone line as a network cable.

1656

1657

To compile this driver as a module, choose M here: the module

1657

To compile this driver as a module, choose M here: the module

1658

will be called sis900. This is recommended.

1658

will be called sis900. This is recommended.

1659

1660

config EPIC100

1660

config EPIC100

1661

tristate "SMC EtherPower II"

1661

tristate "SMC EtherPower II"

1662

depends on NET_PCI && PCI

1662

depends on NET_PCI && PCI

1663

select CRC32

1663

select CRC32

1664

select MII

1664

select MII

1665

help

1665

help

1666

This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,

1666

This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,

1667

which is based on the SMC83c17x (EPIC/100).

1667

which is based on the SMC83c17x (EPIC/100).

1668

More specific information and updates are available from

1668

More specific information and updates are available from

1669

<http://www.scyld.com/network/epic100.html>.

1669

<http://www.scyld.com/network/epic100.html>.

1670

1671

config SUNDANCE

1671

config SUNDANCE

1672

tristate "Sundance Alta support"

1672

tristate "Sundance Alta support"

1673

depends on NET_PCI && PCI

1673

depends on NET_PCI && PCI

1674

select CRC32

1674

select CRC32

1675

select MII

1675

select MII

1676

help

1676

help

1677

This driver is for the Sundance "Alta" chip.

1677

This driver is for the Sundance "Alta" chip.

1678

More specific information and updates are available from

1678

More specific information and updates are available from

1679

<http://www.scyld.com/network/sundance.html>.

1679

<http://www.scyld.com/network/sundance.html>.

1680

1681

config SUNDANCE_MMIO

1681

config SUNDANCE_MMIO

1682

bool "Use MMIO instead of PIO"

1682

bool "Use MMIO instead of PIO"

1683

depends on SUNDANCE

1683

depends on SUNDANCE

1684

help

1684

help

1685

Enable memory-mapped I/O for interaction with Sundance NIC registers.

1685

Enable memory-mapped I/O for interaction with Sundance NIC registers.

1686

Do NOT enable this by default, PIO (enabled when MMIO is disabled)

1686

Do NOT enable this by default, PIO (enabled when MMIO is disabled)

1687

is known to solve bugs on certain chips.

1687

is known to solve bugs on certain chips.

1688

1689

If unsure, say N.

1689

If unsure, say N.

1690

1691

config TLAN

1691

config TLAN

1692

tristate "TI ThunderLAN support"

1692

tristate "TI ThunderLAN support"

1693

depends on NET_PCI && (PCI || EISA)

1693

depends on NET_PCI && (PCI || EISA)

1694

---help---

1694

---help---

1695

If you have a PCI Ethernet network card based on the ThunderLAN chip

1695

If you have a PCI Ethernet network card based on the ThunderLAN chip

1696

which is supported by this driver, say Y and read the

1696

which is supported by this driver, say Y and read the

1697

Ethernet-HOWTO, available from

1697

Ethernet-HOWTO, available from

1698

<http://www.tldp.org/docs.html#howto>.

1698

<http://www.tldp.org/docs.html#howto>.

1699

1700

Devices currently supported by this driver are Compaq Netelligent,

1700

Devices currently supported by this driver are Compaq Netelligent,

1701

Compaq NetFlex and Olicom cards. Please read the file

1701

Compaq NetFlex and Olicom cards. Please read the file

1702

<file:Documentation/networking/tlan.txt> for more details.

1702

<file:Documentation/networking/tlan.txt> for more details.

1703

1704

To compile this driver as a module, choose M here. The module

1704

To compile this driver as a module, choose M here. The module

1705

will be called tlan.

1705

will be called tlan.

1706

1707

Please email feedback to <torben.mathiasen@compaq.com>.

1707

Please email feedback to <torben.mathiasen@compaq.com>.

1708

1709

config VIA_RHINE

1709

config VIA_RHINE

1710

tristate "VIA Rhine support"

1710

tristate "VIA Rhine support"

1711

depends on NET_PCI && PCI

1711

depends on NET_PCI && PCI

1712

select CRC32

1712

select CRC32

1713

select MII

1713

select MII

1714

help

1714

help

1715

If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),

1715

If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),

1716

Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type

1716

Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type

1717

Ethernet functions can also be found integrated on South Bridges

1717

Ethernet functions can also be found integrated on South Bridges

1718

(e.g. VT8235).

1718

(e.g. VT8235).

1719

1720

To compile this driver as a module, choose M here. The module

1720

To compile this driver as a module, choose M here. The module

1721

will be called via-rhine.

1721

will be called via-rhine.

1722

1723

config VIA_RHINE_MMIO

1723

config VIA_RHINE_MMIO

1724

bool "Use MMIO instead of PIO"

1724

bool "Use MMIO instead of PIO"

1725

depends on VIA_RHINE

1725

depends on VIA_RHINE

1726

help

1726

help

1727

This instructs the driver to use PCI shared memory (MMIO) instead of

1727

This instructs the driver to use PCI shared memory (MMIO) instead of

1728

programmed I/O ports (PIO). Enabling this gives an improvement in

1728

programmed I/O ports (PIO). Enabling this gives an improvement in

1729

processing time in parts of the driver.

1729

processing time in parts of the driver.

1730

1731

If unsure, say Y.

1731

If unsure, say Y.

1732

1733

config VIA_RHINE_NAPI

1733

config VIA_RHINE_NAPI

1734

bool "Use Rx Polling (NAPI)"

1734

bool "Use Rx Polling (NAPI)"

1735

depends on VIA_RHINE

1735

depends on VIA_RHINE

1736

help

1736

help

1737

NAPI is a new driver API designed to reduce CPU and interrupt load

1737

NAPI is a new driver API designed to reduce CPU and interrupt load

1738

when the driver is receiving lots of packets from the card.

1738

when the driver is receiving lots of packets from the card.

1739

1740

If your estimated Rx load is 10kpps or more, or if the card will be

1740

If your estimated Rx load is 10kpps or more, or if the card will be

1741

deployed on potentially unfriendly networks (e.g. in a firewall),

1741

deployed on potentially unfriendly networks (e.g. in a firewall),

1742

then say Y here.

1742

then say Y here.

1743

1744

config LAN_SAA9730

1744

config LAN_SAA9730

1745

bool "Philips SAA9730 Ethernet support"

1745

bool "Philips SAA9730 Ethernet support"

1746

depends on NET_PCI && PCI && MIPS_ATLAS

1746

depends on NET_PCI && PCI && MIPS_ATLAS

1747

help

1747

help

1748

The SAA9730 is a combined multimedia and peripheral controller used

1748

The SAA9730 is a combined multimedia and peripheral controller used

1749

in thin clients, Internet access terminals, and diskless

1749

in thin clients, Internet access terminals, and diskless

1750

workstations.

1750

workstations.

1751

See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.

1751

See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.

1752

1753

config SC92031

1753

config SC92031

1754

tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"

1754

tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"

1755

depends on NET_PCI && PCI && EXPERIMENTAL

1755

depends on NET_PCI && PCI && EXPERIMENTAL

1756

select CRC32

1756

select CRC32

1757

---help---

1757

---help---

1758

This is a driver for the Fast Ethernet PCI network cards based on

1758

This is a driver for the Fast Ethernet PCI network cards based on

1759

the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you

1759

the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you

1760

have one of these, say Y here.

1760

have one of these, say Y here.

1761

1762

To compile this driver as a module, choose M here: the module

1762

To compile this driver as a module, choose M here: the module

1763

will be called sc92031. This is recommended.

1763

will be called sc92031. This is recommended.

1764

1765

config CPMAC

1765

config CPMAC

1766

tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"

1766

tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"

1767

depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN

1767

depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN

1768

select PHYLIB

1768

select PHYLIB

1769

help

1769

help

1770

TI AR7 CPMAC Ethernet support

1770

TI AR7 CPMAC Ethernet support

1771

1772

config NET_POCKET

1772

config NET_POCKET

1773

bool "Pocket and portable adapters"

1773

bool "Pocket and portable adapters"

1774

depends on PARPORT

1774

depends on PARPORT

1775

---help---

1775

---help---

1776

Cute little network (Ethernet) devices which attach to the parallel

1776

Cute little network (Ethernet) devices which attach to the parallel

1777

port ("pocket adapters"), commonly used with laptops. If you have

1777

port ("pocket adapters"), commonly used with laptops. If you have

1778

one of those, say Y and read the Ethernet-HOWTO, available from

1778

one of those, say Y and read the Ethernet-HOWTO, available from

1779

<http://www.tldp.org/docs.html#howto>.

1779

<http://www.tldp.org/docs.html#howto>.

1780

1781

If you want to plug a network (or some other) card into the PCMCIA

1781

If you want to plug a network (or some other) card into the PCMCIA

1782

(or PC-card) slot of your laptop instead (PCMCIA is the standard for

1782

(or PC-card) slot of your laptop instead (PCMCIA is the standard for

1783

credit card size extension cards used by all modern laptops), you

1783

credit card size extension cards used by all modern laptops), you

1784

need the pcmcia-cs package (location contained in the file

1784

need the pcmcia-cs package (location contained in the file

1785

<file:Documentation/Changes>) and you can say N here.

1785

<file:Documentation/Changes>) and you can say N here.

1786

1787

Laptop users should read the Linux Laptop home page at

1787

Laptop users should read the Linux Laptop home page at

1788

<http://www.linux-on-laptops.com/> or

1788

<http://www.linux-on-laptops.com/> or

1789

Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.

1789

Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.

1790

1791

Note that the answer to this question doesn't directly affect the

1791

Note that the answer to this question doesn't directly affect the

1792

kernel: saying N will just cause the configurator to skip all

1792

kernel: saying N will just cause the configurator to skip all

1793

the questions about this class of network devices. If you say Y, you

1793

the questions about this class of network devices. If you say Y, you

1794

will be asked for your specific device in the following questions.

1794

will be asked for your specific device in the following questions.

1795

1796

config ATP

1796

config ATP

1797

tristate "AT-LAN-TEC/RealTek pocket adapter support"

1797

tristate "AT-LAN-TEC/RealTek pocket adapter support"

1798

depends on NET_POCKET && PARPORT && X86

1798

depends on NET_POCKET && PARPORT && X86

1799

select CRC32

1799

select CRC32

1800

---help---

1800

---help---

1801

This is a network (Ethernet) device which attaches to your parallel

1801

This is a network (Ethernet) device which attaches to your parallel

1802

port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,

1802

port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,

1803

available from <http://www.tldp.org/docs.html#howto>, if you

1803

available from <http://www.tldp.org/docs.html#howto>, if you

1804

want to use this. If you intend to use this driver, you should have

1804

want to use this. If you intend to use this driver, you should have

1805

said N to the "Parallel printer support", because the two drivers

1805

said N to the "Parallel printer support", because the two drivers

1806

don't like each other.

1806

don't like each other.

1807

1808

To compile this driver as a module, choose M here: the module

1808

To compile this driver as a module, choose M here: the module

1809

will be called atp.

1809

will be called atp.

1810

1811

config DE600

1811

config DE600

1812

tristate "D-Link DE600 pocket adapter support"

1812

tristate "D-Link DE600 pocket adapter support"

1813

depends on NET_POCKET && PARPORT

1813

depends on NET_POCKET && PARPORT

1814

---help---

1814

---help---

1815

This is a network (Ethernet) device which attaches to your parallel

1815

This is a network (Ethernet) device which attaches to your parallel

1816

port. Read <file:Documentation/networking/DLINK.txt> as well as the

1816

port. Read <file:Documentation/networking/DLINK.txt> as well as the

1817

Ethernet-HOWTO, available from

1817

Ethernet-HOWTO, available from

1818

<http://www.tldp.org/docs.html#howto>, if you want to use

1818

<http://www.tldp.org/docs.html#howto>, if you want to use

1819

this. It is possible to have several devices share a single parallel

1819

this. It is possible to have several devices share a single parallel

1820

port and it is safe to compile the corresponding drivers into the

1820

port and it is safe to compile the corresponding drivers into the

1821

kernel.

1821

kernel.

1822

1823

To compile this driver as a module, choose M here: the module

1823

To compile this driver as a module, choose M here: the module

1824

will be called de600.

1824

will be called de600.

1825

1826

config DE620

1826

config DE620

1827

tristate "D-Link DE620 pocket adapter support"

1827

tristate "D-Link DE620 pocket adapter support"

1828

depends on NET_POCKET && PARPORT

1828

depends on NET_POCKET && PARPORT

1829

---help---

1829

---help---

1830

This is a network (Ethernet) device which attaches to your parallel

1830

This is a network (Ethernet) device which attaches to your parallel

1831

port. Read <file:Documentation/networking/DLINK.txt> as well as the

1831

port. Read <file:Documentation/networking/DLINK.txt> as well as the

1832

Ethernet-HOWTO, available from

1832

Ethernet-HOWTO, available from

1833

<http://www.tldp.org/docs.html#howto>, if you want to use

1833

<http://www.tldp.org/docs.html#howto>, if you want to use

1834

this. It is possible to have several devices share a single parallel

1834

this. It is possible to have several devices share a single parallel

1835

port and it is safe to compile the corresponding drivers into the

1835

port and it is safe to compile the corresponding drivers into the

1836

kernel.

1836

kernel.

1837

1838

To compile this driver as a module, choose M here: the module

1838

To compile this driver as a module, choose M here: the module

1839

will be called de620.

1839

will be called de620.

1840

1841

config SGISEEQ

1841

config SGISEEQ

1842

tristate "SGI Seeq ethernet controller support"

1842

tristate "SGI Seeq ethernet controller support"

1843

depends on SGI_HAS_SEEQ

1843

depends on SGI_HAS_SEEQ

1844

help

1844

help

1845

Say Y here if you have an Seeq based Ethernet network card. This is

1845

Say Y here if you have an Seeq based Ethernet network card. This is

1846

used in many Silicon Graphics machines.

1846

used in many Silicon Graphics machines.

1847

1848

config DECLANCE

1848

config DECLANCE

1849

tristate "DEC LANCE ethernet controller support"

1849

tristate "DEC LANCE ethernet controller support"

1850

depends on MACH_DECSTATION

1850

depends on MACH_DECSTATION

1851

select CRC32

1851

select CRC32

1852

help

1852

help

1853

This driver is for the series of Ethernet controllers produced by

1853

This driver is for the series of Ethernet controllers produced by

1854

DEC (now Compaq) based on the AMD Lance chipset, including the

1854

DEC (now Compaq) based on the AMD Lance chipset, including the

1855

DEPCA series. (This chipset is better known via the NE2100 cards.)

1855

DEPCA series. (This chipset is better known via the NE2100 cards.)

1856

1857

config 68360_ENET

1857

config 68360_ENET

1858

bool "Motorola 68360 ethernet controller"

1858

bool "Motorola 68360 ethernet controller"

1859

depends on M68360

1859

depends on M68360

1860

help

1860

help

1861

Say Y here if you want to use the built-in ethernet controller of

1861

Say Y here if you want to use the built-in ethernet controller of

1862

the Motorola 68360 processor.

1862

the Motorola 68360 processor.

1863

1864

config FEC

1864

config FEC

1865

bool "FEC ethernet controller (of ColdFire CPUs)"

1865

bool "FEC ethernet controller (of ColdFire CPUs)"

1866

depends on M523x || M527x || M5272 || M528x || M520x

1866

depends on M523x || M527x || M5272 || M528x || M520x

1867

help

1867

help

1868

Say Y here if you want to use the built-in 10/100 Fast ethernet

1868

Say Y here if you want to use the built-in 10/100 Fast ethernet

1869

controller on some Motorola ColdFire processors.

1869

controller on some Motorola ColdFire processors.

1870

1871

config FEC2

1871

config FEC2

1872

bool "Second FEC ethernet controller (on some ColdFire CPUs)"

1872

bool "Second FEC ethernet controller (on some ColdFire CPUs)"

1873

depends on FEC

1873

depends on FEC

1874

help

1874

help

1875

Say Y here if you want to use the second built-in 10/100 Fast

1875

Say Y here if you want to use the second built-in 10/100 Fast

1876

ethernet controller on some Motorola ColdFire processors.

1876

ethernet controller on some Motorola ColdFire processors.

1877

1878

config FEC_MPC52xx

1878

config FEC_MPC52xx

1879

tristate "MPC52xx FEC driver"

1879

tristate "MPC52xx FEC driver"

1880

depends on PPC_MERGE && PPC_MPC52xx && PPC_BESTCOMM_FEC

1880

depends on PPC_MERGE && PPC_MPC52xx && PPC_BESTCOMM_FEC

1881

select CRC32

1881

select CRC32

1882

select PHYLIB

1882

select PHYLIB

1883

---help---

1883

---help---

1884

This option enables support for the MPC5200's on-chip

1884

This option enables support for the MPC5200's on-chip

1885

Fast Ethernet Controller

1885

Fast Ethernet Controller

1886

If compiled as module, it will be called 'fec_mpc52xx.ko'.

1886

If compiled as module, it will be called 'fec_mpc52xx.ko'.

1887

1888

config FEC_MPC52xx_MDIO

1888

config FEC_MPC52xx_MDIO

1889

bool "MPC52xx FEC MDIO bus driver"

1889

bool "MPC52xx FEC MDIO bus driver"

1890

depends on FEC_MPC52xx

1890

depends on FEC_MPC52xx

1891

default y

1891

default y

1892

---help---

1892

---help---

1893

The MPC5200's FEC can connect to the Ethernet either with

1893

The MPC5200's FEC can connect to the Ethernet either with

1894

an external MII PHY chip or 10 Mbps 7-wire interface

1894

an external MII PHY chip or 10 Mbps 7-wire interface

1895

(Motorola? industry standard).

1895

(Motorola? industry standard).

1896

If your board uses an external PHY connected to FEC, enable this.

1896

If your board uses an external PHY connected to FEC, enable this.

1897

If not sure, enable.

1897

If not sure, enable.

1898

If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.

1898

If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.

1899

1900

config NE_H8300

1900

config NE_H8300

1901

tristate "NE2000 compatible support for H8/300"

1901

tristate "NE2000 compatible support for H8/300"

1902

depends on H8300

1902

depends on H8300

1903

help

1903

help

1904

Say Y here if you want to use the NE2000 compatible

1904

Say Y here if you want to use the NE2000 compatible

1905

controller on the Renesas H8/300 processor.

1905

controller on the Renesas H8/300 processor.

1906

1907

source "drivers/net/fec_8xx/Kconfig"

1907

source "drivers/net/fec_8xx/Kconfig"

1908

source "drivers/net/fs_enet/Kconfig"

1908

source "drivers/net/fs_enet/Kconfig"

1909

1910

endif # NET_ETHERNET

1910

endif # NET_ETHERNET

1911

1912

#

1912

#

1913

# Gigabit Ethernet

1913

# Gigabit Ethernet

1914

#

1914

#

1915

1916

menuconfig NETDEV_1000

1916

menuconfig NETDEV_1000

1917

bool "Ethernet (1000 Mbit)"

1917

bool "Ethernet (1000 Mbit)"

1918

depends on !UML

1918

depends on !UML

1919

default y

1919

default y

1920

---help---

1920

---help---

1921

Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common

1921

Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common

1922

type of Local Area Network (LAN) in universities and companies.

1922

type of Local Area Network (LAN) in universities and companies.

1923

1924

Say Y here to get to see options for Gigabit Ethernet drivers.

1924

Say Y here to get to see options for Gigabit Ethernet drivers.

1925

This option alone does not add any kernel code.

1925

This option alone does not add any kernel code.

1926

Note that drivers supporting both 100 and 1000 MBit may be listed

1926

Note that drivers supporting both 100 and 1000 MBit may be listed

1927

under "Ethernet (10 or 100MBit)" instead.

1927

under "Ethernet (10 or 100MBit)" instead.

1928

1929

If you say N, all options in this submenu will be skipped and disabled.

1929

If you say N, all options in this submenu will be skipped and disabled.

1930

1931

if NETDEV_1000

1931

if NETDEV_1000

1932

1933

config ACENIC

1933

config ACENIC

1934

tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"

1934

tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"

1935

depends on PCI

1935

depends on PCI

1936

---help---

1936

---help---

1937

Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear

1937

Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear

1938

GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet

1938

GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet

1939

adapter. The driver allows for using the Jumbo Frame option (9000

1939

adapter. The driver allows for using the Jumbo Frame option (9000

1940

bytes/frame) however it requires that your switches can handle this

1940

bytes/frame) however it requires that your switches can handle this

1941

as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig

1941

as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig

1942

line.

1942

line.

1943

1944

To compile this driver as a module, choose M here: the

1944

To compile this driver as a module, choose M here: the

1945

module will be called acenic.

1945

module will be called acenic.

1946

1947

config ACENIC_OMIT_TIGON_I

1947

config ACENIC_OMIT_TIGON_I

1948

bool "Omit support for old Tigon I based AceNICs"

1948

bool "Omit support for old Tigon I based AceNICs"

1949

depends on ACENIC

1949

depends on ACENIC

1950

help

1950

help

1951

Say Y here if you only have Tigon II based AceNICs and want to leave

1951

Say Y here if you only have Tigon II based AceNICs and want to leave

1952

out support for the older Tigon I based cards which are no longer

1952

out support for the older Tigon I based cards which are no longer

1953

being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B

1953

being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B

1954

version)). This will reduce the size of the driver object by

1954

version)). This will reduce the size of the driver object by

1955

app. 100KB. If you are not sure whether your card is a Tigon I or a

1955

app. 100KB. If you are not sure whether your card is a Tigon I or a

1956

Tigon II, say N here.

1956

Tigon II, say N here.

1957

1958

The safe and default value for this is N.

1958

The safe and default value for this is N.

1959

1960

config DL2K

1960

config DL2K

1961

tristate "DL2000/TC902x-based Gigabit Ethernet support"

1961

tristate "DL2000/TC902x-based Gigabit Ethernet support"

1962

depends on PCI

1962

depends on PCI

1963

select CRC32

1963

select CRC32

1964

help

1964

help

1965

This driver supports DL2000/TC902x-based Gigabit ethernet cards,

1965

This driver supports DL2000/TC902x-based Gigabit ethernet cards,

1966

which includes

1966

which includes

1967

D-Link DGE-550T Gigabit Ethernet Adapter.

1967

D-Link DGE-550T Gigabit Ethernet Adapter.

1968

D-Link DL2000-based Gigabit Ethernet Adapter.

1968

D-Link DL2000-based Gigabit Ethernet Adapter.

1969

Sundance/Tamarack TC902x Gigabit Ethernet Adapter.

1969

Sundance/Tamarack TC902x Gigabit Ethernet Adapter.

1970

1971

To compile this driver as a module, choose M here: the

1971

To compile this driver as a module, choose M here: the

1972

module will be called dl2k.

1972

module will be called dl2k.

1973

1974

config E1000

1974

config E1000

1975

tristate "Intel(R) PRO/1000 Gigabit Ethernet support"

1975

tristate "Intel(R) PRO/1000 Gigabit Ethernet support"

1976

depends on PCI

1976

depends on PCI

1977

---help---

1977

---help---

1978

This driver supports Intel(R) PRO/1000 gigabit ethernet family of

1978

This driver supports Intel(R) PRO/1000 gigabit ethernet family of

1979

adapters. For more information on how to identify your adapter, go

1979

adapters. For more information on how to identify your adapter, go

1980

to the Adapter & Driver ID Guide at:

1980

to the Adapter & Driver ID Guide at:

1981

1982

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

1982

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

1983

1984

For general information and support, go to the Intel support

1984

For general information and support, go to the Intel support

1985

website at:

1985

website at:

1986

1987

<http://support.intel.com>

1987

<http://support.intel.com>

1988

1989

More specific information on configuring the driver is in

1989

More specific information on configuring the driver is in

1990

<file:Documentation/networking/e1000.txt>.

1990

<file:Documentation/networking/e1000.txt>.

1991

1992

To compile this driver as a module, choose M here. The module

1992

To compile this driver as a module, choose M here. The module

1993

will be called e1000.

1993

will be called e1000.

1994

1995

config E1000_NAPI

1995

config E1000_NAPI

1996

bool "Use Rx Polling (NAPI)"

1996

bool "Use Rx Polling (NAPI)"

1997

depends on E1000

1997

depends on E1000

1998

help

1998

help

1999

NAPI is a new driver API designed to reduce CPU and interrupt load

1999

NAPI is a new driver API designed to reduce CPU and interrupt load

2000

when the driver is receiving lots of packets from the card. It is

2000

when the driver is receiving lots of packets from the card. It is

2001

still somewhat experimental and thus not yet enabled by default.

2001

still somewhat experimental and thus not yet enabled by default.

2002

2003

If your estimated Rx load is 10kpps or more, or if the card will be

2003

If your estimated Rx load is 10kpps or more, or if the card will be

2004

deployed on potentially unfriendly networks (e.g. in a firewall),

2004

deployed on potentially unfriendly networks (e.g. in a firewall),

2005

then say Y here.

2005

then say Y here.

2006

2007

If in doubt, say N.

2007

If in doubt, say N.

2008

2009

config E1000_DISABLE_PACKET_SPLIT

2009

config E1000_DISABLE_PACKET_SPLIT

2010

bool "Disable Packet Split for PCI express adapters"

2010

bool "Disable Packet Split for PCI express adapters"

2011

depends on E1000

2011

depends on E1000

2012

help

2012

help

2013

Say Y here if you want to use the legacy receive path for PCI express

2013

Say Y here if you want to use the legacy receive path for PCI express

2014

hardware.

2014

hardware.

2015

2016

If in doubt, say N.

2016

If in doubt, say N.

2017

2018

config E1000E

2018

config E1000E

2019

tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"

2019

tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"

2020

depends on PCI && (!SPARC32 || BROKEN)

2020

depends on PCI && (!SPARC32 || BROKEN)

2021

---help---

2021

---help---

2022

This driver supports the PCI-Express Intel(R) PRO/1000 gigabit

2022

This driver supports the PCI-Express Intel(R) PRO/1000 gigabit

2023

ethernet family of adapters. For PCI or PCI-X e1000 adapters,

2023

ethernet family of adapters. For PCI or PCI-X e1000 adapters,

2024

use the regular e1000 driver For more information on how to

2024

use the regular e1000 driver For more information on how to

2025

identify your adapter, go to the Adapter & Driver ID Guide at:

2025

identify your adapter, go to the Adapter & Driver ID Guide at:

2026

2027

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

2027

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

2028

2029

For general information and support, go to the Intel support

2029

For general information and support, go to the Intel support

2030

website at:

2030

website at:

2031

2032

<http://support.intel.com>

2032

<http://support.intel.com>

2033

2034

To compile this driver as a module, choose M here. The module

2034

To compile this driver as a module, choose M here. The module

2035

will be called e1000e.

2035

will be called e1000e.

2036

2037

config IP1000

2037

config IP1000

2038

tristate "IP1000 Gigabit Ethernet support"

2038

tristate "IP1000 Gigabit Ethernet support"

2039

depends on PCI && EXPERIMENTAL

2039

depends on PCI && EXPERIMENTAL

2040

select MII

2040

select MII

2041

---help---

2041

---help---

2042

This driver supports IP1000 gigabit Ethernet cards.

2042

This driver supports IP1000 gigabit Ethernet cards.

2043

2044

To compile this driver as a module, choose M here: the module

2044

To compile this driver as a module, choose M here: the module

2045

will be called ipg. This is recommended.

2045

will be called ipg. This is recommended.

2046

2047

config IGB

2047

config IGB

2048

tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"

2048

tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"

2049

depends on PCI

2049

depends on PCI

2050

---help---

2050

---help---

2051

This driver supports Intel(R) 82575 gigabit ethernet family of

2051

This driver supports Intel(R) 82575 gigabit ethernet family of

2052

adapters. For more information on how to identify your adapter, go

2052

adapters. For more information on how to identify your adapter, go

2053

to the Adapter & Driver ID Guide at:

2053

to the Adapter & Driver ID Guide at:

2054

2055

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

2055

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

2056

2057

For general information and support, go to the Intel support

2057

For general information and support, go to the Intel support

2058

website at:

2058

website at:

2059

2060

<http://support.intel.com>

2060

<http://support.intel.com>

2061

2062

More specific information on configuring the driver is in

2062

More specific information on configuring the driver is in

2063

<file:Documentation/networking/e1000.txt>.

2063

<file:Documentation/networking/e1000.txt>.

2064

2065

To compile this driver as a module, choose M here. The module

2065

To compile this driver as a module, choose M here. The module

2066

will be called igb.

2066

will be called igb.

2067

2068

source "drivers/net/ixp2000/Kconfig"

2068

source "drivers/net/ixp2000/Kconfig"

2069

2070

config MYRI_SBUS

2070

config MYRI_SBUS

2071

tristate "MyriCOM Gigabit Ethernet support"

2071

tristate "MyriCOM Gigabit Ethernet support"

2072

depends on SBUS

2072

depends on SBUS

2073

help

2073

help

2074

This driver supports MyriCOM Sbus gigabit Ethernet cards.

2074

This driver supports MyriCOM Sbus gigabit Ethernet cards.

2075

2076

To compile this driver as a module, choose M here: the module

2076

To compile this driver as a module, choose M here: the module

2077

will be called myri_sbus. This is recommended.

2077

will be called myri_sbus. This is recommended.

2078

2079

config NS83820

2079

config NS83820

2080

tristate "National Semiconductor DP83820 support"

2080

tristate "National Semiconductor DP83820 support"

2081

depends on PCI

2081

depends on PCI

2082

help

2082

help

2083

This is a driver for the National Semiconductor DP83820 series

2083

This is a driver for the National Semiconductor DP83820 series

2084

of gigabit ethernet MACs. Cards using this chipset include

2084

of gigabit ethernet MACs. Cards using this chipset include

2085

the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,

2085

the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,

2086

SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of

2086

SOHO-GA2000T, SOHO-GA2500T. The driver supports the use of

2087

zero copy.

2087

zero copy.

2088

2089

config HAMACHI

2089

config HAMACHI

2090

tristate "Packet Engines Hamachi GNIC-II support"

2090

tristate "Packet Engines Hamachi GNIC-II support"

2091

depends on PCI

2091

depends on PCI

2092

select MII

2092

select MII

2093

help

2093

help

2094

If you have a Gigabit Ethernet card of this type, say Y and read

2094

If you have a Gigabit Ethernet card of this type, say Y and read

2095

the Ethernet-HOWTO, available from

2095

the Ethernet-HOWTO, available from

2096

<http://www.tldp.org/docs.html#howto>.

2096

<http://www.tldp.org/docs.html#howto>.

2097

2098

To compile this driver as a module, choose M here. The module will be

2098

To compile this driver as a module, choose M here. The module will be

2099

called hamachi.

2099

called hamachi.

2100

2101

config YELLOWFIN

2101

config YELLOWFIN

2102

tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"

2102

tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"

2103

depends on PCI && EXPERIMENTAL

2103

depends on PCI && EXPERIMENTAL

2104

select CRC32

2104

select CRC32

2105

---help---

2105

---help---

2106

Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet

2106

Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet

2107

adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is

2107

adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is

2108

used by the Beowulf Linux cluster project. See

2108

used by the Beowulf Linux cluster project. See

2109

<http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more

2109

<http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more

2110

information about this driver in particular and Beowulf in general.

2110

information about this driver in particular and Beowulf in general.

2111

2112

To compile this driver as a module, choose M here: the module

2112

To compile this driver as a module, choose M here: the module

2113

will be called yellowfin. This is recommended.

2113

will be called yellowfin. This is recommended.

2114

2115

config R8169

2115

config R8169

2116

tristate "Realtek 8169 gigabit ethernet support"

2116

tristate "Realtek 8169 gigabit ethernet support"

2117

depends on PCI

2117

depends on PCI

2118

select CRC32

2118

select CRC32

2119

---help---

2119

---help---

2120

Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.

2120

Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.

2121

2122

To compile this driver as a module, choose M here: the module

2122

To compile this driver as a module, choose M here: the module

2123

will be called r8169. This is recommended.

2123

will be called r8169. This is recommended.

2124

2125

config R8169_VLAN

2125

config R8169_VLAN

2126

bool "VLAN support"

2126

bool "VLAN support"

2127

depends on R8169 && VLAN_8021Q

2127

depends on R8169 && VLAN_8021Q

2128

---help---

2128

---help---

2129

Say Y here for the r8169 driver to support the functions required

2129

Say Y here for the r8169 driver to support the functions required

2130

by the kernel 802.1Q code.

2130

by the kernel 802.1Q code.

2131

2132

If in doubt, say Y.

2132

If in doubt, say Y.

2133

2134

config SB1250_MAC

2134

config SB1250_MAC

2135

tristate "SB1250 Gigabit Ethernet support"

2135

tristate "SB1250 Gigabit Ethernet support"

2136

depends on SIBYTE_SB1xxx_SOC

2136

depends on SIBYTE_SB1xxx_SOC

2137

select PHYLIB

2137

select PHYLIB

2138

---help---

2138

---help---

2139

This driver supports Gigabit Ethernet interfaces based on the

2139

This driver supports Gigabit Ethernet interfaces based on the

2140

Broadcom SiByte family of System-On-a-Chip parts. They include

2140

Broadcom SiByte family of System-On-a-Chip parts. They include

2141

the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455

2141

the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455

2142

and BCM1480 chips.

2142

and BCM1480 chips.

2143

2144

To compile this driver as a module, choose M here: the module

2144

To compile this driver as a module, choose M here: the module

2145

will be called sb1250-mac.

2145

will be called sb1250-mac.

2146

2147

config SIS190

2147

config SIS190

2148

tristate "SiS190/SiS191 gigabit ethernet support"

2148

tristate "SiS190/SiS191 gigabit ethernet support"

2149

depends on PCI

2149

depends on PCI

2150

select CRC32

2150

select CRC32

2151

select MII

2151

select MII

2152

---help---

2152

---help---

2153

Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or

2153

Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or

2154

a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to

2154

a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to

2155

appear in lan on motherboard designs which are based on SiS 965

2155

appear in lan on motherboard designs which are based on SiS 965

2156

and SiS 966 south bridge.

2156

and SiS 966 south bridge.

2157

2158

To compile this driver as a module, choose M here: the module

2158

To compile this driver as a module, choose M here: the module

2159

will be called sis190. This is recommended.

2159

will be called sis190. This is recommended.

2160

2161

config SKGE

2161

config SKGE

2162

tristate "New SysKonnect GigaEthernet support"

2162

tristate "New SysKonnect GigaEthernet support"

2163

depends on PCI

2163

depends on PCI

2164

select CRC32

2164

select CRC32

2165

---help---

2165

---help---

2166

This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx

2166

This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx

2167

and related Gigabit Ethernet adapters. It is a new smaller driver

2167

and related Gigabit Ethernet adapters. It is a new smaller driver

2168

with better performance and more complete ethtool support.

2168

with better performance and more complete ethtool support.

2169

2170

It does not support the link failover and network management

2170

It does not support the link failover and network management

2171

features that "portable" vendor supplied sk98lin driver does.

2171

features that "portable" vendor supplied sk98lin driver does.

2172

2173

This driver supports adapters based on the original Yukon chipset:

2173

This driver supports adapters based on the original Yukon chipset:

2174

Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,

2174

Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,

2175

Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.

2175

Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.

2176

2177

It does not support the newer Yukon2 chipset: a separate driver,

2177

It does not support the newer Yukon2 chipset: a separate driver,

2178

sky2, is provided for Yukon2-based adapters.

2178

sky2, is provided for Yukon2-based adapters.

2179

2180

To compile this driver as a module, choose M here: the module

2180

To compile this driver as a module, choose M here: the module

2181

will be called skge. This is recommended.

2181

will be called skge. This is recommended.

2182

2183

config SKGE_DEBUG

2183

config SKGE_DEBUG

2184

bool "Debugging interface"

2184

bool "Debugging interface"

2185

depends on SKGE && DEBUG_FS

2185

depends on SKGE && DEBUG_FS

2186

help

2186

help

2187

This option adds the ability to dump driver state for debugging.

2187

This option adds the ability to dump driver state for debugging.

2188

The file debugfs/skge/ethX displays the state of the internal

2188

The file debugfs/skge/ethX displays the state of the internal

2189

transmit and receive rings.

2189

transmit and receive rings.

2190

2191

If unsure, say N.

2191

If unsure, say N.

2192

2193

config SKY2

2193

config SKY2

2194

tristate "SysKonnect Yukon2 support"

2194

tristate "SysKonnect Yukon2 support"

2195

depends on PCI

2195

depends on PCI

2196

select CRC32

2196

select CRC32

2197

---help---

2197

---help---

2198

This driver supports Gigabit Ethernet adapters based on the

2198

This driver supports Gigabit Ethernet adapters based on the

2199

Marvell Yukon 2 chipset:

2199

Marvell Yukon 2 chipset:

2200

Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/

2200

Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/

2201

88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21

2201

88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21

2202

2203

There is companion driver for the older Marvell Yukon and

2203

There is companion driver for the older Marvell Yukon and

2204

Genesis based adapters: skge.

2204

Genesis based adapters: skge.

2205

2206

To compile this driver as a module, choose M here: the module

2206

To compile this driver as a module, choose M here: the module

2207

will be called sky2. This is recommended.

2207

will be called sky2. This is recommended.

2208

2209

config SKY2_DEBUG

2209

config SKY2_DEBUG

2210

bool "Debugging interface"

2210

bool "Debugging interface"

2211

depends on SKY2 && DEBUG_FS

2211

depends on SKY2 && DEBUG_FS

2212

help

2212

help

2213

This option adds the ability to dump driver state for debugging.

2213

This option adds the ability to dump driver state for debugging.

2214

The file debugfs/sky2/ethX displays the state of the internal

2214

The file debugfs/sky2/ethX displays the state of the internal

2215

transmit and receive rings.

2215

transmit and receive rings.

2216

2217

If unsure, say N.

2217

If unsure, say N.

2218

2219

config VIA_VELOCITY

2219

config VIA_VELOCITY

2220

tristate "VIA Velocity support"

2220

tristate "VIA Velocity support"

2221

depends on PCI

2221

depends on PCI

2222

select CRC32

2222

select CRC32

2223

select CRC_CCITT

2223

select CRC_CCITT

2224

select MII

2224

select MII

2225

help

2225

help

2226

If you have a VIA "Velocity" based network card say Y here.

2226

If you have a VIA "Velocity" based network card say Y here.

2227

2228

To compile this driver as a module, choose M here. The module

2228

To compile this driver as a module, choose M here. The module

2229

will be called via-velocity.

2229

will be called via-velocity.

2230

2231

config TIGON3

2231

config TIGON3

2232

tristate "Broadcom Tigon3 support"

2232

tristate "Broadcom Tigon3 support"

2233

depends on PCI

2233

depends on PCI

2234

select PHYLIB

2234

select PHYLIB

2235

help

2235

help

2236

This driver supports Broadcom Tigon3 based gigabit Ethernet cards.

2236

This driver supports Broadcom Tigon3 based gigabit Ethernet cards.

2237

2238

To compile this driver as a module, choose M here: the module

2238

To compile this driver as a module, choose M here: the module

2239

will be called tg3. This is recommended.

2239

will be called tg3. This is recommended.

2240

2241

config BNX2

2241

config BNX2

2242

tristate "Broadcom NetXtremeII support"

2242

tristate "Broadcom NetXtremeII support"

2243

depends on PCI

2243

depends on PCI

2244

select CRC32

2244

select CRC32

2245

select ZLIB_INFLATE

2245

select ZLIB_INFLATE

2246

help

2246

help

2247

This driver supports Broadcom NetXtremeII gigabit Ethernet cards.

2247

This driver supports Broadcom NetXtremeII gigabit Ethernet cards.

2248

2249

To compile this driver as a module, choose M here: the module

2249

To compile this driver as a module, choose M here: the module

2250

will be called bnx2. This is recommended.

2250

will be called bnx2. This is recommended.

2251

2252

config SPIDER_NET

2252

config SPIDER_NET

2253

tristate "Spider Gigabit Ethernet driver"

2253

tristate "Spider Gigabit Ethernet driver"

2254

depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)

2254

depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)

2255

select FW_LOADER

2255

select FW_LOADER

2256

help

2256

help

2257

This driver supports the Gigabit Ethernet chips present on the

2257

This driver supports the Gigabit Ethernet chips present on the

2258

Cell Processor-Based Blades from IBM.

2258

Cell Processor-Based Blades from IBM.

2259

2260

config TSI108_ETH

2260

config TSI108_ETH

2261

tristate "Tundra TSI108 gigabit Ethernet support"

2261

tristate "Tundra TSI108 gigabit Ethernet support"

2262

depends on TSI108_BRIDGE

2262

depends on TSI108_BRIDGE

2263

help

2263

help

2264

This driver supports Tundra TSI108 gigabit Ethernet ports.

2264

This driver supports Tundra TSI108 gigabit Ethernet ports.

2265

To compile this driver as a module, choose M here: the module

2265

To compile this driver as a module, choose M here: the module

2266

will be called tsi108_eth.

2266

will be called tsi108_eth.

2267

2268

config GELIC_NET

2268

config GELIC_NET

2269

tristate "PS3 Gigabit Ethernet driver"

2269

tristate "PS3 Gigabit Ethernet driver"

2270

depends on PPC_PS3

2270

depends on PPC_PS3

2271

select PS3_SYS_MANAGER

2271

select PS3_SYS_MANAGER

2272

help

2272

help

2273

This driver supports the network device on the PS3 game

2273

This driver supports the network device on the PS3 game

2274

console. This driver has built-in support for Ethernet.

2274

console. This driver has built-in support for Ethernet.

2275

2276

To compile this driver as a module, choose M here: the

2276

To compile this driver as a module, choose M here: the

2277

module will be called ps3_gelic.

2277

module will be called ps3_gelic.

2278

2279

config GELIC_WIRELESS

2279

config GELIC_WIRELESS

2280

bool "PS3 Wireless support"

2280

bool "PS3 Wireless support"

2281

depends on GELIC_NET

2281

depends on GELIC_NET

2282

select WIRELESS_EXT

2282

select WIRELESS_EXT

2283

help

2283

help

2284

This option adds the support for the wireless feature of PS3.

2284

This option adds the support for the wireless feature of PS3.

2285

If you have the wireless-less model of PS3 or have no plan to

2285

If you have the wireless-less model of PS3 or have no plan to

2286

use wireless feature, disabling this option saves memory. As

2286

use wireless feature, disabling this option saves memory. As

2287

the driver automatically distinguishes the models, you can

2287

the driver automatically distinguishes the models, you can

2288

safely enable this option even if you have a wireless-less model.

2288

safely enable this option even if you have a wireless-less model.

2289

2290

config GELIC_WIRELESS_OLD_PSK_INTERFACE

2290

config GELIC_WIRELESS_OLD_PSK_INTERFACE

2291

bool "PS3 Wireless private PSK interface (OBSOLETE)"

2291

bool "PS3 Wireless private PSK interface (OBSOLETE)"

2292

depends on GELIC_WIRELESS

2292

depends on GELIC_WIRELESS

2293

help

2293

help

2294

This option retains the obsolete private interface to pass

2294

This option retains the obsolete private interface to pass

2295

the PSK from user space programs to the driver. The PSK

2295

the PSK from user space programs to the driver. The PSK

2296

stands for 'Pre Shared Key' and is used for WPA[2]-PSK

2296

stands for 'Pre Shared Key' and is used for WPA[2]-PSK

2297

(WPA-Personal) environment.

2297

(WPA-Personal) environment.

2298

If WPA[2]-PSK is used and you need to use old programs that

2298

If WPA[2]-PSK is used and you need to use old programs that

2299

support only this old interface, say Y. Otherwise N.

2299

support only this old interface, say Y. Otherwise N.

2300

2301

If unsure, say N.

2301

If unsure, say N.

2302

2303

config GIANFAR

2303

config GIANFAR

2304

tristate "Gianfar Ethernet"

2304

tristate "Gianfar Ethernet"

2305

depends on FSL_SOC

2305

depends on FSL_SOC

2306

select PHYLIB

2306

select PHYLIB

2307

select CRC32

2307

select CRC32

2308

help

2308

help

2309

This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,

2309

This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,

2310

and MPC86xx family of chips, and the FEC on the 8540.

2310

and MPC86xx family of chips, and the FEC on the 8540.

2311

2312

config GFAR_NAPI

2312

config GFAR_NAPI

2313

bool "Use Rx Polling (NAPI)"

2313

bool "Use Rx Polling (NAPI)"

2314

depends on GIANFAR

2314

depends on GIANFAR

2315

2316

config UCC_GETH

2316

config UCC_GETH

2317

tristate "Freescale QE Gigabit Ethernet"

2317

tristate "Freescale QE Gigabit Ethernet"

2318

depends on QUICC_ENGINE

2318

depends on QUICC_ENGINE

2319

select PHYLIB

2319

select PHYLIB

2320

help

2320

help

2321

This driver supports the Gigabit Ethernet mode of the QUICC Engine,

2321

This driver supports the Gigabit Ethernet mode of the QUICC Engine,

2322

which is available on some Freescale SOCs.

2322

which is available on some Freescale SOCs.

2323

2324

config UGETH_NAPI

2324

config UGETH_NAPI

2325

bool "Use Rx Polling (NAPI)"

2325

bool "Use Rx Polling (NAPI)"

2326

depends on UCC_GETH

2326

depends on UCC_GETH

2327

2328

config UGETH_MAGIC_PACKET

2328

config UGETH_MAGIC_PACKET

2329

bool "Magic Packet detection support"

2329

bool "Magic Packet detection support"

2330

depends on UCC_GETH

2330

depends on UCC_GETH

2331

2332

config UGETH_FILTERING

2332

config UGETH_FILTERING

2333

bool "Mac address filtering support"

2333

bool "Mac address filtering support"

2334

depends on UCC_GETH

2334

depends on UCC_GETH

2335

2336

config UGETH_TX_ON_DEMAND

2336

config UGETH_TX_ON_DEMAND

2337

bool "Transmit on Demand support"

2337

bool "Transmit on Demand support"

2338

depends on UCC_GETH

2338

depends on UCC_GETH

2339

2340

config MV643XX_ETH

2340

config MV643XX_ETH

2341

tristate "Marvell Discovery (643XX) and Orion ethernet support"

2341

tristate "Marvell Discovery (643XX) and Orion ethernet support"

2342

depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION

2342

depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION

2343

select MII

2343

select MII

2344

help

2344

help

2345

This driver supports the gigabit ethernet MACs in the

2345

This driver supports the gigabit ethernet MACs in the

2346

Marvell Discovery PPC/MIPS chipset family (MV643XX) and

2346

Marvell Discovery PPC/MIPS chipset family (MV643XX) and

2347

in the Marvell Orion ARM SoC family.

2347

in the Marvell Orion ARM SoC family.

2348

2349

Some boards that use the Discovery chipset are the Momenco

2349

Some boards that use the Discovery chipset are the Momenco

2350

Ocelot C and Jaguar ATX and Pegasos II.

2350

Ocelot C and Jaguar ATX and Pegasos II.

2351

2352

config QLA3XXX

2352

config QLA3XXX

2353

tristate "QLogic QLA3XXX Network Driver Support"

2353

tristate "QLogic QLA3XXX Network Driver Support"

2354

depends on PCI

2354

depends on PCI

2355

help

2355

help

2356

This driver supports QLogic ISP3XXX gigabit Ethernet cards.

2356

This driver supports QLogic ISP3XXX gigabit Ethernet cards.

2357

2358

To compile this driver as a module, choose M here: the module

2358

To compile this driver as a module, choose M here: the module

2359

will be called qla3xxx.

2359

will be called qla3xxx.

2360

2361

config ATL1

2361

config ATL1

2362

tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"

2362

tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"

2363

depends on PCI && EXPERIMENTAL

2363

depends on PCI && EXPERIMENTAL

2364

select CRC32

2364

select CRC32

2365

select MII

2365

select MII

2366

help

2366

help

2367

This driver supports the Attansic L1 gigabit ethernet adapter.

2367

This driver supports the Attansic L1 gigabit ethernet adapter.

2368

2369

To compile this driver as a module, choose M here. The module

2369

To compile this driver as a module, choose M here. The module

2370

will be called atl1.

2370

will be called atl1.

2371

2372

endif # NETDEV_1000

2372

endif # NETDEV_1000

2373

2374

#

2374

#

2375

# 10 Gigabit Ethernet

2375

# 10 Gigabit Ethernet

2376

#

2376

#

2377

2378

menuconfig NETDEV_10000

2378

menuconfig NETDEV_10000

2379

bool "Ethernet (10000 Mbit)"

2379

bool "Ethernet (10000 Mbit)"

2380

depends on !UML

2380

depends on !UML

2381

default y

2381

default y

2382

---help---

2382

---help---

2383

Say Y here to get to see options for 10 Gigabit Ethernet drivers.

2383

Say Y here to get to see options for 10 Gigabit Ethernet drivers.

2384

This option alone does not add any kernel code.

2384

This option alone does not add any kernel code.

2385

2386

If you say N, all options in this submenu will be skipped and disabled.

2386

If you say N, all options in this submenu will be skipped and disabled.

2387

2388

if NETDEV_10000

2388

if NETDEV_10000

2389

2390

config CHELSIO_T1

2390

config CHELSIO_T1

2391

tristate "Chelsio 10Gb Ethernet support"

2391

tristate "Chelsio 10Gb Ethernet support"

2392

depends on PCI

2392

depends on PCI

2393

select CRC32

2393

select CRC32

2394

help

2394

help

2395

This driver supports Chelsio gigabit and 10-gigabit

2395

This driver supports Chelsio gigabit and 10-gigabit

2396

Ethernet cards. More information about adapter features and

2396

Ethernet cards. More information about adapter features and

2397

performance tuning is in <file:Documentation/networking/cxgb.txt>.

2397

performance tuning is in <file:Documentation/networking/cxgb.txt>.

2398

2399

For general information about Chelsio and our products, visit

2399

For general information about Chelsio and our products, visit

2400

our website at <http://www.chelsio.com>.

2400

our website at <http://www.chelsio.com>.

2401

2402

For customer support, please visit our customer support page at

2402

For customer support, please visit our customer support page at

2403

<http://www.chelsio.com/support.htm>.

2403

<http://www.chelsio.com/support.htm>.

2404

2405

Please send feedback to <linux-bugs@chelsio.com>.

2405

Please send feedback to <linux-bugs@chelsio.com>.

2406

2407

To compile this driver as a module, choose M here: the module

2407

To compile this driver as a module, choose M here: the module

2408

will be called cxgb.

2408

will be called cxgb.

2409

2410

config CHELSIO_T1_1G

2410

config CHELSIO_T1_1G

2411

bool "Chelsio gigabit Ethernet support"

2411

bool "Chelsio gigabit Ethernet support"

2412

depends on CHELSIO_T1

2412

depends on CHELSIO_T1

2413

help

2413

help

2414

Enables support for Chelsio's gigabit Ethernet PCI cards. If you

2414

Enables support for Chelsio's gigabit Ethernet PCI cards. If you

2415

are using only 10G cards say 'N' here.

2415

are using only 10G cards say 'N' here.

2416

2417

config CHELSIO_T1_NAPI

2417

config CHELSIO_T1_NAPI

2418

bool "Use Rx Polling (NAPI)"

2418

bool "Use Rx Polling (NAPI)"

2419

depends on CHELSIO_T1

2419

depends on CHELSIO_T1

2420

default y

2420

default y

2421

help

2421

help

2422

NAPI is a driver API designed to reduce CPU and interrupt load

2422

NAPI is a driver API designed to reduce CPU and interrupt load

2423

when the driver is receiving lots of packets from the card.

2423

when the driver is receiving lots of packets from the card.

2424

2425

config CHELSIO_T3

2425

config CHELSIO_T3

2426

tristate "Chelsio Communications T3 10Gb Ethernet support"

2426

tristate "Chelsio Communications T3 10Gb Ethernet support"

2427

depends on PCI && INET

2427

depends on PCI && INET

2428

select FW_LOADER

2428

select FW_LOADER

2429

select INET_LRO

2429

select INET_LRO

2430

help

2430

help

2431

This driver supports Chelsio T3-based gigabit and 10Gb Ethernet

2431

This driver supports Chelsio T3-based gigabit and 10Gb Ethernet

2432

adapters.

2432

adapters.

2433

2434

For general information about Chelsio and our products, visit

2434

For general information about Chelsio and our products, visit

2435

our website at <http://www.chelsio.com>.

2435

our website at <http://www.chelsio.com>.

2436

2437

For customer support, please visit our customer support page at

2437

For customer support, please visit our customer support page at

2438

<http://www.chelsio.com/support.htm>.

2438

<http://www.chelsio.com/support.htm>.

2439

2440

Please send feedback to <linux-bugs@chelsio.com>.

2440

Please send feedback to <linux-bugs@chelsio.com>.

2441

2442

To compile this driver as a module, choose M here: the module

2442

To compile this driver as a module, choose M here: the module

2443

will be called cxgb3.

2443

will be called cxgb3.

2444

2445

config EHEA

2445

config EHEA

2446

tristate "eHEA Ethernet support"

2446

tristate "eHEA Ethernet support"

2447

depends on IBMEBUS && INET && SPARSEMEM

2447

depends on IBMEBUS && INET && SPARSEMEM

2448

select INET_LRO

2448

select INET_LRO

2449

---help---

2449

---help---

2450

This driver supports the IBM pSeries eHEA ethernet adapter.

2450

This driver supports the IBM pSeries eHEA ethernet adapter.

2451

2452

To compile the driver as a module, choose M here. The module

2452

To compile the driver as a module, choose M here. The module

2453

will be called ehea.

2453

will be called ehea.

2454

2455

config IXGBE

2455

config IXGBE

2456

tristate "Intel(R) 10GbE PCI Express adapters support"

2456

tristate "Intel(R) 10GbE PCI Express adapters support"

2457

depends on PCI && INET

2457

depends on PCI && INET

2458

select INET_LRO

2458

select INET_LRO

2459

---help---

2459

---help---

2460

This driver supports Intel(R) 10GbE PCI Express family of

2460

This driver supports Intel(R) 10GbE PCI Express family of

2461

adapters. For more information on how to identify your adapter, go

2461

adapters. For more information on how to identify your adapter, go

2462

to the Adapter & Driver ID Guide at:

2462

to the Adapter & Driver ID Guide at:

2463

2464

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

2464

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

2465

2466

For general information and support, go to the Intel support

2466

For general information and support, go to the Intel support

2467

website at:

2467

website at:

2468

2469

<http://support.intel.com>

2469

<http://support.intel.com>

2470

2471

To compile this driver as a module, choose M here. The module

2471

To compile this driver as a module, choose M here. The module

2472

will be called ixgbe.

2472

will be called ixgbe.

2473

2474

config IXGB

2474

config IXGB

2475

tristate "Intel(R) PRO/10GbE support"

2475

tristate "Intel(R) PRO/10GbE support"

2476

depends on PCI

2476

depends on PCI

2477

---help---

2477

---help---

2478

This driver supports Intel(R) PRO/10GbE family of adapters for

2478

This driver supports Intel(R) PRO/10GbE family of adapters for

2479

PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver

2479

PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver

2480

instead. For more information on how to identify your adapter, go

2480

instead. For more information on how to identify your adapter, go

2481

to the Adapter & Driver ID Guide at:

2481

to the Adapter & Driver ID Guide at:

2482

2483

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

2483

<http://support.intel.com/support/network/adapter/pro100/21397.htm>

2484

2485

For general information and support, go to the Intel support

2485

For general information and support, go to the Intel support

2486

website at:

2486

website at:

2487

2488

<http://support.intel.com>

2488

<http://support.intel.com>

2489

2490

More specific information on configuring the driver is in

2490

More specific information on configuring the driver is in

2491

<file:Documentation/networking/ixgb.txt>.

2491

<file:Documentation/networking/ixgb.txt>.

2492

2493

To compile this driver as a module, choose M here. The module

2493

To compile this driver as a module, choose M here. The module

2494

will be called ixgb.

2494

will be called ixgb.

2495

2496

config IXGB_NAPI

2496

config IXGB_NAPI

2497

bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"

2497

bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"

2498

depends on IXGB && EXPERIMENTAL

2498

depends on IXGB && EXPERIMENTAL

2499

help

2499

help

2500

NAPI is a new driver API designed to reduce CPU and interrupt load

2500

NAPI is a new driver API designed to reduce CPU and interrupt load

2501

when the driver is receiving lots of packets from the card. It is

2501

when the driver is receiving lots of packets from the card. It is

2502

still somewhat experimental and thus not yet enabled by default.

2502

still somewhat experimental and thus not yet enabled by default.

2503

2504

If your estimated Rx load is 10kpps or more, or if the card will be

2504

If your estimated Rx load is 10kpps or more, or if the card will be

2505

deployed on potentially unfriendly networks (e.g. in a firewall),

2505

deployed on potentially unfriendly networks (e.g. in a firewall),

2506

then say Y here.

2506

then say Y here.

2507

2508

If in doubt, say N.

2508

If in doubt, say N.

2509

2510

config S2IO

2510

config S2IO

2511

tristate "S2IO 10Gbe XFrame NIC"

2511

tristate "S2IO 10Gbe XFrame NIC"

2512

depends on PCI

2512

depends on PCI

2513

---help---

2513

---help---

2514

This driver supports the 10Gbe XFrame NIC of S2IO.

2514

This driver supports the 10Gbe XFrame NIC of S2IO.

2515

More specific information on configuring the driver is in

2515

More specific information on configuring the driver is in

2516

<file:Documentation/networking/s2io.txt>.

2516

<file:Documentation/networking/s2io.txt>.

2517

2518

config S2IO_NAPI

2519

bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"

2520

depends on S2IO && EXPERIMENTAL

2521

help

2522

NAPI is a new driver API designed to reduce CPU and interrupt load

2523

when the driver is receiving lots of packets from the card. It is

2524

still somewhat experimental and thus not yet enabled by default.

2525

2526

If your estimated Rx load is 10kpps or more, or if the card will be

2527

deployed on potentially unfriendly networks (e.g. in a firewall),

2528

then say Y here.

2529

2530

If in doubt, say N.

2531

2532

config MYRI10GE

2518

config MYRI10GE

2533

tristate "Myricom Myri-10G Ethernet support"

2519

tristate "Myricom Myri-10G Ethernet support"

2534

depends on PCI && INET

2520

depends on PCI && INET

2535

select FW_LOADER

2521

select FW_LOADER

2536

select CRC32

2522

select CRC32

2537

select INET_LRO

2523

select INET_LRO

2538

---help---

2524

---help---

2539

This driver supports Myricom Myri-10G Dual Protocol interface in

2525

This driver supports Myricom Myri-10G Dual Protocol interface in

2540

Ethernet mode. If the eeprom on your board is not recent enough,

2526

Ethernet mode. If the eeprom on your board is not recent enough,

2541

you will need a newer firmware image.

2527

you will need a newer firmware image.

2542

You may get this image or more information, at:

2528

You may get this image or more information, at:

2543

2529

2544

<http://www.myri.com/scs/download-Myri10GE.html>

2530

<http://www.myri.com/scs/download-Myri10GE.html>

2545

2531

2546

To compile this driver as a module, choose M here. The module

2532

To compile this driver as a module, choose M here. The module

2547

will be called myri10ge.

2533

will be called myri10ge.

2548

2534

2549

config NETXEN_NIC

2535

config NETXEN_NIC

2550

tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"

2536

tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"

2551

depends on PCI

2537

depends on PCI

2552

help

2538

help

2553

This enables the support for NetXen's Gigabit Ethernet card.

2539

This enables the support for NetXen's Gigabit Ethernet card.

2554

2540

2555

config NIU

2541

config NIU

2556

tristate "Sun Neptune 10Gbit Ethernet support"

2542

tristate "Sun Neptune 10Gbit Ethernet support"

2557

depends on PCI

2543

depends on PCI

2558

help

2544

help

2559

This enables support for cards based upon Sun's

2545

This enables support for cards based upon Sun's

2560

Neptune chipset.

2546

Neptune chipset.

2561

2547

2562

config PASEMI_MAC

2548

config PASEMI_MAC

2563

tristate "PA Semi 1/10Gbit MAC"

2549

tristate "PA Semi 1/10Gbit MAC"

2564

depends on PPC_PASEMI && PCI

2550

depends on PPC_PASEMI && PCI

2565

select PHYLIB

2551

select PHYLIB

2566

select INET_LRO

2552

select INET_LRO

2567

help

2553

help

2568

This driver supports the on-chip 1/10Gbit Ethernet controller on

2554

This driver supports the on-chip 1/10Gbit Ethernet controller on

2569

PA Semi's PWRficient line of chips.

2555

PA Semi's PWRficient line of chips.

2570

2556

2571

config MLX4_CORE

2557

config MLX4_CORE

2572

tristate

2558

tristate

2573

depends on PCI

2559

depends on PCI

2574

default n

2560

default n

2575

2561

2576

config MLX4_DEBUG

2562

config MLX4_DEBUG

2577

bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)

2563

bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)

2578

depends on MLX4_CORE

2564

depends on MLX4_CORE

2579

default y

2565

default y

2580

---help---

2566

---help---

2581

This option causes debugging code to be compiled into the

2567

This option causes debugging code to be compiled into the

2582

mlx4_core driver. The output can be turned on via the

2568

mlx4_core driver. The output can be turned on via the

2583

debug_level module parameter (which can also be set after

2569

debug_level module parameter (which can also be set after

2584

the driver is loaded through sysfs).

2570

the driver is loaded through sysfs).

2585

2571

2586

config TEHUTI

2572

config TEHUTI

2587

tristate "Tehuti Networks 10G Ethernet"

2573

tristate "Tehuti Networks 10G Ethernet"

2588

depends on PCI

2574

depends on PCI

2589

help

2575

help

2590

Tehuti Networks 10G Ethernet NIC

2576

Tehuti Networks 10G Ethernet NIC

2591

2577

2592

config BNX2X

2578

config BNX2X

2593

tristate "Broadcom NetXtremeII 10Gb support"

2579

tristate "Broadcom NetXtremeII 10Gb support"

2594

depends on PCI

2580

depends on PCI

2595

select ZLIB_INFLATE

2581

select ZLIB_INFLATE

2596

select LIBCRC32C

2582

select LIBCRC32C

2597

help

2583

help

2598

This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.

2584

This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.

2599

To compile this driver as a module, choose M here: the module

2585

To compile this driver as a module, choose M here: the module

2600

will be called bnx2x. This is recommended.

2586

will be called bnx2x. This is recommended.

2601

2587

2602

source "drivers/net/sfc/Kconfig"

2588

source "drivers/net/sfc/Kconfig"

2603

2589

2604

endif # NETDEV_10000

2590

endif # NETDEV_10000

2605

2591

2606

source "drivers/net/tokenring/Kconfig"

2592

source "drivers/net/tokenring/Kconfig"

2607

2593

2608

source "drivers/net/wireless/Kconfig"

2594

source "drivers/net/wireless/Kconfig"

2609

2595

2610

source "drivers/net/usb/Kconfig"

2596

source "drivers/net/usb/Kconfig"

2611

2597

2612

source "drivers/net/pcmcia/Kconfig"

2598

source "drivers/net/pcmcia/Kconfig"

2613

2599

2614

source "drivers/net/wan/Kconfig"

2600

source "drivers/net/wan/Kconfig"

2615

2601

2616

source "drivers/atm/Kconfig"

2602

source "drivers/atm/Kconfig"

2617

2603

2618

source "drivers/s390/net/Kconfig"

2604

source "drivers/s390/net/Kconfig"

2619

2605

2620

config XEN_NETDEV_FRONTEND

2606

config XEN_NETDEV_FRONTEND

2621

tristate "Xen network device frontend driver"

2607

tristate "Xen network device frontend driver"

2622

depends on XEN

2608

depends on XEN

2623

default y

2609

default y

2624

help

2610

help

2625

The network device frontend driver allows the kernel to

2611

The network device frontend driver allows the kernel to

2626

access network devices exported exported by a virtual

2612

access network devices exported exported by a virtual

2627

machine containing a physical network device driver. The

2613

machine containing a physical network device driver. The

2628

frontend driver is intended for unprivileged guest domains;

2614

frontend driver is intended for unprivileged guest domains;

2629

if you are compiling a kernel for a Xen guest, you almost

2615

if you are compiling a kernel for a Xen guest, you almost

2630

certainly want to enable this.

2616

certainly want to enable this.

2631

2617

2632

config ISERIES_VETH

2618

config ISERIES_VETH

2633

tristate "iSeries Virtual Ethernet driver support"

2619

tristate "iSeries Virtual Ethernet driver support"

2634

depends on PPC_ISERIES

2620

depends on PPC_ISERIES

2635

2621

2636

config RIONET

2622

config RIONET

2637

tristate "RapidIO Ethernet over messaging driver support"

2623

tristate "RapidIO Ethernet over messaging driver support"

2638

depends on RAPIDIO

2624

depends on RAPIDIO

2639

2625

2640

config RIONET_TX_SIZE

2626

config RIONET_TX_SIZE

2641

int "Number of outbound queue entries"

2627

int "Number of outbound queue entries"

2642

depends on RIONET

2628

depends on RIONET

2643

default "128"

2629

default "128"

2644

2630

2645

config RIONET_RX_SIZE

2631

config RIONET_RX_SIZE

2646

int "Number of inbound queue entries"

2632

int "Number of inbound queue entries"

2647

depends on RIONET

2633

depends on RIONET

2648

default "128"

2634

default "128"

2649

2635

2650

config FDDI

2636

config FDDI

2651

bool "FDDI driver support"

2637

bool "FDDI driver support"

2652

depends on (PCI || EISA || TC)

2638

depends on (PCI || EISA || TC)

2653

help

2639

help

2654

Fiber Distributed Data Interface is a high speed local area network

2640

Fiber Distributed Data Interface is a high speed local area network

2655

design; essentially a replacement for high speed Ethernet. FDDI can

2641

design; essentially a replacement for high speed Ethernet. FDDI can

2656

run over copper or fiber. If you are connected to such a network and

2642

run over copper or fiber. If you are connected to such a network and

2657

want a driver for the FDDI card in your computer, say Y here (and

2643

want a driver for the FDDI card in your computer, say Y here (and

2658

then also Y to the driver for your FDDI card, below). Most people

2644

then also Y to the driver for your FDDI card, below). Most people

2659

will say N.

2645

will say N.

2660

2646

2661

config DEFXX

2647

config DEFXX

2662

tristate "Digital DEFTA/DEFEA/DEFPA adapter support"

2648

tristate "Digital DEFTA/DEFEA/DEFPA adapter support"

2663

depends on FDDI && (PCI || EISA || TC)

2649

depends on FDDI && (PCI || EISA || TC)

2664

---help---

2650

---help---

2665

This is support for the DIGITAL series of TURBOchannel (DEFTA),

2651

This is support for the DIGITAL series of TURBOchannel (DEFTA),

2666

EISA (DEFEA) and PCI (DEFPA) controllers which can connect you

2652

EISA (DEFEA) and PCI (DEFPA) controllers which can connect you

2667

to a local FDDI network.

2653

to a local FDDI network.

2668

2654

2669

To compile this driver as a module, choose M here: the module

2655

To compile this driver as a module, choose M here: the module

2670

will be called defxx. If unsure, say N.

2656

will be called defxx. If unsure, say N.

2671

2657

2672

config DEFXX_MMIO

2658

config DEFXX_MMIO

2673

bool

2659

bool

2674

prompt "Use MMIO instead of PIO" if PCI || EISA

2660

prompt "Use MMIO instead of PIO" if PCI || EISA

2675

depends on DEFXX

2661

depends on DEFXX

2676

default n if PCI || EISA

2662

default n if PCI || EISA

2677

default y

2663

default y

2678

---help---

2664

---help---

2679

This instructs the driver to use EISA or PCI memory-mapped I/O

2665

This instructs the driver to use EISA or PCI memory-mapped I/O

2680

(MMIO) as appropriate instead of programmed I/O ports (PIO).

2666

(MMIO) as appropriate instead of programmed I/O ports (PIO).

2681

Enabling this gives an improvement in processing time in parts

2667

Enabling this gives an improvement in processing time in parts

2682

of the driver, but it may cause problems with EISA (DEFEA)

2668

of the driver, but it may cause problems with EISA (DEFEA)

2683

adapters. TURBOchannel does not have the concept of I/O ports,

2669

adapters. TURBOchannel does not have the concept of I/O ports,

2684

so MMIO is always used for these (DEFTA) adapters.

2670

so MMIO is always used for these (DEFTA) adapters.

2685

2671

2686

If unsure, say N.

2672

If unsure, say N.

2687

2673

2688

config SKFP

2674

config SKFP

2689

tristate "SysKonnect FDDI PCI support"

2675

tristate "SysKonnect FDDI PCI support"

2690

depends on FDDI && PCI

2676

depends on FDDI && PCI

2691

select BITREVERSE

2677

select BITREVERSE

2692

---help---

2678

---help---

2693

Say Y here if you have a SysKonnect FDDI PCI adapter.

2679

Say Y here if you have a SysKonnect FDDI PCI adapter.

2694

The following adapters are supported by this driver:

2680

The following adapters are supported by this driver:

2695

- SK-5521 (SK-NET FDDI-UP)

2681

- SK-5521 (SK-NET FDDI-UP)

2696

- SK-5522 (SK-NET FDDI-UP DAS)

2682

- SK-5522 (SK-NET FDDI-UP DAS)

2697

- SK-5541 (SK-NET FDDI-FP)

2683

- SK-5541 (SK-NET FDDI-FP)

2698

- SK-5543 (SK-NET FDDI-LP)

2684

- SK-5543 (SK-NET FDDI-LP)

2699

- SK-5544 (SK-NET FDDI-LP DAS)

2685

- SK-5544 (SK-NET FDDI-LP DAS)

2700

- SK-5821 (SK-NET FDDI-UP64)

2686

- SK-5821 (SK-NET FDDI-UP64)

2701

- SK-5822 (SK-NET FDDI-UP64 DAS)

2687

- SK-5822 (SK-NET FDDI-UP64 DAS)

2702

- SK-5841 (SK-NET FDDI-FP64)

2688

- SK-5841 (SK-NET FDDI-FP64)

2703

- SK-5843 (SK-NET FDDI-LP64)

2689

- SK-5843 (SK-NET FDDI-LP64)

2704

- SK-5844 (SK-NET FDDI-LP64 DAS)

2690

- SK-5844 (SK-NET FDDI-LP64 DAS)

2705

- Netelligent 100 FDDI DAS Fibre SC

2691

- Netelligent 100 FDDI DAS Fibre SC

2706

- Netelligent 100 FDDI SAS Fibre SC

2692

- Netelligent 100 FDDI SAS Fibre SC

2707

- Netelligent 100 FDDI DAS UTP

2693

- Netelligent 100 FDDI DAS UTP

2708

- Netelligent 100 FDDI SAS UTP

2694

- Netelligent 100 FDDI SAS UTP

2709

- Netelligent 100 FDDI SAS Fibre MIC

2695

- Netelligent 100 FDDI SAS Fibre MIC

2710

2696

2711

Read <file:Documentation/networking/skfp.txt> for information about

2697

Read <file:Documentation/networking/skfp.txt> for information about

2712

the driver.

2698

the driver.

2713

2699

2714

Questions concerning this driver can be addressed to:

2700

Questions concerning this driver can be addressed to:

2715

<linux@syskonnect.de>

2701

<linux@syskonnect.de>

2716

2702

2717

To compile this driver as a module, choose M here: the module

2703

To compile this driver as a module, choose M here: the module

2718

will be called skfp. This is recommended.

2704

will be called skfp. This is recommended.

2719

2705

2720

config HIPPI

2706

config HIPPI

2721

bool "HIPPI driver support (EXPERIMENTAL)"

2707

bool "HIPPI driver support (EXPERIMENTAL)"

2722

depends on EXPERIMENTAL && INET && PCI

2708

depends on EXPERIMENTAL && INET && PCI

2723

help

2709

help

2724

HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and

2710

HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and

2725

1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI

2711

1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI

2726

can run over copper (25m) or fiber (300m on multi-mode or 10km on

2712

can run over copper (25m) or fiber (300m on multi-mode or 10km on

2727

single-mode). HIPPI networks are commonly used for clusters and to

2713

single-mode). HIPPI networks are commonly used for clusters and to

2728

connect to super computers. If you are connected to a HIPPI network

2714

connect to super computers. If you are connected to a HIPPI network

2729

and have a HIPPI network card in your computer that you want to use

2715

and have a HIPPI network card in your computer that you want to use

2730

under Linux, say Y here (you must also remember to enable the driver

2716

under Linux, say Y here (you must also remember to enable the driver

2731

for your HIPPI card below). Most people will say N here.

2717

for your HIPPI card below). Most people will say N here.

2732

2718

2733

config ROADRUNNER

2719

config ROADRUNNER

2734

tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"

2720

tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"

2735

depends on HIPPI && PCI

2721

depends on HIPPI && PCI

2736

help

2722

help

2737

Say Y here if this is your PCI HIPPI network card.

2723

Say Y here if this is your PCI HIPPI network card.

2738

2724

2739

To compile this driver as a module, choose M here: the module

2725

To compile this driver as a module, choose M here: the module

2740

will be called rrunner. If unsure, say N.

2726

will be called rrunner. If unsure, say N.

2741

2727

2742

config ROADRUNNER_LARGE_RINGS

2728

config ROADRUNNER_LARGE_RINGS

2743

bool "Use large TX/RX rings (EXPERIMENTAL)"

2729

bool "Use large TX/RX rings (EXPERIMENTAL)"

2744

depends on ROADRUNNER

2730

depends on ROADRUNNER

2745

help

2731

help

2746

If you say Y here, the RoadRunner driver will preallocate up to 2 MB

2732

If you say Y here, the RoadRunner driver will preallocate up to 2 MB

2747

of additional memory to allow for fastest operation, both for

2733

of additional memory to allow for fastest operation, both for

2748

transmitting and receiving. This memory cannot be used by any other

2734

transmitting and receiving. This memory cannot be used by any other

2749

kernel code or by user space programs. Say Y here only if you have

2735

kernel code or by user space programs. Say Y here only if you have

2750

the memory.

2736

the memory.

2751

2737

2752

config PLIP

2738

config PLIP

2753

tristate "PLIP (parallel port) support"

2739

tristate "PLIP (parallel port) support"

2754

depends on PARPORT

2740

depends on PARPORT

2755

---help---

2741

---help---

2756

PLIP (Parallel Line Internet Protocol) is used to create a

2742

PLIP (Parallel Line Internet Protocol) is used to create a

2757

reasonably fast mini network consisting of two (or, rarely, more)

2743

reasonably fast mini network consisting of two (or, rarely, more)

2758

local machines. A PLIP link from a Linux box is a popular means to

2744

local machines. A PLIP link from a Linux box is a popular means to

2759

install a Linux distribution on a machine which doesn't have a

2745

install a Linux distribution on a machine which doesn't have a

2760

CD-ROM drive (a minimal system has to be transferred with floppies

2746

CD-ROM drive (a minimal system has to be transferred with floppies

2761

first). The kernels on both machines need to have this PLIP option

2747

first). The kernels on both machines need to have this PLIP option

2762

enabled for this to work.

2748

enabled for this to work.

2763

2749

2764

The PLIP driver has two modes, mode 0 and mode 1. The parallel

2750

The PLIP driver has two modes, mode 0 and mode 1. The parallel

2765

ports (the connectors at the computers with 25 holes) are connected

2751

ports (the connectors at the computers with 25 holes) are connected

2766

with "null printer" or "Turbo Laplink" cables which can transmit 4

2752

with "null printer" or "Turbo Laplink" cables which can transmit 4

2767

bits at a time (mode 0) or with special PLIP cables, to be used on

2753

bits at a time (mode 0) or with special PLIP cables, to be used on

2768

bidirectional parallel ports only, which can transmit 8 bits at a

2754

bidirectional parallel ports only, which can transmit 8 bits at a

2769

time (mode 1); you can find the wiring of these cables in

2755

time (mode 1); you can find the wiring of these cables in

2770

<file:Documentation/networking/PLIP.txt>. The cables can be up to

2756

<file:Documentation/networking/PLIP.txt>. The cables can be up to

2771

15m long. Mode 0 works also if one of the machines runs DOS/Windows

2757

15m long. Mode 0 works also if one of the machines runs DOS/Windows

2772

and has some PLIP software installed, e.g. the Crynwr PLIP packet

2758

and has some PLIP software installed, e.g. the Crynwr PLIP packet

2773

driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)

2759

driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)

2774

and winsock or NCSA's telnet.

2760

and winsock or NCSA's telnet.

2775

2761

2776

If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well

2762

If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well

2777

as the NET-3-HOWTO, both available from

2763

as the NET-3-HOWTO, both available from

2778

<http://www.tldp.org/docs.html#howto>. Note that the PLIP

2764

<http://www.tldp.org/docs.html#howto>. Note that the PLIP

2779

protocol has been changed and this PLIP driver won't work together

2765

protocol has been changed and this PLIP driver won't work together

2780

with the PLIP support in Linux versions 1.0.x. This option enlarges

2766

with the PLIP support in Linux versions 1.0.x. This option enlarges

2781

your kernel by about 8 KB.

2767

your kernel by about 8 KB.

2782

2768

2783

To compile this driver as a module, choose M here. The module

2769

To compile this driver as a module, choose M here. The module

2784

will be called plip. If unsure, say Y or M, in case you buy

2770

will be called plip. If unsure, say Y or M, in case you buy

2785

a laptop later.

2771

a laptop later.

2786

2772

2787

config PPP

2773

config PPP

2788

tristate "PPP (point-to-point protocol) support"

2774

tristate "PPP (point-to-point protocol) support"

2789

select SLHC

2775

select SLHC

2790

---help---

2776

---help---

2791

PPP (Point to Point Protocol) is a newer and better SLIP. It serves

2777

PPP (Point to Point Protocol) is a newer and better SLIP. It serves

2792

the same purpose: sending Internet traffic over telephone (and other

2778

the same purpose: sending Internet traffic over telephone (and other

2793

serial) lines. Ask your access provider if they support it, because

2779

serial) lines. Ask your access provider if they support it, because

2794

otherwise you can't use it; most Internet access providers these

2780

otherwise you can't use it; most Internet access providers these

2795

days support PPP rather than SLIP.

2781

days support PPP rather than SLIP.

2796

2782

2797

To use PPP, you need an additional program called pppd as described

2783

To use PPP, you need an additional program called pppd as described

2798

in the PPP-HOWTO, available at

2784

in the PPP-HOWTO, available at

2799

<http://www.tldp.org/docs.html#howto>. Make sure that you have

2785

<http://www.tldp.org/docs.html#howto>. Make sure that you have

2800

the version of pppd recommended in <file:Documentation/Changes>.

2786

the version of pppd recommended in <file:Documentation/Changes>.

2801

The PPP option enlarges your kernel by about 16 KB.

2787

The PPP option enlarges your kernel by about 16 KB.

2802

2788

2803

There are actually two versions of PPP: the traditional PPP for

2789

There are actually two versions of PPP: the traditional PPP for

2804

asynchronous lines, such as regular analog phone lines, and

2790

asynchronous lines, such as regular analog phone lines, and

2805

synchronous PPP which can be used over digital ISDN lines for

2791

synchronous PPP which can be used over digital ISDN lines for

2806

example. If you want to use PPP over phone lines or other

2792

example. If you want to use PPP over phone lines or other

2807

asynchronous serial lines, you need to say Y (or M) here and also to

2793

asynchronous serial lines, you need to say Y (or M) here and also to

2808

the next option, "PPP support for async serial ports". For PPP over

2794

the next option, "PPP support for async serial ports". For PPP over

2809

synchronous lines, you should say Y (or M) here and to "Support

2795

synchronous lines, you should say Y (or M) here and to "Support

2810

synchronous PPP", below.

2796

synchronous PPP", below.

2811

2797

2812

If you said Y to "Version information on all symbols" above, then

2798

If you said Y to "Version information on all symbols" above, then

2813

you cannot compile the PPP driver into the kernel; you can then only

2799

you cannot compile the PPP driver into the kernel; you can then only

2814

compile it as a module. To compile this driver as a module, choose M

2800

compile it as a module. To compile this driver as a module, choose M

2815

here. The module will be called ppp_generic.

2801

here. The module will be called ppp_generic.

2816

2802

2817

config PPP_MULTILINK

2803

config PPP_MULTILINK

2818

bool "PPP multilink support (EXPERIMENTAL)"

2804

bool "PPP multilink support (EXPERIMENTAL)"

2819

depends on PPP && EXPERIMENTAL

2805

depends on PPP && EXPERIMENTAL

2820

help

2806

help

2821

PPP multilink is a protocol (defined in RFC 1990) which allows you

2807

PPP multilink is a protocol (defined in RFC 1990) which allows you

2822

to combine several (logical or physical) lines into one logical PPP

2808

to combine several (logical or physical) lines into one logical PPP

2823

connection, so that you can utilize your full bandwidth.

2809

connection, so that you can utilize your full bandwidth.

2824

2810

2825

This has to be supported at the other end as well and you need a

2811

This has to be supported at the other end as well and you need a

2826

version of the pppd daemon which understands the multilink protocol.

2812

version of the pppd daemon which understands the multilink protocol.

2827

2813

2828

If unsure, say N.

2814

If unsure, say N.

2829

2815

2830

config PPP_FILTER

2816

config PPP_FILTER

2831

bool "PPP filtering"

2817

bool "PPP filtering"

2832

depends on PPP

2818

depends on PPP

2833

help

2819

help

2834

Say Y here if you want to be able to filter the packets passing over

2820

Say Y here if you want to be able to filter the packets passing over

2835

PPP interfaces. This allows you to control which packets count as

2821

PPP interfaces. This allows you to control which packets count as

2836

activity (i.e. which packets will reset the idle timer or bring up

2822

activity (i.e. which packets will reset the idle timer or bring up

2837

a demand-dialed link) and which packets are to be dropped entirely.

2823

a demand-dialed link) and which packets are to be dropped entirely.

2838

You need to say Y here if you wish to use the pass-filter and

2824

You need to say Y here if you wish to use the pass-filter and

2839

active-filter options to pppd.

2825

active-filter options to pppd.

2840

2826

2841

If unsure, say N.

2827

If unsure, say N.

2842

2828

2843

config PPP_ASYNC

2829

config PPP_ASYNC

2844

tristate "PPP support for async serial ports"

2830

tristate "PPP support for async serial ports"

2845

depends on PPP

2831

depends on PPP

2846

select CRC_CCITT

2832

select CRC_CCITT

2847

---help---

2833

---help---

2848

Say Y (or M) here if you want to be able to use PPP over standard

2834

Say Y (or M) here if you want to be able to use PPP over standard

2849

asynchronous serial ports, such as COM1 or COM2 on a PC. If you use

2835

asynchronous serial ports, such as COM1 or COM2 on a PC. If you use

2850

a modem (not a synchronous or ISDN modem) to contact your ISP, you

2836

a modem (not a synchronous or ISDN modem) to contact your ISP, you

2851

need this option.

2837

need this option.

2852

2838

2853

To compile this driver as a module, choose M here.

2839

To compile this driver as a module, choose M here.

2854

2840

2855

If unsure, say Y.

2841

If unsure, say Y.

2856

2842

2857

config PPP_SYNC_TTY

2843

config PPP_SYNC_TTY

2858

tristate "PPP support for sync tty ports"

2844

tristate "PPP support for sync tty ports"

2859

depends on PPP

2845

depends on PPP

2860

help

2846

help

2861

Say Y (or M) here if you want to be able to use PPP over synchronous

2847

Say Y (or M) here if you want to be able to use PPP over synchronous

2862

(HDLC) tty devices, such as the SyncLink adapter. These devices

2848

(HDLC) tty devices, such as the SyncLink adapter. These devices

2863

are often used for high-speed leased lines like T1/E1.

2849

are often used for high-speed leased lines like T1/E1.

2864

2850

2865

To compile this driver as a module, choose M here.

2851

To compile this driver as a module, choose M here.

2866

2852

2867

config PPP_DEFLATE

2853

config PPP_DEFLATE

2868

tristate "PPP Deflate compression"

2854

tristate "PPP Deflate compression"

2869

depends on PPP

2855

depends on PPP

2870

select ZLIB_INFLATE

2856

select ZLIB_INFLATE

2871

select ZLIB_DEFLATE

2857

select ZLIB_DEFLATE

2872

---help---

2858

---help---

2873

Support for the Deflate compression method for PPP, which uses the

2859

Support for the Deflate compression method for PPP, which uses the

2874

Deflate algorithm (the same algorithm that gzip uses) to compress

2860

Deflate algorithm (the same algorithm that gzip uses) to compress

2875

each PPP packet before it is sent over the wire. The machine at the

2861

each PPP packet before it is sent over the wire. The machine at the

2876

other end of the PPP link (usually your ISP) has to support the

2862

other end of the PPP link (usually your ISP) has to support the

2877

Deflate compression method as well for this to be useful. Even if

2863

Deflate compression method as well for this to be useful. Even if

2878

they don't support it, it is safe to say Y here.

2864

they don't support it, it is safe to say Y here.

2879

2865

2880

To compile this driver as a module, choose M here.

2866

To compile this driver as a module, choose M here.

2881

2867

2882

config PPP_BSDCOMP

2868

config PPP_BSDCOMP

2883

tristate "PPP BSD-Compress compression"

2869

tristate "PPP BSD-Compress compression"

2884

depends on PPP

2870

depends on PPP

2885

---help---

2871

---help---

2886

Support for the BSD-Compress compression method for PPP, which uses

2872

Support for the BSD-Compress compression method for PPP, which uses

2887

the LZW compression method to compress each PPP packet before it is

2873

the LZW compression method to compress each PPP packet before it is

2888

sent over the wire. The machine at the other end of the PPP link

2874

sent over the wire. The machine at the other end of the PPP link

2889

(usually your ISP) has to support the BSD-Compress compression

2875

(usually your ISP) has to support the BSD-Compress compression

2890

method as well for this to be useful. Even if they don't support it,

2876

method as well for this to be useful. Even if they don't support it,

2891

it is safe to say Y here.

2877

it is safe to say Y here.

2892

2878

2893

The PPP Deflate compression method ("PPP Deflate compression",

2879

The PPP Deflate compression method ("PPP Deflate compression",

2894

above) is preferable to BSD-Compress, because it compresses better

2880

above) is preferable to BSD-Compress, because it compresses better

2895

and is patent-free.

2881

and is patent-free.

2896

2882

2897

Note that the BSD compression code will always be compiled as a

2883

Note that the BSD compression code will always be compiled as a

2898

module; it is called bsd_comp and will show up in the directory

2884

module; it is called bsd_comp and will show up in the directory

2899

modules once you have said "make modules". If unsure, say N.

2885

modules once you have said "make modules". If unsure, say N.

2900

2886

2901

config PPP_MPPE

2887

config PPP_MPPE

2902

tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"

2888

tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"

2903

depends on PPP && EXPERIMENTAL

2889

depends on PPP && EXPERIMENTAL

2904

select CRYPTO

2890

select CRYPTO

2905

select CRYPTO_SHA1

2891

select CRYPTO_SHA1

2906

select CRYPTO_ARC4

2892

select CRYPTO_ARC4

2907

select CRYPTO_ECB

2893

select CRYPTO_ECB

2908

---help---

2894

---help---

2909

Support for the MPPE Encryption protocol, as employed by the

2895

Support for the MPPE Encryption protocol, as employed by the

2910

Microsoft Point-to-Point Tunneling Protocol.

2896

Microsoft Point-to-Point Tunneling Protocol.

2911

2897

2912

See http://pptpclient.sourceforge.net/ for information on

2898

See http://pptpclient.sourceforge.net/ for information on

2913

configuring PPTP clients and servers to utilize this method.

2899

configuring PPTP clients and servers to utilize this method.

2914

2900

2915

config PPPOE

2901

config PPPOE

2916

tristate "PPP over Ethernet (EXPERIMENTAL)"

2902

tristate "PPP over Ethernet (EXPERIMENTAL)"

2917

depends on EXPERIMENTAL && PPP

2903

depends on EXPERIMENTAL && PPP

2918

help

2904

help

2919

Support for PPP over Ethernet.

2905

Support for PPP over Ethernet.

2920

2906

2921

This driver requires the latest version of pppd from the CVS

2907

This driver requires the latest version of pppd from the CVS

2922

repository at cvs.samba.org. Alternatively, see the

2908

repository at cvs.samba.org. Alternatively, see the

2923

RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)

2909

RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)

2924

which contains instruction on how to use this driver (under

2910

which contains instruction on how to use this driver (under

2925

the heading "Kernel mode PPPoE").

2911

the heading "Kernel mode PPPoE").

2926

2912

2927

config PPPOATM

2913

config PPPOATM

2928

tristate "PPP over ATM"

2914

tristate "PPP over ATM"

2929

depends on ATM && PPP

2915

depends on ATM && PPP

2930

help

2916

help

2931

Support PPP (Point to Point Protocol) encapsulated in ATM frames.

2917

Support PPP (Point to Point Protocol) encapsulated in ATM frames.

2932

This implementation does not yet comply with section 8 of RFC2364,

2918

This implementation does not yet comply with section 8 of RFC2364,

2933

which can lead to bad results if the ATM peer loses state and

2919

which can lead to bad results if the ATM peer loses state and

2934

changes its encapsulation unilaterally.

2920

changes its encapsulation unilaterally.

2935

2921

2936

config PPPOL2TP

2922

config PPPOL2TP

2937

tristate "PPP over L2TP (EXPERIMENTAL)"

2923

tristate "PPP over L2TP (EXPERIMENTAL)"

2938

depends on EXPERIMENTAL && PPP && INET

2924

depends on EXPERIMENTAL && PPP && INET

2939

help

2925

help

2940

Support for PPP-over-L2TP socket family. L2TP is a protocol

2926

Support for PPP-over-L2TP socket family. L2TP is a protocol

2941

used by ISPs and enterprises to tunnel PPP traffic over UDP

2927

used by ISPs and enterprises to tunnel PPP traffic over UDP

2942

tunnels. L2TP is replacing PPTP for VPN uses.

2928

tunnels. L2TP is replacing PPTP for VPN uses.

2943

2929

2944

This kernel component handles only L2TP data packets: a

2930

This kernel component handles only L2TP data packets: a

2945

userland daemon handles L2TP the control protocol (tunnel

2931

userland daemon handles L2TP the control protocol (tunnel

2946

and session setup). One such daemon is OpenL2TP

2932

and session setup). One such daemon is OpenL2TP

2947

(http://openl2tp.sourceforge.net/).

2933

(http://openl2tp.sourceforge.net/).

2948

2934

2949

config SLIP

2935

config SLIP

2950

tristate "SLIP (serial line) support"

2936

tristate "SLIP (serial line) support"

2951

---help---

2937

---help---

2952

Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to

2938

Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to

2953

connect to your Internet service provider or to connect to some

2939

connect to your Internet service provider or to connect to some

2954

other local Unix box or if you want to configure your Linux box as a

2940

other local Unix box or if you want to configure your Linux box as a

2955

Slip/CSlip server for other people to dial in. SLIP (Serial Line

2941

Slip/CSlip server for other people to dial in. SLIP (Serial Line

2956

Internet Protocol) is a protocol used to send Internet traffic over

2942

Internet Protocol) is a protocol used to send Internet traffic over

2957

serial connections such as telephone lines or null modem cables;

2943

serial connections such as telephone lines or null modem cables;

2958

nowadays, the protocol PPP is more commonly used for this same

2944

nowadays, the protocol PPP is more commonly used for this same

2959

purpose.

2945

purpose.

2960

2946

2961

Normally, your access provider has to support SLIP in order for you

2947

Normally, your access provider has to support SLIP in order for you

2962

to be able to use it, but there is now a SLIP emulator called SLiRP

2948

to be able to use it, but there is now a SLIP emulator called SLiRP

2963

around (available from

2949

around (available from

2964

<ftp://ibiblio.org/pub/Linux/system/network/serial/>) which

2950

<ftp://ibiblio.org/pub/Linux/system/network/serial/>) which

2965

allows you to use SLIP over a regular dial up shell connection. If

2951

allows you to use SLIP over a regular dial up shell connection. If

2966

you plan to use SLiRP, make sure to say Y to CSLIP, below. The

2952

you plan to use SLiRP, make sure to say Y to CSLIP, below. The

2967

NET-3-HOWTO, available from

2953

NET-3-HOWTO, available from

2968

<http://www.tldp.org/docs.html#howto>, explains how to

2954

<http://www.tldp.org/docs.html#howto>, explains how to

2969

configure SLIP. Note that you don't need this option if you just

2955

configure SLIP. Note that you don't need this option if you just

2970

want to run term (term is a program which gives you almost full

2956

want to run term (term is a program which gives you almost full

2971

Internet connectivity if you have a regular dial up shell account on

2957

Internet connectivity if you have a regular dial up shell account on

2972

some Internet connected Unix computer. Read

2958

some Internet connected Unix computer. Read

2973

<http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP

2959

<http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP

2974

support will enlarge your kernel by about 4 KB. If unsure, say N.

2960

support will enlarge your kernel by about 4 KB. If unsure, say N.

2975

2961

2976

To compile this driver as a module, choose M here. The module

2962

To compile this driver as a module, choose M here. The module

2977

will be called slip.

2963

will be called slip.

2978

2964

2979

config SLIP_COMPRESSED

2965

config SLIP_COMPRESSED

2980

bool "CSLIP compressed headers"

2966

bool "CSLIP compressed headers"

2981

depends on SLIP

2967

depends on SLIP

2982

select SLHC

2968

select SLHC

2983

---help---

2969

---help---

2984

This protocol is faster than SLIP because it uses compression on the

2970

This protocol is faster than SLIP because it uses compression on the

2985

TCP/IP headers (not on the data itself), but it has to be supported

2971

TCP/IP headers (not on the data itself), but it has to be supported

2986

on both ends. Ask your access provider if you are not sure and

2972

on both ends. Ask your access provider if you are not sure and

2987

answer Y, just in case. You will still be able to use plain SLIP. If

2973

answer Y, just in case. You will still be able to use plain SLIP. If

2988

you plan to use SLiRP, the SLIP emulator (available from

2974

you plan to use SLiRP, the SLIP emulator (available from

2989

<ftp://ibiblio.org/pub/Linux/system/network/serial/>) which

2975

<ftp://ibiblio.org/pub/Linux/system/network/serial/>) which

2990

allows you to use SLIP over a regular dial up shell connection, you

2976

allows you to use SLIP over a regular dial up shell connection, you

2991

definitely want to say Y here. The NET-3-HOWTO, available from

2977

definitely want to say Y here. The NET-3-HOWTO, available from

2992

<http://www.tldp.org/docs.html#howto>, explains how to configure

2978

<http://www.tldp.org/docs.html#howto>, explains how to configure

2993

CSLIP. This won't enlarge your kernel.

2979

CSLIP. This won't enlarge your kernel.

2994

2980

2995

config SLHC

2981

config SLHC

2996

tristate

2982

tristate

2997

help

2983

help

2998

This option enables Van Jacobsen serial line header compression

2984

This option enables Van Jacobsen serial line header compression

2999

routines.

2985

routines.

3000

2986

3001

config SLIP_SMART

2987

config SLIP_SMART

3002

bool "Keepalive and linefill"

2988

bool "Keepalive and linefill"

3003

depends on SLIP

2989

depends on SLIP

3004

help

2990

help

3005

Adds additional capabilities to the SLIP driver to support the

2991

Adds additional capabilities to the SLIP driver to support the

3006

RELCOM line fill and keepalive monitoring. Ideal on poor quality

2992

RELCOM line fill and keepalive monitoring. Ideal on poor quality

3007

analogue lines.

2993

analogue lines.

3008

2994

3009

config SLIP_MODE_SLIP6

2995

config SLIP_MODE_SLIP6

3010

bool "Six bit SLIP encapsulation"

2996

bool "Six bit SLIP encapsulation"

3011

depends on SLIP

2997

depends on SLIP

3012

help

2998

help

3013

Just occasionally you may need to run IP over hostile serial

2999

Just occasionally you may need to run IP over hostile serial

3014

networks that don't pass all control characters or are only seven

3000

networks that don't pass all control characters or are only seven

3015

bit. Saying Y here adds an extra mode you can use with SLIP:

3001

bit. Saying Y here adds an extra mode you can use with SLIP:

3016

"slip6". In this mode, SLIP will only send normal ASCII symbols over

3002

"slip6". In this mode, SLIP will only send normal ASCII symbols over

3017

the serial device. Naturally, this has to be supported at the other

3003

the serial device. Naturally, this has to be supported at the other

3018

end of the link as well. It's good enough, for example, to run IP

3004

end of the link as well. It's good enough, for example, to run IP

3019

over the async ports of a Camtec JNT Pad. If unsure, say N.

3005

over the async ports of a Camtec JNT Pad. If unsure, say N.

3020

3006

3021

config NET_FC

3007

config NET_FC

3022

bool "Fibre Channel driver support"

3008

bool "Fibre Channel driver support"

3023

depends on SCSI && PCI

3009

depends on SCSI && PCI

3024

help

3010

help

3025

Fibre Channel is a high speed serial protocol mainly used to connect

3011

Fibre Channel is a high speed serial protocol mainly used to connect

3026

large storage devices to the computer; it is compatible with and

3012

large storage devices to the computer; it is compatible with and

3027

intended to replace SCSI.

3013

intended to replace SCSI.

3028

3014

3029

If you intend to use Fibre Channel, you need to have a Fibre channel

3015

If you intend to use Fibre Channel, you need to have a Fibre channel

3030

adaptor card in your computer; say Y here and to the driver for your

3016

adaptor card in your computer; say Y here and to the driver for your

3031

adaptor below. You also should have said Y to "SCSI support" and

3017

adaptor below. You also should have said Y to "SCSI support" and

3032

"SCSI generic support".

3018

"SCSI generic support".

3033

3019

3034

config NETCONSOLE

3020

config NETCONSOLE

3035

tristate "Network console logging support (EXPERIMENTAL)"

3021

tristate "Network console logging support (EXPERIMENTAL)"

3036

depends on EXPERIMENTAL

3022

depends on EXPERIMENTAL

3037

---help---

3023

---help---

3038

If you want to log kernel messages over the network, enable this.

3024

If you want to log kernel messages over the network, enable this.

3039

See <file:Documentation/networking/netconsole.txt> for details.

3025

See <file:Documentation/networking/netconsole.txt> for details.

3040

3026

3041

config NETCONSOLE_DYNAMIC

3027

config NETCONSOLE_DYNAMIC

3042

bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"

3028

bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"

3043

depends on NETCONSOLE && SYSFS && EXPERIMENTAL

3029

depends on NETCONSOLE && SYSFS && EXPERIMENTAL

3044

select CONFIGFS_FS

3030

select CONFIGFS_FS

3045

help

3031

help

3046

This option enables the ability to dynamically reconfigure target

3032

This option enables the ability to dynamically reconfigure target

3047

parameters (interface, IP addresses, port numbers, MAC addresses)

3033

parameters (interface, IP addresses, port numbers, MAC addresses)

3048

at runtime through a userspace interface exported using configfs.

3034

at runtime through a userspace interface exported using configfs.

3049

See <file:Documentation/networking/netconsole.txt> for details.

3035

See <file:Documentation/networking/netconsole.txt> for details.

3050

3036

3051

config NETPOLL

3037

config NETPOLL

3052

def_bool NETCONSOLE

3038

def_bool NETCONSOLE

3053

3039

3054

config NETPOLL_TRAP

3040

config NETPOLL_TRAP

3055

bool "Netpoll traffic trapping"

3041

bool "Netpoll traffic trapping"

3056

default n

3042

default n

3057

depends on NETPOLL

3043

depends on NETPOLL

3058

3044

3059

config NET_POLL_CONTROLLER

3045

config NET_POLL_CONTROLLER

3060

def_bool NETPOLL

3046

def_bool NETPOLL

3061

3047

3062

config VIRTIO_NET

3048

config VIRTIO_NET

3063

tristate "Virtio network driver (EXPERIMENTAL)"

3049

tristate "Virtio network driver (EXPERIMENTAL)"

3064

depends on EXPERIMENTAL && VIRTIO

3050

depends on EXPERIMENTAL && VIRTIO

3065

---help---

3051

---help---

3066

This is the virtual network driver for virtio. It can be used with

3052

This is the virtual network driver for virtio. It can be used with

3067

lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.

3053

lguest or QEMU based VMMs (like KVM or Xen). Say Y or M.

3068

3054

3069

endif # NETDEVICES

3055

endif # NETDEVICES

3070

3056

GITLAB

netdev: remove unused S2IO_NAPI

 Release notes for Neterion's (Formerly S2io) Xframe I/II PCI-X 10GbE driver.
 Contents
 =======
 - 1.  Introduction
 - 2.  Identifying the adapter/interface
 - 3.  Features supported
 - 4.  Command line parameters
 - 5.  Performance suggestions
 - 6.  Available Downloads
 1.	Introduction:
 This Linux driver supports Neterion's Xframe I PCI-X 1.0 and
 Xframe II PCI-X 2.0 adapters. It supports several features
 such as jumbo frames, MSI/MSI-X, checksum offloads, TSO, UFO and so on.
 See below for complete list of features.
 All features are supported for both IPv4 and IPv6.
 2.	Identifying the adapter/interface:
 a. Insert the adapter(s) in your system.
 b. Build and load driver
 # insmod s2io.ko
 c. View log messages
 # dmesg | tail -40
 You will see messages similar to:
 eth3: Neterion Xframe I 10GbE adapter (rev 3), Version 2.0.9.1, Intr type INTA
 eth4: Neterion Xframe II 10GbE adapter (rev 2), Version 2.0.9.1, Intr type INTA
 eth4: Device is on 64 bit 133MHz PCIX(M1) bus
 The above messages identify the adapter type(Xframe I/II), adapter revision,
 driver version, interface name(eth3, eth4), Interrupt type(INTA, MSI, MSI-X).
 In case of Xframe II, the PCI/PCI-X bus width and frequency are displayed
 as well.
 To associate an interface with a physical adapter use "ethtool -p <ethX>".
 The corresponding adapter's LED will blink multiple times.
 3.	Features supported:
 a. Jumbo frames. Xframe I/II supports MTU upto 9600 bytes,
 modifiable using ifconfig command.
 b. Offloads. Supports checksum offload(TCP/UDP/IP) on transmit
 and receive, TSO.
 c. Multi-buffer receive mode. Scattering of packet across multiple
 buffers. Currently driver supports 2-buffer mode which yields
 significant performance improvement on certain platforms(SGI Altix,
 IBM xSeries).
 d. MSI/MSI-X. Can be enabled on platforms which support this feature
 (IA64, Xeon) resulting in noticeable performance improvement(upto 7%
 on certain platforms).
-e. NAPI. Compile-time option(CONFIG_S2IO_NAPI) for better Rx interrupt
+e. Statistics. Comprehensive MAC-level and software statistics displayed
-moderation.
-f. Statistics. Comprehensive MAC-level and software statistics displayed
 using "ethtool -S" option.
-g. Multi-FIFO/Ring. Supports up to 8 transmit queues and receive rings,
+f. Multi-FIFO/Ring. Supports up to 8 transmit queues and receive rings,
 with multiple steering options.
 4.  Command line parameters
 a. tx_fifo_num
 Number of transmit queues
 Valid range: 1-8
 Default: 1
 b. rx_ring_num
 Number of receive rings
 Valid range: 1-8
 Default: 1
 c. tx_fifo_len
 Size of each transmit queue
 Valid range: Total length of all queues should not exceed 8192
 Default: 4096
 d. rx_ring_sz
 Size of each receive ring(in 4K blocks)
 Valid range: Limited by memory on system
 Default: 30
 e. intr_type
 Specifies interrupt type. Possible values 0(INTA), 2(MSI-X)
 Valid values: 0, 2
 Default: 2
 5.  Performance suggestions
 General:
 a. Set MTU to maximum(9000 for switch setup, 9600 in back-to-back configuration)
 b. Set TCP windows size to optimal value.
 For instance, for MTU=1500 a value of 210K has been observed to result in
 good performance.
 # sysctl -w net.ipv4.tcp_rmem="210000 210000 210000"
 # sysctl -w net.ipv4.tcp_wmem="210000 210000 210000"
 For MTU=9000, TCP window size of 10 MB is recommended.
 # sysctl -w net.ipv4.tcp_rmem="10000000 10000000 10000000"
 # sysctl -w net.ipv4.tcp_wmem="10000000 10000000 10000000"
 Transmit performance:
 a. By default, the driver respects BIOS settings for PCI bus parameters.
 However, you may want to experiment with PCI bus parameters
 max-split-transactions(MOST) and MMRBC (use setpci command).
 A MOST value of 2 has been found optimal for Opterons and 3 for Itanium.
 It could be different for your hardware.
 Set MMRBC to 4K**.
 For example you can set
 For opteron
 #setpci -d 17d5:* 62=1d
 For Itanium
 #setpci -d 17d5:* 62=3d
 For detailed description of the PCI registers, please see Xframe User Guide.
 b. Ensure Transmit Checksum offload is enabled. Use ethtool to set/verify this
 parameter.
 c. Turn on TSO(using "ethtool -K")
 # ethtool -K <ethX> tso on
 Receive performance:
 a. By default, the driver respects BIOS settings for PCI bus parameters.
 However, you may want to set PCI latency timer to 248.
 #setpci -d 17d5:* LATENCY_TIMER=f8
 For detailed description of the PCI registers, please see Xframe User Guide.
 b. Use 2-buffer mode. This results in large performance boost on
 certain platforms(eg. SGI Altix, IBM xSeries).
 c. Ensure Receive Checksum offload is enabled. Use "ethtool -K ethX" command to
 set/verify this option.
 d. Enable NAPI feature(in kernel configuration Device Drivers ---> Network
 device support --->  Ethernet (10000 Mbit) ---> S2IO 10Gbe Xframe NIC) to
 bring down CPU utilization.
 ** For AMD opteron platforms with 8131 chipset, MMRBC=1 and MOST=1 are
 recommended as safe parameters.
 For more information, please review the AMD8131 errata at
 http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/26310.pdf
 6.  Available Downloads
 Neterion "s2io" driver in Red Hat and Suse 2.6-based distributions is kept up
 to date, also the latest "s2io" code (including support for 2.4 kernels) is
 available via "Support" link on the Neterion site:  http://www.neterion.com.
 For Xframe User Guide (Programming manual), visit ftp site ns1.s2io.com,
 user: linuxdocs password: HALdocs
 7. Support
 For further support please contact either your 10GbE Xframe NIC vendor (IBM,
 HP, SGI etc.) or click on the "Support" link on the Neterion site:
 http://www.neterion.com.

 #
 # Network device configuration
 #
 menuconfig NETDEVICES
 	default y if UML
 	depends on NET
 	bool "Network device support"
 	---help---
 	  You can say N here if you don't intend to connect your Linux box to
 	  any other computer at all.
 	  You'll have to say Y if your computer contains a network card that
 	  you want to use under Linux. If you are going to run SLIP or PPP over
 	  telephone line or null modem cable you need say Y here. Connecting
 	  two machines with parallel ports using PLIP needs this, as well as
 	  AX.25/KISS for sending Internet traffic over amateur radio links.
 	  See also "The Linux Network Administrator's Guide" by Olaf Kirch and
 	  Terry Dawson. Available at <http://www.tldp.org/guides.html>.
 	  If unsure, say Y.
 # All the following symbols are dependent on NETDEVICES - do not repeat
 # that for each of the symbols.
 if NETDEVICES
 config NETDEVICES_MULTIQUEUE
 	bool "Netdevice multiple hardware queue support"
 	---help---
 	  Say Y here if you want to allow the network stack to use multiple
 	  hardware TX queues on an ethernet device.
 	  Most people will say N here.
 config IFB
 	tristate "Intermediate Functional Block support"
 	depends on NET_CLS_ACT
 	---help---
 	  This is an intermediate driver that allows sharing of
 	  resources.
 	  To compile this driver as a module, choose M here: the module
 	  will be called ifb.  If you want to use more than one ifb
 	  device at a time, you need to compile this driver as a module.
 	  Instead of 'ifb', the devices will then be called 'ifb0',
 	  'ifb1' etc.
 	  Look at the iproute2 documentation directory for usage etc
 config DUMMY
 	tristate "Dummy net driver support"
 	---help---
 	  This is essentially a bit-bucket device (i.e. traffic you send to
 	  this device is consigned into oblivion) with a configurable IP
 	  address. It is most commonly used in order to make your currently
 	  inactive SLIP address seem like a real address for local programs.
 	  If you use SLIP or PPP, you might want to say Y here. Since this
 	  thing often comes in handy, the default is Y. It won't enlarge your
 	  kernel either. What a deal. Read about it in the Network
 	  Administrator's Guide, available from
 	  <http://www.tldp.org/docs.html#guide>.
 	  To compile this driver as a module, choose M here: the module
 	  will be called dummy.  If you want to use more than one dummy
 	  device at a time, you need to compile this driver as a module.
 	  Instead of 'dummy', the devices will then be called 'dummy0',
 	  'dummy1' etc.
 config BONDING
 	tristate "Bonding driver support"
 	depends on INET
 	---help---
 	  Say 'Y' or 'M' if you wish to be able to 'bond' multiple Ethernet
 	  Channels together. This is called 'Etherchannel' by Cisco,
 	  'Trunking' by Sun, 802.3ad by the IEEE, and 'Bonding' in Linux.
 	  The driver supports multiple bonding modes to allow for both high
 	  performance and high availability operation.
 	  Refer to <file:Documentation/networking/bonding.txt> for more
 	  information.
 	  To compile this driver as a module, choose M here: the module
 	  will be called bonding.
 config MACVLAN
 	tristate "MAC-VLAN support (EXPERIMENTAL)"
 	depends on EXPERIMENTAL
 	---help---
 	  This allows one to create virtual interfaces that map packets to
 	  or from specific MAC addresses to a particular interface.
 	  Macvlan devices can be added using the "ip" command from the
 	  iproute2 package starting with the iproute2-2.6.23 release:
 	  "ip link add link <real dev> [ address MAC ] [ NAME ] type macvlan"
 	  To compile this driver as a module, choose M here: the module
 	  will be called macvlan.
 config EQUALIZER
 	tristate "EQL (serial line load balancing) support"
 	---help---
 	  If you have two serial connections to some other computer (this
 	  usually requires two modems and two telephone lines) and you use
 	  SLIP (the protocol for sending Internet traffic over telephone
 	  lines) or PPP (a better SLIP) on them, you can make them behave like
 	  one double speed connection using this driver.  Naturally, this has
 	  to be supported at the other end as well, either with a similar EQL
 	  Linux driver or with a Livingston Portmaster 2e.
 	  Say Y if you want this and read
 	  <file:Documentation/networking/eql.txt>.  You may also want to read
 	  section 6.2 of the NET-3-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here: the module
 	  will be called eql.  If unsure, say N.
 config TUN
 	tristate "Universal TUN/TAP device driver support"
 	select CRC32
 	---help---
 	  TUN/TAP provides packet reception and transmission for user space
 	  programs.  It can be viewed as a simple Point-to-Point or Ethernet
 	  device, which instead of receiving packets from a physical media,
 	  receives them from user space program and instead of sending packets
 	  via physical media writes them to the user space program.
 	  When a program opens /dev/net/tun, driver creates and registers
 	  corresponding net device tunX or tapX.  After a program closed above
 	  devices, driver will automatically delete tunXX or tapXX device and
 	  all routes corresponding to it.
 	  Please read <file:Documentation/networking/tuntap.txt> for more
 	  information.
 	  To compile this driver as a module, choose M here: the module
 	  will be called tun.
 	  If you don't know what to use this for, you don't need it.
 config VETH
 	tristate "Virtual ethernet pair device"
 	---help---
 	  This device is a local ethernet tunnel. Devices are created in pairs.
 	  When one end receives the packet it appears on its pair and vice
 	  versa.
 config NET_SB1000
 	tristate "General Instruments Surfboard 1000"
 	depends on PNP
 	---help---
 	  This is a driver for the General Instrument (also known as
 	  NextLevel) SURFboard 1000 internal
 	  cable modem. This is an ISA card which is used by a number of cable
 	  TV companies to provide cable modem access. It's a one-way
 	  downstream-only cable modem, meaning that your upstream net link is
 	  provided by your regular phone modem.
 	  At present this driver only compiles as a module, so say M here if
 	  you have this card. The module will be called sb1000. Then read
 	  <file:Documentation/networking/README.sb1000> for information on how
 	  to use this module, as it needs special ppp scripts for establishing
 	  a connection. Further documentation and the necessary scripts can be
 	  found at:
 	  <http://www.jacksonville.net/~fventuri/>
 	  <http://home.adelphia.net/~siglercm/sb1000.html>
 	  <http://linuxpower.cx/~cable/>
 	  If you don't have this card, of course say N.
 source "drivers/net/arcnet/Kconfig"
 source "drivers/net/phy/Kconfig"
 #
 #	Ethernet
 #
 menuconfig NET_ETHERNET
 	bool "Ethernet (10 or 100Mbit)"
 	depends on !UML
 	---help---
 	  Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
 	  type of Local Area Network (LAN) in universities and companies.
 	  Common varieties of Ethernet are: 10BASE-2 or Thinnet (10 Mbps over
 	  coaxial cable, linking computers in a chain), 10BASE-T or twisted
 	  pair (10 Mbps over twisted pair cable, linking computers to central
 	  hubs), 10BASE-F (10 Mbps over optical fiber links, using hubs),
 	  100BASE-TX (100 Mbps over two twisted pair cables, using hubs),
 	  100BASE-T4 (100 Mbps over 4 standard voice-grade twisted pair
 	  cables, using hubs), 100BASE-FX (100 Mbps over optical fiber links)
 	  [the 100BASE varieties are also known as Fast Ethernet], and Gigabit
 	  Ethernet (1 Gbps over optical fiber or short copper links).
 	  If your Linux machine will be connected to an Ethernet and you have
 	  an Ethernet network interface card (NIC) installed in your computer,
 	  say Y here and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>. You will then also have
 	  to say Y to the driver for your particular NIC.
 	  Note that the answer to this question won't directly affect the
 	  kernel: saying N will just cause the configurator to skip all
 	  the questions about Ethernet network cards. If unsure, say N.
 if NET_ETHERNET
 config MII
 	tristate "Generic Media Independent Interface device support"
 	help
 	  Most ethernet controllers have MII transceiver either as an external
 	  or internal device.  It is safe to say Y or M here even if your
 	  ethernet card lack MII.
 config MACB
 	tristate "Atmel MACB support"
 	depends on AVR32 || ARCH_AT91SAM9260 || ARCH_AT91SAM9263 || ARCH_AT91CAP9
 	select PHYLIB
 	help
 	  The Atmel MACB ethernet interface is found on many AT32 and AT91
 	  parts. Say Y to include support for the MACB chip.
 	  To compile this driver as a module, choose M here: the module
 	  will be called macb.
 source "drivers/net/arm/Kconfig"
 config AX88796
 	tristate "ASIX AX88796 NE2000 clone support"
 	depends on ARM || MIPS || SUPERH
 	select CRC32
 	select MII
 	help
 	  AX88796 driver, using platform bus to provide
 	  chip detection and resources
 config AX88796_93CX6
 	bool "ASIX AX88796 external 93CX6 eeprom support"
 	depends on AX88796
 	select EEPROM_93CX6
 	help
 	  Select this if your platform comes with an external 93CX6 eeprom.
 config MACE
 	tristate "MACE (Power Mac ethernet) support"
 	depends on PPC_PMAC && PPC32
 	select CRC32
 	help
 	  Power Macintoshes and clones with Ethernet built-in on the
 	  motherboard will usually use a MACE (Medium Access Control for
 	  Ethernet) interface. Say Y to include support for the MACE chip.
 	  To compile this driver as a module, choose M here: the module
 	  will be called mace.
 config MACE_AAUI_PORT
 	bool "Use AAUI port instead of TP by default"
 	depends on MACE
 	help
 	  Some Apple machines (notably the Apple Network Server) which use the
 	  MACE ethernet chip have an Apple AUI port (small 15-pin connector),
 	  instead of an 8-pin RJ45 connector for twisted-pair ethernet.  Say
 	  Y here if you have such a machine.  If unsure, say N.
 	  The driver will default to AAUI on ANS anyway, and if you use it as
 	  a module, you can provide the port_aaui=0|1 to force the driver.
 config BMAC
 	tristate "BMAC (G3 ethernet) support"
 	depends on PPC_PMAC && PPC32
 	select CRC32
 	help
 	  Say Y for support of BMAC Ethernet interfaces. These are used on G3
 	  computers.
 	  To compile this driver as a module, choose M here: the module
 	  will be called bmac.
 config ARIADNE
 	tristate "Ariadne support"
 	depends on ZORRO
 	help
 	  If you have a Village Tronic Ariadne Ethernet adapter, say Y.
 	  Otherwise, say N.
 	  To compile this driver as a module, choose M here: the module
 	  will be called ariadne.
 config A2065
 	tristate "A2065 support"
 	depends on ZORRO
 	select CRC32
 	help
 	  If you have a Commodore A2065 Ethernet adapter, say Y. Otherwise,
 	  say N.
 	  To compile this driver as a module, choose M here: the module
 	  will be called a2065.
 config HYDRA
 	tristate "Hydra support"
 	depends on ZORRO
 	select CRC32
 	help
 	  If you have a Hydra Ethernet adapter, say Y. Otherwise, say N.
 	  To compile this driver as a module, choose M here: the module
 	  will be called hydra.
 config ZORRO8390
 	tristate "Zorro NS8390-based Ethernet support"
 	depends on ZORRO
 	select CRC32
 	help
 	  This driver is for Zorro Ethernet cards using an NS8390-compatible
 	  chipset, like the Village Tronic Ariadne II and the Individual
 	  Computers X-Surf Ethernet cards. If you have such a card, say Y.
 	  Otherwise, say N.
 	  To compile this driver as a module, choose M here: the module
 	  will be called zorro8390.
 config APNE
 	tristate "PCMCIA NE2000 support"
 	depends on AMIGA_PCMCIA
 	select CRC32
 	help
 	  If you have a PCMCIA NE2000 compatible adapter, say Y.  Otherwise,
 	  say N.
 	  To compile this driver as a module, choose M here: the module
 	  will be called apne.
 config APOLLO_ELPLUS
 	tristate "Apollo 3c505 support"
 	depends on APOLLO
 	help
 	  Say Y or M here if your Apollo has a 3Com 3c505 ISA Ethernet card.
 	  If you don't have one made for Apollos, you can use one from a PC,
 	  except that your Apollo won't be able to boot from it (because the
 	  code in the ROM will be for a PC).
 config MAC8390
 	bool "Macintosh NS 8390 based ethernet cards"
 	depends on MAC
 	select CRC32
 	help
 	  If you want to include a driver to support Nubus or LC-PDS
 	  Ethernet cards using an NS8390 chipset or its equivalent, say Y
 	  and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 config MAC89x0
 	tristate "Macintosh CS89x0 based ethernet cards"
 	depends on MAC
 	---help---
 	  Support for CS89x0 chipset based Ethernet cards.  If you have a
 	  Nubus or LC-PDS network (Ethernet) card of this type, say Y and
 	  read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. This module will
 	  be called mac89x0.
 config MACSONIC
 	tristate "Macintosh SONIC based ethernet (onboard, NuBus, LC, CS)"
 	depends on MAC
 	---help---
 	  Support for NatSemi SONIC based Ethernet devices.  This includes
 	  the onboard Ethernet in many Quadras as well as some LC-PDS,
 	  a few Nubus and all known Comm Slot Ethernet cards.  If you have
 	  one of these say Y and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. This module will
 	  be called macsonic.
 config MACMACE
 	bool "Macintosh (AV) onboard MACE ethernet"
 	depends on MAC
 	select CRC32
 	help
 	  Support for the onboard AMD 79C940 MACE Ethernet controller used in
 	  the 660AV and 840AV Macintosh.  If you have one of these Macintoshes
 	  say Y and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 config MVME147_NET
 	tristate "MVME147 (Lance) Ethernet support"
 	depends on MVME147
 	select CRC32
 	help
 	  Support for the on-board Ethernet interface on the Motorola MVME147
 	  single-board computer.  Say Y here to include the
 	  driver for this chip in your kernel.
 	  To compile this driver as a module, choose M here.
 config MVME16x_NET
 	tristate "MVME16x Ethernet support"
 	depends on MVME16x
 	help
 	  This is the driver for the Ethernet interface on the Motorola
 	  MVME162, 166, 167, 172 and 177 boards.  Say Y here to include the
 	  driver for this chip in your kernel.
 	  To compile this driver as a module, choose M here.
 config BVME6000_NET
 	tristate "BVME6000 Ethernet support"
 	depends on BVME6000
 	help
 	  This is the driver for the Ethernet interface on BVME4000 and
 	  BVME6000 VME boards.  Say Y here to include the driver for this chip
 	  in your kernel.
 	  To compile this driver as a module, choose M here.
 config ATARILANCE
 	tristate "Atari Lance support"
 	depends on ATARI
 	help
 	  Say Y to include support for several Atari Ethernet adapters based
 	  on the AMD Lance chipset: RieblCard (with or without battery), or
 	  PAMCard VME (also the version by Rhotron, with different addresses).
 config SUN3LANCE
 	tristate "Sun3/Sun3x on-board LANCE support"
 	depends on SUN3 || SUN3X
 	help
 	  Most Sun3 and Sun3x motherboards (including the 3/50, 3/60 and 3/80)
 	  featured an AMD Lance 10Mbit Ethernet controller on board; say Y
 	  here to compile in the Linux driver for this and enable Ethernet.
 	  General Linux information on the Sun 3 and 3x series (now
 	  discontinued) is at
 	  <http://www.angelfire.com/ca2/tech68k/sun3.html>.
 	  If you're not building a kernel for a Sun 3, say N.
 config SUN3_82586
 	bool "Sun3 on-board Intel 82586 support"
 	depends on SUN3
 	help
 	  This driver enables support for the on-board Intel 82586 based
 	  Ethernet adapter found on Sun 3/1xx and 3/2xx motherboards.  Note
 	  that this driver does not support 82586-based adapters on additional
 	  VME boards.
 config HPLANCE
 	bool "HP on-board LANCE support"
 	depends on DIO
 	select CRC32
 	help
 	  If you want to use the builtin "LANCE" Ethernet controller on an
 	  HP300 machine, say Y here.
 config LASI_82596
 	tristate "Lasi ethernet"
 	depends on GSC
 	help
 	  Say Y here to support the builtin Intel 82596 ethernet controller
 	  found in Hewlett-Packard PA-RISC machines with 10Mbit ethernet.
 config SNI_82596
 	tristate "SNI RM ethernet"
 	depends on NET_ETHERNET && SNI_RM
 	help
 	  Say Y here to support the on-board Intel 82596 ethernet controller
 	  built into SNI RM machines.
 config KORINA
 	tristate "Korina (IDT RC32434) Ethernet support"
 	depends on NET_ETHERNET && MIKROTIK_RB532
 	help
 	  If you have a Mikrotik RouterBoard 500 or IDT RC32434
 	  based system say Y. Otherwise say N.
 config MIPS_JAZZ_SONIC
 	tristate "MIPS JAZZ onboard SONIC Ethernet support"
 	depends on MACH_JAZZ
 	help
 	  This is the driver for the onboard card of MIPS Magnum 4000,
 	  Acer PICA, Olivetti M700-10 and a few other identical OEM systems.
 config MIPS_AU1X00_ENET
 	bool "MIPS AU1000 Ethernet support"
 	depends on SOC_AU1X00
 	select PHYLIB
 	select CRC32
 	help
 	  If you have an Alchemy Semi AU1X00 based system
 	  say Y.  Otherwise, say N.
 config SGI_IOC3_ETH
 	bool "SGI IOC3 Ethernet"
 	depends on PCI && SGI_IP27
 	select CRC32
 	select MII
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 config MIPS_SIM_NET
 	tristate "MIPS simulator Network device"
 	depends on MIPS_SIM
 	help
 	  The MIPSNET device is a simple Ethernet network device which is
 	  emulated by the MIPS Simulator.
 	  If you are not using a MIPSsim or are unsure, say N.
 config SGI_O2MACE_ETH
 	tristate "SGI O2 MACE Fast Ethernet support"
 	depends on SGI_IP32=y
 config STNIC
 	tristate "National DP83902AV  support"
 	depends on SUPERH
 	select CRC32
 	help
 	  Support for cards based on the National Semiconductor DP83902AV
 	  ST-NIC Serial Network Interface Controller for Twisted Pair.  This
 	  is a 10Mbit/sec Ethernet controller.  Product overview and specs at
 	  <http://www.national.com/pf/DP/DP83902A.html>.
 	  If unsure, say N.
 config SH_ETH
 	tristate "Renesas SuperH Ethernet support"
 	depends on SUPERH && \
 		(CPU_SUBTYPE_SH7710 || CPU_SUBTYPE_SH7712)
 	select CRC32
 	select MII
 	select MDIO_BITBANG
 	select PHYLIB
 	help
 	  Renesas SuperH Ethernet device driver.
 	  This driver support SH7710 and SH7712.
 config SUNLANCE
 	tristate "Sun LANCE support"
 	depends on SBUS
 	select CRC32
 	help
 	  This driver supports the "le" interface present on all 32-bit Sparc
 	  systems, on some older Ultra systems and as an Sbus option.  These
 	  cards are based on the AMD Lance chipset, which is better known
 	  via the NE2100 cards.
 	  To compile this driver as a module, choose M here: the module
 	  will be called sunlance.
 config HAPPYMEAL
 	tristate "Sun Happy Meal 10/100baseT support"
 	depends on SBUS || PCI
 	select CRC32
 	help
 	  This driver supports the "hme" interface present on most Ultra
 	  systems and as an option on older Sbus systems. This driver supports
 	  both PCI and Sbus devices. This driver also supports the "qfe" quad
 	  100baseT device available in both PCI and Sbus configurations.
 	  To compile this driver as a module, choose M here: the module
 	  will be called sunhme.
 config SUNBMAC
 	tristate "Sun BigMAC 10/100baseT support (EXPERIMENTAL)"
 	depends on SBUS && EXPERIMENTAL
 	select CRC32
 	help
 	  This driver supports the "be" interface available as an Sbus option.
 	  This is Sun's older 100baseT Ethernet device.
 	  To compile this driver as a module, choose M here: the module
 	  will be called sunbmac.
 config SUNQE
 	tristate "Sun QuadEthernet support"
 	depends on SBUS
 	select CRC32
 	help
 	  This driver supports the "qe" 10baseT Ethernet device, available as
 	  an Sbus option. Note that this is not the same as Quad FastEthernet
 	  "qfe" which is supported by the Happy Meal driver instead.
 	  To compile this driver as a module, choose M here: the module
 	  will be called sunqe.
 config SUNGEM
 	tristate "Sun GEM support"
 	depends on PCI
 	select CRC32
 	help
 	  Support for the Sun GEM chip, aka Sun GigabitEthernet/P 2.0.  See also
 	  <http://www.sun.com/products-n-solutions/hardware/docs/pdf/806-3985-10.pdf>.
 config CASSINI
 	tristate "Sun Cassini support"
 	depends on PCI
 	select CRC32
 	help
 	  Support for the Sun Cassini chip, aka Sun GigaSwift Ethernet. See also
 	  <http://www.sun.com/products-n-solutions/hardware/docs/pdf/817-4341-10.pdf>
 config SUNVNET
 	tristate "Sun Virtual Network support"
 	depends on SUN_LDOMS
 	help
 	  Support for virtual network devices under Sun Logical Domains.
 config NET_VENDOR_3COM
 	bool "3COM cards"
 	depends on ISA || EISA || MCA || PCI
 	help
 	  If you have a network (Ethernet) card belonging to this class, say Y
 	  and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  Note that the answer to this question doesn't directly affect the
 	  kernel: saying N will just cause the configurator to skip all
 	  the questions about 3COM cards. If you say Y, you will be asked for
 	  your specific card in the following questions.
 config EL1
 	tristate "3c501 \"EtherLink\" support"
 	depends on NET_VENDOR_3COM && ISA
 	---help---
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.  Also, consider buying a
 	  new card, since the 3c501 is slow, broken, and obsolete: you will
 	  have problems.  Some people suggest to ping ("man ping") a nearby
 	  machine every minute ("man cron") when using this card.
 	  To compile this driver as a module, choose M here. The module
 	  will be called 3c501.
 config EL2
 	tristate "3c503 \"EtherLink II\" support"
 	depends on NET_VENDOR_3COM && ISA
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called 3c503.
 config ELPLUS
 	tristate "3c505 \"EtherLink Plus\" support"
 	depends on NET_VENDOR_3COM && ISA && ISA_DMA_API
 	---help---
 	  Information about this network (Ethernet) card can be found in
 	  <file:Documentation/networking/3c505.txt>.  If you have a card of
 	  this type, say Y and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called 3c505.
 config EL16
 	tristate "3c507 \"EtherLink 16\" support (EXPERIMENTAL)"
 	depends on NET_VENDOR_3COM && ISA && EXPERIMENTAL
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called 3c507.
 config EL3
 	tristate "3c509/3c529 (MCA)/3c579 \"EtherLink III\" support"
 	depends on NET_VENDOR_3COM && (ISA || EISA || MCA)
 	---help---
 	  If you have a network (Ethernet) card belonging to the 3Com
 	  EtherLinkIII series, say Y and read the Ethernet-HOWTO, available
 	  from <http://www.tldp.org/docs.html#howto>.
 	  If your card is not working you may need to use the DOS
 	  setup disk to disable Plug & Play mode, and to select the default
 	  media type.
 	  To compile this driver as a module, choose M here. The module
 	  will be called 3c509.
 config 3C515
 	tristate "3c515 ISA \"Fast EtherLink\""
 	depends on NET_VENDOR_3COM && (ISA || EISA) && ISA_DMA_API
 	help
 	  If you have a 3Com ISA EtherLink XL "Corkscrew" 3c515 Fast Ethernet
 	  network card, say Y and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called 3c515.
 config ELMC
 	tristate "3c523 \"EtherLink/MC\" support"
 	depends on NET_VENDOR_3COM && MCA_LEGACY
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called 3c523.
 config ELMC_II
 	tristate "3c527 \"EtherLink/MC 32\" support (EXPERIMENTAL)"
 	depends on NET_VENDOR_3COM && MCA && MCA_LEGACY
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called 3c527.
 config VORTEX
 	tristate "3c590/3c900 series (592/595/597) \"Vortex/Boomerang\" support"
 	depends on NET_VENDOR_3COM && (PCI || EISA)
 	select MII
 	---help---
 	  This option enables driver support for a large number of 10Mbps and
 	  10/100Mbps EISA, PCI and PCMCIA 3Com network cards:
 	  "Vortex"    (Fast EtherLink 3c590/3c592/3c595/3c597) EISA and PCI
 	  "Boomerang" (EtherLink XL 3c900 or 3c905)            PCI
 	  "Cyclone"   (3c540/3c900/3c905/3c980/3c575/3c656)    PCI and Cardbus
 	  "Tornado"   (3c905)                                  PCI
 	  "Hurricane" (3c555/3cSOHO)                           PCI
 	  If you have such a card, say Y and read the Ethernet-HOWTO,
 	  available from <http://www.tldp.org/docs.html#howto>. More
 	  specific information is in
 	  <file:Documentation/networking/vortex.txt> and in the comments at
 	  the beginning of <file:drivers/net/3c59x.c>.
 	  To compile this support as a module, choose M here.
 config TYPHOON
 	tristate "3cr990 series \"Typhoon\" support"
 	depends on NET_VENDOR_3COM && PCI
 	select CRC32
 	---help---
 	  This option enables driver support for the 3cr990 series of cards:
 	  3C990-TX, 3CR990-TX-95, 3CR990-TX-97, 3CR990-FX-95, 3CR990-FX-97,
 	  3CR990SVR, 3CR990SVR95, 3CR990SVR97, 3CR990-FX-95 Server,
 	  3CR990-FX-97 Server, 3C990B-TX-M, 3C990BSVR
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called typhoon.
 config LANCE
 	tristate "AMD LANCE and PCnet (AT1500 and NE2100) support"
 	depends on ISA && ISA_DMA_API
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>. Some LinkSys cards are
 	  of this type.
 	  To compile this driver as a module, choose M here: the module
 	  will be called lance.  This is recommended.
 config NET_VENDOR_SMC
 	bool "Western Digital/SMC cards"
 	depends on ISA || MCA || EISA || MAC
 	help
 	  If you have a network (Ethernet) card belonging to this class, say Y
 	  and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  Note that the answer to this question doesn't directly affect the
 	  kernel: saying N will just cause the configurator to skip all
 	  the questions about Western Digital cards. If you say Y, you will be
 	  asked for your specific card in the following questions.
 config WD80x3
 	tristate "WD80*3 support"
 	depends on NET_VENDOR_SMC && ISA
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called wd.
 config ULTRAMCA
 	tristate "SMC Ultra MCA support"
 	depends on NET_VENDOR_SMC && MCA
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type and are running
 	  an MCA based system (PS/2), say Y and read the Ethernet-HOWTO,
 	  available from <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called smc-mca.
 config ULTRA
 	tristate "SMC Ultra support"
 	depends on NET_VENDOR_SMC && ISA
 	select CRC32
 	---help---
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  Important: There have been many reports that, with some motherboards
 	  mixing an SMC Ultra and an Adaptec AHA154x SCSI card (or compatible,
 	  such as some BusLogic models) causes corruption problems with many
 	  operating systems. The Linux smc-ultra driver has a work-around for
 	  this but keep it in mind if you have such a SCSI card and have
 	  problems.
 	  To compile this driver as a module, choose M here. The module
 	  will be called smc-ultra.
 config ULTRA32
 	tristate "SMC Ultra32 EISA support"
 	depends on NET_VENDOR_SMC && EISA
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called smc-ultra32.
 config BFIN_MAC
 	tristate "Blackfin 527/536/537 on-chip mac support"
 	depends on NET_ETHERNET && (BF527 || BF537 || BF536)
 	select CRC32
 	select MII
 	select PHYLIB
 	select BFIN_MAC_USE_L1 if DMA_UNCACHED_NONE
 	help
 	  This is the driver for blackfin on-chip mac device. Say Y if you want it
 	  compiled into the kernel. This driver is also available as a module
 	  ( = code which can be inserted in and removed from the running kernel
 	  whenever you want). The module will be called bfin_mac.
 config BFIN_MAC_USE_L1
 	bool "Use L1 memory for rx/tx packets"
 	depends on BFIN_MAC && (BF527 || BF537)
 	default y
 	help
 	  To get maximum network performance, you should use L1 memory as rx/tx buffers.
 	  Say N here if you want to reserve L1 memory for other uses.
 config BFIN_TX_DESC_NUM
 	int "Number of transmit buffer packets"
 	depends on BFIN_MAC
 	range 6 10 if BFIN_MAC_USE_L1
 	range 10 100
 	default "10"
 	help
 	  Set the number of buffer packets used in driver.
 config BFIN_RX_DESC_NUM
 	int "Number of receive buffer packets"
 	depends on BFIN_MAC
 	range 20 100 if BFIN_MAC_USE_L1
 	range 20 800
 	default "20"
 	help
 	  Set the number of buffer packets used in driver.
 config BFIN_MAC_RMII
 	bool "RMII PHY Interface (EXPERIMENTAL)"
 	depends on BFIN_MAC && EXPERIMENTAL
 	default y if BFIN527_EZKIT
 	default n if BFIN537_STAMP
 	help
 	  Use Reduced PHY MII Interface
 config SMC9194
 	tristate "SMC 9194 support"
 	depends on NET_VENDOR_SMC && (ISA || MAC && BROKEN)
 	select CRC32
 	---help---
 	  This is support for the SMC9xxx based Ethernet cards. Choose this
 	  option if you have a DELL laptop with the docking station, or
 	  another SMC9192/9194 based chipset.  Say Y if you want it compiled
 	  into the kernel, and read the file
 	  <file:Documentation/networking/smc9.txt> and the Ethernet-HOWTO,
 	  available from <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called smc9194.
 config SMC91X
 	tristate "SMC 91C9x/91C1xxx support"
 	select CRC32
 	select MII
 	depends on ARM || REDWOOD_5 || REDWOOD_6 || M32R || SUPERH || \
 		SOC_AU1X00 || BLACKFIN || MN10300
 	help
 	  This is a driver for SMC's 91x series of Ethernet chipsets,
 	  including the SMC91C94 and the SMC91C111. Say Y if you want it
 	  compiled into the kernel, and read the file
 	  <file:Documentation/networking/smc9.txt>  and the Ethernet-HOWTO,
 	  available from  <http://www.linuxdoc.org/docs.html#howto>.
 	  This driver is also available as a module ( = code which can be
 	  inserted in and removed from the running kernel whenever you want).
 	  The module will be called smc91x.  If you want to compile it as a
 	  module, say M here and read <file:Documentation/kbuild/modules.txt>.
 config NET_NETX
 	tristate "NetX Ethernet support"
 	select MII
 	depends on ARCH_NETX
 	help
 	  This is support for the Hilscher netX builtin Ethernet ports
 	  To compile this driver as a module, choose M here. The module
 	  will be called netx-eth.
 config DM9000
 	tristate "DM9000 support"
 	depends on ARM || BLACKFIN || MIPS
 	select CRC32
 	select MII
 	---help---
 	  Support for DM9000 chipset.
 	  To compile this driver as a module, choose M here.  The module
 	  will be called dm9000.
 config DM9000_DEBUGLEVEL
 	int "DM9000 maximum debug level"
 	depends on DM9000
 	default 4
 	help
 	  The maximum level of debugging code compiled into the DM9000
 	  driver.
 config DM9000_FORCE_SIMPLE_PHY_POLL
 	bool "Force simple NSR based PHY polling"
 	depends on DM9000
 	---help---
 	  This configuration forces the DM9000 to use the NSR's LinkStatus
 	  bit to determine if the link is up or down instead of the more
 	  costly MII PHY reads. Note, this will not work if the chip is
 	  operating with an external PHY.
 config ENC28J60
 	tristate "ENC28J60 support"
 	depends on EXPERIMENTAL && SPI && NET_ETHERNET
 	select CRC32
 	---help---
 	  Support for the Microchip EN28J60 ethernet chip.
 	  To compile this driver as a module, choose M here. The module will be
 	  called enc28j60.
 config ENC28J60_WRITEVERIFY
 	bool "Enable write verify"
 	depends on ENC28J60
 	---help---
 	  Enable the verify after the buffer write useful for debugging purpose.
 	  If unsure, say N.
 config SMC911X
 	tristate "SMSC LAN911[5678] support"
 	select CRC32
 	select MII
 	depends on ARCH_PXA || SUPERH
 	help
 	  This is a driver for SMSC's LAN911x series of Ethernet chipsets
 	  including the new LAN9115, LAN9116, LAN9117, and LAN9118.
 	  Say Y if you want it compiled into the kernel,
 	  and read the Ethernet-HOWTO, available from
 	  <http://www.linuxdoc.org/docs.html#howto>.
 	  This driver is also available as a module. The module will be
 	  called smc911x.  If you want to compile it as a module, say M
 	  here and read <file:Documentation/kbuild/modules.txt>
 config NET_VENDOR_RACAL
 	bool "Racal-Interlan (Micom) NI cards"
 	depends on ISA
 	help
 	  If you have a network (Ethernet) card belonging to this class, such
 	  as the NI5010, NI5210 or NI6210, say Y and read the Ethernet-HOWTO,
 	  available from <http://www.tldp.org/docs.html#howto>.
 	  Note that the answer to this question doesn't directly affect the
 	  kernel: saying N will just cause the configurator to skip all
 	  the questions about NI cards. If you say Y, you will be asked for
 	  your specific card in the following questions.
 config NI5010
 	tristate "NI5010 support (EXPERIMENTAL)"
 	depends on NET_VENDOR_RACAL && ISA && EXPERIMENTAL && BROKEN_ON_SMP
 	---help---
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>. Note that this is still
 	  experimental code.
 	  To compile this driver as a module, choose M here. The module
 	  will be called ni5010.
 config NI52
 	tristate "NI5210 support"
 	depends on NET_VENDOR_RACAL && ISA
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called ni52.
 config NI65
 	tristate "NI6510 support"
 	depends on NET_VENDOR_RACAL && ISA && ISA_DMA_API
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called ni65.
 source "drivers/net/tulip/Kconfig"
 config AT1700
 	tristate "AT1700/1720 support (EXPERIMENTAL)"
 	depends on (ISA || MCA_LEGACY) && EXPERIMENTAL
 	select CRC32
 	---help---
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called at1700.
 config DEPCA
 	tristate "DEPCA, DE10x, DE200, DE201, DE202, DE422 support"
 	depends on ISA || EISA || MCA
 	select CRC32
 	---help---
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto> as well as
 	  <file:drivers/net/depca.c>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called depca.
 config HP100
 	tristate "HP 10/100VG PCLAN (ISA, EISA, PCI) support"
 	depends on ISA || EISA || PCI
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called hp100.
 config NET_ISA
 	bool "Other ISA cards"
 	depends on ISA
 	---help---
 	  If your network (Ethernet) card hasn't been mentioned yet and its
 	  bus system (that's the way the cards talks to the other components
 	  of your computer) is ISA (as opposed to EISA, VLB or PCI), say Y.
 	  Make sure you know the name of your card. Read the Ethernet-HOWTO,
 	  available from <http://www.tldp.org/docs.html#howto>.
 	  If unsure, say Y.
 	  Note that the answer to this question doesn't directly affect the
 	  kernel: saying N will just cause the configurator to skip all
 	  the remaining ISA network card questions. If you say Y, you will be
 	  asked for your specific card in the following questions.
 config E2100
 	tristate "Cabletron E21xx support"
 	depends on NET_ISA
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called e2100.
 config EWRK3
 	tristate "EtherWORKS 3 (DE203, DE204, DE205) support"
 	depends on NET_ISA
 	select CRC32
 	---help---
 	  This driver supports the DE203, DE204 and DE205 network (Ethernet)
 	  cards. If this is for you, say Y and read
 	  <file:Documentation/networking/ewrk3.txt> in the kernel source as
 	  well as the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called ewrk3.
 config EEXPRESS
 	tristate "EtherExpress 16 support"
 	depends on NET_ISA
 	---help---
 	  If you have an EtherExpress16 network (Ethernet) card, say Y and
 	  read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.  Note that the Intel
 	  EtherExpress16 card used to be regarded as a very poor choice
 	  because the driver was very unreliable. We now have a new driver
 	  that should do better.
 	  To compile this driver as a module, choose M here. The module
 	  will be called eexpress.
 config EEXPRESS_PRO
 	tristate "EtherExpressPro support/EtherExpress 10 (i82595) support"
 	depends on NET_ISA
 	---help---
 	  If you have a network (Ethernet) card of this type, say Y. This
 	  driver supports Intel i82595{FX,TX} based boards. Note however
 	  that the EtherExpress PRO/100 Ethernet card has its own separate
 	  driver.  Please read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called eepro.
 config HPLAN_PLUS
 	tristate "HP PCLAN+ (27247B and 27252A) support"
 	depends on NET_ISA
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called hp-plus.
 config HPLAN
 	tristate "HP PCLAN (27245 and other 27xxx series) support"
 	depends on NET_ISA
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called hp.
 config LP486E
 	tristate "LP486E on board Ethernet"
 	depends on NET_ISA
 	help
 	  Say Y here to support the 82596-based on-board Ethernet controller
 	  for the Panther motherboard, which is one of the two shipped in the
 	  Intel Professional Workstation.
 config ETH16I
 	tristate "ICL EtherTeam 16i/32 support"
 	depends on NET_ISA
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called eth16i.
 config NE2000
 	tristate "NE2000/NE1000 support"
 	depends on NET_ISA || (Q40 && m) || M32R || TOSHIBA_RBTX4927 || TOSHIBA_RBTX4938
 	select CRC32
 	---help---
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.  Many Ethernet cards
 	  without a specific driver are compatible with NE2000.
 	  If you have a PCI NE2000 card however, say N here and Y to "PCI
 	  NE2000 and clone support" under "EISA, VLB, PCI and on board
 	  controllers" below. If you have a NE2000 card and are running on
 	  an MCA system (a bus system used on some IBM PS/2 computers and
 	  laptops), say N here and Y to "NE/2 (ne2000 MCA version) support",
 	  below.
 	  To compile this driver as a module, choose M here. The module
 	  will be called ne.
 config ZNET
 	tristate "Zenith Z-Note support (EXPERIMENTAL)"
 	depends on NET_ISA && EXPERIMENTAL && ISA_DMA_API
 	help
 	  The Zenith Z-Note notebook computer has a built-in network
 	  (Ethernet) card, and this is the Linux driver for it. Note that the
 	  IBM Thinkpad 300 is compatible with the Z-Note and is also supported
 	  by this driver. Read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 config SEEQ8005
 	tristate "SEEQ8005 support (EXPERIMENTAL)"
 	depends on NET_ISA && EXPERIMENTAL
 	help
 	  This is a driver for the SEEQ 8005 network (Ethernet) card.  If this
 	  is for you, read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called seeq8005.
 config NE2_MCA
 	tristate "NE/2 (ne2000 MCA version) support"
 	depends on MCA_LEGACY
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called ne2.
 config IBMLANA
 	tristate "IBM LAN Adapter/A support"
 	depends on MCA
 	---help---
 	  This is a Micro Channel Ethernet adapter.  You need to set
 	  CONFIG_MCA to use this driver.  It is both available as an in-kernel
 	  driver and as a module.
 	  To compile this driver as a module, choose M here. The only
 	  currently supported card is the IBM LAN Adapter/A for Ethernet.  It
 	  will both support 16K and 32K memory windows, however a 32K window
 	  gives a better security against packet losses.  Usage of multiple
 	  boards with this driver should be possible, but has not been tested
 	  up to now due to lack of hardware.
 config IBMVETH
 	tristate "IBM LAN Virtual Ethernet support"
 	depends on PPC_PSERIES
 	---help---
 	  This driver supports virtual ethernet adapters on newer IBM iSeries
 	  and pSeries systems.
 	  To compile this driver as a module, choose M here. The module will
 	  be called ibmveth.
 source "drivers/net/ibm_newemac/Kconfig"
 config NET_PCI
 	bool "EISA, VLB, PCI and on board controllers"
 	depends on ISA || EISA || PCI
 	help
 	  This is another class of network cards which attach directly to the
 	  bus. If you have one of those, say Y and read the Ethernet-HOWTO,
 	  available from <http://www.tldp.org/docs.html#howto>.
 	  Note that the answer to this question doesn't directly affect the
 	  kernel: saying N will just cause the configurator to skip all
 	  the questions about this class of network cards. If you say Y, you
 	  will be asked for your specific card in the following questions. If
 	  you are unsure, say Y.
 config PCNET32
 	tristate "AMD PCnet32 PCI support"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	help
 	  If you have a PCnet32 or PCnetPCI based network (Ethernet) card,
 	  answer Y here and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called pcnet32.
 config AMD8111_ETH
 	tristate "AMD 8111 (new PCI lance) support"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	help
 	  If you have an AMD 8111-based PCI lance ethernet card,
 	  answer Y here and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called amd8111e.
 config AMD8111E_NAPI
 	bool "Use RX polling (NAPI)"
 	depends on AMD8111_ETH
 	help
 	  NAPI is a new driver API designed to reduce CPU and interrupt load
 	  when the driver is receiving lots of packets from the card. It is
 	  still somewhat experimental and thus not yet enabled by default.
 	  If your estimated Rx load is 10kpps or more, or if the card will be
 	  deployed on potentially unfriendly networks (e.g. in a firewall),
 	  then say Y here.
 	  If in doubt, say N.
 config ADAPTEC_STARFIRE
 	tristate "Adaptec Starfire/DuraLAN support"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	help
 	  Say Y here if you have an Adaptec Starfire (or DuraLAN) PCI network
 	  adapter. The DuraLAN chip is used on the 64 bit PCI boards from
 	  Adaptec e.g. the ANA-6922A. The older 32 bit boards use the tulip
 	  driver.
 	  To compile this driver as a module, choose M here: the module
 	  will be called starfire.  This is recommended.
 config ADAPTEC_STARFIRE_NAPI
 	bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
 	depends on ADAPTEC_STARFIRE && EXPERIMENTAL
 	help
 	  NAPI is a new driver API designed to reduce CPU and interrupt load
 	  when the driver is receiving lots of packets from the card. It is
 	  still somewhat experimental and thus not yet enabled by default.
 	  If your estimated Rx load is 10kpps or more, or if the card will be
 	  deployed on potentially unfriendly networks (e.g. in a firewall),
 	  then say Y here.
 	  If in doubt, say N.
 config AC3200
 	tristate "Ansel Communications EISA 3200 support (EXPERIMENTAL)"
 	depends on NET_PCI && (ISA || EISA) && EXPERIMENTAL
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called ac3200.
 config APRICOT
 	tristate "Apricot Xen-II on board Ethernet"
 	depends on NET_PCI && ISA
 	help
 	  If you have a network (Ethernet) controller of this type, say Y and
 	  read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called apricot.
 config B44
 	tristate "Broadcom 440x/47xx ethernet support"
 	depends on SSB_POSSIBLE && HAS_DMA
 	select SSB
 	select MII
 	help
 	  If you have a network (Ethernet) controller of this type, say Y
 	  or M and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called b44.
 # Auto-select SSB PCI-HOST support, if possible
 config B44_PCI_AUTOSELECT
 	bool
 	depends on B44 && SSB_PCIHOST_POSSIBLE
 	select SSB_PCIHOST
 	default y
 # Auto-select SSB PCICORE driver, if possible
 config B44_PCICORE_AUTOSELECT
 	bool
 	depends on B44 && SSB_DRIVER_PCICORE_POSSIBLE
 	select SSB_DRIVER_PCICORE
 	default y
 config B44_PCI
 	bool
 	depends on B44_PCI_AUTOSELECT && B44_PCICORE_AUTOSELECT
 	default y
 config FORCEDETH
 	tristate "nForce Ethernet support"
 	depends on NET_PCI && PCI
 	help
 	  If you have a network (Ethernet) controller of this type, say Y and
 	  read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called forcedeth.
 config FORCEDETH_NAPI
 	bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
 	depends on FORCEDETH && EXPERIMENTAL
 	help
 	  NAPI is a new driver API designed to reduce CPU and interrupt load
 	  when the driver is receiving lots of packets from the card. It is
 	  still somewhat experimental and thus not yet enabled by default.
 	  If your estimated Rx load is 10kpps or more, or if the card will be
 	  deployed on potentially unfriendly networks (e.g. in a firewall),
 	  then say Y here.
 	  If in doubt, say N.
 config CS89x0
 	tristate "CS89x0 support"
 	depends on NET_PCI && (ISA || MACH_IXDP2351 || ARCH_IXDP2X01 || ARCH_PNX010X)
 	---help---
 	  Support for CS89x0 chipset based Ethernet cards. If you have a
 	  network (Ethernet) card of this type, say Y and read the
 	  Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto> as well as
 	  <file:Documentation/networking/cs89x0.txt>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called cs89x0.
 config TC35815
 	tristate "TOSHIBA TC35815 Ethernet support"
 	depends on NET_PCI && PCI && MIPS
 	select PHYLIB
 config EEPRO100
 	tristate "EtherExpressPro/100 support (eepro100, original Becker driver)"
 	depends on NET_PCI && PCI
 	select MII
 	help
 	  If you have an Intel EtherExpress PRO/100 PCI network (Ethernet)
 	  card, say Y and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called eepro100.
 config E100
 	tristate "Intel(R) PRO/100+ support"
 	depends on NET_PCI && PCI
 	select MII
 	---help---
 	  This driver supports Intel(R) PRO/100 family of adapters.
 	  To verify that your adapter is supported, find the board ID number
 	  on the adapter. Look for a label that has a barcode and a number
 	  in the format 123456-001 (six digits hyphen three digits).
 	  Use the above information and the Adapter & Driver ID Guide at:
 	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
           to identify the adapter.
 	  For the latest Intel PRO/100 network driver for Linux, see:
 	  <http://appsr.intel.com/scripts-df/support_intel.asp>
 	  More specific information on configuring the driver is in
 	  <file:Documentation/networking/e100.txt>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called e100.
 config LNE390
 	tristate "Mylex EISA LNE390A/B support (EXPERIMENTAL)"
 	depends on NET_PCI && EISA && EXPERIMENTAL
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called lne390.
 config FEALNX
 	tristate "Myson MTD-8xx PCI Ethernet support"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	help
 	  Say Y here to support the Mysom MTD-800 family of PCI-based Ethernet
 	  cards. Specifications and data at
 	  <http://www.myson.com.hk/mtd/datasheet/>.
 config NATSEMI
 	tristate "National Semiconductor DP8381x series PCI Ethernet support"
 	depends on NET_PCI && PCI
 	select CRC32
 	help
 	  This driver is for the National Semiconductor DP83810 series,
 	  which is used in cards from PureData, NetGear, Linksys
 	  and others, including the 83815 chip.
 	  More specific information and updates are available from
 	  <http://www.scyld.com/network/natsemi.html>.
 config NE2K_PCI
 	tristate "PCI NE2000 and clones support (see help)"
 	depends on NET_PCI && PCI
 	select CRC32
 	---help---
 	  This driver is for NE2000 compatible PCI cards. It will not work
 	  with ISA NE2000 cards (they have their own driver, "NE2000/NE1000
 	  support" below). If you have a PCI NE2000 network (Ethernet) card,
 	  say Y and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  This driver also works for the following NE2000 clone cards:
 	  RealTek RTL-8029  Winbond 89C940  Compex RL2000  KTI ET32P2
 	  NetVin NV5000SC   Via 86C926      SureCom NE34   Winbond
 	  Holtek HT80232    Holtek HT80229
 	  To compile this driver as a module, choose M here. The module
 	  will be called ne2k-pci.
 config NE3210
 	tristate "Novell/Eagle/Microdyne NE3210 EISA support (EXPERIMENTAL)"
 	depends on NET_PCI && EISA && EXPERIMENTAL
 	select CRC32
 	---help---
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.  Note that this driver
 	  will NOT WORK for NE3200 cards as they are completely different.
 	  To compile this driver as a module, choose M here. The module
 	  will be called ne3210.
 config ES3210
 	tristate "Racal-Interlan EISA ES3210 support (EXPERIMENTAL)"
 	depends on NET_PCI && EISA && EXPERIMENTAL
 	select CRC32
 	help
 	  If you have a network (Ethernet) card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called es3210.
 config 8139CP
 	tristate "RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support (EXPERIMENTAL)"
 	depends on NET_PCI && PCI && EXPERIMENTAL
 	select CRC32
 	select MII
 	help
 	  This is a driver for the Fast Ethernet PCI network cards based on
 	  the RTL8139C+ chips. If you have one of those, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here: the module
 	  will be called 8139cp.  This is recommended.
 config 8139TOO
 	tristate "RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	---help---
 	  This is a driver for the Fast Ethernet PCI network cards based on
 	  the RTL 8129/8130/8139 chips. If you have one of those, say Y and
 	  read the Ethernet-HOWTO <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here: the module
 	  will be called 8139too.  This is recommended.
 config 8139TOO_PIO
 	bool "Use PIO instead of MMIO"
 	default y
 	depends on 8139TOO
 	help
 	  This instructs the driver to use programmed I/O ports (PIO) instead
 	  of PCI shared memory (MMIO).  This can possibly solve some problems
 	  in case your mainboard has memory consistency issues.  If unsure,
 	  say N.
 config 8139TOO_TUNE_TWISTER
 	bool "Support for uncommon RTL-8139 rev. K (automatic channel equalization)"
 	depends on 8139TOO
 	help
 	  This implements a function which might come in handy in case you
 	  are using low quality on long cabling. It is required for RealTek
 	  RTL-8139 revision K boards, and totally unused otherwise.  It tries
 	  to match the transceiver to the cable characteristics. This is
 	  experimental since hardly documented by the manufacturer.
 	  If unsure, say Y.
 config 8139TOO_8129
 	bool "Support for older RTL-8129/8130 boards"
 	depends on 8139TOO
 	help
 	  This enables support for the older and uncommon RTL-8129 and
 	  RTL-8130 chips, which support MII via an external transceiver,
 	  instead of an internal one.  Disabling this option will save some
 	  memory by making the code size smaller.  If unsure, say Y.
 config 8139_OLD_RX_RESET
 	bool "Use older RX-reset method"
 	depends on 8139TOO
 	help
 	  The 8139too driver was recently updated to contain a more rapid
 	  reset sequence, in the face of severe receive errors.  This "new"
 	  RX-reset method should be adequate for all boards.  But if you
 	  experience problems, you can enable this option to restore the
 	  old RX-reset behavior.  If unsure, say N.
 config R6040
 	tristate "RDC R6040 Fast Ethernet Adapter support (EXPERIMENTAL)"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	help
 	  This is a driver for the R6040 Fast Ethernet MACs found in the
 	  the RDC R-321x System-on-chips.
 	  To compile this driver as a module, choose M here: the module
 	  will be called r6040. This is recommended.
 config SIS900
 	tristate "SiS 900/7016 PCI Fast Ethernet Adapter support"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	---help---
 	  This is a driver for the Fast Ethernet PCI network cards based on
 	  the SiS 900 and SiS 7016 chips. The SiS 900 core is also embedded in
 	  SiS 630 and SiS 540 chipsets.
 	  This driver also supports AMD 79C901 HomePNA so that you can use
 	  your phone line as a network cable.
 	  To compile this driver as a module, choose M here: the module
 	  will be called sis900.  This is recommended.
 config EPIC100
 	tristate "SMC EtherPower II"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	help
 	  This driver is for the SMC EtherPower II 9432 PCI Ethernet NIC,
 	  which is based on the SMC83c17x (EPIC/100).
 	  More specific information and updates are available from
 	  <http://www.scyld.com/network/epic100.html>.
 config SUNDANCE
 	tristate "Sundance Alta support"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	help
 	  This driver is for the Sundance "Alta" chip.
 	  More specific information and updates are available from
 	  <http://www.scyld.com/network/sundance.html>.
 config SUNDANCE_MMIO
 	bool "Use MMIO instead of PIO"
 	depends on SUNDANCE
 	help
 	  Enable memory-mapped I/O for interaction with Sundance NIC registers.
 	  Do NOT enable this by default, PIO (enabled when MMIO is disabled)
 	  is known to solve bugs on certain chips.
 	  If unsure, say N.
 config TLAN
 	tristate "TI ThunderLAN support"
 	depends on NET_PCI && (PCI || EISA)
 	---help---
 	  If you have a PCI Ethernet network card based on the ThunderLAN chip
 	  which is supported by this driver, say Y and read the
 	  Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  Devices currently supported by this driver are Compaq Netelligent,
 	  Compaq NetFlex and Olicom cards.  Please read the file
 	  <file:Documentation/networking/tlan.txt> for more details.
 	  To compile this driver as a module, choose M here. The module
 	  will be called tlan.
 	  Please email feedback to <torben.mathiasen@compaq.com>.
 config VIA_RHINE
 	tristate "VIA Rhine support"
 	depends on NET_PCI && PCI
 	select CRC32
 	select MII
 	help
 	  If you have a VIA "Rhine" based network card (Rhine-I (VT86C100A),
 	  Rhine-II (VT6102), or Rhine-III (VT6105)), say Y here. Rhine-type
 	  Ethernet functions can also be found integrated on South Bridges
 	  (e.g. VT8235).
 	  To compile this driver as a module, choose M here. The module
 	  will be called via-rhine.
 config VIA_RHINE_MMIO
 	bool "Use MMIO instead of PIO"
 	depends on VIA_RHINE
 	help
 	  This instructs the driver to use PCI shared memory (MMIO) instead of
 	  programmed I/O ports (PIO). Enabling this gives an improvement in
 	  processing time in parts of the driver.
 	  If unsure, say Y.
 config VIA_RHINE_NAPI
 	bool "Use Rx Polling (NAPI)"
 	depends on VIA_RHINE
 	help
 	  NAPI is a new driver API designed to reduce CPU and interrupt load
 	  when the driver is receiving lots of packets from the card.
 	  If your estimated Rx load is 10kpps or more, or if the card will be
 	  deployed on potentially unfriendly networks (e.g. in a firewall),
 	  then say Y here.
 config LAN_SAA9730
 	bool "Philips SAA9730 Ethernet support"
 	depends on NET_PCI && PCI && MIPS_ATLAS
 	help
 	  The SAA9730 is a combined multimedia and peripheral controller used
 	  in thin clients, Internet access terminals, and diskless
 	  workstations.
 	  See <http://www.semiconductors.philips.com/pip/SAA9730_flyer_1>.
 config SC92031
 	tristate "Silan SC92031 PCI Fast Ethernet Adapter driver (EXPERIMENTAL)"
 	depends on NET_PCI && PCI && EXPERIMENTAL
 	select CRC32
 	---help---
 	  This is a driver for the Fast Ethernet PCI network cards based on
 	  the Silan SC92031 chip (sometimes also called Rsltek 8139D). If you
 	  have one of these, say Y here.
 	  To compile this driver as a module, choose M here: the module
 	  will be called sc92031.  This is recommended.
 config CPMAC
 	tristate "TI AR7 CPMAC Ethernet support (EXPERIMENTAL)"
 	depends on NET_ETHERNET && EXPERIMENTAL && AR7 && BROKEN
 	select PHYLIB
 	help
 	  TI AR7 CPMAC Ethernet support
 config NET_POCKET
 	bool "Pocket and portable adapters"
 	depends on PARPORT
 	---help---
 	  Cute little network (Ethernet) devices which attach to the parallel
 	  port ("pocket adapters"), commonly used with laptops. If you have
 	  one of those, say Y and read the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  If you want to plug a network (or some other) card into the PCMCIA
 	  (or PC-card) slot of your laptop instead (PCMCIA is the standard for
 	  credit card size extension cards used by all modern laptops), you
 	  need the pcmcia-cs package (location contained in the file
 	  <file:Documentation/Changes>) and you can say N here.
 	  Laptop users should read the Linux Laptop home page at
 	  <http://www.linux-on-laptops.com/> or
 	  Tuxmobil - Linux on Mobile Computers at <http://www.tuxmobil.org/>.
 	  Note that the answer to this question doesn't directly affect the
 	  kernel: saying N will just cause the configurator to skip all
 	  the questions about this class of network devices. If you say Y, you
 	  will be asked for your specific device in the following questions.
 config ATP
 	tristate "AT-LAN-TEC/RealTek pocket adapter support"
 	depends on NET_POCKET && PARPORT && X86
 	select CRC32
 	---help---
 	  This is a network (Ethernet) device which attaches to your parallel
 	  port. Read <file:drivers/net/atp.c> as well as the Ethernet-HOWTO,
 	  available from <http://www.tldp.org/docs.html#howto>, if you
 	  want to use this.  If you intend to use this driver, you should have
 	  said N to the "Parallel printer support", because the two drivers
 	  don't like each other.
 	  To compile this driver as a module, choose M here: the module
 	  will be called atp.
 config DE600
 	tristate "D-Link DE600 pocket adapter support"
 	depends on NET_POCKET && PARPORT
 	---help---
 	  This is a network (Ethernet) device which attaches to your parallel
 	  port. Read <file:Documentation/networking/DLINK.txt> as well as the
 	  Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>, if you want to use
 	  this. It is possible to have several devices share a single parallel
 	  port and it is safe to compile the corresponding drivers into the
 	  kernel.
 	  To compile this driver as a module, choose M here: the module
 	  will be called de600.
 config DE620
 	tristate "D-Link DE620 pocket adapter support"
 	depends on NET_POCKET && PARPORT
 	---help---
 	  This is a network (Ethernet) device which attaches to your parallel
 	  port. Read <file:Documentation/networking/DLINK.txt> as well as the
 	  Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>, if you want to use
 	  this. It is possible to have several devices share a single parallel
 	  port and it is safe to compile the corresponding drivers into the
 	  kernel.
 	  To compile this driver as a module, choose M here: the module
 	  will be called de620.
 config SGISEEQ
 	tristate "SGI Seeq ethernet controller support"
 	depends on SGI_HAS_SEEQ
 	help
 	  Say Y here if you have an Seeq based Ethernet network card. This is
 	  used in many Silicon Graphics machines.
 config DECLANCE
 	tristate "DEC LANCE ethernet controller support"
 	depends on MACH_DECSTATION
 	select CRC32
 	help
 	  This driver is for the series of Ethernet controllers produced by
 	  DEC (now Compaq) based on the AMD Lance chipset, including the
 	  DEPCA series.  (This chipset is better known via the NE2100 cards.)
 config 68360_ENET
 	bool "Motorola 68360 ethernet controller"
 	depends on M68360
 	help
 	  Say Y here if you want to use the built-in ethernet controller of
 	  the Motorola 68360 processor.
 config FEC
 	bool "FEC ethernet controller (of ColdFire CPUs)"
 	depends on M523x || M527x || M5272 || M528x || M520x
 	help
 	  Say Y here if you want to use the built-in 10/100 Fast ethernet
 	  controller on some Motorola ColdFire processors.
 config FEC2
 	bool "Second FEC ethernet controller (on some ColdFire CPUs)"
 	depends on FEC
 	help
 	  Say Y here if you want to use the second built-in 10/100 Fast
 	  ethernet controller on some Motorola ColdFire processors.
 config FEC_MPC52xx
 	tristate "MPC52xx FEC driver"
 	depends on PPC_MERGE && PPC_MPC52xx && PPC_BESTCOMM_FEC
 	select CRC32
 	select PHYLIB
 	---help---
 	  This option enables support for the MPC5200's on-chip
 	  Fast Ethernet Controller
 	  If compiled as module, it will be called 'fec_mpc52xx.ko'.
 config FEC_MPC52xx_MDIO
 	bool "MPC52xx FEC MDIO bus driver"
 	depends on FEC_MPC52xx
 	default y
 	---help---
 	  The MPC5200's FEC can connect to the Ethernet either with
 	  an external MII PHY chip or 10 Mbps 7-wire interface
 	  (Motorola? industry standard).
 	  If your board uses an external PHY connected to FEC, enable this.
 	  If not sure, enable.
 	  If compiled as module, it will be called 'fec_mpc52xx_phy.ko'.
 config NE_H8300
 	tristate "NE2000 compatible support for H8/300"
 	depends on H8300
 	help
 	  Say Y here if you want to use the NE2000 compatible
 	  controller on the Renesas H8/300 processor.
 source "drivers/net/fec_8xx/Kconfig"
 source "drivers/net/fs_enet/Kconfig"
 endif # NET_ETHERNET
 #
 #	Gigabit Ethernet
 #
 menuconfig NETDEV_1000
 	bool "Ethernet (1000 Mbit)"
 	depends on !UML
 	default y
 	---help---
 	  Ethernet (also called IEEE 802.3 or ISO 8802-2) is the most common
 	  type of Local Area Network (LAN) in universities and companies.
 	  Say Y here to get to see options for Gigabit Ethernet drivers.
 	  This option alone does not add any kernel code.
 	  Note that drivers supporting both 100 and 1000 MBit may be listed
 	  under "Ethernet (10 or 100MBit)" instead.
 	  If you say N, all options in this submenu will be skipped and disabled.
 if NETDEV_1000
 config ACENIC
 	tristate "Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support"
 	depends on PCI
 	---help---
 	  Say Y here if you have an Alteon AceNIC, 3Com 3C985(B), NetGear
 	  GA620, SGI Gigabit or Farallon PN9000-SX PCI Gigabit Ethernet
 	  adapter. The driver allows for using the Jumbo Frame option (9000
 	  bytes/frame) however it requires that your switches can handle this
 	  as well. To enable Jumbo Frames, add `mtu 9000' to your ifconfig
 	  line.
 	  To compile this driver as a module, choose M here: the
 	  module will be called acenic.
 config ACENIC_OMIT_TIGON_I
 	bool "Omit support for old Tigon I based AceNICs"
 	depends on ACENIC
 	help
 	  Say Y here if you only have Tigon II based AceNICs and want to leave
 	  out support for the older Tigon I based cards which are no longer
 	  being sold (ie. the original Alteon AceNIC and 3Com 3C985 (non B
 	  version)).  This will reduce the size of the driver object by
 	  app. 100KB.  If you are not sure whether your card is a Tigon I or a
 	  Tigon II, say N here.
 	  The safe and default value for this is N.
 config DL2K
 	tristate "DL2000/TC902x-based Gigabit Ethernet support"
 	depends on PCI
 	select CRC32
 	help
 	  This driver supports DL2000/TC902x-based Gigabit ethernet cards,
 	  which includes
 	  D-Link DGE-550T Gigabit Ethernet Adapter.
 	  D-Link DL2000-based Gigabit Ethernet Adapter.
 	  Sundance/Tamarack TC902x Gigabit Ethernet Adapter.
 	  To compile this driver as a module, choose M here: the
 	  module will be called dl2k.
 config E1000
 	tristate "Intel(R) PRO/1000 Gigabit Ethernet support"
 	depends on PCI
 	---help---
 	  This driver supports Intel(R) PRO/1000 gigabit ethernet family of
 	  adapters.  For more information on how to identify your adapter, go
 	  to the Adapter & Driver ID Guide at:
 	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
 	  For general information and support, go to the Intel support
 	  website at:
 	  <http://support.intel.com>
 	  More specific information on configuring the driver is in
 	  <file:Documentation/networking/e1000.txt>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called e1000.
 config E1000_NAPI
 	bool "Use Rx Polling (NAPI)"
 	depends on E1000
 	help
 	  NAPI is a new driver API designed to reduce CPU and interrupt load
 	  when the driver is receiving lots of packets from the card. It is
 	  still somewhat experimental and thus not yet enabled by default.
 	  If your estimated Rx load is 10kpps or more, or if the card will be
 	  deployed on potentially unfriendly networks (e.g. in a firewall),
 	  then say Y here.
 	  If in doubt, say N.
 config E1000_DISABLE_PACKET_SPLIT
 	bool "Disable Packet Split for PCI express adapters"
 	depends on E1000
 	help
 	  Say Y here if you want to use the legacy receive path for PCI express
 	  hardware.
 	  If in doubt, say N.
 config E1000E
 	tristate "Intel(R) PRO/1000 PCI-Express Gigabit Ethernet support"
 	depends on PCI && (!SPARC32 || BROKEN)
 	---help---
 	  This driver supports the PCI-Express Intel(R) PRO/1000 gigabit
 	  ethernet family of adapters. For PCI or PCI-X e1000 adapters,
 	  use the regular e1000 driver For more information on how to
 	  identify your adapter, go to the Adapter & Driver ID Guide at:
 	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
 	  For general information and support, go to the Intel support
 	  website at:
 	  <http://support.intel.com>
 	  To compile this driver as a module, choose M here. The module
 	  will be called e1000e.
 config IP1000
 	tristate "IP1000 Gigabit Ethernet support"
 	depends on PCI && EXPERIMENTAL
 	select MII
 	---help---
 	  This driver supports IP1000 gigabit Ethernet cards.
 	  To compile this driver as a module, choose M here: the module
 	  will be called ipg.  This is recommended.
 config IGB
        tristate "Intel(R) 82575 PCI-Express Gigabit Ethernet support"
        depends on PCI
        ---help---
          This driver supports Intel(R) 82575 gigabit ethernet family of
          adapters.  For more information on how to identify your adapter, go
          to the Adapter & Driver ID Guide at:
          <http://support.intel.com/support/network/adapter/pro100/21397.htm>
          For general information and support, go to the Intel support
          website at:
          <http://support.intel.com>
          More specific information on configuring the driver is in
          <file:Documentation/networking/e1000.txt>.
          To compile this driver as a module, choose M here. The module
          will be called igb.
 source "drivers/net/ixp2000/Kconfig"
 config MYRI_SBUS
 	tristate "MyriCOM Gigabit Ethernet support"
 	depends on SBUS
 	help
 	  This driver supports MyriCOM Sbus gigabit Ethernet cards.
 	  To compile this driver as a module, choose M here: the module
 	  will be called myri_sbus.  This is recommended.
 config NS83820
 	tristate "National Semiconductor DP83820 support"
 	depends on PCI
 	help
 	  This is a driver for the National Semiconductor DP83820 series
 	  of gigabit ethernet MACs.  Cards using this chipset include
 	  the D-Link DGE-500T, PureData's PDP8023Z-TG, SMC's SMC9462TX,
 	  SOHO-GA2000T, SOHO-GA2500T.  The driver supports the use of
 	  zero copy.
 config HAMACHI
 	tristate "Packet Engines Hamachi GNIC-II support"
 	depends on PCI
 	select MII
 	help
 	  If you have a Gigabit Ethernet card of this type, say Y and read
 	  the Ethernet-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>.
 	  To compile this driver as a module, choose M here. The module will be
 	  called hamachi.
 config YELLOWFIN
 	tristate "Packet Engines Yellowfin Gigabit-NIC support (EXPERIMENTAL)"
 	depends on PCI && EXPERIMENTAL
 	select CRC32
 	---help---
 	  Say Y here if you have a Packet Engines G-NIC PCI Gigabit Ethernet
 	  adapter or the SYM53C885 Ethernet controller. The Gigabit adapter is
 	  used by the Beowulf Linux cluster project.  See
 	  <http://cesdis.gsfc.nasa.gov/linux/drivers/yellowfin.html> for more
 	  information about this driver in particular and Beowulf in general.
 	  To compile this driver as a module, choose M here: the module
 	  will be called yellowfin.  This is recommended.
 config R8169
 	tristate "Realtek 8169 gigabit ethernet support"
 	depends on PCI
 	select CRC32
 	---help---
 	  Say Y here if you have a Realtek 8169 PCI Gigabit Ethernet adapter.
 	  To compile this driver as a module, choose M here: the module
 	  will be called r8169.  This is recommended.
 config R8169_VLAN
 	bool "VLAN support"
 	depends on R8169 && VLAN_8021Q
 	---help---
 	  Say Y here for the r8169 driver to support the functions required
 	  by the kernel 802.1Q code.
 	  If in doubt, say Y.
 config SB1250_MAC
 	tristate "SB1250 Gigabit Ethernet support"
 	depends on SIBYTE_SB1xxx_SOC
 	select PHYLIB
 	---help---
 	  This driver supports Gigabit Ethernet interfaces based on the
 	  Broadcom SiByte family of System-On-a-Chip parts.  They include
 	  the BCM1120, BCM1125, BCM1125H, BCM1250, BCM1255, BCM1280, BCM1455
 	  and BCM1480 chips.
 	  To compile this driver as a module, choose M here: the module
 	  will be called sb1250-mac.
 config SIS190
 	tristate "SiS190/SiS191 gigabit ethernet support"
 	depends on PCI
 	select CRC32
 	select MII
 	---help---
 	  Say Y here if you have a SiS 190 PCI Fast Ethernet adapter or
 	  a SiS 191 PCI Gigabit Ethernet adapter. Both are expected to
 	  appear in lan on motherboard designs which are based on SiS 965
 	  and SiS 966 south bridge.
 	  To compile this driver as a module, choose M here: the module
 	  will be called sis190.  This is recommended.
 config SKGE
 	tristate "New SysKonnect GigaEthernet support"
 	depends on PCI
 	select CRC32
 	---help---
 	  This driver support the Marvell Yukon or SysKonnect SK-98xx/SK-95xx
 	  and related Gigabit Ethernet adapters. It is a new smaller driver
 	  with better performance and more complete ethtool support.
 	  It does not support the link failover and network management
 	  features that "portable" vendor supplied sk98lin driver does.
 	  This driver supports adapters based on the original Yukon chipset:
 	  Marvell 88E8001, Belkin F5D5005, CNet GigaCard, DLink DGE-530T,
 	  Linksys EG1032/EG1064, 3Com 3C940/3C940B, SysKonnect SK-9871/9872.
 	  It does not support the newer Yukon2 chipset: a separate driver,
 	  sky2, is provided for Yukon2-based adapters.
 	  To compile this driver as a module, choose M here: the module
 	  will be called skge.  This is recommended.
 config SKGE_DEBUG
        bool "Debugging interface"
        depends on SKGE && DEBUG_FS
        help
 	 This option adds the ability to dump driver state for debugging.
 	 The file debugfs/skge/ethX displays the state of the internal
 	 transmit and receive rings.
 	 If unsure, say N.
 config SKY2
 	tristate "SysKonnect Yukon2 support"
 	depends on PCI
 	select CRC32
 	---help---
 	  This driver supports Gigabit Ethernet adapters based on the
 	  Marvell Yukon 2 chipset:
 	  Marvell 88E8021/88E8022/88E8035/88E8036/88E8038/88E8050/88E8052/
 	  88E8053/88E8055/88E8061/88E8062, SysKonnect SK-9E21D/SK-9S21
 	  There is companion driver for the older Marvell Yukon and
 	  Genesis based adapters: skge.
 	  To compile this driver as a module, choose M here: the module
 	  will be called sky2.  This is recommended.
 config SKY2_DEBUG
        bool "Debugging interface"
        depends on SKY2 && DEBUG_FS
        help
 	 This option adds the ability to dump driver state for debugging.
 	 The file debugfs/sky2/ethX displays the state of the internal
 	 transmit and receive rings.
 	 If unsure, say N.
 config VIA_VELOCITY
 	tristate "VIA Velocity support"
 	depends on PCI
 	select CRC32
 	select CRC_CCITT
 	select MII
 	help
 	  If you have a VIA "Velocity" based network card say Y here.
 	  To compile this driver as a module, choose M here. The module
 	  will be called via-velocity.
 config TIGON3
 	tristate "Broadcom Tigon3 support"
 	depends on PCI
 	select PHYLIB
 	help
 	  This driver supports Broadcom Tigon3 based gigabit Ethernet cards.
 	  To compile this driver as a module, choose M here: the module
 	  will be called tg3.  This is recommended.
 config BNX2
 	tristate "Broadcom NetXtremeII support"
 	depends on PCI
 	select CRC32
 	select ZLIB_INFLATE
 	help
 	  This driver supports Broadcom NetXtremeII gigabit Ethernet cards.
 	  To compile this driver as a module, choose M here: the module
 	  will be called bnx2.  This is recommended.
 config SPIDER_NET
 	tristate "Spider Gigabit Ethernet driver"
 	depends on PCI && (PPC_IBM_CELL_BLADE || PPC_CELLEB)
 	select FW_LOADER
 	help
 	  This driver supports the Gigabit Ethernet chips present on the
 	  Cell Processor-Based Blades from IBM.
 config TSI108_ETH
 	   tristate "Tundra TSI108 gigabit Ethernet support"
 	   depends on TSI108_BRIDGE
 	   help
 	     This driver supports Tundra TSI108 gigabit Ethernet ports.
 	     To compile this driver as a module, choose M here: the module
 	     will be called tsi108_eth.
 config GELIC_NET
 	tristate "PS3 Gigabit Ethernet driver"
 	depends on PPC_PS3
 	select PS3_SYS_MANAGER
 	help
 	  This driver supports the network device on the PS3 game
 	  console.  This driver has built-in support for Ethernet.
 	  To compile this driver as a module, choose M here: the
 	  module will be called ps3_gelic.
 config GELIC_WIRELESS
 	bool "PS3 Wireless support"
 	depends on GELIC_NET
 	select WIRELESS_EXT
 	help
 	  This option adds the support for the wireless feature of PS3.
 	  If you have the wireless-less model of PS3 or have no plan to
 	  use wireless feature, disabling this option saves memory.  As
 	  the driver automatically distinguishes the models, you can
 	  safely enable this option even if you have a wireless-less model.
 config GELIC_WIRELESS_OLD_PSK_INTERFACE
        bool "PS3 Wireless private PSK interface (OBSOLETE)"
        depends on GELIC_WIRELESS
        help
           This option retains the obsolete private interface to pass
           the PSK from user space programs to the driver.  The PSK
           stands for 'Pre Shared Key' and is used for WPA[2]-PSK
           (WPA-Personal) environment.
           If WPA[2]-PSK is used and you need to use old programs that
           support only this old interface, say Y.  Otherwise N.
           If unsure, say N.
 config GIANFAR
 	tristate "Gianfar Ethernet"
 	depends on FSL_SOC
 	select PHYLIB
 	select CRC32
 	help
 	  This driver supports the Gigabit TSEC on the MPC83xx, MPC85xx,
 	  and MPC86xx family of chips, and the FEC on the 8540.
 config GFAR_NAPI
 	bool "Use Rx Polling (NAPI)"
 	depends on GIANFAR
 config UCC_GETH
 	tristate "Freescale QE Gigabit Ethernet"
 	depends on QUICC_ENGINE
 	select PHYLIB
 	help
 	  This driver supports the Gigabit Ethernet mode of the QUICC Engine,
 	  which is available on some Freescale SOCs.
 config UGETH_NAPI
 	bool "Use Rx Polling (NAPI)"
 	depends on UCC_GETH
 config UGETH_MAGIC_PACKET
 	bool "Magic Packet detection support"
 	depends on UCC_GETH
 config UGETH_FILTERING
 	bool "Mac address filtering support"
 	depends on UCC_GETH
 config UGETH_TX_ON_DEMAND
 	bool "Transmit on Demand support"
 	depends on UCC_GETH
 config MV643XX_ETH
 	tristate "Marvell Discovery (643XX) and Orion ethernet support"
 	depends on MV64360 || MV64X60 || (PPC_MULTIPLATFORM && PPC32) || PLAT_ORION
 	select MII
 	help
 	  This driver supports the gigabit ethernet MACs in the
 	  Marvell Discovery PPC/MIPS chipset family (MV643XX) and
 	  in the Marvell Orion ARM SoC family.
 	  Some boards that use the Discovery chipset are the Momenco
 	  Ocelot C and Jaguar ATX and Pegasos II.
 config QLA3XXX
 	tristate "QLogic QLA3XXX Network Driver Support"
 	depends on PCI
 	help
 	  This driver supports QLogic ISP3XXX gigabit Ethernet cards.
 	  To compile this driver as a module, choose M here: the module
 	  will be called qla3xxx.
 config ATL1
 	tristate "Attansic L1 Gigabit Ethernet support (EXPERIMENTAL)"
 	depends on PCI && EXPERIMENTAL
 	select CRC32
 	select MII
 	help
 	  This driver supports the Attansic L1 gigabit ethernet adapter.
 	  To compile this driver as a module, choose M here.  The module
 	  will be called atl1.
 endif # NETDEV_1000
 #
 #	10 Gigabit Ethernet
 #
 menuconfig NETDEV_10000
 	bool "Ethernet (10000 Mbit)"
 	depends on !UML
 	default y
 	---help---
 	  Say Y here to get to see options for 10 Gigabit Ethernet drivers.
 	  This option alone does not add any kernel code.
 	  If you say N, all options in this submenu will be skipped and disabled.
 if NETDEV_10000
 config CHELSIO_T1
         tristate "Chelsio 10Gb Ethernet support"
         depends on PCI
 	select CRC32
         help
           This driver supports Chelsio gigabit and 10-gigabit
           Ethernet cards. More information about adapter features and
 	  performance tuning is in <file:Documentation/networking/cxgb.txt>.
           For general information about Chelsio and our products, visit
           our website at <http://www.chelsio.com>.
           For customer support, please visit our customer support page at
           <http://www.chelsio.com/support.htm>.
           Please send feedback to <linux-bugs@chelsio.com>.
           To compile this driver as a module, choose M here: the module
           will be called cxgb.
 config CHELSIO_T1_1G
         bool "Chelsio gigabit Ethernet support"
         depends on CHELSIO_T1
         help
           Enables support for Chelsio's gigabit Ethernet PCI cards.  If you
           are using only 10G cards say 'N' here.
 config CHELSIO_T1_NAPI
 	bool "Use Rx Polling (NAPI)"
 	depends on CHELSIO_T1
 	default y
 	help
 	  NAPI is a driver API designed to reduce CPU and interrupt load
 	  when the driver is receiving lots of packets from the card.
 config CHELSIO_T3
 	tristate "Chelsio Communications T3 10Gb Ethernet support"
 	depends on PCI && INET
 	select FW_LOADER
 	select INET_LRO
 	help
 	  This driver supports Chelsio T3-based gigabit and 10Gb Ethernet
 	  adapters.
 	  For general information about Chelsio and our products, visit
 	  our website at <http://www.chelsio.com>.
 	  For customer support, please visit our customer support page at
 	  <http://www.chelsio.com/support.htm>.
 	  Please send feedback to <linux-bugs@chelsio.com>.
 	  To compile this driver as a module, choose M here: the module
 	  will be called cxgb3.
 config EHEA
 	tristate "eHEA Ethernet support"
 	depends on IBMEBUS && INET && SPARSEMEM
 	select INET_LRO
 	---help---
 	  This driver supports the IBM pSeries eHEA ethernet adapter.
 	  To compile the driver as a module, choose M here. The module
 	  will be called ehea.
 config IXGBE
 	tristate "Intel(R) 10GbE PCI Express adapters support"
 	depends on PCI && INET
 	select INET_LRO
 	---help---
 	  This driver supports Intel(R) 10GbE PCI Express family of
 	  adapters.  For more information on how to identify your adapter, go
 	  to the Adapter & Driver ID Guide at:
 	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
 	  For general information and support, go to the Intel support
 	  website at:
 	  <http://support.intel.com>
 	  To compile this driver as a module, choose M here. The module
 	  will be called ixgbe.
 config IXGB
 	tristate "Intel(R) PRO/10GbE support"
 	depends on PCI
 	---help---
 	  This driver supports Intel(R) PRO/10GbE family of adapters for
 	  PCI-X type cards. For PCI-E type cards, use the "ixgbe" driver
 	  instead. For more information on how to identify your adapter, go
 	  to the Adapter & Driver ID Guide at:
 	  <http://support.intel.com/support/network/adapter/pro100/21397.htm>
 	  For general information and support, go to the Intel support
 	  website at:
 	  <http://support.intel.com>
 	  More specific information on configuring the driver is in
 	  <file:Documentation/networking/ixgb.txt>.
 	  To compile this driver as a module, choose M here. The module
 	  will be called ixgb.
 config IXGB_NAPI
 	bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
 	depends on IXGB && EXPERIMENTAL
 	help
 	  NAPI is a new driver API designed to reduce CPU and interrupt load
 	  when the driver is receiving lots of packets from the card. It is
 	  still somewhat experimental and thus not yet enabled by default.
 	  If your estimated Rx load is 10kpps or more, or if the card will be
 	  deployed on potentially unfriendly networks (e.g. in a firewall),
 	  then say Y here.
 	  If in doubt, say N.
 config S2IO
 	tristate "S2IO 10Gbe XFrame NIC"
 	depends on PCI
 	---help---
 	  This driver supports the 10Gbe XFrame NIC of S2IO.
 	  More specific information on configuring the driver is in
 	  <file:Documentation/networking/s2io.txt>.
-config S2IO_NAPI
-	bool "Use Rx Polling (NAPI) (EXPERIMENTAL)"
-	depends on S2IO && EXPERIMENTAL
-	help
-	  NAPI is a new driver API designed to reduce CPU and interrupt load
-	  when the driver is receiving lots of packets from the card. It is
-	  still somewhat experimental and thus not yet enabled by default.
-	  If your estimated Rx load is 10kpps or more, or if the card will be
-	  deployed on potentially unfriendly networks (e.g. in a firewall),
-	  then say Y here.
-	  If in doubt, say N.
 config MYRI10GE
 	tristate "Myricom Myri-10G Ethernet support"
 	depends on PCI && INET
 	select FW_LOADER
 	select CRC32
 	select INET_LRO
 	---help---
 	  This driver supports Myricom Myri-10G Dual Protocol interface in
 	  Ethernet mode. If the eeprom on your board is not recent enough,
 	  you will need a newer firmware image.
 	  You may get this image or more information, at:
 	  <http://www.myri.com/scs/download-Myri10GE.html>
 	  To compile this driver as a module, choose M here. The module
 	  will be called myri10ge.
 config NETXEN_NIC
 	tristate "NetXen Multi port (1/10) Gigabit Ethernet NIC"
 	depends on PCI
 	help
 	  This enables the support for NetXen's Gigabit Ethernet card.
 config NIU
 	tristate "Sun Neptune 10Gbit Ethernet support"
 	depends on PCI
 	help
 	  This enables support for cards based upon Sun's
 	  Neptune chipset.
 config PASEMI_MAC
 	tristate "PA Semi 1/10Gbit MAC"
 	depends on PPC_PASEMI && PCI
 	select PHYLIB
 	select INET_LRO
 	help
 	  This driver supports the on-chip 1/10Gbit Ethernet controller on
 	  PA Semi's PWRficient line of chips.
 config MLX4_CORE
 	tristate
 	depends on PCI
 	default n
 config MLX4_DEBUG
 	bool "Verbose debugging output" if (MLX4_CORE && EMBEDDED)
 	depends on MLX4_CORE
 	default y
 	---help---
 	  This option causes debugging code to be compiled into the
 	  mlx4_core driver.  The output can be turned on via the
 	  debug_level module parameter (which can also be set after
 	  the driver is loaded through sysfs).
 config TEHUTI
 	tristate "Tehuti Networks 10G Ethernet"
 	depends on PCI
 	help
 	  Tehuti Networks 10G Ethernet NIC
 config BNX2X
 	tristate "Broadcom NetXtremeII 10Gb support"
 	depends on PCI
 	select ZLIB_INFLATE
 	select LIBCRC32C
 	help
 	  This driver supports Broadcom NetXtremeII 10 gigabit Ethernet cards.
 	  To compile this driver as a module, choose M here: the module
 	  will be called bnx2x.  This is recommended.
 source "drivers/net/sfc/Kconfig"
 endif # NETDEV_10000
 source "drivers/net/tokenring/Kconfig"
 source "drivers/net/wireless/Kconfig"
 source "drivers/net/usb/Kconfig"
 source "drivers/net/pcmcia/Kconfig"
 source "drivers/net/wan/Kconfig"
 source "drivers/atm/Kconfig"
 source "drivers/s390/net/Kconfig"
 config XEN_NETDEV_FRONTEND
 	tristate "Xen network device frontend driver"
 	depends on XEN
 	default y
 	help
 	  The network device frontend driver allows the kernel to
 	  access network devices exported exported by a virtual
 	  machine containing a physical network device driver. The
 	  frontend driver is intended for unprivileged guest domains;
 	  if you are compiling a kernel for a Xen guest, you almost
 	  certainly want to enable this.
 config ISERIES_VETH
 	tristate "iSeries Virtual Ethernet driver support"
 	depends on PPC_ISERIES
 config RIONET
 	tristate "RapidIO Ethernet over messaging driver support"
 	depends on RAPIDIO
 config RIONET_TX_SIZE
 	int "Number of outbound queue entries"
 	depends on RIONET
 	default "128"
 config RIONET_RX_SIZE
 	int "Number of inbound queue entries"
 	depends on RIONET
 	default "128"
 config FDDI
 	bool "FDDI driver support"
 	depends on (PCI || EISA || TC)
 	help
 	  Fiber Distributed Data Interface is a high speed local area network
 	  design; essentially a replacement for high speed Ethernet. FDDI can
 	  run over copper or fiber. If you are connected to such a network and
 	  want a driver for the FDDI card in your computer, say Y here (and
 	  then also Y to the driver for your FDDI card, below). Most people
 	  will say N.
 config DEFXX
 	tristate "Digital DEFTA/DEFEA/DEFPA adapter support"
 	depends on FDDI && (PCI || EISA || TC)
 	---help---
 	  This is support for the DIGITAL series of TURBOchannel (DEFTA),
 	  EISA (DEFEA) and PCI (DEFPA) controllers which can connect you
 	  to a local FDDI network.
 	  To compile this driver as a module, choose M here: the module
 	  will be called defxx.  If unsure, say N.
 config DEFXX_MMIO
 	bool
 	prompt "Use MMIO instead of PIO" if PCI || EISA
 	depends on DEFXX
 	default n if PCI || EISA
 	default y
 	---help---
 	  This instructs the driver to use EISA or PCI memory-mapped I/O
 	  (MMIO) as appropriate instead of programmed I/O ports (PIO).
 	  Enabling this gives an improvement in processing time in parts
 	  of the driver, but it may cause problems with EISA (DEFEA)
 	  adapters.  TURBOchannel does not have the concept of I/O ports,
 	  so MMIO is always used for these (DEFTA) adapters.
 	  If unsure, say N.
 config SKFP
 	tristate "SysKonnect FDDI PCI support"
 	depends on FDDI && PCI
 	select BITREVERSE
 	---help---
 	  Say Y here if you have a SysKonnect FDDI PCI adapter.
 	  The following adapters are supported by this driver:
 	  - SK-5521 (SK-NET FDDI-UP)
 	  - SK-5522 (SK-NET FDDI-UP DAS)
 	  - SK-5541 (SK-NET FDDI-FP)
 	  - SK-5543 (SK-NET FDDI-LP)
 	  - SK-5544 (SK-NET FDDI-LP DAS)
 	  - SK-5821 (SK-NET FDDI-UP64)
 	  - SK-5822 (SK-NET FDDI-UP64 DAS)
 	  - SK-5841 (SK-NET FDDI-FP64)
 	  - SK-5843 (SK-NET FDDI-LP64)
 	  - SK-5844 (SK-NET FDDI-LP64 DAS)
 	  - Netelligent 100 FDDI DAS Fibre SC
 	  - Netelligent 100 FDDI SAS Fibre SC
 	  - Netelligent 100 FDDI DAS UTP
 	  - Netelligent 100 FDDI SAS UTP
 	  - Netelligent 100 FDDI SAS Fibre MIC
 	  Read <file:Documentation/networking/skfp.txt> for information about
 	  the driver.
 	  Questions concerning this driver can be addressed to:
 	  <linux@syskonnect.de>
 	  To compile this driver as a module, choose M here: the module
 	  will be called skfp.  This is recommended.
 config HIPPI
 	bool "HIPPI driver support (EXPERIMENTAL)"
 	depends on EXPERIMENTAL && INET && PCI
 	help
 	  HIgh Performance Parallel Interface (HIPPI) is a 800Mbit/sec and
 	  1600Mbit/sec dual-simplex switched or point-to-point network. HIPPI
 	  can run over copper (25m) or fiber (300m on multi-mode or 10km on
 	  single-mode). HIPPI networks are commonly used for clusters and to
 	  connect to super computers. If you are connected to a HIPPI network
 	  and have a HIPPI network card in your computer that you want to use
 	  under Linux, say Y here (you must also remember to enable the driver
 	  for your HIPPI card below). Most people will say N here.
 config ROADRUNNER
 	tristate "Essential RoadRunner HIPPI PCI adapter support (EXPERIMENTAL)"
 	depends on HIPPI && PCI
 	help
 	  Say Y here if this is your PCI HIPPI network card.
 	  To compile this driver as a module, choose M here: the module
 	  will be called rrunner.  If unsure, say N.
 config ROADRUNNER_LARGE_RINGS
 	bool "Use large TX/RX rings (EXPERIMENTAL)"
 	depends on ROADRUNNER
 	help
 	  If you say Y here, the RoadRunner driver will preallocate up to 2 MB
 	  of additional memory to allow for fastest operation, both for
 	  transmitting and receiving. This memory cannot be used by any other
 	  kernel code or by user space programs. Say Y here only if you have
 	  the memory.
 config PLIP
 	tristate "PLIP (parallel port) support"
 	depends on PARPORT
 	---help---
 	  PLIP (Parallel Line Internet Protocol) is used to create a
 	  reasonably fast mini network consisting of two (or, rarely, more)
 	  local machines.  A PLIP link from a Linux box is a popular means to
 	  install a Linux distribution on a machine which doesn't have a
 	  CD-ROM drive (a minimal system has to be transferred with floppies
 	  first). The kernels on both machines need to have this PLIP option
 	  enabled for this to work.
 	  The PLIP driver has two modes, mode 0 and mode 1.  The parallel
 	  ports (the connectors at the computers with 25 holes) are connected
 	  with "null printer" or "Turbo Laplink" cables which can transmit 4
 	  bits at a time (mode 0) or with special PLIP cables, to be used on
 	  bidirectional parallel ports only, which can transmit 8 bits at a
 	  time (mode 1); you can find the wiring of these cables in
 	  <file:Documentation/networking/PLIP.txt>.  The cables can be up to
 	  15m long.  Mode 0 works also if one of the machines runs DOS/Windows
 	  and has some PLIP software installed, e.g. the Crynwr PLIP packet
 	  driver (<http://oak.oakland.edu/simtel.net/msdos/pktdrvr-pre.html>)
 	  and winsock or NCSA's telnet.
 	  If you want to use PLIP, say Y and read the PLIP mini-HOWTO as well
 	  as the NET-3-HOWTO, both available from
 	  <http://www.tldp.org/docs.html#howto>.  Note that the PLIP
 	  protocol has been changed and this PLIP driver won't work together
 	  with the PLIP support in Linux versions 1.0.x.  This option enlarges
 	  your kernel by about 8 KB.
 	  To compile this driver as a module, choose M here. The module
 	  will be called plip. If unsure, say Y or M, in case you buy
 	  a laptop later.
 config PPP
 	tristate "PPP (point-to-point protocol) support"
 	select SLHC
 	---help---
 	  PPP (Point to Point Protocol) is a newer and better SLIP.  It serves
 	  the same purpose: sending Internet traffic over telephone (and other
 	  serial) lines.  Ask your access provider if they support it, because
 	  otherwise you can't use it; most Internet access providers these
 	  days support PPP rather than SLIP.
 	  To use PPP, you need an additional program called pppd as described
 	  in the PPP-HOWTO, available at
 	  <http://www.tldp.org/docs.html#howto>.  Make sure that you have
 	  the version of pppd recommended in <file:Documentation/Changes>.
 	  The PPP option enlarges your kernel by about 16 KB.
 	  There are actually two versions of PPP: the traditional PPP for
 	  asynchronous lines, such as regular analog phone lines, and
 	  synchronous PPP which can be used over digital ISDN lines for
 	  example.  If you want to use PPP over phone lines or other
 	  asynchronous serial lines, you need to say Y (or M) here and also to
 	  the next option, "PPP support for async serial ports".  For PPP over
 	  synchronous lines, you should say Y (or M) here and to "Support
 	  synchronous PPP", below.
 	  If you said Y to "Version information on all symbols" above, then
 	  you cannot compile the PPP driver into the kernel; you can then only
 	  compile it as a module. To compile this driver as a module, choose M
 	  here. The module will be called ppp_generic.
 config PPP_MULTILINK
 	bool "PPP multilink support (EXPERIMENTAL)"
 	depends on PPP && EXPERIMENTAL
 	help
 	  PPP multilink is a protocol (defined in RFC 1990) which allows you
 	  to combine several (logical or physical) lines into one logical PPP
 	  connection, so that you can utilize your full bandwidth.
 	  This has to be supported at the other end as well and you need a
 	  version of the pppd daemon which understands the multilink protocol.
 	  If unsure, say N.
 config PPP_FILTER
 	bool "PPP filtering"
 	depends on PPP
 	help
 	  Say Y here if you want to be able to filter the packets passing over
 	  PPP interfaces.  This allows you to control which packets count as
 	  activity (i.e. which packets will reset the idle timer or bring up
 	  a demand-dialed link) and which packets are to be dropped entirely.
 	  You need to say Y here if you wish to use the pass-filter and
 	  active-filter options to pppd.
 	  If unsure, say N.
 config PPP_ASYNC
 	tristate "PPP support for async serial ports"
 	depends on PPP
 	select CRC_CCITT
 	---help---
 	  Say Y (or M) here if you want to be able to use PPP over standard
 	  asynchronous serial ports, such as COM1 or COM2 on a PC.  If you use
 	  a modem (not a synchronous or ISDN modem) to contact your ISP, you
 	  need this option.
 	  To compile this driver as a module, choose M here.
 	  If unsure, say Y.
 config PPP_SYNC_TTY
 	tristate "PPP support for sync tty ports"
 	depends on PPP
 	help
 	  Say Y (or M) here if you want to be able to use PPP over synchronous
 	  (HDLC) tty devices, such as the SyncLink adapter. These devices
 	  are often used for high-speed leased lines like T1/E1.
 	  To compile this driver as a module, choose M here.
 config PPP_DEFLATE
 	tristate "PPP Deflate compression"
 	depends on PPP
 	select ZLIB_INFLATE
 	select ZLIB_DEFLATE
 	---help---
 	  Support for the Deflate compression method for PPP, which uses the
 	  Deflate algorithm (the same algorithm that gzip uses) to compress
 	  each PPP packet before it is sent over the wire.  The machine at the
 	  other end of the PPP link (usually your ISP) has to support the
 	  Deflate compression method as well for this to be useful.  Even if
 	  they don't support it, it is safe to say Y here.
 	  To compile this driver as a module, choose M here.
 config PPP_BSDCOMP
 	tristate "PPP BSD-Compress compression"
 	depends on PPP
 	---help---
 	  Support for the BSD-Compress compression method for PPP, which uses
 	  the LZW compression method to compress each PPP packet before it is
 	  sent over the wire. The machine at the other end of the PPP link
 	  (usually your ISP) has to support the BSD-Compress compression
 	  method as well for this to be useful. Even if they don't support it,
 	  it is safe to say Y here.
 	  The PPP Deflate compression method ("PPP Deflate compression",
 	  above) is preferable to BSD-Compress, because it compresses better
 	  and is patent-free.
 	  Note that the BSD compression code will always be compiled as a
 	  module; it is called bsd_comp and will show up in the directory
 	  modules once you have said "make modules". If unsure, say N.
 config PPP_MPPE
        tristate "PPP MPPE compression (encryption) (EXPERIMENTAL)"
        depends on PPP && EXPERIMENTAL
        select CRYPTO
        select CRYPTO_SHA1
        select CRYPTO_ARC4
        select CRYPTO_ECB
        ---help---
          Support for the MPPE Encryption protocol, as employed by the
 	 Microsoft Point-to-Point Tunneling Protocol.
 	 See http://pptpclient.sourceforge.net/ for information on
 	 configuring PPTP clients and servers to utilize this method.
 config PPPOE
 	tristate "PPP over Ethernet (EXPERIMENTAL)"
 	depends on EXPERIMENTAL && PPP
 	help
 	  Support for PPP over Ethernet.
 	  This driver requires the latest version of pppd from the CVS
 	  repository at cvs.samba.org.  Alternatively, see the
 	  RoaringPenguin package (<http://www.roaringpenguin.com/pppoe>)
 	  which contains instruction on how to use this driver (under
 	  the heading "Kernel mode PPPoE").
 config PPPOATM
 	tristate "PPP over ATM"
 	depends on ATM && PPP
 	help
 	  Support PPP (Point to Point Protocol) encapsulated in ATM frames.
 	  This implementation does not yet comply with section 8 of RFC2364,
 	  which can lead to bad results if the ATM peer loses state and
 	  changes its encapsulation unilaterally.
 config PPPOL2TP
 	tristate "PPP over L2TP (EXPERIMENTAL)"
 	depends on EXPERIMENTAL && PPP && INET
 	help
 	  Support for PPP-over-L2TP socket family. L2TP is a protocol
 	  used by ISPs and enterprises to tunnel PPP traffic over UDP
 	  tunnels. L2TP is replacing PPTP for VPN uses.
 	  This kernel component handles only L2TP data packets: a
 	  userland daemon handles L2TP the control protocol (tunnel
 	  and session setup). One such daemon is OpenL2TP
 	  (http://openl2tp.sourceforge.net/).
 config SLIP
 	tristate "SLIP (serial line) support"
 	---help---
 	  Say Y if you intend to use SLIP or CSLIP (compressed SLIP) to
 	  connect to your Internet service provider or to connect to some
 	  other local Unix box or if you want to configure your Linux box as a
 	  Slip/CSlip server for other people to dial in. SLIP (Serial Line
 	  Internet Protocol) is a protocol used to send Internet traffic over
 	  serial connections such as telephone lines or null modem cables;
 	  nowadays, the protocol PPP is more commonly used for this same
 	  purpose.
 	  Normally, your access provider has to support SLIP in order for you
 	  to be able to use it, but there is now a SLIP emulator called SLiRP
 	  around (available from
 	  <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
 	  allows you to use SLIP over a regular dial up shell connection. If
 	  you plan to use SLiRP, make sure to say Y to CSLIP, below. The
 	  NET-3-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>, explains how to
 	  configure SLIP. Note that you don't need this option if you just
 	  want to run term (term is a program which gives you almost full
 	  Internet connectivity if you have a regular dial up shell account on
 	  some Internet connected Unix computer. Read
 	  <http://www.bart.nl/~patrickr/term-howto/Term-HOWTO.html>). SLIP
 	  support will enlarge your kernel by about 4 KB. If unsure, say N.
 	  To compile this driver as a module, choose M here. The module
 	  will be called slip.
 config SLIP_COMPRESSED
 	bool "CSLIP compressed headers"
 	depends on SLIP
 	select SLHC
 	---help---
 	  This protocol is faster than SLIP because it uses compression on the
 	  TCP/IP headers (not on the data itself), but it has to be supported
 	  on both ends. Ask your access provider if you are not sure and
 	  answer Y, just in case. You will still be able to use plain SLIP. If
 	  you plan to use SLiRP, the SLIP emulator (available from
 	  <ftp://ibiblio.org/pub/Linux/system/network/serial/>) which
 	  allows you to use SLIP over a regular dial up shell connection, you
 	  definitely want to say Y here. The NET-3-HOWTO, available from
 	  <http://www.tldp.org/docs.html#howto>, explains how to configure
 	  CSLIP. This won't enlarge your kernel.
 config SLHC
 	tristate
 	help
 	  This option enables Van Jacobsen serial line header compression
 	  routines.
 config SLIP_SMART
 	bool "Keepalive and linefill"
 	depends on SLIP
 	help
 	  Adds additional capabilities to the SLIP driver to support the
 	  RELCOM line fill and keepalive monitoring. Ideal on poor quality
 	  analogue lines.
 config SLIP_MODE_SLIP6
 	bool "Six bit SLIP encapsulation"
 	depends on SLIP
 	help
 	  Just occasionally you may need to run IP over hostile serial
 	  networks that don't pass all control characters or are only seven
 	  bit. Saying Y here adds an extra mode you can use with SLIP:
 	  "slip6". In this mode, SLIP will only send normal ASCII symbols over
 	  the serial device. Naturally, this has to be supported at the other
 	  end of the link as well. It's good enough, for example, to run IP
 	  over the async ports of a Camtec JNT Pad. If unsure, say N.
 config NET_FC
 	bool "Fibre Channel driver support"
 	depends on SCSI && PCI
 	help
 	  Fibre Channel is a high speed serial protocol mainly used to connect
 	  large storage devices to the computer; it is compatible with and
 	  intended to replace SCSI.
 	  If you intend to use Fibre Channel, you need to have a Fibre channel
 	  adaptor card in your computer; say Y here and to the driver for your
 	  adaptor below. You also should have said Y to "SCSI support" and
 	  "SCSI generic support".
 config NETCONSOLE
 	tristate "Network console logging support (EXPERIMENTAL)"
 	depends on EXPERIMENTAL
 	---help---
 	If you want to log kernel messages over the network, enable this.
 	See <file:Documentation/networking/netconsole.txt> for details.
 config NETCONSOLE_DYNAMIC
 	bool "Dynamic reconfiguration of logging targets (EXPERIMENTAL)"
 	depends on NETCONSOLE && SYSFS && EXPERIMENTAL
 	select CONFIGFS_FS
 	help
 	  This option enables the ability to dynamically reconfigure target
 	  parameters (interface, IP addresses, port numbers, MAC addresses)
 	  at runtime through a userspace interface exported using configfs.
 	  See <file:Documentation/networking/netconsole.txt> for details.
 config NETPOLL
 	def_bool NETCONSOLE
 config NETPOLL_TRAP
 	bool "Netpoll traffic trapping"
 	default n
 	depends on NETPOLL
 config NET_POLL_CONTROLLER
 	def_bool NETPOLL
 config VIRTIO_NET
 	tristate "Virtio network driver (EXPERIMENTAL)"
 	depends on EXPERIMENTAL && VIRTIO
 	---help---
 	  This is the virtual network driver for virtio.  It can be used with
           lguest or QEMU based VMMs (like KVM or Xen).  Say Y or M.
 endif # NETDEVICES