Historically PHY intialization was disabled on motionpro board. Then
at some point PHY init was enabled and only comment message was left.
It worked somehow provided that PHY init was done at the early stage.
But after commit f5cf2ef the driver initializes PHY only when it is
actually needed and now Ethernet on motionpro board is broken again.
I haven't managed to find the true reason of such behavior so I've
just disabled PHY initialization on motionpro board.
Signed-off-by: Ilya Yanok <ya...@emcraft.com>
---
drivers/net/mpc5xxx_fec.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/net/mpc5xxx_fec.c b/drivers/net/mpc5xxx_fec.c
index c88e596..5ea87f1 100644
--- a/drivers/net/mpc5xxx_fec.c
+++ b/drivers/net/mpc5xxx_fec.c
@@ -429,6 +429,7 @@ static int mpc5xxx_fec_init_phy(struct eth_device *dev,
bd_t * bis)
* PHY initialization for the Motion-PRO board, until a proper fix is found.
*/
+#ifndef CONFIG_MOTIONPRO
if (fec->xcv_type != SEVENWIRE) {
/*
* Set MII_SPEED = (1/(mii_speed * 2)) * System Clock
@@ -561,6 +562,7 @@ static int mpc5xxx_fec_init_phy(struct eth_device *dev,
bd_t * bis)
if (fec->xcv_type != SEVENWIRE)
mpc5xxx_fec_phydump (dev->name);
#endif
+#endif /* CONFIG_MOTIONPRO */
#if (DEBUG & 0x1)
--
1.7.0.4
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
