Re: [U-Boot-Users] PPC4xx enet crossover

Wolfgang Denk wrote:
It seems every now and then a report pops up that the Sequoia board (or now on equivalent hardware) has problems connecting to a Gigabit capable network interface. In our case, it's when the Sequoia is attached to a HP Procurve switch.
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.
Mike
diff --git a/cpu/ppc4xx/miiphy.c b/cpu/ppc4xx/miiphy.c index 4216f0b..f48e68d 100644 --- a/cpu/ppc4xx/miiphy.c +++ b/cpu/ppc4xx/miiphy.c @@ -143,7 +143,7 @@ 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 | + adv |= (PHY_ANLPAR_ACK | PHY_ANLPAR_TXFD | PHY_ANLPAR_TX | PHY_ANLPAR_10FD | PHY_ANLPAR_10); miiphy_write (devname, addr, PHY_ANAR, adv);

Dear Mike,
in message 2C7DE72B9BD00F44BAECA5B0CBB873950729A0@hermes.terascala.com you wrote:
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.
Excellent! thanks a lot.
Stefan, can you please test this tomorrow morning in the VL setup? If possible, I would like to see this go into the 1.3.2 release.
Best regards,
Wolfgang Denk

In message 2C7DE72B9BD00F44BAECA5B0CBB873950729A0@hermes.terascala.com you wrote:
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.
I verified that it fixes the problem with our setup (Sequoia board with HP Procurve switch), too. I still see a timeout for the very first packet after a reset, but after that it's working fine.
Thanks.
Could you just please add your Signed-off-by: line?
Best regards,
Wolfgang Denk

I setup the crosstools last night , but I failed.
Environment : RedHat8.1 Enterprise + crosstool-0.43.
After I enter " sh demo-powerpc-750.sh " command, with its dat file is gcc-4.1.0-glibc-2.3.6-tls.dat. It faild to setup , the information notice me that somthing is old.
Are they not compatible ? does anyone meet the problem?
_________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

In message BAY122-W333BEDBD9AF07DA6A81266EB120@phx.gbl you wrote:
I setup the crosstools last night , but I failed.
And what has this to do with U-Boot?
You are completely off topic here.
--_55cb0a7d-a4ce-46e8-83d8-b5e91e606ad4_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: 8bit
<html> <head>
And NEVER post HTML!
Best regards,
Wolfgang Denk
participants (3)
-
A A
-
Mike Nuss
-
Wolfgang Denk