Hello all,
I have a custom board having MPC8560 as main processor. FCC3 is to be
configured for ethernet (10/100BaseT)
OS is linux-2.6.10 and U-BOOT is 2009.rc1
FCC3 is connected to Intel LXT971 PHY device . THE MDC and MDIO
connectivity between FCC3 and PHY is through PortC pins hence BITBANGED
MII is to be used for PHY management. NO INTERRUPT line is there from
PHY.
This ethernet interface is working properly in U-BOOT and i am able to
do tftp ping dhcp... but when I load Linux OS 2.6.10 this interface
does not comes up.
I have configured following flasgs in .config
#
# PHY device support
#
CONFIG_PHYLIB=y
#
# MII PHY device drivers
#
CONFIG_MARVELL_PHY=y
CONFIG_DAVICOM_PHY=y
# CONFIG_QSEMI_PHY is not set
CONFIG_LXT_PHY=y
# CONFIG_CICADA_PHY is not set
# CONFIG_FIXED_PHY is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
CONFIG_FS_ENET=y
# CONFIG_FS_ENET_HAS_SCC is not set
CONFIG_FS_ENET_HAS_FCC=y
CONFIG_GIANFAR=y
# CONFIG_GFAR_NAPI is not set
The driver getting compiled are drivers/net/fs_enet-main.c and
drivers/net/phy/lxt.c
Are these option sufficient for getting a working drivers for FCC3 PHY
and MII Bitbanged interface ?
I tried enabling CPM2 options
#
# CPM2 Options
#
# CONCONFIG_FEC_ENET=y
CONFIG_USE_MDIO=y
FIG_FCC1_ENET is not set
# CONFIG_FCC2_ENET is not set
CONFIG_FCC3_ENET=y
but the kernel doen not get compiled when these options are enabled
it gives compilation error in arch/ppc/8260_io/fcc_enet.c
This board has two TSEC ethernet also connected over GMII interface
Pls help me in understanding the correct options and drivers required
for enabling FCC3 driver along with relevant MII bitbanged and PHY
driver
with regards,
Deepak Gaur
________________________________________________________________________
You are invited to Get a Free AOL Email ID. - http://webmail.aol.in
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
