EST SBC8260 and Canary CTX-1170

Brian Ford ford at vss.fsi.com
Wed Nov 29 06:19:13 EST 2000


On Mon, 27 Nov 2000, Dan Malek wrote:

> That driver either "supports" any PHY, or none at all, depending upon
> your perspective.  None of the command/status MII interface is in
> place to do anything.  None of those functions are called in the
> driver.  The QS6612 comment is left over from the 860T FEC driver I
> copied to get the framework for the FCC driver.
>
So does this mean that a "complete" implementation would have a
"command/status MII interface" or that a "complete" implementation does
not need one?

> From looking at the drivers, it appears they are a little out of
> date.  I have a newer one (that I was certain I checked in) that will
> interrogate the PHY.  In any case, this driver should work fine on
> any half duplex Ethernet, and you should see transmit packets in any
> case.
>
That seems to be my problem.  It is negotiating a full duplex link.

> > I know that the hardware can work, because the VxWorks boot rom loads
> > Linux successfully via this interface and MII.
>
> Then the driver must not be configuring the I/O lines correctly for
> some unknown reason, or you are running full duplex without the FCC
> initialized to do that.
>
Can you help point me to where I need to write code that would initialize
the FCC to do full duplex, or to have it auto-negotiate to half
duplex?  It is fairly problematic for me to force the other end to half
duplex and, ultimately, I would really like to run full.

Thank you for any information that would allow me to write such code.

--
Brian Ford
Software Engineer
Vital Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/





More information about the Linuxppc-embedded mailing list