Hi all,
I'm debugging my board with MPC 8540 and marvell 88e1111 designed on it.
I'm sure the hardware connection is correct, and the phy's ID could be read
through terminal port. But anyway, phy can not work. I wonder if it is the
driver's problem? Since the Gianfar Ethernet Controller Version 1.1
surpport 88e1011s, but some 88e1111's registers are different from
88e1011s'. Actually I'm a new guy to Linux. Has anybody ever used 88e1111
phy in Linux envirenmemt? Please
give me some points. Thank you!
I have read the Gianfar ethernet controller driver, but it's difficult for
me to find out the sofware flow.
On Jun 8, 2006, at 02:43, =E9=83=AD =E5=89=91=E9=9D=9E wrote:
Hi all,
I'm debugging my board with MPC 8540 and marvell 88e1111 designed =20
on it.
I'm sure the hardware connection is correct, and the phy's ID could =20=
be read
through terminal port. But anyway, phy can not work. I wonder if it =20=
is the
driver's problem? Since the Gianfar Ethernet Controller Version 1.1
surpport 88e1011s, but some 88e1111's registers are different from
88e1011s'. Actually I'm a new guy to Linux. Has anybody ever used =20
88e1111
phy in Linux envirenmemt? Please
give me some points. Thank you!
I have read the Gianfar ethernet controller driver, but it's =20
difficult for
me to find out the sofware flow.
It would be better if you upgraded to the latest kernel. The PHY =20
subsystem in the driver has changed significantly since version 1.1 =20
of the driver. What leads you to believe that the PHY doesn't work? =20=
What errors do you see? I'm fairly certain the 88e1111 works with =20
the 88e1011 driver, but it's been a while.
Hi Andy,
Thank you for your information. So the driver is not the issue, but better
to upgraded.
I will check the board once more. The PHY doesn't work because the 8bit bus
between MAC and PHY is locked(TX_EN and RX_DV all disabled from the scope's
view) and also you can't see any signals exist at the Magnetic side(nor LED
signals). It seems that only MDC/MDIO and CLOCK reference pin works. The
PHY's ID must be read from MDC/MDIO interface and Clocks are right showed
on the scope.
Best Regards,
Jaffe
From: Andy Fleming <redacted>
To: ��� ������ <redacted>
CC: Linuxppc-embedded@ozlabs.org
Subject: Re: does Gianfar Ethernet Controller Version 1.1 support MARVELL
88E1111?
Date: Thu, 8 Jun 2006 11:15:32 -0500
On Jun 8, 2006, at 02:43, ��� ������ wrote:
quoted
Hi all,
I'm debugging my board with MPC 8540 and marvell 88e1111 designed
on it.
I'm sure the hardware connection is correct, and the phy's ID could
be read
through terminal port. But anyway, phy can not work. I wonder if it
is the
driver's problem? Since the Gianfar Ethernet Controller Version 1.1
surpport 88e1011s, but some 88e1111's registers are different from
88e1011s'. Actually I'm a new guy to Linux. Has anybody ever used
88e1111
phy in Linux envirenmemt? Please
give me some points. Thank you!
I have read the Gianfar ethernet controller driver, but it's
difficult for
me to find out the sofware flow.
It would be better if you upgraded to the latest kernel. The PHY
subsystem in the driver has changed significantly since version 1.1
of the driver. What leads you to believe that the PHY doesn't work?
What errors do you see? I'm fairly certain the 88e1111 works
with the 88e1011 driver, but it's been a while.
On Jun 8, 2006, at 12:51, Guo Jaffe wrote:
Hi Andy,
Thank you for your information. So the driver is not the issue, but
better to upgraded.
I will check the board once more. The PHY doesn't work because the
8bit bus between MAC and PHY is locked(TX_EN and RX_DV all disabled
from the scope's view) and also you can't see any signals exist at
the Magnetic side(nor LED signals). It seems that only MDC/MDIO and
CLOCK reference pin works. The PHY's ID must be read from MDC/MDIO
interface and Clocks are right showed on the scope.
But what error are you getting? What are the symptoms of your
problem? The GMII interface (the 8-bit bus) is inconsequential to
PHY configuration and management. Only the MDC/MDIO bus is used.
Therefore the PHY id should be quite readable. What version of Linux
are you using? Please describe what the kernel prints out when you
boot, and when you try to bring up the interface (assuming you don't
do that at boot).
Andy
From: Andy Fleming <redacted>
To: Guo Jaffe <redacted>
CC: Linuxppc-embedded@ozlabs.org
Subject: Re: does Gianfar Ethernet Controller Version 1.1 support MARVELL
88E1111?
Date: Thu, 8 Jun 2006 14:25:44 -0500
On Jun 8, 2006, at 12:51, Guo Jaffe wrote:
quoted
Hi Andy,
Thank you for your information. So the driver is not the issue, but
better to upgraded.
I will check the board once more. The PHY doesn't work because the
8bit bus between MAC and PHY is locked(TX_EN and RX_DV all disabled
from the scope's view) and also you can't see any signals exist
at the Magnetic side(nor LED signals). It seems that only MDC/MDIO
and CLOCK reference pin works. The PHY's ID must be read from
MDC/MDIO interface and Clocks are right showed on the scope.
But what error are you getting? What are the symptoms of your
problem? The GMII interface (the 8-bit bus) is inconsequential to
PHY configuration and management. Only the MDC/MDIO bus is used.
Therefore the PHY id should be quite readable. What version of
Linux are you using? Please describe what the kernel prints out
when you boot, and when you try to bring up the interface (assuming
you don't do that at boot).
Andy