1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
|
#
# Freescale device configuration
#
config NET_VENDOR_FREESCALE
bool "Freescale devices"
default y
depends on FSL_SOC || QUICC_ENGINE || CPM1 || CPM2 || PPC_MPC512x || \
M523x || M527x || M5272 || M528x || M520x || M532x || \
ARCH_MXC || ARCH_MXS || (PPC_MPC52xx && PPC_BESTCOMM)
---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 Freescale devices. If you say Y, you will be
asked for your specific card in the following questions.
if NET_VENDOR_FREESCALE
config FEC
tristate "FEC ethernet controller (of ColdFire and some i.MX CPUs)"
depends on (M523x || M527x || M5272 || M528x || M520x || M532x || \
ARCH_MXC || SOC_IMX28)
default ARCH_MXC || SOC_IMX28 if ARM
select PHYLIB
select PTP_1588_CLOCK
---help---
Say Y here if you want to use the built-in 10/100 Fast ethernet
controller on some Motorola ColdFire and Freescale i.MX processors.
config FEC_MPC52xx
tristate "FEC MPC52xx driver"
depends on PPC_MPC52xx && PPC_BESTCOMM
select CRC32
select PHYLIB
select PPC_BESTCOMM_FEC
---help---
This option enables support for the MPC5200's on-chip
Fast Ethernet Controller
If compiled as module, it will be called fec_mpc52xx.
config FEC_MPC52xx_MDIO
bool "FEC MPC52xx 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.
source "drivers/net/ethernet/freescale/fs_enet/Kconfig"
config FSL_PQ_MDIO
tristate "Freescale PQ MDIO"
depends on FSL_SOC
select PHYLIB
---help---
This driver supports the MDIO bus used by the gianfar and UCC drivers.
config FSL_XGMAC_MDIO
tristate "Freescale XGMAC MDIO"
depends on FSL_SOC
select PHYLIB
select OF_MDIO
---help---
This driver supports the MDIO bus on the Fman 10G Ethernet MACs, and
on the FMan mEMAC (which supports both Clauses 22 and 45)
config UCC_GETH
tristate "Freescale QE Gigabit Ethernet"
depends on QUICC_ENGINE
select FSL_PQ_MDIO
select PHYLIB
---help---
This driver supports the Gigabit Ethernet mode of the QUICC Engine,
which is available on some Freescale SOCs.
config UGETH_TX_ON_DEMAND
bool "Transmit on Demand support"
depends on UCC_GETH
config GIANFAR
tristate "Gianfar Ethernet"
depends on FSL_SOC
select FSL_85XX_CACHE_SRAM if PPC
select FSL_PQ_MDIO
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 FSL_GIANFAR_1588
bool "Gianfar 1588"
depends on GIANFAR
---help---
This driver supports Freescale eTSEC 1588 function.
Integrate the IEEE 1588 specification v2 ioctls with the gianfar driver.
The user space application should be IXXAT IEEE 1588 stack v1.04 or above.
Say Y here if you want to use IXXAT 1588 stack.
config GFAR_DBG_LOOP
bool "Gianfar IP forwarding debug loop"
depends on GIANFAR && DEBUG_FS
---help---
Enable this only to do packet forwarding benchmark tests for
the Gianfar driver in isolation from the Linux protocol stack.
A debugfs loopback target config file, named "lo", is created
for each Gianfar ethernet interface. To configure a packet
forwarding loop for a given Gianfar interface, one must write
to the coresponding "lo" file the name of the desired Gianfar
ethernet target interface.
Example - given the "eth1" interface, to forward incoming traffic
to "eth2":
#echo "eth2" > ./eth1/lo
In this example, a uni-directional loop from "eth1" to "eth2" is
created. Packets received by "eth1" will be forwarded directly
to "eth2" to be transmitted without further processing.
To delete an exiting loop, write 0 or "off" to the "lo" file.
source "drivers/net/ethernet/freescale/fman/Kconfig"
source "drivers/net/ethernet/freescale/dpa/Kconfig"
endif # NET_VENDOR_FREESCALE
|
