summaryrefslogtreecommitdiff
path: root/cpu/ppc4xx
diff options
context:
space:
mode:
authorMike Nuss <mike@terascala.com>2008-03-03 15:27:05 -0500
committerWolfgang Denk <wd@denx.de>2008-03-04 08:55:27 +0100
commit74eb0222594fd23aafdf168e60e872814eea8b62 (patch)
treea7457dea0e4058141886f01f5edc931e7eaecb29 /cpu/ppc4xx
parent491fb6dea9f52fdb9cb5996e8e978b9e9685179f (diff)
downloadu-boot-imx-74eb0222594fd23aafdf168e60e872814eea8b62.zip
u-boot-imx-74eb0222594fd23aafdf168e60e872814eea8b62.tar.gz
u-boot-imx-74eb0222594fd23aafdf168e60e872814eea8b62.tar.bz2
PPC4xx (Sequoia): Fix Ethernet "remote fault" problems
Every now and then a Sequoia board (or equivalent hardware) had problems connecting to a Gigabit capable network interface. There were differences in the PHY setup between Linux and U-Boot. This patch fixes the problem. Apparently "remote fault" is being set, which signals to some devices (on the other end of the cable) that a fault has occurred, while other devices ignore it. I believe the RF bit was causing the issue, but I removed T4 also, to match up with Linux. Signed-off-by: Mike Nuss <mike@terascala.com>
Diffstat (limited to 'cpu/ppc4xx')
-rw-r--r--cpu/ppc4xx/miiphy.c5
1 files changed, 2 insertions, 3 deletions
diff --git a/cpu/ppc4xx/miiphy.c b/cpu/ppc4xx/miiphy.c
index 4216f0b..3978773 100644
--- a/cpu/ppc4xx/miiphy.c
+++ b/cpu/ppc4xx/miiphy.c
@@ -143,9 +143,8 @@ int phy_setup_aneg (char *devname, unsigned char addr)
u16 adv;
miiphy_read (devname, addr, PHY_ANAR, &adv);
- adv |= (PHY_ANLPAR_ACK | PHY_ANLPAR_RF | PHY_ANLPAR_T4 |
- PHY_ANLPAR_TXFD | PHY_ANLPAR_TX | PHY_ANLPAR_10FD |
- PHY_ANLPAR_10);
+ adv |= (PHY_ANLPAR_ACK | PHY_ANLPAR_TXFD | PHY_ANLPAR_TX |
+ PHY_ANLPAR_10FD | PHY_ANLPAR_10);
miiphy_write (devname, addr, PHY_ANAR, adv);
miiphy_read (devname, addr, PHY_1000BTCR, &adv);